Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#72132 - BOOT_IMAGE (Linux command line "error" reported in log)

Attached to Project: Arch Linux
Opened by Jim Davis (metadope) - Tuesday, 14 September 2021, 14:59 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 19 September 2021, 08:13 GMT
Task Type Bug Report
Category Kernel
Status Assigned
Assigned To Ronald van Haren (pressh)
Jan Alexander Steffens (heftig)
Christian Hesse (eworm)
Levente Polyak (anthraxx)
Architecture x86_64
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No


Description: BOOT_IMAGE (Linux command line "error" reported in logs since v5.14)

This is the lowest-level bug possible, just pollution in the boot log witnessed via dmesg since Arch kernel 5.14.

Upstream denies responsibility and kicks it back down to distributors:

Steps to reproduce:
1) boot Arch with linux 5.14 or later
2) witness the single line of noise produced by the kernel in the log (sample):

[ 0.047266] Unknown command line parameters: BOOT_IMAGE=/boot/vmlinuz-linux

So, BOOT_IMAGE is no longer used or swallowed silently by the kernel...

Should this actually fall downstream to GRUB?
This task depends upon

Comment by loqs (loqs) - Tuesday, 14 September 2021, 16:15 GMT
This was expected when the commit was introduced [1]. Grub adds the parameter BOOT_IMAGE [2] which the kernel now issues a notice message about.

Comment by Christian Hesse (eworm) - Monday, 20 September 2021, 07:03 GMT
Guess we can close this with "won't fix", no? Any objections?
Comment by Cedric (Cbhihe) - Thursday, 23 September 2021, 07:01 GMT
Not adding anything new, just reporting the fact that for me as well since update to v5.14 the exact same message appears in my `journalctl -b` output. I am actually surprised that users do not report this "en-masse". Also what is the use of BOOT_IMAGE now ?

kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=0f2397cc-ee76-44b5-b7d...
kernel: Unknown command line parameters: BOOT_IMAGE=/vmlinuz-linux
Comment by Michele (mileon) - Saturday, 13 August 2022, 08:14 GMT
Same with syslinux
"Unknown kernel command line parameters "BOOT_IMAGE=../vmlinuz-linux", will be passed to user space."

uname -a:
Linux m2 5.18.16-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 03 Aug 2022 11:25:04 +0000 x86_64 GNU/Linux

syslinux 6.04