Brandeburg, Jesse <[EMAIL PROTECTED]> wrote:
>Kok, Auke-jan H wrote:
>> Auke Kok wrote:
>>> Jay Vosburgh wrote:
>>>> Running both 2.6.17.6 plus the e1000 7.2.7 from sourceforge, or
>>>> the e1000 in netdev-2.6#upstream (7.1.9-k4).
>>>>
>>>> Starting up "ethtool -p ethX" then unplugging the cable
>>>> connected to the identified port is causing my system to completely
>>>> freeze; even sysrq is unresponsive. I'm running on a 2-way x86
>>>> box, with an 82545GM.
[...]
>Has something to do with the RTNL lock being held and link notification,
>as I remember.
>We noticed it to be a global problem, happens with e100 too.
>
>http://www.mail-archive.com/netdev@vger.kernel.org/msg01654.html
Well, I thought maybe I'd messed it up when I tested the other
cards, but I just went and tried it again. Only the e1000 wedges the
system if I pull the cable with ethtool -p running. The e100 and tg3
don't lock up. Pulling the cable ends the ethtool for tg3, but for e100
the blinky blinky keeps going even after the cable is back in.
Even so, as you mention, the operation is holding the RTNL, so
anything else that wants it has to wait.
-J
---
-Jay Vosburgh, IBM Linux Technology Center, [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
