From: laures@esiea.fr
To: linuxppc-dev@lists.linuxppc.org
Subject: Initio miles tests :-(
Date: Mon, 24 May 1999 17:14:49 +0200 (CEST) [thread overview]
Message-ID: <199905241534.KAA24850@lists.linuxppc.org> (raw)
OK so far it's not really good...
Let's begin by what's working...
mke2fs /dev/disk-on-miles is ok
fsck too
mount -t hfs
mount -t ext2 as well
cp a 2M file (kernel) ok, not corrupted when cp back to mesh (gzip'ed
and de-gzip'ed succesfully)
umount ok after cping this small file.
Now what doesn't work...
pdisk /dev/disk-on-miles destroy the partition map if re-written, even
just renaming a partition
mke2fs -c gives a kernel panic ("kernel stack overflow")
cp /usr/src/linux/* /mnt/disk-on miles/ goes ok few... and then I got
this kind of lines (several times):
scsi: aborting command due to timeout: pid 20175, scsi1, channel 0,
id5, lun0, Write (6) 04 9C 45 80 00
SCSI bus is being reset for host 1 channel 0
the kernel "panics" soon after
I got his behaviour also when cping 10 megs of files (/boot/*) and
issuing umount when done.
Finally hdparm -Tt gives a kernel panic, or smth just under
Each time the ext2 partition is completely screwed, I must reformat to
continue tests, the hfs is screwed once over 2.
I think I will go on with a ramdisk !
So I guess the patch wasn't enough...
Any way of investigation someone ?
--
Guillaume Laurès - student @ ESIEA (www.esiea.fr)
[[ 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. ]]
next reply other threads:[~1999-05-24 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-24 15:14 laures [this message]
1999-05-24 19:28 ` Initio miles tests :-( Tom Rini
1999-05-24 22:02 ` laures
[not found] <199905242203.SAA10401@mail.ntplx.net>
1999-05-24 22:10 ` Tom Rini
1999-05-25 9:50 ` Kostas Gewrgiou
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=199905241534.KAA24850@lists.linuxppc.org \
--to=laures@esiea.fr \
--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).