From: Jeff Garzik <jgarzik@pobox.com>
To: Scott Ashcroft <ashcroft@qzxyz.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tg3/Broadcom gigabit driver just got worse in 2.4.23-pre3
Date: Thu, 04 Sep 2003 08:51:14 -0400 [thread overview]
Message-ID: <3F573542.5010509@pobox.com> (raw)
In-Reply-To: <3F56E8F5.6020702@qzxyz.com>
Scott Ashcroft wrote:
> walt wrote:
>
>> Hi Jeff et all,
>>
>> I just tried 2.4.23-pre3 with results that are disastrous, for me at
>> least.
>>
>> As you will remember, I'm the one who has to do an ifconfig down/up cycle
>> on my asus A7V8X mobo with built-in Broadcom chip. But after the updates
>> in -pre3 the chip no longer will work at all.
>>
>> In fact, if I try 'ifconfig eth0 down' the command hangs forever and
>> chews
>> up 99.9% of the CPU. No packets are ever transmitted in spite of a
>> normal
>> 'ifconfig' output after bootup. The chip is correctly identified in
>> dmesg:
>>
>> eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit)
>> 10/100/1000BaseT Ethernet 00:e0:18:d2:a6:c1
>
>
> Same here but it's a 5705M in a laptop. Tried backing out just the
> changes to the tg3 driver but couldn't get it to build correctly.
Does 2.4.23-pre2 work for you?
Jeff
next prev parent reply other threads:[~2003-09-04 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 1:52 tg3/Broadcom gigabit driver just got worse in 2.4.23-pre3 walt
2003-09-04 7:25 ` Scott Ashcroft
2003-09-04 12:51 ` Jeff Garzik [this message]
2003-09-04 13:46 ` Scott Ashcroft
2003-09-04 12:50 ` Jeff Garzik
2003-09-04 14:03 ` walt
2003-09-04 16:09 ` Jeff Garzik
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=3F573542.5010509@pobox.com \
--to=jgarzik@pobox.com \
--cc=ashcroft@qzxyz.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