linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Chris Vandomelen <chrisv@b0rked.dhs.org>
Cc: <linux-kernel@vger.kernel.org>, VDA <VDA@port.imtp.ilyichevsk.odessa.ua>
Subject: Re: Athlon bug stomping #2
Date: 13 Sep 2001 23:51:58 -0600	[thread overview]
Message-ID: <m1d74utj41.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.31.0109132101210.10262-100000@linux.local>
In-Reply-To: <Pine.LNX.4.31.0109132101210.10262-100000@linux.local>

Chris Vandomelen <chrisv@b0rked.dhs.org> writes:

> > On Thu, 13 Sep 2001, VDA wrote:
> >
> > > Device 0 Offset 55 - Debug (RW)
> > > 7-0 Reserved (do not program). default = 0
> > > *** 3R BIOS: non-zero!?
> > > *** YH BIOS: zero.
> > > *** TODO: try to set to 0.
> >
> > I tryed sequentially to test the values given. It only worked when I set
> > offset 0x55 to 0, and then stopped. I don't need to set any other value in
> > other addresses. This is enough.
> >
> > It's weird when your system only works when changing a "do not
> > program" value. :)
> 
> Makes me wonder just a little: my system is perfectly fine with 0x02
> written to offset 0x55. (Yes, it is an Athlon compiled kernel.. something
> I've been doing ever since I've been using this machine). It had it's
> problems when I originally got it

So we have two confirmations that setting this register clears the problem.
Anyone want to generate a kernel patch so this fix can get some wider
testing?

Eric

  reply	other threads:[~2001-09-14  6:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 12:31 Athlon bug stomping #2 VDA
2001-09-14  2:56 ` Roberto Jung Drebes
2001-09-14  4:02   ` Chris Vandomelen
2001-09-14  5:51     ` Eric W. Biederman [this message]
2001-09-14  7:34       ` Roberto Jung Drebes
2001-09-14  8:27         ` Athlon: Try this (was: Re: Athlon bug stomping #2) Roberto Jung Drebes
2001-09-14 18:19           ` Byron Stanoszek
2001-09-15 18:00             ` Liakakis Kostas
2001-09-15 20:28               ` VDA
2001-09-15  7:15           ` brian
2001-09-19  1:30             ` brian
2001-09-19 13:10             ` Re[2]: " VDA
2001-09-19 23:56               ` Nicholas Knight
2001-09-20  3:17                 ` Nicholas Knight
2001-09-20 12:34                   ` Alan Cox
2001-09-16 21:53           ` Carsten Leonhardt
2001-09-19  3:55             ` Dan Hollis
2001-09-14  9:26         ` Jeff Lightfoot

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=m1d74utj41.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=VDA@port.imtp.ilyichevsk.odessa.ua \
    --cc=chrisv@b0rked.dhs.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).