Public bug reported:
Environment:
- Source package: `apport`
- Ubuntu: `24.04.4 LTS`
- Installed Apport version: `2.28.3-0ubuntu0.1`
- Kernel: `7.1.5-070105-generic` (mainline build)
- Hardware: Dell Vostro 15 3515; AMD Raven USB controller `1022:15e0`
Expected behavior / requested enhancement:
- Handle USB host-controller failure events: `ACTION=offline`, `SUBSYSTEM=usb`,
`ERROR=DEAD`.
- Save a system problem report.
- Show a desktop warning explaining that a USB controller stopped responding
and some devices may be unavailable.
Actual behavior:
- A USB controller stopped responding. Built-in Bluetooth and a USB receiver
became unavailable.
- Bluetooth Settings showed “No Bluetooth found”. I saw no warning explaining
the failure.
- Unbinding and rebinding the controller's PCI driver restored both devices
without a reboot.
Evidence:
On September 22, 2026, at 11:44:17 (UTC+04:00), the kernel logged:
```text
xhci_hcd 0000:04:00.3: xHCI host not responding to stop endpoint command
xhci_hcd 0000:04:00.3: xHCI host controller not responding, assume dead
xhci_hcd 0000:04:00.3: HC died; cleaning up
```
- At the same time, udev ran Snap device helpers with action `offline` for
`0000:04:00.3/usb1`. This confirms delivery of the offline event. The journal
did not record its `ERROR` field.
- Apport's installed `50-apport.rules` handles Intel Wi-Fi firmware errors, but
not this USB event. The upstream `main`, `2.34` and `2.28` versions also lack a
USB failure rule.
- Apport did not create a report through another mechanism.
Existing implementation:
ChromiumOS passes this event to its crash reporter:
```udev
ACTION=="offline", SUBSYSTEM=="usb", ENV{ERROR}=="DEAD", \
RUN+="/sbin/crash_reporter --udev=SUBSYSTEM=usb:ACTION=dead"
```
- [Rule in the WhaleOS fork of
ChromiumOS](https://raw.githubusercontent.com/naverwhale/whaleos-platform2/main/crash-reporter/99-crash-reporter.rules)
- [Kernel discussion linking the ChromeOS
implementation](https://lkml.iu.edu/1904.2/02340.html)
Scope:
- Reporting and notification, not automatic resets or the cause of the
controller failure.
- I cannot reliably reproduce the failure.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apport 2.28.3-0ubuntu0.1
Uname: Linux 7.1.5-070105-generic x86_64
ApportLog: ERROR: apport (pid 1492486) 2026-09-29 13:31:20,262: host pid
1492485 crashed in a container without apport support
ApportVersion: 2.28.3-0ubuntu0.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 23:29:11 2026
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85
InstallationDate: Installed on 2021-12-04 (1760 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to noble on 2025-02-18 (588 days ago)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2168894
Title:
Feature request: report USB host-controller failures from udev events
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2168894/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
