Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 18 Jun 2005 13:47:32 -0700 (PDT)
From:      Mitch Parks <mitch@kuoi.asui.uidaho.edu>
To:        freebsd-stable@freebsd.org
Subject:   Re: 5.4-p1 crash
Message-ID:  <20050618133936.P1236@kuoi.asui.uidaho.edu>
In-Reply-To: <20050618192721.GA34601@frontfree.net>
References:  <20050617150950.F1236@kuoi.asui.uidaho.edu> <20050617235352.GA80058@xor.obsecurity.org> <20050618192721.GA34601@frontfree.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 19 Jun 2005, Xin LI wrote:

> On Fri, Jun 17, 2005 at 07:53:52PM -0400, Kris Kennaway wrote:
>> On Fri, Jun 17, 2005 at 03:23:19PM -0700, Mitch Parks wrote:
>>> Below are details regarding another crash on a Dell 2600 SMP (HTT and USB
>>> disabled). It has been 9 days since the last crash. I didn't have the
>>> serial console in place for this last crash, but it is now.
>>>
>>> [snip]
>>> Since Dell diagnostics and Memtest check out fine, I'm kind of between a
>>> rock and a hard place here. I have a similar 2600 running 4.9 that is
>>> working great. I'd welcome any advice.
>>
>> Unfortunately this is a known bug in FreeBSD; check the archives for
>> more discussion.  Doug White tried to look at fixing it before
>> 5.4-RELEASE but I think he gave up.
>
> Just curious...
>
> What's the problem?  Is there known steps that can trigger it quickly so
> we can grab the bug?

For my occurrence, I haven't found a predictable way to make it crash. 
Though I haven't *tried* to trigger it. Crashes have been at seemingly 
random times with no particular correlational activities that have been 
detected.

If there are particular benchmark, performance or other tools I could use to 
try and trigger it, let me know if that will help.

Mitch Parks




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050618133936.P1236>