public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bert Karwatzki <spasswolf@web.de>
To: paulmck@kernel.org, "Aithal, Srikanth" <sraithal@amd.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Kuniyuki Iwashima	 <kuniyu@amazon.com>,
	Mateusz Guzik <mjguzik@gmail.com>,
	Petr Mladek	 <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Ogness	 <john.ogness@linutronix.de>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	linux-kernel@vger.kernel.org,
	Linux-Next Mailing List	 <linux-next@vger.kernel.org>,
	spasswolf@web.de
Subject: Re: commit dd4cf8c9e1f4 leads to failed boot
Date: Wed, 23 Apr 2025 16:59:24 +0200	[thread overview]
Message-ID: <fe8ff6a7943b8438de2daa237e20a940cb6a86e8.camel@web.de> (raw)
In-Reply-To: <fa8dd394-45c1-48d3-881c-5f3d5422df39@paulmck-laptop>

Am Mittwoch, dem 23.04.2025 um 07:18 -0700 schrieb Paul E. McKenney:
> On Wed, Apr 23, 2025 at 07:09:42PM +0530, Aithal, Srikanth wrote:
> > On 4/23/2025 5:24 PM, Bert Karwatzki wrote:
> > > Since linux next-20250422 booting fails on my MSI Alpha 15 Laptop runnning
> > > debian sid. When booting kernel message appear on screen but no messages from
> > > init (systemd). There are also no logs written even thought emergency sync
> > > via magic sysrq works (a message is printed on screen), presumably because
> > > / is not mounted. I bisected this (from 6.15-rc3 to next-20250422) and found
> > > commit dd4cf8c9e1f4 as the first bad commit.
> > > Reverting commit dd4cf8c9e1f4 in next-20250422 fixes the issue.
> > 
> > 
> > Hello,
> > 
> > On AMD platform as well boot failed starting next-20250422, bisecting the
> > issue led me to same commit dd4cf8c9e1f4. I have attached kernel config and
> > logs.
> 
> Thank you all for the bisection and the report!
> 
> Please check out the predecessor of commit dd4cf8c9e1f4 ("ratelimit:
> Force re-initialization when rate-limiting re-enabled"):
> 
> 13fa70e052dd ("ratelimit: Allow zero ->burst to disable ratelimiting")

The predecessor commit is 24ff89c63355 ("ratelimit: Allow zero ->burst to
disable ratelimiting") in linux-next.

> 
> Then please apply the patch shown below, and let me know what happens?
> (Yes, I should have split that commit up...)
> 
> 							Thanx, Paul
> 
> ------------------------------------------------------------------------
> 
> diff --git a/lib/ratelimit.c b/lib/ratelimit.c
> index 04f16b8e24575..13ed636642270 100644
> --- a/lib/ratelimit.c
> +++ b/lib/ratelimit.c
> @@ -35,7 +35,7 @@ int ___ratelimit(struct ratelimit_state *rs, const char *func)
>  	unsigned long flags;
>  	int ret;
>  
> -	if (!interval || !burst)
> +	if (interval <= 0 || burst <= 0)
>  		return 1;
>  
>  	/*

The patch applied on top of 24ff89c63355 ("ratelimit: Allow zero ->burst to
disable ratelimiting") works fine.

Bert Karwatzki

  reply	other threads:[~2025-04-23 14:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 11:54 commit dd4cf8c9e1f4 leads to failed boot Bert Karwatzki
2025-04-23 13:39 ` Aithal, Srikanth
2025-04-23 13:46   ` Steven Rostedt
2025-04-23 13:47     ` Aithal, Srikanth
2025-04-23 14:01       ` Steven Rostedt
2025-04-23 14:02         ` Steven Rostedt
2025-04-23 14:18   ` Paul E. McKenney
2025-04-23 14:59     ` Bert Karwatzki [this message]
2025-04-23 18:03       ` Bert Karwatzki
2025-04-23 15:19     ` Aithal, Srikanth
2025-04-23 18:07       ` Paul E. McKenney
2025-04-23 19:19         ` Bert Karwatzki
2025-04-23 19:56           ` Paul E. McKenney
2025-04-24  4:30             ` Aithal, Srikanth
2025-04-24  7:36             ` Petr Mladek
2025-04-24 14:43               ` Paul E. McKenney
2025-04-25  9:35                 ` Petr Mladek
2025-04-25 16:34                   ` Paul E. McKenney
2025-04-24 12:40             ` Bert Karwatzki
2025-04-24 14:30               ` Paul E. McKenney

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=fe8ff6a7943b8438de2daa237e20a940cb6a86e8.camel@web.de \
    --to=spasswolf@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=john.ogness@linutronix.de \
    --cc=kuniyu@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=sraithal@amd.com \
    /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