Your message dated Thu, 20 Feb 2025 15:28:34 +0100 (CET)
with message-id <20250220142834.555e1be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1041141,
regarding pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a
huge-page mapping due to MTRR override.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1041141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
