From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "J.A. Magallón" <jamagallon@ono.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Out of mtrrs
Date: Fri, 29 Aug 2008 10:37:09 -0700 [thread overview]
Message-ID: <86802c440808291037v688b72e0kda1a606e246223a9@mail.gmail.com> (raw)
In-Reply-To: <8EF35F63-8FF6-483F-9DED-D573C40430C8@ono.com>
On Fri, Aug 29, 2008 at 9:17 AM, "J.A. Magallón" <jamagallon@ono.com> wrote:
>
> On 2008.08.29, at 18:01, Arjan van de Ven wrote:
>
>> On Fri, 29 Aug 2008 17:32:49 +0200
>> ""J.A. Magallón"" <jamagallon@ono.com> wrote:
>>
>>> Hi all...
>>>
>>> I'm using the xorg intel driver, and drm/X report it has no free mtrrs
>>> in kernel to set up:
>>>
>>> one:~# cat /proc/mtrr
>>> reg00: base=0xfffe0000 (4095MB), size= 128KB: write-protect, count=1
>>> reg01: base=0xfffc0000 (4095MB), size= 128KB: uncachable, count=1
>>> reg02: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
>>> reg03: base=0x10000000 ( 256MB), size= 256MB: write-back, count=1
>>> reg04: base=0x1f800000 ( 504MB), size= 8MB: uncachable, count=1
>>> reg05: base=0x1f600000 ( 502MB), size= 2MB: uncachable, count=1
>>> reg06: base=0x1f500000 ( 501MB), size= 1MB: uncachable, count=1
>>> reg07: base=0x00000000 ( 0MB), size= 128KB: uncachable, count=1
>>>
>
> with disable_mtrr_trim, I get te same:
>
> reg00: base=0xfffe0000 (4095MB), size= 128KB: write-protect, count=1
> reg01: base=0xfffc0000 (4095MB), size= 128KB: uncachable, count=1
> reg02: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
> reg03: base=0x10000000 ( 256MB), size= 256MB: write-back, count=1
> reg04: base=0x1f800000 ( 504MB), size= 8MB: uncachable, count=1
> reg05: base=0x1f600000 ( 502MB), size= 2MB: uncachable, count=1
> reg06: base=0x1f500000 ( 501MB), size= 1MB: uncachable, count=1
> reg07: base=0x00000000 ( 0MB), size= 128KB: uncachable, count=1
>
the mtrr looks crazy from setting by BIOS...
32bit or 64bit?
please set
CONFIG_MTRR=y
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
and boot with "debug" in boot command line...
and send out
dmesg -s 262144 > dmesg.txt
YH
next prev parent reply other threads:[~2008-08-29 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 15:32 "J.A. Magallón"
[not found] ` <20080829090139.30c69ead@infradead.org>
2008-08-29 16:17 ` "J.A. Magallón"
2008-08-29 17:37 ` Yinghai Lu [this message]
2008-08-29 22:55 ` Pallipadi, Venkatesh
2008-08-30 3:16 ` Bill Davidsen
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=86802c440808291037v688b72e0kda1a606e246223a9@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=jamagallon@ono.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®