![]() | |||||||||||
Messages in this thread
|
On 3/26/07, Ingo Molnar <mingo@elte.hu> wrote: >> hm, on a T60, after suspend/resume, i get an e1000 timeout: >> e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX > e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang > Tx Queue <0> > TDH <ec> > TDT <ec> > next_to_use <ec> > next_to_clean <82> > buffer_info[next_to_clean] > time_stamp <fffcc3db> > next_to_watch <82> > jiffies <fffd5da0> > next_to_watch.status <1> > > it works fine after that reset. The e1000 driver didnt do this before > after resume the network was always available immediately. So this > appears to be a relatively new regression (post-rc3 or so). high-res > timers was disabled. was there a "NETDEV WATCHDOG" message that follows this? If not it is a harmless debug print. Note the time_stamp and jiffies difference, very large, consistent with a resume. I think we need to disable the internal e1000 tx hang code that causes this debug print when we are suspending. I'll work with auke to generate a short patch. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2007-03-26 17:53 [from the cache] ©2003-2008 | |||||||||||