From: Andrea Arcangeli <andrea@suse.de>
To: Peter Waechtler <pwaechtler@mac.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: Oops in sched.c on PPro SMP
Date: Tue, 17 Sep 2002 19:41:23 +0200 [thread overview]
Message-ID: <20020917174123.GU11605@dualathlon.random> (raw)
In-Reply-To: <8F7381E4-CA60-11D6-8873-00039387C942@mac.com>
On Tue, Sep 17, 2002 at 07:11:52PM +0200, Peter Waechtler wrote:
> Once I had a machine check exception - sine then I lowered the CPU clock.
> After the box was running fine with 180MHz I switched to 200MHz
> (yes, I overclocked the CPUs with 233MHz 2 or 3 years - without problems)
I guess this explain the corruption. Please make sure the cpu are not
overclocked at all and then try to reproduce. You cannot choose 180mhz
or 200mhz randomly based on which kernel crashes or not, if the cpu are
180mhz ppro you should use 180mhz only, 200mhz will break. It won't
break so easily as 233mhz, but it will, the timings are strict on smp.
So please try to reproduce at 180mhz if the cpu should run at 180mhz.
I don't want to sound boring but please next times try if you can
reproduce on non overclocked hardware before reporting anything to l-k.
Andrea
next prev parent reply other threads:[~2002-09-17 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 14:25 Oops in sched.c on PPro SMP Peter Waechtler
2002-09-16 14:49 ` Alan Cox
2002-09-16 15:44 ` Andrea Arcangeli
2002-09-16 21:16 ` Peter Waechtler
2002-09-16 23:13 ` Andrea Arcangeli
2002-09-17 17:18 ` Peter Waechtler
2002-09-17 2:51 ` Adam Kropelin
2002-09-16 21:10 ` Peter Waechtler
2002-09-16 15:42 ` Andrea Arcangeli
2002-09-17 17:11 ` Peter Waechtler
2002-09-17 17:41 ` Andrea Arcangeli [this message]
2002-09-18 11:00 ` Peter Waechtler
2002-09-18 17:52 ` Andrea Arcangeli
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=20020917174123.GU11605@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pwaechtler@mac.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.