Date: Mon, 29 Dec 2003 08:58:32 -0700 From: Scott Long <scottl@freebsd.org> To: Stefan Ehmann <shoesoft@gmx.net> Cc: current@freebsd.org Subject: Re: page fault panic tracked down (selwakeuppri()) Message-ID: <3FF04F28.5000306@freebsd.org> In-Reply-To: <1072618904.757.12.camel@shoeserv.freebsd> References: <1072618904.757.12.camel@shoeserv.freebsd>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan Ehmann wrote: > Some weeks ago I posted about a panic in 5.2-BETA. > > After accessing a read-only ext2fs for some hours I got a "page fault" > panic (or rarely a "getblk: size(7537385) > MAXBSIZE(65536)"). The > backtrace was always somewhat different. You can read about it a bit > more detailed here: > > http://lists.freebsd.org/pipermail/freebsd-current/2003-November/015405.html > > After lots of buildworld and buildkernel I finally was able to detect > the commit that caused this panic. > > Current from 2003.11.09.09.00.00 runs fine for > 10 hours. Current from > 2003.11.09.09.20.00 crashed twice within less than 2 hours. > > The only src/sys commit in that time is > http://lists.freebsd.org/pipermail/cvs-src/2003-November/013515.html > where selwakeup()s is replaced with selwakeuppri(). > > So the problem must be somewhere in selwakeuppri(). > > I hope this can be resolved now. > Thanks for tracking this down! Just for completeness, can you send a verbose dmesg? Thanks! Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FF04F28.5000306>