New kernels

[xeno74]

Should the 6.12.4 boot without any other changes to the U-boot variables than the "uImage-6.12"?

Which boot arguments do you use?

When I simply placed it into my usual variable string, "load mmc 0:1 1000000 uImage-6.12;load mmc 0:1 1d00000 cyrus_5020.dtb;load mmc 0:1 2000000 uInitrd-5.10", I did not get MintPPC loaded. The kernel itself was loaded normally as far as I could see, but it did not seem find the root file system at all...

Please boot without the uInitrd-5.10.

or is there possibly missing a NVMe disk driver...?

The NVMe driver is built into the kernel.

[xeno74]

KVM: PPC: Book3E: KVM HV host module doesn't work anymore since the alpha3 of kernel 6.13. (alpha3: PowerPC updates 6.13-1 and PowerPC MM updates)

The kernel doesn't boot. There is no output via the serial connection and no output via the graphics card.

I reported this issue to the kernel developers today.

Link: KVM: PPC: Book3E: KVM HV host module doesn't work anymore

I bisected today because of this issue.

About bisecting:

Git bisect is like a little wizard that walks you through recent commits, asks you if they are good or bad, and narrows down the broken commit.
Git bisect starts with the midpoint commit. The midpoint commit is between the initial good commit and the initial bad commit.
If the midpoint commit was good, you know the commit that introduced the change is between your midpoint and the initial bad commit.
If the midpoint commit was bad, you know the commit that introduced the change is between your midpoint and the initial good commit.
After that git bisect selects a new midpoint in the area where the commit was bad. And this is repeated over and over again till the bad commit has been found.

1. Code: Select all

   git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git a

2. Code: Select all

   git bisect start

3. Code: Select all

   git bisect good adc218676eef25575469234709c2d87185ca223a

   (Good: Linux 6.12)

4. Code: Select all

   git bisect bad 40384c840ea1944d7c5a392e8975ed088ecf0b37

   (Bad: Linux 6.13-rc1)
   Output:

   Code: Select all

   Bisecting: 6011 revisions left to test after this (roughly 13 steps)
   [071b34dcf71523a559b6c39f5d21a268a9531b50] Merge tag 'sound-6.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound

5. git bisect good
   Output:

   Code: Select all

   Bisecting: 2956 revisions left to test after this (roughly 12 steps)
   [3e51108c72e8adbcf3180ed40527a2a9d2d0123b] Merge tag 'input-for-v6.13-rc0' of git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input

6. git bisect bad
   Output:

   Code: Select all

   Bisecting: 1531 revisions left to test after this (roughly 11 steps)
   [1f8bdc31c7222578a209146247c650055f3f4f40] Merge tag 'amd-drm-next-6.13-2024-11-06' of https://gitlab.freedesktop.org/agd5f/linux into drm-next

7. git bisect good
   Output:

   Code: Select all

   Bisecting: 768 revisions left to test after this (roughly 10 steps)
   [060fc106b6854d3289d838ac3c98eb17afb261d7] Merge tag 'unicode-next-6.13' of git://git.kernel.org/pub/scm/linux/kernel/git/krisman/unicode

8. git bisect good
   Output:

   Code: Select all

   Bisecting: 428 revisions left to test after this (roughly 9 steps)
   [42d9e8b7ccddee75989283cf7477305cfe3776ff] Merge tag 'powerpc-6.13-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux

9. git bisect good
   Output:

   Code: Select all

   Bisecting: 220 revisions left to test after this (roughly 8 steps)
   [b467ab82a9fde4b46c0cd2c299220857afb0e0d4] KVM: x86: expose MSR_PLATFORM_INFO as a feature MSR

10. git bisect bad
    Output:

    Code: Select all

    Bisecting: 103 revisions left to test after this (roughly 7 steps)
    [e3e0f9b7ae280f2f479f74ef7799f4108d0e7f77] Merge tag 'kvm-riscv-6.13-1' of https://github.com/kvm-riscv/linux into HEAD

11. git bisect bad
    Output:

    Code: Select all

    Bisecting: 51 revisions left to test after this (roughly 6 steps)
    [c9be85dabb376299504e0d391d15662c0edf8273] KVM: PPC: e500: Mark "struct page" dirty in kvmppc_e500_shadow_map()

12. git bisect bad (It seems bad because the host system doesn't boot - Maybe another issue)
    Output:

    Code: Select all

    Bisecting: 25 revisions left to test after this (roughly 5 steps)
    [12fac89950996e556a99eb16f0359307ed4c2566] KVM: Use plain "struct page" pointer instead of single-entry array

13. git bisect bad (It seems bad because the host system doesn't boot - Maybe another issue)
    Output:

    Code: Select all

    Bisecting: 12 revisions left to test after this (roughly 4 steps)
    [eec1e5db464eba928273b27246122d157fd0eff8] KVM: Annotate that all paths in hva_to_pfn() might sleep

    I have to stop bisecting because the X5000 doesn't boot with the last 2 test kernels and I don't really know if these kernels are bad or good.
    
    Cheers,
    Christian

[Roland]

Which boot arguments do you use?

root=LABEL=Mint mem=3500M

Please boot without the uInitrd-5.10.

Then I could not use the 'Label' for choosing the root filesystem! I am not going to relearn and move back to the ancien boot system... Rather I use older kernels, if the possibility to use uInitrd has been removed from the newest ones.

[xeno74]

Which boot arguments do you use?

root=LABEL=Mint mem=3500M

Please boot without the uInitrd-5.10.

Then I could not use the 'Label' for choosing the root filesystem! I am not going to relearn and move back to the ancien boot system... Rather I use older kernels, if the possibility to use uInitrd has been removed from the newest ones.

I just wanted to know if it boots without the uInitrd-5.10.

It boots and works on my X5000/40. Maybe we need a new uInitrd but we need to find out if the uInitrd is the problem.

[Roland]

I just wanted to know if it boots without the uInitrd-5.10.

It boots and works on my X5000/40. Maybe we need a new uInitrd but we need to find out if the uInitrd is the problem.

I do not enymore remember how to boot with the old system... I have removed the old scripts from my UBoot,

But I tested the final kernels backwards, and the newest one which still booted was 6.9. Instead, 6.10, 6.11, 6,12 and 6.13-a2 did not.

Can you guess any other reason than the uInitrd which could cause this kind of boot issue? uInitrd 5.10 is already very old, so shouldn't it be updated anyway?

PS. I did some further testing... Kernel 6.10-alpha3 was the last which booted normally! But 6.10rc1-4 did not any more...

[xeno74]

I created a new initial ramdisk as U-Boot image with Void PPC today.

Code: Select all

xbps-install dracut-053_5 uboot-mkimage

Code: Select all

dracut initrd-6.12.img 6.12.4-powerpc64-smp

Code: Select all

mkimage -T ramdisk -C gzip -n 'Kernel 6.12 uInitrd' -d initrd-6.12.img uInitrd-6.12

-- Testing --

Code: Select all

X5000> setenv bootargs root=LABEL=Void

Code: Select all

X5000> load sata 1:1 1000000 uImage-6.12

Code: Select all

X5000> load sata 1:1 1c00000 cyrus-p5040.dtb

Code: Select all

X5000> load sata 1:1 2000000 uInitrd-6.12

Code: Select all

X5000> bootm 1000000 2000000 1c00000

SUCCESS! cat /proc/cmdline: root=LABEL=Void

Download: uInitrd-6.12

[Roland]

Download: uInitrd-6.12

Thanks! I Dowloaded and tested it, but booting still works only up to 6.10-alpha3 .

This time halting of the boot process happens after the RTL 8169 ethernet card has been renamed, and after a couple of minutes this message starts to repeat itself on the screen:

Code: Select all

dracut: Scanning for all btrfs devices

I tried also to boot from a Sata3 controlle/drive instead of NVMe but not any change.

[xeno74]

Thanks! I Dowloaded and tested it, but booting still works only up to 6.10-alpha3 .

Oh dear, the old initrd isn't the issue but it is good that we have a new modern one built by dracut.

I tested the new uInitrd a lot today and it works great.

I'm sorry, I don't know what problem your X5000 has with the new kernels.

[Roland]

I tested the new uInitrd a lot today and it works great.

What string did you use in fstab to define the 'root'?

And do you have a swap partition on your system? Has it been defined in '/etc/initramfs-tools/conf.d/resume'?
(I do not have one).

[xeno74]

What string did you use in fstab to define the 'root'?

I don't use a string for root.

bash-5.1# cat /etc/fstab

Code: Select all

#
# See fstab(5).
#
# <file system>	<dir>	<type>	<options>		<dump>	<pass>
tmpfs		/tmp	tmpfs	defaults,nosuid,nodev   0       0

And do you have a swap partition on your system? Has it been defined in '/etc/initramfs-tools/conf.d/resume'?
(I do not have one).

I don't have one either.