From: Piotr Muszynski <u0295020@iwate-u.ac.jp>
To: linuxppc-dev@lists.linuxppc.org
Cc: Eric Guenterberg <mavpion@fire.csua.ucla.edu>,
Paul Mackerras <paulus@cs.anu.edu.au>
Subject: Re: Linux 2.2.1 Kernel scsi troubles
Date: Sat, 13 Feb 1999 21:54:21 +1000 [thread overview]
Message-ID: <36C567ED.F1982DB5@iwate-u.ac.jp> (raw)
I have the same problem (aborting MESH target) on my
7500/601/100MHz/64MB with 2 disks, linuxppc r4:
binutils-2.9.1-19a
modutils-2.1.121-1
egcs-1.1-1b
egcs-c++-1.1-1b
egcs-as-gcc-1.1-1b
egcs-fixes-1-1
glibc-0.961212-1o
glibc-devel-0.961212-1o
glibc-static-0.961212-1o
/dev/sda -- MacOS, with BootX/vmlinux (Fireball) --> this one's
aborted
/dev/sdb -- half MacOS, half Linux (IBM)
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: QUANTUM Model: FIREBALL1280S Rev: 630G
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: IBM Model: DCAS-32160 Rev: S65A
Type: Direct-Access ANSI SCSI revision: 02
Host: scsi0 Channel: 00 Id: 03 Lun: 00
Vendor: SONY Model: CD-ROM CDU-8005 Rev: 1.0j
Type: CD-ROM ANSI SCSI revision: 02
Is there anything I could help with?
BTW, vmlinux by Paul displayed only the welcome line. 2.2.1 boots
further (until failing on MESH) only after adding #ifdef __SMP__ /
#endif to arch/ppc/kernel/head.S (lines 1208/1212).
piotru
[[ 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. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-02-13 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-13 11:54 Piotr Muszynski [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-02-14 0:10 Linux 2.2.1 Kernel scsi troubles Aleksandar Kobilarov
1999-02-08 0:35 Eric Guenterberg
1999-02-01 23:53 Eric Guenterberg
1999-02-09 1:59 ` Paul Mackerras
1999-02-09 18:59 ` Eric Guenterberg
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=36C567ED.F1982DB5@iwate-u.ac.jp \
--to=u0295020@iwate-u.ac.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mavpion@fire.csua.ucla.edu \
--cc=paulus@cs.anu.edu.au \
/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).