From: Marc Giger <gigerstyle@gmx.ch>
To: linux-kernel@vger.kernel.org
Subject: Fw: Seg-faults and crashes
Date: Mon, 9 Sep 2002 20:56:06 +0200 [thread overview]
Message-ID: <20020909205606.39282976.gigerstyle@gmx.ch> (raw)
Hi all!
First, I'm sorry for the not directly linux related question.
I don't know who to ask for my problems. I think the Linux people can help me because they have the biggest experience with hard- and software. And, as you know, most people in the computer shops are idiots!
Secondly, very good work from all Kernel-gurus! I love Linux (not so much as my girlfriend but also much) :-)
Well, here's my problem:
I have a big hardware problem but I don't know what to do anymore..:-(
For more than 2 years the box was running smoothly.
For a month or two now it started lots of segmentation faults. Mostly when I was compiling kernel or other programs.
Since last week, I don't have seg-faults anymore BUT the box crashes after a while...
Mostly, the crashes happen when the machine is under high load.
What did I do to find the bug?
Replaced the memory sticks with new ones...
Removed all cards (incl. graphic card)
Booted only with one processor (and then changed both)
All of them didn't help, the same problems remain.
I think it must be a hardware problem because I have never seen any kernel oops or other kernel message in the log files!
Well, my question is: is it possible that the memory controller on the MB is defective? Can we boot a machine with a defective memory controller?
What are the next steps to find the dog?
Some info re. my box:
Dual P3 600Mhz
Intel i820 chipset
RAMBUS memory
18 GB IBM SCSI HD (also crashes without connected IDE or SCSI HD)
80 GB IBM IDE HD
Do you need more info? No problem!
Thank you very very much!!
Have a nice day with a running tux :-)
greets
marc
reply other threads:[~2002-09-09 18:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020909205606.39282976.gigerstyle@gmx.ch \
--to=gigerstyle@gmx.ch \
--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
all inboxes | Powered by JetHome®