[ISSUE] linux6.6 i386 boot failed

[ISSUE] linux6.6 i386 boot failed

[naY9yjoS6ZqhOd35sIFH]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

New issue by naY9yjoS6ZqhOd35sIFH on void-packages repository

https://github.com/void-linux/void-packages/issues/47514

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.63_1

### Package(s) Affected

linux6.6

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

boot and show dmesg to serial console

### Actual behaviour

stuck after loading vmlinuz

### Steps to reproduce

1.install linux6.6 dracut and grub from xbps-install
2.generate initramfs from dracut
3.using grub-mkconfig to add grub menu
4.reboot and stuck at loading 

Re: linux6.6 i386 boot failed

[mtboehlke]

[-- Attachment #1: Type: text/plain, Size: 356 bytes --]

New comment by mtboehlke on void-packages repository

https://github.com/void-linux/void-packages/issues/47514#issuecomment-1837290350

Comment:
I was able to reproduce on my i686 machine.  After decompressing the kernel successfully, boot hangs on message: `Booting the kernel`
I use syslinux, so probably not a grub problem.

Linux 6.5.13 boots fine.

Re: linux6.6 i386 boot failed

[naY9yjoS6ZqhOd35sIFH]

[-- Attachment #1: Type: text/plain, Size: 187 bytes --]

New comment by naY9yjoS6ZqhOd35sIFH on void-packages repository

https://github.com/void-linux/void-packages/issues/47514#issuecomment-1837876579

Comment:
and 6.5 is eol now 
@Duncaen 

Re: linux6.6 i386 boot failed

[leahneukirchen]

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

New comment by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/issues/47514#issuecomment-1838953817

Comment:
Are you sure your /boot isn't full and the initrd can be read completely? (try `lsinitrd`)

Re: linux6.6 i386 boot failed

[mtboehlke]

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

New comment by mtboehlke on void-packages repository

https://github.com/void-linux/void-packages/issues/47514#issuecomment-1840069837

Comment:
No, at least that wasn't it for me.  My /boot partition is less than half full.  I usually run an lts kernel.  I installed linux6.6 to see if I had the same issue, and installed 6.5 afterwards and was able to boot, so I am not running into a space issue.  No error messages during initramfs generation, and lsinitrd succeeds and looks normal.  I just tested 6.6.4 just in case, but still stuck.  This issue seems to be specific to the 6.6 series.

Re: linux6.6 i386 boot failed

[leahneukirchen]

[-- Attachment #1: Type: text/plain, Size: 227 bytes --]

New comment by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/issues/47514#issuecomment-1843048681

Comment:
I can reproduce in qemu, thanks.  A bit clueless how to debug this, however.

Re: linux6.6 i386 boot failed

[leahneukirchen]

[-- Attachment #1: Type: text/plain, Size: 193 bytes --]

New comment by leahneukirchen on void-packages repository

https://github.com/void-linux/void-packages/issues/47514#issuecomment-1843061485

Comment:
Alpine has a working 6.6.4 kernel on i686.

Re: linux6.6 i386 boot failed

[leahneukirchen]

[-- 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.

Re: [ISSUE] [CLOSED] linux6.6 i386 boot failed

[leahneukirchen]

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

Closed issue by naY9yjoS6ZqhOd35sIFH on void-packages repository

https://github.com/void-linux/void-packages/issues/47514

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.63_1

### Package(s) Affected

linux6.6

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

boot and show dmesg to serial console

### Actual behaviour

stuck after loading vmlinuz

### Steps to reproduce

1.install linux6.6 dracut and grub from xbps-install
2.generate initramfs from dracut
3.using grub-mkconfig to add grub menu
4.reboot and stuck at loading