mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: Christian Hewitt <christianshewitt@gmail.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mathias Nyman <mathias.nyman@linux.intel.com>,
	Chris Chiu <chris.chiu@canonical.com>,
	linux-usb@vger.kernel.org, linux-amlogic@lists.infradead.org,
	stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Neil Armstrong <narmstrong@baylibre.com>
Subject: Regression in 5.18.3 from "xhci: Set HCD flag to defer primary roothub registration"
Date: Sat, 11 Jun 2022 10:49:23 +0400	[thread overview]
Message-ID: <743F7369-2794-4189-8891-5DA62E4B62DA@gmail.com> (raw)

Commit 6c64a664e1cff339ec698d803fa8cbb9af5d95ce “xhci: Set HCD flag to defer
primary roothub registration” added for Linux 5.18.3 caused a regression on
some Amlogic S912 devices (original user forum report with an Android TV box
and confirmed with a Khadas VIM2 board). I do not see issues with older S905
(WeTeK Play2) or newer S922X (Odroid N2+) devices running the same kernel.
There are no kernel splats or error messages but lsusb shows no output and
nothing works. Simple revert restores the previous good working behaviour.

dmesg with commit http://ix.io/3ZTv
dmesg with revert http://ix.io/3ZTw

I’m not a coder so will need to be fed instructions to assist with debugging
the issue further if you don't have access to an Amlogic S912 device. I can
share devices online for remote poking around if needed.

Christian
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

             reply	other threads:[~2022-06-11  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  6:49 Christian Hewitt [this message]
2022-06-11  7:32 ` Greg Kroah-Hartman
2022-06-11 14:18   ` Christian Hewitt

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=743F7369-2794-4189-8891-5DA62E4B62DA@gmail.com \
    --to=christianshewitt@gmail.com \
    --cc=chris.chiu@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kishon@ti.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=narmstrong@baylibre.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

all inboxes | Powered by JetHome®