Re: tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
On 10/25/06, Michael Chan [EMAIL PROTECTED] wrote: ... Can you cat /proc/interrupts a few times to see if the interrupt counts on eth1 and eth2 are increasing? # grep eth /proc/interrupts 9: 0 0 0 0IO-APIC-edge eth2 16: 177724 0 371238 19350 IO-APIC-level libata, eth0, eth1 # ifconfig eth1;ifconfig eth2 eth1 Link encap:Ethernet HWaddr 00:16:E6:80:B1:3E inet addr:128.1.9.0 Bcast:128.1.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15276 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1389350 (1.3 Mb) TX bytes:1920 (1.8 Kb) Interrupt:16 eth2 Link encap:Ethernet HWaddr 00:16:E6:80:B1:3F UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:9 You can also run ethtool -t [eth1 | eth2] to run a basic selftest on the 2 devices. Be sure to ifconfig up first before the selftest. # ethtool -t eth1 The test result is PASS The test extra info: nvram test (online) 0 link test (online) 0 register test (offline) 0 memory test(offline) 0 loopback test (offline) 0 interrupt test (offline) 0 # ethtool -t eth2 The test result is FAIL The test extra info: nvram test (online) 0 link test (online) 1 register test (offline) 0 memory test(offline) 0 loopback test (offline) 0 interrupt test (offline) 1 - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
On 10/25/06, David Miller [EMAIL PROTECTED] wrote: It's an interrupt routing problem for sure, Adrian Bunk posted a potential fix to this poster an hour or so ago. I'm running with arch=i386 and the only related postings I see are for x86_64 :-(. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
On Wed, 2006-10-25 at 09:02 -0400, Richard Bollinger wrote: # ethtool -t eth2 The test result is FAIL The test extra info: nvram test (online) 0 link test (online) 1 register test (offline) 0 memory test(offline) 0 loopback test (offline) 0 interrupt test (offline) 1 This confirms that it's some kind of interrupt problem as David had suggested, at least on eth2. You can try booting with noapic to see if it works if you haven't got the patch from Adrian Bunk yet. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
On 10/25/06, Michael Chan [EMAIL PROTECTED] wrote: This confirms that it's some kind of interrupt problem as David had suggested, at least on eth2. You can try booting with noapic to see if it works if you haven't got the patch from Adrian Bunk yet. No joy. Here's the dmesg after boot w/ noapic, modprobe tg3 and ifconfig eth1 up ifconfig eth2 up: tg3.c:v3.65 (August 07, 2006) PCI: Found IRQ 11 for device :08:00.0 PCI: Sharing IRQ 11 with :00:00.0 PCI: Sharing IRQ 11 with :00:02.0 PCI: Sharing IRQ 11 with :00:03.0 PCI: Sharing IRQ 11 with :00:1c.1 PCI: Sharing IRQ 11 with :01:00.0 PCI: Sharing IRQ 11 with :02:00.0 PCI: Sharing IRQ 11 with :03:00.0 PCI: Sharing IRQ 11 with :05:01.0 PCI: Sharing IRQ 11 with :0b:01.0 PCI: Setting latency timer of device :08:00.0 to 64 eth1: Tigon3 [partno(BCM95789) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:16:e6:80:b1:3e eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth1: dma_rwctrl[7618] dma_mask[64-bit] PCI: Setting latency timer of device :09:00.0 to 64 eth2: Tigon3 [partno(BCM95789) rev 4101 PHY(5750)] (PCI Express) 10/100/1000BaseT Ethernet 00:16:e6:80:b1:3f eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth2: dma_rwctrl[7618] dma_mask[64-bit] tg3: eth1: Link is up at 1000 Mbps, full duplex. tg3: eth1: Flow control is on for TX and on for RX. tg3: eth2: Link is up at 1000 Mbps, full duplex. tg3: eth2: Flow control is on for TX and on for RX. irq 9: nobody cared (try booting with the irqpoll option) [c013d41a] __report_bad_irq+0x2a/0x8f [c013d50f] note_interrupt+0x76/0xef [c013cbc3] __do_IRQ+0xf0/0xfd [c0105515] do_IRQ+0x31/0x69 [c010387e] common_interrupt+0x1a/0x20 [c0120e11] __do_softirq+0x63/0xeb [c0120ed3] do_softirq+0x3a/0x3c [c010551a] do_IRQ+0x36/0x69 [c010387e] common_interrupt+0x1a/0x20 [c0124e5b] del_timer_sync+0x1/0x1d [c0381998] schedule_timeout+0x60/0xaa [c01260eb] process_timeout+0x0/0x9 [c01735ac] do_select+0x1cc/0x349 [c0173292] __pollwait+0x0/0x69 [c011644e] default_wake_function+0x0/0x12 [c011644e] default_wake_function+0x0/0x12 [c011644e] default_wake_function+0x0/0x12 [c011644e] default_wake_function+0x0/0x12 [c011644e] default_wake_function+0x0/0x12 [c011644e] default_wake_function+0x0/0x12 [c035609e] fn_hash_lookup+0xb3/0xbc [c035609e] fn_hash_lookup+0xb3/0xbc [c021e8a0] copy_to_user+0x42/0x5c [c02efdf2] memcpy_toiovec+0x4a/0x5f [c02f03e7] skb_copy_datagram_iovec+0x50/0x20c [c02f02f6] skb_recv_datagram+0xbb/0xce [c02ed49c] kfree_skbmem+0x61/0x86 [c0349ced] udp_recvmsg+0x1ca/0x251 [c02ec6dc] sock_common_recvmsg+0x57/0x72 [c02e870d] sock_recvmsg+0x104/0x11e [c021e908] copy_from_user+0x4e/0x82 [c0173962] core_sys_select+0x239/0x3b1 [c01303e4] autoremove_wake_function+0x0/0x57 [c021e8a0] copy_to_user+0x42/0x5c [c02e7fb9] move_addr_to_user+0x5c/0x67 [c02e9d1d] sys_recvfrom+0x120/0x162 [f8a979d8] tg3_rx+0x13d/0x3f3 [tg3] [f8a9371e] tg3_restart_ints+0x23/0x87 [tg3] [c0173b7e] sys_select+0xa4/0x1be [c0128b8d] sys_rt_sigprocmask+0x82/0x10c [c0102ef7] syscall_call+0x7/0xb handlers: [f8a98093] (tg3_interrupt_tagged+0x0/0xc2 [tg3]) Disabling IRQ #9 tg3: eth1: Link is down. tg3: eth1: Link is up at 1000 Mbps, full duplex. tg3: eth1: Flow control is on for TX and on for RX. tg3: eth2: Link is down. tg3: eth2: Link is up at 1000 Mbps, full duplex. tg3: eth2: Flow control is on for TX and on for RX. irq 9: nobody cared (try booting with the irqpoll option) [c013d41a] __report_bad_irq+0x2a/0x8f [c013d50f] note_interrupt+0x76/0xef [c013cbc3] __do_IRQ+0xf0/0xfd [c0105515] do_IRQ+0x31/0x69 [c010e522] smp_apic_timer_interrupt+0x69/0x75 [c010387e] common_interrupt+0x1a/0x20 [c012007b] sys_setitimer+0xaa/0xb7 [c013ca92] handle_IRQ_event+0x1e/0x5f [c0107730] mask_and_ack_8259A+0x1d/0xde [c013cb61] __do_IRQ+0x8e/0xfd [c0105515] do_IRQ+0x31/0x69 [c010e522] smp_apic_timer_interrupt+0x69/0x75 [c010387e] common_interrupt+0x1a/0x20 [c0120e11] __do_softirq+0x63/0xeb [c0120ed3] do_softirq+0x3a/0x3c [c010551a] do_IRQ+0x36/0x69 [c010387e] common_interrupt+0x1a/0x20 [c0380ee3] schedule+0x3f7/0x741 [c03819e0] schedule_timeout+0xa8/0xaa [c0120e87] __do_softirq+0xd9/0xeb [c0130322] prepare_to_wait_exclusive+0x20/0x68 [c02f01f9] wait_for_packet+0xf5/0x137 [c01303e4] autoremove_wake_function+0x0/0x57 [c01303e4] autoremove_wake_function+0x0/0x57 [c02f02d0] skb_recv_datagram+0x95/0xce [c036dcdf] packet_recvmsg+0x6b/0x1b3 [c02e870d] sock_recvmsg+0x104/0x11e [f8a97d95] tg3_poll+0x107/0x1b6 [tg3] [c0121124] tasklet_action+0x76/0xcc [c01303e4] autoremove_wake_function+0x0/0x57 [c021e8a0] copy_to_user+0x42/0x5c [c02e7fb9] move_addr_to_user+0x5c/0x67 [c02e9ce1] sys_recvfrom+0xe4/0x162 [c014e48a] do_no_page+0x1eb/0x31a [c021e8a0] copy_to_user+0x42/0x5c [c02ec5f8] sock_get_timestamp+0x4a/0x7d [c02e8dee] sock_ioctl+0xb8/0x1b6 [c02ea59a] sys_socketcall+0x1bc/0x256 [c0102ef7] syscall_call+0x7/0xb handlers: [f8a98093] (tg3_interrupt_tagged+0x0/0xc2 [tg3])
tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
GigaByte GA-7VCSV-RH motherboard w/two dual core Xeon's, 4gb RAM, Intel 5000v Chipset, dual Broadcom 5789 Gigabit Ethernet Controllers, connected to Dell GigE switch. Both interfaces work fine with vendor's drivers on Windows 2003, but using Linux 2.6.18.1 tg3 or vendor's Linux driver, the first interface only works for a few packets, then stops receiving, while the second interface doesn't work at all - even to the point of recognizing the link is up or down. Same results with 2.6.17.14 and non-smp kernel. lspci -v output: 00:00.0 Host bridge: Intel Corporation: Unknown device 25d4 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25d8 Flags: bus master, fast devsel, latency 0 Capabilities: [50] Power Management version 2 Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Capabilities: [6c] #10 [0041] 00:02.0 PCI bridge: Intel Corporation: Unknown device 25e2 (rev 92) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=05, sec-latency=0 I/O behind bridge: 2000-3fff Memory behind bridge: de00-de3f Prefetchable memory behind bridge: d100-d110 Capabilities: [50] Power Management version 2 Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Capabilities: [6c] #10 [0041] 00:03.0 PCI bridge: Intel Corporation: Unknown device 25e3 (rev 92) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=06, subordinate=06, sec-latency=0 Capabilities: [50] Power Management version 2 Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Capabilities: [6c] #10 [0041] 00:10.0 Host bridge: Intel Corporation: Unknown device 25f0 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25f0 Flags: fast devsel 00:10.1 Host bridge: Intel Corporation: Unknown device 25f0 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25f0 Flags: fast devsel 00:10.2 Host bridge: Intel Corporation: Unknown device 25f0 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25f0 Flags: fast devsel 00:11.0 Host bridge: Intel Corporation: Unknown device 25f1 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25f1 Flags: fast devsel 00:13.0 Host bridge: Intel Corporation: Unknown device 25f3 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25f3 Flags: fast devsel 00:15.0 Host bridge: Intel Corporation: Unknown device 25f5 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25f5 Flags: fast devsel 00:16.0 Host bridge: Intel Corporation: Unknown device 25f6 (rev 92) Subsystem: Giga-byte Technology: Unknown device 25f6 Flags: fast devsel 00:1c.0 PCI bridge: Intel Corporation: Unknown device 2690 (rev 09) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=07, subordinate=07, sec-latency=0 Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 00:1c.1 PCI bridge: Intel Corporation: Unknown device 2692 (rev 09) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=08, subordinate=08, sec-latency=0 Memory behind bridge: de50-de5f Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 00:1c.2 PCI bridge: Intel Corporation: Unknown device 2694 (rev 09) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=09, subordinate=09, sec-latency=0 Memory behind bridge: de60-de6f Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 00:1c.3 PCI bridge: Intel Corporation: Unknown device 2696 (rev 09) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0 Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable- Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 00:1e.0 PCI bridge: Intel Corporation: Unknown device 244e (rev d9) (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=32 I/O behind bridge: 4000-4fff Memory behind bridge: de40-de4f Prefetchable memory behind bridge: dc00-ddf0 Capabilities: [50] #0d [] 00:1f.0 ISA bridge: Intel Corporation: Unknown device 2670 (rev 09) Subsystem: Giga-byte Technology: Unknown device 2670 Flags: bus master, medium devsel, latency 0 00:1f.1 IDE interface: Intel Corporation: Unknown device 269e (rev 09) (prog-if 8a [Master SecP PriP]) Subsystem: Giga-byte Technology: Unknown device
Re: tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
Richard Bollinger wrote: GigaByte GA-7VCSV-RH motherboard w/two dual core Xeon's, 4gb RAM, Intel 5000v Chipset, dual Broadcom 5789 Gigabit Ethernet Controllers, connected to Dell GigE switch. Both interfaces work fine with vendor's drivers on Windows 2003, but using Linux 2.6.18.1 tg3 or vendor's Linux driver, the first interface only works for a few packets, then stops receiving, while the second interface doesn't work at all - even to the point of recognizing the link is up or down. Same results with 2.6.17.14 and non-smp kernel. Can you cat /proc/interrupts a few times to see if the interrupt counts on eth1 and eth2 are increasing? You can also run ethtool -t [eth1 | eth2] to run a basic selftest on the 2 devices. Be sure to ifconfig up first before the selftest. Thanks. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: tg3 driver fails with on-board BCM95789 NICS (GigaByte GA-7VCSV)
From: Michael Chan [EMAIL PROTECTED] Date: Tue, 24 Oct 2006 21:31:56 -0700 Can you cat /proc/interrupts a few times to see if the interrupt counts on eth1 and eth2 are increasing? You can also run ethtool -t [eth1 | eth2] to run a basic selftest on the 2 devices. Be sure to ifconfig up first before the selftest. It's an interrupt routing problem for sure, Adrian Bunk posted a potential fix to this poster an hour or so ago. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
