All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Greg KH <gregkh@linuxfoundation.org>,
	Mario Limonciello <mario.limonciello@dell.com>
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 10:27:50 +0100	[thread overview]
Message-ID: <8c5d6edd-d41b-0d86-e0ea-d1a1689625de@molgen.mpg.de> (raw)
In-Reply-To: <X89ABDFgyjpQPeRq@kroah.com>

Dear Greg, dear Mario,


Am 08.12.20 um 09:57 schrieb Greg KH:
> On Tue, Dec 08, 2020 at 09:18:08AM +0100, Paul Menzel wrote:

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

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


Kind regards,

Paul

  reply	other threads:[~2020-12-08  9:28 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 [this message]
2020-12-08 18:16     ` Limonciello, Mario
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=8c5d6edd-d41b-0d86-e0ea-d1a1689625de@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mario.limonciello@dell.com \
    --cc=mathias.nyman@intel.com \
    /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.