From: Steve <s.egbert@sbcglobal.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-r1 MTRR bug (
Date: Fri, 14 Jan 2005 16:57:56 -0800 [thread overview]
Message-ID: <41E86A94.5050305@sbcglobal.net> (raw)
In-Reply-To: <41E84729.1090209@gentoo.org>
Daniel Drake wrote:
> Hi Andrew,
>
> Andrew Morton wrote:
>
>> Steve <s.egbert@sbcglobal.net> wrote:
>>
>>> For the Athlon 2100, I get the following outputs and then the VGA
>>> console is frozen from further output (but it doesn't prevent the
>>> full bootup into X windows session of which I am able to resume
>>> normal Linux/X session, but not able to regain any virtual console
>>> session.)
>>
>
>>> mtrr: size and base must be multiples of 4kiB (<<-- this line is
>>> repeated 20 times).
>>
>>
>>
>> Could you add this so we can track down the culprit?
>
>
> I got another user who reported the same problem to test the patch,
> the result is:
> http://bugs.gentoo.org/attachment.cgi?id=48451
> (original bug http://bugs.gentoo.org/77674)
>
> I will confirm whether or not this is a gentoo-specific problem or not
> and let you know.
>
> Daniel
>
Patched + removed VESAFB from config.
The mtrr patch in http://bugs.gentoo.org/show_bug.cgi?id=77674 appears
to fixes the problem. No further mtrr debug outputs occurred. Clean
boot output now for 2.6.10-r4 + mtrr-debug.patch.
Will try again with VESAFB re-enabled and post further results @
bugs.gentoo.org (if any).
THX!
Steve
next prev parent reply other threads:[~2005-01-17 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 21:26 2.4.10-r1 MTRR bug Steve
2005-01-12 21:34 ` Steve
2005-01-13 7:05 ` Andrew Morton
2005-01-14 22:26 ` Daniel Drake
2005-01-15 0:50 ` disabling VESAFB no longer locks up VT (was Re: 2.4.10-r1 MTRR bug) Steve
2005-01-15 0:57 ` Steve [this message]
2005-01-15 23:59 ` 2.4.10-r1 MTRR bug ( Steve
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=41E86A94.5050305@sbcglobal.net \
--to=s.egbert@sbcglobal.net \
--cc=akpm@osdl.org \
--cc=dsd@gentoo.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).