From: Richard Ems <richard.ems@mtg-marinetechnik.de>
To: Jon Mason <jdmason@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?"
Date: Wed, 29 Dec 2004 18:53:35 +0100 [thread overview]
Message-ID: <41D2EF1F.2020400@mtg-marinetechnik.de> (raw)
In-Reply-To: <892457750412220654918c785@mail.gmail.com>
Jon Mason wrote:
> Richard,
> 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?
Hi Jon!
No, the system is not pingable from the outside but it still responds to
pings from the inside after the hang happens if i'm logged in.
Here the last hang data. I can't get it to print the "tx timeout" lines.
Two hangs today, I waited 35/40 min and still no "tx timeout". But I got
"Transmit error, TxStatus ..." lines which were not there in the past
hangs. I must admit that I did a SuSE kernel update.
I had 2.6.8-24.5 installed now I have 2.6.8-24.10.
The dl2k driver is the same on both versions, your patch applied
cleanly, the hang is still there.
How can I get "netif_stop_queue to have true for a minute" as you
described to get the "tx timed out" lines? I can login before the hang
and stay logged in to give some commands or get any more data that you
could use to continue searching ...
Thanks, Richard
Dec 29 17:31:08 urutu kernel: eth1: Transmit error, TxStatus 0001,
FrameId 0.
Dec 29 17:32:03 urutu kdm[4064]: XDMCP socket creation failed, errno 97
Dec 29 17:33:07 urutu kernel: eth1: Transmit error, TxStatus 0005,
FrameId 0.
Dec 29 17:35:01 urutu /usr/sbin/cron[12663]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 17:37:02 urutu kdm[4064]: XDMCP socket creation failed, errno 97
Dec 29 17:37:32 urutu last message repeated 2 times
Dec 29 17:37:56 urutu kdm: urutu.mtg-marinetechnik.de:6[13087]:
pam_unix2: session started for user ems2, service xdm
Dec 29 17:38:08 urutu kdm[4064]: XDMCP socket creation failed, errno 97
Dec 29 17:38:09 urutu kdm[4064]: XDMCP socket creation failed, errno 97
Dec 29 17:38:24 urutu kdm: urutu.mtg-marinetechnik.de:7[13254]:
pam_unix2: session started for user ems2, service xdm
Dec 29 17:38:32 urutu kdm[4064]: XDMCP socket creation failed, errno 97
Dec 29 17:38:32 urutu kdm[4064]: XDMCP socket creation failed, errno 97
Dec 29 17:38:53 urutu kdm: urutu.mtg-marinetechnik.de:8[13548]:
pam_unix2: session started for user ems2, service xdm
Dec 29 17:40:01 urutu /usr/sbin/cron[14078]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 17:42:03 urutu kdm[4064]: XDMCP socket creation failed, errno 97
Dec 29 17:42:03 urutu kernel: eth1: Transmit error, TxStatus 0007,
FrameId 0.
Dec 29 17:42:20 urutu kernel: eth1: HostError! IntStatus 0002. 119 107 0 7c2
Dec 29 17:44:06 urutu kernel: nfs: server jupiter not responding, still
trying
Dec 29 17:44:38 urutu last message repeated 3 times
Dec 29 17:44:38 urutu kernel: nfs: server jupiter not responding, still
trying
Dec 29 17:45:01 urutu /usr/sbin/cron[15081]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 17:45:07 urutu kernel: nfs: server jupiter not responding, still
trying
Dec 29 17:50:01 urutu /usr/sbin/cron[15163]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 17:55:01 urutu /usr/sbin/cron[15202]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 17:59:01 urutu /usr/sbin/cron[15211]: (root) CMD ( rm -f
/var/spool/cron/lastrun/cron.hourly)
Dec 29 18:00:01 urutu /usr/sbin/cron[15218]: (root) CMD (
/usr/lib/sa/sa2 -A)
Dec 29 18:00:01 urutu /usr/sbin/cron[15215]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 18:05:01 urutu /usr/sbin/cron[15265]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 18:09:02 urutu login[4286]: FAILED LOGIN 1 FROM /dev/tty3 FOR
root, Authentication failure
Dec 29 18:10:01 urutu /usr/sbin/cron[15325]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 18:15:01 urutu /usr/sbin/cron[15342]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 18:20:01 urutu /usr/sbin/cron[15376]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 18:25:01 urutu /usr/sbin/cron[15393]: (root) CMD (
/root/scripts/reboot-on-network-hang.sh)
Dec 29 18:29:14 urutu syslogd 1.4.1: restart.
--
Richard Ems
Tel: +49 40 65803 312
Fax: +49 40 65803 392
Richard.Ems@mtg-marinetechnik.de
MTG Marinetechnik GmbH - Wandsbeker Königstr. 62 - D 22041 Hamburg
GF Dipl.-Ing. Ullrich Keil
Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66
USt.-IdNr.: DE 1186 70571
next prev parent reply other threads:[~2004-12-29 17:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200412171100.16601.richard.ems@mtg-marinetechnik.de>
2004-12-17 17:07 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" Jon Mason
2004-12-17 17:15 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" (Plain) Richard Ems
2004-12-17 18:05 ` Jon Mason
2004-12-17 20:52 ` Jon Mason
2004-12-20 9:42 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" (Plain) (Plain) Richard Ems
2004-12-20 14:34 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" Richard Ems
2004-12-20 17:12 ` Jon Mason
2004-12-20 18:03 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" (Plain) Richard Ems
2004-12-20 20:31 ` Jon Mason
2004-12-21 9:51 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" Richard Ems
2004-12-21 16:02 ` Jon Mason
2004-12-22 9:29 ` Richard Ems
2004-12-22 14:54 ` Jon Mason
2004-12-22 15:58 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" (Plain) Richard Ems
2004-12-29 17:53 ` Richard Ems [this message]
2005-01-04 21:32 ` PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" Jon Mason
2005-01-04 22:09 ` Francois Romieu
2004-12-17 14:54 Richard Ems
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41D2EF1F.2020400@mtg-marinetechnik.de \
--to=richard.ems@mtg-marinetechnik.de \
--cc=jdmason@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox