From: Jorge Peixoto Vasquez <jorge@aker.com.br>
To: linux-kernel@vger.kernel.org
Subject: via-rhine tx timeouts (AGAIN)
Date: Fri, 21 Jan 2005 18:31:29 -0200 [thread overview]
Message-ID: <41F166A1.4030000@aker.com.br> (raw)
Hi all.
This error seems to appear and re-appear periodically in this list.
This time's encarnation is triggered by a sequence of changing the board
state to up and down.
When this happens, the system can no longer send data through the board
and keeps periodically printing (each other second or so):
NETDEV WATCHDOG: eth0 trasmit timed out
eth0: Trasmit timed out, status 0000, PHY status 786d, reseting ...
eth0: Reset not complete yet. Trying harder.
eth0: Setting full duplex based on MII .... capability of 45e1.
ifconfig up / down again won't recover from the problem.
This box serves as a firewall, so there is traffic all the time during
the sequence described above comming from other interfaces.
This behaviours first showed up when loading the slhc.o PPP driver,
which wasn't used before.
And this machine has neither APIC or ACPI enabled and runs kernel
2.4.26. Switching to kernel 2.4.29 didn't help at all.
Any ideas?
jOrge
--
Jorge Peixoto Vasquez, Elect. Eng.
Aker Security Solutions - www.aker.com.br
reply other threads:[~2005-01-21 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41F166A1.4030000@aker.com.br \
--to=jorge@aker.com.br \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.