Re: [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness

netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* Re: [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness
       [not found] <bug-9391-10286@http.bugzilla.kernel.org/>
@ 2007-11-16  2:18 ` Andrew Morton
  2007-11-16  8:30   ` Jarek Poplawski
  0 siblings, 1 reply; 5+ messages in thread
From: Andrew Morton @ 2007-11-16  2:18 UTC (permalink / raw)
  To: netdev; +Cc: bugme-daemon, mchan

On Thu, 15 Nov 2007 18:04:19 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=9391
> 
>            Summary: Netgear GA320T(tg3) strange errors and non-workingness
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.22.12 (openSUSE 10.3)
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: jgarzik@pobox.com
>         ReportedBy: jnelson-kernel-bugzilla@jamponi.net
> 
> 
> Most recent kernel where this bug did not occur: 2.4.something
> 
> Distribution: openSUSE 10.3
> 
> Hardware Environment: Athlon XP 2200+
> Software Environment: 2.6.22.12
> Problem Description: this bug is being created from a mailing list discussion.
> 
> 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
> 
> 

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness
  2007-11-16  2:18 ` [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness Andrew Morton
@ 2007-11-16  8:30   ` Jarek Poplawski
  2007-11-16 14:08     ` Jon Nelson
  0 siblings, 1 reply; 5+ messages in thread
From: Jarek Poplawski @ 2007-11-16  8:30 UTC (permalink / raw)
  To: Jon Nelson; +Cc: netdev, bugme-daemon, mchan, Andrew Morton

On 16-11-2007 03:18, Andrew Morton wrote:
> On Thu, 15 Nov 2007 18:04:19 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> 
>> http://bugzilla.kernel.org/show_bug.cgi?id=9391
>>
>>            Summary: Netgear GA320T(tg3) strange errors and non-workingness
>>            Product: Drivers
>>            Version: 2.5
>>      KernelVersion: 2.6.22.12 (openSUSE 10.3)
...

I see we have a new thread for this...

Jon, maybe it's only me, but this really looks strange. I don't know
this board, but probably these interrupts shouldn't look like this.
It seems there is a problem with detecting your apic. I'm not sure
if this is a default SUSE kernel, but maybe it would be better to
try some current live-cd distro with good hardware detection. tg3
card & driver seem to have quite good opinions, especially if msi
interrupts could be used.

Btw., these logs (dmesg, lspci) could be much longer... (Somebody
might even think you have something to hide; it would be better to
mask only personal data then.)

Cheers,
Jarek P.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness
  2007-11-16  8:30   ` Jarek Poplawski
@ 2007-11-16 14:08     ` Jon Nelson
  2007-11-16 16:55       ` Michael Chan
  2007-11-16 19:46       ` Jarek Poplawski
  0 siblings, 2 replies; 5+ messages in thread
From: Jon Nelson @ 2007-11-16 14:08 UTC (permalink / raw)
  To: Jarek Poplawski; +Cc: netdev, bugme-daemon, mchan, Andrew Morton

On 11/16/07, Jarek Poplawski <jarkao2@o2.pl> wrote:
> On 16-11-2007 03:18, Andrew Morton wrote:
> > On Thu, 15 Nov 2007 18:04:19 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> >
> >> http://bugzilla.kernel.org/show_bug.cgi?id=9391
> >>
> >>            Summary: Netgear GA320T(tg3) strange errors and non-workingness
> >>            Product: Drivers
> >>            Version: 2.5
> >>      KernelVersion: 2.6.22.12 (openSUSE 10.3)
> ...
>
> I see we have a new thread for this...
>
> Jon, maybe it's only me, but this really looks strange. I don't know
> this board, but probably these interrupts shouldn't look like this.
> It seems there is a problem with detecting your apic. I'm not sure
> if this is a default SUSE kernel, but maybe it would be better to
> try some current live-cd distro with good hardware detection. tg3
> card & driver seem to have quite good opinions, especially if msi
> interrupts could be used.
>
> Btw., these logs (dmesg, lspci) could be much longer... (Somebody
> might even think you have something to hide; it would be better to
> mask only personal data then.)

The lspci is exactly as it was output. The dmesg is shortened only
slightly. The kernel is the latest available for openSUSE 10.3. No MSI
because this is an Athlon XP (read: 32bit, single core, regular old
33MHz, 32bit PCI).

The interrupts look *exactly* the same with or without noapic. This
board doesn't have apic as far as I know. It's an ECS K7S5A I think.

Does that help?

-- 
Jon

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness
  2007-11-16 14:08     ` Jon Nelson
@ 2007-11-16 16:55       ` Michael Chan
  2007-11-16 19:46       ` Jarek Poplawski
  1 sibling, 0 replies; 5+ messages in thread
From: Michael Chan @ 2007-11-16 16:55 UTC (permalink / raw)
  To: Jon Nelson, Jarek Poplawski; +Cc: netdev, bugme-daemon, Andrew Morton

Jon Nelson wrote:

> The lspci is exactly as it was output. The dmesg is shortened only
> slightly. The kernel is the latest available for openSUSE 10.3. No MSI
> because this is an Athlon XP (read: 32bit, single core, regular old
> 33MHz, 32bit PCI).
> 

The lspci doesn't look correct to me either.  We don't have AGP
capability on these network cards.  Please provide:

lspci -vvxxx -s0:0:b.0


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness
  2007-11-16 14:08     ` Jon Nelson
  2007-11-16 16:55       ` Michael Chan
@ 2007-11-16 19:46       ` Jarek Poplawski
  1 sibling, 0 replies; 5+ messages in thread
From: Jarek Poplawski @ 2007-11-16 19:46 UTC (permalink / raw)
  To: Jon Nelson; +Cc: netdev, bugme-daemon, mchan, Andrew Morton

Jon Nelson wrote, On 11/16/2007 03:08 PM:

...
> The lspci is exactly as it was output. The dmesg is shortened only
> slightly. The kernel is the latest available for openSUSE 10.3. No MSI
> because this is an Athlon XP (read: 32bit, single core, regular old
> 33MHz, 32bit PCI).
> 
> The interrupts look *exactly* the same with or without noapic. This
> board doesn't have apic as far as I know. It's an ECS K7S5A I think.
> 
> Does that help?


Yes. You might be right with these interrupts. But, dmesg doesn't
really show enough. Try to paste this all, at least until the first
WATCHDOG time out and card reset.

Thanks,
Jarek P.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-11-16 19:44 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <bug-9391-10286@http.bugzilla.kernel.org/>
2007-11-16  2:18 ` [Bugme-new] [Bug 9391] New: Netgear GA320T(tg3) strange errors and non-workingness Andrew Morton
2007-11-16  8:30   ` Jarek Poplawski
2007-11-16 14:08     ` Jon Nelson
2007-11-16 16:55       ` Michael Chan
2007-11-16 19:46       ` Jarek Poplawski

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).