Messages in this thread |  | | | Date | Mon, 8 Nov 2010 21:55:11 +0100 | | From | Markus Trippelsdorf <> | | Subject | Re: 2.6.37-rc1-git5 -- WARNING: at net/ipv4/devinet.c:137 in_dev_finish_destroy+0x3d/0x6e() |
| |
On Mon, Nov 08, 2010 at 09:46:31PM +0100, Eric Dumazet wrote: > Le lundi 08 novembre 2010 à 21:42 +0100, Markus Trippelsdorf a écrit : > > On Mon, Nov 08, 2010 at 09:29:26PM +0100, Eric Dumazet wrote: > > > Le lundi 08 novembre 2010 à 12:06 -0800, Paul E. McKenney a écrit : > > > > On Mon, Nov 08, 2010 at 02:56:06PM -0500, Miles Lane wrote: > > > > > WARNING: at net/ipv4/devinet.c:137 in_dev_finish_destroy+0x3d/0x6e() > > > > > > > > Ilpo, thoughts? > > > > > > > > > > Hmm... > > > > > > WARN_ON(idev->mc_list); > > > > > > Might be a problem with refcounts somewhere... > > > > I have similar warnings in my logs, although its at > > net/ipv4/devinet.c:136 in my case. Happened altogether three times in > > the last few days and they all look the same: > > > > Nov 5 17:31:35 arch kernel: WARNING: at net/ipv4/devinet.c:136 in_dev_finish_destroy+0x5c/0x90() > > Nov 5 17:31:35 arch kernel: Hardware name: System Product Name > > Nov 5 17:31:35 arch kernel: Pid: 0, comm: kworker/0:1 Not tainted 2.6.37-rc1-00027-gff8b16d-dirty #4 > > Nov 5 17:31:35 arch kernel: Call Trace: > > Nov 5 17:31:35 arch kernel: <IRQ> [<ffffffff8105c9f6>] ? warn_slowpath_common+0x76/0xc0 > > Nov 5 17:31:35 arch kernel: [<ffffffff8141889c>] ? in_dev_finish_destroy+0x5c/0x90 > > Nov 5 17:31:35 arch kernel: [<ffffffff813c49e8>] ? dst_destroy+0x68/0x120 > > Nov 5 17:31:35 arch kernel: [<ffffffff813e888f>] ? dst_rcu_free+0x1f/0x30 > > Nov 5 17:31:35 arch kernel: [<ffffffff81090e0c>] ? __rcu_process_callbacks+0xfc/0x2f0 > > Nov 5 17:31:35 arch kernel: [<ffffffff8109103f>] ? rcu_process_callbacks+0x3f/0x70 > > Nov 5 17:31:35 arch kernel: [<ffffffff810621bc>] ? __do_softirq+0x9c/0x120 > > Nov 5 17:31:35 arch kernel: [<ffffffff81030fc9>] ? timer_interrupt+0x19/0x30 > > Nov 5 17:31:35 arch kernel: [<ffffffff8102ea4c>] ? call_softirq+0x1c/0x30 > > Nov 5 17:31:35 arch kernel: [<ffffffff8103080d>] ? do_softirq+0x4d/0x80 > > Nov 5 17:31:35 arch kernel: [<ffffffff8106232d>] ? irq_exit+0x8d/0x90 > > Nov 5 17:31:35 arch kernel: [<ffffffff810306c7>] ? do_IRQ+0x67/0xe0 > > Nov 5 17:31:35 arch kernel: [<ffffffff8144a153>] ? ret_from_intr+0x0/0xa > > Nov 5 17:31:35 arch kernel: <EOI> [<ffffffff81035ba0>] ? default_idle+0x20/0x40 > > Nov 5 17:31:35 arch kernel: [<ffffffff81035c12>] ? c1e_idle+0x52/0xf0 > > Nov 5 17:31:35 arch kernel: [<ffffffff8102c12c>] ? cpu_idle+0x4c/0xa0 > > Nov 5 17:31:35 arch kernel: ---[ end trace 143683935de8f41f ]--- > > Nov 5 17:31:35 arch kernel: Freeing alive in_device ffff88011ffba600 > > > > Hmm.... > > Is commit 1f1b9c9990205759aae31b7734b0ede41a867f32 present in your > kernel ? (fib: fib_result_assign() should not change fib refcounts)
Yes, the last warning happend today on the lastest git kernel (from today). > > Could you provide some information ? > > ifconfig -a
dummy0 Link encap:Ethernet HWaddr 76:FE:79:D4:80:DF BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 00:08:54:36:F2:2F inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:1945 errors:0 dropped:0 overruns:0 frame:0 TX packets:1450 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1910343 (1.8 Mb) TX bytes:177533 (173.3 Kb) Interrupt:20 Base address:0x6c00
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:18321 errors:0 dropped:0 overruns:0 frame:0 TX packets:18321 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2200368 (2.0 Mb) TX bytes:2200368 (2.0 Mb)
> ip ro
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 default via 192.168.1.1 dev eth0
-- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |