From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.21-pre5-ac1: Broadcom gigabit ethernet quirk introduced
Date: Wed, 05 Mar 2003 09:37:09 -0800 [thread overview]
Message-ID: <3E6635C5.4080006@myrealbox.com> (raw)
Hi Alan,
I have an ASUS A7VX8 motherboard with built-in Broadcom gigabit
ethernet chip which has been working perfectly right up through
-pre4-ac7 and now has developed a strange problem starting with
-pre5-ac1.
After rebooting the machine the Broadcom chip appears to be
configured normally, i.e. 'ifconfig eth0' looks perfectly
normal, and the routing table is the same as always.
The problem is that the chip simply doesn't transmit any packets
until I manually do 'ifconfig eth0 down' and 'ifconfig eth0 up'
at which point the chip starts working normally.
The output of 'ifconfig eth0' is identical before and after this
down/up cycle. The internal state of the chip is clearly changed
by this manoeuver, however.
Can you think of any change between -pre4-ac7 and -pre5-ac1 which
might have affected the way the Broadcom chip is initialized?
next reply other threads:[~2003-03-05 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 17:37 walt [this message]
2003-03-05 18:08 ` 2.4.21-pre5-ac1: Broadcom gigabit ethernet quirk introduced Jeff Garzik
[not found] <fa.fl0gpjr.t3u29h@ifi.uio.no>
[not found] ` <fa.f079mas.1qlo10a@ifi.uio.no>
2003-03-05 19:10 ` walt
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=3E6635C5.4080006@myrealbox.com \
--to=wa1ter@myrealbox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox