From: Shawn Starr <spstarr@sh0n.net>
To: Dave Jones <davej@suse.de>
Cc: linux-kernel@vger.kernel.org, rgooch@atnf.csiro.au
Subject: Re: MTRR Problems - 2.4.19-rc3
Date: Thu, 25 Jul 2002 13:55:59 -0400 [thread overview]
Message-ID: <200207251355.59880.spstarr@sh0n.net> (raw)
In-Reply-To: <20020725195000.A8672@suse.de>
Is there a fix to this?
Shawn.
On July 25, 2002 01:50 pm, Dave Jones wrote:
> On Thu, Jul 25, 2002 at 01:41:24PM -0400, Shawn Starr wrote:
> > > > mtrr: no MTRR for e0000000,4000000 found
> >
> > Fair enough, but that doesn't explain the broken MTRR :)
>
> Something in userspace tried to delete an MTRR that didn't exist.
> The only time I've seen this happen personally has been with
> a dual-head card for which the BIOS set up one MTRR to cover
> the video ram used by both heads, and then iirc X did something
> silly and tried to remove separate MTRRs for each head on exit.
>
> Dave
next prev parent reply other threads:[~2002-07-25 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 7:03 MTRR Problems - 2.4.19-rc3 Shawn Starr
2002-07-25 13:05 ` Dave Jones
2002-07-25 17:41 ` Shawn Starr
2002-07-25 17:50 ` Dave Jones
2002-07-25 17:55 ` Shawn Starr [this message]
2002-07-25 18:01 ` Dave Jones
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=200207251355.59880.spstarr@sh0n.net \
--to=spstarr@sh0n.net \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
/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