All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <Mario.Limonciello@dell.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	USB list <linux-usb@vger.kernel.org>
Subject: RE: usb usb1-port10: disabled by hub (EMI?), re-enabling...
Date: Tue, 8 Dec 2020 18:16:16 +0000	[thread overview]
Message-ID: <DM6PR19MB2636B65562B4A768A9629E94FACD0@DM6PR19MB2636.namprd19.prod.outlook.com> (raw)
In-Reply-To: <8c5d6edd-d41b-0d86-e0ea-d1a1689625de@molgen.mpg.de>

> >> 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?

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?

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.

> 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.

  reply	other threads:[~2020-12-08 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08  8:18 usb usb1-port10: disabled by hub (EMI?), re-enabling Paul Menzel
2020-12-08  8:57 ` Greg KH
2020-12-08  9:27   ` Paul Menzel
2020-12-08 18:16     ` Limonciello, Mario [this message]
2020-12-12 11:01       ` Paul Menzel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR19MB2636B65562B4A768A9629E94FACD0@DM6PR19MB2636.namprd19.prod.outlook.com \
    --to=mario.limonciello@dell.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.