xHCI (xhci_hcd) host controller not working after unattended kernel upgrade

[Ivo]

After the unattended-upgrade on January 5th (i.e. 5.4.0-92.103~18.04.2, automatic), the xHCI (xhci_hcd) host controller stopped working (i.e. no USB device is working):

===>dmesg log:
 linux1804 kernel: xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
 linux1804 kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
 linux1804 kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up
 linux1804 kernel: xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
 linux1804 kernel: usb 4-1: device not accepting address 2, error -108
 linux1804 kernel: usb usb4-port1: couldn't allocate usb_device
 linux1804 kernel: usb usb3-port1: couldn't allocate usb_device

===>unattended-upgrade info:
 Start-Date: 2022-01-05 11:08:54
 Commandline: /usr/bin/unattended-upgrade
 Install: linux-image-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules- extra-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-headers-5.4.0-92 -generic:amd64 (5.4.0-92.103~18.04.2, automatic), linux-hwe-5.4-headers-5.4.0-92:amd64 (5.4.0-92.103~18.04.2, automatic), linux-modules-5.4.0-92-generic:amd64 (5.4.0-92.103~18.04.2, automatic)
Upgrade: linux-headers-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-image-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82), linux-generic-hwe-18.04:amd64 (5.4.0.91.102~18.04.81, 5.4.0.92.103~18.04.82)
 End-Date: 2022-01-05 11:09:29

===>lsb_release -rd
Description: Ubuntu 18.04.6 LTS
Release: 18.04

===>Workaround:
This happens on any boot after power off. If I restart the computer, the problem is not reproducible.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: gdm 2060 F.... pulseaudio
                      igoretov 8697 F.... pulseaudio
 /dev/snd/controlC0: gdm 2060 F.... pulseaudio
                      igoretov 8697 F.... pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-07-15 (913 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: ASUSTeK COMPUTER INC. N551JW
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=446babcc-3c36-4899-ac47-f721db732d2a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.4.0-92.103~18.04.2-generic 5.4.157
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-92-generic N/A
 linux-backports-modules-5.4.0-92-generic N/A
 linux-firmware 1.173.20
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: bionic
Uname: Linux 5.4.0-92-generic x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: False
dmi.bios.date: 01/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N551JW.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N551JW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN551JW.202:bd01/16/2015:svnASUSTeKCOMPUTERINC.:pnN551JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N551JW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1956760/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1956760

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

apport information

[Ivo (dexbg)]

It is strange that after restart (i.e. the Lsusb.txt contains the info for a boot after power off), the lsusb command output has quite different results:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 05e3:0612 Genesys Logic, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 005: ID 13d3:5188 IMC Networks
Bus 003 Device 003: ID 8087:07dc Intel Corp.
Bus 003 Device 008: ID 1908:0226 GEMBIRD
Bus 003 Device 007: ID 046d:0a8f Logitech, Inc.
Bus 003 Device 006: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 003 Device 004: ID 076b:3021 OmniKey AG CardMan 3121
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[Paul White (paulw2u)]

Ivo, in comment #1 you were asked to run the apport-collect command (which you did) and change the status to 'Confirmed' (which you didn't).

I'm changing the status for you now so that the bug report now comes to the attention of the kernel team.

If this issue has been resolved with an update since you first raised the bug report then please let the kernel team know. Thank you.

[Ivo (dexbg)]

I can confirm that now, with the latest updates, I cannot reproduce the problem.

[Ivo (dexbg)]

I guess the problem is already fixed in a newer version because I cannot reproduce it anymore.