Hello,
I cannot boot using the new kernel 6.12 LTS (kernel panic) but I am still able to boot using an old kernel 6.1 LTS initramfs.
Desktop PC - Manjaro 26.0.0
Let me know what info you require
Thanks in advance
P.
Hello @lappetspm !
Please post at least the result of inxi -zv8 so we get more info about your system.
When posting the info, either put three backticks ( ` -sign) on an empty line before and after it, or paint over the text and then press “preformatted text” </> from the post toolbar. With long entries, you might also want to use “hide details” on it from behind the + -button on the toolbar to make the post more manageable.
1 Like
Or:
click the </> button - a black field will appear
paste your output in it
2 Likes
System:
Kernel: 6.1.159-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64
root=UUID=afd6fdc8-a2ba-48e6-9a1e-793b6468f3cd rw apparmor=1
security=apparmor udev.log_priority=3
Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.51 wm: xfwm4 v: 4.20.0
with: xfce4-panel tools: light-locker vt: 7 dm: LightDM v: 1.32.0
Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop System: NOVATECH product: MBB-81004 v: V1.0
serial: <superuser required> Chassis: type: 3 v: 1.0
serial: <superuser required>
Mobo: Gigabyte model: H310M S2H v: x.x serial: <superuser required>
part-nu: MBB-81004 uuid: <superuser required> Firmware: UEFI-[Legacy]
vendor: American Megatrends v: FJ date: 08/21/2018
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 16 GiB available: 15.56 GiB used: 3.23 GiB (20.8%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 64 GiB slots: 4 modules: 1 EC: None
max-module-size: 16 GiB note: est.
Device-1: ChannelA-DIMM0 type: DDR4 detail: synchronous size: 16 GiB
speed: 2400 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
data: 64 total: 64 manufacturer: Crucial part-no: CT16G4DFD824A.C16FHD
serial: <filter>
Device-2: ChannelA-DIMM1 type: no module installed
Device-3: ChannelB-DIMM0 type: no module installed
Device-4: ChannelB-DIMM1 type: no module installed
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: Intel Core i3-8100 bits: 64 type: MCP arch: Coffee Lake
gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xB (11) microcode: 0x8E
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 smt: <unsupported> cache:
L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
L3: 6 MiB desc: 1x6 MiB
Speed (MHz): avg: 800 min/max: 800/3600 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 28808
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat arch_perfmon
art avx avx2 bmi1 bmi2 bts clflush clflushopt cmov constant_tsc cpuid
cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts ept ept_ad erms est f16c
flexpriority flush_l1d fma fpu fsgsbase fxsr ht hwp hwp_act_window
hwp_epp hwp_notify ibpb ibpb_exit_to_user ibrs intel_pt invpcid
invpcid_single lahf_lm lm mca mce mmx monitor movbe mpx msr mtrr
nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln
pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep smap
smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow
tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic xgetbv1 xsave
xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling status: Vulnerable: No microcode
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
disabled
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
SMT disabled
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Vulnerable: Clear CPU buffers attempted, no
microcode; SMT disabled
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled;
RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Vulnerable: No microcode
Type: tsa status: Not affected
Type: tsx_async_abort status: Not affected
Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
Device-1: NVIDIA GF108 [GeForce GT 430] driver: nouveau v: kernel non-free:
series: 390.xx+ status: legacy (EOL~2022-11-22) last: release: 390.157
kernel: 6.0 xorg: 1.21 arch: Fermi code: GF1xx process: 40/28nm
built: 2010-2016 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
active: VGA-1 empty: DVI-I-1,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:0de1
class-ID: 0300 temp: 40.0 C
Display: x11 server: X.Org v: 21.1.21 compositor: xfwm4 v: 4.20.0 driver:
X: loaded: modesetting alternate: fbdev,vesa dri: nouveau gpu: nouveau
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26")
s-diag: 584mm (22.99")
Monitor-1: VGA-1 model: Samsung S24F350 serial: <filter> built: 2016 res:
mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2 chroma: red:
x: 0.651 y: 0.333 green: x: 0.318 y: 0.612 blue: x: 0.153 y: 0.067 white:
x: 0.314 y: 0.329 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
ratio: 16:9 modes: 1920x1080, 1680x1050, 1600x900, 1280x1024, 1440x900,
1280x800, 1152x864, 1280x720, 1024x768, 832x624, 800x600, 640x480,
720x400
API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
drv: nouveau inactive: wayland
API: OpenGL v: 4.5 compat-v: 4.3 vendor: mesa v: 25.3.2-arch1.1 glx-v: 1.4
direct-render: yes renderer: NVC1 device-ID: 10de:0de1 memory: 974.6 MiB
unified: no
Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel
v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA GF108 High Definition Audio driver: snd_hda_intel
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1
chip-ID: 10de:0bea class-ID: 0403
API: ALSA v: k6.1.159-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.4.9 status: off tools: pw-cli
Server-3: PulseAudio v: 17.0-98-gb096 status: active with: pulseaudio-alsa
type: plugin tools: pacat,pactl,pavucontrol
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
Info: services: mld,NetworkManager
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 279.47 GiB used: 72.53 GiB (26.0%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: WDC WDS240G2G0A-00JH30
size: 223.57 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 0400 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: OCZ model: AGILITY3 size: 55.9 GiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 2.25 scheme: MBR
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 106.81 GiB size: 104.58 GiB (97.91%)
used: 72.53 GiB (69.4%) fs: ext4 dev: /dev/sda3 maj-min: 8:3 label: N/A
uuid: afd6fdc8-a2ba-48e6-9a1e-793b6468f3cd
ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 6.2 MiB (1.2%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: N/A
uuid: 17A8-360C
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 18 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/sda4 maj-min: 8:4 label: N/A
uuid: c5d916d1-75c5-41d4-ba03-b97e4947a630
Unmounted:
ID-1: /dev/sda2 maj-min: 8:2 size: 97.26 GiB fs: ext4 label: N/A
uuid: 7c4b9261-26d8-4cd8-8f8d-729ece698ee9
ID-2: /dev/sdb1 maj-min: 8:17 size: 49.94 GiB fs: ext4 label: N/A
uuid: 2973e173-1692-4dde-b422-c59d24189351
ID-3: /dev/sdb2 maj-min: 8:18 size: 1 KiB fs: <superuser required>
label: N/A uuid: N/A
ID-4: /dev/sdb5 maj-min: 8:21 size: 5.96 GiB fs: swap label: N/A
uuid: 3cbd46d1-59e6-4068-9e77-8fcc3934382c
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 1-1:2 info: Logitech Keyboard K120 type: keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 90mA
chip-ID: 046d:c31c class-ID: 0300
Device-2: 1-5:3 info: Logitech Mouse type: mouse
driver: hid-generic,usbhid interfaces: 1 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 046d:c077 class-ID: 0301
Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 31.0 C pch: 36.0 C mobo: N/A gpu: nouveau
temp: 40.0 C
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 1606 libs: 462 tools: pamac pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
2: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
3: https://manjaro.mirrors.uk2.net/stable/$repo/$arch
4: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 236
1: cpu: 100% command: ps pid: 12036 mem: 3.80 MiB (0.0%)
2: cpu: 8.5% command: chromium pid: 11637 mem: 259.9 MiB (1.6%)
3: cpu: 4.0% command: chromium pid: 2384 mem: 467.1 MiB (2.9%)
4: cpu: 2.8% command: chromium pid: 2372 mem: 477.8 MiB (2.9%)
5: cpu: 2.1% command: chromium pid: 5133 mem: 242.6 MiB (1.5%)
Memory top: 5 of 236
1: mem: 477.8 MiB (2.9%) command: chromium pid: 2372 cpu: 2.8%
2: mem: 467.1 MiB (2.9%) command: chromium pid: 2384 cpu: 4.0%
3: mem: 360.7 MiB (2.2%) command: chromium pid: 2225 cpu: 1.8%
4: mem: 305.1 MiB (1.9%) command: chromium pid: 2361 cpu: 0.3%
5: mem: 259.9 MiB (1.6%) command: chromium pid: 11637 cpu: 8.5%
Info:
Processes: 236 Power: uptime: 1h 48m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.19 GiB services: upowerd,xfce4-power-manager
Init: systemd v: 258 default: graphical tool: systemctl
Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash v: 5.3.9
running-in: xfce4-terminal inxi: 3.3.40
Hello,
I’ve posted the results is there anything else you need me to do ?
At this point we wait for people to look over it.
linux54
linux510
linux515
linux61
linux66
linux612
are all LTS kernels
Have you tried installing and booting one of the other ones?
How did you install the linux612 kernel?
Have you tried to install it again?
before you do that:
refresh your list of mirrors
sudo pacman-mirrors -f
and remove the package from cache - to force a re-download of a fresh copy:
sudo rm /var/cache/pacman/pkg/linux612*
The checksum should make sure that it isn’t corrupted, but I’d do that anyway just in case …
Maybe you can transcribe what you see on screen when the panic happens - perhaps some text just before the panic is announced
to get some context?
1 Like
Hello, thanks for your reply.
I have just tried to boot from all the kernels available on the menu, 5.15, 6.1, 6.6 and 6.12 but all fail with the kernel panic message. Kernel 5.4 failed with a different message.
Kernel panic message is preceded by x86/cpu: SGX disabled by BIOS.
Then
kernel panic - not syncinging: VFS: Unable to mount root fs on unknown-block(0,0)
then lots of other messages below.
I am able to boot using kernel 6.1 with fallback initramfs option only
Help!
All updates installed via the package manager except the one today which failed to display authentication password box so I installed it from the sixth virtual console.
I would try regenerating one initrd at a time
pick one of the ones that are currently not working - to preserve/not touch the only one that is still working
for instance the linux612 one:
sudo mkinitcpio -p linux612
sudo update-grub
See whether you can then boot this one.
Did you replace some .pacnew files instead of properly merging them?
Especially /etc/mkinitcpio.conf ?
Ok. I tried to regenerate kernel linux612 following your instructions but booting still failed with kernel panic message. Then tried the same for Linux515 and Linux66 but with the same result.
Please provide the output of the following commands:
First, the entire contents of the /etc/mkinitcpio.conf file:
cat /etc/mkinitcpio.conf
And, to isolate just the active (i.e. uncommented) settings within that file:
cat /etc/mkinitcpio.conf | grep -e '=' | grep -v '^#'
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(usbhid xhci_hcd)
MODULES=()
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=()
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No RAID, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect modconf block filesystems fsck)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev modconf block filesystems fsck)
#
## This setup assembles a mdadm array with an encrypted root file system.
## Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
# HOOKS=(base udev modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
## This setup loads an lvm2 volume group.
# HOOKS=(base udev modconf block lvm2 filesystems fsck)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr and fsck hooks.
HOOKS=(base udev autodetect modconf kms block keyboard keymap consolefont plymouth filesystems fsck)
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
#COMPRESSION="zstd"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
# MODULES_DECOMPRESS
# Decompress kernel modules during initramfs creation.
# Enable to speedup boot process, disable to save RAM
# during early userspace. Switch (yes/no).
#MODULES_DECOMPRESS="yes"
MODULES=()
BINARIES=()
FILES=()
HOOKS=(base udev autodetect modconf kms block keyboard keymap consolefont plymouth filesystems fsck)
It looks like you haven’t been maintaining your .pacnew & .pacsave files, as microcode was added to the hooks a couple of years ago. Also, there has been a recent change to using systemd-based hooks instead of busybox, so some HOOKS have been replaced or are no longer required.
This is what my HOOKS line looks like:
HOOKS=(systemd autodetect microcode modconf kms keyboard sd-vconsole block filesystems fsck)
You could probably change yours to the same. Make sure the HOOKS are in the same order.
I don’t use plymouth, which is why it is not in my HOOKS; however your inxi output shows that your boot parameters don’t include splash, so you could leave plymouth out of your /etc/mkinitcpio.conf.
After editing your /etc/mkinitcpio.conf file, ensure you run:
sudo mkinitcpio -P && sudo update-grub
And then reboot, hopefully into a working kernel.
Further reading:
Instructions for dealing with .pacnew & .pacsave files:
And mkinitcpio common HOOKS:
1 Like
Changed Hooks line, ran the command line re-booted but still the same issue. I tried the other kernels but nothing has changed. Please advise.
So is 6.18. 
1 Like
I installed kernel 6.17 but still receive kernel panic after boot.
I also reset mirrors and removed old package files before re-installing linux612 kernel
Update - I generated a fallback image for kernel 6.12 and this is working ok, so I now have two fallback images booting ok but none of the stripped back kernels work. What impact,if any, will this have on my running system?
If a fallback image works, and a striped down image does not:
You need to look into what is missing.
Go, look into your mkinitcpio.conf and find the error.
3 Likes