The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug 218665 - nohz_full=0 prevents kernel from booting
Date: Wed, 3 Apr 2024 09:14:36 -1000	[thread overview]
Message-ID: <Zg2qnEgOo9CaFwgB@slm.duckdns.org> (raw)
In-Reply-To: <5be248c6-cdda-4d2e-8fae-30fc2cc124c0@leemhuis.info>

Hello, Thorsten.

On Tue, Apr 02, 2024 at 10:17:16AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
> 
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developers don't keep an eye on it, I decided to forward it by mail.
> 
> Tejun, apparently it's cause by a change of yours.
> 
> Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
> not CCed them in mails like this.
> 
> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=218665 :

This looks like the same problem that's being discussed in the following
thread.

 http://lkml.kernel.org/r/20240402105847.GA24832@redhat.com

Hopefully, we'll soon reach a resolution.

Thanks.

-- 
tejun

  reply	other threads:[~2024-04-03 19:14 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 [this message]
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
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=Zg2qnEgOo9CaFwgB@slm.duckdns.org \
    --to=tj@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