From: Roger Luethi <rl@hellgate.ch>
To: Jindrich Makovicka <makovick@kmlinux.fjfi.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: via-rhine broken in 2.4.22-pre8 and 2.6.0-pre1&2
Date: Mon, 28 Jul 2003 20:32:21 +0200 [thread overview]
Message-ID: <20030728183220.GB30246@k3.hellgate.ch> (raw)
In-Reply-To: <3F2515A2.8040008@kmlinux.fjfi.cvut.cz>
On Mon, 28 Jul 2003 14:22:58 +0200, Jindrich Makovicka wrote:
> I recently tried 2.6.0-test1, 2.6.0-test2, 2.4.22-pre6 and 2.4.22-pre8,
> and via-rhine seems broken in all of them. Network connection doesn't
> work, and only the timeout messages appear:
Does that mean no traffic at all? No ping, no nothing?
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
> eth0: Setting full-duplex based on MII #1 link partner capability of 41e1.
>
> 2.4.21 still works fine.
Same .config? Is APIC and/or ACPI enabled? Are you running half-duplex?
What other modules do you loaded?
Roger
next prev parent reply other threads:[~2003-07-28 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 12:22 via-rhine broken in 2.4.22-pre8 and 2.6.0-pre1&2 Jindrich Makovicka
2003-07-28 18:32 ` Roger Luethi [this message]
2003-07-29 7:57 ` Claas Langbehn
2003-07-29 9:51 ` Stefan Voelkel
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=20030728183220.GB30246@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=makovick@kmlinux.fjfi.cvut.cz \
/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