[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-amd64/39283: Kernel crash on Dell Poweredge 2950
The following reply was made to PR port-amd64/39283; it has been noted by GNATS.
To: "Mindaugas Rasiukevicius" <rmind%netbsd.org@localhost>
Subject: Re: port-amd64/39283: Kernel crash on Dell Poweredge 2950
Date: Tue, 24 Nov 2009 22:02:08 +0100
>> > Synopsis: 4.99.71 crashed after about 3-4 days when running MP-kernel
>> > State-Changed-From-To: open->feedback
>> > State-Changed-By: dsl%NetBSD.org@localhost
>> > State-Changed-When: Fri, 06 Nov 2009 22:49:43 +0000
>> > State-Changed-Why:
>> > Any further info ??
>> No more than the info that we put in the PR and on the mailing lists:
>> The server crashed every 8'th day on SP-kernel and every 24'th hour
>> MP-kernel. The problem has evolved with NetBSD releases, these days
>> "only" the filesystem that seems to hang and no i/o is possible without
>> reboot, if it runs to long without reboot is eventually crashed.
> Seems there is not yet enough information to figure out where bug is
> Also, it the only problem report with such symptoms, but if it is
> consistently and crashing the same way - unlikely to be a hardware
> Looking at the data from your email, there is callback_run_roundrobin()
> calls a function pointer, but it is very unlikely to be NULL. I have
> added an
> assert, "just in case":
> Would you be able to try -current kernel, with that change in the link,
> with the following debug options:
> options DIAGNOSTIC
> options DEBUG
> makeoptions DEBUG="-g -fno-omit-frame-pointer"
> Then repeat x/Lx and x/I dance again. But no LOCKDEBUG option, as it
> avoid some overhead and hopefully get stack dump a little bit more
> Additionally, 'show uvm' output from DDB might be useful.
Thanks for the response.
We will try a current kernel tonight and report back with the result.
Main Index |
Thread Index |