From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux6.6 i386 boot failed
Date: Wed, 06 Dec 2023 16:12:57 +0100 [thread overview]
Message-ID: <20231206151257.NntY9DWsSNGR0XxgpKciHyyGV6LwJbSpSY11w3GBJzQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47514@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3165 bytes --]
New comment by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/47514#issuecomment-1843086483
Comment:
Booting with `earlyprintk=ttySO` helps:
```
No EFI environment detected.
early console in extract_kernel
input_data: 0x02004094
input_len: 0x00a8b825
output: 0x01000000
output_len: 0x018f19d0
kernel_total_size: 0x01aaf000
needed_size: 0x01aaf000
Physical KASLR using RDTSC...
Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel (entry_offset: 0x00000080).
Poking KASLR using RDTSC...
[ 0.593769] kernel BUG at arch/x86/mm/physaddr.c:81!
[ 0.594640] invalid opcode: 0000 [#1] PREEMPT SMP PTI
[ 0.594772] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.6.4_1 #1
[ 0.594865] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014
[ 0.595028] EIP: __phys_addr+0x78/0x84
[ 0.595450] Code: 75 fc 89 ec 5d e9 cc f8 ab 00 8d b4 26 00 00 00 00 90 0f 0b 8d b6 00 00 00 00 e8 bf 23 29 00 84 c0 74 b8 0f 0b 8d 74 26 00 90 <0f> 0b 8d b6 00 00 00 00 0f 0b 66 90 3e 8d 74 26 00 3d ff ff ff bf
[ 0.595718] EAX: fffff000 EBX: f7318000 ECX: 00000000 EDX: ffffffff
[ 0.595768] ESI: 37318000 EDI: f7318000 EBP: cf405f3c ESP: cf405f34
[ 0.595815] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00200086
[ 0.595876] CR0: 80050033 CR2: ffbff000 CR3: 0f7b4000 CR4: 000000b0
[ 0.595979] Call Trace:
[ 0.596580] ? show_regs+0x56/0x64
[ 0.596663] ? die+0x34/0x90
[ 0.596692] ? ftrace_dump+0x30c/0x30c
[ 0.596723] ? do_trap+0xcc/0x154
[ 0.596748] ? notify_die+0x56/0x74
[ 0.596792] ? do_error_trap+0x69/0x84
[ 0.596821] ? __phys_addr+0x78/0x84
[ 0.596848] ? exc_overflow+0x54/0x54
[ 0.596877] ? exc_invalid_op+0x5d/0x74
[ 0.596905] ? __phys_addr+0x78/0x84
[ 0.596932] ? handle_exception+0x133/0x133
[ 0.596985] ? exc_overflow+0x54/0x54
[ 0.597013] ? __phys_addr+0x78/0x84
[ 0.597042] ? exc_overflow+0x54/0x54
[ 0.597068] ? __phys_addr+0x78/0x84
[ 0.597104] kfence_init+0xce/0xe4
[ 0.597198] start_kernel+0x4b1/0xba8
[ 0.597237] i386_start_kernel+0x48/0x48
[ 0.597266] startup_32_smp+0x156/0x158
[ 0.597393] Modules linked in:
[ 0.597835] ---[ end trace 0000000000000000 ]---
[ 0.597896] EIP: __phys_addr+0x78/0x84
[ 0.597931] Code: 75 fc 89 ec 5d e9 cc f8 ab 00 8d b4 26 00 00 00 00 90 0f 0b 8d b6 00 00 00 00 e8 bf 23 29 00 84 c0 74 b8 0f 0b 8d 74 26 00 90 <0f> 0b 8d b6 00 00 00 00 0f 0b 66 90 3e 8d 74 26 00 3d ff ff ff bf
[ 0.598020] EAX: fffff000 EBX: f7318000 ECX: 00000000 EDX: ffffffff
[ 0.598055] ESI: 37318000 EDI: f7318000 EBP: cf405f3c ESP: cf405f34
[ 0.598088] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 EFLAGS: 00200086
[ 0.598125] CR0: 80050033 CR2: ffbff000 CR3: 0f7b4000 CR4: 000000b0
[ 0.598271] Kernel panic - not syncing: Attempted to kill the idle task!
[ 0.598705] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---
```
`CONFIG_KFENCE` was enabled between 6.5 and 6.6, so I suggest removing it.
next prev parent reply other threads:[~2023-12-06 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 8:43 [ISSUE] " naY9yjoS6ZqhOd35sIFH
2023-12-03 0:21 ` mtboehlke
2023-12-04 5:37 ` naY9yjoS6ZqhOd35sIFH
2023-12-04 16:01 ` leahneukirchen
2023-12-05 6:05 ` mtboehlke
2023-12-06 14:52 ` leahneukirchen
2023-12-06 14:59 ` leahneukirchen
2023-12-06 15:12 ` leahneukirchen [this message]
2023-12-06 17:25 ` [ISSUE] [CLOSED] " leahneukirchen
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=20231206151257.NntY9DWsSNGR0XxgpKciHyyGV6LwJbSpSY11w3GBJzQ@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).