From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Tejun Heo <tj@kernel.org>, Bjorn Andersson <andersson@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: Bug 218665 - nohz_full=0 prevents kernel from booting
Date: Wed, 17 Apr 2024 07:48:33 +0200 [thread overview]
Message-ID: <51942e58-a5a3-4dcd-80c1-6735c7b5cc1e@leemhuis.info> (raw)
In-Reply-To: <Zh8H_vG2dQLOjoIB@slm.duckdns.org>
On 17.04.24 01:21, Tejun Heo wrote:
> On Tue, Apr 16, 2024 at 08:08:07AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
>> 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?
>
> Can you elaborate why Bjorn's case is different?
Well "not booting at all when using 'nohz_full=0'"[as reported two
times] and "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."[while no 'nohz_full=0' in use]
at least on the first sight to and outsider sound a lot like different
problems to me -- but of course that impression might be wrong and you
know better about these things.
> I was assuming it was the
> same problem and that Oleg's fixes would address the issue.
Bjorn, could you give it a try?
Ciao, Thorsten
next prev parent reply other threads:[~2024-04-17 5:48 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)
2024-04-16 23:21 ` Tejun Heo
2024-04-17 5:48 ` Linux regression tracking (Thorsten Leemhuis) [this message]
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=51942e58-a5a3-4dcd-80c1-6735c7b5cc1e@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.