Date: Wed, 31 Dec 2003 03:20:11 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Stefan Ehmann <shoesoft@gmx.net> Cc: current@freebsd.org Subject: Re: page fault panic tracked down (selwakeuppri()) Message-ID: <20031231031218.N1268@gamplex.bde.org> In-Reply-To: <1072794615.775.4.camel@shoeserv.freebsd> References: <1072618904.757.12.camel@shoeserv.freebsd> <20031230173151.M6634@gamplex.bde.org> <1072794615.775.4.camel@shoeserv.freebsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 30 Dec 2003, Stefan Ehmann wrote:
> On Tue, 2003-12-30 at 07:56, Bruce Evans wrote:
> > I have farily large patches which do buffering in ext2fs in a different
> > way so that the 2003/08/28 changes are irrelevant. I will send these
> > in private mail.
>
> Applied the patches and rebuilt kernel. Unfortunately I got the same
> panic after 2 hours.
At least it's easy to duplicate, and another possible cause is ruled out.
Do you do anything special with ext2fs or have a special configuration?
It should be easy to turn off the selwakeuppri() chnages by editing a
line or two of selwakeuppri(). From sys_generic.c:
% /* Wake up a selecting thread. */
% void
% selwakeup(sip)
% struct selinfo *sip;
% {
% doselwakeup(sip, -1);
% }
%
% /* Wake up a selecting thread, and set its priority. */
% void
% selwakeuppri(sip, pri)
% struct selinfo *sip;
% int pri;
% {
% doselwakeup(sip, pri);
% }
Just change the last `pri' to -1.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031231031218.N1268>