TW20230312: No (wired) network with kernel 6.2.2
Hi list, I just DUPed my laptop to the latest TW (20230312), and was left without (wired) network :( From the journal: Mar 14 13:09:35 woodstock.pitnet NetworkManager[950]: <info> [1678795775.3538] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/6) Mar 14 13:09:35 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 50:7b:9d:cf:13:43 Mar 14 13:09:35 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection Mar 14 13:09:35 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: 1000FF-0FF Mar 14 13:09:35 woodstock.pitnet NetworkManager[950]: <info> [1678795775.3881] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Mar 14 13:09:35 woodstock.pitnet systemd-networkd[826]: eth0: Link UP Mar 14 13:09:38 woodstock.pitnet systemd-networkd[826]: eth0: Gained carrier Mar 14 13:09:38 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None Mar 14 13:09:38 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO Mar 14 13:09:38 woodstock.pitnet kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9629] device (eth0): carrier: link connected Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9633] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9642] device (eth0): Activation: starting connection 'Wired connection 1' (44d9a1e3-ba1a-3cd2-b746-b172b9ac4f84) Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9643] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 14 13:09:39 woodstock.pitnet NetworkManager[950]: <info> [1678795779.0713] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mar 14 13:09:39 woodstock.pitnet NetworkManager[950]: <info> [1678795779.0723] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Mar 14 13:09:39 woodstock.pitnet NetworkManager[950]: <info> [1678795779.0727] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Mar 14 13:09:39 woodstock.pitnet systemd-networkd[826]: eth0: Lost carrier What? 10Mbps? What happened there? Booting with the previous kernel (6.1.12) everything works Mar 14 13:14:00 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Anyone else having issues with the network, or hints what has changed?
On Tue, Mar 14, 2023 at 3:37 PM Pit Suetterlin <pit@astro.su.se> wrote:
Booting with the previous kernel (6.1.12) everything works
Mar 14 13:14:00 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Anyone else having issues with the network, or hints what has changed?
Kernel driver I guess. This deserves a bug report.
Andrei Borzenkov wrote:
On Tue, Mar 14, 2023 at 3:37 PM Pit Suetterlin <pit@astro.su.se> wrote:
Booting with the previous kernel (6.1.12) everything works
Mar 14 13:14:00 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Anyone else having issues with the network, or hints what has changed?
Kernel driver I guess. This deserves a bug report.
--> boo#1209254
On 3/14/23 07:37, Pit Suetterlin wrote:
I just DUPed my laptop to the latest TW (20230312), and was left without (wired) network :(
Make sure the kernel is 6.2.5. Wireless (WPA) broke in 6.2.3 (kernel bug) and it took two more minor releases to fix that. With changes to networking, it wouldn't surprise me if it also has wired side-effects. Regression: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i... -- David C. Rankin, J.D.,P.E.
On 3/15/23 05:51, Peter Suetterlin wrote:
David C. Rankin wrote:
On 3/14/23 21:26, David C. Rankin wrote:
Make sure the kernel is 6.2.5
6.2.6 now...
TW is still at 6.2.4 ATM. I don't intend to add a bleeding edge kernel repo :-o
I'll lock 6.1.12, then try dup to 6.2.4 and see what happens....
Following along the bug report -- does seem like it is some kernel regression that popped up for you with the 6.2 kernel. It will be interesting to see what broke. -- David C. Rankin, J.D.,P.E.
On 15.03.2023 05:26, David C. Rankin wrote:
On 3/14/23 07:37, Pit Suetterlin wrote:
I just DUPed my laptop to the latest TW (20230312), and was left without (wired) network :(
Make sure the kernel is 6.2.5. Wireless (WPA) broke in 6.2.3 (kernel bug) and
How wireless WPA bug is relevant to the wrong speed of wired interface?
it took two more minor releases to fix that. With changes to networking, it wouldn't surprise me if it also has wired side-effects.
Regression:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?i...
On 3/14/23 23:14, Andrei Borzenkov wrote:
Make sure the kernel is 6.2.5. Wireless (WPA) broke in 6.2.3 (kernel bug) and
How wireless WPA bug is relevant to the wrong speed of wired interface?
Not saying it is, I said it wouldn't surprise me if while tweaking the kernel networking code an unwanted wired side effect could have crept in. The link was to a WPA issue by way of example. I'll see where this bug goes as I'm interested as well. -- David C. Rankin, J.D.,P.E.
participants (4)
-
Andrei Borzenkov -
David C. Rankin -
Peter Suetterlin -
Pit Suetterlin