public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Wragg <dpw@doc.ic.ac.uk>
To: v.j.orlikowski@gte.net
Cc: Julian Anastasov <ja@ssi.bg>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.18pre25, S3, AMD K6-2, and MTRR....
Date: 10 Dec 2000 18:20:31 +0000	[thread overview]
Message-ID: <y7ru28cdtow.fsf@sytry.doc.ic.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0012092218280.877-100000@u> <14898.42117.34020.145433@critterling.garfield.home>

"Victor J. Orlikowski" <v.j.orlikowski@gte.net> writes:
> This is precisely my problem.
> K6-2, model 8, stepping 12.
> Thus far, everything is *fine*, as long as MTRR is not compiled into
> the kernel.
> If MTRR is compiled into the kernel, I get lock-ups in X *only*, and
> the entire machine locks.

Just to check the important facts (correct any of this if it is
wrong): In 2.2.18, the problem appears when you enable MTRR support,
but goes away when you disable MTRR support.  You are using the vesafb
driver.  You are running XFree86-3.x.

Are you passing any vesafb options on the kernel command line?

If not, this is very strange, because the 2.2.18 mtrr.c (or any other)
should not be touching the MTRR registers (or whatever the K6 calls
them) unless you do something to /proc/mtrr.

If I understood why the MTRR driver was doing something on the K6-2,
then model-specific differences might make some sense.  But currently,
I don't see why there would be any difference between "MTRR disabled"
and "MTRR enabled, but not used".


David Wragg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-10 18:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-09 23:05 2.2.18pre25, S3, AMD K6-2, and MTRR Julian Anastasov
2000-12-09 21:30 ` Victor J. Orlikowski
2000-12-10 18:20   ` David Wragg [this message]
2000-12-10 18:34     ` Steven Walter
2000-12-11 10:29       ` David Wragg
2000-12-09 23:48 ` Victor J. Orlikowski
2000-12-10 22:32   ` Julian Anastasov
2000-12-11  0:58     ` Victor J. Orlikowski
2000-12-11  8:57       ` Julian Anastasov
  -- strict thread matches above, loose matches on Subject: below --
2000-12-09 15:53 Victor J. Orlikowski

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=y7ru28cdtow.fsf@sytry.doc.ic.ac.uk \
    --to=dpw@doc.ic.ac.uk \
    --cc=ja@ssi.bg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v.j.orlikowski@gte.net \
    /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