From: ebiederman@lnxi.com (Eric W. Biederman)
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LinuxBIOS + ASUS CUA + 2.4.5 works; with 2.4.6 locks up
Date: 18 Sep 2001 17:43:59 -0600 [thread overview]
Message-ID: <m33d5kgj40.fsf@DLT.linuxnetworx.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10109181931570.2275-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10109181931570.2275-100000@coffee.psychology.mcmaster.ca>
Mark Hahn <hahn@physics.mcmaster.ca> writes:
> > It is hard to call. The most interesting case I know of is the VIA kt133
> > AMD bug. I believe it is register 0x55 bit 7 that when set causes an
> > athlon optimized memcpy to crash the machine, but when clear it works.
>
> "causes" is a bit strong - there are plenty of machines where it
> most definitely doesn't effect stability at all. that is, kt133a
> machines which use Arjan's fast_copy_page without any problem,
> and yet have 0x55:7 set. (my A7V133's is 0x89, for instance.)
Granted. But it it does seem to be the cause for the set of systems affected.
And it nicely illustrates the point that you can have very weird problems that
don't show up under normal circumstances.
In the kt133 case it feels like a problem initializing the cpu<->northbridge bus.
In Rons case it is probably completely different.
Eric
prev parent reply other threads:[~2001-09-18 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 22:22 LinuxBIOS + ASUS CUA + 2.4.5 works; with 2.4.6 locks up Ronald G Minnich
2001-09-18 22:54 ` Eric W. Biederman
2001-09-18 22:56 ` Ronald G Minnich
2001-09-18 23:03 ` Eric W. Biederman
2001-09-18 23:35 ` Mark Hahn
2001-09-18 23:43 ` Eric W. Biederman [this message]
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=m33d5kgj40.fsf@DLT.linuxnetworx.com \
--to=ebiederman@lnxi.com \
--cc=hahn@physics.mcmaster.ca \
--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