From: Tejun Heo <tj@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Bjorn Andersson <andersson@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug 218665 - nohz_full=0 prevents kernel from booting
Date: Wed, 17 Apr 2024 16:07:26 -1000 [thread overview]
Message-ID: <ZiCAXq-jS1Z6vgCK@slm.duckdns.org> (raw)
In-Reply-To: <51942e58-a5a3-4dcd-80c1-6735c7b5cc1e@leemhuis.info>
Hello, Thorsten.
On Wed, Apr 17, 2024 at 07:48:33AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > 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.
You are right. That is very different.
> > I was assuming it was the
> > same problem and that Oleg's fixes would address the issue.
>
> Bjorn, could you give it a try?
Yeah, I'm curious whether it's just a different symptom of the same problem.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-04-18 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 8:17 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)
2024-04-18 2:07 ` Tejun Heo [this message]
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=ZiCAXq-jS1Z6vgCK@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
all inboxes | Powered by JetHome®