On Tue, Mar 7, 2017 at 3:05 AM, Tom Ivar Helbekkmo <tih%hamartun.priv.no@localhost> wrote:
Ryota Ozaki <ozaki-r%NetBSD.org@localhost> writes:
<tih%hamartun.priv.no@localhost> wrote:
No idea, I'm afraid. I'll just have to provoke another one.
It seems rather unwilling to crash again. It's possible, I guess, that
the last one was actually due to the corrupted file system, which I
fixed. I'll keep trying, anyway.
Thanks.
I also encountered the ffs panic. It seems to happen on bootup after
a kernel panicked and a filesystem became unclean. It's not related to
neither NFS nor re(4). I guess it's because of a recent ffs/vfs change.
BTW sysctl -w ddb.onpanic=1 may help to avoid losing the first crash.
I've been wondering about that: will it do the right thing if the system
crashes while I'm using X on the console? I assume it has to switch to
a text-based virtual console, and then run the debugger on that?
Oh, I have no idea when using X because I don't use X daily. I guess you
need to switch to a console beforehand to see DDB on a kernel panic.
ozaki-r