Kernel panic upon boot

[pietinger]

That is embarasing, I meant DEBUG_KERNEL (forced by EXPERT),

Please, never try to disable it (there is also no reason to do it).

[...] And regarding the other thread - I specifically wanted to split from this thread, which I kind of hijacked

I see. Yes, open another thread if you have more questions. ... Maybe have more trust in kernel developers doing a great job with our Linux kernel.

[dmpogo]

That is embarasing, I meant DEBUG_KERNEL (forced by EXPERT),

Please, never try to disable it (there is also no reason to do it).
l.

BTW, why ? Or, better to say, why does trhis option in then exist and can be disabled if you are not an EXPERT ?

[pietinger]

BTW, why ? Or, better to say, why does trhis option in then exist and can be disabled if you are not an EXPERT ?

I can't give you a definite answer, but my strong suspicion is that it's because kernel developers are lazy. You have to understand this as a development over time. So that you don't have to enable everything separately, they simply configured this automatic activation. And yes, sometimes even "corpses" remain. How useful is this IF query? ->

Code: Select all

config DEBUG_BUGVERBOSE
        bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT

(Yes, sometimes they forget you can then remove something Yes, ‘if DEBUG_KERNEL’ would be sufficient.)

[dmpogo]

BTW, why ? Or, better to say, why does trhis option in then exist and can be disabled if you are not an EXPERT ?

I can't give you a definite answer, but my strong suspicion is that it's because kernel developers are lazy. You have to understand this as a development over time. So that you don't have to enable everything separately, they simply configured this automatic activation. And yes, sometimes even "corpses" remain. How useful is this IF query? ->

Code: Select all

config DEBUG_BUGVERBOSE
        bool "Verbose BUG() reporting (adds 70K)" if DEBUG_KERNEL && EXPERT

(Yes, sometimes they forget you can then remove something Yes, ‘if DEBUG_KERNEL’ would be sufficient.)

Yes, I noticed that !. But, I admiit, I was under impression that this organization was new to 6.x.x, but I looked and see that my 5.15 kernels have the same. I simply forgot when I configured them from scratch years ago.

Now I need to find out on what bus my trouchpad and sound sits

[dmpogo]

And here comes a new minor problem. After all the configuration, 'make' fails with

Code: Select all

  CC      certs/system_keyring.o
  HOSTCC  certs/extract-cert
  CERT    certs/x509_certificate_list
make[3]: *** No rule to make target '/var/tmp/portage/sys-kernel/gentoo-kernel-6.12.47/temp/kernel_key.pem', needed by 'certs/signing_key.x509'.  Stop.
make[2]: *** [scripts/Makefile.build:556: certs] Error 2
make[1]: *** [/usr/src/linux-6.17.7-gentoo/Makefile:2011: .] Error 2
make: *** [Makefile:248: __sub-make] Error 2

I guess x509_certificate_list was nit populated and empty ?

[pietinger]

dmpogo,

do you use genkernel? If yes, please create a new thread (I cannot help with genkernel). If no, please describe more detailed what you have installed. Maybe this article will help you:
https://wiki.gentoo.org/wiki/Signed_ker ... le_support

[Dimitri001]

This belongs in another thread but since I saw this by coincidence and I know the solution:

CONFIG_MODULE_SIG_KEY is set to /var/tmp/portage/sys-kernel/gentoo-kernel-6.12.47/temp/kernel_key.pem. Setting the default certs/signing_key.pem will cause a key and certificate to be created automatically.

As mentioned in the article pietinger shared, the generated key has to be secured for signing to have benefits.

[dmpogo]

dmpogo,

do you use genkernel? If yes, please create a new thread (I cannot help with genkernel). If no, please describe more detailed what you have installed. Maybe this article will help you:
https://wiki.gentoo.org/wiki/Signed_ker ... le_support

No, I do not. It is a plain gentoo-sources and menuconfig without initamfs. For now I disabled modules signing and it boots fine

[dmpogo]

This belongs in another thread but since I saw this by coincidence and I know the solution:

CONFIG_MODULE_SIG_KEY is set to /var/tmp/portage/sys-kernel/gentoo-kernel-6.12.47/temp/kernel_key.pem. Setting the default certs/signing_key.pem will cause a key and certificate to be created automatically.

As mentioned in the article pietinger shared, the generated key has to be secured for signing to have benefits.

Indeed, I did not notice that the path is set to ..../gentoo-kernel-6.12.47/... while I was compiling 6.17.7 kernel ! (6.12.47 is the kernel being run while compiling) ! Since I now have 6.17.7 running, I rebuild the kernel with modules signing on,
and compilation worked fine. I'll check again sometime if it still fails when I complile 6.17 while running 6.12

[amosbarsinai]

Hey...
So it's a slightly different problem this time.
I booted into the Gentoo LIveCD and shrunk my root directory to 128GiB (it's currently using only 68 of them). When then trying to boot it I received a kernel panic, and not even a graphic one, even though DRM_PANIC is enabled and compiled into the kernel.
This issue persisted until I resized my partition to exactly its original size and then everything seemed to work perfectly.
I couldn't find this issue online.
My /etc/fstab is as follows:

Code: Select all

/dev/sda1           /efi      vfat         defaults          0 2
/dev/sda2           none      swap         sw                0 0
/dev/sda3           /         btrfs        defaults          0 1

[NeddySeagoon]

amosbarsinai,

Your root filesystem is a block device within a block device.
When you shrank the partition, the filesystem it contained hung over the the end of the new smaller partition.

Doing what you want to do is a three step process.
1. Shrink the filesystem, too far.
2. Shrink the partition, so that there is unallocated space at the end.
3. Test.
4. Grow the filesystem to fit the partition.

Not all filesystems support shrinking. I'm not a btrfs user, so I'll let you discover that.

At no time must the filesystem be bigger than the block device that contains it.
If you had made a new partition and formatted it in tho middle of your root filesystem ... well, thats why you keep validated backups.

[amosbarsinai]

Yes, the issue was I didn't shrink the filesystem as well.
Thank you so much!