From: Pedro Pla <pedropla@holidaymarketing.com>
To: linux-scsi@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: Problem with Gdt driver under smp?
Date: Wed, 06 Nov 2002 08:50:08 +0800 [thread overview]
Message-ID: <3DC86740.3070804@holidaymarketing.com> (raw)
In-Reply-To: 20021105033435.GA16634@redhat.com
Doug Ledford wrote:
>On Tue, Nov 05, 2002 at 09:16:40AM +0800, Pedro Pla wrote:
>
>
>>Doug Ledford wrote:
>>
>>
>>>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?
>>
>>
>>
>
>I've got a memory test shell script on my web site that runs under
linux.
>Do me a favor and see if it thinks your machine has bad RAM.
>
>
>
Been running the script all day and still no errors yet, and yes, it
seems to have used up all the memory or so says a cat /proc/meminfo with
only a few megs free and no swap activated. This is under a no smp
compiled kernel, under an smp compiled kernel I think it could die while
ungzipping the first source directory.. yeah it's that bad, no "subtle"
problem, just an asap kernel oops or segmentation fault.. can't switch
to mp 1.1 from mp 1.4 on this motherboard either, or at least I haven't
found out how yet, it's an intel scb2, intel says nothing about how to
do so on their sites, and the bios has no such option... at least the
machine runs flawlessly all tests in non-smp mode which makes me think
it isn't hardware..
next prev parent reply other threads:[~2002-11-06 0:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DC0EBB3.9030707@holidaymarketing.com>
[not found] ` <20021031120257.GF23217@redhat.com>
2002-11-05 1:17 ` Problem with Gdt driver under smp? Pedro Pla
[not found] ` <3DC71BF8.80100@holidaymarketing.com>
2002-11-05 3:34 ` Doug Ledford
2002-11-06 0:50 ` Pedro Pla [this message]
[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 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=3DC86740.3070804@holidaymarketing.com \
--to=pedropla@holidaymarketing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox