--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: r8169: frequent nic hangs; no supported pause frames, advertises Symmetric read-only
- From: Daniel Dickinson <debian@cshore.neomailbox.net>
- Date: Sun, 11 Aug 2013 13:25:20 -0400
- Message-id: <20130811172520.20626.47078.reportbug@aileron.lan>
Source: linux
Version: 3.2.0-4-amd64
Severity: normal
Tags: upstream
I have an ASUS M5A97 R2.0 Motherboard which a build realtek gigabit NIC.
It hangs (at least) when there is significant amounts of traffic (e.g.
accessing large files on a web server on the machine). It doesn't
matter if the link speed is forced to 100Mb/s or 1000Mb/s, only that the
actual max throughput for designated maximum link speed is ocurring.
ethtool reveals that supported and advertised pause from use are not the
same (none supported but advertises support for Symmetric and
Receive-only)
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
lspci -vv reveals
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 09)
Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:8505]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort+ <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 73
Region 0: I/O ports at d000 [size=256]
Region 2: Memory at d0004000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at d0000000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000feeff00c Data: 416b
Capabilities: [70] Express (v2) Endpoint, MSI 01
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 unlimited, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [d0] Vital Product Data
No end tag found
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number XX-XX-XX-XX-XX-XX-XX-XX
Kernel driver in use: r8169
If you wait long enough dmesg shows a hang timout dump (unfortunate I do
not have a copy of that output handy to include).
After a hang the device sometimes does (and sometimes does not) recover
and connectivity comes back (once a new DHCP lease is negotiated).
rmmod 8169 / modprobe 8169 when hung (and required when connectivity
doesn't come back on it's own) brings back the connection.
In wireshark (on both sides) I also notice a lot of reassembled packets
even though both sides (Windows 8 on the other side) claim to be using
MTU 1500.
If there is more info I can give please let me know what it is (I don't
want to spam you with more information than is useful to you, you have
enough to wade through as it is).
Regards,
Daniel
Linux aileron 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: Daniel Dickinson <daniel@cshore.neomailbox.net>, 719433-done@bugs.debian.org
- Subject: Re: Bug#719433: Occurring much less frequently now
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Sat, 24 Apr 2021 20:16:51 +0200
- Message-id: <YIRgkxznvJVsPNAl@eldamar.lan>
- In-reply-to: <52289252.4040400@cshore.neomailbox.net>
- References: <52289252.4040400@cshore.neomailbox.net>
Hi,
On Thu, Sep 05, 2013 at 10:16:50AM -0400, Daniel Dickinson wrote:
> Hi,
>
> I just thought I'd let you know that the issue appears to occur only
> rarely now, even without jumbo frames (which I had to disable because of
> communicating to a target host through a router that doesn't support
> jumbo frames).
Given that and the age of the bug (and last conversation on it), I
went ahead and closed the bug now. If you still experience issues and
disagree more importantly on the closure, feel free to reopen!
Regards,
Salvatore
--- End Message ---