[SOLVED] Weird network issues

salvo · 2024-12-24 18:13:10

I have a weird issue, my ethernet adapter stops working intermittently

I have a physical adapter connected to a cable and a wifi network connected at the same time. I am on : 6.6.67.1-lts

This is the network adapter coming online:

Dec 24 15:29:03 archsalvo kernel: igc 0000:0a:00.0 eno1: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

and then it dies

Dec 24 17:39:02 archsalvo kernel: igc 0000:0a:00.0 eno1: PCIe link lost, device now detached
Dec 24 17:39:02 archsalvo kernel: ------------[ cut here ]------------
Dec 24 17:39:02 archsalvo kernel: igc: Failed to read reg 0xc030!
Dec 24 17:39:02 archsalvo kernel: WARNING: CPU: 14 PID: 148 at drivers/net/ethernet/intel/igc/igc_main.c:6631 igc_rd32+0x86/0xa0 [igc]
Dec 24 17:39:02 archsalvo kernel: Modules linked in: ntfs3 btusb btrtl btintel btbcm btmtk bluetooth ecdh_generic snd_seq_dummy snd_hrtimer snd_seq mousedev joydev uinput nzxt_smart2 usbhid vfat fat intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd iwlmvm kvm irqbypass crct10dif_pclmul mac80211 crc32_pclmul polyval_clmulni polyval_gen>
Dec 24 17:39:02 archsalvo kernel:  fuse loop dm_mod nfnetlink zram bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme crc32c_intel nvme_core xhci_pci xhci_pci_renesas video nvme_common wmi
Dec 24 17:39:02 archsalvo kernel: CPU: 14 PID: 148 Comm: kworker/14:1 Tainted: P           OE      6.6.67-1-lts #1 3de9c5fc43f1a151bd6a367e4d9c9608713d9761
Dec 24 17:39:02 archsalvo kernel: Hardware name: ASUS System Product Name/ROG STRIX X670E-E GAMING WIFI, BIOS 2204 08/02/2024
Dec 24 17:39:02 archsalvo kernel: Workqueue: events igc_watchdog_task [igc]
Dec 24 17:39:02 archsalvo kernel: RIP: 0010:igc_rd32+0x86/0xa0 [igc]
Dec 24 17:39:02 archsalvo kernel: Code: e8 df 8a f9 e2 48 8b bb 28 ff ff ff e8 03 81 b7 e2 84 c0 75 07 b8 ff ff ff ff eb ac 89 ee 48 c7 c7 a0 29 5f c5 e8 ca b5 4e e2 <0f> 0b eb e7 b8 ff ff ff ff e9 b7 29 33 e3 66 66 2e 0f 1f 84 00 00
Dec 24 17:39:02 archsalvo kernel: RSP: 0018:ffffc90000657dc0 EFLAGS: 00010286
Dec 24 17:39:02 archsalvo kernel: RAX: 0000000000000000 RBX: ffff88811c4b4cb8 RCX: 0000000000000027
Dec 24 17:39:02 archsalvo kernel: RDX: ffff88903dfa1708 RSI: 0000000000000001 RDI: ffff88903dfa1700
Dec 24 17:39:02 archsalvo kernel: RBP: 000000000000c030 R08: 0000000000000000 R09: ffffc90000657c30
Dec 24 17:39:02 archsalvo kernel: R10: ffffffffa98b26c8 R11: 0000000000000003 R12: ffff88811c4b4000
Dec 24 17:39:02 archsalvo kernel: R13: 0000000000000000 R14: ffff888103293d40 R15: 000000000000c030
Dec 24 17:39:02 archsalvo kernel: FS:  0000000000000000(0000) GS:ffff88903df80000(0000) knlGS:0000000000000000
Dec 24 17:39:02 archsalvo kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 24 17:39:02 archsalvo kernel: CR2: 0000063406634000 CR3: 000000011c98c000 CR4: 0000000000f50ee0
Dec 24 17:39:02 archsalvo kernel: PKRU: 55555554
Dec 24 17:39:02 archsalvo kernel: Call Trace:
Dec 24 17:39:02 archsalvo kernel:  <TASK>
Dec 24 17:39:02 archsalvo kernel:  ? igc_rd32+0x86/0xa0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 24 17:39:02 archsalvo kernel:  ? __warn+0x81/0x130
Dec 24 17:39:02 archsalvo kernel:  ? igc_rd32+0x86/0xa0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 24 17:39:02 archsalvo kernel:  ? report_bug+0x16f/0x1a0
Dec 24 17:39:02 archsalvo kernel:  ? handle_bug+0x58/0x90
Dec 24 17:39:02 archsalvo kernel:  ? exc_invalid_op+0x17/0x70
Dec 24 17:39:02 archsalvo kernel:  ? asm_exc_invalid_op+0x1a/0x20
Dec 24 17:39:02 archsalvo kernel:  ? igc_rd32+0x86/0xa0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 24 17:39:02 archsalvo kernel:  igc_update_stats+0x8a/0x6d0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 24 17:39:02 archsalvo kernel:  igc_watchdog_task+0x9d/0x4a0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 24 17:39:02 archsalvo kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Dec 24 17:39:02 archsalvo kernel:  process_one_work+0x17d/0x350
Dec 24 17:39:02 archsalvo kernel:  worker_thread+0x315/0x450
Dec 24 17:39:02 archsalvo kernel:  ? __pfx_worker_thread+0x10/0x10
Dec 24 17:39:02 archsalvo kernel:  kthread+0xe5/0x120
Dec 24 17:39:02 archsalvo kernel:  ? __pfx_kthread+0x10/0x10
Dec 24 17:39:02 archsalvo kernel:  ret_from_fork+0x31/0x50
Dec 24 17:39:02 archsalvo kernel:  ? __pfx_kthread+0x10/0x10
Dec 24 17:39:02 archsalvo kernel:  ret_from_fork_asm+0x1b/0x30
Dec 24 17:39:02 archsalvo kernel:  </TASK>
Dec 24 17:39:02 archsalvo kernel: ---[ end trace 0000000000000000 ]---

I can switch wireless on and then I can connect, bu Gnome keeps pushing the messages that it is trying to connect the ethernet adapter.

I have tried a second network cable to a different port on my switch ( my sons PC that is on and working) and it works perfectly fine in Windows 11 and I used the same equipment when I was on NixOS and Nobara - with no issues. I am fairly certain its a hardware issue.

When I reboot its backto working again and no issues!

Thanks!

Last edited by salvo (2024-12-28 10:00:55)

Head_on_a_Stick · 2024-12-24 18:21:56

Check the firmware ("BIOS") options and disable PCIe ASPM support for that device (or globally).

If there is no such option try the pcie_port_pm=off kernel parameter: https://wiki.archlinux.org/title/Kernel_parameters

Top result in startpage.com when I entered "linux igc ethernet driver drops out" in the search box: https://www.reddit.com/r/buildapc/comme … i225v_igc/

Your search-fu is poor

salvo · 2024-12-24 18:39:39

Head_on_a_Stick wrote:

Check the firmware ("BIOS") options and disable PCIe ASPM support for that device (or globally).
If there is no such option try the pcie_port_pm=off kernel parameter: https://wiki.archlinux.org/title/Kernel_parameters
Top result in startpage.com when I entered "linux igc ethernet driver drops out" in the search box: https://www.reddit.com/r/buildapc/comme … i225v_igc/
Your search-fu is poor

Yeah, I was using ChatGPT

I have made the changes you recommended and will let you know what this looks like!

Thanks!

salvo · 2024-12-24 20:34:14

Well, the same thing happened. Any further ideas?

seth · 2024-12-24 21:00:57

Please post your complete system journal for the boot:

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

Resp. if you need to reboot to get your network back, "… -b -1 …" for the previous boot.
Also try "pcie_aspm=off"

salvo · 2024-12-26 09:43:18

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Resp. if you need to reboot to get your network back, "… -b -1 …" for the previous boot.
Also try "pcie_aspm=off"

Sorry for the late reply, and happy festive seasons greetings!

https://0x0.st/8rRK.txt

Its resolves itself after a reboot.

This is my /etc/default/grub file

https://0x0.st/8rRq.txt

Head_on_a_Stick · 2024-12-26 12:26:09

Best to check /proc/cmdline to see if the /etc/default/grub options are actually being applied.

seth · 2024-12-26 22:48:48

Dec 26 09:33:41 archsalvo kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=3e4aeb05-d80e-4eda-bd99-63676d2631c9 rw zswap.enabled=0 rootfstype=ext4 loglevel=3 quiet pcie_aspm=off pcie_port_pm=off

Dec 26 09:34:00 archsalvo NetworkManager[704]: <info>  [1735205640.6441] dhcp4 (eno1): state changed new lease, address=192.168.0.176
Dec 26 09:34:00 archsalvo NetworkManager[704]: <info>  [1735205640.6444] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Dec 26 09:34:00 archsalvo NetworkManager[704]: <info>  [1735205640.6784] device (eno1): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Dec 26 09:34:00 archsalvo NetworkManager[704]: <info>  [1735205640.6788] device (eno1): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Dec 26 09:34:00 archsalvo NetworkManager[704]: <info>  [1735205640.6789] device (eno1): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Dec 26 09:34:00 archsalvo NetworkManager[704]: <info>  [1735205640.6790] device (eno1): Activation: successful, device activated.
Dec 26 09:34:01 archsalvo wpa_supplicant[767]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=GB
Dec 26 09:34:01 archsalvo wpa_supplicant[767]: p2p-dev-wlan0: Channel list changed: 6 GHz was enabled
Dec 26 09:34:01 archsalvo wpa_supplicant[767]: wlan0: Channel list changed: 6 GHz was enabled
Dec 26 09:34:01 archsalvo wpa_supplicant[767]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=GB
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0432] device (wlan0): Activation: starting connection 'Morrigan_5G' (a0acb357-1f62-4d03-8dbc-c75a2e0acfcc)
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0433] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0754] device (wlan0): set-hw-addr: reset MAC address to BC:09:1B:10:51:A8 (preserve)
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0769] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0769] device (wlan0): Activation: (wifi) access point 'Morrigan_5G' has security, but secrets are required.
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0769] device (wlan0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0770] sup-iface[770e37ca144c7871,0,wlan0]: wps: type pbc start...
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0772] device (wlan0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0773] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.0774] device (wlan0): Activation: (wifi) connection 'Morrigan_5G' has security, and secrets exist.  No new secrets needed.
Dec 26 09:34:01 archsalvo wpa_supplicant[767]: wlan0: WPS-CANCEL
Dec 26 09:34:01 archsalvo wpa_supplicant[767]: wlan0: SME: Trying to authenticate with a8:42:a1:4c:75:10 (SSID='Morrigan_5G' freq=5200 MHz)
Dec 26 09:34:01 archsalvo kernel: wlan0: authenticate with a8:42:a1:4c:75:10
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.1092] device (wlan0): supplicant interface state: disconnected -> authenticating
…
Dec 26 09:34:01 archsalvo NetworkManager[704]: <info>  [1735205641.6208] dhcp4 (wlan0): state changed new lease, address=192.168.0.81

You're using wifi and ethernet at the same time and in the same subnet, your routerswitch device probably doesn't like that too much.
https://wiki.archlinux.org/title/Networ … plugged_in

salvo · 2024-12-27 09:11:29

Head_on_a_Stick wrote:

Best to check /proc/cmdline to see if the /etc/default/grub options are actually being applied.

09:08:41 salvo@archsalvo ~ → cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=3e4aeb05-d80e-4eda-bd99-63676d2631c9 rw zswap.enabled=0 rootfstype=ext4 loglevel=3 quiet pcie_aspm=off pcie_port_pm=off

salvo · 2024-12-27 09:17:51

You're using wifi and ethernet at the same time and in the same subnet, your routerswitch device probably doesn't like that too much.
https://wiki.archlinux.org/title/Networ … plugged_in

Thanks, I have implemented the script you pointed me to, and also manually disabled my Wifi - holding thumbs!!!

salvo · 2024-12-27 09:40:00

Ok, the ethernet went down again, and the script worked perfectly, once I did a

sudo nmcli device disconnect eno1

And this is the output of the journalctl command:

http://0x0.st/8sXF.txt

seth · 2024-12-27 09:49:45

That journal starts Dec 19th and is 212 MB, please post only the one for the relevant boot ("sudo journalctl -b -1" for the previous boot, "sudo journalctl -b" for the current one)

salvo · 2024-12-27 09:54:06

seth wrote:

That journal starts Dec 19th and is 212 MB, please post only the one for the relevant boot ("sudo journalctl -b -1" for the previous boot, "sudo journalctl -b" for the current one)

Previous boot: http://0x0.st/8s8-.txt
Current boot: http://0x0.st/8s8o.txt

seth · 2024-12-27 10:23:45

Back to square one:

Dec 27 09:16:07 archsalvo sudo[4924]:    salvo : TTY=pts/0 ; PWD=/home/salvo ; USER=root ; COMMAND=/usr/bin/nmcli device connect eno1
Dec 27 09:16:07 archsalvo NetworkManager[714]: <info>  [1735290967.7700] device (eno1): Activation: starting connection 'Wired connection 1' (3fdb9673-a85b-3e75-a744-885a7325414b)
Dec 27 09:16:07 archsalvo NetworkManager[714]: <info>  [1735290967.7701] device (eno1): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Dec 27 09:16:07 archsalvo NetworkManager[714]: <info>  [1735290967.7702] device (eno1): state change: prepare -> config (reason 'none', managed-type: 'full')
Dec 27 09:16:07 archsalvo NetworkManager[714]: <info>  [1735290967.7706] device (eno1): state change: config -> ip-config (reason 'none', managed-type: 'full')
Dec 27 09:16:07 archsalvo NetworkManager[714]: <info>  [1735290967.7707] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Dec 27 09:16:07 archsalvo NetworkManager[714]: <info>  [1735290967.7721] dhcp4 (eno1): state changed no lease
Dec 27 09:16:07 archsalvo NetworkManager[714]: <info>  [1735290967.7997] dhcp4 (eno1): state changed new lease, address=192.168.0.81, acd pending
Dec 27 09:16:08 archsalvo NetworkManager[714]: <info>  [1735290968.0075] dhcp4 (eno1): state changed new lease, address=192.168.0.81
…
Dec 27 09:16:08 archsalvo NetworkManager[714]: <info>  [1735290968.0440] device (eno1): Activation: successful, device activated.
Dec 27 09:16:08 archsalvo NetworkManager[714]: <info>  [1735290968.3727] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS

Then out of nowhere

Dec 27 09:36:21 archsalvo kernel: igc 0000:0a:00.0 eno1: PCIe link lost, device now detached
Dec 27 09:36:21 archsalvo kernel: ------------[ cut here ]------------
Dec 27 09:36:21 archsalvo kernel: igc: Failed to read reg 0xc030!
Dec 27 09:36:21 archsalvo kernel: WARNING: CPU: 3 PID: 416 at drivers/net/ethernet/intel/igc/igc_main.c:6631 igc_rd32+0x86/0xa0 [igc]
Dec 27 09:36:21 archsalvo kernel: Modules linked in: btusb btrtl btintel btbcm btmtk bluetooth ecdh_generic snd_seq_dummy snd_hrtimer snd_seq ccm uinput mousedev nzxt_smart2 joydev usbhid xpad ff_memless intel_rapl_msr intel_rapl_common edac_mce_amd kvm_amd kvm irqbypass iwlmvm crct10dif_pclmul vfat amdgpu crc32_pclmul fat polyval_clmulni polyval_generic gf128mul mac80211 snd_hda_codec_hdmi drm_exec ghash_clmulni_intel uvcvideo snd_usb_audio amdxcp sha512_ssse3 drm_buddy sha256_ssse3 snd_hda_intel videobuf2_vmalloc libarc4 gpu_sched snd_intel_dspcfg snd_usbmidi_lib uvc sha1_ssse3 i2c_algo_bit snd_intel_sdw_acpi videobuf2_memops snd_ump asus_nb_wmi aesni_intel eeepc_wmi drm_suballoc_helper videobuf2_v4l2 snd_hda_codec asus_wmi drm_ttm_helper snd_rawmidi crypto_simd iwlwifi videodev snd_hda_core ledtrig_audio cryptd snd_seq_device ttm snd_hwdep videobuf2_common sparse_keymap platform_profile mc drm_display_helper i8042 snd_pcm rapl nvidia_drm(POE) cfg80211 serio wmi_bmof cec pcspkr ccp k10temp snd_timer nvidia_modeset(POE) sp5100_tco snd
Dec 27 09:36:21 archsalvo kernel:  i2c_piix4 rfkill igc soundcore gpio_amdpt gpio_generic mac_hid pkcs8_key_parser nvidia_uvm(POE) nvidia(POE) crypto_user fuse dm_mod loop nfnetlink zram bpf_preload ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme crc32c_intel nvme_core xhci_pci xhci_pci_renesas nvme_common video wmi
Dec 27 09:36:21 archsalvo kernel: CPU: 3 PID: 416 Comm: kworker/3:2 Tainted: P           OE      6.6.67-1-lts #1 3de9c5fc43f1a151bd6a367e4d9c9608713d9761
Dec 27 09:36:21 archsalvo kernel: Hardware name: ASUS System Product Name/ROG STRIX X670E-E GAMING WIFI, BIOS 2204 08/02/2024
Dec 27 09:36:21 archsalvo kernel: Workqueue: events igc_watchdog_task [igc]
Dec 27 09:36:21 archsalvo kernel: RIP: 0010:igc_rd32+0x86/0xa0 [igc]
Dec 27 09:36:21 archsalvo kernel: Code: e8 df ca 03 df 48 8b bb 28 ff ff ff e8 03 c1 c1 de 84 c0 75 07 b8 ff ff ff ff eb ac 89 ee 48 c7 c7 a0 e9 f4 c4 e8 ca f5 58 de <0f> 0b eb e7 b8 ff ff ff ff e9 b7 69 3d df 66 66 2e 0f 1f 84 00 00
Dec 27 09:36:21 archsalvo kernel: RSP: 0018:ffffc90001fafdc0 EFLAGS: 00010286
Dec 27 09:36:21 archsalvo kernel: RAX: 0000000000000000 RBX: ffff88810bf4ccb8 RCX: 0000000000000027
Dec 27 09:36:21 archsalvo kernel: RDX: ffff88901e4e1708 RSI: 0000000000000001 RDI: ffff88901e4e1700
Dec 27 09:36:21 archsalvo kernel: RBP: 000000000000c030 R08: 0000000000000000 R09: ffffc90001fafc30
Dec 27 09:36:21 archsalvo kernel: R10: ffffffffa52b26c8 R11: 0000000000000003 R12: ffff88810bf4c000
Dec 27 09:36:21 archsalvo kernel: R13: 0000000000000000 R14: ffff88810d882d40 R15: 000000000000c030
Dec 27 09:36:21 archsalvo kernel: FS:  0000000000000000(0000) GS:ffff88901e4c0000(0000) knlGS:0000000000000000
Dec 27 09:36:21 archsalvo kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 27 09:36:21 archsalvo kernel: CR2: 00000e3400204000 CR3: 00000008e3220000 CR4: 0000000000f50ee0
Dec 27 09:36:21 archsalvo kernel: PKRU: 55555554
Dec 27 09:36:21 archsalvo kernel: Call Trace:
Dec 27 09:36:21 archsalvo kernel:  <TASK>
Dec 27 09:36:21 archsalvo kernel:  ? igc_rd32+0x86/0xa0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 27 09:36:21 archsalvo kernel:  ? __warn+0x81/0x130
Dec 27 09:36:21 archsalvo kernel:  ? igc_rd32+0x86/0xa0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 27 09:36:21 archsalvo kernel:  ? report_bug+0x16f/0x1a0
Dec 27 09:36:21 archsalvo kernel:  ? handle_bug+0x58/0x90
Dec 27 09:36:21 archsalvo kernel:  ? exc_invalid_op+0x17/0x70
Dec 27 09:36:21 archsalvo kernel:  ? asm_exc_invalid_op+0x1a/0x20
Dec 27 09:36:21 archsalvo kernel:  ? igc_rd32+0x86/0xa0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 27 09:36:21 archsalvo kernel:  igc_update_stats+0x8a/0x6d0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 27 09:36:21 archsalvo kernel:  igc_watchdog_task+0x9d/0x4a0 [igc 9a2595399dc231883891130f33d74a54cc37df52]
Dec 27 09:36:21 archsalvo kernel:  process_one_work+0x17d/0x350
Dec 27 09:36:21 archsalvo kernel:  worker_thread+0x315/0x450
Dec 27 09:36:21 archsalvo kernel:  ? __pfx_worker_thread+0x10/0x10
Dec 27 09:36:21 archsalvo kernel:  kthread+0xe5/0x120
Dec 27 09:36:21 archsalvo kernel:  ? __pfx_kthread+0x10/0x10
Dec 27 09:36:21 archsalvo kernel:  ret_from_fork+0x31/0x50
Dec 27 09:36:21 archsalvo kernel:  ? __pfx_kthread+0x10/0x10
Dec 27 09:36:21 archsalvo kernel:  ret_from_fork_asm+0x1b/0x30
Dec 27 09:36:21 archsalvo kernel:  </TASK>
Dec 27 09:36:21 archsalvo kernel: ---[ end trace 0000000000000000 ]---

Dec 27 08:49:34 archsalvo kernel: pci 0000:0a:00.0: PME# supported from D0 D3hot D3cold

Apparently not - but we also should™ completely have disabled aspm.

See whether you can throw the NIC a life-line and keep "ping google.com" running (you can also ping some LAN host, we just want to keep traffic on the NIC)
Then there's gsd-power… can you run the system on non-gnome (ideally something trivial) - I assume you're not running other powersaving tools?

Also, can you revive the NIC w/o a reboot

# echo 1 > /sys/bus/pci/rescan

salvo · 2024-12-27 10:31:40

seth wrote:

Back to square one:

Dec 27 09:16:07 archsalvo sudo[4924]:    salvo : TTY=pts/0 ; PWD=/home/salvo ; USER=root ; COMMAND=/usr/bin/nmcli device connect eno1

I initially did that to test that it was able to be disconnected and reconnect again, which it seemed like it was able to do perfectly, as it should/

Then out of nowhere
Dec 27 09:36:21 archsalvo kernel: igc 0000:0a:00.0 eno1: PCIe link lost, device now detached
...
Dec 27 09:36:21 archsalvo kernel: ---[ end trace 0000000000000000 ]---
Dec 27 08:49:34 archsalvo kernel: pci 0000:0a:00.0: PME# supported from D0 D3hot D3cold
Apparently not - but we also should™ completely have disabled aspm.
See whether you can throw the NIC a life-line and keep "ping google.com" running (you can also ping some LAN host, we just want to keep traffic on the NIC)
Then there's gsd-power… can you run the system on non-gnome (ideally something trivial) - I assume you're not running other powersaving tools?
Also, can you revive the NIC w/o a reboot
# echo 1 > /sys/bus/pci/rescan

10:26:20 salvo@archsalvo ~ → echo 1 > /sys/bus/pci/rescan
bash: /sys/bus/pci/rescan: cannot overwrite existing file
10:26:23 salvo@archsalvo ~ → sudo echo 1 > /sys/bus/pci/rescan
bash: /sys/bus/pci/rescan: cannot overwrite existing file
10:26:25 salvo@archsalvo ~ →

I am not running any powersaving tools whatsoever. I have Hyprland installed, will reboot and switch to that.

I also changed the network cable to a different port on the switch.

I'm currently running on WiFi, so a continuous ping will work, I'll try it when I am on Hyprland now and see if it works out.

seth · 2024-12-27 10:36:36

The "#" generally indicates "UID 0" but you sudo the wrong thing.

echo 1 | sudo tee /sys/bus/pci/rescan

I'm currently running on WiFi, so a continuous ping will work

The idea would be to run it while using the wired connection to see whether it can keep the chip on the bus by prohibiting any efforts to power itself down.

salvo · 2024-12-27 12:37:33

OK, been in Hyprland for over two hours now and doing a ping -i 5 192.168.0.187 and its not lost the network connection.

Going back to Gnome to see if its the same or different

seth · 2024-12-27 14:50:54

The last cross-test would be to see whether the ethernet remains stable on hyprland w/o the helping ping.
The latter might be a serviceable mitigation for the moment but is oc. anything but ideal - there're actually quite some hits for "igc" and "PCIe link lost, device now detached" - do you have any powersaving options in the UEFI/BIOS?

Edit: "igc.debug=16" might (cause a lot of spam in the journal, but also) help, https://wiki.archlinux.org/title/Kernel_parameters

Last edited by seth (2024-12-27 14:51:57)

salvo · 2024-12-27 15:58:49

seth wrote:

The last cross-test would be to see whether the ethernet remains stable on hyprland w/o the helping ping.
The latter might be a serviceable mitigation for the moment but is oc. anything but ideal - there're actually quite some hits for "igc" and "PCIe link lost, device now detached" - do you have any powersaving options in the UEFI/BIOS?
Edit: "igc.debug=16" might (cause a lot of spam in the journal, but also) help, https://wiki.archlinux.org/title/Kernel_parameters

It took about a very short amount of time before the Ethernet disappeared in Gnome.

I'm going to add the igc.debug=16 into the kernel and then reboot.

I turned all of the power saving options off in the BIOS, but will double check once I have made the kernel changes and rebooted.

seth · 2024-12-27 16:08:42

It took about a very short amount of time before the Ethernet disappeared in Gnome.

Despite the ping life-line?
And the connection is stable in hyprland? (Even w/o the ping?)
Do you overclock CPU or GPU? Does gnome use considerably more RAM than your hyprland session?

salvo · 2024-12-27 16:13:53

seth wrote:

It took about a very short amount of time before the Ethernet disappeared in Gnome.
Despite the ping life-line?
And the connection is stable in hyprland? (Even w/o the ping?)
Do you overclock CPU or GPU? Does gnome use considerably more RAM than your hyprland session?

Yeah, I'm going it again now with the kernel changes you recommended.

04:08:32 salvo@archsalvo ~ → cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=3e4aeb05-d80e-4eda-bd99-63676d2631c9 rw zswap.enabled=0 rootfstype=ext4 loglevel=3 quiet pcie_aspm=off pcie_port_pm=off igc.debug=16

I also double checked that there is no power saving on in the BIOS, and no I am not over clocking the CPU, not the GPU.

I haven't checked whether the connection is stable in Hyprland without the ping check, if this Gnome session's Ethernet fails, I will do the Hyprland test without the ping-test.

Thanks for all of your help!!

salvo · 2024-12-28 06:05:05

Well, its been a while since the last update here and things seem to be stable. I have no idea what could have caused it to become stable, but I am holding thumbs it will remain that way.

Thanks for all of the help!!

I'm going to leave it for a few more hours and see if it remains stable.

seth · 2024-12-28 07:47:24

It's windows:

Dec 26 10:26:28 archsalvo kernel: ntfs3: Enabled Linux POSIX ACLs support
Dec 26 10:26:28 archsalvo kernel: ntfs3: Read-only LZX/Xpress compression included
Dec 26 09:33:41 archsalvo kernel:  nvme1n1: p1 p2 p3 p4 p5
Dec 26 09:33:41 archsalvo kernel:  nvme0n1: p1 p2 p3 p4

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

salvo · 2024-12-28 09:57:39

seth wrote:

It's windows:
Dec 26 10:26:28 archsalvo kernel: ntfs3: Enabled Linux POSIX ACLs support
Dec 26 10:26:28 archsalvo kernel: ntfs3: Read-only LZX/Xpress compression included
Dec 26 09:33:41 archsalvo kernel:  nvme1n1: p1 p2 p3 p4 p5
Dec 26 09:33:41 archsalvo kernel:  nvme0n1: p1 p2 p3 p4
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Thank you for the help! I have done what was in the article you liked and will mark this as resolved.

Arch Linux

#1 2024-12-24 18:13:10

[SOLVED] Weird network issues

#2 2024-12-24 18:21:56

Re: [SOLVED] Weird network issues

#3 2024-12-24 18:39:39

Re: [SOLVED] Weird network issues

#4 2024-12-24 20:34:14

Re: [SOLVED] Weird network issues

#5 2024-12-24 21:00:57

Re: [SOLVED] Weird network issues

#6 2024-12-26 09:43:18

Re: [SOLVED] Weird network issues

#7 2024-12-26 12:26:09

Re: [SOLVED] Weird network issues

#8 2024-12-26 22:48:48

Re: [SOLVED] Weird network issues

#9 2024-12-27 09:11:29

Re: [SOLVED] Weird network issues

#10 2024-12-27 09:17:51

Re: [SOLVED] Weird network issues

#11 2024-12-27 09:40:00

Re: [SOLVED] Weird network issues

#12 2024-12-27 09:49:45

Re: [SOLVED] Weird network issues

#13 2024-12-27 09:54:06

Re: [SOLVED] Weird network issues

#14 2024-12-27 10:23:45

Re: [SOLVED] Weird network issues

#15 2024-12-27 10:31:40

Re: [SOLVED] Weird network issues

#16 2024-12-27 10:36:36

Re: [SOLVED] Weird network issues

#17 2024-12-27 12:37:33

Re: [SOLVED] Weird network issues

#18 2024-12-27 14:50:54

Re: [SOLVED] Weird network issues

#19 2024-12-27 15:58:49

Re: [SOLVED] Weird network issues

#20 2024-12-27 16:08:42

Re: [SOLVED] Weird network issues

#21 2024-12-27 16:13:53

Re: [SOLVED] Weird network issues

#22 2024-12-28 06:05:05

Re: [SOLVED] Weird network issues

#23 2024-12-28 07:47:24

Re: [SOLVED] Weird network issues

#24 2024-12-28 09:57:39

Re: [SOLVED] Weird network issues

Board footer