From: "D. Lance Robinson" <lancer@airways.com>
To: linux-raid <linux-raid@vger.rutgers.edu>,
linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Memory buffer corruption with Raid on PPC
Date: Tue, 13 Apr 1999 17:42:03 -0700 [thread overview]
Message-ID: <3713E45B.60335A75@airways.com> (raw)
I have linux 2.2.3 with raid014519990309.. patch.
On a PPC (Mac G3) system, I am getting what seems to be memory buffer
courruption when using raidstart. The same kernel source run with i386
architecture seems to be fine.
To show the problem, I do something like the following...
# cd ~me
# gcc source_a.c
# raidstart /dev/md0 ; gcc source_a.c
# raidstop /dev/md0 ; gcc source_a.c
# raidstart /dev/md0 ; gcc source_a.c
# raidstop /dev/md0 ; gcc source_a.c
# raidstart /dev/md0 ; gcc source_a.c
# raidstop /dev/md0 ; gcc source_a.c
# raidstart /dev/md0 ; gcc source_a.c
# raidstop /dev/md0 ; gcc source_a.c
Usually doing this will cause the compile to have a problem. Such as:
"Illegal Instruction", or some compile error. This indicates some sort
of memory buffer corruption since the gcc is all done out of memory.
The problem seems to be in the raidstart area. It shows up after
starting the array, but once the array is started (and passes the gcc
test,) it works fine.
Any ideas ?
Thanks, <>< Lance.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
reply other threads:[~1999-04-14 0:42 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=3713E45B.60335A75@airways.com \
--to=lancer@airways.com \
--cc=linux-raid@vger.rutgers.edu \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).