From owner-freebsd-current@FreeBSD.ORG Wed Nov 28 07:45:19 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32CBF16A417; Wed, 28 Nov 2007 07:45:19 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id B89C313C478; Wed, 28 Nov 2007 07:45:18 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.local (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id lAS7jGW5057824; Wed, 28 Nov 2007 08:45:16 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <474D1C8C.2060304@deepcore.dk> Date: Wed, 28 Nov 2007 08:45:16 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: John Baldwin References: <73807.10710.qm@web63912.mail.re1.yahoo.com> <474C71B1.1080104@deepcore.dk> <200711271639.09601.jhb@freebsd.org> In-Reply-To: <200711271639.09601.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Barney Cordoba , freebsd-current@freebsd.org, current@freebsd.org 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: Wed, 28 Nov 2007 07:45:19 -0000 John Baldwin wrote: > > FYI, I've seen weird in-memory corruption with machines with the HT1000= _S1=20 > atapci device. In all the cases I've seen so far, a single page is cor= rupted=20 > with garbage and the page happens to be used by UMA to hold credentials= =20 > including proc0's credentials. I've seen this corruption (trashed cred= s for=20 > proc0 and other creds in that page) on many of the same boxes (Dell 143= 5's=20 > IIRC) running on 6.2. I've tried switching the HT1000_S1 to use SWKSMI= O=20 > rather SWKS100 as I mentioned to you in an earlier e-mail (the Linux dr= iver=20 > uses equivalent of SWKSMIO FWIW) but don't have any conclusive tests on= that. > > =20 OK, seems the chipset has some real problems, I have digged through all=20 the (very little) docs and info I got from serverworks back when, and=20 the only thing I can find is that the chips doesn't support MSI in any=20 shape or fashion or it will do really strange things. Now on my system it seems to be disabled but I'm not sure yet how its=20 determined to be that way. Would be worth for you guys to check what the = sysctl's "hw.pci.enable_msi" and "hw.pci.enable_msix" are set to. I havn't looked into this yet, but I'm pretty sure we added MSI support=20 in the 6.2 -> 7.0 timeframe, so that might have uncovered this chipset=20 bug, and possibly the Promise data corruption one as well. -S=F8ren