From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Joshua Hoblitt" <josh@hoblitt.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
j_kernel@hoblitt.com
Subject: Re: [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable
Date: Thu, 21 Aug 2008 18:55:58 -0700 [thread overview]
Message-ID: <86802c440808211855h50ea65faudc169e48f83e18e2@mail.gmail.com> (raw)
In-Reply-To: <20080822011055.GI23377@hoblitt.com>
On Thu, Aug 21, 2008 at 6:10 PM, Joshua Hoblitt <josh@hoblitt.com> wrote:
> Ugh - I just realized I forgot to type "-dirty" into grub after
> rebuilding the kernel. Here is the new dmesg with the msr trace.
>
> -J
>
> --
> On Thu, Aug 21, 2008 at 03:00:14PM -1000, Joshua Hoblitt wrote:
>> I have applied your patch to the tip tree and rebuilt. Still no msr
>> dump.
>>
>> -J
>>
>> --
>> On Thu, Aug 21, 2008 at 02:29:52PM -1000, Joshua Hoblitt wrote:
>> > Lol. No - I thought you implied it was in the tip tree. Sigh. I'll
>> > try again.
>> >
[ 0.429971] MSR00000200: 00000000d0000000
[ 0.433305] MSR00000201: 0000000ff0000800
==> base: 0xd0000000 size: 0x10000000 UC
[ 0.436638] MSR00000202: 00000000e0000000
[ 0.439971] MSR00000203: 0000000fe0000800
==> base: 0xe000000 size: 0x2000000 UC
[ 0.443304] MSR00000204: 0000000000000006
[ 0.446637] MSR00000205: 0000000c00000800
==> base: 0 size 16G WB
[ 0.449970] MSR00000206: 0000000400000006
[ 0.453303] MSR00000207: 0000000fe0000800
==> base: 16G, size: 128M WB
[ 0.456636] MSR00000208: 0000000420000006
[ 0.459970] MSR00000209: 0000000ff0000800
==> base: 16g+128M, size 64M WB
[ 0.463303] MSR0000020a: 0000000000000000
[ 0.466636] MSR0000020b: 0000000000000000
[ 0.469969] MSR0000020c: 0000000000000000
[ 0.473302] MSR0000020d: 0000000000000000
it seems right.
can you send out /proc/cpuinfo
YH
next prev parent reply other threads:[~2008-08-22 1:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11388-27@http.bugzilla.kernel.org/>
2008-08-21 1:04 ` Andrew Morton
2008-08-21 1:20 ` Yinghai Lu
2008-08-21 1:49 ` Yinghai Lu
2008-08-21 11:44 ` Ingo Molnar
2008-08-21 11:56 ` Ingo Molnar
2008-08-21 15:39 ` Yinghai Lu
2008-08-22 3:51 ` Ingo Molnar
2008-08-22 4:45 ` Yinghai Lu
2008-08-21 20:55 ` Joshua Hoblitt
2008-08-21 21:51 ` Yinghai Lu
2008-08-21 23:33 ` Joshua Hoblitt
2008-08-22 0:10 ` Joshua Hoblitt
2008-08-22 0:28 ` Yinghai Lu
2008-08-22 0:29 ` Joshua Hoblitt
2008-08-22 1:00 ` Joshua Hoblitt
2008-08-22 1:10 ` Joshua Hoblitt
2008-08-22 1:55 ` Yinghai Lu [this message]
2008-08-22 2:15 ` Joshua Hoblitt
2008-08-22 2:26 ` Yinghai Lu
2008-08-22 3:24 ` Yinghai Lu
2008-08-22 3:50 ` Ingo Molnar
2008-08-22 3:56 ` Ingo Molnar
2008-08-22 4:48 ` Yinghai Lu
2008-08-23 0:22 ` Joshua Hoblitt
2008-08-23 5:52 ` Yinghai Lu
2008-08-23 10:43 ` Ingo Molnar
2008-08-26 8:35 ` Joshua Hoblitt
2008-08-26 8:42 ` Ingo Molnar
2008-08-25 21:43 ` Joshua Hoblitt
2008-08-22 6:16 ` Yinghai Lu
2008-08-22 6:24 ` Ingo Molnar
2008-08-23 23:53 ` Arjan van de Ven
2008-08-25 9:17 ` Ingo Molnar
2008-08-22 3:26 ` Joshua Hoblitt
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=86802c440808211855h50ea65faudc169e48f83e18e2@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=j_kernel@hoblitt.com \
--cc=josh@hoblitt.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®