Enabling the kernel boot parameter 'hpet_mmap' does not take effect.

Solution Verified - Updated -

Issue

  • The kernel parameter hpet_mmap is used to enabled/disable (default) HPET MMAP. However, booting the kernel with this parameter does not take effect and always takes the default value (0) of hpet_mmap_enabled.

  • dmesg output after booting the kernel with the kernel parameter hpet_mmap=1

# cat /proc/cmdline 
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-4.18.0-32.el8.x86_64 root=/dev/mapper/rhel-root ro crashkernel=auto resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap hpet_mmap=1

# dmesg | grep 'HPET mmap'
[    0.000000] HPET mmap disabled
  • dmesg output after booting the kernel with the kernel parameter hpet_mmap=0
# cat /proc/cmdline 
BOOT_IMAGE=(hd0,msdos1)/vmlinuz-4.18.0-32.el8.x86_64 root=/dev/mapper/rhel-root ro crashkernel=auto resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap hpet_mmap=0

# dmesg | grep 'HPET mmap'
[    0.000000] HPET mmap disabled

Environment

  • Red Hat Enterprise Linux 8
  • kernel
  • hpet_mmap

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content