On May 11, 2007, at 01:49:27, Kyle Moffett wrote:
On May 10, 2007, at 00:34:11, Kyle Moffett wrote:
On May 10, 2007, at 00:25:54, Ben Greear wrote:
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
On May 10, 2007, at 00:34:11, Kyle Moffett wrote:
On May 10, 2007, at 00:25:54, Ben Greear wrote:
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
On May 10, 2007, at 00:25:54, Ben Greear wrote:
Kyle Moffett wrote:
vconfig D 83CCD8CE 0 16564 16562
(NOTLB)
efdd7e7c 0086 ee120afb 83ccd8ce 98f00788 b7083ffa
5384b49a c76c0b05
9ebaf791 0004 efdd7e4e 0007 f1468a90 2ab74174
0362 00
Kyle Moffett wrote:
vconfig D 83CCD8CE 0 16564 16562 (NOTLB)
efdd7e7c 0086 ee120afb 83ccd8ce 98f00788 b7083ffa 5384b49a
c76c0b05
9ebaf791 0004 efdd7e4e 0007 f1468a90 2ab74174 0362
0326
f1468b9c c180e420 0001 0286 c
I've managed to fairly reliably trigger a deadlock in some portion of
the linux networking code on my Debian test box (using the debian
kernel linux-image-2.6.20-1-686). I'm pretty sure that it's a race
condition of some sort as it doesn't trigger if I ifdown the
interfaces one by one, but
