From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tg3 and Netgear GA302T x 2 locks machine
Date: Sat, 05 Oct 2002 21:58:01 -0700 [thread overview]
Message-ID: <3D9FC2D9.8010805@candelatech.com> (raw)
In-Reply-To: 20021005.212355.122592301.davem@redhat.com
David S. Miller wrote:
> From: Ben Greear <greearb@candelatech.com>
> Date: Sat, 05 Oct 2002 13:08:02 -0700
>
> With raw ethernet packets, sent from user-space, at around 40Mbps bi-directional,
> I see loads of these messages:
>
> tg3: eth3: Error, poll already scheduled
>
> This, frankly, isn't possible.
>
> When we get the first interrupt, we hold the spinlock and have IRQs
> disabled, in that environment we invoke netif_rx_schedule_prep(dev)
> and then disable device interrupts....
>
> is the tg3 sharing it's IRQ with something else? That might be
> an important clue. In that case what you report might be possible.
Here is what the interrupts look like:
[root@localhost lanforge]# cat /proc/interrupts
CPU0 CPU1
0: 14734 19562 IO-APIC-edge timer
1: 3 1 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
4: 1163 1124 IO-APIC-edge serial
5: 0 0 IO-APIC-level eth1
8: 0 1 IO-APIC-edge rtc
9: 558 0 IO-APIC-level eth2, eth4
10: 0 0 IO-APIC-level usb-ohci
11: 1385 1454 IO-APIC-level eth0, eth3, eth5
12: 20 12 IO-APIC-edge PS/2 Mouse
14: 3958 4169 IO-APIC-edge ide0
15: 7 13 IO-APIC-edge ide1
NMI: 0 0
LOC: 34138 34183
ERR: 0
MIS: 0
[root@localhost lanforge]#
eth0-1 is the 3com built-in nics
eth2-3 is the e1000 dual nic
eth4-5 is the tg3
Oct 5 21:42:10 localhost kernel: tg3.c:v1.1 (Aug 30, 2002)
Oct 5 21:42:11 localhost kernel: eth4: Tigon3 [partno(AC91002A1) rev 0105 PHY(5701)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:40:f4:47:22:fd
Oct 5 21:42:11 localhost kernel: eth5: Tigon3 [partno(AC91002A1) rev 0105 PHY(5701)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet 00:40:f4:47:20:56
Upon starting a user-space TCP connection to myself (no traffic running on eth2-3,
eth1 is not plugged in to a cable. eth0 is handling a small amount of traffic,
no more than about 25 packets per second on average):
[root@localhost lanforge]# tg3: eth5: Error, poll already scheduled
tg3: eth5: Error, poll already scheduled
tg3: eth5: Error, poll already scheduled
tg3: eth5: Error, poll already scheduled
tg3: eth5: Error, poll already scheduled
tg3: eth5: Error, poll already scheduled
tg3: eth5: Error, poll already scheduled
Please let me know what other debugging info I can get you.
> Otherwise the message you see appears to be totally impossible.
I told the machine that...but it only blinked it's little leds in mirth! ;)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-10-06 4:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 4:19 tg3 and Netgear GA302T x 2 locks machine Ben Greear
2002-10-04 5:06 ` Ben Greear
2002-10-04 15:52 ` James Morris
2002-10-05 5:50 ` Ben Greear
2002-10-04 21:24 ` David S. Miller
2002-10-05 1:20 ` James Morris
2002-10-05 1:15 ` David S. Miller
2002-10-05 6:03 ` Ben Greear
2002-10-05 20:08 ` Ben Greear
2002-10-06 4:23 ` David S. Miller
2002-10-06 4:58 ` Ben Greear [this message]
2002-10-05 2:01 ` Matthew N. Andrews
2002-10-05 5:47 ` Ben Greear
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=3D9FC2D9.8010805@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.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.