From: Richard Browning <richard@redline.org.uk>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: 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: Mon, 22 Mar 2004 01:04:10 +0000 [thread overview]
Message-ID: <200403220104.10619.richard@redline.org.uk> (raw)
In-Reply-To: <200403220133.21659.vda@port.imtp.ilyichevsk.odessa.ua>
On Sunday 21 March 2004 23:33, Denis Vlasenko wrote:
> But it must be SOMETHING, right?
I haven't been completely idle :)
> Kernel compile is too broad. Can you try to narrow it down?
> Does burnCPU trigger it? Several burnCPUs?
> dd if=/dev/hda of=/dev/null?
> dd if=/dev/zero of=file bs=1M count=128?
> network flood? (/me uses netcat and UDP)
> Combination of above?
As I suggested in the original post, the problem can be triggered simply by
executing ./configure - the kernel corrupts when gcc does its thing. I can
boot into KDE, run Enemy Territory, execute a Java compile, and so on. But
the thing absolutely and most definitely able to upset the cart is to execute
gcc.
Oh, I've even recompiled libgcc etc using a variety of optimisation flags
(Gentoo is my distro), from the sooper-over-the-top P4 flags down to simple
-O2 -march=pentium3. With no effect.
> Then, you will be able to call for testing.
Because I have exhausted my own meagre talents in the search for the cause (eg
swapping hardware, altering config parameters, using different hard drives,
etc) I felt the time was right to 'call in the experts'.
> You can post your kernel version and .config
I've done that, too, oddly enough. The config, cpuinfo, pci, the works. It's
all there in the original thread.
> and ask folks who has identical hardware to try
> to duplicate.
The nearest I've got is someone who has the same mobo but with different CPUs,
no AGP graphics card and no SATA.
Like I said, as a software engineer of some 20 years (heavens! I had my first
game published when I was 14, lovingly handcrafted in 65c102 assember), I am
aware of the steps required to pinpoint an issue. The penultimate one - the
last, of course, is to give up - is to enlist the help of others who know
more. That is what I've done.
R
next prev parent reply other threads:[~2004-03-22 1:04 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 [this message]
2004-03-22 7:25 ` Guennadi Liakhovetski
2004-03-24 4:01 ` Richard Browning
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=200403220104.10619.richard@redline.org.uk \
--to=richard@redline.org.uk \
--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