[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250423094655.2a0e25e0@gandalf.local.home>
Date: Wed, 23 Apr 2025 09:46:55 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Aithal, Srikanth" <sraithal@....com>
Cc: Bert Karwatzki <spasswolf@....de>, "Paul E . McKenney"
<paulmck@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, Kuniyuki
Iwashima <kuniyu@...zon.com>, Mateusz Guzik <mjguzik@...il.com>, Petr
Mladek <pmladek@...e.com>, John Ogness <john.ogness@...utronix.de>, Sergey
Senozhatsky <senozhatsky@...omium.org>, linux-kernel@...r.kernel.org,
Linux-Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: commit dd4cf8c9e1f4 leads to failed boot
On Wed, 23 Apr 2025 19:09:42 +0530
"Aithal, Srikanth" <sraithal@....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
Powered by blists - more mailing lists