From: Pedro Pla <pedropla@holidaymarketing.com>
To: Doug Ledford <dledford@redhat.com>
Cc: linux-scsi@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: Problem with Gdt driver under smp?
Date: Tue, 05 Nov 2002 09:17:25 +0800 [thread overview]
Message-ID: <3DC71C25.1000702@holidaymarketing.com> (raw)
In-Reply-To: 20021031120257.GF23217@redhat.com
Sorry I accidently sent the last one in html, so it probably didn't get
through.
Doug Ledford wrote:
>On Thu, Oct 31, 2002 at 04:37:07PM +0800, Pedro Pla wrote:
>
>
>>Hello,
>>
>>I was wondering if there is any known problem with the Gdt driver under
>>an smp machine, I have a dual p3 scb2 motherboard, with 1-2GB ram, an
>>scrmr intel 0 channel raid controller and 3 hotswap disks. Initially I
>>thought it was a memory problem since the kernel was complaining at
>>mem_alloc:89, however as long as the memory I move is not read from the
>>disk (through a kernel compile, or a dd if=/dev/sda) then it seems to
>>work fine. A kernel compiled with no smp works fine as well. I've tried
>>kernels from the 2.2.22 to the 2.4.17-2.4.20-pre10-ac with pre11 patches
>>applied on top.
>>
>>The symptoms are segmentation faults, signal 11's, and occasionally
>>kernel oops at mem_alloc:89, I have also seen several kernel oops in
>>journal.c when I tried using ext3, I disactivated that but the faults
>>remained. It has also froze once and given a kernel oops while loading
>>the scsi driver at boot, and another time it simply rebooted the machine
>>when loading the driver. Any ideas? For now I will work with only one
>>cpu and smp disactivated since that gives no problems at all, but I
>>would like to be able to unleash the full power of these machines.
>>
>>
>
>Sounds like typical bad RAM problems. Run a memory test on your RAM.
>
>
>
I've run memory tests, and memtest86 v3 gives no errors at all after its
most thorough testing, I did however find some problems when running a
test on memtest86 v2.8, however that gave errors on 8 seperate simm
cards running under two different dual p3 motherboards, I just find it
strange that they would all fail, I thought it might be the motherboard
then, but 2 motherboards failing?
next prev parent reply other threads:[~2002-11-05 1:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 8:37 Problem with Gdt driver under smp? Pedro Pla
2002-10-31 12:02 ` Doug Ledford
2002-11-05 1:17 ` Pedro Pla [this message]
[not found] ` <3DC71BF8.80100@holidaymarketing.com>
2002-11-05 3:34 ` Doug Ledford
2002-11-06 0:50 ` Pedro Pla
[not found] ` <3DC79701.8070802@holidaymarketing.com>
[not found] ` <20021105164106.GG16634@redhat.com>
2002-11-06 1:27 ` Pedro Pla
2002-11-06 3:34 ` Pedro Pla
2002-11-06 3:34 ` Pedro Pla
2002-11-06 14:33 ` Bill Davidsen
2002-11-07 2:08 ` Pedro Pla
2002-11-07 5:10 ` Ishikawa
2002-11-07 7:34 ` Pedro Pla
2002-11-05 3:35 ` Doug Ledford
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=3DC71C25.1000702@holidaymarketing.com \
--to=pedropla@holidaymarketing.com \
--cc=dledford@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--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 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.