Hi,

an up-to-date netbsd-2 i386 system crashed today:

db> dmesg
[...]
viaide0:0:1: lost interrupt
        type: ata tc_bcount: 0 tc_skip: 0
db> bt
ltsleep(c03a4db8,10,c02d6d2f,1,0) at netbsd:ltsleep+0x6b
wdcwait(c0c45900,48,40,3e8,9) at netbsd:wdcwait+0xa5
__wdccommand_start(c0c45900,c0d97000,0,c0d98904,c0d98904) at netbsd:__wdccommand_start+0x73
wdcstart(c0c45900,c0d97034,c03a4e50,c0d37b00,4000) at netbsd:wdcstart+0xb1
wdc_ata_bio_intr(c0c45900,c0d97034,1,1,c03a4e7c) at netbsd:wdc_ata_bio_intr+0x18a
wdcintr(c0c45900,0,7aad0010,30,580e0010) at netbsd:wdcintr+0xda
Xintr_legacy14() at netbsd:Xintr_legacy14+0xa8
--- interrupt ---
cpu_switch(c0354400,0,cb762000,c024ebd9,1) at netbsd:cpu_switch+0x9f
ltsleep(c0354260,4,c02dc1c2,0,0) at netbsd:ltsleep+0x323
uvm_scheduler(c0354240,0,c03587dc,c02d9069,0) at netbsd:uvm_scheduler+0x74
main(0,0,0,0,0) at netbsd:main+0x67f
bt> 

(Not being sure what to do, I also captured output of 'show registers'
and 'ps /[anw]' but don't include it here; please tell if I should do
so.)

Unfortunately I wasn't able to get a crash dump.

This system was running fine for about a year; I didn't notice any
recent pullups which might have caused this crash, but probably I'm
missing something. Has anybody encountered this bug before? Should I
send-pr?


Regards, Jukka

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~