public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: "Morten P.D. Stevens" <mstevens@win-professional.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: warning in arch/x86/kernel/cpu/mtrr/generic.c:400 with 2.6.29-rc3 on IBM x3400
Date: Wed, 11 Feb 2009 10:52:04 -0800	[thread overview]
Message-ID: <49931E54.7000305@kernel.org> (raw)
In-Reply-To: <B4ED8DE8E195E84A872496A085BC07822F2A@exchange01.corp.win-professional.com>

Morten P.D. Stevens wrote:
> Hi,
> 
>> so there is some problem with your BIOS, please ask the vendor to
>> provide one to make
>> 2.6.24 happy.
> 
> I'll report the issue to the IBM support.
> 
> on our IBM x3400 servers running RHEL the same output:
> 
> 2.6.18-92.1.10.el5 #
> 
> reg00: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1
> reg01: base=0x00000000 (   0MB), size=4096MB: write-back, count=1
> reg02: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
> reg03: base=0xbff80000 (3071MB), size=196608MB: uncachable, count=1

so that bios need to be fixed too.

> 
> and in dmesg:
> 
> mtrr: type mismatch for d0000000,1000000 old: uncachable new:
> write-combining
want add one entry for xwindow with your display card.
> 
> 
> Is this a big problem for direct usage? The performance on these servers
> is still fine...?
x window could be some slow.

YH

  reply	other threads:[~2009-02-11 18:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-08  1:43 warning in arch/x86/kernel/cpu/mtrr/generic.c:400 with 2.6.29-rc3 on IBM x3400 Morten P.D. Stevens
2009-02-09 15:50 ` Morten P.D. Stevens
2009-02-09 23:45   ` Ingo Molnar
2009-02-10  0:25     ` AW: warning in arch/x86/kernel/cpu/mtrr/generic.c:400 with2.6.29-rc3 " Morten P.D. Stevens
2009-02-10  2:40     ` warning in arch/x86/kernel/cpu/mtrr/generic.c:400 with 2.6.29-rc3 " Yinghai Lu
2009-02-10 16:21       ` Morten P.D. Stevens
2009-02-10 18:52         ` Yinghai Lu
2009-02-10 20:34           ` Morten P.D. Stevens
2009-02-10 20:45             ` Yinghai Lu
2009-02-10 21:19               ` Morten P.D. Stevens
2009-02-11  5:06                 ` Yinghai Lu
2009-02-11 16:01                   ` Morten P.D. Stevens
2009-02-11 18:52                     ` Yinghai Lu [this message]
2009-03-29 16:03                       ` Morten P.D. Stevens
2009-03-29 19:17                         ` Yinghai Lu
2009-02-11 10:43       ` Ingo Molnar

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=49931E54.7000305@kernel.org \
    --to=yinghai@kernel.org \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mstevens@win-professional.com \
    --cc=tglx@linutronix.de \
    /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