From: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: linux-kbuild@vger.kernel.org, Kees Cook <keescook@chromium.org>
Subject: [CRASH][BISECTED] 6.4.1 crash in boot
Date: Sun, 2 Jul 2023 18:36:12 +0200 [thread overview]
Message-ID: <9a8e34ad-8a8b-3830-4878-3c2c82e69dd9@alu.unizg.hr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
Hi,
After new git pull the kernel in Torvalds tree with default debug config
failed to boot with error that occurs prior to mounting filesystems, so there
is no log safe for the screenshot(s) here:
[1] https://domac.alu.unizg.hr/~mtodorov/linux/crashes/2023-07-02/
Bisect shows the first bad commit is 2d47c6956ab3 (v6.4-rc2-1-g2d47c6956ab3):
# good: [98be618ad03010b1173fc3c35f6cbb4447ee2b07] Merge tag 'Smack-for-6.5' of https://github.com/cschaufler/smack-next
git bisect good 98be618ad03010b1173fc3c35f6cbb4447ee2b07
# bad: [f4a0659f823e5a828ea2f45b4849ea8e2dd2984c] drm/i2c: tda998x: Replace all non-returning strlcpy with strscpy
git bisect bad f4a0659f823e5a828ea2f45b4849ea8e2dd2984c
.
.
.
# bad: [2d47c6956ab3c8b580a59d7704aab3e2a4882b6c] ubsan: Tighten UBSAN_BOUNDS on GCC
git bisect bad 2d47c6956ab3c8b580a59d7704aab3e2a4882b6c
# first bad commit: [2d47c6956ab3c8b580a59d7704aab3e2a4882b6c] ubsan: Tighten UBSAN_BOUNDS on GCC
The architecture is Ubuntu 22.04 with lshw and config give in the attachment.
Best regards,
Mirsad Todorovac
[-- Attachment #2: config-6.4.0-060400-generic.xz --]
[-- Type: application/x-xz, Size: 57448 bytes --]
[-- Attachment #3: lshw.txt.xz --]
[-- Type: application/x-xz, Size: 6500 bytes --]
next reply other threads:[~2023-07-02 16:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 16:36 Mirsad Goran Todorovac [this message]
2023-07-03 1:44 ` [CRASH][BISECTED] 6.4.1 crash in boot 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
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=9a8e34ad-8a8b-3830-4878-3c2c82e69dd9@alu.unizg.hr \
--to=mirsad.todorovac@alu.unizg.hr \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).