rt remote free backtrace (#2)

Sepherosa Ziehau sepherosa at gmail.com
Thu Oct 30 07:06:09 PDT 2008

On Thu, Oct 30, 2008 at 10:06 AM, Sepherosa Ziehau <sepherosa at gmail.com> wrote:
> On Thu, Oct 30, 2008 at 12:12 AM, Peter Avalos <pavalos at theshell.com> wrote:
>> On Thu, Sep 11, 2008 at 07:36:02PM +0800, Sepherosa Ziehau wrote:
>>> Hi all,
>>> I have committed a patch to HEAD, which will print backtrace if
>>> rtfree_remote() is called.  If you see this kind of messages on your
>>> console, please post them to bugs at .  If you think your box could
>>> afford panicking (mainly to get coredumps), you could set
>>> net.route.remote_free_panic to 1, and post the URL to the coredump so
>>> we could fetch and debug it.
>> Here's a different one I got twice yesterday:
>> rt remote free rt_cpuid 1, mycpuid 0
>> Trace beginning at frame 0xda6f5c90
>> rtfree_remote(c0371380,1,0,da6f5cf4,c023dc8d) at rtfree_remote+0x74
>> rtfree_remote(f059e120,1) at rtfree_remote+0x74
>> rtfree(f059e120,daa41080,da6f5d14,c023e36c,daa44680) at rtfree+0x2e
>> in_rtchange(daa44680,0) at in_rtchange+0x14
>> in_pcbnotifyall(c0421f58,91fa5e77,0,c023d65a) at in_pcbnotifyall+0x46
>> udp_ctlinput(f,d73c9bf8,0,0,da6f5d68) at udp_ctlinput+0x10f
>> netmsg_pru_ctlinput(d73c9b1c,0,c0421f24,da6f5d84,c0233f7a) at
>> netmsg_pru_ctlinput+0x13
>> netmsg_service(d73c9b1c,1,0,c03f3934,ff800000) at netmsg_service+0x44
>> netmsg_service_loop(c0421f24,0,0,0,0) at netmsg_service_loop+0x18
>> lwkt_exit() at lwkt_exit
> Ok, I see.  We need to locate the msgport based on 'cmd' paraeter
> passed to pr_ctlport too.  And forwarding in_pcbnotifyall() to all
> related msgports (i.e. all udp msgports or all tcp msgports).  I will
> give you a patch to try when I get home.

Please test/review following patch:

Best Regards,

Live Free or Die

More information about the Bugs mailing list