Re: deadlock in 2.6.18.2 related to bridging?

2007-02-14 Thread Stephen Hemminger
On Tue, 13 Feb 2007 17:23:05 -0800 Ben Greear [EMAIL PROTECTED] wrote: I think I may have found a deadlock bug in 2.6.18.2. This is with my hacked kernel, but my binary module has not been loaded. I have several bridges configured, including some containing my redirect-device virtual

Re: deadlock in 2.6.18.2 related to bridging?

2007-02-14 Thread Ben Greear
Stephen Hemminger wrote: The bug is in r8139too.c driver. It calls flush_scheduled_work with RTNL mutex held, so any other work using it will get stuck. It looks like a fairly common problem, as tg3 has the same issue (though it seems someone tried to hack around one particular case): static

Re: deadlock in 2.6.18.2 related to bridging?

2007-02-14 Thread Francois Romieu
Ben Greear [EMAIL PROTECTED] : [...] e1000 appears clean, at least, but there are a lot of other drivers that are calling that method (I didn't check to see if they might be holding rtnl when called.) Not that lot: only r8169, sis190, s2io and cassini (through change_mtu). Bad week. --

deadlock in 2.6.18.2 related to bridging?

2007-02-13 Thread Ben Greear
I think I may have found a deadlock bug in 2.6.18.2. This is with my hacked kernel, but my binary module has not been loaded. I have several bridges configured, including some containing my redirect-device virtual devices and ethernet devices. I believe the deadlock is this: The work-queue