|
|
The following reply was made to PR port-amd64/39283; it has been noted by GNATS.
From: fredrik@xxxxxxxxx
To: gnats-bugs@xxxxxxxxxx
Cc: port-amd64-maintainer@xxxxxxxxxx,
gnats-admin@xxxxxxxxxx,
netbsd-bugs@xxxxxxxxxx,
fredrik@xxxxxxxxx
Subject: Re: port-amd64/39283: Kernel crash on Dell Poweredge 2950
Date: Sun, 23 Nov 2008 15:52:10 +0100 (CET)
> The following reply was made to PR port-amd64/39283; it has been noted by
> GNATS.
>
> From: David Holland <dholland-bugs@xxxxxxxxxx>
> To: fredrik@xxxxxxxxx
> Cc: David Holland <dholland-bugs@xxxxxxxxxx>, gnats-bugs@xxxxxxxxxx,
> port-amd64-maintainer@xxxxxxxxxx, gnats-admin@xxxxxxxxxx,
> netbsd-bugs@xxxxxxxxxx
> Subject: Re: port-amd64/39283: Kernel crash on Dell Poweredge 2950
> Date: Wed, 19 Nov 2008 06:50:28 +0000
>
> On Mon, Sep 01, 2008 at 08:01:01AM +0200, fredrik@xxxxxxxxx wrote:
> > > > > My guess is a bad callout, but that doesn't narrow it down very
> much.
> > > [...]
> > > @@ -722,6 +722,7 @@ callout_softclock(void *v)
> > > [...]
> > > + KASSERT(func != NULL);
> >
> > We are already running with DEBUG and DIAGNOSTIC, hopefully it will be
> a
> > little more verbose after your patch.
>
> Have you seen this again recently? PR 39655, which might be the same
> problem, was fixed in -current on October 10.
>
> --
> David A. Holland
> dholland@xxxxxxxxxx
>
>
We did a test with 5.0_BETA and the machines was alive for about 23 hours
then it paniced.
Regards
Fredrik
|
|