From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: stable@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>
Subject: Re: 5.14.14+ USB regression caused by "usb: core: hcd: Add support for deferring roothub registration" series
Date: Wed, 3 Nov 2021 10:07:18 +0100 [thread overview]
Message-ID: <YYJRRg8QDBfy2PP7@kroah.com> (raw)
In-Reply-To: <42bcbea6-5eb8-16c7-336a-2cb72e71bc36@redhat.com>
On Wed, Nov 03, 2021 at 10:02:52AM +0100, Hans de Goede wrote:
> Hi Greg,
>
> We (Fedora) have been receiving multiple reports about USB devices stopping
> working starting with 5.14.14 .
>
> An Arch Linux user has found that reverting the first 2 patches from this series:
> https://lore.kernel.org/all/20210909064200.16216-1-kishon@ti.com/
>
> Fixes things (the 3th patch is just some mostly unrelated refactoring/cleanup).
>
> See here for the Arch-linux discussion surrounding this:
> https://bbs.archlinux.org/viewtopic.php?pid=2000956#p2000956
>
> And here are 2 Fedora bug reports of Fedora users being unable to use their
> machines due their mouse + kbd not working:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2019542
> https://bugzilla.redhat.com/show_bug.cgi?id=2019576
>
> Can we get this patch-series reverted from the 5.14.y releases please ?
Sure, but can you also submit patches to get into 5.15.y and 5.16-rc1
that revert these changes as they should still be an issue there, right?
thanks,
greg k-h
next prev parent reply other threads:[~2021-11-03 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 9:02 5.14.14+ USB regression caused by "usb: core: hcd: Add support for deferring roothub registration" series Hans de Goede
2021-11-03 9:07 ` Greg Kroah-Hartman [this message]
2021-11-03 12:48 ` Hans de Goede
2021-11-03 14:44 ` Kishon Vijay Abraham I
2021-11-03 14:59 ` Alan Stern
2021-11-03 23:54 ` Mathias Nyman
2021-11-15 22:05 ` Mathias Nyman
2021-11-03 17:45 ` Greg Kroah-Hartman
2021-11-05 7:57 ` Greg Kroah-Hartman
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=YYJRRg8QDBfy2PP7@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kishon@ti.com \
--cc=stable@vger.kernel.org \
/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 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).