From: P@draigBrady.com
To: e1000-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: strange e1000 interface freeze
Date: Mon, 09 Aug 2004 11:54:02 +0100 [thread overview]
Message-ID: <411757CA.4010401@draigBrady.com> (raw)
I've been able to reproduce an situation here
where the interface freezes on a platform
where a continuous stream of about 8000 packets
per second are being received. It usually takes
about 2 days to reproduce, but I've a system
in this state now if you have anything you want
me to look at.
I've reproduced the problem in both 100 and 1000 Mb/s mode,
but it seems easier to reproduce in 100 mode?
Also usually one but sometimes both interfaces lock up.
By lock up I mean that the interface records all packets
as fifo errors, and it receives only 1 interrupt every 2 seconds.
Note the other NAPI interface works fine (at about 7.5K interrupts/s).
The system is E7501 based with an 82546EB running kernel 2.4.20
with the 5.2.52 e1000 driver in NAPI mode.
Here are the ethernet settings from one of the dual ports
(the other is identical):
Intel(R) PRO/1000 Network Driver - version 5.2.52
Copyright (c) 1999-2004 Intel Corporation.
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth1: e1000_validate_option: Transmit Descriptors set to 4096
e1000: eth1: e1000_validate_option: Receive Descriptors set to 4096
e1000: eth1: e1000_validate_option: Checksum Offload Enabled
e1000: eth1: e1000_validate_option: Flow Control Disabled
e1000: eth1: e1000_validate_option: Transmit Interrupt Delay set to 0
e1000: eth1: e1000_validate_option: Transmit Absolute Interrupt Delay
set to 0
e1000: eth1: e1000_validate_option: Receive Interrupt Delay set to 0
e1000: eth1: e1000_validate_option: Receive Absolute Interrupt Delay
set to 0
Here is the lspci output for the locked interface.
NOTE the pci master abort is set!
05:0c.1 Class 0200: 8086:1010 (rev 01)
Subsystem: 8086:1011
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: 52 (63750ns min), cache line size 08
Interrupt: pin B routed to IRQ 49
Region 0: Memory at fc220000 (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at 2040 [size=64]
Capabilities: [dc] 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: [e4] PCI-X non-bridge device.
Command: DPERE- ERO+ RBC=2 OST=0
Status: Bus=0 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, DC=simple,
DMMRBC=0, DMOST=0, DMCRS=0, RSCEM- Capabilities: [f0] Message
Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
There are no e1000 messages in the logs.
cheers,
Pádraig.
next reply other threads:[~2004-08-09 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 10:54 P [this message]
2004-08-11 14:26 ` strange e1000 interface freeze Robert Olsson
[not found] ` <411A3238.6060400@draigBrady.com>
2004-08-11 15:08 ` Robert Olsson
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=411757CA.4010401@draigBrady.com \
--to=p@draigbrady.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).