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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee 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 the assignee for the bug.

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

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

...

(In reply to Oliver Neukum from comment #38)

...

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

...

So the first step is cloning the stable tree -that is the kernel?

Yes. To be precise that is the stable releases of the kernel, not the development tree. As you are seeing a regression between two stable branches let's begin there.

ok... how to start and where to start? is it possible to do a meet real-time on jitsi or google meet?

Can you give me a URL?

https://meet.jit.si/git-bisect -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c43 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(benthomasgeorge78 | |99@gmail.com) | --- Comment #43 from Ben Thomas George --- Created attachment 854721 --> http://bugzilla.opensuse.org/attachment.cgi?id=854721&action=edit Dmesg of v5.15.8-1.1 **UPDATE** So today again saw a new kernel update. The problem exists. The keyboard worked through the encryption password entering and stopped at the login screen. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c46 --- Comment #46 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

Will update you seen after testing -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c48 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(benthomasgeorge78 | |99@gmail.com) | --- Comment #48 from Ben Thomas George --- Created attachment 854762 --> http://bugzilla.opensuse.org/attachment.cgi?id=854762&action=edit Dmesg Test Kernel 5.15.5-1.g83fc97 I am adding the dmesg too. Thank you for your time put into this!! -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 Ben Thomas George changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Logitech mouse and keyboard |Mouse and keyboard / USB |stop working on the latest |ports stop working on the |kernel. |latest kernel. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c50 --- Comment #50 from Ben Thomas George --- Created attachment 854883 --> http://bugzilla.opensuse.org/attachment.cgi?id=854883&action=edit dmesg of latest update **UPDATE** Hi! I updated the laptop again and after a few minutes of login the USB ports stop responding. So the USB dongle mouse and keyboard and mouse and also the pendrive is also not working. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c52 --- Comment #52 from Takashi Iwai --- 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. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c54 --- Comment #54 from Takashi Iwai --- It's a good news. Then please keep using it and confirm that it's really working well. We're going to switch to 5.16 in a few days (on the next Sunday or Monday) once after 5.16 reaches to the final, so the issue will be automagically "fixed" sooner or later. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c56 --- Comment #56 from Ben Thomas George --- Created attachment 855093 --> http://bugzilla.opensuse.org/attachment.cgi?id=855093&action=edit 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? -- You are receiving this mail because: You are the assignee for the bug.

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

(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.

I am sorry but I could not find the other kernel in the snapshots to reload it. It was the v5.16-rc8 that i downloaded from the Kernel:HEAD on Jan 6, around 10:00 UTC. -- You are receiving this mail because: You are the assignee for the bug.

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

You should be able to choose the previous kernel in GRUB menu.

I am really sorry about the mess up. I looked into the grub menu and it has some previous versions and double checked the snapshots too but i think the snapshots have been deleted from that kernel. Is there a way I can build that version again. If that is possible I can try that with some help. Again I would apologize about this mess up. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c62 --- Comment #62 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 corresponpatient ding 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.

Thank you for being (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.

Thank you for being patient with me. I will do and inform you the results. -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c64 --- Comment #64 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.

** UPDATE ** I have been using this kernel till now. What is to be done next? Thank you -- You are receiving this mail because: You are the assignee for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1193652 http://bugzilla.opensuse.org/show_bug.cgi?id=1193652#c66 Rainer Hurtado Navarro changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |publio.escipion.el.africano | |@gmail.com --- Comment #66 from Rainer Hurtado Navarro --- (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... I have to constantly remove and load xhci_pci & xhci_hcd. I'm looking for a fix. -- You are receiving this mail because: You are the assignee for the bug.