mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Andy Isaacson <adi@hexapodia.org>,
	Maciej Rutecki <maciej.rutecki@gmail.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Eric Anholt <eric@anholt.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	"lenb@kernel.org" <lenb@kernel.org>,
	mjg@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
	rui.zhang@intel.com, airlied@redhat.com
Subject: Re: [Linux 2.6.29-rc6] [drm:i915_set_status_page] *ERROR* can not ioremap virtual address for G33 hw status page
Date: Tue, 24 Feb 2009 20:44:32 +0100	[thread overview]
Message-ID: <20090224194432.GB28772@elte.hu> (raw)
In-Reply-To: <86802c440902232150m2b22e3cfg8993193f8867dfbf@mail.gmail.com>


* Yinghai Lu <yinghai@kernel.org> wrote:

> On Mon, Feb 23, 2009 at 7:23 PM, Andy Isaacson <adi@hexapodia.org> wrote:
> > On Mon, Feb 23, 2009 at 05:01:10PM -0800, Yinghai Lu wrote:
> >> CONFIG_MTRR=y
> >> CONFIG_MTRR_SANITIZER=y
> >> CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
> >> CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
> >>
> >> should help mtrr ones.
> >>
> >> please post bootlog with those option set.
> >
> > Doesn't help here (Dell E6400).
> >
> > [    0.000000] Initializing cgroup subsys cpuset
> > [    0.000000] Initializing cgroup subsys cpu
> > [    0.000000] Linux version 2.6.29-rc6-dirty (adi@cvp-loaner-01) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu12) ) #14 SMP Mon Feb 23 19:05:31 PST 2009
> > [    0.000000] Command line: root=/dev/sda1 ro
> > [    0.000000] KERNEL supported cpus:
> > [    0.000000]   Intel GenuineIntel
> > [    0.000000]   AMD AuthenticAMD
> > [    0.000000]   Centaur CentaurHauls
> > [    0.000000] BIOS-provided physical RAM map:
> > [    0.000000]  BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
> > [    0.000000]  BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
> > [    0.000000]  BIOS-e820: 0000000000100000 - 000000007d04d400 (usable)
> > [    0.000000]  BIOS-e820: 000000007d04d400 - 000000007d04f400 (ACPI NVS)
> > [    0.000000]  BIOS-e820: 000000007d04f400 - 0000000080000000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
> > [    0.000000]  BIOS-e820: 00000000ffe60000 - 0000000100000000 (reserved)
> > [    0.000000] DMI 2.4 present.
> > [    0.000000] last_pfn = 0x7d04d max_arch_pfn = 0x100000000
> > [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> > [    0.000000] original variable MTRRs
> > [    0.000000] reg 0, base: 0GB, range: 32GB, type WB
> > [    0.000000] reg 1, base: 3584MB, range: 512MB, type UC
> > [    0.000000] reg 2, base: 2012MB, range: 4MB, type UC
> > [    0.000000] reg 3, base: 2016MB, range: 32MB, type UC
> 
> the BIOS is so sick
> according to MTRR, it said:
> [0,2012M) is WB
> [2048M, 3.5G) is WB too
> [4G, 32G) is WB
> 
> but according to e820: about [0,2g) is RAM...
> 
> really not how to workaround in BIOS.

I suspect the box was tested with other OSs and limped along 
there. Should we perhaps clear non-sensical MTRR entries?

	Ingo

  parent reply	other threads:[~2009-02-24 19:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 14:46 Maciej Rutecki
2009-02-23 15:22 ` Sitsofe Wheeler
2009-02-23 18:27   ` Maciej Rutecki
2009-02-23 20:02 ` Eric Anholt
2009-02-23 21:30   ` Rafael J. Wysocki
2009-02-23 21:40     ` Maciej Rutecki
2009-02-24  1:01       ` Yinghai Lu
2009-02-24  3:23         ` Andy Isaacson
2009-02-24  5:50           ` Yinghai Lu
2009-02-24  6:48             ` Andy Isaacson
2009-02-24 22:54               ` Andy Isaacson
2009-02-25 14:35                 ` Zdenek Kabelac
2009-02-27 11:14                   ` Maciej Rutecki
2009-02-24 19:44             ` Ingo Molnar [this message]
2009-02-24 19:48               ` Yinghai Lu
2009-02-24 21:39                 ` Ingo Molnar
2009-02-24 21:44                   ` Dave Airlie
2009-02-24 21:59                     ` Linus Torvalds
2009-02-24 22:10                       ` Pallipadi, Venkatesh
2009-02-24  6:54         ` Maciej Rutecki
2009-02-24  8:54           ` Maciej Rutecki
2009-02-24  9:01             ` Maciej Rutecki
2009-02-24 18:25             ` Yinghai Lu
2009-02-24  3:56       ` Andy Isaacson

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=20090224194432.GB28772@elte.hu \
    --to=mingo@elte.hu \
    --cc=adi@hexapodia.org \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric@anholt.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=mjg@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@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®