From: "Jim Roland" <jroland@roland.net>
To: "David Hollister" <david@digitalaudioresources.org>,
"Jan Niehusmann" <jan@gondor.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Athlon doesn't like Athlon optimisation?
Date: Sat, 1 Sep 2001 05:06:40 -0500 [thread overview]
Message-ID: <001101c132cd$cbbf7050$bb1cfa18@JimWS> (raw)
In-Reply-To: <20010831044247.B811@gondor.com> <3B8EFF67.9010409@digitalaudioresources.org>
Which kernel are you gentlemen using? I have a Athlon 1.2GHz (not
overclocked), 512MB PC133, and also an EPoX 8KTA3+, and have had no problems
whatsoever (using kernel 2.4.2-2).
----- Original Message -----
From: "David Hollister" <david@digitalaudioresources.org>
To: "Jan Niehusmann" <jan@gondor.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, August 30, 2001 10:07 PM
Subject: Re: Athlon doesn't like Athlon optimisation?
> Jan Niehusmann wrote:
> > I have a computer with a duron 600 which doesn't like current athlon
> > optimised kernels: It runs fairly well with an old 2.4.0-test7 kernel
> > (but I had some unexplained crashes during the last months),
> > but crashes after a few minutes after booting 2.4.9-ac3 or 2.4.7.
> >
> > If I don't build the kernels for athlon, but for i386 only, the
> > system seems to be stable. (Not tested for more than 20 minutes,
> > but definitely longer than the athlon optimised kernel was able to run)
> >
> > Does anybody know these symptoms and has an idea what may be wrong?
> > Is it likely to be a broken CPU?
> > The board is an A7V with the infamous via chipset, but I don't think
> > this looks like the typical via problems, does it?
> >
> > Jan
>
> This has apparently been a source of frustration for many an Athlon user,
myself
> included. I can't even get my system to finish the init process before it
> oopses and locks up on me.
>
> It seems to work somewhat better for some if you set your BIOS to the
> conservative settings, but that didn't help me. I have an Epox 8KTA3+
(Via
> KT133A) w/ a 1.4GHz Athlon and 512MB memory. If you can't get it to work
that
> way, just stick with the K6 setting. The point is, your hardware is
likely fine
> (fine being relative, I suppose)
> If there are other tricks, I'm all ears.
>
> --
> David Hollister
> Driversoft Engineering: http://devicedrivers.com
> Digital Audio Resources: http://digitalaudioresources.org
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-09-01 10:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 2:42 Athlon doesn't like Athlon optimisation? Jan Niehusmann
2001-08-31 3:07 ` David Hollister
2001-08-31 3:34 ` Albert D. Cahalan
2001-08-31 3:50 ` Richard Gooch
2001-08-31 4:20 ` Dan Hollis
2001-08-31 5:05 ` Chris Abbey
2001-08-31 8:27 ` Arjan van de Ven
2001-08-31 9:36 ` Nicholas Knight
2001-08-31 14:17 ` David Hollister
2001-08-31 6:02 ` Paul G. Allen
2001-08-31 6:15 ` Steven Spence
2001-08-31 14:06 ` Alan Cox
2001-08-31 9:21 ` Phillip Susi
[not found] ` <l4nnm9.rqp.ln@schlich.user.dfncis.de>
2001-08-31 13:58 ` Athlon doesn't like Athlon optimisation? [PATCH] Radu-Adrian Feurdean
2001-08-31 14:00 ` Athlon doesn't like Athlon optimisation? Alan Cox
2001-08-31 20:37 ` Dan Hollis
2001-08-31 20:53 ` Alan Cox
2001-09-08 18:01 ` Eric W. Biederman
2001-08-31 20:53 ` Mike Fedyk
2001-08-31 8:08 ` Joerg Plate
2001-08-31 18:18 ` Tim Moore
2001-08-31 19:17 ` Bobby D. Bryant
2001-08-31 19:43 ` Tim Moore
2001-09-01 10:06 ` Jim Roland [this message]
2001-09-01 12:04 ` Joerg Plate
2001-09-01 14:39 ` David Hollister
2001-09-01 15:50 ` Alan Cox
2001-09-01 16:27 ` David Hollister
2001-09-03 8:03 ` Jim Roland
[not found] <fa.kt7mv6v.qiq718@ifi.uio.no>
[not found] ` <fa.j3okgqv.lmova7@ifi.uio.no>
2001-08-31 12:11 ` Dan Maas
-- strict thread matches above, loose matches on Subject: below --
2001-09-03 8:13 Eric Olson
2001-09-03 15:55 ` Ghozlane Toumi
2001-09-04 10:19 ` Dan Hollis
2001-09-04 9:35 ` Matthew S . Hallacy
2001-09-05 5:21 Eric Olson
2001-09-05 9:59 ` Matthew S . Hallacy
2001-09-05 15:56 ` David Hollister
2001-09-05 14:22 noneuclidean
2001-09-05 17:37 ` Simen Thoresen
2001-09-05 18:07 ` Dan Hollis
2001-09-05 18:37 Eric Olson
2001-09-07 7:33 Jim Blomo
2001-09-07 8:00 ` Dan Hollis
2001-09-07 8:39 ` Andrzej Krzysztofowicz
2001-09-07 17:25 ` Mike Fedyk
2001-09-23 10:04 Jim Blomo
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='001101c132cd$cbbf7050$bb1cfa18@JimWS' \
--to=jroland@roland.net \
--cc=david@digitalaudioresources.org \
--cc=jan@gondor.com \
--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