linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Munteanu <rombert@apache.org>
To: Mathias Nyman <mathias.nyman@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: tiwai@suse.com, regressions@lists.linux.dev,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Regression: plugging in USB scanner breaks all USB functionality
Date: Thu, 02 Dec 2021 15:55:44 +0100	[thread overview]
Message-ID: <35f7428b39f996c793f5b4a6a314772681c73d7a.camel@apache.org> (raw)

Hi,

After updating from kernel 5.14.11 to 5.14.14 I am seeing the following
problem:

When plugging in an USB scanner ( Brother DSMobile DS-740D ) to my
Lenovo P52 laptop I lose connection to all USB devices. Not only are
the devices no longer available on the host, but no power is drawn by
them. Only a reboot fixes the problem.

The scanner is the only device that triggers the problem, even when it
is the only device plugged in. I have a host of other devices,
connected either directly or via a USB hub in my monitor:

- keyboard
- mouse
- logitech brio webcam
- yubikey
- stream deck
- microphone

None of these cause any issues.
I have tried the following kernels ( packaged for openSUSE Tumbleweed
), and none of them fixed the issue:

- 5.15.2
- 5.15.5
- 5.16~rc3-1.1.ge8ae228

The problem does not appear if the scanner is connected when the laptop
is shutdown. It seems to have an init phase of about 6-7 seconds
(blinking green led) and then stays on. However, it is not detected via
lsusb or scanimage -L.

The problem does not appear on a desktop class machine ( ASUS Prime
X470-PRO/Ryzen 3700x).

The relevant parts of the kernel log seem to be:

Nov 22 11:53:18 rombert kernel: xhci_hcd 0000:00:14.0: Abort failed to stop command ring: -110
Nov 22 11:53:18 rombert kernel: xhci_hcd 0000:00:14.0: xHCI host controller not responding, assume dead
Nov 22 11:53:18 rombert kernel: xhci_hcd 0000:00:14.0: HC died; cleaning up

I've initially reported this at
https://bugzilla.opensuse.org/show_bug.cgi?id=1192569 and CC'ed the
distribution's kernel maintainer.

Please let me know if additional information is needed.

Regards,
Robert Munteanu

             reply	other threads:[~2021-12-02 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 14:55 Robert Munteanu [this message]
2021-12-02 15:13 ` Thorsten Leemhuis
2021-12-03 17:24   ` Regression: plugging in USB scanner breaks all USB functionality #forregzbot Thorsten Leemhuis
2021-12-04 10:03     ` Greg KH
2021-12-04 10:26       ` Regression: plugging in USB scanner breaks all USB functionality Thorsten Leemhuis
2021-12-04 10:44         ` Greg KH
2021-12-04 11:06           ` Thorsten Leemhuis
2021-12-02 15:17 ` Greg Kroah-Hartman
2021-12-03 15:33   ` Robert Munteanu
2021-12-03 10:57 ` Mathias Nyman
2021-12-03 11:36   ` Takashi Iwai
2021-12-03 16:22     ` Robert Munteanu

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=35f7428b39f996c793f5b4a6a314772681c73d7a.camel@apache.org \
    --to=rombert@apache.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=tiwai@suse.com \
    --subject='Re: Regression: plugging in USB scanner breaks all USB functionality' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).