Re: usb usb1-port10: disabled by hub (EMI?), re-enabling...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Mario, dear Greg,


Am 08.12.20 um 19:16 schrieb Limonciello, Mario:
On a Dell Precision 3540/0M14W7, BIOS 1.9.1 07/06/2020

      $ lspci -nn | grep -i usb
      00:14.0 USB controller [0c03]: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller [8086:9ded] (rev 30)
      3a:00.0 USB controller [0c03]: Intel Corporation JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016] [8086:15db] (rev 02)

at each boot Linux 5.6 to 5.9 logs the error below.

      [   95.528190] usb usb1-port10: disabled by hub (EMI?), re-enabling...

Everything seems to be fine, so I wonder, why this is level error. Is it a
hardware error?

Yes, it is a hardware issue.

To me from your logs it looks like it's Intel BT device with this problem.
https://linux-hardware.org/index.php?id=usb:8087-0aaa

Does BT actually work after bootup completes?

Asking the user, and checking the device, no Bluetooth device is listed by GNOME.

BTW I notice that you are setting auto-suspend on your kernel command line.  Presumably
that's not the default for this module.  Is this possibly causing the behavior?

Good point. I removed it, and the behavior was the same.

Also I notice that you have an error loading firmware for the device.  You might check
that you have the latest firmware from linux-firmware.  If you do - maybe it's related
to the HW error?

[  105.743441] Bluetooth: hci0: Failed to send firmware data (-110)
[  105.743558] Bluetooth: hci0: sending frame failed (-19)
[  105.743633] Bluetooth: hci0: Intel reset sent to retry FW download

And lastly if you want to confirm it's actually BT causing the problem, I believe you
should be able to turn off BT in UEFI firmware setup.

Good idea. I did that, and disabling the BT device in the firmware (which took several seconds), the error was gone.

Thank you for the confirmation. Mario, do you know if this issues is
known to the Dell hardware team?

I'm sorry, I don't know.  You would need to work with the support team on a case.

My own opinion:
I would suspect you'll have a better result if there is a functional issue to show.

Thank you for your help. The device seems broken, but I’ll try to find some live system to rule out a problem with Debian.


Kind regards,

Paul



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux