[SOLVED]USB Tethering - How to disconnect?

unnilquadium · 2024-09-06 12:18:45

I use the USB tethering function on my mobile phone (android) with NetworkManager.

It works fine, but when I disconnect the phone the computer hangs after a while.

I believe it thinks that the network is still connected because it's still shows as available in NetworkManager.
I've tried disconnecting the network and switching tethering off before unplugging the phone, but the network remains as "available" and the PC still hangs if I try to switch it off or restart.

So my question is:

What is the proper way to disconnect USB tethering?

Thank you!

Last edited by unnilquadium (2024-09-11 06:23:34)

seth · 2024-09-06 13:11:48

Do you disable tethering in the phone before you yank the cable?
What's the output of "ip a" after "disconnecting" the phone?

unnilquadium · 2024-09-07 15:40:05

seth wrote:

Do you disable tethering in the phone before you yank the cable?

Yes, I select "USB for charging only" on the phone.

seth wrote:

What's the output of "ip a" after "disconnecting" the phone?

I'm unable to post the output of said command. It hangs.
I think NetworkManager never assumes that the network was disconnected.

seth · 2024-09-07 15:46:06

That's not an NM problem - reboot, tether, run "dmesg -w", disconnect the tethering device and post the dmesg output that generated.

unnilquadium · 2024-09-08 04:32:05

output of "dmesg -w"

[    6.550924] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input20
[    6.721148] Bluetooth: hci0: BCM: features 0x07
[    6.737275] Bluetooth: hci0: Broadcom Bluetooth Device
[    6.737293] Bluetooth: hci0: BCM20702A0 (001.001.024) build 0204
[    6.810108] Bluetooth: MGMT ver 1.22
[    6.838847] NET: Registered PF_ALG protocol family
[    7.317227] Console: switching to colour frame buffer device 160x50
[    7.336573] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[   10.691799] iwlwifi 0000:0a:00.0: Radio type=0x1-0x2-0x0
[   10.987280] iwlwifi 0000:0a:00.0: Radio type=0x1-0x2-0x0
[   11.106803] wlp10s0: authenticate with 40:b0:76:39:20:5c (local address=10:0b:a9:20:b5:60)
[   11.106827] wlp10s0: send auth to 40:b0:76:39:20:5c (try 1/3)
[   11.177322] wlp10s0: authenticated
[   11.177783] wlp10s0: associate with 40:b0:76:39:20:5c (try 1/3)
[   11.178885] wlp10s0: RX AssocResp from 40:b0:76:39:20:5c (capab=0x1011 status=0 aid=3)
[   11.181196] wlp10s0: associated
[   11.279227] wlp10s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 40:b0:76:39:20:5c
[   14.336308] Bluetooth: RFCOMM TTY layer initialized
[   14.336321] Bluetooth: RFCOMM socket layer initialized
[   14.336326] Bluetooth: RFCOMM ver 1.11
[   24.380024] wlp10s0: deauthenticating from 40:b0:76:39:20:5c by local choice (Reason: 3=DEAUTH_LEAVING)
[   24.526040] iwlwifi 0000:0a:00.0: Radio type=0x1-0x2-0x0
[   24.829657] iwlwifi 0000:0a:00.0: Radio type=0x1-0x2-0x0
[   77.511220] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[   77.634737] usb 3-1: device descriptor read/64, error -32
[   77.884945] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e82, bcdDevice= 4.04
[   77.884967] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   77.884975] usb 3-1: Product: moto g13
[   77.884979] usb 3-1: Manufacturer: motorola
[   77.884984] usb 3-1: SerialNumber: ZY22GRRSZL
[   86.507985] usb 3-1: USB disconnect, device number 2
[  125.137875] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[  125.261332] usb 3-1: device descriptor read/64, error -32
[  125.511502] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e82, bcdDevice= 4.04
[  125.511523] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  125.511530] usb 3-1: Product: moto g13
[  125.511535] usb 3-1: Manufacturer: motorola
[  125.511540] usb 3-1: SerialNumber: ZY22GRRSZL
[  138.328657] usb 3-1: reset high-speed USB device number 3 using xhci_hcd
[  138.468878] usb 3-1: device firmware changed
[  138.469013] usb 3-1: USB disconnect, device number 3
[  138.591212] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[  138.735433] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e24, bcdDevice= 4.04
[  138.735459] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  138.735462] usb 3-1: Product: moto g13
[  138.735463] usb 3-1: Manufacturer: motorola
[  138.735464] usb 3-1: SerialNumber: ZY22GRRSZL
[  139.370281] usbcore: registered new interface driver cdc_ether
[  139.380545] rndis_host 3-1:1.0 usb0: register 'rndis_host' at usb-0000:0b:00.0-1, RNDIS device, d2:67:a9:56:4a:6d
[  139.380599] usbcore: registered new interface driver rndis_host
[  139.388481] rndis_host 3-1:1.0 enp11s0u1: renamed from usb0
[  195.883636] usb 3-1: USB disconnect, device number 4
[  195.884257] rndis_host 3-1:1.0 enp11s0u1: unregister 'rndis_host' usb-0000:0b:00.0-1, RNDIS device

Could only get those last lines before it hung.

seth · 2024-09-08 06:19:39

[   77.511220] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[   77.634737] usb 3-1: device descriptor read/64, error -32
[   77.884945] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e82, bcdDevice= 4.04
[   77.884967] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   77.884975] usb 3-1: Product: moto g13
[   77.884979] usb 3-1: Manufacturer: motorola
[   77.884984] usb 3-1: SerialNumber: ZY22GRRSZL
[   86.507985] usb 3-1: USB disconnect, device number 2

So the phone shows up w/ a broken pipe (cut data transfer) and disconnects 9s later

[  125.137875] usb 3-1: new high-speed USB device number 3 using xhci_hcd
[  125.261332] usb 3-1: device descriptor read/64, error -32
[  125.511502] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e82, bcdDevice= 4.04
[  125.511523] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  125.511530] usb 3-1: Product: moto g13
[  125.511535] usb 3-1: Manufacturer: motorola
[  125.511540] usb 3-1: SerialNumber: ZY22GRRSZL

then ~40s later again shows up again w/ a broken pipe error

[  138.328657] usb 3-1: reset high-speed USB device number 3 using xhci_hcd
[  138.468878] usb 3-1: device firmware changed
[  138.469013] usb 3-1: USB disconnect, device number 3
[  138.591212] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[  138.735433] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e24, bcdDevice= 4.04
[  138.735459] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  138.735462] usb 3-1: Product: moto g13
[  138.735463] usb 3-1: Manufacturer: motorola
[  138.735464] usb 3-1: SerialNumber: ZY22GRRSZL
[  139.370281] usbcore: registered new interface driver cdc_ether

12s later resets, dis- and reconnects and finally you're getting a CDC device (I assume the reset is response to you activating the twthering mode?)

[  195.883636] usb 3-1: USB disconnect, device number 4
[  195.884257] rndis_host 3-1:1.0 enp11s0u1: unregister 'rndis_host' usb-0000:0b:00.0-1, RNDIS device

Then the dmesg ends w/ the device disconnecting and *then* removes the rndis_host - did you not disable the tethering modein the phone before yanking the cable?

Speaking of which and because the EPIPE: do you have another cable?

unnilquadium · 2024-09-08 21:43:13

seth wrote:

did you not disable the tethering modein the phone before yanking the cable?

Tethering mode was disabled before removing the cable.

seth wrote:

do you have another cable?

Tried with another cable - same result

When tethering is deselected on the phone, the following output is produced:

[  195.883636] usb 3-1: USB disconnect, device number 4
[  195.884257] rndis_host 3-1:1.0 enp11s0u1: unregister 'rndis_host' usb-0000:0b:00.0-1, RNDIS device

and NetworkManager keeps the network listed after that.

If I disconnect from the tethering on NetworkManager before removing the phone, it disconnects but the network remains listed as available even if I disable tethering. In that case, the PC hangs when shutting down.

P.S.:
At this point I think I'll just live with this mild annoyance.
At first I thought that many more people would be having the same problem, but this must be one of kind PC / phone weirdness.
It's not justifiable for anyone to lose much more time with this.
I thank you anyway for giving this some attention.

seth · 2024-09-09 06:00:11

If I disconnect from the tethering on NetworkManager before removing the phone, it disconnects but the network remains listed as available even if I disable tethering. In that case, the PC hangs when shutting down.

Do you have a journal for that as well?
You're losing the host but somehow the NIC device doesn't seem to get removed?

Most people will likely only tether when there's an issue w/ their network stack anyway and to fix that.
If I don't forget get it, I'll try here what happens - but now you scared me

Since you seem to be using this on a regular base, did you add any udev rules? Is there maybe a second network managing daemon?

unnilquadium · 2024-09-09 12:24:29

seth wrote:

Do you have a journal for that as well?

Link to journal here.

For convenience, I'll leave here the most relevant lines starting at phone connection:

Sep 09 12:54:48 sandy kernel: usb 3-1: new high-speed USB device number 2 using xhci_hcd
Sep 09 12:54:49 sandy kernel: usb 3-1: device descriptor read/64, error -32
Sep 09 12:54:49 sandy kernel: usb 3-1: New USB device found, idVendor=22b8, idProduct=2e82, bcdDevice= 4.04
Sep 09 12:54:49 sandy kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 09 12:54:49 sandy kernel: usb 3-1: Product: moto g13
Sep 09 12:54:49 sandy kernel: usb 3-1: Manufacturer: motorola
Sep 09 12:54:49 sandy kernel: usb 3-1: SerialNumber: ZY22GRRSZL
Sep 09 12:54:55 sandy kernel: usb 3-1: USB disconnect, device number 2
Sep 09 12:54:57 sandy kernel: usb 3-1: new high-speed USB device number 3 using xhci_hcd
Sep 09 12:54:57 sandy kernel: usb 3-1: New USB device found, idVendor=22b8, idProduct=2e24, bcdDevice= 4.04
Sep 09 12:54:57 sandy kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 09 12:54:57 sandy kernel: usb 3-1: Product: moto g13
Sep 09 12:54:57 sandy kernel: usb 3-1: Manufacturer: motorola
Sep 09 12:54:57 sandy kernel: usb 3-1: SerialNumber: ZY22GRRSZL
Sep 09 12:54:57 sandy kernel: usbcore: registered new interface driver cdc_ether
Sep 09 12:54:57 sandy kernel: rndis_host 3-1:1.0 usb0: register 'rndis_host' at usb-0000:0b:00.0-1, RNDIS device, d2:67:a9:56:4a:6d
Sep 09 12:54:57 sandy kernel: usbcore: registered new interface driver rndis_host
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8398] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Sep 09 12:54:57 sandy kernel: rndis_host 3-1:1.0 enp11s0u1: renamed from usb0
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8464] device (usb0): interface index 4 renamed iface from 'usb0' to 'enp11s0u1'
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8527] device (enp11s0u1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8557] settings: (enp11s0u1): created default wired connection 'Wired connection 2'
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8561] device (enp11s0u1): carrier: link connected
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8577] device (enp11s0u1): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8587] policy: auto-activating connection 'Wired connection 2' (1d8f4217-5d7a-3d70-a26b-77d711d024c1)
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8593] device (enp11s0u1): Activation: starting connection 'Wired connection 2' (1d8f4217-5d7a-3d70-a26b-77d711d024c1)
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8594] device (enp11s0u1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8598] manager: NetworkManager state is now CONNECTING
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8601] device (enp11s0u1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8609] device (enp11s0u1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8614] dhcp4 (enp11s0u1): activation: beginning transaction (timeout in 45 seconds)
Sep 09 12:54:57 sandy NetworkManager[674]: <info>  [1725882897.8817] dhcp4 (enp11s0u1): state changed new lease, address=192.168.85.239, acd pending
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.0560] dhcp4 (enp11s0u1): state changed new lease, address=192.168.85.239
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.0574] policy: set 'Wired connection 2' (enp11s0u1) as default for IPv4 routing and DNS
Sep 09 12:54:58 sandy dbus-broker-launch[608]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could not be found.
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.0778] device (enp11s0u1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 09 12:54:58 sandy systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 09 12:54:58 sandy systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.1322] device (enp11s0u1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.1325] device (enp11s0u1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.1331] manager: NetworkManager state is now CONNECTED_SITE
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.1335] device (enp11s0u1): Activation: successful, device activated.
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.3042] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 09 12:55:03 sandy systemd[1]: Starting Time & Date Service...
Sep 09 12:55:03 sandy systemd[1]: Started Time & Date Service.
Sep 09 12:55:04 sandy systemd[1]: Started PC/SC Smart Card Daemon.
Sep 09 12:55:04 sandy (pcscd)[1615]: pcscd.service: Referenced but unset environment variable evaluates to an empty string: PCSCD_ARGS
Sep 09 12:55:08 sandy systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Sep 09 12:55:15 sandy systemd-timesyncd[518]: Contacted time server 194.117.47.42:123 (ntp02.oal.ul.pt).
Sep 09 12:55:15 sandy systemd-timesyncd[518]: Initial clock synchronization to Mon 2024-09-09 12:55:14.767923 WEST.
Sep 09 12:55:33 sandy systemd[1]: systemd-timedated.service: Deactivated successfully.
Sep 09 12:56:10 sandy pcscd[1615]: 00000000 commands.c:1155:CmdPowerOff Card absent or mute
Sep 09 12:56:10 sandy systemd[1]: pcscd.service: Deactivated successfully.
Sep 09 12:56:11 sandy sudo[1825]: pam_systemd_home(sudo:auth): New sd-bus connection (system-bus-pam-systemd-home-1825) opened.
Sep 09 12:56:12 sandy sudo[1825]: usernam1 : TTY=pts/0 ; PWD=/home/usernam1 ; USER=root ; COMMAND=/usr/bin/dmesg -w
Sep 09 12:56:12 sandy sudo[1825]: pam_unix(sudo:session): session opened for user root(uid=0) by usernam1(uid=1000)
Sep 09 12:56:20 sandy kernel: usb 3-1: USB disconnect, device number 3
Sep 09 12:56:20 sandy kernel: rndis_host 3-1:1.0 enp11s0u1: unregister 'rndis_host' usb-0000:0b:00.0-1, RNDIS device
Sep 09 12:56:37 sandy sudo[1825]: pam_unix(sudo:session): session closed for user root
Sep 09 12:56:42 sandy systemd-logind[692]: The system will power off now!
Sep 09 12:56:42 sandy systemd-logind[692]: System is powering down.
Sep 09 12:56:42 sandy ssh-agent[1151]: exiting on signal 15
Sep 09 12:56:42 sandy systemd[1]: Stopping Session 1 of User usernam1...
Sep 09 12:56:42 sandy systemd[1]: Removed slice Slice /system/modprobe.
Sep 09 12:56:42 sandy systemd[1]: Stopped target Graphical Interface.
Sep 09 12:56:42 sandy systemd[1]: Stopped target Smart Card.
Sep 09 12:56:42 sandy login[822]: pam_unix(login:session): session closed for user usernam1
Sep 09 12:56:42 sandy at-spi2-registryd[1148]: X connection to :0 broken (explicit kill or server shutdown).
Sep 09 12:56:42 sandy systemd[1]: Stopped target Sound Card.
Sep 09 12:56:42 sandy login[822]: pam_systemd(login:session): New sd-bus connection (system-bus-pam-systemd-822) opened.
Sep 09 12:56:42 sandy systemd[1]: Stopped target Timer Units.
Sep 09 12:56:42 sandy systemd[1]: archlinux-keyring-wkd-sync.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Refresh existing PGP keys of archlinux-keyring regularly.
Sep 09 12:56:42 sandy systemd[1]: fstrim.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Discard unused filesystem blocks once a week.
Sep 09 12:56:42 sandy systemd[1]: logrotate.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Daily rotation of log files.
Sep 09 12:56:42 sandy systemd[1]: man-db.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1057]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Sep 09 12:56:42 sandy systemd[1]: Stopped Daily man-db regeneration.
Sep 09 12:56:42 sandy systemd[1057]: xfce4-notifyd.service: Failed with result 'exit-code'.
Sep 09 12:56:42 sandy systemd[1]: pkgstats.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Weekly pkgstats submission.
Sep 09 12:56:42 sandy systemd[1]: shadow.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Daily verification of password and group files.
Sep 09 12:56:42 sandy systemd[1]: systemd-tmpfiles-clean.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Sep 09 12:56:42 sandy systemd[1]: updatedb.timer: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Daily locate database update.
Sep 09 12:56:42 sandy systemd[1]: Stopped target System Time Set.
Sep 09 12:56:42 sandy systemd[1]: lvm2-lvmpolld.socket: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Closed LVM2 poll daemon socket.
Sep 09 12:56:42 sandy systemd[1]: systemd-rfkill.socket: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
Sep 09 12:56:42 sandy systemd[1]: Stopping Accounts Service...
Sep 09 12:56:42 sandy systemd[1057]: dbus-:1.9-org.a11y.atspi.Registry@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 09 12:56:42 sandy systemd[1057]: dbus-:1.9-org.a11y.atspi.Registry@0.service: Failed with result 'exit-code'.
Sep 09 12:56:42 sandy systemd[1]: Stopping Save/Restore Sound Card State...
Sep 09 12:56:42 sandy systemd[1]: Starting Generate shutdown-ramfs...
Sep 09 12:56:42 sandy systemd[1]: Stopping Authorization Manager...
Sep 09 12:56:42 sandy systemd[1]: Stopping Load/Save OS Random Seed...
Sep 09 12:56:42 sandy systemd[1]: systemd-udev-load-credentials.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Load udev Rules from Credentials.
Sep 09 12:56:42 sandy systemd[1]: Stopping TLP system startup/shutdown...
Sep 09 12:56:42 sandy systemd[1]: Stopping Disk Manager...
Sep 09 12:56:42 sandy systemd[1]: Stopping Daemon for power management...
Sep 09 12:56:42 sandy systemd[1]: run-credentials-systemd\x2dudev\x2dload\x2dcredentials.service.mount: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: getty@tty1.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Getty on tty1.
Sep 09 12:56:42 sandy systemd[1]: run-credentials-getty\x40tty1.service.mount: Deactivated successfully.
Sep 09 12:56:42 sandy udisksd[1288]: udisks daemon version 2.10.1 exiting
Sep 09 12:56:42 sandy systemd[1]: accounts-daemon.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Accounts Service.
Sep 09 12:56:42 sandy systemd[1]: polkit.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Authorization Manager.
Sep 09 12:56:42 sandy systemd[1]: udisks2.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Disk Manager.
Sep 09 12:56:42 sandy systemd[1]: alsa-restore.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Save/Restore Sound Card State.
Sep 09 12:56:42 sandy systemd[1]: systemd-random-seed.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Load/Save OS Random Seed.
Sep 09 12:56:42 sandy systemd-logind[692]: Session 1 logged out. Waiting for processes to exit.
Sep 09 12:56:42 sandy systemd[1]: Removed slice Slice /system/getty.
Sep 09 12:56:42 sandy systemd[1]: upower.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Daemon for power management.
Sep 09 12:56:42 sandy systemd[1]: tlp.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped TLP system startup/shutdown.
Sep 09 12:56:42 sandy systemd[1]: Stopped target Multi-User System.
Sep 09 12:56:42 sandy systemd[1]: Stopped target Login Prompts.
Sep 09 12:56:42 sandy systemd[1]: cpupower.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Apply cpupower configuration.
Sep 09 12:56:42 sandy systemd[1]: Stopping Initialize hardware monitoring sensors...
Sep 09 12:56:42 sandy (modprobe)[1907]: lm_sensors.service: Referenced but unset environment variable evaluates to an empty string: BUS_MODULES
Sep 09 12:56:42 sandy systemd[1]: session-1.scope: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Session 1 of User usernam1.
Sep 09 12:56:42 sandy systemd[1]: session-1.scope: Consumed 16.644s CPU time, 971.7M memory peak.
Sep 09 12:56:42 sandy systemd[1]: Stopping User Manager for UID 1000...
Sep 09 12:56:42 sandy systemd-logind[692]: Removed session 1.
Sep 09 12:56:42 sandy systemd[1057]: Activating special unit Exit the Session...
Sep 09 12:56:42 sandy systemd[1057]: Removed slice Slice /app/dbus-:1.9-org.a11y.atspi.Registry.
Sep 09 12:56:42 sandy systemd[1057]: Stopped target Main User Target.
Sep 09 12:56:42 sandy dbus-broker[1141]: Dispatched 313 messages @ 8(±10)μs / message.
Sep 09 12:56:42 sandy systemd[1057]: Stopping Accessibility services bus...
Sep 09 12:56:42 sandy systemd[1057]: Stopping dbus-:1.2-org.xfce.Xfconf@0.service...
Sep 09 12:56:42 sandy gpg-agent[1162]: SIGTERM received - shutting down ...
Sep 09 12:56:42 sandy systemd[1057]: Stopping GnuPG cryptographic agent and passphrase cache...
Sep 09 12:56:42 sandy systemd[1057]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Sep 09 12:56:42 sandy tumblerd[1267]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
Sep 09 12:56:42 sandy systemd[1057]: Stopping Virtual filesystem service...
Sep 09 12:56:42 sandy systemd[1057]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Sep 09 12:56:42 sandy systemd[1057]: Stopping Virtual filesystem service - digital camera monitor...
Sep 09 12:56:42 sandy systemd[1057]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Sep 09 12:56:42 sandy gpg-agent[1162]: gpg-agent (GnuPG) 2.4.5 stopped
Sep 09 12:56:42 sandy systemd[1057]: Stopping Virtual filesystem service - disk device monitor...
Sep 09 12:56:42 sandy systemd[1057]: Stopping PipeWire PulseAudio...
Sep 09 12:56:42 sandy systemd[1057]: Stopping Thumbnailing service...
Sep 09 12:56:42 sandy systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Unmounted /run/user/1000/gvfs.
Sep 09 12:56:42 sandy systemd[1057]: Stopped Virtual filesystem service.
Sep 09 12:56:42 sandy systemd[1057]: Stopped dbus-:1.2-org.xfce.Xfconf@0.service.
Sep 09 12:56:42 sandy systemd[1057]: Stopped GnuPG cryptographic agent and passphrase cache.
Sep 09 12:56:42 sandy systemd[1057]: Stopped PipeWire PulseAudio.
Sep 09 12:56:42 sandy systemd[1057]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Sep 09 12:56:42 sandy systemd[1057]: Stopped Virtual filesystem service - digital camera monitor.
Sep 09 12:56:42 sandy systemd[1057]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Sep 09 12:56:42 sandy systemd[1057]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Sep 09 12:56:42 sandy systemd[1057]: Removed slice Slice /app/dbus-:1.2-org.xfce.Xfconf.
Sep 09 12:56:42 sandy wireplumber[1173]: wireplumber: stopped by signal: Terminated
Sep 09 12:56:42 sandy systemd[1057]: Stopping Multimedia Service Session Manager...
Sep 09 12:56:42 sandy systemd[1057]: Stopped Thumbnailing service.
Sep 09 12:56:42 sandy wireplumber[1173]: wireplumber: disconnected from pipewire
Sep 09 12:56:42 sandy wireplumber[1173]: pw.core: 0x5c2315bcfca0: leaked proxy 0x5c2315d6cf80 id:3
Sep 09 12:56:42 sandy systemd[1057]: Stopped Virtual filesystem service - disk device monitor.
Sep 09 12:56:42 sandy systemd[1057]: Stopped Multimedia Service Session Manager.
Sep 09 12:56:42 sandy systemd[1057]: Stopping PipeWire Multimedia Service...
Sep 09 12:56:42 sandy systemd[1057]: Stopped PipeWire Multimedia Service.
Sep 09 12:56:42 sandy systemd[1]: lm_sensors.service: Deactivated successfully.
Sep 09 12:56:42 sandy systemd[1]: Stopped Initialize hardware monitoring sensors.
Sep 09 12:56:47 sandy systemd[1057]: at-spi-dbus-bus.service: State 'stop-sigterm' timed out. Killing.
Sep 09 12:56:47 sandy systemd[1057]: at-spi-dbus-bus.service: Killing process 1134 (at-spi-bus-laun) with signal SIGKILL.
Sep 09 12:56:53 sandy systemd[1057]: at-spi-dbus-bus.service: Processes still around after SIGKILL. Ignoring.
Sep 09 12:56:58 sandy systemd[1057]: at-spi-dbus-bus.service: State 'final-sigterm' timed out. Killing.
Sep 09 12:56:58 sandy systemd[1057]: at-spi-dbus-bus.service: Killing process 1134 (at-spi-bus-laun) with signal SIGKILL.
Sep 09 12:57:03 sandy systemd[1057]: at-spi-dbus-bus.service: Processes still around after final SIGKILL. Entering failed mode.
Sep 09 12:57:03 sandy systemd[1057]: at-spi-dbus-bus.service: Failed with result 'timeout'.
Sep 09 12:57:03 sandy systemd[1057]: at-spi-dbus-bus.service: Unit process 1134 (at-spi-bus-laun) remains running after unit stopped.
Sep 09 12:57:03 sandy systemd[1057]: Stopped Accessibility services bus.
Sep 09 12:57:03 sandy systemd[1057]: Stopped target Basic System.
Sep 09 12:57:03 sandy systemd[1057]: Stopped target Paths.
Sep 09 12:57:03 sandy systemd[1057]: Stopped target Sockets.
Sep 09 12:57:03 sandy systemd[1057]: Stopped target Timers.
Sep 09 12:57:03 sandy systemd[1057]: Closed GnuPG network certificate management daemon.
Sep 09 12:57:03 sandy systemd[1057]: Closed GCR ssh-agent wrapper.
Sep 09 12:57:03 sandy systemd[1057]: Closed GNOME Keyring daemon.
Sep 09 12:57:03 sandy systemd[1057]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 09 12:57:03 sandy systemd[1057]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 09 12:57:03 sandy systemd[1057]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 09 12:57:03 sandy systemd[1057]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 09 12:57:03 sandy systemd[1057]: Closed GnuPG public key management service.
Sep 09 12:57:03 sandy systemd[1057]: Closed p11-kit server.
Sep 09 12:57:03 sandy systemd[1057]: Closed PipeWire PulseAudio.
Sep 09 12:57:03 sandy systemd[1057]: Closed PipeWire Multimedia System Sockets.
Sep 09 12:57:03 sandy dbus-broker[1113]: Dispatched 2663 messages @ 7(±8)μs / message.
Sep 09 12:57:03 sandy systemd[1057]: Stopping D-Bus User Message Bus...
Sep 09 12:57:03 sandy systemd[1057]: Stopped D-Bus User Message Bus.
Sep 09 12:57:03 sandy systemd[1057]: Removed slice User Core Session Slice.
Sep 09 12:57:03 sandy systemd[1057]: Closed D-Bus User Message Bus Socket.
Sep 09 12:57:03 sandy systemd[1057]: Removed slice User Application Slice.
Sep 09 12:57:03 sandy systemd[1057]: Reached target Shutdown.
Sep 09 12:57:03 sandy systemd[1057]: Finished Exit the Session.
Sep 09 12:57:03 sandy systemd[1057]: Reached target Exit the Session.
Sep 09 12:57:03 sandy (sd-pam)[1059]: pam_unix(systemd-user:session): session closed for user usernam1
Sep 09 12:57:03 sandy systemd[1]: user@1000.service: Killing process 1134 (at-spi-bus-laun) with signal SIGKILL.
Sep 09 12:57:37 sandy systemd-timesyncd[518]: Timed out waiting for reply from 194.117.47.42:123 (ntp02.oal.ul.pt).
Sep 09 12:57:38 sandy kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Sep 09 12:57:38 sandy kernel: sd 0:0:0:0: [sda] Stopping disk
Sep 09 12:57:43 sandy kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 09 12:57:43 sandy kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out
Sep 09 12:57:43 sandy kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0(SECURITY FREEZE LOCK) filtered out
Sep 09 12:57:43 sandy kernel: ata1.00: configured for UDMA/133
Sep 09 12:57:43 sandy kernel: ata1.00: Entering active power mode
Sep 09 12:57:43 sandy kernel: sd 0:0:0:0: [sda] Starting disk
Sep 09 12:57:43 sandy kernel: sd 0:0:0:0: [sda] Starting disk
Sep 09 12:57:43 sandy kernel: sd 0:0:0:0: [sda] Starting disk

As you can see, it just hangs and never shuts down. This journal is after an unsuccessful shutdown attempt after removing the tethering phone.

seth wrote:

You're losing the host but somehow the NIC device doesn't seem to get removed?

That's exactly what happens.

seth wrote:

Since you seem to be using this on a regular base

Yes, I travel frequently to a hotel that provides free wifi, but with only one login, so I use that login on my phone and use tethering to get internet on the laptop

seth wrote:

did you add any udev rules

No udev rules were added.

seth wrote:

Is there maybe a second network managing daemon?

No other daemons, only NetworkManager.

Last edited by unnilquadium (2024-09-09 12:27:18)

seth · 2024-09-09 14:25:39

Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.1335] device (enp11s0u1): Activation: successful, device activated.
Sep 09 12:54:58 sandy NetworkManager[674]: <info>  [1725882898.3042] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 09 12:55:03 sandy systemd[1]: Starting Time & Date Service...
Sep 09 12:55:03 sandy systemd[1]: Started Time & Date Service.
Sep 09 12:55:04 sandy systemd[1]: Started PC/SC Smart Card Daemon.
Sep 09 12:55:04 sandy (pcscd)[1615]: pcscd.service: Referenced but unset environment variable evaluates to an empty string: PCSCD_ARGS
Sep 09 12:55:08 sandy systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Sep 09 12:55:15 sandy systemd-timesyncd[518]: Contacted time server 194.117.47.42:123 (ntp02.oal.ul.pt).
Sep 09 12:55:15 sandy systemd-timesyncd[518]: Initial clock synchronization to Mon 2024-09-09 12:55:14.767923 WEST.
Sep 09 12:55:33 sandy systemd[1]: systemd-timedated.service: Deactivated successfully.
Sep 09 12:56:10 sandy pcscd[1615]: 00000000 commands.c:1155:CmdPowerOff Card absent or mute
Sep 09 12:56:10 sandy systemd[1]: pcscd.service: Deactivated successfully.
Sep 09 12:56:11 sandy sudo[1825]: pam_systemd_home(sudo:auth): New sd-bus connection (system-bus-pam-systemd-home-1825) opened.
Sep 09 12:56:12 sandy sudo[1825]: usernam1 : TTY=pts/0 ; PWD=/home/usernam1 ; USER=root ; COMMAND=/usr/bin/dmesg -w
Sep 09 12:56:12 sandy sudo[1825]: pam_unix(sudo:session): session opened for user root(uid=0) by usernam1(uid=1000)
Sep 09 12:56:20 sandy kernel: usb 3-1: USB disconnect, device number 3
Sep 09 12:56:20 sandy kernel: rndis_host 3-1:1.0 enp11s0u1: unregister 'rndis_host' usb-0000:0b:00.0-1, RNDIS device

So you connect via the tethering NIC at 12:54:58
At 12:56:12 you started dmesg and 8s later, 12:56:20, the usb disappears.
This might be an implicit consequence of disabling tethering, but I don't see NM disconnecting the NIC anywhere?
Did you at all

nmcli device disconnect ifname enp11s0u1

beforehand?
Can you still after whatever triggered

Sep 09 12:56:20 sandy kernel: usb 3-1: USB disconnect, device number 3

(cause then you could add a udev rule to automatize that)
https://wiki.archlinux.org/title/Networ … i_examples

unnilquadium · 2024-09-09 22:08:59

seth wrote:

12:56:20, the usb disappears.
This might be an implicit consequence of disabling tethering, but I don't see NM disconnecting the NIC anywhere?

That's correct. Whether I disconnect the network or not, after removing the tethering device the network remains showing as available in network-manager-applet.

seth wrote:

Did you at all
nmcli device disconnect ifname enp11s0u1
beforehand?

Not on that particular occasion, but I have many times and did it once again using nmcli instead of network-manager-applet (the method I normally use), and the result is the same.

unnilquadium · 2024-09-09 22:25:42

OK, ruled out a wider problem.

I was able to test it on another PC and it behaves normally.

The following are the returns of dmesg:

[  118.274060] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e82, bcdDevice= 4.04
[  118.274069] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  118.274072] usb 3-1: Product: moto g13
[  118.274074] usb 3-1: Manufacturer: motorola
[  118.274077] usb 3-1: SerialNumber: ZY22GRRSZL
[  127.789350] usb 3-1: USB disconnect, device number 7
[  128.266641] usb 3-1: new high-speed USB device number 8 using xhci_hcd
[  128.407661] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e24, bcdDevice= 4.04
[  128.407669] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  128.407673] usb 3-1: Product: moto g13
[  128.407675] usb 3-1: Manufacturer: motorola
[  128.407677] usb 3-1: SerialNumber: ZY22GRRSZL
[  128.447652] usbcore: registered new interface driver cdc_ether
[  128.453625] rndis_host 3-1:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-1, RNDIS device, d2:67:a9:56:4a:6d
[  128.453654] usbcore: registered new interface driver rndis_host
[  128.459830] rndis_host 3-1:1.0 enp0s20u1: renamed from usb0
[  149.220440] usb 3-1: USB disconnect, device number 8
[  149.220544] rndis_host 3-1:1.0 enp0s20u1: unregister 'rndis_host' usb-0000:00:14.0-1, RNDIS device
[  149.703399] usb 3-1: new high-speed USB device number 9 using xhci_hcd
[  149.844680] usb 3-1: New USB device found, idVendor=22b8, idProduct=2e82, bcdDevice= 4.04
[  149.844689] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  149.844692] usb 3-1: Product: moto g13
[  149.844694] usb 3-1: Manufacturer: motorola
[  149.844697] usb 3-1: SerialNumber: ZY22GRRSZL
[  166.087805] usb 3-1: USB disconnect, device number 9

At 127 I switch tethering on.
At 149 I switch tethering off.
The PC never hangs after that, and the network is no longer displayed on the available networks.

Note that the output produced is different from the other PC, which returns only the following upon disconnection:

[  195.883636] usb 3-1: USB disconnect, device number 4
[  195.884257] rndis_host 3-1:1.0 enp11s0u1: unregister 'rndis_host' usb-0000:0b:00.0-1, RNDIS device

So it must be something specific to the hardware on the laptop.

seth · 2024-09-10 13:23:44

So the device re-registers in response to the de-tether and that doesn't happen on your bad notebook.

1. try a different USB port
2. do you use any kind of powersaving tools? Main concern would be https://wiki.archlinux.org/title/Power_ … utosuspend
3. What if you "fake" the reconnect, ie. deactivate the tether, yank and re-plug the device?
4. Does it make a difference whether the system is on battery or external supply?

unnilquadium · 2024-09-11 06:23:00

seth wrote:

1. try a different USB port

This works.

Thank you for the suggestion.
For information the USB port that works is USB2. The port the has the problem is USB3.

Arch Linux

#1 2024-09-06 12:18:45

[SOLVED]USB Tethering - How to disconnect?

#2 2024-09-06 13:11:48

Re: [SOLVED]USB Tethering - How to disconnect?

#3 2024-09-07 15:40:05

Re: [SOLVED]USB Tethering - How to disconnect?

#4 2024-09-07 15:46:06

Re: [SOLVED]USB Tethering - How to disconnect?

#5 2024-09-08 04:32:05

Re: [SOLVED]USB Tethering - How to disconnect?

#6 2024-09-08 06:19:39

Re: [SOLVED]USB Tethering - How to disconnect?

#7 2024-09-08 21:43:13

Re: [SOLVED]USB Tethering - How to disconnect?

#8 2024-09-09 06:00:11

Re: [SOLVED]USB Tethering - How to disconnect?

#9 2024-09-09 12:24:29

Re: [SOLVED]USB Tethering - How to disconnect?

#10 2024-09-09 14:25:39

Re: [SOLVED]USB Tethering - How to disconnect?

#11 2024-09-09 22:08:59

Re: [SOLVED]USB Tethering - How to disconnect?

#12 2024-09-09 22:25:42

Re: [SOLVED]USB Tethering - How to disconnect?

#13 2024-09-10 13:23:44

Re: [SOLVED]USB Tethering - How to disconnect?

#14 2024-09-11 06:23:00

Re: [SOLVED]USB Tethering - How to disconnect?

Board footer