All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>
Subject: 5.14.14+ USB regression caused by "usb: core: hcd: Add support for deferring roothub registration" series
Date: Wed, 3 Nov 2021 10:02:52 +0100	[thread overview]
Message-ID: <42bcbea6-5eb8-16c7-336a-2cb72e71bc36@redhat.com> (raw)

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 ?

Regards,

Hans


             reply	other threads:[~2021-11-03  9:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  9:02 Hans de Goede [this message]
2021-11-03  9:07 ` 5.14.14+ USB regression caused by "usb: core: hcd: Add support for deferring roothub registration" series Greg Kroah-Hartman
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
2021-11-04  6:53 ` Thorsten Leemhuis
2021-11-04  7:04   ` Greg KH
2021-11-04  8:50     ` Thorsten Leemhuis
2021-11-05  7:56       ` Greg KH
2021-11-06  9:26         ` Thorsten Leemhuis

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=42bcbea6-5eb8-16c7-336a-2cb72e71bc36@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --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 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.