From: walt <wa1ter@myrealbox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Broadcom gigabit ethernet question for Jeff?
Date: Tue, 19 Aug 2003 13:53:48 -0700 [thread overview]
Message-ID: <3F428E5C.80801@myrealbox.com> (raw)
Hi, it's me again. Sorry to be back, but 2.6 is looming and I still have the
same old problem with my Asus A7V8X with builtin Broadcom chip.
If you'll recall I must do an ifconfig down/up cycle to get the chip to transmit
any packets. Once I do that the chip works fine until the next reboot. See lkml
archives for March 5.
This problem first appeared in 2.4.21-rc5. Before that the chip worked fine for me.
All I can offer is below. I'll be happy to do any debugging you wish, but I will
need explicit help. I'm no expert at kernel debugging.
00:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702 Gigabit Ethernet (rev 02)
Subsystem: Asustek Computer, Inc.: Unknown device 80a9
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 10
Memory at f1800000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at f7ff0000 [disabled] [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:e0:18:d2:a6:c1
If there is some way of dumping the 'state' of the chip before and after doing the
ifconfig down/up it might be a valuable clue. I just don't know how to do it.
next reply other threads:[~2003-08-19 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 20:53 walt [this message]
2003-08-19 21:29 ` Broadcom gigabit ethernet question for Jeff? Jeff Garzik
2003-08-19 23:19 ` Broadcom gigabit ethernet question for Jeff? (correction!) 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=3F428E5C.80801@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 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.