From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Mark Rutland <mark.rutland@arm.com>,
Alexey Klimov <alexey.klimov@linaro.org>
Cc: peterz@infradead.org, draszik@google.com,
peter.griffin@linaro.org, willmcvicker@google.com,
mingo@kernel.org, ulf.hansson@linaro.org, tony@atomide.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
axboe@kernel.dk, alim.akhtar@samsung.com,
regressions@lists.linux.dev, avri.altman@wdc.com,
bvanassche@acm.org, klimova@google.com
Subject: Re: [REGRESSION] CPUIDLE_FLAG_RCU_IDLE, blk_mq_freeze_queue_wait() and slow-stuck reboots
Date: Sun, 2 Apr 2023 14:40:32 +0200 [thread overview]
Message-ID: <3a2ca263-7f60-63d3-7f9a-208ab8197c07@leemhuis.info> (raw)
In-Reply-To: <ZBiEEyDaxq9oSXJk@FVFF77S0Q05N.cambridge.arm.com>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 20.03.23 17:04, Mark Rutland wrote:
> On Mon, Mar 20, 2023 at 01:52:47PM +0000, Mark Rutland wrote:
>> On Tue, Mar 14, 2023 at 11:00:04PM +0000, Alexey Klimov wrote:
>>> #regzbot introduced: 0c5ffc3d7b15
>>> #regzbot title: CPUIDLE_FLAG_RCU_IDLE, blk_mq_freeze_queue_wait() and slow-stuck reboots
>>>
>>> The upstream changes are being merged into android-mainline repo and at some
>>> point we started to observe kernel panics on reboot or long reboot times.
>>
>> Where can I find the android-mainline repo, and which specific branch/commit
>> from that repo is being merged in?
>
> I assume that was the android-mainline branch in:
>
> https://android.googlesource.com/kernel/common/
>
> ... and I had a go with commit:
>
> 8338670fd5bdf8d7 ("Merge "Merge 36289a03bcd3 ("Merge tag 'v6.3-p1' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6") into android-mainline" into android-mainline")
>
> ... as that was the commit immediately before your local revert:
>
> a32cec8e3f2253bc ("ANDROID: Revert "cpuidle, dt: Push RCU-idle into driver")
>
> Testing on Juno R2 with defconfig + PROVE_LOCKING=y + DEBUG_LOCKDEP=y, I cannot
> reproduce the reboot issue; everything seems to work just fine.
>
> Can you say which config you're using?
>
> Just to check: are you using a pristine version of that tree, or do you have
> any vendor hooks present? I note that there are special hooks added to the
> cpuidle and PSCI code, and I can imagine those might expect the old behaviour
> w.r.t. RCU and idle, so ruling those out would help.
No reply to this since more than 10 days afaics, hence for now assuming
that this is not really a regression.
#regzbot inconclusive: another dev could not reproduce issue; reporter
MIA and might have used a patched tree
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-04-02 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 23:00 [REGRESSION] CPUIDLE_FLAG_RCU_IDLE, blk_mq_freeze_queue_wait() and slow-stuck reboots Alexey Klimov
2023-03-14 23:21 ` Bart Van Assche
2023-03-17 1:38 ` Alexey Klimov
2023-03-15 11:16 ` Peter Zijlstra
2023-03-17 2:11 ` Alexey Klimov
2023-03-20 9:05 ` Peter Zijlstra
2023-03-20 9:36 ` Peter Zijlstra
2023-04-11 16:16 ` Alexey Klimov
2023-03-20 9:22 ` Peter Zijlstra
2023-03-20 13:52 ` Mark Rutland
2023-03-20 16:04 ` Mark Rutland
2023-04-02 12:40 ` Linux regression tracking #update (Thorsten Leemhuis) [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=3a2ca263-7f60-63d3-7f9a-208ab8197c07@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=alexey.klimov@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=draszik@google.com \
--cc=klimova@google.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=peter.griffin@linaro.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=tony@atomide.com \
--cc=ulf.hansson@linaro.org \
--cc=willmcvicker@google.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;
as well as URLs for NNTP newsgroup(s).