[Bug 1200781] New: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781 Bug ID: 1200781 Summary: xhci stop working. Works briefly after reboot, or remove and load xhci_pci & xhci_hcd. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: publio.escipion.el.africano@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- openSuSE Leap 15.4 x86_64, kernel 4.14.21-150400.22-default, in a Lenovo IdeaPad 3 15ADA05: https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_3_15ADA05/IdeaPad_3... An external mouse stops working after a brief period of time, after login into KDE, or after removing and loading xhci_pci & xhci_hcd. System complaints of: �xhci_hcd 0000:02:00.3 WARNIGN: Host System Error� and: �usb 2-3: device not accepting address 2, error -108� I've tried two bluetooth mice, and a standard cord mouse. The same result. It seems that it's the USB controllers are the only components affected, so far. Mousepad works properly, but I'm not use to it. I have to constantly remove and load xhci_pci & xhci_hcd, as root. rmmod xhci_pci rmmod xhci_hcd modprobe xhci_pci modprobe xhci_hcd Mouse works after that for a short time. Nota bene: Devices work properly under openSuSE Leap 15.2 x86_64, kernel 5.3.18-lp152.106-default (old HP Pavillion). This bug resembles https://bugzilla.opensuse.org/show_bug.cgi?id=1193652 -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c1
Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c2
--- Comment #2 from Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c3
--- Comment #3 from Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c4
Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c5
Johannes Carraro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c8
--- Comment #8 from Rainer Hurtado Navarro
(In reply to Takashi Iwai from comment #6)
Could you check with the latest kernel in OBS Kernel:SLE15-SP4 repo? https://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/
If that does not work, please try the original kernel with usbcore.autosuspend=-1 on the kernel command line.
I'm not familiar with the new GRUB 2 command line at boot time. I was not able to load the kernel, before "boot". There is no help in https://doc.opensuse.org/documentation/leap/reference/html/book-reference/ch.... -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c9
--- Comment #9 from Rainer Hurtado Navarro
openSuSE Leap 15.4 x86_64, kernel 4.14.21-150400.22-default, in a Lenovo IdeaPad 3 15ADA05: https://psref.lenovo.com/syspool/Sys/PDF/IdeaPad/IdeaPad_3_15ADA05/ IdeaPad_3_15ADA05_Spec.PDF
An external mouse stops working after a brief period of time, after login into KDE, or after removing and loading xhci_pci & xhci_hcd.
System complaints of: �xhci_hcd 0000:02:00.3 WARNIGN: Host System Error� and: �usb 2-3: device not accepting address 2, error -108�
I've tried two bluetooth mice, and a standard cord mouse. The same result.
It seems that it's the USB controllers are the only components affected, so far. Mousepad works properly, but I'm not use to it.
I have to constantly remove and load xhci_pci & xhci_hcd, as root.
rmmod xhci_pci rmmod xhci_hcd modprobe xhci_pci modprobe xhci_hcd
Mouse works after that for a short time.
Nota bene: Devices work properly under openSuSE Leap 15.2 x86_64, kernel 5.3.18-lp152.106-default (old HP Pavillion).
This bug resembles https://bugzilla.opensuse.org/show_bug.cgi?id=1193652
The issue persists, after Leap 15.4 kernel update (5.14.21-150400.24.11-default x86_64). -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c10
Rainer Hurtado Navarro
(In reply to Takashi Iwai from comment #6)
Could you check with the latest kernel in OBS Kernel:SLE15-SP4 repo? https://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/
If that does not work, please try the original kernel with usbcore.autosuspend=-1 on the kernel command line.
(In reply to Takashi Iwai from comment #6)
Could you check with the latest kernel in OBS Kernel:SLE15-SP4 repo? https://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/
Done. But I got a load error, so I manually fall back to kernel 5.14.21-150400.24.11-default x86_64. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c11
--- Comment #11 from Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c12
--- Comment #12 from Rainer Hurtado Navarro
(In reply to Takashi Iwai from comment #6)
Could you check with the latest kernel in OBS Kernel:SLE15-SP4 repo? https://download.opensuse.org/repositories/Kernel:/SLE15-SP4/pool/
If that does not work, please try the original kernel with usbcore.autosuspend=-1 on the kernel command line.
I introduced the parameter into YaST (Leap 15.4 kernel 5.14.21-150400.24.11-default x86_64), and the workaround seems to work fine: input devices are working far longer as they were, without failure so far as I'm writing. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c13
--- Comment #13 from Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c14
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c15
--- Comment #15 from Rainer Hurtado Navarro
You seem enabling Secure Boot. Could you try to disable Secure Boot on BIOS?
The kernel in OBS Kernel:HEAD is an unofficial build, hence it won't boot with Secure Boot easily.
I'll try. Although the parameter suggested above makes the functionality to last longer, it just mean only that: last longer, and I've working with may old computer, because this bug has the potential of corrupt my data while working with external USB storage devices. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c16
--- Comment #16 from Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c17
Rainer Hurtado Navarro
You seem enabling Secure Boot. Could you try to disable Secure Boot on BIOS?
The kernel in OBS Kernel:HEAD is an unofficial build, hence it won't boot with Secure Boot easily.
The device does not allow to unset secure mode, keeping UEFI. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c18
--- Comment #18 from Rainer Hurtado Navarro
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781
http://bugzilla.opensuse.org/show_bug.cgi?id=1200781#c19
--- Comment #19 from Rainer Hurtado Navarro
participants (1)
-
bugzilla_noreply@suse.com