From: Hans-Christian Armingeon <linux.johnny@gmx.net>
To: Steven Walter <srwalter@yahoo.com>,
Berend De Schouwer <bds@jhb.ucs.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA text console corruption and fix.
Date: Thu, 28 Mar 2002 09:03:37 +0100 [thread overview]
Message-ID: <200203280903.37096.linux.johnny@gmx.net> (raw)
In-Reply-To: <1017256651.18224.40.camel@bds.ucs.co.za> <20020327225549.GA5337@hapablap.dyn.dhs.org>
Am Mittwoch, 27. März 2002 23:55 schrieb Steven Walter:
> On Wed, Mar 27, 2002 at 09:17:30PM +0200, Berend De Schouwer wrote:
> [...]
>
> > I have 3000+ identical VIA KT133/Duron 750MHz machines. In 20% of these
> > the bug is visible, in the others, it isn't. The machines run in an
> > LTSP-ish configuration. The machines are supposed to be identical (they
> > were bought together), but have different revisions of BIOS versions,
> > etc. They have on-board S3 Savage cards that steal RAM from the main
> > RAM.
>
> Aha, another. You're the fourth or fifth person with this problem. I
> have a patch very similar to yours. What my patch does is only clear
> bit 7, which is what was experimentally determined to disable the Write
> Memory Queue. So far it seems that only KM133 (KT133 w/onboard S3
> Savage) are afflicted.
Well, I had a corrupted screen [unreadable characters], after running KDE rc3 for a few hours. Seems like the console font has been corrupted.
>
> However, the patch isn't being accepted until an explanation from VIA is
> obtained (apparently the head kernel honcho's were explicitly told to
> clear bit 5). I'm working on that now.
next prev parent reply other threads:[~2002-03-28 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 19:17 VIA text console corruption and fix Berend De Schouwer
2002-03-27 22:55 ` Steven Walter
2002-03-28 8:03 ` Hans-Christian Armingeon [this message]
2002-03-28 9:33 ` Berend De Schouwer
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=200203280903.37096.linux.johnny@gmx.net \
--to=linux.johnny@gmx.net \
--cc=bds@jhb.ucs.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=srwalter@yahoo.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