* Re: tg3: strange errors and non-working-ness [not found] <cccedfc60711131057y41630b99h44e1c611f3e92fda@mail.gmail.com> @ 2007-11-15 9:47 ` Jarek Poplawski 2007-11-15 19:23 ` Michael Chan 0 siblings, 1 reply; 7+ messages in thread From: Jarek Poplawski @ 2007-11-15 9:47 UTC (permalink / raw) To: Jon Nelson; +Cc: netdev, linux-kernel On 13-11-2007 19:57, Jon Nelson wrote: > I'm not sure if this is the right place, Me too. Looks more like acpi or pci problem. Did you try to experiment with something like: pci=noacpi or acpi=off boot parameters? Probably some point to your .config and dmesg should be useful too, so taking it to bugzilla and sending a number as a follow up to this thread should be resonable. Btw, I add main kernel to cc. Regards, Jarek P. > but I've got a pair of GiG-E > cards that do not work correctly. Everything appears to come up just > fine, but sooner or later (typically fairly quickly) the cards weird > out and never really come back. > > The best info I've got is this: > > Nov 10 22:21:19 frank kernel: tg3.c:v3.65 (August 07, 2006) > Nov 10 22:21:19 frank kernel: ACPI: PCI Interrupt 0000:00:0b.0[A] -> > Link [LNKB] -> GSI 3 (level, low) -> IRQ 3 > Nov 10 22:21:19 frank kernel: eth0: Tigon3 [partno(AC91002A1) rev 0105 > PHY(5701)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet > 00:09:5b:09:b1:69 > Nov 10 22:21:19 frank kernel: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] > ASF[0] Split[0] WireSpeed[1] TSOcap[0] > Nov 10 22:21:19 frank kernel: eth0: dma_rwctrl[76ff000f] dma_mask[64-bit] > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:21:20 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > Nov 10 22:21:20 frank kernel: tg3: eth0: Flow control is on for TX and > on for RX. > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:21:20 frank kernel: ACPI: PCI interrupt for device > 0000:00:0b.0 disabled > Nov 10 22:21:20 frank kernel: PCI: Enabling device 0000:00:0b.0 (0100 -> 0102) > Nov 10 22:21:20 frank kernel: ACPI: PCI Interrupt 0000:00:0b.0[A] -> > Link [LNKB] -> GSI 3 (level, low) -> IRQ 3 > Nov 10 22:21:20 frank kernel: eth0: Tigon3 [partno(AC91002A1) rev 0105 > PHY(5701)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet > 00:09:5b:09:b1:69 > Nov 10 22:21:20 frank kernel: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] > ASF[0] Split[0] WireSpeed[1] TSOcap[0] > Nov 10 22:21:20 frank kernel: eth0: dma_rwctrl[76ff000f] dma_mask[64-bit] > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:21:20 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > Nov 10 22:21:20 frank kernel: tg3: eth0: Flow control is on for TX and > on for RX. > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:21:20 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > Nov 10 22:21:20 frank kernel: tg3: eth0: Flow control is on for TX and > on for RX. > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:43:02 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:45:52 frank kernel: NETDEV WATCHDOG: eth0: transmit timed out > Nov 10 22:45:52 frank kernel: tg3: eth0: transmit timed out, resetting > Nov 10 22:45:52 frank kernel: tg3: tg3_stop_block timed out, ofs=1400 > enable_bit=2 > Nov 10 22:45:52 frank kernel: tg3: tg3_stop_block timed out, ofs=c00 > enable_bit=2 > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > Nov 10 22:45:52 frank kernel: tg3: eth0: Link is down. > Nov 10 22:45:56 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > Nov 10 22:45:56 frank kernel: tg3: eth0: Flow control is on for TX and > on for RX. > Nov 10 22:47:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:47:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:47:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > Nov 10 22:49:02 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Other gig-e cards work OK in this box. > I have a *pair* of the TG3 boards and they both do the same thing. > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tg3: strange errors and non-working-ness 2007-11-15 9:47 ` tg3: strange errors and non-working-ness Jarek Poplawski @ 2007-11-15 19:23 ` Michael Chan 2007-11-15 19:17 ` Jon Nelson 0 siblings, 1 reply; 7+ messages in thread From: Michael Chan @ 2007-11-15 19:23 UTC (permalink / raw) To: Jarek Poplawski; +Cc: Jon Nelson, netdev, linux-kernel On Thu, 2007-11-15 at 10:47 +0100, Jarek Poplawski wrote: > On 13-11-2007 19:57, Jon Nelson wrote: > > The best info I've got is this: It looks like the card is being reset periodically. Every time the card gets reset, you'll see those PM messages in the version of the driver you're using. Do you see NETDEV WATCHDOG message as well in the dmesg log? > > > > Nov 10 22:21:19 frank kernel: tg3.c:v3.65 (August 07, 2006) > > Nov 10 22:21:19 frank kernel: ACPI: PCI Interrupt 0000:00:0b.0[A] -> > > Link [LNKB] -> GSI 3 (level, low) -> IRQ 3 > > Nov 10 22:21:19 frank kernel: eth0: Tigon3 [partno(AC91002A1) rev 0105 > > PHY(5701)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet > > 00:09:5b:09:b1:69 > > Nov 10 22:21:19 frank kernel: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] > > ASF[0] Split[0] WireSpeed[1] TSOcap[0] > > Nov 10 22:21:19 frank kernel: eth0: dma_rwctrl[76ff000f] dma_mask[64-bit] > > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:21:19 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:21:20 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > > Nov 10 22:21:20 frank kernel: tg3: eth0: Flow control is on for TX and > > on for RX. > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:21:20 frank kernel: ACPI: PCI interrupt for device > > 0000:00:0b.0 disabled > > Nov 10 22:21:20 frank kernel: PCI: Enabling device 0000:00:0b.0 (0100 -> 0102) > > Nov 10 22:21:20 frank kernel: ACPI: PCI Interrupt 0000:00:0b.0[A] -> > > Link [LNKB] -> GSI 3 (level, low) -> IRQ 3 > > Nov 10 22:21:20 frank kernel: eth0: Tigon3 [partno(AC91002A1) rev 0105 > > PHY(5701)] (PCI:33MHz:32-bit) 10/100/1000BaseT Ethernet > > 00:09:5b:09:b1:69 > > Nov 10 22:21:20 frank kernel: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] > > ASF[0] Split[0] WireSpeed[1] TSOcap[0] > > Nov 10 22:21:20 frank kernel: eth0: dma_rwctrl[76ff000f] dma_mask[64-bit] > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:21:20 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > > Nov 10 22:21:20 frank kernel: tg3: eth0: Flow control is on for TX and > > on for RX. > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:21:20 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:21:20 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > > Nov 10 22:21:20 frank kernel: tg3: eth0: Flow control is on for TX and > > on for RX. > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:24:40 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:48 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:41:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:43:02 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:45:52 frank kernel: NETDEV WATCHDOG: eth0: transmit timed out > > Nov 10 22:45:52 frank kernel: tg3: eth0: transmit timed out, resetting > > Nov 10 22:45:52 frank kernel: tg3: tg3_stop_block timed out, ofs=1400 > > enable_bit=2 > > Nov 10 22:45:52 frank kernel: tg3: tg3_stop_block timed out, ofs=c00 > > enable_bit=2 > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset b (was 164514e4, writing 302a1385) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 3 (was 0, writing 4008) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 2 (was 2000000, writing 2000015) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 1 (was 2b00000, writing 2b00106) > > Nov 10 22:45:52 frank kernel: PM: Writing back config space on device > > 0000:00:0b.0 at offset 0 (was 164514e4, writing 3ea173b) > > Nov 10 22:45:52 frank kernel: tg3: eth0: Link is down. > > Nov 10 22:45:56 frank kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex. > > Nov 10 22:45:56 frank kernel: tg3: eth0: Flow control is on for TX and > > on for RX. > > Nov 10 22:47:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:47:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:47:49 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > Nov 10 22:49:02 frank kernel: nfs: server 192.168.2.1 not responding, timed out > > > > Other gig-e cards work OK in this box. > > I have a *pair* of the TG3 boards and they both do the same thing. > > > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tg3: strange errors and non-working-ness 2007-11-15 19:23 ` Michael Chan @ 2007-11-15 19:17 ` Jon Nelson 2007-11-15 20:23 ` Michael Chan 0 siblings, 1 reply; 7+ messages in thread From: Jon Nelson @ 2007-11-15 19:17 UTC (permalink / raw) To: Michael Chan; +Cc: Jarek Poplawski, netdev, linux-kernel On 11/15/07, Michael Chan <mchan@broadcom.com> wrote: > On Thu, 2007-11-15 at 10:47 +0100, Jarek Poplawski wrote: > > On 13-11-2007 19:57, Jon Nelson wrote: > > > The best info I've got is this: > > It looks like the card is being reset periodically. Every time the card > gets reset, you'll see those PM messages in the version of the driver > you're using. Do you see NETDEV WATCHDOG message as well in the dmesg > log? Is this what you mean? I pulled this from the quoted text: Nov 10 22:45:52 frank kernel: NETDEV WATCHDOG: eth0: transmit timed out -- Jon ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tg3: strange errors and non-working-ness 2007-11-15 19:17 ` Jon Nelson @ 2007-11-15 20:23 ` Michael Chan 2007-11-15 20:21 ` Jon Nelson 0 siblings, 1 reply; 7+ messages in thread From: Michael Chan @ 2007-11-15 20:23 UTC (permalink / raw) To: Jon Nelson; +Cc: Jarek Poplawski, netdev, linux-kernel On Thu, 2007-11-15 at 13:17 -0600, Jon Nelson wrote: > Is this what you mean? I pulled this from the quoted text: > > Nov 10 22:45:52 frank kernel: NETDEV WATCHDOG: eth0: transmit timed out > Right. This explains the reset at 22:45:52, but not the earlier reset at 22:24:40. Link never came up after that earlier reset. Is this a new problem introduced by a new driver? I notice you are using tg3 3.65. Have you used newer versions or older versions? ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tg3: strange errors and non-working-ness 2007-11-15 20:23 ` Michael Chan @ 2007-11-15 20:21 ` Jon Nelson 2007-11-15 22:11 ` Jarek Poplawski 0 siblings, 1 reply; 7+ messages in thread From: Jon Nelson @ 2007-11-15 20:21 UTC (permalink / raw) To: Michael Chan; +Cc: Jarek Poplawski, netdev, linux-kernel On 11/15/07, Michael Chan <mchan@broadcom.com> wrote: > On Thu, 2007-11-15 at 13:17 -0600, Jon Nelson wrote: > > > Is this what you mean? I pulled this from the quoted text: > > > > Nov 10 22:45:52 frank kernel: NETDEV WATCHDOG: eth0: transmit timed out > > > > Right. This explains the reset at 22:45:52, but not the earlier reset > at 22:24:40. Link never came up after that earlier reset. > > Is this a new problem introduced by a new driver? I notice you are > using tg3 3.65. Have you used newer versions or older versions? This is not a new problem - these cards have done this or something like it for as long as I've had them*. They work just fine in 100 MBit mode but not in all of my machines, and in none of them at gig-e. I've tried every version of the driver since SUSE 9.1 without much luck (at least as far back as 2.6.9). I'd try a newer driver, esp. if I could make it compile on 2.6.22.12 (I prefer but do not require to stay with the stock distro kernel, modules notwithstanding). NOTE: to avoid list noise, I can make a bug out of this on bugzilla.kernel.org and we can proceed from there if that is preferred. [*] Actually, they worked OK in 2.4.something way-back-when but only for short durations at gig-e speeds. -- Jon ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tg3: strange errors and non-working-ness 2007-11-15 20:21 ` Jon Nelson @ 2007-11-15 22:11 ` Jarek Poplawski 2007-11-16 2:12 ` Jon Nelson 0 siblings, 1 reply; 7+ messages in thread From: Jarek Poplawski @ 2007-11-15 22:11 UTC (permalink / raw) To: Jon Nelson; +Cc: Michael Chan, netdev, linux-kernel Jon Nelson wrote, On 11/15/2007 09:21 PM: ... > NOTE: to avoid list noise, I can make a bug out of this on > bugzilla.kernel.org and we can proceed from there if that is > preferred. Why avoid list noise? These lists are made just for this. But, since this case needs a lot of space for your configs, maybe a lot of time, and maybe a bit more people to have a look at this as well, bugzilla could be very useful. Of course, like Michael said, it would be better if you could do at least short test with a version as new as possible. Regards, Jarek P. PS: I've forgot to mention: lspci -vv, cat /proc/interrupts and maybe the same for these other, working gig-e cards. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tg3: strange errors and non-working-ness 2007-11-15 22:11 ` Jarek Poplawski @ 2007-11-16 2:12 ` Jon Nelson 0 siblings, 0 replies; 7+ messages in thread From: Jon Nelson @ 2007-11-16 2:12 UTC (permalink / raw) To: Jarek Poplawski; +Cc: Michael Chan, netdev, linux-kernel I have created bug 9391 on bugzilla.kernel.org containing pretty much everything. -- Jon ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2007-11-16 2:12 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <cccedfc60711131057y41630b99h44e1c611f3e92fda@mail.gmail.com>
2007-11-15 9:47 ` tg3: strange errors and non-working-ness Jarek Poplawski
2007-11-15 19:23 ` Michael Chan
2007-11-15 19:17 ` Jon Nelson
2007-11-15 20:23 ` Michael Chan
2007-11-15 20:21 ` Jon Nelson
2007-11-15 22:11 ` Jarek Poplawski
2007-11-16 2:12 ` Jon Nelson
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox