Bogon kernel command line options - revision history

Dank at 00:31, 13 March 2022

2022-03-13T00:31:05Z

← Older revision		Revision as of 00:31, 13 March 2022
Line 28:		Line 28:
	<tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 root=UUID=939be09a-b63d-403c-996a-8b9866313fbb ro mem_encrypt=off psi=0 acpi_enforce_resources=lax intel_iommu=on</tt>		<tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 root=UUID=939be09a-b63d-403c-996a-8b9866313fbb ro mem_encrypt=off psi=0 acpi_enforce_resources=lax intel_iommu=on</tt>

	<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here]. <tt>acpi_enforce_resources=~~lex~~</tt> is sadly necessary to control my bling-ass LEDs using [https://openrgb.org/ OpenRGB].		<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here]. <tt>acpi_enforce_resources=lax</tt> is sadly necessary to control my bling-ass LEDs using [https://openrgb.org/ OpenRGB].

	anyway, i wasn't aware of this dmesg output (added on [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line!		anyway, i wasn't aware of this dmesg output (added on [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line!

Dank at 00:30, 13 March 2022

2022-03-13T00:30:37Z

← Older revision		Revision as of 00:30, 13 March 2022
Line 21:		Line 21:
	<li><tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2</tt> this is set by [https://www.gnu.org/software/grub/ GRUB] since 1.91, released 2005-10-15. i'm not sure why, or who consumes it. LILO set this parameter as well, and this might have just been a compatibility thing, so it might be lost in the river of time.</li>		<li><tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2</tt> this is set by [https://www.gnu.org/software/grub/ GRUB] since 1.91, released 2005-10-15. i'm not sure why, or who consumes it. LILO set this parameter as well, and this might have just been a compatibility thing, so it might be lost in the river of time.</li>
	<li><tt>mem_encrypt=off</tt> this refers to AMD's [https://en.wikichip.org/wiki/x86/sme Secure Memory Encryption] extension, allowing per-page transparent encryption. i've got this disabled in my kernel config now (<tt>CONFIG_AMD_MEM_ENCRYPT</tt>), so it's no longer recognized. i've removed it.</li>		<li><tt>mem_encrypt=off</tt> this refers to AMD's [https://en.wikichip.org/wiki/x86/sme Secure Memory Encryption] extension, allowing per-page transparent encryption. i've got this disabled in my kernel config now (<tt>CONFIG_AMD_MEM_ENCRYPT</tt>), so it's no longer recognized. i've removed it.</li>
	<li><tt>intel_iommu=on</tt> well duh i don't have an intel in this machine. i want <tt>iommu=pt iommu=1</tt></li>		<li><tt>intel_iommu=on</tt> well duh i don't have an intel in [[Schwarzgerat_III\|this machine]]. i want <tt>iommu=pt iommu=1</tt></li>
	</ul>		</ul>

Dank at 00:30, 13 March 2022

2022-03-13T00:30:09Z

← Older revision		Revision as of 00:30, 13 March 2022
Line 28:		Line 28:
	<tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 root=UUID=939be09a-b63d-403c-996a-8b9866313fbb ro mem_encrypt=off psi=0 acpi_enforce_resources=lax intel_iommu=on</tt>		<tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 root=UUID=939be09a-b63d-403c-996a-8b9866313fbb ro mem_encrypt=off psi=0 acpi_enforce_resources=lax intel_iommu=on</tt>

	<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here].		<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here]. <tt>acpi_enforce_resources=lex</tt> is sadly necessary to control my bling-ass LEDs using [https://openrgb.org/ OpenRGB].

	anyway, i wasn't aware of this dmesg output (added on [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line!		anyway, i wasn't aware of this dmesg output (added on [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line!

Dank at 00:28, 13 March 2022

2022-03-13T00:28:47Z

← Older revision		Revision as of 00:28, 13 March 2022
Line 19:		Line 19:

	<ul>		<ul>
	<li><tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2</tt> this is set by grub since ~~grub~~ 1.91, released 2005-10-15. i'm not sure why, or who consumes it. LILO set this parameter as well, and this might have just been a compatibility thing, so it might be lost in the river of time.</li>		<li><tt>BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2</tt> this is set by [https://www.gnu.org/software/grub/ GRUB] since 1.91, released 2005-10-15. i'm not sure why, or who consumes it. LILO set this parameter as well, and this might have just been a compatibility thing, so it might be lost in the river of time.</li>
	<li><tt>mem_encrypt=off</tt> this refers to AMD's [https://en.wikichip.org/wiki/x86/sme Secure Memory Encryption] extension, allowing per-page transparent encryption. i've got this disabled in my kernel config now (<tt>CONFIG_AMD_MEM_ENCRYPT</tt>), so it's no longer recognized. i've removed it.</li>		<li><tt>mem_encrypt=off</tt> this refers to AMD's [https://en.wikichip.org/wiki/x86/sme Secure Memory Encryption] extension, allowing per-page transparent encryption. i've got this disabled in my kernel config now (<tt>CONFIG_AMD_MEM_ENCRYPT</tt>), so it's no longer recognized. i've removed it.</li>
	<li><tt>intel_iommu=on</tt> well duh i don't have an intel in this machine. i want <tt>iommu=pt iommu=1</tt></li>		<li><tt>intel_iommu=on</tt> well duh i don't have an intel in this machine. i want <tt>iommu=pt iommu=1</tt></li>

Dank at 00:25, 13 March 2022

2022-03-13T00:25:59Z

← Older revision		Revision as of 00:25, 13 March 2022
Line 30:		Line 30:
	<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here].		<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here].

	anyway, i wasn't aware of this dmesg output (added in [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line!		anyway, i wasn't aware of this dmesg output (added on [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line!

	the only crappy element is the low visibility. ideally, a systemd oneshot unit would deliver a potent shock to the operator when this message was detected. constant vigilance!		the only crappy element is the low visibility. ideally, a systemd oneshot unit would deliver a potent shock to the operator when this message was detected. constant vigilance!

Dank at 00:21, 13 March 2022

2022-03-13T00:21:32Z

← Older revision		Revision as of 00:21, 13 March 2022
Line 1:		Line 1:
	'''[[Dankblog\|dankblog!]] 2022-03-12, 1842 ~~EDT~~, at [[Viewpoint\|the danktower]]'''		'''[[Dankblog\|dankblog!]] 2022-03-12, 1842 EST, at [[Viewpoint\|the danktower]]'''

	i was looking at my dmesg output today, wanting to know something about [[IOMMU]], and noticed the following line:		i was looking at my dmesg output today, wanting to know something about [[IOMMU]], and noticed the following line:

Dank at 00:18, 13 March 2022

2022-03-13T00:18:08Z

← Older revision		Revision as of 00:18, 13 March 2022
Line 34:		Line 34:
	the only crappy element is the low visibility. ideally, a systemd oneshot unit would deliver a potent shock to the operator when this message was detected. constant vigilance!		the only crappy element is the low visibility. ideally, a systemd oneshot unit would deliver a potent shock to the operator when this message was detected. constant vigilance!

	'''~~next~~: "[[On_the_Effectiveness_of_nonnull\|on the effectiveness of nonnull]]" 2021-11-05'''		'''previously: "[[On_the_Effectiveness_of_nonnull\|on the effectiveness of nonnull]]" 2021-11-05'''

	[[Category:Blog]]		[[Category:Blog]]

Dank at 00:15, 13 March 2022

2022-03-13T00:15:54Z

← Older revision		Revision as of 00:15, 13 March 2022
Line 29:		Line 29:

	<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here].		<tt>psi=0</tt> refers to the Pressure Stall Information feedback system introduced in 2018 by Facebook hackers, which you can read about [https://www.kernel.org/doc/html/latest/accounting/psi.html here] or [https://lwn.net/Articles/764761/ here].

			anyway, i wasn't aware of this dmesg output (added in [https://lore.kernel.org/lkml/20210511211009.42259-1-ahalaney@redhat.com/ 2021-05]), but it seems a useful bit of diagnostics. unfuck your kernel command line!

			the only crappy element is the low visibility. ideally, a systemd oneshot unit would deliver a potent shock to the operator when this message was detected. constant vigilance!

	'''next: "[[On_the_Effectiveness_of_nonnull\|on the effectiveness of nonnull]]" 2021-11-05'''		'''next: "[[On_the_Effectiveness_of_nonnull\|on the effectiveness of nonnull]]" 2021-11-05'''

	[[Category:Blog]]		[[Category:Blog]]

Dank at 00:12, 13 March 2022

2022-03-13T00:12:58Z

@@ Line 15: / Line 15: @@
 <li>hyphens and underscores are equivalent</li>
 </ul>
 '''next: "[[On_the_Effectiveness_of_nonnull|on the effectiveness of nonnull]]" 2021-11-05'''
 [[Category:Blog]]

Dank: Created page with "'''dankblog! 2022-03-12, 1842 EDT, at the danktower''' i was looking at my dmesg output today, wanting to know something about IOMMU, and noticed the following line: `[ 0.015134] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 mem_encrypt=off intel_iommu=on", will be passed to user space` first off, some basic [https://man7.org/linux/man-pages/man7/kernel-command-line.7.html kernel command line] fa..."

2022-03-12T23:53:45Z

Created page with "'''dankblog! 2022-03-12, 1842 EDT, at the danktower''' i was looking at my dmesg output today, wanting to know something about IOMMU, and noticed the following line: <tt>[ 0.015134] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 mem_encrypt=off intel_iommu=on", will be passed to user space </tt> first off, some basic [https://man7.org/linux/man-pages/man7/kernel-command-line.7.html kernel command line] fa..."

New page

'''[[Dankblog|dankblog!]] 2022-03-12, 1842 EDT, at [[Viewpoint|the danktower]]'''

i was looking at my dmesg output today, wanting to know something about [[IOMMU]], and noticed the following line:

<tt>[ 0.015134] Unknown kernel command line parameters "BOOT_IMAGE=/boot/vmlinuz-5.16.13nlb2 mem_encrypt=off intel_iommu=on", will be passed to user space
</tt>

first off, some basic [https://man7.org/linux/man-pages/man7/kernel-command-line.7.html kernel command line] facts:
<ul>
<li>there's a man page, of course: <tt>kernel-command-line(7)</tt>. many options are explained in <tt>[https://man7.org/linux/man-pages/man7/bootparam.7.html bootparam(7)]</tt></li>
<li>an option is prefixed with <tt>modname.</tt> if it's intended for a module (whether that code has been built as a module, or built into the kernel)</li>
<li>options can be specified in <tt>modprobe.d(5)</tt>, but this only works if the code was actually built as a module</li>
<li>any unrecognized parameter, and any parameter following "--", is passed to <tt>init</tt></li>
<li>parameters containing a "=" go into <tt>init</tt>'s environment</li>
<li>hyphens and underscores are equivalent</li>
</ul>

'''next: "[[On_the_Effectiveness_of_nonnull|on the effectiveness of nonnull]]" 2021-11-05'''

[[Category:Blog]]