Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Ingo Molnar
* Jesse Brandeburg <[EMAIL PROTECTED]> wrote: > 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

Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Kok, Auke
Jesse Brandeburg wrote: On 3/26/07, Ingo Molnar <[EMAIL PROTECTED]> 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

Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Jesse Brandeburg
On 3/26/07, Ingo Molnar <[EMAIL PROTECTED]> 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

Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Kok, Auke
Ingo Molnar 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 > TDT

-rc5: e1000 resume weirdness

2007-03-26 Thread Ingo Molnar
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 TDT next_to_use

-rc5: e1000 resume weirdness

2007-03-26 Thread Ingo Molnar
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

Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Kok, Auke
Ingo Molnar 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

Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Jesse Brandeburg
On 3/26/07, Ingo Molnar [EMAIL PROTECTED] 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

Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Kok, Auke
Jesse Brandeburg wrote: On 3/26/07, Ingo Molnar [EMAIL PROTECTED] 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

Re: -rc5: e1000 resume weirdness

2007-03-26 Thread Ingo Molnar
* Jesse Brandeburg [EMAIL PROTECTED] wrote: 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