Date: Wed, 18 Oct 2006 20:07:29 +0100 From: Tom Judge <tom@tomjudge.com> To: Kris Kennaway <kris@obsecurity.org> Cc: Jason Thomson <jason.thomson@mintel.com>, freebsd-stable@freebsd.org, Conrad Burger <conrad.burger@gmail.com> Subject: Re: When will the new BCE driver in HEAD be incorporated into RELENG_6? Message-ID: <45367B71.40704@tomjudge.com> In-Reply-To: <20061018175257.GA97258@xor.obsecurity.org> References: <d0c4d1610610180258l1fb94e96m349022fcb2d0330c@mail.gmail.com> <45364782.8090209@samsco.org> <45366122.6090704@mintel.com> <20061018175257.GA97258@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Wed, Oct 18, 2006 at 06:15:14PM +0100, Jason Thomson wrote: > >> Using the driver from HEAD* in the latest RELENG_6 didn't fix our >> problems. >> >> We could still trigger the Watchdog timeout when copying a local file to >> an NFS mounted filesystem (UDP mount, GigE speeds). >> >> It was also possible to trigger this bug with multiple simultaneous TCP >> streams, but that took a little longer. >> >> Copying a local file to an NFS/UDP filesystem would trigger the bug in a >> few seconds. >> >> If there's anything we can do to help debug this, please let us know. >> > > Per my previous mails, the (known) bce watchdogs are symptoms of > driver bugs which can be usefully converted into panics by enabling > INVARIANTS and INVARIANT_SUPPORT. Please do so, then report what > happens. > > Kris > Hi Kris, I am a colleague of Jason's, when we were testing this patch the kernel used had both options set: option INVARIANTS option INVARIANT_SUPPORT Although on several boxes we have failed to cause a kernel panic, only watchdog timeouts. However the last crash that we reproduced did trigger several: bce: need to defrag Messages on the console before the watchdob timeout occured. Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45367B71.40704>