Very Computer

Quote:>Hi,

>I've had a K6-233 for 6 weeks now. Because of the succes peopple have had
>with overclocking their K6's I had to try it too. I'm running now at
>3*83MHz and it's really fast as expected. A week back I decided to take
>part in an effort (www.rc5.*ian.org) to crunch  rc-5 encryption. The
>crunching went fine for a few days at 390Kkeys/s until linux started
>crashing. At first I got kernel Oopses and after that the system just
>locked up and the screen was filled with

>'Aiee scheduling interrupt at xxxxx'

>Now, I suspect the problem is that the CPU is too hot, I've checked the
>temperature after a few crashes. It's been around 68 degrees celcius which
>seems kinda hot. AMD says the CPU should run in up to 70 degrees celcius.

The Thermalloy 2334B-TCM is one of my favorites.
Look for the "recommended thermal solutions" page on AMD's
web site for more ideas.

Mike

Hi,

I've had a K6-233 for 6 weeks now. Because of the succes peopple have had
with overclocking their K6's I had to try it too. I'm running now at
3*83MHz and it's really fast as expected. A week back I decided to take
part in an effort (www.rc5.*ian.org) to crunch  rc-5 encryption. The
crunching went fine for a few days at 390Kkeys/s until linux started
crashing. At first I got kernel Oopses and after that the system just
locked up and the screen was filled with

'Aiee scheduling interrupt at xxxxx'

Now, I suspect the problem is that the CPU is too hot, I've checked the
temperature after a few crashes. It's been around 68 degrees celcius which
seems kinda hot. AMD says the CPU should run in up to 70 degrees celcius.
So I just want to make shure that heat is the problem before buying extra
fans. What does the error message mean anyway?

Thanks, all help appreciated...

 ---
  ! Lauri

  <---------Lauri-Pesonen-------------------------------------------------->

  |             'Linux, the PC program from hell' David Hewson             |  
  <-------------------------------TiK W2 '97------------------Finland------>

: Hi,

: I've had a K6-233 for 6 weeks now. Because of the succes peopple have had
: with overclocking their K6's I had to try it too. I'm running now at
: 3*83MHz and it's really fast as expected. A week back I decided to take
: part in an effort (www.rc5.*ian.org) to crunch  rc-5 encryption. The
: crunching went fine for a few days at 390Kkeys/s until linux started
: crashing. At first I got kernel Oopses and after that the system just
: locked up and the screen was filled with

: 'Aiee scheduling interrupt at xxxxx'

  just as a side note, a few of use have gotten kernel oopses from the new
rc5 client. I got one just this morning..  the rest of the system didn't
even blink, though...

 <snip>

: Thanks, all help appreciated...

dave

--
David Murphy                       'I wanna make a dent in the universe.'
Student, Consultant, Programmer

: >Now, I suspect the problem is that the CPU is too hot, I've checked the
: >temperature after a few crashes. It's been around 68 degrees celcius which
: >seems kinda hot. AMD says the CPU should run in up to 70 degrees celcius.

: Aieee! that's a bit too close to 70 for comfort.
: Run (don't walk) and buy a good heatsink/fan combo.

definitely!  manufacturers normally quote those temperatures
for a thermister attached directly on the center of the case.
if the edge of your heatsink measures 68C, chances are good that
you have at least a 2C gradient to the chip, which is overheating...

: >So I just want to make shure that heat is the problem before buying extra
: >fans. What does the error message mean anyway?

it means just what it says: that the scheduler was called from within
an interrupt.  this is either a bogus interrupt handler, or some kind of
hardware failure.  with millions of people using Linux, chances are slim
that you'll discover a new bug in a driver.

therefore you need better cooling.  personally, I prefer good passive
heatsinks (with thermal grease) and decent airflow.  the advantage of
this over a heatsink/fan is simply that it's a nicer failure mode;
and certainly easier to tell when the case fan dies.  besides, you already
need case airflow to keep your other components from frying.

: >  |             'Linux, the PC program from hell' David Hewson             |  

heh.  I wonder if he'd understand being quoted sarcastically.
then again, if he doesn't grok Linux, he wouldn't get the joke.
bet he'd be scandalized by DaveM's comments in the code, too ;)

regards, mark hahn.
--

                                        http://neurocog.lrdc.pitt.edu/~hahn/