Re: [E1000-devel] e1000: ethtool -p + cable pull = system wedges hard
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
RE: [E1000-devel] e1000: ethtool -p + cable pull = system wedges hard
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. >>> >>> Is this by any chance a known problem? >> >> not at all. > > One of my brain halves (the third one ;)) poked me and told me that > it *is* a known issue. Not good. Apparently as early as kernel 2.5.50 > a change was introduced that causes this. I am unsure what exactly > caused it and I assume it is generic (other nic's might also suffer). > The issue is documented in our standalone driver documentation. Not > sure what to do with this. 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 Jesse - 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
Re: [E1000-devel] e1000: ethtool -p + cable pull = system wedges hard
Auke Kok <[EMAIL PROTECTED]> 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. >>> >>> Is this by any chance a known problem? >> not at all. > >One of my brain halves (the third one ;)) poked me and told me that it >*is* a known issue. Not good. Apparently as early as kernel 2.5.50 a >change was introduced that causes this. I am unsure what exactly caused it >and I assume it is generic (other nic's might also suffer). The issue is >documented in our standalone driver documentation. Not sure what to do >with this. It appears to not be generic. The same recipe on tg3 and e100 devices does not mete out the same frontier justice as e1000. I made no changes to the system (same one described above), tried it against 2.6.17.6 with whatever versions of tg3 and e100 it comes with. -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
Re: [E1000-devel] e1000: ethtool -p + cable pull = system wedges hard
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. Is this by any chance a known problem? not at all. One of my brain halves (the third one ;)) poked me and told me that it *is* a known issue. Not good. Apparently as early as kernel 2.5.50 a change was introduced that causes this. I am unsure what exactly caused it and I assume it is generic (other nic's might also suffer). The issue is documented in our standalone driver documentation. Not sure what to do with this. Auke - 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
