Panic: ad0: WARNING - removed from configuration

[Tom Jensen]

Hi
 
Seen this panic twice, there seems to be no pattern and I have no idea what
triggers this, is it failing hardware?
 
System: FreeBSD 5.4-STABLE FreeBSD 5.4-STABLE #10: Sat Nov  5 17:14:46 CET
2005
 
db> show msgbuf
msgbufp = 0xc101cfe4
magic = 63062, size = 32740, r= 33501, w = 63892, ptr = 0xc1015000, cksum=
3187082
ad0: WARNING - removed from configuration
swap_pager: I/O error - pagein failed; blkno 5212,size 4096, error 0
vm_fault: pager read error, pid 282 (syslogd)
<6>pid 282 (syslogd), uid 0: exited on signal 11
ata0-master: FAILURE - WRITE_DMA timed out
initiate_write_filepage: already started
swap_pager: I/O error - pagein failed; blkno 6496,size 12288, error 6
vm_fault: pager read error, pid 657 (courierlogger)
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
.
. [snip] 
.
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
initiate_write_filepage: already started
panic: newdirrem: not ATTACHED
KDB: enter: panic
 
db> tr
Tracing pid 490 tid 100088 td 0xc1769c00
kdb_enter(c08404d5) at kdb_enter+0x2b
panic(c0853a7c,c08d2638,c2885460,c2878580,c1d8ece4) at panic+0xbb
newdirrem(c502e680,c1fa3c08,c21d4000,0,ceb92998) at newdirrem+0x163
softdep_setup_directory_change(c502e680,c1fa3c08,c21d4000,d0588,0) at
softdep_setup_directory_change+0x67
ufs_dirrewrite(c1fa3c08,c21d4000,d0588,8,0) at ufs_dirrewrite+0x8d
ufs_rename(ceb92bd8,ceb92cc4,c0684601,ceb92bd8,c1d8ece4) at ufs_rename+0x9a1
ufs_vnoperate(ceb92bd8,c1d8ece4,c203ae10,c15be000,c08e0c80) at
ufs_vnoperate+0x13
kern_rename(c1769c00,8248500,8248900,0,ceb92d30) at kern_rename+0x2e1
rename(c1769c00,ceb92d04,2,672,296) at rename+0x15
syscall(2f,284e002f,bfbf002f,284e6000,0) at syscall+0x2ab
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (128, FreeBSD ELF32, rename), eip = 0x2845a22b, esp =
0xbfbfe37c, ebp = 0xbfbfe3d8 ---
db> call doadump
Cannot dump. No dump device defined.
0x25
db> reset
 
Running a savecore gives this, but I'm not sure if it's relevant
 
bash-2.05b# savecore -f /var/crash/ /dev/ad0s1b 
savecore: reboot after panic: kmem_malloc(4096): kmem_map too small:
62877696 total allocated
savecore: writing core to vmcore.38

Thanks

- Tom