Kernel panic upon boot

[amosbarsinai]

I get a kernel panic immediately after my first boot (note that the hexadecimals might have some errors, I typed this by hand):

Code: Select all

/dev/root: Can't open blockdev
VFS: Cannot open root device "PARTUUID=<my root uuid...>" or unknown-block(0,0): error -6
Please append a correct "root=" boot option; here are the available partitions:
(note that no available partitions seem to be listed)
List of bdev filesystems:
 ext3
 ext2
 ext4
 xfs
 btrfs

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
CPU: 6 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.41-gentoo #1
Hardware name: ASUSTeK COMPUTER INC. Vivobook Go E1404GA_E1404GA/E1404GA, BIOS E1404GA.301 04/28/2023
Call Trace:
 <TASK>
 dump_stack_lvl+0x5d/0x80
 panic+0x157/0x32b
 mount_root_generic+0x1ec/0x270
 prepare_namespace+0x1ec/0x270
 kernel_init_freeable+0x2d7/0x310
 ? __pfx_kernel_init+0x10/0x10
 kernel_init+0x1a/0x140
 ret_from_fork+0x31/0x50
 ? __pfx_kernel_init+0x10/0x10
 ret_frin_firk_asm_0x1a/0x31
 </TASK>
Kernel Offset: 0x16000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xfffffffbffffff)
--[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0) ]--

[NeddySeagoon]

amosbarsinai,

The key here is

Code: Select all

unknown-block(0,0)

which tells that the kernel cannot see the block device holding the root partition.
That's confirmed by

Code: Select all

(note that no available partitions seem to be listed)

Either you intended to use an initrd and its not being loaded/used, then you would get a rescue shell, or you inteded to be able to boot without an initrd, in which case, you have something missing, or made as a module, that needs to be cofigured as built in.

[amosbarsinai]

Okay, but how do I fix it...?

[pietinger]

Okay, but how do I fix it...?

First we must know which kernel you have installed: Our Gentoo distribution kernel (gentoo-kernel / gentoo-kernel-bin; having an initramfs) or a self configured kernel (gentoo-sources).

IF our gentoo-kernel (or -bin) check if you have done all these steps described here:
https://wiki.gentoo.org/wiki/User:Pieti ... tem#Kernel

If gentoo-sources: Do you want a kernel WITH or without an initramfs?
With: https://wiki.gentoo.org/wiki/Dracut or https://wiki.gentoo.org/wiki/UgRD
Without: https://wiki.gentoo.org/wiki/User:Pieti ... figuration

Chrooting back into your installation is described here:
https://wiki.gentoo.org/wiki/User:Pieti ... stallation

[amosbarsinai]

So I just reran the whole installation guide, step-by-step, and the exact same thing happened... that's not supposed to happen, is it?
It's a self-configured kernel (gentoo-sources) with no initramfs.

[pietinger]

[...] It's a self-configured kernel (gentoo-sources) with no initramfs.

This means you must configure all kernel modules which the kernel needs to access the root partition static <*> (= as built-in) into the kernel.

As Neddy already said, (0,0) means: Kernel is not able to access the device. So, you have either configured some modules as <M>odule ... or ... you miss some important modules.

- pci
- scsi
- nvme
- sata
- filesystem

Have you read my Wiki article?

It contains also links to important other articles ... especially in this chapter:
https://wiki.gentoo.org/wiki/User:Pieti ... c_Settings
---->
https://wiki.gentoo.org/wiki/User:Pieti ... rsion_6.12
-OR-
https://wiki.gentoo.org/wiki/User:Pieti ... ent_Kernel (6.17 at the moment)

[NeddySeagoon]

amosbarsinai,

There is almost never any need to reinstall Gentoo. It's very difficult to break so badly that is the only option.

To spot whats missing from your kernel we need two things ...
The output of

Code: Select all

lspci -nnk

so we can see your hardware.
Your kernel .config file on a pastebin site.
wgetpaste can help there.

As well as the things pietinger mentioned, some Intel systems have some oddities that need to be taken care of.
You may find my Wiki page on the boot process of interest too.

[amosbarsinai]

So the problem is that I have some filesystem component that I either haven't compiled into the kernel at all, or marked it as a module? If so, could you please help me understand which?
I'm on BTRFS.

[pietinger]

So the problem is that I have some filesystem component that I either haven't compiled into the kernel at all, or marked it as a module? If so, could you please help me understand which?

Yes, we can help you to understand which ... but ... you really, really should read what we give you ... we can tell from the questions whether someone has read something or not ...

For example:

If ... IF you would have read this:

https://wiki.gentoo.org/wiki/User:Pieti ... _at_Gentoo

you would have found this link:

https://wiki.gentoo.org/wiki/User:Pieti ... nformation

telling you HOW to give us all needed information ... with wgetpaste ... and an "emerge --info"

If you would have read my wiki article about a manually kernel configuration (last post from me) you would have found a link to this old forums post from our forums legend Neddy:
https://forums.gentoo.org/viewtopic-p-8 ... ml#8688524

... which is not even necessary because I describe a "tour" to a kernel configuration where I describe everything you need (essentiell options).

Now start here: https://wiki.gentoo.org/wiki/User:Pieti ... _at_Gentoo and plan some hours for reading this one and all linked articles and then again all linked articles ....

[NeddySeagoon]

amosbarsinai,

We know nothing about the filesystem from the panic message. The kernel cannot find the underlying block device.
The numbers in unknown-block(x,y) are the kernel major, minior device numbers.
No block devices were found. If the kernel found the block device for the root fs, but was missing the fs, the numbers would show the block device it was trying to read.

Its a kernel build to fix. We can help but you need to provide the information so we can do that.

-- edit --
From your original post

Code: Select all

List of bdev filesystems:
 ext3
 ext2
 ext4
 xfs
 btrfs 

So btrfs is there.

[amosbarsinai]

Okay, thank you so much...
Pastebin URL: https://pastebin.com/5dYuLhgX
lspci output:

Code: Select all

livecd ~ # lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:4617]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: igen6_edac
lspci: Unable to load libkmod resources: error -2
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-N [UHD Graphics] [8086:46d0]
	DeviceName: Onboard - Video
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
00:04.0 Signal processing controller [1180]: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant [8086:461d]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: proc_thermal_pci
00:08.0 System peripheral [0880]: Intel Corporation GNA Scoring Accelerator [8086:467e]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
00:0a.0 Signal processing controller [1180]: Intel Corporation Platform Monitoring Technology [8086:467d] (rev 01)
	DeviceName: Onboard - Other
	Kernel driver in use: intel_vsec
00:12.0 Serial controller [0700]: Intel Corporation Alder Lake-N Integrated Sensor Hub [8086:54fc]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
00:12.6 Serial bus controller [0c80]: Intel Corporation Alder Lake-N Generic SPI (GSPI) Controller #2 [8086:54fb]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: intel-lpss
00:12.7 Universal Flash Storage controller [0109]: Intel Corporation Alder Lake-N UFS Controller [8086:54ff]
	DeviceName: Onboard - Other
	Kernel driver in use: ufshcd
00:14.0 USB controller [0c03]: Intel Corporation Alder Lake-N PCH USB 3.2 Gen 2x1 (10 Gb/s) xHCI Host Controller [8086:54ed]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:201f]
	Kernel driver in use: xhci_hcd
00:14.2 RAM memory [0500]: Intel Corporation Alder Lake-N PCH Shared SRAM [8086:54ef]
	DeviceName: Onboard - Other
00:15.0 Serial bus controller [0c80]: Intel Corporation Alder Lake-N PCH I2C Controller [8086:54e8]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: intel-lpss
00:16.0 Communication controller [0780]: Intel Corporation Alder Lake-N PCH HECI Controller [8086:54e0]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: mei_me
00:19.0 Serial bus controller [0c80]: Intel Corporation Alder Lake-N I2C Controller #4 [8086:54c5]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: intel-lpss
00:1c.0 PCI bridge [0604]: Intel Corporation Alder Lake-N PCI Express Root Port #4 [8086:54bb]
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Alder Lake-N PCH eSPI Controller [8086:5481]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Alder Lake-N PCH High Definition Audio Controller [8086:54c8]
	DeviceName: Onboard - Sound
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: sof-audio-pci-intel-tgl
00:1f.4 SMBus [0c05]: Intel Corporation Alder Lake-N SMBus [8086:54a3]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: i801_smbus
00:1f.5 Serial bus controller [0c80]: Intel Corporation Alder Lake-N SPI (flash) Controller [8086:54a4]
	DeviceName: Onboard - Other
	Subsystem: ASUSTeK Computer Inc. Device [1043:18f3]
	Kernel driver in use: intel-spi
01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821]
	Subsystem: AzureWave Device [1a3b:304a]
	Kernel driver in use: rtw_8821ce

[pietinger]

I dont know which harddisk you have ... a M.2 SSD (=NVMe) or a normal one ...

IF M.2 then you miss: # CONFIG_BLK_DEV_NVME is not set

For a normal AHCI you have already: CONFIG_SATA_AHCI=y but some systems need also: # CONFIG_SATA_AHCI_PLATFORM is not set

I dont see an Intel vmd device (if you would have you would need: # CONFIG_VMD is not set)


Not related to the kernel panic:

I see you have not included the CPU microcode:

CONFIG_EXTRA_FIRMWARE=""

This should also not be the cause of the kerenl panic, but I suggest to enable it also: # CONFIG_INTEL_IOMMU_DEFAULT_ON is not set

[amosbarsinai]

Okay, thanks... And then just rerun

Code: Select all

make
make install

?
No need for regenerating GRUB (the vmlinuz will have the same name...)?

[amosbarsinai]

Also, are all of the options you mentioned booleans? (CONFIG_EXTRA_FIRMWARE seems to be a string...)

[pietinger]

Okay, thanks... And then just rerun

Code: Select all

make
make install

?
No need for regenerating GRUB (the vmlinuz will have the same name...)?

It depends (what "make install" do with the naming of the new and old kernel) ... if the new kernel has a new name then you need grub-mkconfig again ,,, to be on a safe side I always recommend to do it (see my cheat sheet)

[pietinger]

Also, are all of the options you mentioned booleans? (CONFIG_EXTRA_FIRMWARE seems to be a string...)

Yes, it is a string ... where you can include firmware files ... AND ... your CPU microcode ... today it is very easy to select the needed file ... see more in this very old post: https://forums.gentoo.org/viewtopic-t-1065464.html

[NeddySeagoon]

pietinger,

It's difficult for me to review the .config file on my phone :) so I won't, for now anyway.
I'm still following the topic though.

-- edit--

CONFIG_ExTRA_FIRMWARE is a space seperated list of pathnames with respect to /lib/firmware/ although that default can be changed too.

[pietinger]

P.S.: I dont know if this is a server machine or if you want use it as a desktop (=with a GUI)?

IF desktop you miss: # CONFIG_DRM is not set

(and then Intel related modules)

I guess you have booted with a minimal or Admin CD ... here you will not see the loaded i915 module ... I suggest to boot with our LiveCD and THEN do number 2 of:
https://wiki.gentoo.org/wiki/User:Pieti ... _you_start

[pietinger]

pietinger,

It's difficult for me to review the .config file on my phone so I won't, for now anyway.
I'm still following the topic though.

No problem ... I already did it ... but I must leave in one hour (back at late night).

[amosbarsinai]

I'm using the LiveCD. And yeah, I generally want this computer to be usable as a personal laptop...
About the config file fixes you suggested, could you please explain what exactly you suggest to fix them to? (The y/n/m flags are easy, but the string values...)

[NeddySeagoon]

amosbarsinai,

The string values for your CPU microcode depend on the CPU model and sometimes the stepping.
They are not make or break for booting so can be left for your next kernel update.

The microcode can exist in three places.
1. It's programmed into the CPU at manufacture.
2. The UEFI firmware can update the microcode. if it contains a newer microcode that the CPU.
3. The kernel can also update after the UEFI firmware, if it has a newer still microcode.

microcode updates are used to fix errors in the CPU operation. You CPU will work without any microcode updates, so it will boot, but it way have unfixed errors, which include security updates.

[NeddySeagoon]

amosbarsinai,

Code: Select all

CONFIG_PINCTRL_ALDERLAKE=m

could be a problem.
Many chipsets use pinctrl for powers thing on/off, so it may be required for booting. Better make it built in

Here's a link I couldn't get to earlier PC Boot Process

[amosbarsinai]

So I enabled the CONFIG_PINCTRL_ALDERLAKE, CONFIG_PINCTRL_INTEL, CONFIG_PINCTRL_INTEL_PLATFORM, CONFIG_SATA_AHCI_PLATFORM, and CONFIG_VMD options with 'y' (not 'm'), reran make && make modules_install and later make install, even reran the grub install and mkconfig, and still the kernel panics on boot...

[Hu]

Is it the same panic output as before? There are multiple ways to produce a non-working system, so since you made some changes, we need to understand (a) whether the changes were picked up[1] and (b) whether the changes fixed the reported problem (and thus revealed a new problem). If the output changed, we may need a new round of output in order to diagnose the new problem.

[1]: It's quite common for people to mishandle the kernel install and continue running the old known-bad kernel instead of switching to the improved kernel they meant to use.

[pietinger]

So I enabled [...] with 'y' (not 'm'), [...]

To me, this sounds like you edited the .config with an editor. If that's the case, then:

1. Make sure you read this chapter:
https://wiki.gentoo.org/wiki/User:Pieti ... it_.config
2. Discard this configuration and start over
3. Read the entire article.
4. If you still need help, tell us what you did and when you did it ... feedback ... so we don't have to guess. An “emerge --info” is still missing... even though it was requested.

Yes, a kernel configuration cannot be done in a few minutes; just reading the articles takes hours, and then there's the actual configuration.

Have you really read all the articles? Especially this paragraph from https://wiki.gentoo.org/wiki/User:Pieti ... _recommend:

If you are looking for help with a problem in the Gentoo Forum and forgot to read the Guidelines [[5]] beforehand, here is the most important information:

* The more precisely you describe your problem, the greater the chance that others will be able to help you straight away - An exact description of the problem is already half the solution.

* If Portage tells you [...]

* If your problem has been solved,[...]

* Even if you are frustrated with your problem, stay friendly and polite on the Forum; all users on the forum are volunteers and do not earn money for their help. The only thing we get is a "thank you" (and sometimes not even that). The same applies to our IRC channels.

[...] (The y/n/m flags are easy, but the string values...)

If you ask questions that are answered precisely and clearly in an article, then I know you haven't read the link.