From: Alexander Lam <lambchop468@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: mtrr cleanup not doing anything on 2.6.33-rc7
Date: Wed, 10 Feb 2010 15:02:30 -0500 [thread overview]
Message-ID: <dfb03c971002101202i37f4a243jc6bfb44bc853cb5d@mail.gmail.com> (raw)
Hi all,
Please CC: me when replying.
My kernel config has the following:
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
With previous kernels, dmesg would show that the sanitizer was indeed
cleaning up the mtrrs [1]
but now, with 2.6.33-rc7 there is no indication that this is occuring,
and the intel i915 driver complains:
[ 0.613419] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.614577] i915 0000:00:02.0: setting latency timer to 64
[ 0.625446] mtrr: no more MTRRs available
[ 0.625529] [drm] MTRR allocation failed. Graphics performance
may suffer.
What has changed and what do I need to do to make the mtrr sanitation
work again?
[1]: dmesg from previous kernels:
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C7FFF write-protect
[ 0.000000] C8000-EFFFF uncachable
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0FFFE0000 mask 0FFFE0000 write-protect
[ 0.000000] 1 base 0FFFC0000 mask 0FFFE0000 uncachable
[ 0.000000] 2 base 000000000 mask 0E0000000 write-back
[ 0.000000] 3 base 020000000 mask 0E0000000 write-back
[ 0.000000] 4 base 03F800000 mask 0FF800000 uncachable
[ 0.000000] 5 base 03F600000 mask 0FFE00000 uncachable
[ 0.000000] 6 base 03F500000 mask 0FFF00000 uncachable
[ 0.000000] 7 base 000000000 mask 0FFFE0000 uncachable
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] original variable MTRRs
[ 0.000000] reg 0, base: 4194176KB, range: 128KB, type WP
[ 0.000000] reg 1, base: 4194048KB, range: 128KB, type UC
[ 0.000000] reg 2, base: 0GB, range: 512MB, type WB
[ 0.000000] reg 3, base: 512MB, range: 512MB, type WB
[ 0.000000] reg 4, base: 1016MB, range: 8MB, type UC
[ 0.000000] reg 5, base: 1014MB, range: 2MB, type UC
[ 0.000000] reg 6, base: 1013MB, range: 1MB, type UC
[ 0.000000] reg 7, base: 0GB, range: 128KB, type UC
[ 0.000000] WARNING: BIOS bug: VAR MTRR 7 contains strange UC entry
under 1M, check with your system vendor!
[ 0.000000] total RAM coverred: 1013M
[ 0.000000] Found optimal setting for mtrr clean up
[ 0.000000] gran_size: 64K chunk_size: 16M num_reg: 4
lose cover RAM: 0G
[ 0.000000] New variable MTRRs
[ 0.000000] reg 0, base: 0GB, range: 1GB, type WB
[ 0.000000] reg 1, base: 1013MB, range: 1MB, type UC
[ 0.000000] reg 2, base: 1014MB, range: 2MB, type UC
[ 0.000000] reg 3, base: 1016MB, range: 8MB, type UC
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Thanks,
--
Alexander Lam
next reply other threads:[~2010-02-10 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 20:02 Alexander Lam [this message]
2010-02-11 1:48 ` Alexander Lam
2010-02-11 10:10 ` Carlos R. Mafra
2010-02-11 14:56 ` H. Peter Anvin
2010-02-11 17:15 ` Carlos R. Mafra
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=dfb03c971002101202i37f4a243jc6bfb44bc853cb5d@mail.gmail.com \
--to=lambchop468@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®