> > You mentioned earlier some watchdog timeout. Do you know if you always > > see one when the pool corruption triggers? You can type "dmesg" at the > > ddb prompt to check if there's any weird message before the panic. > > > > No. I only see the watchdog timeout if I don't try to start netstart by > hand. > If it's only started in the boot process due to the existence of > /etc/hostname.re > then after a while I see a blue watchdog timeout for re0 but it does not > result > in the kernel panicking. > > If I start it manually then I immediately get a kernel panic. By > manually I mean: > - init tries to netstart, passes without crash but doesn't get an > address > - I run sh /etc/netstart immediately after logging in > > I just did that again to check dmesg from ddb. There's no watchdog entry > there > in this case. Just last boot message (WARNING: / was not properly > unmounted as I > had a hard crash) followed by the ddb 'panic' entry. > > I can reproduce this issue every time so can help with debugging it with > some > newbie guidance ;) >
One more thing. It's worth to note that this only happens when re0 is set to dhcp. If I manually assign an address the kernel doesn't panic and once I even had proper connectivity with manual ip setup. Regards, Adam
