On Sun, May 26, 2013 at 11:46:34AM -0500, Shawn Bohrer wrote: > I guess I have two questions: > > 1) Do these need to be mdelays instead of msleeps? It looks like in > my case this is called from process context, but I didn't audit all of > the callers of this function and maybe it can happen from interrupt > context too? > > 2) Any idea why I'm hitting this in the first place?
Well, as is probably expected doing a cold boot of the system fixed the issue (a warm reboot did not), so I'm guessing the hardware was simply in a bad state. It seems a bit excessive to me that this code can spin in the kernel for up to a second, and it appears on my system it was doing this every two seconds. -- Shawn ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ 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
