From: Paul Mackerras <paulus@cs.anu.edu.au>
To: brad@pht.com
Cc: linuxppc-dev@lists.linuxppc.org, p1rabbit@halcyon.com
Subject: Re: 2.2.0pre2 SCSI problems, more (fwd)
Date: Tue, 5 Jan 1999 09:45:30 +1100 [thread overview]
Message-ID: <199901042245.JAA00826@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.3.95.990104100936.8496A-100000@pacific.pht.com> (message from Brad Midgley on Mon, 4 Jan 1999 10:18:56 -0700 (MST))
> that's the SAME drive that aborts for me in 2.2.0p4. mine is also
> connected to mesh. my 2.1.30 identifies it as:
>
> Vendor: QUANTUM Model: FIREBALL1280S Rev: 630G
>
> i don't see it blacklisted. something just makes it want to abort now. the
> scary thing about this is this drive ships STANDARD in 1gig 7500's. that's
> a lot of computers that suddenly can't run linux.
I have a 7600 but it no longer has this disk in it (it's in another
machine). Could somebody with a 7600 and this disk and the kernel
sources do the following: change drivers/scsi/mesh.c to #define
MESH_DBG and to initialize mesh_debug_targets to 1, and send me the
resulting debug log?
I may be able to take my fireball1280S out of the machine it's in if
we can't resolve the problem soon.
Paul.
[[ 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 prev parent reply other threads:[~1999-01-04 22:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-04 13:24 2.2.0pre2 SCSI problems, more (fwd) Geert Uytterhoeven
1999-01-04 17:18 ` Brad Midgley
1999-01-04 18:04 ` Peter Abrahamsen
1999-01-04 22:45 ` Paul Mackerras [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-01-05 2:41 Brad Midgley
1999-01-05 22:41 ` Paul Mackerras
1999-01-06 17:05 ` Brad Midgley
1999-01-13 2:53 ` Brad Midgley
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=199901042245.JAA00826@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=brad@pht.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=p1rabbit@halcyon.com \
/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).