You are not logged in.
Hello I am kind of a newbie to pure arch, but not to linux overall. I have installed arch recently and now I face a problem of USB devices shutting down. Unfortunately for me I use USB wifi so that means no internet.
Sudo dmesg gives an output like
xhci host controller not responding assume dead
Usb device disconnect, device number 2
I already tried that unbind and bind method to turn off and turn on USB but few seconds after it stops again. I turned of USB power management in tlp also, still same result.
I am using kernel 6.1.31-1-lts
The device is a hp laptop with ryzen 3500u and 8gb ram.
Last edited by ca11mejp (2023-06-15 16:46:23)
Offline
I would take a close look at the journal looking for stuff that happened within a minute before the failure. You might want to upload your journal and provide a link using something like
journalctl -b --no-pager | curl -F 'f:1=<-' ix.io so we can look it it.
Also, is it one device that fails, or do all USB devices fail? What about other USB devices on the same BUS (based on the output of lsusb ?
Is there a cable involved? If so eliminate or replace the cable.
Is device visible in llsusb after it fails?
Is there a cable involved? If so eliminate or replace the cable.
Have you tried a different kernel?
Is there a cable involved? If so eliminate or replace the cable.
I hate cables.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Thanks for replying
I would take a close look at the journal looking for stuff that happened within a minute before the failure. You might want to upload your journal and provide a link using something like
journalctl -b --no-pager | curl -F 'f:1=<-' ix.ioso we can look it it.
I have uploaded it in pastebin using another distro because I am not able to access the internet in this one due to this issue. Also it is kind of random sometimes. It does not happen every time.
Also, is it one device that fails, or do all USB devices fail? What about other USB devices on the same BUS (based on the output of lsusb ?
My webcam is connected using usb interface in my laptop. Everything gets disconnected
Is there a cable involved? If so eliminate or replace the cable.
Is device visible in llsusb after it fails?
Is there a cable involved? If so eliminate or replace the cable.
Have you tried a different kernel?
Is there a cable involved? If so eliminate or replace the cable.
I hate cables.
No cable is involved.
No the device is not visible in lsusb. Thats how I found out that it is getting disconnected.
Just after I installed I only had this problem when I suspend it. Now it kind of happens without even suspending. I have updated the kernel sometimes after I installed I think.
No cable is involved XD
Offline
There're two wifi NICs?
Try to reproduce the xhci death w/o the wifi dongle…
The add "acpi_aspm" to the kernel parameters.
Offline
Yeah there are two NICs, one is PCI which does not work most of the time. The other is USB wifi adapter I bought as a replacement. I didnt mind disabling the PCI one as it doesnt work most of the time.
Also I am not quite sure how to add acpi_aspm parameter in kernel parameters. I vaguely know how to add it, but what value should I give it?
Offline
Sorry, "pcie_aspm=off", NOT "acpi_aspm" (half my brain was at a different thread ![]()
=> https://wiki.archlinux.org/title/Kernel_parameters
But no, you'd have to disable (or rather "remove") the usb dongle and see whether the issue still occurs, because I suspect it to be the culprit.
Edit: maybe you get away w/ a different hub…
lsusb -tvLast edited by seth (2023-06-06 15:52:58)
Offline
Sorry, "pcie_aspm=off", NOT "acpi_aspm" (half my brain was at a different thread
=> https://wiki.archlinux.org/title/Kernel_parametersBut no, you'd have to disable (or rather "remove") the usb dongle and see whether the issue still occurs, because I suspect it to be the culprit.
Edit: maybe you get away w/ a different hub…
lsusb -tv
I added pcie_aspm=off but there have not been any difference.
My PCI NIC does not work properly. Randomly it will work. I have tried in different distro and in windows. Seems like an hardware problem. Thats why I switched to USB Wifi adapter. I use ubuntu, windows. It works very well in ubuntu with default realtek driver. But arch has this problem of usb shutting down.
This time I had the problem after waking it up from suspend. I posted the journalctl here https://pastebin.com/GacaVuwY
Offline
lsusb -tv
My PCI NIC does not work properly.
Yeah, I understood that.
The point is to operate the system w/o the wifi dongle to see whether you still get the xhcd errors to see whether something else kills the bus (or likely the wifi dongle itself)
I use ubuntu, windows.
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
I'd not even be surprised if that's the issue w/ the internal wifi NIC…
Offline
Yeah, I understood that.
The point is to operate the system w/o the wifi dongle to see whether you still get the xhcd errors to see whether something else kills the bus (or likely the wifi dongle itself)
I tried this. But after I attached my phone for usb tethering same error occured and every usb shutdown as before. Even webcam.
While my pci card which surprisingly worked at that time entered DOWN state after sometime. It usually do that in arch. Is it some power management thing? I did add that kernel parameter though.
This is the journalctl log https://pastebin.com/qiWWipig.
I use ubuntu, windows.
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.I'd not even be surprised if that's the issue w/ the internal wifi NIC…
Well the fastboot option I have turned it off when I was dual booting. But I checked it again and it is still off. Also the PCI thing I actually gave up because I tried so many things from driver change to bringing it to a repair shop. They suggested I go for wifi adapter as it would cost more to change the PCI NIC and it is not worth it. The PCI NIC stopped working and would not show in device manager in windows or in linux lspci. It will work sometimes randomly. Anyway I started using USB wifi adapter (Realtek chip) and the driver for that is shitty in windows. In ubuntu though it works seamlessly with the default driver rtl8xxxu. And same driver is used in arch also. It does work with arch except for this usb shutting down after sometime.
And sorry for replying late. I just wanted to check everything before I replied and also busy with some IRL stuff haha. But I want to make this arch work without any probelms somehow
Last edited by ca11mejp (2023-06-10 03:58:15)
Offline
at that time entered DOWN state after sometime
Inside or outside the carets (assuming you're talking about DOWN in "ip a")
The journal you posted lacks the entire header, so there's no reference point for the pci devices and bus IDs (or whether aspm is actually relevant etcetc.)
The failing xHCI host seems to hang on the same bus as the GPU?
Post the *complete* journal as well as the requested output of "lsusb -tv"and for convenience also "lspci -nn"
Offline
at that time entered DOWN state after sometime
Inside or outside the carets (assuming you're talking about DOWN in "ip a")
yep I am talking about "ip a"
The journal you posted lacks the entire header, so there's no reference point for the pci devices and bus IDs (or whether aspm is actually relevant etcetc.)
The failing xHCI host seems to hang on the same bus as the GPU?
Post the *complete* journal as well as the requested output of "lsusb -tv"and for convenience also "lspci -nn"
I am not sure I understand that thing about GPU, but heres the full log http://ix.io/4xT4
lsusb -tv
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
|__ Port 1: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
ID 0bda:b009 Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Wireless, Driver=btusb, 480M
ID 0bda:b720 Realtek Semiconductor Corp. RTL8723BU 802.11b/g/n WLAN Adapter
|__ Port 1: Dev 2, If 1, Class=Wireless, Driver=btusb, 480M
ID 0bda:b720 Realtek Semiconductor Corp. RTL8723BU 802.11b/g/n WLAN Adapter
|__ Port 1: Dev 2, If 2, Class=Vendor Specific Class, Driver=rtl8xxxu, 480M
ID 0bda:b720 Realtek Semiconductor Corp. RTL8723BU 802.11b/g/n WLAN Adapter
|__ Port 4: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
ID 04f2:b67f Chicony Electronics Co., Ltd
|__ Port 4: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
ID 04f2:b67f Chicony Electronics Co., Ltdlspci -nn
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU [1022:15d1]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
00:01.6 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
00:01.7 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] [1022:15d3]
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A [1022:15db]
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:15dc]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61)
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 [1022:15e8]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 [1022:15e9]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 [1022:15ea]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 [1022:15eb]
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 [1022:15ec]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 [1022:15ed]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 [1022:15ee]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 [1022:15ef]
01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller 980 [144d:a809]
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723]
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c2)
04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller [1002:15de]
04:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e0]
04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e1]
04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2]
04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
05:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 61)Last edited by ca11mejp (2023-06-10 07:21:33)
Offline
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
yep I am talking about "ip a"
[DOWN] Inside or outside the carets
that thing about GPU
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c2)
…
04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e0]
04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 [1022:15e1]You don't have https://wiki.archlinux.org/title/Microc … _microcode installed, do you?
Jun 10 12:09:22 HP kernel: rtw_8723de 0000:03:00.0: pci bus timeout, check dma statusshows up almost 4000 times within 45 seconds (likely the cause of the journal uploading issues)
Can you deactivate the chip in the BIOS?
Otherwise blacklist rtw_8723de, https://wiki.archlinux.org/title/Kernel … and_line_2
Offline
yep I am talking about "ip a"
seth wrote:[DOWN] Inside or outside the carets
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether f8:0d:ac:cb:64:e8 brd ff:ff:ff:ff:ff:ff
altname enp2s0
3: wlp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether ba:55:25:90:1b:97 brd ff:ff:ff:ff:ff:ff permaddr 28:cd:c4:46:5e:73
5: wlp4s0f3u1i2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 38:a3:8c:80:8e:06 brd ff:ff:ff:ff:ff:ff
inet 192.168.126.123/24 brd 192.168.126.255 scope global dynamic noprefixroute wlp4s0f3u1i2
valid_lft 2918sec preferred_lft 2918sec
inet6 2409:4073:219b:a037:a326:da6e:2d50:7215/64 scope global dynamic noprefixroute
valid_lft 7172sec preferred_lft 7172sec
inet6 fe80::af14:e04d:bf4a:39ae/64 scope link noprefixroute
valid_lft forever preferred_lft foreverYou don't have https://wiki.archlinux.org/title/Microc … _microcode installed, do you?
Yes I have installed it when installing the system. amd-ucode
Jun 10 12:09:22 HP kernel: rtw_8723de 0000:03:00.0: pci bus timeout, check dma statusshows up almost 4000 times within 45 seconds (likely the cause of the journal uploading issues)
Can you deactivate the chip in the BIOS?
Otherwise blacklist rtw_8723de, https://wiki.archlinux.org/title/Kernel … and_line_2
I blacklisted it.
Offline
I blacklisted it.
Any discernable impact on the original problem?
The operational steate is DOWN for wlp3s0 what is perfectly expectable since there's no carrier
Offline
Any discernable impact on the original problem?
It seems like the probelm stopped occuring. I tried suspending and it does not seem to be removing. I didnt really get the reason though. What was the problem? Was it the module i blacklisted?
Actually another problem occured. After logging out and logging in the device is still there but it turns to DOWN state like the pci. Now the pci device is not shown but I am okay with that. I want this usb wifi to work
The operational steate is DOWN for wlp3s0 what is perfectly expectable since there's no carrier
What is it meant by that? Now the usb nic turns to that state when i log out and log in
Here's the journalctl -> http://ix.io/4xV2
Last edited by ca11mejp (2023-06-10 16:47:17)
Offline
It seems like the probelm stopped occuring.
Good.
What was the problem?
If blacklisting the module helped, your internal WiFi NIC.
Which is also why
Now the pci device is not shown
After logging out and logging in the device is still there but it turns to DOWN state like the pci.
…
What is it meant by that?
"the wifi-cable isn't plugged" (metaphorically)
This isn't covered by the journal you posted (there's no logout/re-login logged), was it supposed to be?
Can you re-connect to the AP after the login?
Offline
Seems like the probelm started again
I suspended it and the usb got disconnected, with same error xhci controller not responding assume dead.
This isn't covered by the journal you posted (there's no logout/re-login logged), was it supposed to be?
Can you re-connect to the AP after the login?
Nope that does not work
journalctl -> http://ix.io/4xXp
Last edited by ca11mejp (2023-06-11 03:27:46)
Offline
The journal you posted covers 8 boots, everytime you login you get a connections.
There's one sleep/resume which has
Jun 11 08:40:41 HP kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Jun 11 08:40:41 HP kernel: xhci_hcd 0000:04:00.4: xHCI host not responding to stop endpoint command
Jun 11 08:40:41 HP kernel: xhci_hcd 0000:04:00.4: xHCI host controller not responding, assume dead
Jun 11 08:40:41 HP kernel: xhci_hcd 0000:04:00.4: HC died; cleaning upWhich is [drumroll]
Jun 10 22:09:04 HP kernel: usb 1-2: RTL8723BU rev E (SMIC) 1T1R, TX queues 3, WiFi=1, BT=1, GPS=0, HI PA=0
Jun 10 22:09:04 HP kernel: usb 1-2: RTL8723BU MAC: 38:a3:8c:80:8e:06
Jun 10 22:09:04 HP kernel: usb 1-2: rtl8xxxu: Loading firmware rtlwifi/rtl8723bu_nic.bin
Jun 10 22:09:04 HP kernel: usb 1-2: Firmware revision 35.0 (signature 0x5301)
Jun 10 22:09:07 HP kernel: usb 1-2: rtl8xxxu_bss_info_changed: HT supported
Jun 11 08:40:41 HP kernel: usb 1-2: disconnecting
Jun 11 08:40:41 HP kernel: usb 1-2: Device still attached, trying to reset
Jun 11 08:40:41 HP kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Jun 11 08:40:41 HP kernel: usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Jun 11 08:40:41 HP kernel: usb 1-2: This Realtek USB WiFi dongle (0x0bda:0xb720) is untested!
Jun 11 08:40:41 HP kernel: usb 1-2: Please report results to Jes.Sorensen@gmail.comyour wifi dongle.
If the system is otherwise stable*, try to remove the dongle before sleeping the system…
*again: there's no indication of connection failure after re-logins; post the journal for a single incident where you believe that to be the case and also dump
ip a
ip r
ping -c 1.1.1.1
dig google.comDo you use any bluetooth devices?
(Cause that shows a lot of errors and seems to be the dongle as well)
Offline
The journal you posted covers 8 boots, everytime you login you get a connections.
There's one sleep/resume which hasWhich is [drumroll]
your wifi dongle.
So is it my wifi dongle problem? But I use the same one with ubuntu and same driver rtl8xxxu. It works fine with that though.
If the system is otherwise stable*, try to remove the dongle before sleeping the system…
*again: there's no indication of connection failure after re-logins; post the journal for a single incident where you believe that to be the case
I will post when something like that occurs. But here I am going to post one where it got disconnected when I was using. I just took log of just 1 hour interval so it might be easy to look --> http://ix.io/4xYc
and also dump
ip a ip r ping -c 1.1.1.1 dig google.com
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether f8:0d:ac:cb:64:e8 brd ff:ff:ff:ff:ff:ff
altname enp2s0
3: wlp4s0f3u1i2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 38:a3:8c:80:8e:06 brd ff:ff:ff:ff:ff:ff
inet 192.168.126.123/24 brd 192.168.126.255 scope global dynamic noprefixroute wlp4s0f3u1i2
valid_lft 3404sec preferred_lft 3404sec
inet6 2409:4073:219a:8712:a22c:cc0:1f4:7349/64 scope global dynamic noprefixroute
valid_lft 7008sec preferred_lft 7008sec
inet6 fe80::af14:e04d:bf4a:39ae/64 scope link noprefixroute
valid_lft forever preferred_lft foreverip r
default via 192.168.126.134 dev wlp4s0f3u1i2 proto dhcp src 192.168.126.123 metric 600
192.168.126.0/24 dev wlp4s0f3u1i2 proto kernel scope link src 192.168.126.123 metric 600ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=53 time=98.9 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=53 time=127 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=53 time=188 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=53 time=211 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=53 time=222 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=53 time=120 ms
^C
--- 1.1.1.1 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5010ms
rtt min/avg/max/mdev = 98.931/161.115/221.616/47.532 msping -c does not seem to take in ip address as the parameter
I am a bit confused. did you mean to dump these when it is not working? If so I will do that next time. I restart the system when it stops working.
Do you use any bluetooth devices?
(Cause that shows a lot of errors and seems to be the dongle as well)
Well it is part of the dongle. I bought one with wifi and bluetooth since the pci NIC was the one handling bluetooth sometimes the bluetooth also didnt work that time.
Also I have this inkling that it might be tlp?
Last edited by ca11mejp (2023-06-11 09:25:15)
Offline
But I use the same one with ubuntu and same driver rtl8xxxu.
On the same notebook?
ping -c does not seem to take in ip address as the parameter
Sorry, too many ones ;-)
ping -c 1 1.1.1.1But that only limits the count, not relevant.
I am a bit confused. did you mean to dump these when it is not working?
Yes, after failing to reconnect the network.
Also I have this inkling that it might be tlp?
Sure, disable it or except the dongle and see whether that has any impact.
Well it is part of the dongle.
Do you use any bluetooth devices?
Otherwise the idea would be to rfkill BT.
But here I am going to post one where it got disconnected when I was using. I just took log of just 1 hour interval so it might be easy to look
There's only one login and a failure (and reboot) before w/ "xHCI host not responding to stop endpoint command"
Offline
I tested it for two days and it got resolved!!! I think it was tlp. I kind of disabled the runtime_pm_on thing and it deems to work. I saw it in one of your reply to another post. There is no problem even when I log out or log in or with suspend. It sure worked out.
On the same notebook?
Yep
Thanks a lot for the help!!!
Should I mark this thread as solved? If so how can I do that?
Edit: I found out how to mark it solved. Thanks
Last edited by ca11mejp (2023-06-15 16:47:06)
Offline