From: Richard Browning <richard@redline.org.uk>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Horst von Brand <vonbrand@inf.utfsm.cl>,
Len Brown <len.brown@intel.com>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
<linux-kernel@vger.kernel.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Subject: Re: ANYONE? Re: SMP + Hyperthreading / Asus PCDL Deluxe / Kernel 2.4.x 2.6.x / Crash/Freeze
Date: Wed, 24 Mar 2004 04:01:42 +0000 [thread overview]
Message-ID: <200403240401.42322.richard@redline.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0403220823020.2831-100000@poirot.grange>
On Monday 22 March 2004 07:25, Guennadi Liakhovetski wrote:
> Aha! A single thread? A specific asm insn? Is gcc --version enough to kill
> the machine? Or on smth like
> int main(void)
> {return 0;}
> gcc -E; gcc -S; gcc -c; ld? Step-by-step with gdb (hopefully, gdb doesn't
> have this insn...). NMI watchdog?
gcc -version is fine. A compile will cause the problem.
It should be noted that whilst a ./configure cycle is *guaranteed* to initiate
the MCE, the MCE can occur on other (seemingly random) occasions.
This of course smacks of hardware failure, but not only are the components new
I have also swapped them all (excluding graphics card.) And, don't forget,
simple dual 'SMP' mode works fine too.
R
next prev parent reply other threads:[~2004-03-24 4:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F4B99@hdsmsx402.hd.intel.com>
2004-03-11 6:50 ` Len Brown
2004-03-11 13:38 ` Richard Browning
2004-03-11 18:19 ` Richard Browning
2004-03-11 22:17 ` Zwane Mwaikambo
2004-03-12 0:22 ` Richard Browning
2004-03-12 0:36 ` Zwane Mwaikambo
2004-03-12 0:42 ` Richard Browning
2004-03-12 6:27 ` Len Brown
2004-03-12 7:07 ` Len Brown
2004-03-12 8:24 ` Richard Browning
2004-03-18 3:01 ` Richard Browning
2004-03-20 14:33 ` ANYONE? " Richard Browning
2004-03-20 17:26 ` Richard Browning
2004-03-20 21:30 ` Zwane Mwaikambo
2004-03-21 3:41 ` Richard Browning
2004-03-21 3:33 ` Horst von Brand
2004-03-21 20:32 ` Richard Browning
2004-03-21 23:33 ` Denis Vlasenko
2004-03-22 1:04 ` Richard Browning
2004-03-22 7:25 ` Guennadi Liakhovetski
2004-03-24 4:01 ` Richard Browning [this message]
2004-03-24 7:15 ` Guennadi Liakhovetski
[not found] ` <1080214330.982.10.camel@sven>
[not found] ` <200403251304.56877.richard@redline.org.uk>
2004-03-25 22:47 ` Sven Dowideit
2004-03-26 0:36 ` Richard Browning
2004-03-21 14:46 ` Richard B. Johnson
2004-03-21 14:57 ` Richard Browning
2004-03-12 1:16 ` Richard Browning
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=200403240401.42322.richard@redline.org.uk \
--to=richard@redline.org.uk \
--cc=g.liakhovetski@gmx.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=venkatesh.pallipadi@intel.com \
--cc=vonbrand@inf.utfsm.cl \
--cc=zwane@linuxpower.ca \
/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
Powered by JetHome