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: Mon, 24 Nov 2008 14:27:44 +0100 [thread overview]
Message-ID: <20081124132744.GB24851@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.
fairly easier now with the same switch. I just have to transfer 100k objects
over HTTP via this switch to see the problem happen :
tg3: eth0: The system may be re-ordering memory-mapped I/O cycles to the network device, attempting to recover. Please report the problem to the driver maintainer and include system chipset information.
tg3: tg3_stop_block timed out, ofs=1400 enable_bit=2
tg3: tg3_stop_block timed out, ofs=c00 enable_bit=2
tg3: eth0: Link is down.
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is on for TX and on for RX.
The switch is an el-cheapo D-Link 10/100. Note that this time I did not see
any warning. Maybe I did not wait long enough though. Here are some stats
and information I could collect :
root@wtap:/# ethtool -i eth0
driver: tg3
version: 3.94
firmware-version: 5705-v3.14
bus-info: 0000:02:0e.0
root@wtap:/# ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes
root@wtap:/# ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp segmentation offload: off
root@wtap:/# ethtool -a eth0
Pause parameters for eth0:
Autonegotiate: on
RX: on
TX: on
root@wtap:/# netstat -ni
Kernel Interface table
Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 61665 0 0 0 65133 0 0 0 BMRU
lo 16436 0 945938 0 0 0 945938 0 0 0 LRU
root@wtap:/# ethtool -S eth0
NIC statistics:
rx_octets: 52461785
rx_fragments: 0
rx_ucast_packets: 61018
rx_mcast_packets: 0
rx_bcast_packets: 476
rx_fcs_errors: 0
rx_align_errors: 0
rx_xon_pause_rcvd: 0
rx_xoff_pause_rcvd: 0
rx_mac_ctrl_rcvd: 0
rx_xoff_entered: 0
rx_frame_too_long_errors: 0
rx_jabbers: 0
rx_undersize_packets: 0
rx_in_length_errors: 0
rx_out_length_errors: 0
rx_64_or_less_octet_packets: 0
rx_65_to_127_octet_packets: 0
rx_128_to_255_octet_packets: 0
rx_256_to_511_octet_packets: 0
rx_512_to_1023_octet_packets: 0
rx_1024_to_1522_octet_packets: 0
rx_1523_to_2047_octet_packets: 0
rx_2048_to_4095_octet_packets: 0
rx_4096_to_8191_octet_packets: 0
rx_8192_to_9022_octet_packets: 0
tx_octets: 54658258
tx_collisions: 0
tx_xon_sent: 0
tx_xoff_sent: 0
tx_flow_control: 0
tx_mac_errors: 0
tx_single_collisions: 0
tx_mult_collisions: 0
tx_deferred: 0
tx_excessive_collisions: 0
tx_late_collisions: 0
tx_collide_2times: 0
tx_collide_3times: 0
tx_collide_4times: 0
tx_collide_5times: 0
tx_collide_6times: 0
tx_collide_7times: 0
tx_collide_8times: 0
tx_collide_9times: 0
tx_collide_10times: 0
tx_collide_11times: 0
tx_collide_12times: 0
tx_collide_13times: 0
tx_collide_14times: 0
tx_collide_15times: 0
tx_ucast_packets: 65033
tx_mcast_packets: 0
tx_bcast_packets: 0
tx_carrier_sense_errors: 0
tx_discards: 0
tx_errors: 0
dma_writeq_full: 0
dma_write_prioq_full: 0
rxbds_empty: 0
rx_discards: 0
rx_errors: 0
rx_threshold_hit: 0
dma_readq_full: 0
dma_read_prioq_full: 0
tx_comp_queue_full: 0
ring_set_send_prod_index: 0
ring_status_update: 0
nic_irqs: 0
nic_avoided_irqs: 0
nic_tx_threshold_hit: 0
I will try to go back to older kernels then bisect tg3 changes. I
cannot do this right now since I'm using my laptop for work ;-)
Regards,
Willy
next prev parent reply other threads:[~2008-11-24 13:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 9:48 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
2008-11-24 13:27 ` Willy Tarreau [this message]
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=20081124132744.GB24851@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®