You are not logged in.
Hello! On my Dell Optiplex 7010 the Ethernet controller does not work with kernel 5.3. I've tested with current kernel 5.3.5.arch1-1 as well as with recent kernels 5.3.* and switched back to the last 5.2-kernel, i.e. 5.2.14-arch2-1. Ethernet is setup using netctl with a static ip address. With kernel 5.3 there is no signal found on the line! Up to kernel 5.2.* there was no problem before.
lspci shows that the driver e1000e is actice:
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 04)
DeviceName: Onboard LAN
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville)
Flags: bus master, fast devsel, latency 0, IRQ 29
Memory at f7c00000 (32-bit, non-prefetchable) [size=128K]
Memory at f7c39000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f080 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000eThe difference to kernel 5.2 is, that IRQ 29 instead of IRQ 28 is used here. Maybe that is of interest to solve that problem.
ethtool output shows that there is no link detected:
Settings for eno1:
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: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: off (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: noAnd netctl status gives:
netctl@hsh_2544.service - Static address at hsh_2544
Loaded: loaded (/etc/systemd/system/netctl@hsh_2544.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2019-10-07 09:37:52 CEST; 4min 27s ago
Docs: man:netctl.profile(5)
Process: 494 ExecStart=/usr/lib/netctl/network start hsh_2544 (code=exited, status=1/FAILURE)
Main PID: 494 (code=exited, status=1/FAILURE)
Okt 07 09:37:52 hsh systemd[1]: netctl@hsh_2544.service: Main process exited, code=exited, status=1/FAILURE
Okt 07 09:37:52 hsh systemd[1]: netctl@hsh_2544.service: Failed with result 'exit-code'.
Okt 07 09:37:52 hsh systemd[1]: Failed to start Static address in HsH.
Okt 07 09:41:26 hsh systemd[1]: /etc/systemd/system/netctl@hsh_2544.service:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Okt 07 09:41:26 hsh systemd[1]: /etc/systemd/system/netctl@hsh_2544.service:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Okt 07 09:41:28 hsh systemd[1]: /etc/systemd/system/netctl@hsh_2544.service:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Okt 07 09:42:07 hsh systemd[1]: /etc/systemd/system/netctl@hsh_2544.service:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Okt 07 09:42:07 hsh systemd[1]: /etc/systemd/system/netctl@hsh_2544.service:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Okt 07 09:42:12 hsh systemd[1]: /etc/systemd/system/netctl@hsh_2544.service:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.
Okt 07 09:42:20 hsh systemd[1]: /etc/systemd/system/netctl@hsh_2544.service:1: .include directives are deprecated, and support for them will be removed in a future version of systemd. Please use drop-in files instead.The driver e1000e does work successful here in a notebook using DHCP with a different Intel chipset.
Last edited by C-Klaus (2020-01-16 10:10:21)
Offline
Offline
I have the same problem on my Dell T5610 with 82579LM rev 06. After boot with kernel 5.3.x the e1000e network interface is constantly switching between "activated" and "deactivated" state every few seconds. The LEDs on the network port switch between going blank and blinking yellow every few seconds respectively. I use NetworkManager and here is the log from jouirnalctl:
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.7583] device (enp0s25): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 15 10:10:47 plamen kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8230] dhcp4 (enp0s25): canceled DHCP transaction, DHCP client pid 2294
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8231] dhcp4 (enp0s25): state changed unknown -> done
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8257] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8266] device (enp0s25): carrier: link connected
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8272] device (enp0s25): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8293] policy: auto-activating connection 'Wired connection 1' (41322d38-6234-3009-88dd-81e7f365704d)
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8302] device (enp0s25): Activation: starting connection 'Wired connection 1' (41322d38-6234-3009-88dd-81e7f365704d)
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8305] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.8312] manager: NetworkManager state is now CONNECTING
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.9569] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.9576] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.9579] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Oct 15 10:10:47 plamen NetworkManager[960]: <info> [1571159447.9597] dhcp4 (enp0s25): dhclient started with pid 2304
Oct 15 10:10:47 plamen kdeinit5[1339]: plasma-nm: Unhandled active connection state change: 1
Oct 15 10:10:48 plamen dhclient[2304]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 4
Oct 15 10:10:52 plamen dhclient[2304]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 10
Oct 15 10:10:53 plamen kwin_x11[1399]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57092, resource id: 37749534, major code: 15 (QueryTree), minor code: 0
Oct 15 10:10:53 plamen NetworkManager[960]: <info> [1571159453.9583] device (enp0s25): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 15 10:10:54 plamen NetworkManager[960]: <info> [1571159454.0231] dhcp4 (enp0s25): canceled DHCP transaction, DHCP client pid 2304
Oct 15 10:10:54 plamen NetworkManager[960]: <info> [1571159454.0231] dhcp4 (enp0s25): state changed unknown -> done
Oct 15 10:10:54 plamen NetworkManager[960]: <info> [1571159454.0259] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 15 10:10:54 plamen kwin_x11[1399]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57761, resource id: 54556287, major code: 18 (ChangeProperty), minor code: 0
Oct 15 10:10:56 plamen kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.1346] device (enp0s25): carrier: link connected
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.1350] device (enp0s25): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.1366] policy: auto-activating connection 'Wired connection 1' (41322d38-6234-3009-88dd-81e7f365704d)
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.1378] device (enp0s25): Activation: starting connection 'Wired connection 1' (41322d38-6234-3009-88dd-81e7f365704d)
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.1380] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.1388] manager: NetworkManager state is now CONNECTING
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.2674] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.2684] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.2688] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Oct 15 10:10:56 plamen NetworkManager[960]: <info> [1571159456.2704] dhcp4 (enp0s25): dhclient started with pid 2319
Oct 15 10:10:56 plamen kdeinit5[1339]: plasma-nm: Unhandled active connection state change: 1
Oct 15 10:10:56 plamen dhclient[2319]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3
Oct 15 10:10:57 plamen kwin_x11[1399]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 59828, resource id: 54556789, major code: 18 (ChangeProperty), minor code: 0
Oct 15 10:10:59 plamen kwin_x11[1399]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 61382, resource id: 37749563, major code: 15 (QueryTree), minor code: 0
Oct 15 10:10:59 plamen dhclient[2319]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.2690] device (enp0s25): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 15 10:11:02 plamen kernel: e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3336] dhcp4 (enp0s25): canceled DHCP transaction, DHCP client pid 2319
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3336] dhcp4 (enp0s25): state changed unknown -> done
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3359] manager: NetworkManager state is now CONNECTED_LOCAL
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3369] device (enp0s25): carrier: link connected
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3377] device (enp0s25): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3400] policy: auto-activating connection 'Wired connection 1' (41322d38-6234-3009-88dd-81e7f365704d)
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3409] device (enp0s25): Activation: starting connection 'Wired connection 1' (41322d38-6234-3009-88dd-81e7f365704d)
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3411] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.3420] manager: NetworkManager state is now CONNECTING
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.4699] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.4705] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.4708] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Oct 15 10:11:02 plamen NetworkManager[960]: <info> [1571159462.4725] dhcp4 (enp0s25): dhclient started with pid 2328
Oct 15 10:11:02 plamen kdeinit5[1339]: plasma-nm: Unhandled active connection state change: 1
Oct 15 10:11:02 plamen dhclient[2328]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 8The only solution for me as of now is to revert to 5.2.14. If someone finds more information about this please let us know. Thanks!
Last edited by pvn (2019-10-15 17:44:47)
Offline
If someone finds more information about this please let us know. Thanks!
You checked the issue is not https://bugs.archlinux.org/task/64018 and that is why you are asking for more information?
Offline
I don't think it is the same issue - it could be. The bug reads "After upgrading to kernel 5.3 module e1000e not loaded". I personally have no problem loading the e1000e module. It loads automatically on every boot. It just does not work properly.
Last edited by pvn (2019-10-15 18:42:01)
Offline
If the issue was present before 5.3.5 then it is a different issue.
Last edited by loqs (2019-10-15 18:59:37)
Offline
For me the problem started with 5.3 and I can reproduce with all 5.3.x releases so far.
Offline
You could try 5.4-rc3 to see if it has already been fixed upstream.
If it is still present I would suggest bisecting between 5.2 and 5.3 to find the cause then reporting the issue upstream.
Offline
For me the problem started with 5.3 and I can reproduce with all 5.3.x releases so far.
Same here with all 5.3.x kernels. And as pvn wrote: it's not the mentioned bug 64018 because the driver e1000e loads successfully. Still running latest kernel 5.2.x and waiting for kernel 5.4.
Offline
I contacted two guys from Intel about this issue. I took their emails from the most recent e1000e commit. This is their exact response:
I believe the e1000e developers are aware of the issue you reported and are
currently trying to reproduce the issue. I have CC'd Vitaly and Sasha who
maintain the e1000e driver.I will keep you posted.
Offline
https://bugzilla.kernel.org/show_bug.cgi?id=205047#c19
Which I think means test the following and report on the kernel bugzilla
diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c b/drivers/net/ethernet/intel/e1000e/netdev.c
index e4baa13b3cda..72f9957fcb70 100644
--- a/drivers/net/ethernet/intel/e1000e/netdev.c
+++ b/drivers/net/ethernet/intel/e1000e/netdev.c
@@ -5188,6 +5188,7 @@ static void e1000_watchdog_task(struct work_struct *work)
/* Cancel scheduled suspend requests. */
pm_runtime_resume(netdev->dev.parent);
+printk("e1000e deb: STATUS = %d\n", er32(STATUS));
/* Checking if MAC is in DMoff state*/
pcim_state = er32(STATUS);
while (pcim_state & E1000_STATUS_PCIM_STATE) {
@@ -5198,10 +5199,9 @@ static void e1000_watchdog_task(struct work_struct *work)
usleep_range(10000, 20000);
pcim_state = er32(STATUS);
- /* Checking if MAC exited DMoff state */
- if (!(pcim_state & E1000_STATUS_PCIM_STATE))
- e1000_phy_hw_reset(&adapter->hw);
}
+ e1000_phy_hw_reset(&adapter->hw);
+printk("e1000e deb: STATUS = %d\n", er32(STATUS));
/* update snapshot of PHY registers on LSC */
e1000_phy_read_status(adapter);Offline
I did wait for kernel 5.4 but netctl still is not able to configure a static ip address with that kernel, too. Output of information forg the interface does show the same as mentioned on top of this issue.
Offline
Problem is solved since kernel release 5.4.10.
Last edited by C-Klaus (2020-01-16 10:09:01)
Offline