Bug#1041141: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.

[AlMa]

Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1

In the journal we find the following warning (“pmd_set_huge … override.”
line is yellow, everything else is white):

…
Jul 15 03:35:14 AnonymizedMachneName kernel: ACPI FADT declares the
system doesn't support PCIe ASPM, so disable it
Jul 15 03:35:14 AnonymizedMachneName kernel: acpiphp: ACPI Hot Plug PCI
Controller Driver version: 0.5
Jul 15 03:35:14 AnonymizedMachneName kernel: PCI: MMCONFIG for domain
0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Jul 15 03:35:14 AnonymizedMachneName kernel: PCI: MMCONFIG at [mem
0xf8000000-0xfbffffff] reserved in E820
Jul 15 03:35:14 AnonymizedMachneName kernel: pmd_set_huge: Cannot
satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR
override.
Jul 15 03:35:14 AnonymizedMachneName kernel: PCI: Using configuration
type 1 for base access
…


The machine is a Dell Mobile Precision M6700 with the processor Intel
Core i7-3720QM, 32 GB RAM, and AMD FirePro M6000 Mobility Pro graphic
chip with 2GB GDDR5. The BIOS is at its last available version A20. As
the machine experiences high-level issues later at boot (e.g., some
services can't start), we wish to be sure about the contribution of the
issue warned about here. Can the issue underlying this warning be
easily "fixed" or are we already running a "safe" setting? I took a
look into
https://www.kernel.org/doc/html/v4.10/admin-guide/kernel-parameters.html
, but it seems to me that changing anything _safely_ would require me
going into the depths of the memory layout of x86/amd64; nothing that I
would test myself without proper advice.

Gratefully,
AlMa

[Debian Bug Tracking System]

Processing commands for con...@bugs.debian.org:

> found 1041141 6.1.38-1
Bug #1041141 [linux-image-6.1.0-10-amd64] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
Marked as found in versions linux-signed-amd64/6.1.38+1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
--
1041141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

[Al Ma]

found 1041141 6.1.38-1

thanks

After the kernel upgrade, I got a slightly different message in the same vein:

Jul 22 22:35:22 AnonymizedMachineName kernel: Registering PCC driver as Mailbox controller

Jul 22 22:35:22 AnonymizedMachineName kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5

Jul 22 22:35:22 AnonymizedMachineName kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x60000000-0x6fffffff] (base 0x60000000)

Jul 22 22:35:22 AnonymizedMachineName kernel: PCI: MMCONFIG at [mem 0x60000000-0x6fffffff] reserved in E820

Jul 22 22:35:22 AnonymizedMachineName kernel: pmd_set_huge: Cannot satisfy [mem 0x60000000-0x60200000] with a huge-page mapping due to MTRR override.

Gratefully,

AlMa

[Al Ma]

I stand corrected – the very last message as of a few minutes ago concerned a different machine: WS C422 PRO/SE with Intel® Xeon® W-2235 CPU @ 3.80GHz, 32 GB RAM, ASPEED AST2500 64MB built-in graphics chip, and NVIDIA GeForce GTX 1660 Ti PCIe graphics card.

[Diederik de Haas]

I already had the tabs open which a simple search brought up, so I'll share
that. There are no guarantees in life, so I suggest to just try things out.
Which is rather common/normal in troubleshooting issues.
No guarantees, but there's little chance the device blows up or catches fire...

https://bugzilla.kernel.org/show_bug.cgi?id=118801 which links to
https://web.archive.org/web/20190904223631/http://my-fuzzy-logic.de/blog/
index.php?/archives/41-Solving-linux-MTRR-problems.html

and my own educated guess: Disable the ASPEED device and see what happens ...

[AlMa]

> https://bugzilla.kernel.org/show_bug.cgi?id=118801 which links to
> https://web.archive.org/web/20190904223631/http://my-fuzzy-logic.de/blog/
> index.php?/archives/41-Solving-linux-MTRR-problems.html
>

Thank you, I will look into it!

> and my own educated guess: Disable the ASPEED device and see what happens ...

Any hint on how to do it on the linux command line in grub?

[Diederik de Haas]

On Tuesday, 1 August 2023 02:53:19 CEST AlMa wrote:
> > and my own educated guess: Disable the ASPEED device and see what happens

> Any hint on how to do it on the linux command line in grub?

Please read http://www.catb.org/esr/faqs/smart-questions.html

The "Before You Ask" section lists (among others) the following:
2. Try to find an answer by searching the Web.
3. Try to find an answer by reading the manual.

You said you're managing several hardware devices, so I would also expect (and
the device manual will undoubtedly tell you) that the most logical place to
disable build-in hardware would be the BIOS ...

After the 7 item list, that document says the following:
"When you ask your question, display the fact that you have done these things
first; this will help establish that you're not being a lazy sponge and wasting
people's time."

So please read and apply the document I linked above.
I won't be wasting my time on your issues though.

[AlMa]

On 01.08.23 10:50, Diederik de Haas wrote:
> On Tuesday, 1 August 2023 02:53:19 CEST AlMa wrote:
>>> and my own educated guess: Disable the ASPEED device and see what happens
>> Any hint on how to do it on the linux command line in grub?
>
> Please read http://www.catb.org/esr/faqs/smart-questions.html
>
> The "Before You Ask" section lists (among others) the following:
> 2. Try to find an answer by searching the Web.
> 3. Try to find an answer by reading the manual.
>
> You said you're managing several hardware devices, so I would also expect (and
> the device manual will undoubtedly tell you) that the most logical place to
> disable build-in hardware would be the BIOS ...

Probably a bad idea. This would prevent seeing anything right from the
beginning in case the monitor connected to the NVIDIA graphic cards
stops showing stuff for whatever reason.

> After the 7 item list, that document says the following:
> "When you ask your question, display the fact that you have done these things
> first; this will help establish that you're not being a lazy sponge and wasting
> people's time."
>
> So please read and apply the document I linked above.
> I won't be wasting my time on your issues though.

Don't upbraid me for no good reason; better rail at the bugs themselves.
I don't see folks really retypesetting all the Web search queries they
run. If I would have exposed some of the research I did, I would have
run the risk of introducing typos while retypesetting; nobody is immune
against errors of all kinds. Anyway, I don't expose folks to potentially
useless material. Having said that, I kindly ask for understanding
that, responding to your ranting and raving, I won't be wasting my time
on replying to psychological issues you apparently have.