mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jim McCloskey <mcclosk@ucsc.edu>
Cc: linux-kernel@vger.kernel.org, Shaohua Li <shaohua.li@intel.com>
Subject: Re: [PROBLEM] mtrr's not set, 2.6.13
Date: Mon, 12 Sep 2005 02:51:20 -0700	[thread overview]
Message-ID: <20050912025120.4016c36b.akpm@osdl.org> (raw)
In-Reply-To: <20050912091021.GA2859@branci40>

Jim McCloskey <mcclosk@ucsc.edu> wrote:
>
>  I'm not sure who to report this to ....

This works.

>  Somewhere between 2.6.11.3 and 2.6.12 (also under 2.6.13), the
>  following change occurred on this box.
> 
>  Under 2.6.11.3, mtrr ranges are automatically set when X is started:
> 
>  ----------------------------------------------------------------------
>  running 2.6.11.3:
> 
>  cat /proc/mtrr
>  reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
>  reg01: base=0xe8000000 (3712MB), size= 128MB: write-combining, count=2
>  reg02: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=1
>  ----------------------------------------------------------------------
> 
>  After installation of 2.6.12/13, mtrr ranges are not set:
> 
>  ----------------------------------------------------------------------
>  running 2.6.13:
> 
>  Xorg.0.log:
> 
>  (WW) RADEON(0): Failed to set up write-combining range (0xe8000000,0x8000000)
> 
>  /var/log/messages:
> 
>  Aug 30 17:37:13 localhost kernel: mtrr: type mismatch for e8000000,8000000 old: write-back new: write-combining
>  Aug 30 17:37:14 localhost kernel: mtrr: type mismatch for e0000000,8000000 old: write-back new: write-combining
>  Aug 30 17:37:14 localhost kernel: [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc RV280 [Radeon 9200]
>  Aug 30 17:37:14 localhost kernel: mtrr: type mismatch for e8000000,8000000 old: write-back new: write-combining
> 
>  cat /proc/mtrr
>  reg00: base=0x00000000 (   0MB), size=983552MB: write-back, count=1
>  ----------------------------------------------------------------------
> 
>  Under 2.6.13 it's fairly easy to force a crash of the X server (e.g. by
>  playing Tuxracer badly).
> 
>  The only change here is in the kernel-version. I haven't tried all the
>  point releases between 2.6.11.3 and 2.6.12, but the relevant Changelogs
>  don't suggest that anything relevant changed.

In a 2.6.13 tree could you please do

wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc2/2.6.13-rc2-mm1/broken-out/mtrr-suspend-resume-cleanup.patch
patch -p1 -R < mtrr-suspend-resume-cleanup.patch

and retest?

Thanks.

  reply	other threads:[~2005-09-12  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12  9:10 Jim McCloskey
2005-09-12  9:51 ` Andrew Morton [this message]
2005-09-12 17:24   ` Jim McCloskey
2005-09-12 23:27     ` Dave Jones
2005-09-13  3:01     ` Shaohua Li
2005-09-14  9:22 Kenneth Parrish
2005-10-04 21:14 Jouni Karvo

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=20050912025120.4016c36b.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcclosk@ucsc.edu \
    --cc=shaohua.li@intel.com \
    /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®