Hi again!

Got another "panic: should call debugger here (aha1542.c)" crash, this
time from a runing system doing heavy disk I/O.  I've got the crash
dump, but not the expertise to figure out much from it.  I was running
without DDB, obviously, so my machine rebooted before I could see what
aha.c printed to the screen before crashing and rebooting.  I'm now
compiling a new kernel with DDB support as I type this.

Wild hunch time:  I've got my disks configured to send error reports
for recovered media errors, because it's nice to get these messages
/before/ stuff gets serious:

Mar 23 13:51:09 barsoom /netbsd: sd0(aha0:0:0): soft error (corrected), info = 546853 (decimal), data = 00 00 00 00 17 00 00 00 00 00

Will your new driver handle such reports like the old one did, or
could that be what caused my crash today -- i.e. an unsolicited
message from the controller being treated as a reason to panic?

-tih
--
Tom Ivar Helbekkmo
tih@Hamartun.Priv.NO