Re: panic: tcp_setpersist: retransmit pending

["Sepherosa Ziehau" <sepherosa@xxxxxxxxx>]

On Sun, Dec 14, 2008 at 9:44 PM, Rumko <rumcic@gmail.com> wrote:
> With almost latest -HEAD (from about Dec 13 01:30:43 CET) I get the mentioned
> panic. Panic message:
> panic: tcp_setpersist: retransmit pending
> mp_lock = 00000001; cpuid = 1
> Trace beginning at frame 0xdca71cfc
> panic(dca71d20,dd6e96a0,2,dd6e96a0,dca71d24) at panic+0x14d
> panic(c0544cf8,dd6e96a0,dca71d34,c033d52e,dd6e96a0) at panic+0x14d
> tcp_setpersist(dd6e96a0,1,dca71d50,c033d854,dd6e96a0) at tcp_setpersist+0x23
> tcp_timer_persist_handler(dd6e96a0,dd6e987c,1,dd6e987c,0) at
> tcp_timer_persist_handler+0x98
> tcp_timer_handler(dd6e987c) at tcp_timer_handler+0xa4
> netmsg_service(dd6e987c,0,1,ff8083b0,ff808000) at netmsg_service+0x79
> tcpmsg_service_loop(0,0,0,0,0) at tcpmsg_service_loop+0x1d
> lwkt_exit() at lwkt_exit
>
>
> I'm in the process of uploading the cores, but the connection seems a bit slow
> today so it will take quite a while.
>
> I can't reproduce this panic, since it happened while I was sleeping (I know
> rtorrent was running and I was updating applications from pkgsrc, but that
> should have been it).

There is slight difference between current tcp timer and original code
(even with the priority message, I committed yesterday).  The
difference lies within the callout_active() tests in !tcp_timer.c
files.  I will work out the solution within next 2~3 days.

Best Regards,
sephe

-- 
Live Free or Die