From: "Aithal, Srikanth" <sraithal@amd•com>
To: Steven Rostedt <rostedt@goodmis•org>
Cc: Bert Karwatzki <spasswolf@web•de>,
"Paul E . McKenney" <paulmck@kernel•org>,
Andrew Morton <akpm@linux-foundation•org>,
Kuniyuki Iwashima <kuniyu@amazon•com>,
Mateusz Guzik <mjguzik@gmail•com>, Petr Mladek <pmladek@suse•com>,
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>
Subject: Re: commit dd4cf8c9e1f4 leads to failed boot
Date: Wed, 23 Apr 2025 19:17:43 +0530 [thread overview]
Message-ID: <8f7671cc-32f1-4028-a1b0-c7dccf472f76@amd.com> (raw)
In-Reply-To: <20250423094655.2a0e25e0@gandalf.local.home>
On 4/23/2025 7:16 PM, Steven Rostedt wrote:
> On Wed, 23 Apr 2025 19:09:42 +0530
> "Aithal, Srikanth" <sraithal@amd•com> 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.
>>
>
> What is commit dd4cf8c9e1f4? Please use human readable text. The sha is
> fine for lookup, but without the title it's meaningless to me.
>
> $ git show dd4cf8c9e1f4
> fatal: ambiguous argument 'dd4cf8c9e1f4': unknown revision or path not in the working tree.
>
> Don't make me have to download linux-next to figure this out! :-p
>
> -- Steve
I had referred the commit from next-20250422 tree.
commit dd4cf8c9e1f426496d63fa4e19fbf4edd5623b33
Author: Paul E. McKenney <paulmck@kernel•org>
Date: Thu Apr 10 09:52:53 2025 -0700
ratelimit: Force re-initialization when rate-limiting re-enabled
Currently, rate limiting being disabled results in an immediate early
return with no state changes. This can result in false-positive drops
when re-enabling rate limiting. Therefore, mark the ratelimit_state
structure "uninitialized" when rate limiting is disabled.
Additionally, interpret non-positive ->burst to unconditionally force
rate limiting. When ->burst is positive, interpret non-positive
interval
to unconditionally disable rate limiting.
Signed-off-by: Paul E. McKenney <paulmck@kernel•org>
Cc: Andrew Morton <akpm@linux-foundation•org>
Cc: Kuniyuki Iwashima <kuniyu@amazon•com>
Cc: Mateusz Guzik <mjguzik@gmail•com>
Cc: Petr Mladek <pmladek@suse•com>
Cc: Steven Rostedt <rostedt@goodmis•org>
Cc: John Ogness <john.ogness@linutronix•de>
Cc: Sergey Senozhatsky <senozhatsky@chromium•org>
On todays linux-next build the commit id is
c8943bdecfc76711f83241e21da9d4530f872f0d.
next prev parent reply other threads:[~2025-04-23 13:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250423115409.3425-1-spasswolf@web.de>
2025-04-23 13:39 ` commit dd4cf8c9e1f4 leads to failed boot Aithal, Srikanth
2025-04-23 13:46 ` Steven Rostedt
2025-04-23 13:47 ` Aithal, Srikanth [this message]
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
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=8f7671cc-32f1-4028-a1b0-c7dccf472f76@amd.com \
--to=sraithal@amd$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=john.ogness@linutronix$(echo .)de \
--cc=kuniyu@amazon$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mjguzik@gmail$(echo .)com \
--cc=paulmck@kernel$(echo .)org \
--cc=pmladek@suse$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=senozhatsky@chromium$(echo .)org \
--cc=spasswolf@web$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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