Well,
this is fun...
Just caught panic #3 on my Diablo newstransit box running 4.0 from the
7th of February.
This box pushes around 360-380 GB in a weekend on network IO.
panic: tcp_setpersist: retransmit pending
Debugger("panic")
Stopped at Debugger+0x35: movb $0,in_Debugger.354
db> trace
Debugger(c01e8063) at Debugger+0x35
panic(c01eddc0,d5ce6b60,d8d8bc48,c018bcb6,d5ce6b60) at panic+0x70
tcp_setpersist(d5ce6b60,d5ce6b60,c018bc24,d8d8bc6c,c0149279) at
tcp_setpersist+0x2c
tcp_timer_persist(d5ce6b60,40000000,160,c1cd0000,cdfae000) at
tcp_timer_persist+0x92
softclock(0,c0160010,cc4d0010,cc4d0010,cdfae000) at softclock+0xd1
doreti_swi(c1d7d000,50b0,2000) at doreti_swi+0xf
ffs_reallocblks(d8d8be04) at ffs_reallocblks+0x3d0
cluster_write(cc5213e8,4332000,0) at cluster_write+0x15a
ffs_write(d8d8bea0,d8cf79c0,fdc,c1f14800,c0201e80) at ffs_write+0x476
vn_write(c1f14800,d8d8beec,c1d30500,0,d8cf79c0) at vn_write+0xda
dofilewrite(d8cf79c0,c1f14800,6,280be020,fdc) at dofilewrite+0x91
write(d8cf79c0,d8d8bf80,280be000,15,280be000) at write+0x33
syscall(bfbf002f,280a002f,bfbf002f,280be000,15) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26
This is from the serial console. I'm going to dump the memory to swap
now and do some gdb with my kernel.debug.
Advice is wanted and highly appreciated.
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
<[EMAIL PROTECTED]> bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
