public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Foerster <puckwork@madz.net>
To: linux-kernel@vger.kernel.org
Subject: Again: Linux 2.4.x and AMD Athlon
Date: Thu, 12 Jul 2001 09:15:51 +0200	[thread overview]
Message-ID: <20010712071955Z267448-720+1447@vger.kernel.org> (raw)

Hi folks,

i've upgraded from an AMD Athlon 650 to this system :

AMD Athlon 1,3 GHz, 266 FSB
2*128 MB Kingston SDRAM PC133
Epox 8KTA3+ (VIA KT133A, via686b Southbridge)
Linux 2.4.5-ac27

(Powersupply is 400 Watt, Video is handled by GeForce2 GTS 32 MB)

Compiling the kernel works great, fast and stable. Whenever there is high load
on the systembus (e.g. compiling some source) the noise of my powersupply fans increase.
(Not under Windows, so i think linux makes much more use of the power of AMD's CPUs)

I ran memtest86 for hours without any problems, i couldn't crash the system or any process..
until i start X 4.0.3.

I've tested it with KDE2 and Gnome 1.2. After a (mostly) successful start of one of the 
windowmanagers, most applications crush whenever i open them.
Running console-applications in xterm or compiling the kernel in xterm works still stable, but
working with X11 apps is no more fun ... crashes all over ... (segfaults, sig 11)

This message is meant to be a better approach in solving the problem(s) with AMD Athlons/Durons.

I didn't overclock anything. Compiling the kernel with K6-2 Support or PIII fixes the problems
(and the noise of the power-fan stays constant, so i think the cpu-power isn't used to the max :) )

I've monitored my system using lm_sensors and didn't get any unusual high or low values
(cpu is about 42°)

Seems to be the problem with the AMD optimazion in the kernel.

Thomas


             reply	other threads:[~2001-07-12  7:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12  7:15 Thomas Foerster [this message]
2001-07-12 19:16 ` Again: Linux 2.4.x and AMD Athlon Alan Cox
2001-07-13  2:31 ` Benjamin C.R. LaHaise
2001-07-13  8:52 ` Joerg Schmitz-Linneweber
  -- strict thread matches above, loose matches on Subject: below --
2001-07-12 21:53 Kenneth Vestergaard Schmidt
2001-07-13 11:13 ` Wilfried Weissmann
2001-07-13  7:00 Thomas Foerster
2001-07-13 10:42 ` Alan Cox
2001-07-13 11:12 Thomas Foerster
2001-07-13 12:34 ` Alan Cox
2001-07-13 22:05 ` Stefan Jaschke
2001-07-13 12:19 Thomas Foerster
2001-07-14 19:54 Gabriel Friedmann
2001-07-14 20:04 ` Alan Cox
2001-07-15  0:51 ` Luigi Genoni
2001-07-15  7:09 Andreas Hartmann
2001-07-16  2:19 ` Stephen Degler
2001-07-16  8:50 David Balazic

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=20010712071955Z267448-720+1447@vger.kernel.org \
    --to=puckwork@madz.net \
    --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