pmd_set_huge: Cannot satisfy [mem 0xf0000000-0xf0200000] with a huge-page mapping due to MTRR override

Bug #1622502 reported by dino99
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This is logged with the 4.8 kernels
4.8.0.7-13 actualy used, from the unstable ppa
Its an upstream problem, as such error is found all over the distros.

Can not say if its due to incompatible hardware, buggy bios or lintian/systemd/acpi/... reason(s) nor if a booting setting is required

note: this does not semms affecting the system (in my case at least).

The hardware is quite old, and the bios is no more upgradable.

Relative links:
https://lwn.net/Articles/635357/
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.2.y&id=b73522e0c1be58d3c69b124985b8ccf94e3677f7

" Drivers should make a mapping request aligned to a single MTRR entry
when the range is covered by MTRRs. "

 cat /proc/mtrr
reg00: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
reg01: base=0x000000000 ( 0MB), size= 4096MB, count=1: write-back
reg02: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back

sudo dmesg | grep -5 -i mtrr
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x140000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0C0000000 mask FC0000000 uncachable
[ 0.000000] 1 base 000000000 mask F00000000 write-back
[ 0.000000] 2 base 100000000 mask FC0000000 write-back
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
--
[ 0.249861] ACPI: Interpreter enabled
[ 0.249882] ACPI: (supports S0 S1 S3 S4 S5)
[ 0.249886] ACPI: Using IOAPIC for interrupt routing
[ 0.249918] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[ 0.250976] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in ACPI motherboard resources
[ 0.250986] pmd_set_huge: Cannot satisfy [mem 0xf0000000-0xf0200000] with a huge-page mapping due to MTRR override.
[ 0.251065] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.255750] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.255758] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.255767] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.255778] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
---
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: oem 1821 F.... pulseaudio
 /dev/snd/pcmC0D0p: oem 1821 F...m pulseaudio
 /dev/snd/controlC0: oem 1821 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.

 eth1 no wireless extensions.
Lsusb:
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 simple
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-7-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
ProcVersionSignature: Ubuntu 4.8.0-7.8-generic 4.8.0-rc5
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-7-generic N/A
 linux-backports-modules-4.8.0-7-generic N/A
 linux-firmware 1.160
RfKill:

Tags: yakkety
Uname: Linux 4.8.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5W DH Deluxe
dmi.product.version: System Version
dmi.sys.vendor: ASUSTEK COMPUTER INC

dino99 (9d9)
description: updated
tags: added: bot-stop-nagging
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1622502

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
dino99 (9d9) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected yakkety
description: updated
Revision history for this message
dino99 (9d9) wrote : CRDA.txt

apport information

Revision history for this message
dino99 (9d9) wrote : CurrentDmesg.txt

apport information

Revision history for this message
dino99 (9d9) wrote : JournalErrors.txt

apport information

Revision history for this message
dino99 (9d9) wrote : Lspci.txt

apport information

Revision history for this message
dino99 (9d9) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
dino99 (9d9) wrote : ProcEnviron.txt

apport information

Revision history for this message
dino99 (9d9) wrote : ProcInterrupts.txt

apport information

Revision history for this message
dino99 (9d9) wrote : ProcModules.txt

apport information

Revision history for this message
dino99 (9d9) wrote : PulseList.txt

apport information

Revision history for this message
dino99 (9d9) wrote : UdevDb.txt

apport information

Revision history for this message
dino99 (9d9) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
dino99 (9d9)
description: updated
dino99 (9d9)
description: updated
dino99 (9d9)
description: updated
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
dino99 (9d9) wrote :

Still not fixed with rc7.
From the 4.8.014 kernel:

oem@u64:~$ journalctl | grep pmd_set_huge
Sep 22 06:00:39 u64 kernel: pmd_set_huge: Cannot satisfy [mem 0xf0000000-0xf0200000] with a huge-page mapping due to MTRR override.

Revision history for this message
dino99 (9d9) wrote :

This is now not logged with the 4.8.0-17 kernel. Waiting a couple days before closing that report.

dino99 (9d9)
Changed in linux (Ubuntu):
status: Triaged → Invalid
Revision history for this message
mirh (mirh) wrote :

So, TL;DR you switched from 4.8.0.7-13 (unstable, right?) to 4.8.0-17 generic and profit?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.