From: Mikael Pettersson <mikpelinux@gmail.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Mikael Pettersson <mikpelinux@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG?] mtrr sanitizer fails on Latitude E6230
Date: Thu, 7 Nov 2013 09:25:58 +0100 [thread overview]
Message-ID: <21115.20118.72541.74924@gargle.gargle.HOWL> (raw)
In-Reply-To: <CAE9FiQX3mGLmzFCyaHYPBA2QgvxBYr9zarXcUKa5DC0ZtiiWZw@mail.gmail.com>
Yinghai Lu writes:
> On Wed, Nov 6, 2013 at 1:16 AM, Mikael Pettersson <mikpelinux@gmail.com> wrote:
> > I recently got a Dell Latitude E6230 (Ivy Bridge i7-3540M) and noticed that
> > the mtrr sanitizer failed on it:
> >
> > === snip ===
> > Linux version 3.12.0 (mikpe@barley) (gcc version 4.8.3 20131017 (prerelease) (GCC) ) #1 SMP Wed Nov 6 09:46:02 CET 2013
> > Command line: ro root=LABEL=/ resume=/dev/sda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=sv-latin1
> ...
> gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M
> ...
> > mtrr_cleanup: can not find optimal value
> > please specify mtrr_gran_size/mtrr_chunk_size
> > === snip ===
> >
> > For now I'm disabling the mtrr sanitizer in this machine's kernel.
>
> Can you try to boot with "mtrr_gran_size=8m mtrr_chunk_size=64m" ?
That results in:
Linux version 3.12.0-test (mikpe@barley) (gcc version 4.8.3 20131017 (prerelease) (GCC) ) #1 SMP Thu Nov 7 09:12:14 CET 2013
Command line: mtrr_gran_size=8m mtrr_chunk_size=64m ro root=LABEL=/ resume=/dev/sda2 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=sv-latin1
KERNEL supported cpus:
Intel GenuineIntel
e820: BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
BIOS-e820: [mem 0x0000000020200000-0x0000000040003fff] usable
BIOS-e820: [mem 0x0000000040004000-0x0000000040004fff] reserved
BIOS-e820: [mem 0x0000000040005000-0x00000000d5f09fff] usable
BIOS-e820: [mem 0x00000000d5f0a000-0x00000000d5ffffff] reserved
BIOS-e820: [mem 0x00000000d6000000-0x00000000d6751fff] usable
BIOS-e820: [mem 0x00000000d6752000-0x00000000d67fffff] reserved
BIOS-e820: [mem 0x00000000d6800000-0x00000000d6fb2fff] usable
BIOS-e820: [mem 0x00000000d6fb3000-0x00000000d6ffffff] ACPI data
BIOS-e820: [mem 0x00000000d7000000-0x00000000d86fbfff] usable
BIOS-e820: [mem 0x00000000d86fc000-0x00000000d87fffff] ACPI NVS
BIOS-e820: [mem 0x00000000d8800000-0x00000000d96d4fff] usable
BIOS-e820: [mem 0x00000000d96d5000-0x00000000da054fff] reserved
BIOS-e820: [mem 0x00000000da055000-0x00000000da097fff] ACPI NVS
BIOS-e820: [mem 0x00000000da098000-0x00000000daadcfff] usable
BIOS-e820: [mem 0x00000000daadd000-0x00000000dafeffff] reserved
BIOS-e820: [mem 0x00000000daff0000-0x00000000daffffff] usable
BIOS-e820: [mem 0x00000000db800000-0x00000000df9fffff] reserved
BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x000000021e5fffff] usable
NX (Execute Disable) protection: active
SMBIOS 2.7 present.
DMI: Dell Inc. Latitude E6230/0Y47PX, BIOS A11 08/27/2013
e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
e820: remove [mem 0x000a0000-0x000fffff] usable
e820: last_pfn = 0x21e600 max_arch_pfn = 0x400000000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CFFFF write-protect
D0000-E7FFF uncachable
E8000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask E00000000 write-back
1 base 200000000 mask FE0000000 write-back
2 base 0E0000000 mask FE0000000 uncachable
3 base 0DC000000 mask FFC000000 uncachable
4 base 0DB800000 mask FFF800000 uncachable
5 base 21F000000 mask FFF000000 uncachable
6 base 21E800000 mask FFF800000 uncachable
7 base 21E600000 mask FFFE00000 uncachable
8 disabled
9 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
original variable MTRRs
reg 0, base: 0GB, range: 8GB, type WB
reg 1, base: 8GB, range: 512MB, type WB
reg 2, base: 3584MB, range: 512MB, type UC
reg 3, base: 3520MB, range: 64MB, type UC
reg 4, base: 3512MB, range: 8MB, type UC
reg 5, base: 8688MB, range: 16MB, type UC
reg 6, base: 8680MB, range: 8MB, type UC
reg 7, base: 8678MB, range: 2MB, type UC
total RAM covered: 8094M
gran_size: 8M chunk_size: 64M num_reg: 9 lose cover RAM: 6M
New variable MTRRs
reg 0, base: 0GB, range: 2GB, type WB
reg 1, base: 2GB, range: 1GB, type WB
reg 2, base: 3GB, range: 256MB, type WB
reg 3, base: 3328MB, range: 128MB, type WB
reg 4, base: 3456MB, range: 64MB, type WB
reg 5, base: 3512MB, range: 8MB, type UC
reg 6, base: 4GB, range: 4GB, type WB
reg 7, base: 8GB, range: 512MB, type WB
reg 8, base: 8672MB, range: 32MB, type UC
e820: update [mem 0xdb800000-0xffffffff] usable ==> reserved
e820: update [mem 0x21e000000-0x21e5fffff] usable ==> reserved
WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 6MB of RAM.
update e820 for mtrr
e820: modified physical RAM map:
modified: [mem 0x0000000000000000-0x0000000000000fff] reserved
modified: [mem 0x0000000000001000-0x000000000009d3ff] usable
modified: [mem 0x000000000009d400-0x000000000009ffff] reserved
modified: [mem 0x00000000000e0000-0x00000000000fffff] reserved
modified: [mem 0x0000000000100000-0x000000001fffffff] usable
modified: [mem 0x0000000020000000-0x00000000201fffff] reserved
modified: [mem 0x0000000020200000-0x0000000040003fff] usable
modified: [mem 0x0000000040004000-0x0000000040004fff] reserved
modified: [mem 0x0000000040005000-0x00000000d5f09fff] usable
modified: [mem 0x00000000d5f0a000-0x00000000d5ffffff] reserved
modified: [mem 0x00000000d6000000-0x00000000d6751fff] usable
modified: [mem 0x00000000d6752000-0x00000000d67fffff] reserved
modified: [mem 0x00000000d6800000-0x00000000d6fb2fff] usable
modified: [mem 0x00000000d6fb3000-0x00000000d6ffffff] ACPI data
modified: [mem 0x00000000d7000000-0x00000000d86fbfff] usable
modified: [mem 0x00000000d86fc000-0x00000000d87fffff] ACPI NVS
modified: [mem 0x00000000d8800000-0x00000000d96d4fff] usable
modified: [mem 0x00000000d96d5000-0x00000000da054fff] reserved
modified: [mem 0x00000000da055000-0x00000000da097fff] ACPI NVS
modified: [mem 0x00000000da098000-0x00000000daadcfff] usable
modified: [mem 0x00000000daadd000-0x00000000dafeffff] reserved
modified: [mem 0x00000000daff0000-0x00000000daffffff] usable
modified: [mem 0x00000000db800000-0x00000000df9fffff] reserved
modified: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
modified: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
modified: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
modified: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
modified: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
modified: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
modified: [mem 0x0000000100000000-0x000000021dffffff] usable
modified: [mem 0x000000021e000000-0x000000021e5fffff] reserved
/Mikael
next prev parent reply other threads:[~2013-11-07 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 9:16 [BUG?] mtrr sanitizer fails on Latitude E6230 Mikael Pettersson
2013-11-06 20:08 ` Yinghai Lu
2013-11-07 8:25 ` Mikael Pettersson [this message]
2013-11-07 20:12 ` Yinghai Lu
2013-11-08 8:19 ` Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21115.20118.72541.74924@gargle.gargle.HOWL \
--to=mikpelinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).