[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed3e4315-b149-2f9e-70d4-45d7f83b9922@alu.unizg.hr>
Date: Mon, 3 Jul 2023 09:03:38 +0200
From: Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
To: Kees Cook <keescook@...omium.org>
Cc: Guenter Roeck <linux@...ck-us.net>,
Bagas Sanjaya <bagasdotme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux LLVM <llvm@...ts.linux.dev>,
linux-kbuild@...r.kernel.org,
Linux Regressions <regressions@...ts.linux.dev>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>
Subject: Re: [CRASH][BISECTED] 6.4.1 crash in boot
On 3.7.2023. 7:41, Kees Cook wrote:
> On Mon, Jul 03, 2023 at 07:18:57AM +0200, Mirsad Goran Todorovac wrote:
>> I apologise for confusion. In fact, I have cloned the Torvalds tree after
>> 6.4.1 was released, but I actually cloned the Torvalds tree, not the 6.4.1
>> from the stable branch as the Subject line might have misled.
>
> Thanks, no worries! I got myself confused too. :)
>
> The config you sent looks like I'd expect now too. Questions for you, if
> you have time to diagnose further:
>
> - Are you able to catch the very beginning of the crash, where the Oops
> starts?
It scrolls up very quickly. Couldn't catch that with the camera.
> - Does pstore work for you to catch the crash?
Haven't tried that yet. I will have to do some homework.
> - Can you try booting with this patch applied?
> https://lore.kernel.org/lkml/20230629190900.never.787-kees@kernel.org/
Sure, but after 4 PM UTC+02 I suppose.
> I'll try to see if I can figure out anything more from the images you
> posted.
I really couldn't figure out myself what went wrong with this one?
Best regards,
Mirsad Todorovac
Powered by blists - more mailing lists