From: rob@osinvestor.com (Rob Radez)
To: linux-scsi@vger.kernel.org
Subject: [rob@osinvestor.com: Re: SCSI broken]
Date: Wed, 5 Mar 2003 09:43:37 -0500 [thread overview]
Message-ID: <20030305144336.GA13722@osinvestor.com> (raw)
[forgot to cc: linux-scsi@]
Also forgot to mention that 2.5.64 hangs in the same spot as 2.5.63.
----- Forwarded message from Rob Radez <rob@osinvestor.com> -----
From: rob@osinvestor.com (Rob Radez)
To: David van Hoose <davidvh@cox.net>
Cc: linux-kernel@vger.kernel.org
Date: Wed, 5 Mar 2003 00:44:57 -0500
Subject: Re: SCSI broken
On Tue, Mar 04, 2003 at 11:42:41PM -0600, David van Hoose wrote:
> Kernels 2.5.63 and 2.5.64 lock up when displaying the information for my
> ZipDrive during SCSI probe. Attached is my .config for 2.5.64.
I suspect I'm seeing something similar. On SPARC, I'm getting a hang
after displaying the information for my SCSI CD-ROM drive.
scsi0 : Sparc ESP100A-FAST
Vendor: SEAGATE Model: ST31200W SUN1.05 Rev: 8724
Type: Direct-Access ANSI SCSI revision: 02
Vendor: SEAGATE Model: ST32155W SUN2.1G Rev: 8456
Type: Direct-Access ANSI SCSI revision: 02
Vendor: TOSHIBA Model: XM-4101TASUNSLCD Rev: 1755
Type: CD-ROM ANSI SCSI revision: 02
<hang>
.config available on request. Worked fine in 2.5.62, hangs in 2.5.63.
Reverting the scsi changes listed at
http://osinvestor.com/sparc/patch/2.5.63-revertscsi.diff allows 2.5.63
to boot.
Regards,
Rob Radez
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
----- End forwarded message -----
next reply other threads:[~2003-03-05 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 14:43 Rob Radez [this message]
2003-03-05 18:03 ` [rob@osinvestor.com: Re: SCSI broken] Mike Anderson
2003-03-05 18:56 ` Mike Anderson
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=20030305144336.GA13722@osinvestor.com \
--to=rob@osinvestor.com \
--cc=linux-scsi@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