From owner-freebsd-bugs@FreeBSD.ORG Wed Mar 17 23:40:15 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2178416A4CE for ; Wed, 17 Mar 2004 23:40:15 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 168DD43D2D for ; Wed, 17 Mar 2004 23:40:15 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i2I7eEbv042697 for ; Wed, 17 Mar 2004 23:40:14 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i2I7eE7R042696; Wed, 17 Mar 2004 23:40:14 -0800 (PST) (envelope-from gnats) Date: Wed, 17 Mar 2004 23:40:14 -0800 (PST) Message-Id: <200403180740.i2I7eE7R042696@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: =?KOI8-R?Q?S=3Fren_Schmidt?= Subject: Re: kern/60526: Post-PAE stable SMP machine freezes X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?KOI8-R?Q?S=3Fren_Schmidt?= List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2004 07:40:15 -0000 The following reply was made to PR kern/60526; it has been noted by GNATS. From: =?KOI8-R?Q?S=3Fren_Schmidt?= To: Eugene Grosbein Cc: bug-followup@FreeBSD.ORG, sos@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: kern/60526: Post-PAE stable SMP machine freezes Date: Thu, 18 Mar 2004 08:30:02 +0100 Eugene Grosbein wrote: > Hi! > > According to > http://freebsd.rambler.ru/bsdmail/freebsd-hackers_2003/msg03936.html > the problem may be related to the > and ATA write cache (hw.ata.wc=1). > > Note however, I had no kernel panic with post-PAE STABLE. > I had kernel lockup. I can understand kernel panic due to the faulty > devices but not endless loop that it seems to happen. > > It's known (and noted in the Errata for 4.9-RELEASE) > that PAE integration broke hw.ata.tags. Perhaps, its time > either to document that hw.ata.wc is broken for noted controller too, > either to forbid write cache for it by force. I have a hard time beliving WC can be the problem. WC is a function of the disk drive it has nothing todo with the controller or even the way we talk to the disk... That said, the ROSB4 is known to be wierd, bad things can easily happend with it in some setups and there is noting we can do about it in SW (less using PIO mode). However some HW vendors seem to have found a HW solution to the problem (ASUS is one of them, my old CUR-DLS doesn't show the problems at all)... -- -S?ren