Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[netbsd-5] wapbl assertion failure after crash
All,
after the following kernel panic
<snip>
May 21 11:55:01 Gstoder /netbsd: fatal double fault in supervisor mode
May 21 11:55:01 Gstoder /netbsd: trap type 13 code 80000000 eip c03e59f4
cs 8 eflags 10282 cr2 fffffff0 ilevel 0
May 21 11:55:01 Gstoder /netbsd: panic: trap
May 21 11:55:01 Gstoder /netbsd: Begin traceback...
May 21 11:55:01 Gstoder /netbsd: End traceback...
May 21 11:55:01 Gstoder /netbsd:
May 21 11:55:01 Gstoder /netbsd: dumping to dev 0,1 offset 1399
May 21 11:55:01 Gstoder /netbsd: dump succeeded
</snip>
<snip>
(gdb) target kvm /var/crash/netbsd.8.core
#0 0xc034b1ca in cpu_reboot ()
(gdb) bt
#0 0xc034b1ca in cpu_reboot ()
#1 0xc02d94c6 in panic ()
#2 0xc034df54 in trap ()
#3 0xc034e753 in trap_tss ()
#4 0xc010cb1b in Xtss_trap08 ()
(gdb)
</snip>
triggered by starting a linux binary (ICAclient), the netbsd-5 system
dropped to single-user, fsck(8) dying with the following wapbl assertion
failure:
<http://www.spg.tu-darmstadt.de/~hf/netbsd/netbsd-5-wapbl.jpg>
I've seen this problem three times so far. The only way out appears to
be a 'tunefs -l 0 /dev/rwd0[aefg...]' followed by 'mount -a'.
"Known issue", or should I send-pr?
hauke
--
The ASCII Ribbon Campaign Hauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
Respect for open standards Ruf +49-6151-16-3281
Home |
Main Index |
Thread Index |
Old Index