mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dayu Jiang <jiangdayu@xiaomi.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mathias Nyman <mathias.nyman@intel.com>,
	Longfang Liu <liulongfang@huawei.com>,
	<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	yudongbin <yudongbin@xiaomi.com>, guhuinan <guhuinan@xiaomi.com>,
	chenyu45 <chenyu45@xiaomi.com>,
	mahongwei3 <mahongwei3@xiaomi.com>,
	Dayu Jiang <jiangdayu@xiaomi.com>
Subject: Re: [PATCH] usb: xhci: add xhci_halt() for HCE Handling
Date: Thu, 26 Feb 2026 17:27:01 +0800	[thread overview]
Message-ID: <aaAR5VOtnMhvoCem@oa-jiangdayu.localdomain> (raw)
In-Reply-To: <2026012857-deprive-putdown-0ee8@gregkh>

Hi Greg,

I have updated the changelog text as requested and resubmitted the patch.
https://lore.kernel.org/linux-usb/20260128100746.561626-1-jiangdayu@xiaomi.com/
Please kindly review it and let me know if it is acceptable now.

Thanks,
Dayu Jiang

On Wed, Jan 28, 2026 at 09:56:18AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 28, 2026 at 04:48:49PM +0800, Dayu Jiang wrote:
> > On Tue, Jan 27, 2026 at 12:22:40PM +0100, Greg Kroah-Hartman wrote:
> > > >  	if (status & STS_HCE) {
> > > >  		xhci_warn(xhci, "WARNING: Host Controller Error\n");
> > > > +		xhci_halt(xhci);
> > > 
> > > What is going to start things back up again?  And as you are calling
> > > this function, why is the warning message needed anymore?  The
> > > tracepoint information will give you that message now, right?
> > When HCE is triggered, it indicates a critical hardware failure. 
> > Aligning with the handling of HSE (STS_FATAL) by adding 
> > xhci_halt() here is more reasonable: without xhci_halt(), the 
> > USB controller may fall into an unpredictable and unstable state, 
> > which could exacerbate system issues.  
> > 
> > Retaining the warning message is necessary because it is directly 
> > visible in dmesg, whereas tracepoint information requires explicitly 
> > enabling xHCI tracepoints. Additionally, if xhci_halt() is called in 
> > xhci_irq() without the warning log, it would be impossible to 
> > distinguish whether the halt was triggered by HCE or HSE.
> > > 
> > > And is this just papering over a hardware bug?  Should this really be
> > > happening for any normal system?
> > Yes, this issue has been reproducible on real-world hardware: HCE is 
> > triggered in UAS Storage Device plug/unplug scenarios on Android 
> > devices, which enters this error branch and causes an interrupt storm, 
> > leading to severe system-level faults.
> 
> Great, please provide this information in the changelog text when you
> resubmit this, thanks!
> 
> greg k-h

  reply	other threads:[~2026-02-26  9:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 11:04 jiangdayu
2026-01-27 11:22 ` Greg Kroah-Hartman
2026-01-28  8:48   ` Dayu Jiang
2026-01-28  8:56     ` Greg Kroah-Hartman
2026-02-26  9:27       ` Dayu Jiang [this message]
2026-02-26 16:44         ` Mathias Nyman
2026-02-26 18:17           ` Thinh Nguyen
2026-02-27  7:26             ` Dayu Jiang
2026-02-28  0:22               ` Thinh Nguyen
2026-02-27  9:43             ` Mathias Nyman
2026-02-27 11:05               ` Michal Pecio
2026-02-28  0:06                 ` Thinh Nguyen
2026-02-28  0:18               ` Thinh Nguyen
2026-02-27  7:33           ` Dayu Jiang
2026-01-27 12:25 ` Mathias Nyman
2026-01-28  8:53   ` Dayu Jiang

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=aaAR5VOtnMhvoCem@oa-jiangdayu.localdomain \
    --to=jiangdayu@xiaomi.com \
    --cc=chenyu45@xiaomi.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guhuinan@xiaomi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=liulongfang@huawei.com \
    --cc=mahongwei3@xiaomi.com \
    --cc=mathias.nyman@intel.com \
    --cc=yudongbin@xiaomi.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

all inboxes | Powered by JetHome®