From: Kees Cook <keescook@chromium.org>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: Guenter Roeck <linux@roeck-us.net>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux LLVM <llvm@lists.linux.dev>,
linux-kbuild@vger.kernel.org,
Linux Regressions <regressions@lists.linux.dev>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [CRASH][BISECTED] 6.4.1 crash in boot
Date: Sun, 2 Jul 2023 22:41:02 -0700 [thread overview]
Message-ID: <202307022230.6121D6896@keescook> (raw)
In-Reply-To: <2b1a4f49-ba18-0246-af09-4e4133814411@alu.unizg.hr>
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?
- Does pstore work for you to catch the crash?
- Can you try booting with this patch applied?
https://lore.kernel.org/lkml/20230629190900.never.787-kees@kernel.org/
I'll try to see if I can figure out anything more from the images you
posted.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2023-07-03 5:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 16:36 [CRASH][BISECTED] 6.4.1 crash in boot Mirsad Goran Todorovac
2023-07-03 1:44 ` Bagas Sanjaya
2023-07-03 3:20 ` Kees Cook
2023-07-03 3:26 ` Guenter Roeck
2023-07-03 3:53 ` Mirsad Goran Todorovac
2023-07-03 4:30 ` Kees Cook
2023-07-03 4:38 ` Guenter Roeck
2023-07-03 4:53 ` Kees Cook
2023-07-03 4:50 ` Mirsad Goran Todorovac
2023-07-03 3:58 ` Guenter Roeck
2023-07-03 5:18 ` Mirsad Goran Todorovac
2023-07-03 5:18 ` Mirsad Goran Todorovac
2023-07-03 5:41 ` Kees Cook [this message]
2023-07-03 7:03 ` Mirsad Goran Todorovac
2023-07-03 19:03 ` Kees Cook
2023-07-03 23:09 ` Kees Cook
2023-07-04 17:20 ` Mirsad Todorovac
2023-07-04 21:36 ` Kees Cook
2023-07-04 23:15 ` Mirsad Todorovac
2023-07-05 2:09 ` Kees Cook
2023-07-05 5:18 ` Mirsad Todorovac
2023-07-05 15:16 ` CONFIG_UBSAN_TRAP #UD error message on x86 [was: Re: [CRASH][BISECTED] 6.4.1 crash in boot] Jann Horn
2023-07-05 21:08 ` Kees Cook
2023-07-05 21:31 ` Peter Zijlstra
2023-07-05 21:54 ` Kees Cook
2023-07-06 5:02 ` [CRASH][BISECTED] 6.4.1 crash in boot Mirsad Todorovac
2023-07-03 3:40 ` Mirsad Goran Todorovac
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=202307022230.6121D6896@keescook \
--to=keescook@chromium.org \
--cc=bagasdotme@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.