Panic after memory dump and machine reboot

Wojciech A. Koszek dunstan at freebsd.czest.pl
Sun Nov 20 00:52:15 PST 2005


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 at FreeBSD.czest.pl


More information about the freebsd-current mailing list