linux-firmware 1.187.24 may crash USB ports

Bug #1956518 reported by Alvaro Morera
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Invalid
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

Description: Ubuntu 20.04.3 LTS
Release: 20.04
5.4.0-92-generic

linux-firmware:
  Instalados: 1.187.24
  Candidato: 1.187.24
  Tabla de versión:
 *** 1.187.24 500
        500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1.187 500
        500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages

linux-firmware 1.187.24 upgrade disabled all mainboard USB ports.
USB keyboard and mouse stopped working on the next reboot after upgrade.
I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality.
My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: alvaro 2225 F.... pulseaudio
 /dev/snd/controlC0: alvaro 2225 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Dependencies:

DistroRelease: Ubuntu 20.04
HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a
InstallationDate: Installed on 2014-10-25 (2634 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
IwConfig:
 lo no wireless extensions.

 enp7s0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. B365M H
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux-firmware 1.187.24
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-92-generic N/A
 linux-backports-modules-5.4.0-92-generic N/A
 linux-firmware 1.187.24
RfKill:
 2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: focal
Uname: Linux 5.4.0-92-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago)
UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video
_MarkForUpload: True
dmi.bios.date: 08/18/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4b
dmi.board.asset.tag: Default string
dmi.board.name: B365M H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B365M H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Alvaro Morera (servicenginic) wrote :
Revision history for this message
Juerg Haefliger (juergh) wrote :

Can you run 'apport-collect 1956518' when the system is in that (broken) state?
What kind of USB BT key are you using?

tags: added: kern-1832
Revision history for this message
Alvaro Morera (servicenginic) wrote : Re: [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports
Download full text (30.9 KiB)

Thank you for your kind interest.

After the first successful reboot, I've not been able to reproduce the
described problem, even reconnecting the same USB Bluetooth key to the
same original or other USB ports.
When the problem was on course, it was very annoying. I tried several
reboots, and there were not keyboard or mouse response on Linux log-in
screen.
Entering BIOS was possible, and both keyboard and mouse worked as intended.
I have anydesk installed at the affected host. I tried entering by means
a remote session, and everything appeared to be working, but local USB
keyboard, mouse, or other USB devices.
I then tried to remove Bluetooth key from its USB port, I rebooted, and
everything returned to normality.
The only identifying data at problematic USB Bluetooth key is the
"zaapa" inscription. No model, type, serial number, or other information.
I below attach the listing for a 'sudo lshw' command from the same
affected system with the Bluetooth USB key connected. But now everything
is working normal...

Best regards,
Alvaro Morera

El 6/1/22 a las 10:14, Juerg Haefliger escribió:
> Can you run 'apport-collect 1956518' when the system is in that (broken) state?
> What kind of USB BT key are you using?
>
> ** Tags added: kern-1832
>
alvaro@ALVARO:~$ sudo lshw
[sudo] contraseña para alvaro:
alvaro
     descripción: Equipo de escritorio
     producto: B365M H (Default string)
     fabricante: Gigabyte Technology Co., Ltd.
     versión: Default string
     serie: Default string
     anchura: 64 bits
     capacidades: smbios-3.1.1 dmi-3.1.1 smp vsyscall32
     configuración: boot=normal chassis=desktop family=Default string
sku=Default string uuid=B4022E03-9904-EC05-BB06-110700080009
   *-core
        descripción: Placa base
        producto: B365M H
        fabricante: Gigabyte Technology Co., Ltd.
        id físico: 0
        versión: x.x
        serie: Default string
        ranura: Default string
      *-firmware
           descripción: BIOS
           fabricante: American Megatrends Inc.
           id físico: 0
           versión: F4b
           date: 08/18/2020
           tamaño: 64KiB
           capacidad: 16MiB
           capacidades: pci upgrade shadowing cdboot bootselect
socketedrom edd int13floppy1200 int13floppy720 int13floppy2880
int5printscreen int14serial int17printer acpi usb biosbootspecification uefi
      *-memory
           descripción: Memoria de sistema
           id físico: 35
           ranura: Placa de sistema o placa base
           tamaño: 16GiB
         *-bank:0
              descripción: DIMM DDR4 Síncrono Unbuffered (Unregistered)
2400 MHz (0,4 ns)
              producto: 9905702-137.A00G
              fabricante: Kingston
              id físico: 0
              serie: FA359B27
              ranura: ChannelA-DIMM0
              tamaño: 8GiB
              anchura: 64 bits
              reloj: 2400MHz (0.4ns)
         *-bank:1
              descripción: Project-Id-Version: lshwReport-Msgid-Bugs-To:
FULL NAME <EMAIL@ADDRESS>PO-Revision-Date: 2012-03-14
06:38+0000Last-Translator: Paco Molinero <email address hidden>Language-Team:
Spanish <email address hidden>MIME-Version: 1.0Content-Type: text/plain;
charset=UT...

Revision history for this message
You-Sheng Yang (vicamo) wrote :

"Hi! This is on a Lenovo Thinkpad Type 3259. Today's Linux Firmware update (1.187.24) killed the 3 USB ports on the left side of the computer."

"Ubuntu Linux
Mainboard Z390 UD
linux-firmware 1.187.24 + 5.4.0-92-generic kernel upgrade disabled all mainboard USB ports also for me.
USB keyboard, mouse, nor other USB devices are not recognized.
I'm writing this by means of a remote session from my mobile!"

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-firmware (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Graham (chrisgraham) wrote :

This seems to be affecting me too.
Around the time the firmware package was updated (plus other kernel-related packages), I started having serious problems with USB during boot.
I cannot really be sure it isn't a hardware problem, but I am able to use MacOS okay (this is an iMac).

I boot off of an external SSD. To get boot to work I have to unplug my external HDD and my USB hub, and then plug them back in after the kernel has successfully mounted the SSD. Otherwise I get USB timeouts and get dumped into an emergency prompt.

Additionally, sometimes the USB mouse stops working. This has occasionally happened in the past and I've just have to reseat it in the USB hub. Now I have to remove power to the USB hub and unplug the USB hub from the machine, and then plug it all back. i.e. a hard-reset of the whole USB hub. This is with one USB hub, but I also tried another.

Something is seriously broken with USB.

Is there a supported way to backroll the firmware?

Revision history for this message
Alvaro Morera (servicenginic) wrote :

Since USB ports blockage seems to happen when entering Linux environment, a possible workaround to try in systems with intagrated bluetooth would be entering BIOS setup and disabling bluotooth, or pressing bluetooth disabling key where available.
In systems with external USB bluetooth key, action to try would be to disconnect external bluetooth device and rebooting, as it worked in my case.

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Hi, if you suspect your system is related to this issue, you may want to try launch an Ubuntu Live CD, mount the on disk root filesystem, and remove /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin .

Revision history for this message
You-Sheng Yang (vicamo) wrote :

And for those who's convenient, please download

  https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin?h=master&id=9e4092255a5a0899556c4049723061a5e7081d88

overwrite your /lib/firmware/mediatek/BT_RAM_CODE_MT7961_1_2_hdr.bin and comment the results here. We don't have the hardware to investigate it more yet. And please create a bug or do apport-collect on the affected system when available.

Revision history for this message
Juerg Haefliger (juergh) wrote :

We need more data. Please run 'apport-collect 1956518' with the device plugged in that you believe is causing issues.

Revision history for this message
Pawel W (shamdog) wrote (last edit ):

I have the same problem with Dell Latitude E7440, Ubuntu 20.04, after an update to kernel 5.4.0-92, and having linux-firmware 1.187.24.

1) I'm using a UGreen USB Switch to switch between the inputs of keyboard, mouse and audio between two stations
2) After the kernel and linux-firmware upgrade I did a reboot, the system took much longer to start (console shown "failed to enumerate USB devices"), when it did boot external keyboards and mouse wasn't working
3) Pluging in any device directly to laptop's USB port does not work
4) I've managed to get the external keyboard and mouse to work by disabling the Bluetooth in Ubuntu settings and rebooting back to 5.4.0-91 (worked via USB Switch)
5) However after another reboot to 5.4.0-91, USB ports stopped working again

Another observation, strange - I'm typing this with the external keyboard again, seems the USB ports started working after ~15 minutes out of the blue.. They were connected all the time, I was using the laptop's keyboard, and decided to give the external keyboard a shot - it worked, mouse as well. Seems my point number 4 above could be related - when I was trying to boot to 5.4.0-91 I've actually stepped out for an hour or so, so when I came back the peripherals were working. Could be the same ~15 minute wait time solution, not due to the kernel change.

Revision history for this message
Alvaro Morera (servicenginic) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
Alvaro Morera (servicenginic) wrote : CRDA.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : Lspci.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : Lspci-vt.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : Lsusb.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : Lsusb-t.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : Lsusb-v.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : ProcModules.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : PulseList.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : UdevDb.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : WifiSyslog.txt

apport information

Revision history for this message
Alvaro Morera (servicenginic) wrote : acpidump.txt

apport information

Revision history for this message
jan.t.neurer (neurer) wrote :

Similar issue; also Thinkpad. All USB ports break when connecting a specific USB device during runtime. If the specific device is already connected during boot, it'll work fine.

uname -a
Linux think 5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

dpkg --list linux-firmware
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii linux-firmware 1.187.24 all Firmware for Linux kernel drivers

dmesg -w
[46438.144293] xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
[46438.144300] xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
[46438.144318] xhci_hcd 0000:00:14.0: HC died; cleaning up
[46438.144377] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[46438.144384] clocksource: timekeeping watchdog on CPU5: Marking clocksource 'tsc' as unstable because the skew is too large:
[46438.144386] clocksource: 'acpi_pm' wd_now: 733873 wd_last: b63823 mask: ffffff
[46438.144388] clocksource: 'tsc' cs_now: 542df475a1df cs_last: 542c599b562b mask: ffffffffffffffff
[46438.144389] tsc: Marking TSC unstable due to clocksource watchdog
[46438.144400] usb 1-2: USB disconnect, device number 2
[46438.144403] usb 1-2.3: USB disconnect, device number 4
[46438.144405] usb 1-2.3.3: USB disconnect, device number 7
[46438.144406] usb 1-2.3.3.1: USB disconnect, device number 14
[46438.144607] usb 1-2.3.3.2: USB disconnect, device number 10
[46438.144845] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
[46438.144846] sched_clock: Marking unstable (46438131062428, 13782220)<-(46438199993798, -55148943)
[46438.144884] clocksource: Checking clocksource tsc synchronization from CPU 3.
[46438.144906] clocksource: Switched to clocksource acpi_pm
[46438.216564] usb 1-2.3.3.3: USB disconnect, device number 11
[46438.216568] usb 1-2.3.3.3.1: USB disconnect, device number 12
[46438.481130] usb 1-2.3.3.3.2: USB disconnect, device number 13
[46438.528512] usbhid 1-2.3.3.3.2:1.0: Razer Device disconnected
[46438.608575] usbhid 1-2.3.3.3.2:1.1: Razer Device disconnected
[46438.720839] usbhid 1-2.3.3.3.2:1.2: Razer Device disconnected
[46438.722739] usb 1-5: USB disconnect, device number 3
[46438.722974] usb 1-6: USB disconnect, device number 5
[46438.728331] usb 2-4: device not accepting address 5, error -108
[46438.728409] usb usb2-port4: couldn't allocate usb_device
[46438.728428] usb 2-2: USB disconnect, device number 2
[46438.728434] usb 2-2.1: USB disconnect, device number 3
[46438.784605] usb 1-8: USB disconnect, device number 6
[46438.816916] usb 2-2.3: USB disconnect, device number 4

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Hi, Neurer and Pawel or anyone affected, please file a new bug of your own so that you can run apport-collect to submit more hardware information. Please also help paste your bug link here for further reference.

Revision history for this message
jan.t.neurer (neurer) wrote :

My (corporate) config does not contain the apport and respectively the apport-collect package. My user is also not in the sudo group. End of the line for me i suppose. Came across another bug report though, which appears to be related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849

Revision history for this message
Pawel W (shamdog) wrote :

Tried to get apport-collect log via https://bugs.launchpad.net/ubuntu/+bug/1958512 but only a popup with "no additional information has been gathered" shows up, will try again in the evening / tomorrow

Revision history for this message
You-Sheng Yang (vicamo) wrote :

We're to backport new firmware updates for MT7921 in bug 1958286. Expecting landing in 1.187.26 or later.

Revision history for this message
Alan H (hincha) wrote :

I'm seeing something that seems similar, but with 1.187.25, i think. Is this related? https://ubuntuforums.org/showthread.php?t=2471244

Revision history for this message
john crosbie (johnecrosbie) wrote :

I am having similar issues. Writing to an SDCard sometimes kills all USB ports. I can recover all USB ports by logging in over ssh and running the following script:

for port in $(lspci | grep USB | cut -d' ' -f1); do
    echo -n "0000:${port}"| sudo tee /sys/bus/pci/drivers/xhci_hcd/unbind;
    sleep 5;
    echo -n "0000:${port}" | sudo tee /sys/bus/pci/drivers/xhci_hcd/bind;
    sleep 5;
done

This has happened 3 or 4 times in the last 2 weeks and each time I can recover without reboot.

Revision history for this message
Juerg Haefliger (juergh) wrote :

Can you please install the latest linux-firwmare 1.187.26 and let us know if you're still experiencing the problems?

Changed in linux-firmware (Ubuntu Focal):
status: New → Incomplete
Changed in linux-firmware (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Pawel W (shamdog) wrote :

I can say that with the recent update - linux-firmware 1.187.29 - the issues are no longer present.

Revision history for this message
Juerg Haefliger (juergh) wrote :

Closing the issue as resolved. Please open a new ticket if you experience the problem again.

Changed in linux-firmware (Ubuntu Focal):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.