From: Pedro Pla <pedropla@holidaymarketing.com>
To: linux-smp@vger.kernel.org
Subject: Problem with dual p3 serverworks motherboard
Date: Wed, 30 Oct 2002 10:28:17 +0800 [thread overview]
Message-ID: <3DBF43C1.8070301@holidaymarketing.com> (raw)
Hello,
I have been having problems with some new Intel SCB2 motherboards and
1-2GB ram. The root partition is on a hardware raid 5 with the intel
SCRMR raid controller. I first noticed the problem after getting a basic
debian installed when trying to compile the kernel, initially it gave
the typical signal 11 and segmentation faults which made me think it was
a memory problem, however changing memory didn't help, after that I
suspected it might be a mother board issue and moved to the other
motherboard I had for tests, and it gave the same. After I thought it
might be a kernel issue, so I tried every kernel since 2.4.17 -
2.4.20-pre11 with the pre10-ac patches applied.. in many different
combinations. Some kernels didn't even seem to boot without several oops
in the mem_alloc.c:89. Others booted fine and seemed to be stable till I
did anything that used ram (including the dd if=/dev/sda2 of=/dev/null)
tests. Finally frustrated with my efforts I decided to see if it ran on
a 2.2.22 kernel. No problems when booting but when trying to use any
large amount of ram, or a kernel compile it gave the same errors. Could
this be a hardware problem along all the hardware I bought? Or is there
any known issues with this?
On a side note, I ran the memtest86 v3 and it gives no errors, however
an earlier (2.8) version gives some errors in the ram?
Kind regards
Pedro
next reply other threads:[~2002-10-30 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 2:28 Pedro Pla [this message]
2002-10-30 15:18 ` Problem with dual p3 serverworks motherboard Alan Cox
2002-10-31 1:28 ` Pedro Pla
2002-10-31 11:43 ` Alan Cox
2002-10-31 20:33 ` Bill Davidsen
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=3DBF43C1.8070301@holidaymarketing.com \
--to=pedropla@holidaymarketing.com \
--cc=linux-smp@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