Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 Dec 2003 12:03:06 +0100
From:      Stefan Ehmann <shoesoft@gmx.net>
To:        Scott Long <scottl@freebsd.org>
Cc:        current@freebsd.org
Subject:   Re: page fault panic tracked down (selwakeuppri())
Message-ID:  <1072868585.5107.11.camel@shoeserv.freebsd>
In-Reply-To: <3FF2A6CC.9010207@freebsd.org>
References:  <1072618904.757.12.camel@shoeserv.freebsd> <20031230173151.M6634@gamplex.bde.org> <1072794615.775.4.camel@shoeserv.freebsd> <20031231031218.N1268@gamplex.bde.org><3FF2A6CC.9010207@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2003-12-31 at 11:37, Scott Long wrote:
> Stefan Ehmann wrote:
> > On Tue, 2003-12-30 at 17:20, Bruce Evans wrote:
> > 
> >>On Tue, 30 Dec 2003, Stefan Ehmann wrote:
> >>
> >>
> >>>On Tue, 2003-12-30 at 07:56, Bruce Evans wrote:
> >>It should be easy to turn off the selwakeuppri() chnages by editing a
> >>line or two of selwakeuppri().  From sys_generic.c:
> > 
> > 
> > Thanks. So I can (hopefully) run a recent CURRENT somewhat stable at
> > least until this is resolved.
> > 
> 
> Does Bruce's hack actually work for you?  I'm trying to decide on
> whether to make this a show-stopper for the 5.2 release.

It worked at least with the 2003.11.09.09.20.00 kernel (>5 hours
tested). I upgraded to yesterday's current to see if this runs fine too
with that one line change.

I'm also testing if it still crashes unpatched just to be sure it wasn't
fixed - It's very unlikely but the last current I tested is about 2
weeks old.

I'll report this later today.



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