[arch-general] xhci_hcd support broken [was: Bluetooth no more working after update]

Peter Nabbefeld peter.nabbefeld at gmx.de
Sat Aug 28 14:52:36 UTC 2021 

Hello Dirk,

Thank You for the pointer. The firmware module mentioned there is
related to renesas chipsets, while mine is an integrated intel chip:

$ lspci -vvv -s 00:14.0
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB xHCI (rev 05) (prog-if 30 [XHCI])
     Subsystem: CLEVO/KAPOK Computer Device 7481
     Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
     Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
     Latency: 0
     Interrupt: pin A routed to IRQ 32
     Region 0: Memory at f7b00000 (64-bit, non-prefetchable) [size=64K]
     Capabilities: <access denied>
     Kernel driver in use: xhci_hcd
     Kernel modules: xhci_pci

So I'm still searching for a solution ... :(

Kind regards,
Peter




Am 28.08.21 um 12:42 schrieb Dirk via arch-general:
> You can find information on this message on the Arch Wiki (as always) at:
>
> https://wiki.archlinux.org/title/Mkinitcpio
>
> Regards,
> Dirk
>
> On 28-08-2021 10:16, Peter Nabbefeld via arch-general wrote:
>> Hi,
>>
>> today a new version of the Linux kernel has been installed (5.13.13),
>> and I noticed following message:
>>
>> ==> WARNING: Possibly missing firmware for module: xhci_pci
>>
>> Do I need this additional firmware, and where can I get it?
>>
>> Kind regards,
>> Peter
>>
>>
>> Am 27.08.21 um 08:25 schrieb Peter Nabbefeld via arch-general:
>>>
>>> After some research, I've found many complaints on xhci_hcd driver with
>>> Linux kernel 5.13.x, some versions seem to work, some not, some with
>>> workarounds. So I'd say, in general USB 3.0 support seems to be broken
>>> currently (depending on device and kernel version).
>>>
>>> Anything I can do to get USB 3.0 working again?
>>>
>>> Kind regards
>>> Peter
>>>
>>>
>>>
>>> Am 26.08.21 um 19:46 schrieb Peter Nabbefeld via arch-general:
>>>>
>>>> Hello,
>>>>
>>>> the bluetooth problem seems to be caused by USB driver problems.
>>>> This is
>>>> the output of "lsusb -t":
>>>>
>>>> $ lsusb -t
>>>> /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
>>>> /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
>>>>     |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
>>>>     |__ Port 4: Dev 106, If 0, Class=Wireless, Driver=btusb, 12M
>>>>     |__ Port 4: Dev 106, If 1, Class=Wireless, Driver=btusb, 12M
>>>>     |__ Port 6: Dev 7, If 0, Class=Human Interface Device,
>>>> Driver=usbhid, 12M
>>>>     |__ Port 6: Dev 7, If 1, Class=Human Interface Device,
>>>> Driver=usbhid, 12M
>>>>     |__ Port 10: Dev 8, If 0, Class=Video, Driver=uvcvideo, 480M
>>>>     |__ Port 10: Dev 8, If 1, Class=Video, Driver=uvcvideo, 480M
>>>> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>>>>     |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
>>>> /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
>>>>     |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
>>>>
>>>> The address of the bluetooth adapter (here: Dev 106) is changing
>>>> all the
>>>> time, as the device cannot be initialized since August, 18th. Does
>>>> anybody know, what's going on?
>>>>
>>>> Kind regards
>>>> Peter
>>>>
>>>>
>>>> Am 22.08.21 um 21:43 schrieb Peter Nabbefeld via arch-general:
>>>>>
>>>>> Hello,
>>>>>
>>>>> after updating my arch installation, bluetooth stopped working.
>>>>> "systemctl status bluetooth" shows the service is active, but when I
>>>>> try
>>>>> to power on or list my bluetooth device using bluetoothctl, no
>>>>> device is
>>>>> found.
>>>>>
>>>>> Head lines of dmesg output:
>>>>>
>>>>> [ 2951.799457] usb 3-4: New USB device strings: Mfr=0, Product=0,
>>>>> SerialNumber=0
>>>>> [ 2953.533019] usb 3-4: USB disconnect, device number 75
>>>>> [ 2953.811506] Bluetooth: hci0: command 0x0c03 tx timeout
>>>>> [ 2956.823879] audit: type=1131 audit(1629640847.196:664): pid=1
>>>>> uid=0
>>>>> auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill
>>>>> comm="systemd"
>>>>> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
>>>>> res=success'
>>>>> [ 2961.918096] Bluetooth: hci0: sending initial HCI reset command
>>>>> failed
>>>>> (-110)
>>>>> [ 2961.926281] audit: type=1130 audit(1629640852.299:665): pid=1
>>>>> uid=0
>>>>> auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill
>>>>> comm="systemd"
>>>>> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
>>>>> res=success'
>>>>> [ 2962.174751] usb 3-4: new full-speed USB device number 76 using
>>>>> xhci_hcd
>>>>> [ 2962.298118] usb 3-4: device descriptor read/64, error -71
>>>>> [ 2962.528098] usb 3-4: device descriptor read/64, error -71
>>>>> [ 2962.761408] usb 3-4: new full-speed USB device number 77 using
>>>>> xhci_hcd
>>>>> [peter at tuchola ~]$ sudo dmesg | head -n 20
>>>>> [ 2999.934381] usb 3-4: new full-speed USB device number 88 using
>>>>> xhci_hcd
>>>>> [ 3000.057683] usb 3-4: device descriptor read/64, error -71
>>>>> [ 3000.287770] usb 3-4: device descriptor read/64, error -71
>>>>> [ 3000.517708] usb 3-4: new full-speed USB device number 89 using
>>>>> xhci_hcd
>>>>> [ 3000.641059] usb 3-4: device descriptor read/64, error -71
>>>>> [ 3000.871018] usb 3-4: device descriptor read/64, error -71
>>>>> [ 3000.977743] usb usb3-port4: attempt power cycle
>>>>> [ 3001.381075] usb 3-4: new full-speed USB device number 90 using
>>>>> xhci_hcd
>>>>> [ 3001.381293] usb 3-4: Device not responding to setup address.
>>>>> [ 3001.587720] usb 3-4: Device not responding to setup address.
>>>>> [ 3001.794365] usb 3-4: device not accepting address 90, error -71
>>>>> [ 3002.124364] usb 3-4: new full-speed USB device number 91 using
>>>>> xhci_hcd
>>>>> [ 3002.142567] usb 3-4: New USB device found, idVendor=8087,
>>>>> idProduct=07dc, bcdDevice= 0.01
>>>>> [ 3002.142573] usb 3-4: New USB device strings: Mfr=0, Product=0,
>>>>> SerialNumber=0
>>>>> [ 3003.876301] usb 3-4: USB disconnect, device number 91
>>>>> [ 3004.157679] Bluetooth: hci0: command 0x0c03 tx timeout
>>>>> [ 3007.165585] audit: type=1131 audit(1629640897.539:672): pid=1
>>>>> uid=0
>>>>> auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill
>>>>> comm="systemd"
>>>>> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
>>>>> res=success'
>>>>> [ 3012.264321] Bluetooth: hci0: sending initial HCI reset command
>>>>> failed
>>>>> (-110)
>>>>> [ 3012.273674] audit: type=1130 audit(1629640902.646:673): pid=1
>>>>> uid=0
>>>>> auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill
>>>>> comm="systemd"
>>>>> exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
>>>>> res=success'
>>>>> [ 3012.520945] usb 3-4: new full-speed USB device number 92 using
>>>>> xhci_hcd
>>>>>
>>>>>
>>>>> My bluetooth device:
>>>>> Bus 003 Device 103: ID 8087:07dc Intel Corp. Bluetooth wireless
>>>>> interface
>>>>>
>>>>>
>>>>> "lsusb -v" shows lots of details, e.g.
>>>>>
>>>>> Device Descriptor:
>>>>>   bLength                18
>>>>>   bDescriptorType         1
>>>>>   bcdUSB               2.00
>>>>>   bDeviceClass          224 Wireless
>>>>>   bDeviceSubClass         1 Radio Frequency
>>>>>   bDeviceProtocol         1 Bluetooth
>>>>>   bMaxPacketSize0        64
>>>>>   idVendor           0x8087 Intel Corp.
>>>>>   idProduct          0x07dc Bluetooth wireless interface
>>>>>   bcdDevice            0.01
>>>>>   iManufacturer           0
>>>>>   iProduct                0
>>>>>   iSerial                 0
>>>>>   bNumConfigurations      1
>>>>> ...
>>>>>
>>>>> but ends with the following lines:
>>>>> can't get device qualifier: Resource temporarily unavailable
>>>>> can't get debug descriptor: Resource temporarily unavailable
>>>>> cannot read device status, No such device (19)
>>>>>
>>>>> I guess there's sth. broken with the driver (or now driver
>>>>> assigned at
>>>>> all).
>>>>>
>>>>> When looking into /usr/lib/firmware, I see many if not all updates of
>>>>> August, 18th, and especially many files with pattern
>>>>> "iwlwifi-*.ucode",
>>>>> which might related to my problem.
>>>>>
>>>>> I already searched the internet, but couldn't find anything useful
>>>>> :-/
>>>>>
>>>>> However, I found this:
>>>>> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1591167
>>>>>
>>>>> While it seems not to be the same, it led me to looking for
>>>>> ibt-*.* and
>>>>> especially to
>>>>> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> I found those files locally in /usr/lib/firmware/intel, same date for
>>>>> latest update as for "iwlwifi-*.ucode", so everything should
>>>>> usually be
>>>>> fine.
>>>>>
>>>>> How can I check, if the firmware has been installed/loaded properly?
>>>>> How can I find out, which is the correct firmware?
>>>>>
>>>>>
>>>>> Kind regards
>>>>> Peter
>>>>
>>>
>>

More information about the arch-general mailing list