From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: "Michał Pecio" <michal.pecio@gmail.com>, linux-usb@vger.kernel.org
Cc: Niklas Neronin <niklas.neronin@linux.intel.com>,
regressions@lists.linux.dev,
Christian Heusel <christian@heusel.eu>
Subject: Re: [REGRESSION 6.16] xHCI host not responding to stop endpoint command after suspend and resume
Date: Tue, 19 Aug 2025 11:56:54 +0300 [thread overview]
Message-ID: <2f2b66b5-d845-4e75-aaac-87974b592b4a@linux.intel.com> (raw)
In-Reply-To: <20250819084153.2c13c187@foxbook>
On 19.8.2025 9.41, Michał Pecio wrote:
> On Mon, 18 Aug 2025 23:11:03 +0200, Michał Pecio wrote:
>> A bisect effort is ongoing and c0c9379f235d ("Merge tag 'usb-6.16-rc1'
>> of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb") is bad,
>> so that's where the bug likely came from.
>
> Looks like the result is in.
>
> e1db856bd28891d70008880d7f1d3b8d1ea948fd is the first bad commit
> commit e1db856bd28891d70008880d7f1d3b8d1ea948fd
> Author: Niklas Neronin <niklas.neronin@linux.intel.com>
> Date: Thu May 15 16:56:14 2025 +0300
>
> usb: xhci: remove '0' write to write-1-to-clear register
Thanks for tracking this down, I see the issue now
We may lose interrupts due to this patch, example:
Hardware sets IMAN_IP BIT(0) when in needs attention
Driver later allows xHC interrupt by setting IMAN_IE BIT(1), but
Driver clears IMAN_IP (RW1C) when setting IMAN_IE so no interrupt is triggered.
interrupts are only triggered if both IMAN_IE and IMAN_IP are set, (and some other
moderation and event handling bits are correct)
we need to make sure we don't accidentally clear a pending interrupt (IMAN_IP)
in both the enable and disable case.
Thanks
Mathias
next prev parent reply other threads:[~2025-08-19 8:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 21:11 [REGRESSION 6.16] xHCI host not responding to stop endpoint command after suspend and resume Michał Pecio
2025-08-19 6:41 ` Michał Pecio
2025-08-19 8:56 ` Mathias Nyman [this message]
2025-08-19 9:08 ` Neronin, Niklas
2025-08-19 10:42 ` Mathias Nyman
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=2f2b66b5-d845-4e75-aaac-87974b592b4a@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=christian@heusel.eu \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=niklas.neronin@linux.intel.com \
--cc=regressions@lists.linux.dev \
/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.