From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 08:52:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 47CE116A41F for ; Sun, 20 Nov 2005 08:52:15 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA0A43D45 for ; Sun, 20 Nov 2005 08:52:12 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jAK8rXPx084388; Sun, 20 Nov 2005 08:53:33 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jAK8rXo5084387; Sun, 20 Nov 2005 08:53:33 GMT (envelope-from dunstan) Date: Sun, 20 Nov 2005 08:53:33 +0000 From: "Wojciech A. Koszek" To: Doug White Message-ID: <20051120085333.GB84297@freebsd.czest.pl> References: <20051119170018.GA75757@freebsd.czest.pl> <20051119164627.R88861@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20051119164627.R88861@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Panic after memory dump and machine reboot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Nov 2005 08:52:15 -0000 On Sat, Nov 19, 2005 at 04:47:19PM -0800, Doug White wrote: > On Sat, 19 Nov 2005, Wojciech A. Koszek wrote: > > > Hello, > > > > I noticed very strange problem on -CURRENT. If I get a panic, system writes > > core and reboots. Just after reboot, filesystem check (yes, I sometimes > > forget about sync'ing/mounting in read-only mode) kernel gets another panic, > > which is not (directly?) related with this first one -- problem lies > > somewhere in syscons(4). > > Can you please explain in more detail what you are doing when you say > "filesystem check"? From this, it sounds like you are running fsck while > the FS is mounted, which will cause this behavior. No, I don't check mounted filesystem. I'll try to explain it once again. I mean filesystem checking process, since after kernel panic, filesystem isn't clean. Then, it's being checked with fsck(8). I don't use mount(8), since I have no access to login prompt yet. Kernel panics just after fsck(8) finishes, probably when vidcontrol is executed (see dmesg.txt from link). This situation causes continous panics/filesystem checks, thus making system available to normal use. I have to boot from CD and run fsck(8) on root filesystem. If I succeed in repeating this problem, I'll post additional information. -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl