Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

kernel: pmd_set_huge: Cannot satisfy [mem 0xbc000000-0xbc200000] with a huge-page mapping due to MTRR override.

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
postcd
Posts: 133
Joined: 2022-01-08 18:33
Has thanked: 48 times
Been thanked: 2 times

kernel: pmd_set_huge: Cannot satisfy [mem 0xbc000000-0xbc200000] with a huge-page mapping due to MTRR override.

#1 Post by postcd »

kernel: [drm] Detected VRAM RAM=512M, BAR=512M
kernel: [drm] RAM width 128bits DDR4
kernel: [TTM] Zone kernel: Available graphics memory: 32604796 KiB
kernel: [TTM] Zone dma32: Available graphics memory: 2097152 KiB
kernel: [TTM] Initializing pool allocator
kernel: [TTM] Initializing DMA pool allocator
kernel: pmd_set_huge: Cannot satisfy [mem 0xbc000000-0xbc200000] with a huge-page mapping due to MTRR override.
kernel: [drm] amdgpu: 512M of VRAM memory ready
kernel: [drm] amdgpu: 3072M of GTT memory ready.
inxi system, gpu, ram details output is here
$ sudo cat /proc/mtrr
reg00: base=0x0ff000000 ( 4080MB), size= 16MB, count=1: write-protect
reg01: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg02: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back
reg03: base=0x0bc000000 ( 3008MB), size= 64MB, count=1: uncachable

$ sudo journalctl|grep "mtrr"
Sep 16 11:02:48 kernel: MTRR default type: uncachable
Sep 16 11:02:48 kernel: MTRR fixed ranges enabled:
Sep 16 11:02:48 kernel: MTRR variable ranges enabled:
Sep 16 11:02:48 kernel: pmd_set_huge: Cannot satisfy [mem 0xbc000000-0xbc200000] with a huge-page mapping due to MTRR override.

$ sudo grep -Ria mtrr /boot
/boot/config-5.15.0-0.bpo.3-amd64:CONFIG_MTRR=y
/boot/config-5.15.0-0.bpo.3-amd64:CONFIG_MTRR_SANITIZER=y
/boot/config-5.15.0-0.bpo.3-amd64:CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
/boot/config-5.15.0-0.bpo.3-amd64:CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
/boot/config-5.10.0-18-amd64:CONFIG_MTRR=y
/boot/config-5.10.0-18-amd64:CONFIG_MTRR_SANITIZER=y
/boot/config-5.10.0-18-amd64:CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0
/boot/config-5.10.0-18-amd64:CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
Debian 11+KDE

Should/how the huge-page mapping be satisfied?

Here someone says: "User may specify a new kernel option "nohugeiomap" to disable the huge I/O mapping capability of ioremap() when necessary."

Someone else with same issue here, said following solves the "issue":
echo 'nohugeiomap' | sudo tee /etc/kernel/cmdline
Other user at bugzilla.kernel.org says to use: "enable_mtrr_cleanup=1" (possibly also kernel boot line parameter same like with above mentioned hugeiomap?), but someone else says that this parameter may not be helpful, because "However in this case, MTRR are set by the BIOS, they cannot be changed by the OS (even with kernel param enable_mtrr_cleanup)"

Similar question, rather not answered: https://unix.stackexchange.com/question ... g-messages

What to try please?

postcd
Posts: 133
Joined: 2022-01-08 18:33
Has thanked: 48 times
Been thanked: 2 times

Re: kernel: pmd_set_huge: Cannot satisfy [mem 0xbc000000-0xbc200000] with a huge-page mapping due to MTRR override.

#2 Post by postcd »

Reappear on next boots again.

Post Reply