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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/