From owner-freebsd-current@FreeBSD.ORG Sun Jan 4 07:04:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 880D016A4CE for ; Sun, 4 Jan 2004 07:04:34 -0800 (PST) Received: from email03.aon.at (WARSL402PIP6.highway.telekom.at [195.3.96.93]) by mx1.FreeBSD.org (Postfix) with SMTP id CB43A43D45 for ; Sun, 4 Jan 2004 07:04:32 -0800 (PST) (envelope-from shoesoft@gmx.net) Received: (qmail 171888 invoked from network); 4 Jan 2004 15:04:31 -0000 Received: from n755p030.dipool.highway.telekom.at (HELO ?212.183.104.94?) ([212.183.104.94]) (envelope-sender ) by qmail3rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 4 Jan 2004 15:04:31 -0000 From: Stefan Ehmann To: Bruce Evans In-Reply-To: <20040105003929.Y631@gamplex.bde.org> References: <200401030401.i0341O7E003439@gw.catspoiler.org> <20040105003929.Y631@gamplex.bde.org> Content-Type: text/plain Message-Id: <1073228674.1764.28.camel@shoeserv.freebsd> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 04 Jan 2004 16:04:34 +0100 Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: page fault panic tracked down (selwakeuppri()) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Jan 2004 15:04:34 -0000 On Sun, 2004-01-04 at 14:48, Bruce Evans wrote: > On Fri, 2 Jan 2004, Don Lewis wrote: > My not seeing any problems is consistent with my not using any sound > drivers. > > Did you rule out an invalid file system? I just tested -current and > was reminded that it doesn't reboot cleanly if ext2fs is mounted. > The unclean reboot doesn't affect r/o mounts of ext2fs. OTOH, r/o > mounts of dirty file systems are permitted and there is no easy way > to fsck ext2fs file systems under FreeBSD. (I use fsck.ext2fs from > the e2fsprogs port, but it still needs a block device or filesystem > image to work correctly so it hasn't been easy to use since block > devices were axed. I sometimes copy file systems to regular files > to use it.) I already thought of an invalid file system. But I think it would be very unlikely that it only causes panics with the selwakeuppri() changes. I normally mount it read only and unmount it manually before shutdown to avoid these problems. Last time when I mounted it rw and the system crashed I had big troubles repairing it again. In fact I gave up repairing it under FreeBSD (always complained about wrong superblock - ro mounting was working fine though). Finally repaired it using Knoppix which also had troubles. I only found 1 of about 10 superblock backups working.