CachyOS
[BUG] Kernel panic on boot after upgrading kernel from cachyos-linux-lto (6.16.1-2) to cachyos-linux (6.16.4-2) on Asus Vivobook X515EA
Bug Summary
cachyos-linux (6.16.4-2) have problem to boot on Asus Vivobook X515EA and kernel panic with communicate:
Oops: general protection fault, probably for non-canonical address 0x3ed6111a856be48
Crash occurs randomly sometimes kernel boots to systemd stage and spamming with information thats some program causes a kernel (modules?) to crash
Step to reproduce
- Boot to kernel cachyos-linux (6.16.4-2)
- Wait for systemd to start services
- After approximately 11-30s you will get bluescreen or black screen with a kernel panic log
System Information
Device: VivoBook_ASUSLaptop X515EA_X515EA
BIOS: X515EA.316 03/14/2024
Distribution: CachyOS (up to date)
Bootloader: limine
Kernel: cachyos-linux (6.16.4-2) (i tested also rc version)
No NVIDIA GPU
Logs:
Notes
If you need more information ask for it
Can you check if "linux-cachyos-gcc" kernel works? Also, the RC Kernel would be interesting.
It seems like something at BTRFS makes this crash.
linux-cachyos-gcc kernel boots to system but leaves a Oops in dmesg:
[ 33.242624] usbcore: registered new interface driver r8152
[ 33.243589] Oops: Oops: 0000 [#1] SMP NOPTI
[ 33.243593] CPU: 7 UID: 0 PID: 2142 Comm: (udev-worker) Tainted: G U 6.16.4-2-cachyos-gcc #1 PREEMPT(full) 45449057af8e04de57c683a24f2e31996de5db8d
[ 33.243598] Tainted: [U]=USER
[ 33.249724] Hardware name: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515EA_X515EA/X515EA, BIOS X515EA.316 03/14/2024
[ 33.250734] RIP: 0010:blk_mq_free_rqs+0x10e/0x230
[ 33.251750] Code: 0f 84 8a 00 00 00 44 8b 5d 00 4c 8d 48 f8 41 ba 00 10 00 00 45 31 c0 45 85 db 0f 84 09 01 00 00 4c 89 ce 48 2b 35 ca 37 4d 01 <49> 8b 79 28 31 d2 48 c1 fe 06 48 c1 e6 0c 48 03 35 c5 37 4d 01 c4
[ 33.252740] RSP: 0018:ffffcfacc7cdfa08 EFLAGS: 00010202
[ 33.253952] RAX: 0000000000000000 RBX: ffff8ed249d30460 RCX: ffff8ed24dcefe00
[ 33.255157] RDX: 0000000000000000 RSI: 00000fc9bffffff8 RDI: ffff8ed24d700008
[ 33.256285] RBP: ffff8ed249ebdf00 R08: 0000000000000000 R09: fffffffffffffff8
[ 33.257390] R10: 0000000000001000 R11: 00000000000000ff R12: ffff8ed249d303c0
[ 33.258518] R13: 0000000000000000 R14: ffff8ed24d700008 R15: ffff8ed24d700008
[ 33.259471] FS: 00007f636188d880(0000) GS:ffff8ed606889000(0000) knlGS:0000000000000000
[ 33.260396] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 33.261279] CR2: 0000000000000020 CR3: 000000015584b004 CR4: 0000000000f70ef0
[ 33.262166] PKRU: 55555554
[ 33.263022] Call Trace:
[ 33.263880] <TASK>
[ 33.264725] blk_mq_free_map_and_rqs+0x17/0x60
[ 33.265585] blk_mq_free_sched_tags+0x34/0x70
[ 33.266430] elevator_change_done+0x4a/0x1f0
[ 33.267290] elevator_change+0xdb/0x180
[ 33.268149] elv_iosched_store+0x1ef/0x210
[ 33.269003] kernfs_fop_write_iter+0x135/0x1f0
[ 33.269853] vfs_write+0x32c/0x4f0
[ 33.270721] __x64_sys_write+0x70/0xe0
[ 33.271568] do_syscall_64+0x81/0x970
[ 33.272416] ? vsnprintf+0x429/0x5d0
[ 33.273252] ? vscnprintf+0x12/0x30
[ 33.274092] ? sysfs_emit+0xad/0xc0
[ 33.274932] ? __pfx_queue_rotational_show+0x10/0x10
[ 33.275765] ? queue_rotational_show+0x29/0x30
[ 33.276591] ? queue_attr_show+0x8d/0xb0
[ 33.277405] ? __x64_sys_fcntl+0x80/0x110
[ 33.278224] ? do_syscall_64+0x81/0x970
[ 33.279037] ? __x64_sys_read+0x70/0xe0
[ 33.279851] ? do_syscall_64+0x81/0x970
[ 33.280666] ? clear_bhb_loop+0x50/0xa0
[ 33.281475] ? clear_bhb_loop+0x50/0xa0
[ 33.282274] ? clear_bhb_loop+0x50/0xa0
[ 33.283082] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[ 33.283881] RIP: 0033:0x7f63610a49e7
[ 33.284714] Code: 46 ba 04 00 00 00 48 8b 05 1e 73 18 00 64 89 10 48 c7 c2 ff ff ff ff 48 83 c4 18 48 89 d0 c3 0f 1f 40 00 48 8b 44 24 20 0f 05 <48> 89 c2 48 3d 00 f0 ff ff 77 0e 48 89 d0 48 83 c4 18 c3 66 0f 1f
[ 33.285564] RSP: 002b:00007ffd0f4b0570 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
[ 33.286410] RAX: ffffffffffffffda RBX: 000055843fc1c0f0 RCX: 00007f63610a49e7
[ 33.287262] RDX: 0000000000000004 RSI: 00007ffd0f4b0880 RDI: 0000000000000015
[ 33.288116] RBP: 0000000000000004 R08: 0000000000000000 R09: 0000000000000000
[ 33.288971] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000004
[ 33.289815] R13: 00007ffd0f4b0880 R14: 0000000000000000 R15: 00007ffd0f4b0880
[ 33.290674] </TASK>
[ 33.291511] Modules linked in: snd_pcm kvm_intel(+) spi_pxa2xx_platform btintel libarc4 dw_dmac btbcm uvcvideo snd_timer btmtk hid_multitouch kvm spi_pxa2xx_core 8250_dw cfg80211 videobuf2_vmalloc asus_nb_wmi snd mei_pxp mei_hdcp processor_thermal_device_pci_legacy uvc irqbypass bluetooth rapl processor_thermal_device videobuf2_memops asus_armoury intel_rapl_msr processor_thermal_wt_hint videobuf2_v4l2 intel_cstate platform_temperature_control r8152 videobuf2_common firmware_attributes_class intel_uncore mii asus_wmi i2c_i801 processor_thermal_rfim videodev spi_nor pcspkr i2c_smbus libphy platform_profile processor_thermal_rapl sparse_keymap mtd wmi_bmof intel_lpss_pci soundcore mdio_bus intel_rapl_common i2c_mux mei_me mc intel_lpss processor_thermal_wt_req rfkill idma64 processor_thermal_power_floor mei processor_thermal_mbox igen6_edac intel_soc_dts_iosf i2c_hid_acpi i2c_hid mousedev joydev intel_pmc_core intel_oc_wdt int3403_thermal pmt_telemetry int340x_thermal_zone pmt_class int3400_thermal
[ 33.291567] intel_pmc_ssram_telemetry pinctrl_tigerlake acpi_tad acpi_thermal_rel acpi_pad mac_hid ntsync i2c_dev crypto_user loop nfnetlink lz4 zram 842_decompress 842_compress lz4hc_compress lz4_compress ip_tables x_tables dm_crypt encrypted_keys trusted asn1_encoder tee dm_mod xe drm_ttm_helper nvme drm_suballoc_helper gpu_sched nvme_core drm_gpuvm nvme_keyring drm_exec nvme_auth drm_gpusvm i915 i2c_algo_bit polyval_clmulni drm_buddy ghash_clmulni_intel ttm sha512_ssse3 sha1_ssse3 intel_gtt aesni_intel drm_display_helper spi_intel_pci spi_intel vmd cec intel_vsec video wmi serio_raw
[ 33.299190] CR2: 0000000000000020
[ 33.300200] ---[ end trace 0000000000000000 ]---
[ 33.301297] RIP: 0010:blk_mq_free_rqs+0x10e/0x230
[ 33.302398] Code: 0f 84 8a 00 00 00 44 8b 5d 00 4c 8d 48 f8 41 ba 00 10 00 00 45 31 c0 45 85 db 0f 84 09 01 00 00 4c 89 ce 48 2b 35 ca 37 4d 01 <49> 8b 79 28 31 d2 48 c1 fe 06 48 c1 e6 0c 48 03 35 c5 37 4d 01 c4
[ 33.303532] RSP: 0018:ffffcfacc7cdfa08 EFLAGS: 00010202
[ 33.304681] RAX: 0000000000000000 RBX: ffff8ed249d30460 RCX: ffff8ed24dcefe00
[ 33.305827] RDX: 0000000000000000 RSI: 00000fc9bffffff8 RDI: ffff8ed24d700008
[ 33.306980] RBP: ffff8ed249ebdf00 R08: 0000000000000000 R09: fffffffffffffff8
[ 33.308147] R10: 0000000000001000 R11: 00000000000000ff R12: ffff8ed249d303c0
[ 33.309311] R13: 0000000000000000 R14: ffff8ed24d700008 R15: ffff8ed24d700008
[ 33.310468] FS: 00007f636188d880(0000) GS:ffff8ed606889000(0000) knlGS:0000000000000000
[ 33.311617] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 33.312753] CR2: 0000000000000020 CR3: 000000015584b004 CR4: 0000000000f70ef0
[ 33.313887] PKRU: 55555554
[ 33.314993] note: (udev-worker)[2142] exited with irqs disabled
And cachyos-rc output looks like this: (hangs in this spot)
That is odd. "linux-cachyos-lto" was removed because the default kernel contains now finally the LTO variant, after NVIDIA fixed their bug.
I guess these above are upstream issues, and it would be wroth to retest with the upcoming 6.16.5 and rc4, otherwise needs to be reported upstream.
Can you try the "linux" kernel from archlinux?
sudo pacman -S core/linux core/linux-headers
On linux from core repo i gets spam of oops and of the end i get kernel panic
@ptr1337 So whats now? This will be reported to Arch Linux kernel bug tracker or to linux mainline kernel bug tracker? Or we test new things?
@ptr1337 So whats now? This will be reported to Arch Linux kernel bug tracker or to linux mainline kernel bug tracker? Or we test new things?
Please try 6.17.0rc4, as soon available. Otherwise we need to report the issue upstream
Yep the same issue on 6.17.0rc4 Do you need some more info about my hardware?
@ptr1337 Any updates about issue?
We likely should report this issue to https://bugzilla.kernel.org You can also test 6.16.5 please and see if smth improves, but i dont expect so
You can also test 6.16.5 please and see if smth improves, but i dont expect so
Yep nothing new
@ptr1337 Any updates? Because 2 weeks pass and you didnt report any issues to kernel bug tracker UPDATE: Idk if this was reported or not but on the latest 6.17.0-rc6-1-cachyos-rc and linux-mainline kernel is not crashing UPDATE2: Nevermind is was a some sort of luck after reboot is kernel panicking
This is a joke that this issue is still not reported to kernel bugzilla because someone forgot and have this repo in ***. Someone will ask me "why don't I report by myself?" because on the main page of bugzilla we clearly see that bugs need to be reported to the distribution bugtracker first.
Sorry, but distributions are not obligated to report bugs for you. All of us here are working on our free time and trying to report every bug that gets sent to us can get overwhelming very quickly, especially with other things going on real life such as work and education. It's one thing if the bug is reproducible on our machines, but none of us (AFAIK) can reproduce this bug, so there's going to be a communication issue during the report, which would look something like:
- Kernel dev asks for more info
- CachyOS maintainer receives info and asks for info from the user
- User gives info to CachyOS maintainer
- CachyOS maintainer gives user info to kernel dev
Instead of reporting the bug yourself:
- Kernel dev asks for more info
- User gives info
See which one is preferable :)
we clearly see that bugs need to be reported to the distribution bugtracker first.
Well, yes. That's for cases where the bug lies in the packaging and/or patches that distributions may carry. In this case, we've already confirmed that the bug lies in the upstream kernel, so the right place for this bug report is the kernel bugzilla.
