public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Pecio" <michal.pecio@gmail.com>
To: Su Hui <suhui@nfschina.com>
Cc: mathias.nyman@intel.com, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] usb: xhci: print xhci->xhc_state when queue_command failed
Date: Sat, 26 Jul 2025 11:11:01 +0200	[thread overview]
Message-ID: <20250726111101.5928e289@foxbook> (raw)
In-Reply-To: <09d18144-ab12-4bbc-8b61-e0b334ef13bc@nfschina.com>

On Fri, 25 Jul 2025 19:32:37 +0800, Su Hui wrote:
> On 2025/7/25 18:03, Michał Pecio wrote:
> >> Hmm, any chance you came across bugs that upstream should know about?  
> Actually, this bug is specific to the 5.4 version of the kernel and a 
> particular USB camera. I am working
> to resolve this issue. When the xhci_hcd is initialized, the driver sets 
> xhc_state to "halted", but before
> the xhci_hcd calls xhci_start, the hub starts Initializing. Hub 
> initialization failed due to xhc_state being
> halted. Perhaps this issue is caused by hardware...

Trying to queue commands before the chip is ready sounds like a SW bug.
5.4 is ancient (and EOL soon), newer releases may have this bug fixed.

      reply	other threads:[~2025-07-26  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  3:13 [PATCH] usb: xhci: print xhci->xhc_state when queue_command failed Su Hui
2025-07-25  4:43 ` Greg KH
2025-07-25  5:11   ` Su Hui
2025-07-25  6:01 ` [PATCH v2] " Su Hui
2025-07-25  8:50   ` Greg KH
2025-07-25 10:03   ` Michał Pecio
2025-07-25 11:32     ` Su Hui
2025-07-26  9:11       ` Michał Pecio [this message]

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=20250726111101.5928e289@foxbook \
    --to=michal.pecio@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=suhui@nfschina.com \
    /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