You are not logged in.

#1 2021-06-19 09:50:45

7thSon
Member
Registered: 2017-05-07
Posts: 186

[SOLVED] Network suddenly disconnects (Dell XPS laptop)

I have an issue on a Dell XPS 15 laptop where the network connection suddenly disconnects.

What I've found is that after 5-10 minutes after logging into the desktop and working on it, the network suddenly fails, so that when I ping 8.8.8.8 for instance the responce is "Destination Host Unreachable".
I switched from NetworkManager to dhcpcd, but I'm having the exact same problem with both.
Checking the logs for dhcpcd I found that it said "DCHP lease expired" and then "No ipv6 routes".
After suffering the disconnect I checked `ip route` and there were no routes anymore.

Any idea what could cause this behavior? I haven't changed any settings for neither NetworkManager or dhcpcd.
Could this have anything to do with my home router hardware? I have an ASUS RT-AC66U which is about 7 years old.
What should I check to further investigate?

Last edited by 7thSon (2021-07-02 08:25:43)

Offline

#2 2021-06-19 11:21:17

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,435

Re: [SOLVED] Network suddenly disconnects (Dell XPS laptop)

Any idea what could cause this behavior? I

Yes, something is broken…

Post your system journal, we can't guess what the problem is out of thin air.
The dhcp client would typically try to update the lease before it expires and "no ipv6 routes" is only relevant if you expect to have one.

Offline

#3 2021-06-19 14:47:08

7thSon
Member
Registered: 2017-05-07
Posts: 186

Re: [SOLVED] Network suddenly disconnects (Dell XPS laptop)

Here are the logs from journalctl, from boot until just after the network issue happens.

https://hastebin.com/raw/nupeyuquku

Offline

#4 2021-06-19 15:07:42

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,435

Re: [SOLVED] Network suddenly disconnects (Dell XPS laptop)

There's an unstable carrier

Jun 19 16:29:54 arch dhcpcd[758]: enp0s20f0u1u3: carrier lost
Jun 19 16:29:54 arch avahi-daemon[747]: Leaving mDNS multicast group on interface enp0s20f0u1u3.IPv6 with address fe80::b67a:16bb:1226:8de7.
Jun 19 16:29:54 arch avahi-daemon[747]: Interface enp0s20f0u1u3.IPv4 no longer relevant for mDNS.
Jun 19 16:29:54 arch avahi-daemon[747]: Leaving mDNS multicast group on interface enp0s20f0u1u3.IPv4 with address 192.168.1.81.
Jun 19 16:29:54 arch avahi-daemon[747]: Withdrawing address record for fe80::b67a:16bb:1226:8de7 on enp0s20f0u1u3.
Jun 19 16:29:54 arch avahi-daemon[747]: Withdrawing address record for 192.168.1.81 on enp0s20f0u1u3.
Jun 19 16:29:54 arch dhcpcd[758]: enp0s20f0u1u3: deleting address fe80::b67a:16bb:1226:8de7
Jun 19 16:29:54 arch dhcpcd[758]: enp0s20f0u1u3: deleting route to 192.168.1.0/24
Jun 19 16:29:54 arch dhcpcd[758]: enp0s20f0u1u3: deleting default route via 192.168.1.1
Jun 19 16:29:54 arch kernel: usb 2-1.3: device firmware changed
Jun 19 16:29:54 arch kernel: r8152 2-1.3:1.0 enp0s20f0u1u3: Using pass-thru MAC addr 38:14:28:a8:0e:f4
Jun 19 16:29:54 arch kernel: usb 2-1.3: USB disconnect, device number 3
Jun 19 16:29:54 arch avahi-daemon[747]: Got SIGHUP, reloading.
Jun 19 16:29:54 arch avahi-daemon[747]: No service file found in /etc/avahi/services.
Jun 19 16:29:55 arch kernel: usb 2-1.3: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
Jun 19 16:29:55 arch kernel: usb 2-1.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
Jun 19 16:29:55 arch kernel: usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Jun 19 16:29:55 arch kernel: usb 2-1.3: Product: USB 10/100/1000 LAN
Jun 19 16:29:55 arch kernel: usb 2-1.3: Manufacturer: Realtek
Jun 19 16:29:55 arch kernel: usb 2-1.3: SerialNumber: 000001
Jun 19 16:29:55 arch kernel: usb 2-1.3: reset SuperSpeed Gen 1 USB device number 4 using xhci_hcd
Jun 19 16:29:55 arch kernel: r8152 2-1.3:1.0: load rtl8153a-4 v2 02/07/20 successfully
Jun 19 16:29:55 arch upowerd[1359]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3
Jun 19 16:29:55 arch dhcpcd[758]: enp0s20f0u1u3: removing interface
Jun 19 16:29:55 arch kernel: r8152 2-1.3:1.0 eth0: v1.11.11
Jun 19 16:29:55 arch mtp-probe[3824]: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3"
Jun 19 16:29:55 arch mtp-probe[3824]: bus: 2, device: 4 was not an MTP device
Jun 19 16:29:56 arch upowerd[1359]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3
Jun 19 16:29:56 arch mtp-probe[3851]: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3"
Jun 19 16:29:56 arch mtp-probe[3851]: bus: 2, device: 4 was not an MTP device
Jun 19 16:29:56 arch upowerd[1359]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3
Jun 19 16:29:56 arch upowerd[1359]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3
Jun 19 16:29:56 arch upowerd[1359]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3
Jun 19 16:29:56 arch upowerd[1359]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3
Jun 19 16:29:56 arch systemd-udevd[3821]: Using default interface naming scheme 'v247'.
Jun 19 16:29:56 arch systemd-udevd[3821]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 19 16:29:56 arch kernel: r8152 2-1.3:1.0 enp0s20f0u1u3: renamed from eth0
Jun 19 16:29:56 arch systemd-udevd[3776]: Using default interface naming scheme 'v247'.
Jun 19 16:29:56 arch systemd-udevd[3776]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 19 16:29:56 arch dhcpcd[758]: enp0s20f0u1u3: waiting for carrier
Jun 19 16:29:56 arch dhcpcd[758]: enp0s20f0u1u3: carrier acquired
Jun 19 16:29:56 arch dhcpcd[758]: enp0s20f0u1u3: IAID c8:e7:5f:a4
Jun 19 16:29:56 arch dhcpcd[758]: enp0s20f0u1u3: adding address fe80::b67a:16bb:1226:8de7
Jun 19 16:29:56 arch avahi-daemon[747]: Joining mDNS multicast group on interface enp0s20f0u1u3.IPv6 with address fe80::b67a:16bb:1226:8de7.
Jun 19 16:29:56 arch avahi-daemon[747]: New relevant interface enp0s20f0u1u3.IPv6 for mDNS.
Jun 19 16:29:56 arch dhcpcd[758]: enp0s20f0u1u3: carrier lost
Jun 19 16:29:56 arch avahi-daemon[747]: Registering new address record for fe80::b67a:16bb:1226:8de7 on enp0s20f0u1u3.*.
Jun 19 16:29:56 arch dhcpcd[758]: enp0s20f0u1u3: deleting address fe80::b67a:16bb:1226:8de7
Jun 19 16:29:56 arch avahi-daemon[747]: Withdrawing address record for fe80::b67a:16bb:1226:8de7 on enp0s20f0u1u3.
Jun 19 16:29:56 arch avahi-daemon[747]: Leaving mDNS multicast group on interface enp0s20f0u1u3.IPv6 with address fe80::b67a:16bb:1226:8de7.
Jun 19 16:29:56 arch avahi-daemon[747]: Interface enp0s20f0u1u3.IPv6 no longer relevant for mDNS.
Jun 19 16:29:56 arch dhcpcd[758]: enp0s20f0u1u3: waiting for carrier
Jun 19 16:29:59 arch dhcpcd[758]: enp0s20f0u1u3: carrier acquired

and ultimately a crash in the module

Jun 19 16:36:26 arch upowerd[1359]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1.3
Jun 19 16:36:39 arch kernel: INFO: task kworker/2:0:26 blocked for more than 122 seconds.
Jun 19 16:36:39 arch kernel:       Tainted: G        W         5.10.44-1-lts #1
Jun 19 16:36:39 arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 19 16:36:39 arch kernel: task:kworker/2:0     state:D stack:    0 pid:   26 ppid:     2 flags:0x00004000
Jun 19 16:36:39 arch kernel: Workqueue: usb_hub_wq hub_event
Jun 19 16:36:39 arch kernel: Call Trace:
Jun 19 16:36:39 arch kernel:  __schedule+0x285/0x7e0
Jun 19 16:36:39 arch kernel:  schedule+0x46/0xb0
Jun 19 16:36:39 arch kernel:  rpm_resume+0x16d/0x7a0
Jun 19 16:36:39 arch kernel:  ? wait_woken+0x80/0x80
Jun 19 16:36:39 arch kernel:  rpm_resume+0x314/0x7a0
Jun 19 16:36:39 arch kernel:  __pm_runtime_resume+0x3b/0x60
Jun 19 16:36:39 arch kernel:  usb_autopm_get_interface+0x18/0x40
Jun 19 16:36:39 arch kernel:  rtl8152_set_mac_address+0x50/0x1b0 [r8152]
Jun 19 16:36:39 arch kernel:  set_ethernet_addr.isra.0+0x72/0x80 [r8152]
Jun 19 16:36:39 arch kernel:  rtl8152_reset_resume+0x48/0x60 [r8152]
Jun 19 16:36:39 arch kernel:  usb_resume_interface.part.0.isra.0+0x3a/0xb0
Jun 19 16:36:39 arch kernel:  usb_resume_both+0xf1/0x170
Jun 19 16:36:39 arch kernel:  ? usb_runtime_suspend+0x70/0x70
Jun 19 16:36:39 arch kernel:  __rpm_callback+0x81/0x140
Jun 19 16:36:39 arch kernel:  rpm_callback+0x4f/0x70
Jun 19 16:36:39 arch kernel:  ? usb_runtime_suspend+0x70/0x70
Jun 19 16:36:39 arch kernel:  rpm_resume+0x502/0x7a0
Jun 19 16:36:39 arch kernel:  ? kfree+0xc3/0x480
Jun 19 16:36:39 arch kernel:  ? usb_start_wait_urb+0xa2/0x160
Jun 19 16:36:39 arch kernel:  ? usb_control_msg+0xfd/0x140
Jun 19 16:36:39 arch kernel:  __pm_runtime_resume+0x3b/0x60
Jun 19 16:36:39 arch kernel:  usb_autoresume_device+0x1b/0x50
Jun 19 16:36:39 arch kernel:  usb_reset_device+0x9b/0x250
Jun 19 16:36:39 arch kernel:  hub_event+0xe2a/0x1760
Jun 19 16:36:39 arch kernel:  ? vc_boot_ghcb+0x45/0x74
Jun 19 16:36:39 arch kernel:  ? __switch_to+0x11b/0x460
Jun 19 16:36:39 arch kernel:  ? __schedule+0x28d/0x7e0
Jun 19 16:36:39 arch kernel:  process_one_work+0x1df/0x370
Jun 19 16:36:39 arch kernel:  worker_thread+0x50/0x400
Jun 19 16:36:39 arch kernel:  ? process_one_work+0x370/0x370
Jun 19 16:36:39 arch kernel:  kthread+0x11b/0x140
Jun 19 16:36:39 arch kernel:  ? kthread_associate_blkcg+0xa0/0xa0
Jun 19 16:36:39 arch kernel:  ret_from_fork+0x1f/0x30
Jun 19 16:36:39 arch kernel: INFO: task kworker/2:1:155 blocked for more than 122 seconds.
Jun 19 16:36:39 arch kernel:       Tainted: G        W         5.10.44-1-lts #1
Jun 19 16:36:39 arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 19 16:36:39 arch kernel: task:kworker/2:1     state:D stack:    0 pid:  155 ppid:     2 flags:0x00004000
Jun 19 16:36:39 arch kernel: Workqueue: usb_hub_wq hub_event
Jun 19 16:36:39 arch kernel: Call Trace:
Jun 19 16:36:39 arch kernel:  __schedule+0x285/0x7e0
Jun 19 16:36:39 arch kernel:  schedule+0x46/0xb0
Jun 19 16:36:39 arch kernel:  schedule_preempt_disabled+0xa/0x10
Jun 19 16:36:39 arch kernel:  __mutex_lock.constprop.0+0x158/0x4f0
Jun 19 16:36:39 arch kernel:  ? wake_up_q+0x5b/0xa0
Jun 19 16:36:39 arch kernel:  usb_remote_wakeup+0x1f/0x80
Jun 19 16:36:39 arch kernel:  hub_event+0x4b4/0x1760
Jun 19 16:36:39 arch kernel:  ? verify_cpu+0xf3/0x100
Jun 19 16:36:39 arch kernel:  ? __schedule+0x28d/0x7e0
Jun 19 16:36:39 arch kernel:  process_one_work+0x1df/0x370
Jun 19 16:36:39 arch kernel:  worker_thread+0x50/0x400
Jun 19 16:36:39 arch kernel:  ? process_one_work+0x370/0x370
Jun 19 16:36:39 arch kernel:  kthread+0x11b/0x140
Jun 19 16:36:39 arch kernel:  ? kthread_associate_blkcg+0xa0/0xa0
Jun 19 16:36:39 arch kernel:  ret_from_fork+0x1f/0x30
Jun 19 16:36:39 arch kernel: INFO: task kworker/2:3:4328 blocked for more than 122 seconds.
Jun 19 16:36:39 arch kernel:       Tainted: G        W         5.10.44-1-lts #1
Jun 19 16:36:39 arch kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 19 16:36:39 arch kernel: task:kworker/2:3     state:D stack:    0 pid: 4328 ppid:     2 flags:0x00004080
Jun 19 16:36:39 arch kernel: Workqueue: events_long rtl_hw_phy_work_func_t [r8152]
Jun 19 16:36:39 arch kernel: Call Trace:
Jun 19 16:36:39 arch kernel:  __schedule+0x285/0x7e0
Jun 19 16:36:39 arch kernel:  schedule+0x46/0xb0
Jun 19 16:36:39 arch kernel:  rpm_resume+0x16d/0x7a0
Jun 19 16:36:39 arch kernel:  ? wait_woken+0x80/0x80
Jun 19 16:36:39 arch kernel:  rpm_resume+0x314/0x7a0
Jun 19 16:36:39 arch kernel:  __pm_runtime_resume+0x3b/0x60
Jun 19 16:36:39 arch kernel:  usb_autopm_get_interface+0x18/0x40
Jun 19 16:36:39 arch kernel:  rtl_hw_phy_work_func_t+0x5e/0x5a0 [r8152]
Jun 19 16:36:39 arch kernel:  ? __switch_to_asm+0x42/0x70
Jun 19 16:36:39 arch kernel:  ? __switch_to+0x11b/0x460
Jun 19 16:36:39 arch kernel:  ? __schedule+0x28d/0x7e0
Jun 19 16:36:39 arch kernel:  process_one_work+0x1df/0x370
Jun 19 16:36:39 arch kernel:  worker_thread+0x50/0x400
Jun 19 16:36:39 arch kernel:  ? process_one_work+0x370/0x370
Jun 19 16:36:39 arch kernel:  kthread+0x11b/0x140
Jun 19 16:36:39 arch kernel:  ? kthread_associate_blkcg+0xa0/0xa0
Jun 19 16:36:39 arch kernel:  ret_from_fork+0x1f/0x30

1. Cable
2. Cable
3. Cable
4. Plugs are part of the cable
5. On both ends

Offline

#5 2021-06-20 14:28:15

7thSon
Member
Registered: 2017-05-07
Posts: 186

Re: [SOLVED] Network suddenly disconnects (Dell XPS laptop)

seth wrote:

There's an unstable carrier
1. Cable
2. Cable
3. Cable
4. Plugs are part of the cable
5. On both ends

I have now replaced the previous cable with another one, and I'm still getting the carrier error messages in the log.
I'm thinking it's pretty unlikely (though not impossible) that two separate cables are faulty.
Could this be caused by my router somehow? I saw that I have these carrier errors on my desktop computer as well (using the same initial cable as for the laptop in question) , though I haven't experienced this kind of network breakage on that machine.

Last edited by 7thSon (2021-06-20 14:33:54)

Offline

#6 2021-06-20 14:35:04

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 77,435

Re: [SOLVED] Network suddenly disconnects (Dell XPS laptop)

Could this be caused by my router somehow?

Yes. The carrier is a low-level signal between the two NICs

It's not necessarily the (direct) cause of the kernel crash, but whenever you lose the carrier, the network technically "disconnects" (though it's re-established quickly)

Another thing to look into and because of the particular backtrace is https://wiki.archlinux.org/title/Power_ … utosuspend

usbcore.autosuspend=-1

disables it.
nb. that userspace dameons like TLP etc. can and will change that value at runtime, so if you use anything like that, configure it to disable usb autosuspension.
(The theory here is a reversion of cause and effect - the autosuspend causes the carrier drops and is also eventually responsible for the module crash)

Offline

#7 2021-07-02 08:25:25

7thSon
Member
Registered: 2017-05-07
Posts: 186

Re: [SOLVED] Network suddenly disconnects (Dell XPS laptop)

Okay, I have updated my router to some new gear from Ubiquiti and replaced all cables with new ones.
The carrier lost errors have stopped, so I will mark this as solvec.

Offline

Board footer

Powered by FluxBB