Bug 203447 - [REGRESSION] e1000e spews spurious error messages
Summary: [REGRESSION] e1000e spews spurious error messages
Status: RESOLVED DUPLICATE of bug 203175
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: drivers_network@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-27 15:45 UTC by Artem S. Tashkinov
Modified: 2019-04-27 17:07 UTC (History)
2 users (show)

See Also:
Kernel Version: 5.0.10
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description Artem S. Tashkinov 2019-04-27 15:45:08 UTC
The last known kernel to work fine: 5.0.6

The currently running kernel: 5.0.10

This is what I see on boot in kernel 5.0.10:

[    9.868297] e1000e 0000:00:19.0 eno1: Detected Hardware Unit Hang:
                 TDH                  <0>
                 TDT                  <1>
                 next_to_use          <1>
                 next_to_clean        <0>
               buffer_info[next_to_clean]:
                 time_stamp           <fffb8b09>
                 next_to_watch        <0>
                 jiffies              <fffb9241>
                 next_to_watch.status <0>
               MAC Status             <40080080>
               PHY Status             <7949>
               PHY 1000BASE-T Status  <800>
               PHY Extended Status    <3000>
               PCI Status             <10>
[   11.276808] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

I've never seen this message before and my hardware works fine. I have no issues with my ethernet connection as well.

This is almost certainly caused by the following commit as there are no other commits past 5.0.6 which could have caused this issue:

commit 7f0a3a436e88a71b96694c029f01a9a8eade3d5d
Author: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
Date:   Mon Jan 14 16:29:30 2019 +0300

    e1000e: fix cyclic resets at link up with active tx


My hardware is:

00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 05)
        DeviceName:  Onboard LAN
        Subsystem: ASUSTeK Computer Inc. P8P67 Deluxe Motherboard
        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
        Interrupt: pin A routed to IRQ 31
        Region 0: Memory at f7300000 (32-bit, non-prefetchable) [size=128K]
        Region 1: Memory at f7329000 (32-bit, non-prefetchable) [size=4K]
        Region 2: I/O ports at f040 [size=32]
        Capabilities: [c8] Power Management version 2
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME-
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
                Address: 00000000fee00378  Data: 0000
        Capabilities: [e0] PCI Advanced Features
                AFCap: TP+ FLR+
                AFCtrl: FLR-
                AFStatus: TP-
        Kernel driver in use: e1000e
        Kernel modules: e1000e


Settings for eth0:
	Supported ports: [ TP ]
	Supported link modes:   10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Supported FEC modes: Not reported
	Advertised link modes:  10baseT/Half 10baseT/Full 
	                        100baseT/Half 100baseT/Full 
	                        1000baseT/Full 
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Advertised FEC modes: Not reported
	Speed: 1000Mb/s
	Duplex: Full
	Port: Twisted Pair
	PHYAD: 1
	Transceiver: internal
	Auto-negotiation: on
	MDI-X: on (auto)
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000007 (7)
			       drv probe link
	Link detected: yes
Comment 1 Konstantin Khlebnikov 2019-04-27 17:05:51 UTC
duplicate bug 203175
Comment 2 Artem S. Tashkinov 2019-04-27 17:07:21 UTC

*** This bug has been marked as a duplicate of bug 203175 ***

Note You need to log in before you can comment on or make changes to this bug.