[lkml]   [2007]   [May]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BUG][debian-2.6.20-1-686] bridging + vlans + "vconfig rem" == stuck kernel
Kyle Moffett wrote:
> vconfig D 83CCD8CE 0 16564 16562 (NOTLB)
> efdd7e7c 00000086 ee120afb 83ccd8ce 98f00788 b7083ffa 5384b49a
> c76c0b05
> 9ebaf791 00000004 efdd7e4e 00000007 f1468a90 2ab74174 00000362
> 00000326
> f1468b9c c180e420 00000001 00000286 c012933c efdd7e8c df98a000
> c180e468
> Call Trace:
> [<c012933c>] lock_timer_base+0x15/0x2f
> [<c0129445>] __mod_timer+0x91/0x9b
> [<c02988f5>] schedule_timeout+0x70/0x8d
> [<f8b75209>] vlan_device_event+0x13/0xf8 [8021q]

Looks like a deadlock in the vlan code. Any chance you can run this
test with
lockdep enabled?

You could also add a printk in vlan_device_event() to check which event
it is hanging on, and
the netdevice that is passed in.

Since the vlan code holds RTNL at this point, then most other network
tasks will eventually
hang as well.


Ben Greear <>
Candela Technologies Inc

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-05-10 06:29    [W:0.041 / U:1.392 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site