From: Tejun Heo <tj@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: Bug 218665 - nohz_full=0 prevents kernel from booting
Date: Tue, 16 Apr 2024 13:21:34 -1000 [thread overview]
Message-ID: <Zh8H_vG2dQLOjoIB@slm.duckdns.org> (raw)
In-Reply-To: <81149f18-0132-4ace-8c71-1b75790a88e4@leemhuis.info>
Hello,
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? I was assuming it was the
same problem and that Oleg's fixes would address the issue.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-04-16 23:21 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 [this message]
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=Zh8H_vG2dQLOjoIB@slm.duckdns.org \
--to=tj@kernel.org \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox