From owner-freebsd-current@FreeBSD.ORG Thu Nov 29 06:25:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69FEA16A41B for ; Thu, 29 Nov 2007 06:25:58 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp4.yandex.ru (smtp4.yandex.ru [213.180.223.136]) by mx1.freebsd.org (Postfix) with ESMTP id 88E3E13C45D for ; Thu, 29 Nov 2007 06:25:57 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:52420 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S738068AbXK2GZr (ORCPT + 1 other); Thu, 29 Nov 2007 09:25:47 +0300 X-Comment: RFC 2476 MSA function at smtp4.yandex.ru logged sender identity as: bu7cher Message-ID: <474E5B69.7070406@yandex.ru> Date: Thu, 29 Nov 2007 09:25:45 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: John Baldwin References: <73807.10710.qm@web63912.mail.re1.yahoo.com> <200711280842.09340.jhb@freebsd.org> <474D726A.8080807@deepcore.dk> <200711280938.38545.jhb@freebsd.org> In-Reply-To: <200711280938.38545.jhb@freebsd.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Barney Cordoba , freebsd-current@freebsd.org, =?KOI8-R?Q?S=3Fren_Schmidt?= , Anton Yuzhaninov Subject: Re: Any successful installs on a Broadcom HT1000 chipset? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2007 06:25:58 -0000 John Baldwin wrote: > Again, on the machines I'm seeing this on it was totally disabled. I don't think > I can totally disable DMA (NICs etc. must use DMA) on the machines and since they > are in production and I only see the corruption as an after-effect when the boxes > panic or deadlock for another reason I'm not easily able to reproduce this. Also, > we do disable MSI for devices behind HT2000 chipsets because of a chip bug, but > not on HT1000 currently. However, MSI isn't on on 6.x anyway. Hi, John. Anton Yuzhaninov has mentioned in the top of this thread that this bug may be easy reproduced by using external PCI-X card. He tried use PCI-X Marvell card and got lots of corruptions on the integrated HT1000. Can you or Soren try the same way to reproduce? -- WBR, Andrey V. Elsukov