[SOLVED] laptop freeze when plugging Ethernet cable

cunfusu · 2023-12-16 17:06:22

tl;dr:

Turned out my issue was caused by the wireless system. When the wifi is turned off for some reason things cascade in a way that system become unsable. Plugging the eth cable was simply a trigger for the wifi card being turned off (this can be disabled via uefi).
I don't really grasp the detail of the issue but more details and related discussion have been provided by other users. The issue seems to be within the wifi driver or in the network manager (or both) hopefull it will be solved in future.

Original post follow:

This is one of the strangest issues I've ever had.

Got this refurbished laptop (dell latitude 7390) and I've decided to install arch on it.
I never got to actually use the eth connection till today when I had to download very large files and decided that eth was required.
I actually have a memory of my trying to share the eth connection from another linux computer but I did not managed to get it solved quickly and moved on.

Anyway.
When I plug the eth cable (the other side is connected to the router) the wifi connection stop working and I cannot run any other command in my terminal I've tried to run

nmcli
nmtui
ping
bmon
dmesg
reboot

all these commands seems to hang, do nothing and do not return any output. (so I'm kinda stuck on how to troubleshoot the issue)
I have to keep the poweron button till the laptop shutdown and I have to restart the laptop

I gave a look at the wiki (https://wiki.archlinux.org/title/Networ … n/Ethernet)
but everything looks regular

network cards I see when I run "lspci -v"

02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
	Subsystem: Intel Corporation Device 0050
	Flags: bus master, fast devsel, latency 0, IRQ 144
	Memory at ec100000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21)
	Subsystem: Dell Device 081b
	Flags: bus master, fast devsel, latency 0, IRQ 142
	Memory at ec300000 (32-bit, non-prefetchable) [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: e1000e
	Kernel modules: e1000e

➜  ~ sudo dmesg | grep e1000e 
[sudo] password for corsair: 
[   45.717293] e1000e: Intel(R) PRO/1000 Network Driver
[   45.717297] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   45.717630] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   45.836612] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered PHC clock
[   45.900488] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) c8:f7:50:55:40:8c
[   45.900492] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[   45.900555] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
[   46.066358] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0

nmcli output related to he eth device

enp0s31f6: unavailable
        "Intel I219-LM"
        ethernet (e1000e), C8:F7:50:55:40:8C, hw, mtu 1500

I also own a anker usbc hub that has an eth port. when the cable is plugged into the hub the connection works perfectly so I suspect the issue might be with the laptop port or the driver.

Plan to run an ubuntu iso to check if it is a software issue.
In the meantime please let me know if you have any idea on what I could do to troubleshot or if you know what the cause might be.

Last edited by cunfusu (2023-12-18 22:47:56)

-thc · 2023-12-16 17:55:50

A good baseline test would be to boot the laptop from an Arch install medium and plug in the Ethernet cable.

seth · 2023-12-16 19:00:01

And also don't grep fro random tokens, run "dmesg -w", or even better "sudo journalctl -f" and then plug the cable and post the tail.

cunfusu · 2023-12-17 12:26:41

Okay I start suspecting that the issue might not be software related.
I've prepared an Arch USB key and I'm experiencing a similar issue when I run the arch installer shell.

Strangely if I start the laptop with the cable plugged in I can ping something normally, however if I unplug and replug the eth cable run the ping command freeze the shell and nothing else can be done (cannot even kill the running command wit ctrl-c)

if I halt the laptop with the power button I can see what I believe are some systemd outputs
the ones that look something like:

[ ok ] something something

and it stops with a loading line referring to the fact that something related to networking cannot be stopped or is being stopped but it does not proceed.

I own another similar laptop (same model but different configuration) and when I run arch via usb key the eth connection works correctly even when plugging and unplugging it.

Out of curiosity I've tried to check what happen if I start the laptop with the usb cable plugged in and after login and the sshagent prompts I cannot execute much even if I start sway it will hang.

What's your take?

in case this makes any sense for you here is the journalctl of when i plug the cable

➜  ~ sudo journalctl -f
[sudo] password for corsair:
Dec 17 00:29:54 ptak rtkit-daemon[845]: Supervising 8 threads of 5 processes of 1 users.
Dec 17 00:29:55 ptak kernel: warning: `Socket Thread' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Dec 17 00:30:14 ptak rtkit-daemon[845]: Supervising 8 threads of 5 processes of 1 users.
Dec 17 00:30:14 ptak rtkit-daemon[845]: Supervising 8 threads of 5 processes of 1 users.
Dec 17 00:31:14 ptak rtkit-daemon[845]: Supervising 8 threads of 5 processes of 1 users.
Dec 17 00:31:14 ptak rtkit-daemon[845]: Supervising 8 threads of 5 processes of 1 users.
Dec 17 00:32:07 ptak dbus-daemon[540]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.103' (uid=0 pid=37159 comm="sudo journalctl -f")
Dec 17 00:32:07 ptak dbus-daemon[540]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Dec 17 00:32:09 ptak sudo[37159]:  corsair : TTY=pts/0 ; PWD=/home/corsair ; USER=root ; COMMAND=/usr/bin/journalctl -f
Dec 17 00:32:09 ptak sudo[37159]: pam_unix(sudo:session): session opened for user root(uid=0) by corsair(uid=1000)
Dec 17 00:33:06 ptak kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: Rx/Tx
Dec 17 00:33:06 ptak kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Down
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5689] device (enp0s31f6): carrier: link connected
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5691] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5706] policy: auto-activating connection 'Wired connection 1' (89e65e4a-b62e-3cff-9430-31dd6b3508e3)
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5710] device (enp0s31f6): Activation: starting connection 'Wired connection 1' (89e65e4a-b62e-3cff-9430-31dd6b3508e3)
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5710] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5713] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5719] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 17 00:33:06 ptak NetworkManager[543]: <info>  [1702769586.5722] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds)
Dec 17 00:33:10 ptak NetworkManager[543]: <info>  [1702769590.2742] device (enp0s31f6): carrier: link connected
Dec 17 00:33:10 ptak kernel: e1000e 0000:00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
Dec 17 00:33:11 ptak NetworkManager[543]: <info>  [1702769591.4033] dhcp4 (enp0s31f6): state changed new lease, address=192.168.0.248
Dec 17 00:33:11 ptak NetworkManager[543]: <info>  [1702769591.4280] device (enp0s31f6): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 17 00:33:11 ptak dbus-daemon[540]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.2' (uid=0 pid=543 comm="/usr/bin/NetworkManager --no-daemon")
Dec 17 00:33:11 ptak systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 17 00:33:11 ptak dbus-daemon[540]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 17 00:33:11 ptak systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 17 00:33:11 ptak NetworkManager[543]: <info>  [1702769591.4917] device (enp0s31f6): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 17 00:33:11 ptak NetworkManager[543]: <info>  [1702769591.4919] device (enp0s31f6): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 17 00:33:11 ptak NetworkManager[543]: <info>  [1702769591.4922] device (enp0s31f6): Activation: successful, device activated.
Dec 17 00:33:11 ptak NetworkManager[543]: <info>  [1702769591.6174] policy: set 'Wired connection 1' (enp0s31f6) as default for IPv4 routing and DNS
Dec 17 00:33:12 ptak NetworkManager[543]: <info>  [1702769592.4976] dhcp6 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds)
Dec 17 00:33:12 ptak NetworkManager[543]: <info>  [1702769592.5113] dhcp6 (enp0s31f6): state changed new lease
Dec 17 00:33:15 ptak wpa_supplicant[592]: rfkill: WLAN hard blocked
Dec 17 00:33:15 ptak wpa_supplicant[592]: rfkill: WLAN hard blocked
Dec 17 00:33:15 ptak kernel: iwlwifi 0000:02:00.0: RF_KILL bit toggled to disable radio.
Dec 17 00:33:15 ptak kernel: iwlwifi 0000:02:00.0: reporting RF_KILL (radio disabled)
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2674] manager: rfkill: Wi-Fi now disabled by radio killswitch
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2676] device (wlan0): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2677] dhcp4 (wlan0): canceled DHCP transaction
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2677] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2678] dhcp4 (wlan0): state changed no lease
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2679] dhcp6 (wlan0): canceled DHCP transaction
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2679] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Dec 17 00:33:15 ptak NetworkManager[543]: <info>  [1702769595.2680] dhcp6 (wlan0): state changed no lease
Dec 17 00:33:15 ptak systemd[1]: Starting Load/Save RF Kill Switch Status...
Dec 17 00:33:15 ptak systemd[1]: Started Load/Save RF Kill Switch Status.
Dec 17 00:33:15 ptak kernel: wlan0: deauthenticating from 54:67:51:80:94:54 by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 17 00:33:17 ptak kernel: iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 5
Dec 17 00:33:17 ptak kernel: iwlwifi 0000:02:00.0: Queue 5 is active on fifo 3 and stuck for 10000 ms. SW [7, 8] HW [8, 8] FH TRB=0x080305007
Dec 17 00:33:19 ptak kernel: iwlwifi 0000:02:00.0: fail to flush all tx fifo queues Q 5
Dec 17 00:33:19 ptak kernel: iwlwifi 0000:02:00.0: Queue 5 is active on fifo 3 and stuck for 10000 ms. SW [7, 8] HW [8, 8] FH TRB=0x080305007
Dec 17 00:33:19 ptak kernel: ------------[ cut here ]------------
Dec 17 00:33:19 ptak kernel: WARNING: CPU: 0 PID: 31450 at net/mac80211/sta_info.c:1442 __sta_info_destroy_part2+0x243/0x330 [mac80211]
Dec 17 00:33:19 ptak kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq ntfs3 hid_logitech_hidpp hid_logitech_dj xpad r8153_ecm cdc_ether usbnet snd_usb_audio snd_usbmidi_lib hid_playstation snd_ump led_class_multicolor snd_rawmidi ff_memless snd_seq_device r8152 mii typec_displayport ccm snd_hda_codec_hdmi snd_soc_avs snd_soc_hda_codec snd_ctl_led snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match intel_tcc_cooling snd_soc_acpi x86_pkg_temp_thermal intel_powerclamp snd_soc_core snd_hda_codec_realtek coretemp snd_hda_codec_generic snd_compress iwlmvm ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi mac80211 dell_rbtn uvcvideo kvm snd_hda_codec btusb videobuf2_vmalloc libarc4 snd_hda_core btrtl ee1004 irqbypass dell_laptop snd_hwdep uvc dell_wmi snd_pcm rapl btintel iTCO_wdt iwlwifi videobuf2_memops snd_timer mei_wdt btbcm dell_wmi_sysman intel_cstate intel_pmc_bxt videobuf2_v4l2 processor_thermal_device_pci_legacy dell_smbios btmtk
Dec 17 00:33:19 ptak kernel:  processor_thermal_device vfat mei_pxp mei_hdcp iTCO_vendor_support intel_rapl_msr fat dell_smm_hwmon processor_thermal_rfim intel_uncore pcspkr dcdbas ucsi_acpi firmware_attributes_class bluetooth ledtrig_audio videodev dell_wmi_descriptor intel_wmi_thunderbolt snd wmi_bmof i2c_i801 cfg80211 processor_thermal_mbox mei_me soundcore typec_ucsi processor_thermal_rapl e1000e i2c_smbus ecdh_generic videobuf2_common typec mei intel_rapl_common i2c_hid_acpi intel_xhci_usb_role_switch intel_lpss_pci rfkill intel_pch_thermal mc intel_soc_dts_iosf roles i2c_hid intel_lpss_acpi intel_lpss intel_hid int3403_thermal int3400_thermal idma64 int340x_thermal_zone sparse_keymap acpi_thermal_rel acpi_pad joydev mousedev mac_hid pkcs8_key_parser i2c_dev fuse loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 dm_crypt cbc encrypted_keys trusted asn1_encoder tee dm_mod uas usb_storage hid_multitouch usbhid i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic gf128mul
Dec 17 00:33:19 ptak kernel:  ghash_clmulni_intel serio_raw sha512_ssse3 atkbd sha256_ssse3 i2c_algo_bit rtsx_pci_sdmmc libps2 sha1_ssse3 drm_buddy mmc_core aesni_intel vivaldi_fmap ttm nvme crypto_simd intel_gtt cryptd nvme_core drm_display_helper video nvme_common xhci_pci rtsx_pci cec xhci_pci_renesas i8042 serio wmi
Dec 17 00:33:19 ptak kernel: CPU: 0 PID: 31450 Comm: kworker/0:1 Tainted: G        W          6.6.7-arch1-1 #1 4505c4baa0b3d7c4037b0e8f5402626fa360717f
Dec 17 00:33:19 ptak kernel: Hardware name: Dell Inc. Latitude 7390/09386V, BIOS 1.33.0 07/06/2023
Dec 17 00:33:19 ptak kernel: Workqueue: events cfg80211_rfkill_block_work [cfg80211]
Dec 17 00:33:19 ptak kernel: RIP: 0010:__sta_info_destroy_part2+0x243/0x330 [mac80211]
Dec 17 00:33:19 ptak kernel: Code: bb d4 00 00 00 00 0f 84 68 ff ff ff 45 31 c0 b9 01 00 00 00 48 89 da 4c 89 f6 4c 89 e7 e8 35 86 ff ff 85 c0 0f 84 4a ff ff ff <0f> 0b e9 43 ff ff ff 41 0f b6 d5 be 03 00 00 00 48 89 df e8 75 b5
Dec 17 00:33:19 ptak kernel: RSP: 0018:ffffc900134c3948 EFLAGS: 00010282
Dec 17 00:33:19 ptak kernel: RAX: 00000000ffffff92 RBX: ffff888179622000 RCX: 0000000000000027
Dec 17 00:33:19 ptak kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff888104562098
Dec 17 00:33:19 ptak kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffffc900134c34a0
Dec 17 00:33:19 ptak kernel: R10: 0000000000000003 R11: ffffffffb8aca428 R12: ffff888104560900
Dec 17 00:33:19 ptak kernel: R13: ffff888179622ab8 R14: ffff88810775c9c0 R15: ffff88810775c9c0
Dec 17 00:33:19 ptak kernel: FS:  0000000000000000(0000) GS:ffff888276400000(0000) knlGS:0000000000000000
Dec 17 00:33:19 ptak kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 17 00:33:19 ptak kernel: CR2: 0000558938e4bd28 CR3: 0000000225c20003 CR4: 00000000003706f0
Dec 17 00:33:19 ptak kernel: Call Trace:
Dec 17 00:33:19 ptak kernel:  <TASK>
Dec 17 00:33:19 ptak kernel:  ? __sta_info_destroy_part2+0x243/0x330 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  ? __warn+0x81/0x130
Dec 17 00:33:19 ptak kernel:  ? __sta_info_destroy_part2+0x243/0x330 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  ? report_bug+0x171/0x1a0
Dec 17 00:33:19 ptak kernel:  ? handle_bug+0x3c/0x80
Dec 17 00:33:19 ptak kernel:  ? exc_invalid_op+0x17/0x70
Dec 17 00:33:19 ptak kernel:  ? asm_exc_invalid_op+0x1a/0x20
Dec 17 00:33:19 ptak kernel:  ? __sta_info_destroy_part2+0x243/0x330 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  ? __sta_info_destroy_part2+0x23b/0x330 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  __sta_info_flush+0x169/0x1f0 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  ieee80211_set_disassoc+0x16c/0x620 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  ieee80211_mgd_deauth+0x13f/0x3d0 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  cfg80211_mlme_deauth+0xba/0x1e0 [cfg80211 2310af0ea1e8354b430b4567ebe5a6da9acf5369]
Dec 17 00:33:19 ptak kernel:  cfg80211_mlme_down+0x65/0x90 [cfg80211 2310af0ea1e8354b430b4567ebe5a6da9acf5369]
Dec 17 00:33:19 ptak kernel:  cfg80211_disconnect+0x180/0x1f0 [cfg80211 2310af0ea1e8354b430b4567ebe5a6da9acf5369]
Dec 17 00:33:19 ptak kernel:  cfg80211_netdev_notifier_call+0x141/0x4d0 [cfg80211 2310af0ea1e8354b430b4567ebe5a6da9acf5369]
Dec 17 00:33:19 ptak kernel:  ? iwl_mvm_send_cmd+0x1f/0x60 [iwlmvm f65b20535e0a75d8dada79714f0fe2055d80472b]
Dec 17 00:33:19 ptak kernel:  ? iwl_mvm_mc_iface_iterator+0xcd/0xf0 [iwlmvm f65b20535e0a75d8dada79714f0fe2055d80472b]
Dec 17 00:33:19 ptak kernel:  ? __iterate_interfaces+0x9d/0x110 [mac80211 3ef8b770f72bcbebc8552a2012df1f182a03747f]
Dec 17 00:33:19 ptak kernel:  ? __pfx_iwl_mvm_mc_iface_iterator+0x10/0x10 [iwlmvm f65b20535e0a75d8dada79714f0fe2055d80472b]
Dec 17 00:33:19 ptak kernel:  ? iwl_mvm_send_cmd_pdu+0x62/0xb0 [iwlmvm f65b20535e0a75d8dada79714f0fe2055d80472b]
Dec 17 00:33:19 ptak kernel:  ? rtnl_is_locked+0x15/0x20
Dec 17 00:33:19 ptak kernel:  ? inetdev_event+0x3d/0x6f0
Dec 17 00:33:19 ptak kernel:  ? iwl_mvm_recalc_multicast+0x5d/0xa0 [iwlmvm f65b20535e0a75d8dada79714f0fe2055d80472b]
Dec 17 00:33:19 ptak kernel:  notifier_call_chain+0x5a/0xd0
Dec 17 00:33:19 ptak kernel:  __dev_close_many+0x5f/0x110
Dec 17 00:33:19 ptak kernel:  dev_close_many+0x8f/0x150
Dec 17 00:33:19 ptak kernel:  dev_close+0x83/0xb0
Dec 17 00:33:19 ptak kernel:  cfg80211_shutdown_all_interfaces+0x4d/0xf0 [cfg80211 2310af0ea1e8354b430b4567ebe5a6da9acf5369]
Dec 17 00:33:19 ptak kernel:  cfg80211_rfkill_block_work+0x1e/0x30 [cfg80211 2310af0ea1e8354b430b4567ebe5a6da9acf5369]
Dec 17 00:33:19 ptak kernel:  process_one_work+0x171/0x340
Dec 17 00:33:19 ptak kernel:  worker_thread+0x27b/0x3a0
Dec 17 00:33:19 ptak kernel:  ? __pfx_worker_thread+0x10/0x10
Dec 17 00:33:19 ptak kernel:  kthread+0xe5/0x120
Dec 17 00:33:19 ptak kernel:  ? __pfx_kthread+0x10/0x10
Dec 17 00:33:19 ptak kernel:  ret_from_fork+0x31/0x50
Dec 17 00:33:19 ptak kernel:  ? __pfx_kthread+0x10/0x10
Dec 17 00:33:19 ptak kernel:  ret_from_fork_asm+0x1b/0x30
Dec 17 00:33:19 ptak kernel:  </TASK>
Dec 17 00:33:19 ptak kernel: ---[ end trace 0000000000000000 ]---
Dec 17 00:33:20 ptak systemd[1]: systemd-rfkill.service: Deactivated successfully.
Dec 17 00:33:21 ptak systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Dec 17 00:33:25 ptak kernel: iwlwifi 0000:02:00.0: Queue 5 is active on fifo 3 and stuck for 10000 ms. SW [7, 8] HW [8, 8] FH TRB=0x080305007

seth · 2023-12-17 17:04:21

https://bbs.archlinux.org/viewtopic.php … 0#p2136220

The problem is the wifi chip. You probably have a system where the rj45 plug acts as a hardware rfkill (ie. when you plug that, the uefi deactivates the wifi chip)
See whether you can disable that behavior in the UEFI (BIOS)
Alternatively, make dure to disconnect from the wifi (and ideally software rfkill it) before plugging the rj45 cable - the system should™ remain stable then.

If disabling the HW rfkill works, but you'd like to retain the functionality, see https://wiki.archlinux.org/title/Networ … plugged_in

cunfusu · 2023-12-17 18:58:39

Seth you are absolutely right. the issue seems to be more related to the wireless than to the eth.
plugging the eth cable is only a trigger of the issue.

I've disabled the rfkill trigger in the uefi and now plugging the eth cable does not cause the anymore that level of disruption.

However I've done some experiments and apparently I endup in a similar situation if I try to disable the wireless radio, for instance by using.

nmcli radio wifi off

when turning on the laptop (after a brutal poweroff) the interface appears to be off. So something seems to go wrong during the wifi radio turn off.

My laptop seems to have also a wwan radio (not sure if that is somehow a factor)..

Anyway I quickly scrolled the whole discussion but it wasn't clear to me in the end what piece of software is causing troubles.. is it NetworkManager fault or is it a kernel issue? is it likely that the issue will be fixed in the future?

seth · 2023-12-17 20:14:57

The iwlwifi behavior changed for the other user, it used to crash "worse" in response to the event, now it handles this a bit more gracefully, but that results in NM tripping over the error.

for instance by using.
nmcli radio wifi off
when turning on the laptop (after a brutal poweroff) the interface appears to be off.

* Avoid hard shutdowns.
* Is there a parallel windows installation?
* Can you please elaborate on that? If you're (soft) rfkill'ing the NIC (check rfkill) it'll of course be "off", that's the whole point?

Tvålen · 2024-04-18 17:34:24

I am experiencing essentially the same issue as the op. I have the same drivers, very similar output from journalctl, and the exact same behaviour as described in the first post of the thread.

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 0#p2136220
The problem is the wifi chip. You probably have a system where the rj45 plug acts as a hardware rfkill (ie. when you plug that, the uefi deactivates the wifi chip)
See whether you can disable that behavior in the UEFI (BIOS)
Alternatively, make dure to disconnect from the wifi (and ideally software rfkill it) before plugging the rj45 cable - the system should™ remain stable then.
If disabling the HW rfkill works, but you'd like to retain the functionality, see https://wiki.archlinux.org/title/Networ … plugged_in

This didn't work for me at all. "Wireless Auto Disconnection" as it's called in the lenovo bios is disabled and greyed out.
When i disconnect wifi manually it still hangs and then does a soft lockup (as opposed to the hard lock up that cunfusu got).

Only workaround that has worked for me is to poweroff/reboot and plug in the cable before booting.

(sorry if i break any rules this is the first time i'm engaging with the forum.)

seth · 2024-04-18 19:37:28

Since your symptoms are different and the confirmed approach to mitigate them doesn't work for you either, you're probably facing a different (maybe related) issue.
Please post your complete system journal for a boot covering the incident:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

for the running one and if it turns out to be a different problem you can report your post to be split off into a separate thread.

Arch Linux

#1 2023-12-16 17:06:22

[SOLVED] laptop freeze when plugging Ethernet cable

#2 2023-12-16 17:55:50

Re: [SOLVED] laptop freeze when plugging Ethernet cable

#3 2023-12-16 19:00:01

Re: [SOLVED] laptop freeze when plugging Ethernet cable

#4 2023-12-17 12:26:41

Re: [SOLVED] laptop freeze when plugging Ethernet cable

#5 2023-12-17 17:04:21

Re: [SOLVED] laptop freeze when plugging Ethernet cable

#6 2023-12-17 18:58:39

Re: [SOLVED] laptop freeze when plugging Ethernet cable

#7 2023-12-17 20:14:57

Re: [SOLVED] laptop freeze when plugging Ethernet cable

#8 2024-04-18 17:34:24

Re: [SOLVED] laptop freeze when plugging Ethernet cable

#9 2024-04-18 19:37:28

Re: [SOLVED] laptop freeze when plugging Ethernet cable

Board footer