From: war <war@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Cc: ap@solarrain.com
Subject: Broadcom Gigabit + Linux 2.4.20 - Error with polling.
Date: Sat, 28 Jun 2003 06:44:17 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0306280640290.13092@p500> (raw)
In dmesg, I get this on a board with onboard broadcom gbit ethernet.
The NIC is running at 100mbps.
root@l1:~_26 # uname -a
Linux l1 2.4.20 #6 Thu Jun 12 19:56:43 EDT 2003 i686 unknown unknown
GNU/Linux
root@l1:~_27 #
The description from dmesg:
eth0: Tigon3 [partno(BCM95702A20) rev 1002 PHY(5703)] (PCI:33MHz:32-bit)
10/100/1000BaseT
>From lspci:
00:0f.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702
Gigabit Ethernet (rev 02)
Subsystem: Micro-Star International Co., Ltd.: Unknown device 730b
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 5
Memory at dffb0000 (64-bit, non-prefetchable) [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-
tg3: eth0: Error, poll already scheduled
tg3: eth0: Error, poll already scheduled
tg3: eth0: Error, poll already scheduled
tg3: eth0: Error, poll already scheduled
tg3: eth0: Error, poll already scheduled
tg3: eth0: Error, poll already scheduled
tg3: eth0: Error, poll already scheduled
# dmesg | grep -c tg3
372
I haven't noticed any particular network problems from this message,
however, it certainy is not normal, anyone know what the cause of this
error is?
next reply other threads:[~2003-06-28 10:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 10:44 war [this message]
2003-06-28 22:18 ` Broadcom Gigabit + Linux 2.4.20 - Error with polling David S. Miller
2003-06-28 22:18 ` war
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=Pine.LNX.4.56.0306280640290.13092@p500 \
--to=war@lucidpixels.com \
--cc=ap@solarrain.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;
as well as URLs for NNTP newsgroup(s).