* 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 causes this debug print when we are
> suspending. I'll work with auke to generate a short patch.
there was no "NETDEV WATCHDOG" message. But still there was a ~30
seconds delay until i got the first few packets through the interface -
while normally it's available almost instantly after resume. But ...
this condition seems sporadic, i havent seen it on subsequent
suspend+resume attempts.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
