Re: tg3: strange errors and non-working-ness

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 [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Follow-Ups:
- Re: tg3: strange errors and non-working-ness
  - From: "Jon Nelson" <[email protected]>
References:
- Re: tg3: strange errors and non-working-ness
  - From: Jarek Poplawski <[email protected]>
Prev by Date: Re: [PATCH] x86_64: fix a deadlock in set_rtc_mmss()
Next by Date: Re: 2.6.24-rc2-mm1
Previous by thread: Re: tg3: strange errors and non-working-ness
Next by thread: Re: tg3: strange errors and non-working-ness
Index(es):
- Date
- Thread
[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]