Bug 31592 - Cannot free mtrr on Acer Aspire One since 2.6.31
Summary: Cannot free mtrr on Acer Aspire One since 2.6.31
Status: RESOLVED OBSOLETE
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: i386 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_i386
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-21 19:35 UTC by Justin
Modified: 2013-12-23 11:46 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.38
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
kernel config (15.16 KB, application/x-gzip)
2011-03-21 19:35 UTC, Justin
Details

Description Justin 2011-03-21 19:35:00 UTC
I don't know what is going wrong. 2.6.30 was fine but upwards till .38 mtrr doesn't get cleaned.
Downstream bug is https://bugs.gentoo.org/show_bug.cgi?id=352344

$ cat /proc/mtrr 
reg00: base=0x0fffe0000 ( 4095MB), size=  128KB, count=1: write-protect
reg01: base=0x0fffc0000 ( 4095MB), size=  128KB, count=1: uncachable
reg02: base=0x000000000 (    0MB), size=  512MB, count=1: write-back
reg03: base=0x020000000 (  512MB), size=  512MB, count=1: write-back
reg04: base=0x03f800000 ( 1016MB), size=    8MB, count=1: uncachable
reg05: base=0x03f600000 ( 1014MB), size=    2MB, count=1: uncachable
reg06: base=0x03f500000 ( 1013MB), size=    1MB, count=1: uncachable
reg07: base=0x000000000 (    0MB), size=  128KB, count=1: uncachable

I have 2 * 512 Mb RAM in it.

$ zgrep MTRR /proc/config.gz 
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=2

PAT is also enabled.

I already tested all reg numbers.

$ cat /proc/cmdline 
root=/dev/sda3  enable_mtrr_cleanup mtrr_spare_reg_nr=1

Also in this way.
Comment 1 Justin 2011-03-21 19:35:35 UTC
Created attachment 51562 [details]
kernel config
Comment 2 Andrew Morton 2011-03-21 19:42:58 UTC
Thanks, I'll mark this as a regression and will reassign it to i386.

That config file was double-gzipped, btw.  Sneaky!
Comment 3 Justin 2011-03-21 19:53:03 UTC
(In reply to comment #2)
> That config file was double-gzipped, btw.  Sneaky!

Booo, that's not nice. Sorry.

Note You need to log in before you can comment on or make changes to this bug.