http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c1 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |benthomasgeorge7899@gmail.c | |om, tiwai@suse.com Flags| |needinfo?(benthomasgeorge78 | |99@gmail.com) --- Comment #1 from Takashi Iwai --- Could you give the (full) dmesg outputs when the problem happens? Also, give the dmesg output from the working case (with the older kernel), as well as the output of hwinfo. Please upload those to Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c3 --- Comment #3 from Ben Thomas George --- Created attachment 854510 --> http://bugzilla.opensuse.org/attachment.cgi?id=854510&action=edit dmesg This is the dmesg. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c5 --- Comment #5 from Ben Thomas George --- Created attachment 854512 --> http://bugzilla.opensuse.org/attachment.cgi?id=854512&action=edit sudo journalctl -S "2021-12-12 07:00:00" -U "2021-12-13 14:00:00" This is the result of sudo journalctl -S "2021-12-12 07:00:00" -U "2021-12-13 14:00:00" > Journalctl.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c7 --- Comment #7 from Takashi Iwai --- (In reply to Ben Thomas George from comment #3)

Created attachment 854510 [details] dmesg

This is the dmesg.

Is this the dmesg output while the problem already appeared? I see nothing serious there though a quick glance; the devices were recognized, at least. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c9 --- Comment #9 from Ben Thomas George --- (In reply to Takashi Iwai from comment #7)

(In reply to Ben Thomas George from comment #3)

...

Created attachment 854510 [details] dmesg

This is the dmesg.

Is this the dmesg output while the problem already appeared?

I see nothing serious there though a quick glance; the devices were recognized, at least.

Now this was after I did a rollback (the old kernel). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c11 --- Comment #11 from Takashi Iwai --- (In reply to Ben Thomas George from comment #10)

(In reply to Takashi Iwai from comment #8)

...

For testing the kernel in OBS Kernel:stable repo, try kernel-default-5.15*.rpm from http://download.opensuse.org/repositories/Kernel:/stable/standard/x86_64/

and install it via zypper install kernel-default-5.15.*.rpm

Reboot and retest. After checking it, you can uninstall the package again.

After this should I give you the new dmesg?

And removing it will be - zypper rm kernel-default-5.15.*.rpm ?

The wildcard needs to be expanded by yourself. See the output of "rpm -q kernel-default". Or you can just roll back, of course :) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c13 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #854513|0 |1 is obsolete| | --- Comment #13 from Ben Thomas George --- Created attachment 854520 --> http://bugzilla.opensuse.org/attachment.cgi?id=854520&action=edit sudo journalctl -o short-precise -k -b -1 dmesg when problem first occured -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c15 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #854512|0 |1 is obsolete| | Attachment #854520|0 |1 is obsolete| | --- Comment #15 from Ben Thomas George --- Created attachment 854557 --> http://bugzilla.opensuse.org/attachment.cgi?id=854557&action=edit dmesg when the keyboard and mouse is not working After adding the kernel from OBS Kernel:stable repo, I did a system update to the latest snapshot of TW. And the same problem exists- That the keyboard and mouse stop working after a few minutes from boot. I am sorry, I just realized that the Journalctl logs were not very helpful (I looked that command online). Pls help me with this issue. This is the kernel dmesg when the the keyboard and mouse is NOT WORKING. In the next comment, I will attach the dmesg from the kernel 5.15.5-1 when it was working previously. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c19 --- Comment #19 from Ben Thomas George --- (In reply to Oliver Neukum from comment #18)

...

There is a line that indicates the error: [ 197.277038] xhci_hcd 0000:04:00.3: WARNING: Host System Error

Adding Oliver to Cc. This looks like a new issue.

That is unfortunately a diagnostic message that tells us that the HC itself thinks that it has crashed. It cannot be used to tell us what caused this condition. What is the last version know to not show this issue?

I did not face till problem till the till kernel 5.15.5-1. I did a rollback to the said kernel. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c24 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(benthomasgeorge78 | |99@gmail.com) | --- Comment #24 from Ben Thomas George --- Created attachment 854582 --> http://bugzilla.opensuse.org/attachment.cgi?id=854582&action=edit oliverneukum- Kernel 5.15.7-1-default dmesg I tried the new kernel and it seems to work. During install it showed an error- Subprocess failed. Error: RPM failed: warning: /var/cache/zypp/packages/https-download.opensuse.org-44785bde/x86_64/kernel-default-5.15.7-1.1.gbd72108.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 8b564654: NOKEY error: can't create transaction lock on /usr/lib/sysimage/rpm/.rpm.lock (Read-only file system But the system booted fine. I have been using this for some 15-20 mins now and it works fine. Do you want me keep this kernel version for the time-being or rollback to the v5.15.5-1? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c26 --- Comment #26 from Ben Thomas George --- Created attachment 854597 --> http://bugzilla.opensuse.org/attachment.cgi?id=854597&action=edit Did not shutdown the laptop. dmesg after 17hrs of uptime **UPDATE** I did a dmesg after 17hrs of uptime, although the wireless keyboard and mouse (single dongle) have not been working since my previous comment. I am going to do a rollback to v5.15.5-1 default. I am not sure but line 1867 shows this error - [11687.423550] usb 1-4: hub failed to enable device, error -108. does this error code 108 mean anything? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c30 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(benthomasgeorge78 | |99@gmail.com) | --- Comment #30 from Ben Thomas George --- Created attachment 854625 --> http://bugzilla.opensuse.org/attachment.cgi?id=854625&action=edit Dmesg of v5.15.5-1 default after 19 hours. **UPDATE** So the keyboard and mouse are working fine, with no errors. It has been an uptime of more than 19 Hrs and no issue. I am not switching off the laptop in case something shows up. I have a journalctl -r of your kernel, I will add that as an attachment in case you need it. I saved this log file just before rollback. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c33 --- Comment #33 from Ben Thomas George --- (In reply to Oliver Neukum from comment #32)

(In reply to Ben Thomas George from comment #31)

...

Created attachment 854644 [details] Second dmesg after 28 hrs

**UPDATE** So have the laptop running for 28Hrs. No issues at all. I have attached the the dmesg in case you find any error.

Keeping the laptop on. Will do a reboot if you want the logs after reboot.

This means that we have a regression after v5.15.5 that was not caused by a change to XHCI, because the only one that happened I reverted in the test kernel.

I am out of obvious culprits. Could you bisect?

What do you mean by bisect? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c37 --- Comment #37 from Ben Thomas George --- (In reply to Oliver Neukum from comment #36)

(In reply to Ben Thomas George from comment #35)

...

(In reply to Oliver Neukum from comment #34)

...

(In reply to Ben Thomas George from comment #33)

...

What do you mean by bisect?

This refers to the "git bisect" command which checks out the kernel in the middle between a known good and a known bad version, which you compile and test and theb repeat the process until you end up with the change that has caused a regression.

I am actually not very familiar with tech. Only know the basics to run it as a daily driver.

If you could instruct me step by step I could attempt this.

OK, we can try. Thank you for doing this big jump. The original is documented here: http://events17.linuxfoundation.org/sites/events/files/slides/ Enjoy%20Fighting%20regressions%20with%20git%20bisect%2C%20LinuxCon%20EU%20201 3.pdf

You'd start with cloning the stable tree:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-stable

This will give you a directory with the stable tree. You enter that directory and do

git bisect start ; git bisect good v5.15.5 ; git bisect bad v5.15.7

This will give you the first kernel tree to compile. Do you know how to compile a kernel?

No, I will haven't compiled the kernel yet. So the first step is cloning the stable tree -that is the kernel? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c42 --- Comment #42 from Ben Thomas George --- Created attachment 854699 --> http://bugzilla.opensuse.org/attachment.cgi?id=854699&action=edit dnesg Kernel 5.15.8-1 **UPDATE** So I did an update to Kernel 5.15.8-1 but the problem exists that my logitech keyboard and mouse is not working. But over that my HP laptop's keyboard was also acting up- like the shift key was auto-pressed continuously and the up arrow key was not working. Have rolled back to the v5.15.5-1 default which is working fine. Pls help solve this bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c44 --- Comment #44 from Ben Thomas George --- Created attachment 854722 --> http://bugzilla.opensuse.org/attachment.cgi?id=854722&action=edit journalctl -r I am adding the journalctl -r result just in case the reason of this may be cause by something else. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c47 --- Comment #47 from Ben Thomas George --- (In reply to Oliver Neukum from comment #45)

Just to be certain please test the kernel at https://build.opensuse.org/project/ monitor?project=home%3Aoneukum%3Absc1193652_83fc97405ba5d567d7fddb76fd1813cea bf1be87

**UPDATE** I have been using the Kernel v5.15.5-1.g83fc97 as instructed by you. And I have faced no issue at all so far. I have been using this since yesterday - woke my laptop from sleep, rebooted, powered it off and till now no issues!! This Kernel seems to have fixed the issue. What should be done next on my end? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c49 --- Comment #49 from Ben Thomas George --- Created attachment 854836 --> http://bugzilla.opensuse.org/attachment.cgi?id=854836&action=edit Dmesg Test Kernel 5.15.8-1 Default **UPDATE** So I updated yesterday, and till yesterday I was using the test kernel that was provided by you. So after the update it worked fine and today morning after I woke my laptop from sleep again the same problem continued. I am attaching the dmesg for the same. One thing that I notes that that it was not only the keyboard and mouse that were not working but none of the USB ports were working as i tried to insert a pen drive which too did not work. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c51 --- Comment #51 from Ben Thomas George --- Created attachment 855019 --> http://bugzilla.opensuse.org/attachment.cgi?id=855019&action=edit Dmesg of v5.15.12-1 **Update** I updated to the new kernel and the problem still exists. What should be done to resolve this issue? Thankyou -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c53 --- Comment #53 from Ben Thomas George --- (In reply to Takashi Iwai from comment #52)

Try 5.16-rc8 (found in OBS Kernel:HEAD repo), and if the problem persists, report it rather to the upstream. It's an upstream problem, after all.

**UPDATE** I am using the new kernel that was provided by you and it is working perfectly fine. This is after 3 hrs of uptime. I will keep the machine running. If this is solved with this kernel then what is the next step? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c55 --- Comment #55 from Ben Thomas George --- **UPDATE** The kernel you gave worked fine. But yesterday I did a zypper dup and it updated to the latest kernel in the kernel:HEAD and since that update the problem is back. What do you suggest i do? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c57 --- Comment #57 from Takashi Iwai --- (In reply to Ben Thomas George from comment #55)

**UPDATE** The kernel you gave worked fine.

Exactly which kernel?

But yesterday I did a zypper dup and it updated to the latest kernel in the kernel:HEAD and since that update the problem is back. What do you suggest i do?

Try to boot the previously working kernel and double-check that the problem really doesn't happen with it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c59 --- Comment #59 from Takashi Iwai --- You should be able to choose the previous kernel in GRUB menu. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c61 --- Comment #61 from Takashi Iwai --- There is no archive of the old packages for Kernel:HEAD, unfortunately. But now we've already moved to 5.16 final, let's check that again. First off, please confirm that the problem happens with the current kernel in OBS Kernel:stable repo, kernel-default-5.16.0-1.1.g487d6b3.x86_64.rpm. (Note that it's no Kernel:HEAD any longer.) Once after confirming it's broken, install the corresponding kernel-vanilla package, kernel-vanilla-5.16.0-1.1.g487d6b3.x86_64.rpm, boot with this kernel (choose in GRUB menu), and check whether the problem is seen with this kernel or not. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c63 --- Comment #63 from Ben Thomas George --- (In reply to Takashi Iwai from comment #61)

There is no archive of the old packages for Kernel:HEAD, unfortunately.

But now we've already moved to 5.16 final, let's check that again. First off, please confirm that the problem happens with the current kernel in OBS Kernel:stable repo, kernel-default-5.16.0-1.1.g487d6b3.x86_64.rpm. (Note that it's no Kernel:HEAD any longer.)

Once after confirming it's broken, install the corresponding kernel-vanilla package, kernel-vanilla-5.16.0-1.1.g487d6b3.x86_64.rpm, boot with this kernel (choose in GRUB menu), and check whether the problem is seen with this kernel or not.

I have been using the kernel 5.16.0-1.g487d6b3-default which was suggested by you and it is working fine. So did not try the kernel-vanilla. I will keep using it and report if there is any error. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c65 --- Comment #65 from Ben Thomas George --- Yesterday I did a zypper dup and installed the latest kernel from the main update repo and the same problem persists. The USB ports stopped working after I woke it up from sleep. But the kernel 5.16.0-1.g487d6b3-default #1 SMP PREEMPT Mon Jan 10 07:30:39 UTC 2022 (487d6b3), is working perfect and as expected. What should be done? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c67 --- Comment #67 from Ben Thomas George --- (In reply to Rainer Hurtado Navarro from comment #66)

(In reply to Ben Thomas George from comment #56)

...

Created attachment 855093 [details] Dmesg from kernel:HEAD repo after doing - sudo rmmod xhci_pci; sudo rmmod xhci_hcd; sudo modprobe xhci_pci and sudo modprobe xhci_hcd

**UPDATE**

So I posted this issue on the openSUSE community on reddit. And one of the users suggested that I do the following as he too had the same problem for a while now.

1. sudo rmmod xhci_pci 2. sudo rmmod xhci_hcd 3. sudo modprobe xhci_pci 4. sudo modprobe xhci_hcd

And it now works. I don't know what exactly this does. I am attaching the logs, but what do you think I should do from here?

The same I got (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

I have to constantly remove and load xhci_pci & xhci_hcd.

I'm looking for a fix.

As far as I am aware, there is no fix yet and I think that it is a kernel bug because Leap 15.4 uses the same kernel on which I first reported the bug while using tumbleweed. I had the same issue with Leap 15.4 Beta. So have shifted to Fedora 36 with kernel 5.18, and haven't had the issue since. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c69 --- Comment #69 from Rainer Hurtado Navarro --- Created attachment 859845 --> http://bugzilla.opensuse.org/attachment.cgi?id=859845&action=edit Lenovo's hwinfo -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c72 Rainer Hurtado Navarro changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(benthomasgeorge78 | |99@gmail.com) | --- Comment #72 from Rainer Hurtado Navarro --- Created attachment 860442 --> http://bugzilla.opensuse.org/attachment.cgi?id=860442&action=edit Lenovo's lspci -v -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c74 Dexter Foster changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dexter.1234@hotmail.com --- Comment #74 from Dexter Foster --- Just some additional info that might be useful. I posted some info in the opensuse forums in respose to another user asking about mouse/keyboard issues with Leap 15.4. Rather than repost that info, here is the link to the forum thread: https://forums.opensuse.org/showthread.php/572746-openSUSE-15-4-mouse-is-fre... Observations that were not posted in the forum that might be useful are as follows: 1. The mouse/keyboard issue never crashes the system. 2. When the mouse becomes non-responsive nothing shows up in dmesg or the system log. 3. When the keyboard becomes non-responsive nothing shows up in dmesg, however, the system log records the following: Aug 07 15:01:59 cylon gnome-shell[2866]: libinput error: event0 - Logitech Wireless Keyboard PID:4023: client bug: event processing lagging behind by 35ms, your system is too slow Aug 07 15:02:13 cylon gnome-shell[2866]: libinput error: event0 - Logitech Wireless Keyboard PID:4023: client bug: event processing lagging behind by 15ms, your system is too slow Aug 07 15:02:14 cylon gnome-shell[2866]: libinput error: event0 - Logitech Wireless Keyboard PID:4023: client bug: event processing lagging behind by 23ms, your system is too slow Aug 07 15:03:39 cylon gnome-shell[2866]: libinput error: event0 - Logitech Wireless Keyboard PID:4023: client bug: event processing lagging behind by 43ms, your system is too slow Aug 07 15:03:51 cylon gnome-shell[2866]: libinput error: event0 - Logitech Wireless Keyboard PID:4023: client bug: event processing lagging behind by 23ms, your system is too slow Aug 07 15:03:51 cylon gnome-shell[2866]: libinput error: event0 - Logitech Wireless Keyboard PID:4023: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. HTH -- You are receiving this mail because: You are on the CC list for the bug.