On 1/19/06, Tamas TEVESZ <[EMAIL PROTECTED]> wrote: > barghest:/etc/ppp# chmod 06panic: ffs_read: type 0
can you perform some mem / hw testing? this smells like disk corruption. > as a strange addition, it seems that the board can pretty > reliably be panicked with the following: > > > barghest:~# sysctl ddb.console=1 > ddb.console: 0 -> 1 # then send a break > barghest:~# Stopped at Debugger+0x4: leave > ddb> boot > sync crash dump halt reboot poweroff > ddb> boot sync > syncing disks... panic: tsleep > it seems always to give this same response to the same sequence of > actions. > > granted, i'm not very frequent at intentionally dropping boxes to ddb > then trying to screw them, but it isn't really supposed to work that > way, is it? the problem is, once you're in ddb, interrupts and the scheduler are forcibly stopped, and sometimes they don't like coming back to life. spend less time in ddb, you'll be happier. :)
