From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Bug 218665 - nohz_full=0 prevents kernel from booting
Date: Tue, 16 Apr 2024 08:08:07 +0200 [thread overview]
Message-ID: <81149f18-0132-4ace-8c71-1b75790a88e4@leemhuis.info> (raw)
In-Reply-To: <7kugx5ivbplwwrcq5zp37djtpakl55b3pfy36gpbsbcx43dpcs@uheu6iv7gm7h>
On 12.04.24 04:57, Bjorn Andersson wrote:
> On Wed, Apr 10, 2024 at 11:18:04AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 08.04.24 00:52, Bjorn Andersson wrote:
>>> On Tue, Apr 02, 2024 at 10:17:16AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>>>>
>>>> Tejun, apparently it's cause by a change of yours.
>>>> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=218665 :
>>>>
>>>>> booting the current kernel (6.9.0-rc1, master/712e1425) on x86_64
>>>>> with nohz_full=0 cause a page fault and prevents the kernel from
>>>>> booting.
>>> [...]
Tejun, I got a bit lost here. Can you help me out please?
I'm currently assuming that these two reports have the same cause:
https://lore.kernel.org/all/20240402105847.GA24832@redhat.com/T/#u
https://bugzilla.kernel.org/show_bug.cgi?id=218665
And that both will be fixed by this patch from Oleg Nesterov:
https://lore.kernel.org/lkml/20240411143905.GA19288@redhat.com/
But well, to me it looks like below issue from Bjorn is different, even
if it is caused by the same change -- nevertheless it looks like nobody
has looked into this since it was reported about two weeks ago. Or was
progress made and I just missed it?
>>> In addition to this report, I have finally bisected another regression
>>> to the same commit:
>>>
>>> I start neovim, send SIGSTOP (i.e. ^Z) to it, start another neovim
>>> instance and upon sending SIGSTOP to that instance all of userspace
>>> locks up - 100% reproducible.
>>>
>>> The kernel seems to continue to operate, and tapping the power button
>>> dislodge the lockup and I get a clean shutdown.
>>>
>>> This is seen on multiple Arm64 (Qualcomm) machines with upstream
>>> defconfig since commit '5797b1c18919 ("workqueue: Implement system-wide
>>> nr_active enforcement for unbound workqueues")'.
>>
>> Hmmm, I had hoped Tejun would reply and share an opinion if these
>> problems are related. But that didn't happen. :-/ So let me at least ask
>> one question that might help to answer that question: is the machine
>> using CPU isolation, like the two other reports about problems caused by
>> this commit do (see the
>> https://bugzilla.kernel.org/show_bug.cgi?id=218665 and
>> https://lore.kernel.org/all/20240402105847.GA24832@redhat.com/ for
>> details) ?
>
> No, this is a clean SMP system running stock arch/arm64/defconfig,
> booted with "clk_ignore_unused pd_ignore_unused audit=0" as the command
> line.
>
> Regards,
> Bjorn
Ciao, Thorsten
next prev parent reply other threads:[~2024-04-16 6:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 8:17 Bug 218665 - nohz_full=0 prevents kernel from booting Linux regression tracking (Thorsten Leemhuis)
2024-04-03 19:14 ` Tejun Heo
2024-04-07 22:52 ` Bjorn Andersson
2024-04-10 9:18 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-12 2:57 ` Bjorn Andersson
2024-04-16 6:08 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-04-16 23:21 ` Tejun Heo
2024-04-17 5:48 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-18 2:07 ` Tejun Heo
2024-04-22 21:23 ` Bjorn Andersson
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=81149f18-0132-4ace-8c71-1b75790a88e4@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tj@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 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.