On 06/23/2011 12:16 PM, Brandeburg, Jesse wrote: > > > On Wed, 22 Jun 2011, Ben Greear wrote: > >> This is hacked and tainted 2.6.38.8 kernel, but no modifications to the >> e1000e driver. >> >> Didn't seem to cause any troubles. > > How about info on a test to help reproduce the issue? RESETTING is set > either by the tx_timeout task or by the ethtool calls. > > could it be your code is somehow related to those? > > I'm wondering if the WARN_ON needs to be after the cancel_work_sync and > cancel_timers?
We think it was during our program's startup, which will effectively ifdown/ifup the interface several times. We were not resetting via ethtool API as far as I know, though our tool does have that option, so it's possible something weird triggered that action. There were no logs about tx timeouts in this area, and we're running a patch to print it out each time a timeout happens, not just once like in the main kernel. Don't recall seeing this WARN_ON recently, and we restart our program and bounce interfaces all the time, so I'm not sure how reproducible this would be. I'll let you know if we find any way to reproduce it reliably. Thanks, Ben -- Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Data protection magic? Nope - It's vRanger. Get your free trial download today. http://p.sf.net/sfu/quest-sfdev2dev _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
