Re: PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?"

From: Jon Mason
Date: Wed Dec 22 2004 - 09:56:11 EST

Yes, I need the tx timeout lines. Those tell me if the patch was
successfull in solving the interrupt enablement issue. From your
statement below, it appears that it was either unsucessful (and you
didn't wait long enough for it to timeout) or the root problem lies
somewhere else.

Please give it a good 20 minutes (if you can get away with it being
down for that long) to timeout, as it has been taking 5-10 minutes in
your previous errors. There is no set timeframe for it to timeout.
It will only timeout after netif_stop_queue has true for a minute. if
this never happens, then it leads me to believe that the adapter is
still functioning. I know you can't log in to the system because of
the nfs mounts, but can you see if the system is pingable before you
reboot it?


On Wed, 22 Dec 2004 10:29:55 +0100, Richard Ems
<richard.ems@xxxxxxxxxxxxxxxxxxxx> wrote:
> Jon, thanks for the last patch, it applied without errors or warnings.
> But the NIC is still hanging.
> Here the last hang data. Do you need the "Tx timed out" lines? I
> apparently didn't wait long enough for this timeout to trigger ...
> Is it a 5 min timeout?
> Dec 22 10:00:37 urutu kernel: eth0: HostError! IntStatus 0082. 216 59
> 248001a0 7c2
> Dec 22 10:02:24 urutu kernel: nfs: server jupiter not responding, still
> trying
> Dec 22 10:02:55 urutu last message repeated 7 times
> Dec 22 10:03:52 urutu last message repeated 3 times
> Dec 22 10:04:14 urutu kernel: nfs: server jupiter not responding, still
> trying
> Dec 22 10:06:07 urutu syslogd 1.4.1: restart.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at