From: Bernd Schubert <bernd-schubert@gmx•de>
To: "Michael Chan" <mchan@broadcom•com>
Cc: netdev@vger•kernel.org
Subject: Re: tg3: tg3_stop_block timed out
Date: Tue, 8 Aug 2006 01:24:38 +0200 [thread overview]
Message-ID: <200608080124.38823.bernd-schubert@gmx.de> (raw)
In-Reply-To: <1154992063.5328.3.camel@rh4>
Hi Michael,
thanks for your help!
On Tuesday 08 August 2006 01:07, Michael Chan wrote:
> > ... [many hamilton not responding messages]
> > 4554928.798000] nfs: server hamilton not responding, still trying
> > [4554935.319000] nfs: server hamilton not responding, still trying
> > [4555468.940000] NETDEV WATCHDOG: eth1: transmit timed out
> > [4555468.940000] tg3: eth1: transmit timed out, resetting
> > [4555469.044000] tg3: tg3_stop_block timed out, ofs=3400 enable_bit=2
> > [4555469.147000] tg3: tg3_stop_block timed out, ofs=2400 enable_bit=2
> > [4555469.251000] tg3: tg3_stop_block timed out, ofs=1400 enable_bit=2
> > [4555469.354000] tg3: tg3_stop_block timed out, ofs=c00 enable_bit=2
> > [4555469.433000] tg3: eth1: Link is down.
> > [4555472.593000] tg3: eth1: Link is up at 1000 Mbps, full duplex.
> > [4555472.594000] tg3: eth1: Flow control is on for TX and on for RX.
> > [4555498.016000] nfs: server 129.206.21.200 OK
> > [4555648.015000] nfs: server 129.206.21.200 OK
> > ... [many ok messages]
>
> I need to know what hardware you're using so please send me the tg3
> probing output for eth1 when you load the driver. Do you have TSO
> enabled?
tg3.c:v3.49 (Feb 2, 2006)
acpi_bus-0201 [01] bus_set_power : Device is not power manageable
eth1: Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:2b:aa:28
eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
eth1: dma_rwctrl[769f4000] dma_mask[64-bit]
eth2: Tigon3 [partno(BCM95704A6) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:2b:aa:29
eth2: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1]
eth2: dma_rwctrl[769f4000] dma_mask[64-bit]
The NIC is onboard a Tyan S2882.
0000:02:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03)
Subsystem: Broadcom Corporation: Unknown device 1644
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 24
Memory at fc8c0000 (64-bit, non-prefetchable) [size=64K]
Memory at fc8b0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
0000:02:09.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 03)
Subsystem: Broadcom Corporation: Unknown device 1644
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 25
Memory at fc8e0000 (64-bit, non-prefetchable) [size=64K]
Memory at fc8d0000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
The driver is compiled into the kernel (its a nfs-root booted system and
NIC modules are presently not supported by our initrd).
So the default option for tso is set. Is there any way to determine the
present tso setting? With ethtool I only find the options to turn it off/on,
but none to query the current state.
Thanks a lot,
Bernd
--
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
next prev parent reply other threads:[~2006-08-07 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 22:43 tg3: tg3_stop_block timed out Bernd Schubert
2006-08-07 23:07 ` Michael Chan
2006-08-07 23:24 ` Bernd Schubert [this message]
2006-08-07 23:46 ` Michael Chan
2006-08-09 14:44 ` Philip Molter
2006-09-03 22:35 ` Philip Molter
2006-09-04 18:25 ` Michael Chan
2006-09-04 21:27 ` Philip Molter
2006-09-12 17:22 ` Philip Molter
2006-08-09 15:20 ` Bernd Schubert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608080124.38823.bernd-schubert@gmx.de \
--to=bernd-schubert@gmx$(echo .)de \
--cc=mchan@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox