Date: Tue, 30 Dec 2003 18:28:28 +0100 From: Stefan Ehmann <shoesoft@gmx.net> To: Bruce Evans <bde@zeta.org.au> Cc: current@freebsd.org Subject: Re: page fault panic tracked down (selwakeuppri()) Message-ID: <1072805308.1349.13.camel@shoeserv.freebsd> In-Reply-To: <20031231031218.N1268@gamplex.bde.org> References: <1072618904.757.12.camel@shoeserv.freebsd> <20031230173151.M6634@gamplex.bde.org> <1072794615.775.4.camel@shoeserv.freebsd> <20031231031218.N1268@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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: > > > 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? On this partition my music collection is stored. Normally I run cplay (CLI music player) in shuffle mode. So there is a low but constant load on the drive. I'm not sure about this, but at least sometimes the panics seems to happen immediately after a new file is opened. The only special thing I can think about is that I created it with the largefile4 (one inode per 4 megabytes) option in knoppix. As I mentioned above it is mounted read-only. > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1072805308.1349.13.camel>