From: Willy Tarreau <w@1wt.eu>
To: Matt Carlson <mcarlson@broadcom.com>
Cc: Roger Heflin <rogerheflin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xfe/0x17e() with tg3 network
Date: Fri, 21 Nov 2008 18:55:15 +0100 [thread overview]
Message-ID: <20081121175515.GA32198@1wt.eu> (raw)
In-Reply-To: <20081120215318.GB27907@xw6200.broadcom.net>
Hi Matt,
On Thu, Nov 20, 2008 at 01:53:18PM -0800, Matt Carlson wrote:
> > Today, with the notebook connected to a gig switch, I could not reproduce
> > the problem, even after one hour of approximately the same workload. I'll
> > retry with the original 100 Mbps switch on monday.
>
> Was it really a 5704 that you were using?
No, I was wrong, finally it's a 5705 :
tg3.c:v3.94 (August 14, 2008)
ACPI: PCI Interrupt Link [C0C5] enabled at IRQ 11
tg3 0000:02:0e.0: PCI INT A -> Link[C0C5] -> GSI 11 (level, low) -> IRQ 11
eth0: Tigon3 [partno(BMC5705mA3) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000Base-T Ethernet 00:0d:9d:91:ef:24
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[1]
eth0: dma_rwctrl[763f0000] dma_mask[64-bit]
tg3: eth0: Link is up at 1000 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
Here's the lspci :
02:0e.0 Class 0200: 14e4:165e (rev 03)
Subsystem: 103c:088c
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (16000ns min), cache line size 10
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 90000000 (64-bit, non-prefetchable) [size=64K]
Expansion ROM at 5c000000 [disabled] [size=64K]
Capabilities: [48] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
Address: fbff71ffffbfebfc Data: edff
00: e4 14 5e 16 06 00 b0 02 03 00 00 02 10 40 00 00
10: 04 00 00 90 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 07 00 00 00 3c 10 8c 08
30: 00 00 00 00 48 00 00 00 00 00 00 00 0b 01 40 00
Regards,
Willy
next prev parent reply other threads:[~2008-11-21 17:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 9:48 WARNING: at net/sched/sch_generic.c:219 dev_watchdog+0xfe/0x17e() with tg3 network Roger Heflin
2008-11-11 11:31 ` Peter Zijlstra
2008-11-15 4:01 ` Roger Heflin
2008-11-18 6:50 ` Willy Tarreau
2008-11-20 3:11 ` Matt Carlson
2008-11-20 5:37 ` Willy Tarreau
2008-11-20 18:43 ` Matt Carlson
2008-11-20 21:26 ` Willy Tarreau
2008-11-20 21:53 ` Matt Carlson
2008-11-21 17:55 ` Willy Tarreau [this message]
2008-11-24 13:27 ` Willy Tarreau
2008-11-24 21:52 ` Willy Tarreau
2008-11-25 1:52 ` Matt Carlson
2008-11-25 5:31 ` Willy Tarreau
2008-11-25 17:54 ` Matt Carlson
2008-11-26 21:12 ` Willy Tarreau
2008-11-26 22:54 ` Matt Carlson
2008-11-27 5:16 ` Willy Tarreau
2008-11-27 10:06 ` Frantisek Hanzlik
2008-11-27 20:33 ` Willy Tarreau
2008-12-02 22:55 ` Willy Tarreau
2008-11-20 3:00 ` Matt Carlson
2008-11-20 10:07 ` Roger Heflin
2008-11-20 17:11 ` Matt Carlson
2008-11-21 9:34 ` Roger Heflin
2008-11-20 2:52 ` Matt Carlson
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=20081121175515.GA32198@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rogerheflin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.