linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Robert Munteanu <rombert@apache.org>,
	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: Re: Regression: plugging in USB scanner breaks all USB functionality
Date: Thu, 2 Dec 2021 16:13:39 +0100	[thread overview]
Message-ID: <3eb9c3f8-6bca-da08-47ec-af2a02d6a485@leemhuis.info> (raw)
In-Reply-To: <35f7428b39f996c793f5b4a6a314772681c73d7a.camel@apache.org>

Hi, this is your Linux kernel regression tracker speaking.

Thanks for the report.

Top-posting for once, to make this easy accessible to everyone.

FWIW, 5.14 is EOL, so it might not be fixed there. As the problem is in
newer kernels as well, I suspect that it was a change applies to 5.15 or
5.16 that got backported. Maybe one of the developers might have an idea
which commit causes it. If that's not the case you likely should try a
bisection to find the culprit. Performing one between v5.14.11..v5.14.14
is likely the easiest and quickest way to find it.

To be sure this issue doesn't fall through the cracks unnoticed, I'm
adding it to regzbot, my Linux kernel regression tracking bot:

#regzbot ^introduced v5.14.11..v5.14.14
#regzbot title usb: plugging in USB scanner breaks all USB functionality
[regression present in 5.15.2 und 5.16-rc3, too]
#regzbot ignore-activity

Reminder for developers: when fixing the issue, please add a 'Link:' tag
with the URL to the report (the parent of this mail), then regzbot will
automatically mark the regression as resolved once the fix lands in the
appropriate tree. For more details about regzbot see footer.

Sending this to everyone that got the initial report, to make all aware
of the tracking. I also hope that messages like this motivate people to
directly get regzbot involved when dealing with regressions, as messages
like this wouldn't be needed then.

Don't worry, I'll send further messages wrt to this regression just to
the lists (with a tag in the subject so people can filter them away), as
long as they are intended just for regzbot. With a bit of luck no such
messages will be needed anyway.

Ciao, Thorsten, your Linux kernel regression tracker.

P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
on my table. I can only look briefly into most of them. Unfortunately
therefore I sometimes will get things wrong or miss something important.
I hope that's not the case here; if you think it is, don't hesitate to
tell me about it in a public reply. That's in everyone's interest, as
what I wrote above might be misleading to everyone reading this; any
suggestion I gave they thus might sent someone reading this down the
wrong rabbit hole, which none of us wants.

BTW, I have no personal interest in this issue, which is tracked using
regzbot, my Linux kernel regression tracking bot
(https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
this mail to get things rolling again and hence don't need to be CC on
all further activities wrt to this regression.

---
Additional information about regzbot:

If you want to know more about regzbot, check out its web-interface, the
getting start guide, and/or the references documentation:

https://linux-regtracking.leemhuis.info/regzbot/
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md

The last two documents will explain how you can interact with regzbot
yourself if your want to.

Hint for reporters: when reporting a regression it's in your interest to
tell #regzbot about it in the report, as that will ensure the regression
gets on the radar of regzbot and the regression tracker. That's in your
interest, as they will make sure the report won't fall through the
cracks unnoticed.

Hint for developers: you normally don't need to care about regzbot once
it's involved. Fix the issue as you normally would, just remember to
include a 'Link:' tag to the report in the commit message, as explained
in Documentation/process/submitting-patches.rst
That aspect was recently was made more explicit in commit 1f57bd42b77c:
https://git.kernel.org/linus/1f57bd42b77c

On 02.12.21 15:55, Robert Munteanu wrote:
> 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:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 14:55 Robert Munteanu
2021-12-02 15:13 ` Thorsten Leemhuis [this message]
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=3eb9c3f8-6bca-da08-47ec-af2a02d6a485@leemhuis.info \
    --to=regressions@leemhuis.info \
    --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=rombert@apache.org \
    --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).