From: James Bottomley <James.Bottomley@SteelEye.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] linux-2.6.10-pa1 panic on C360 in SCSI driver
Date: Wed, 29 Dec 2004 16:37:52 -0600 [thread overview]
Message-ID: <1104359873.5298.25.camel@mulgrave> (raw)
In-Reply-To: <200412291649.29411.vapier@gentoo.org>
On Wed, 2004-12-29 at 16:49 -0500, Mike Frysinger wrote:
> Current DV: sense = 70 5
> ASC=24 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x18 0xff 0xff 0xff
> 0xff 0x24 0x00 0x00 0xc0 0x00 0x08 0x00 0xff 0xff 0xff 0xff 0xff 0x00
> 0x00 0x00 0x00 0x00 0x00 0x00 0x00
This means invalid request, illegal field in cdb and identifies the 8th
field as the illegal one (that's the length of the write buffer
request). So the thing told us that it supports a write buffer of
length 255 and then tells us our request is too long when we try to
write 255 bytes ... that seems about par for the course for this drive.
Could you try this patch, it halves the write buffer length. That
should tell us if this drive actually has one and just lies about the
length, or lies about having one altogether.
James
===== drivers/scsi/scsi_transport_spi.c 1.21 vs edited =====
--- 1.21/drivers/scsi/scsi_transport_spi.c 2004-12-06 14:51:40 -06:00
+++ edited/drivers/scsi/scsi_transport_spi.c 2004-12-29 16:36:21 -06:00
@@ -637,6 +639,8 @@
len = 0;
if (sdev->ppr)
len = spi_dv_device_get_echo_buffer(sreq, buffer);
+
+ len = len/2;
if (len == 0) {
SPI_PRINTK(sdev->sdev_target, KERN_INFO, "Domain Validation skipping write tests\n");
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-12-29 22:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 10:04 [parisc-linux] linux-2.6.10-pa1 panic on C360 in SCSI driver Mike Frysinger
2004-12-26 17:37 ` Matthew Wilcox
2004-12-26 17:42 ` Kyle McMartin
2004-12-27 0:26 ` Joel Soete
2004-12-27 0:49 ` Matthew Wilcox
2004-12-28 1:45 ` Mike Frysinger
2004-12-28 3:30 ` James Bottomley
2004-12-28 3:49 ` Mike Frysinger
2004-12-28 3:35 ` Matthew Wilcox
2004-12-28 4:01 ` Mike Frysinger
2004-12-29 3:43 ` Matthew Wilcox
2004-12-29 19:19 ` Mike Frysinger
2004-12-29 21:28 ` James Bottomley
2004-12-29 21:49 ` Mike Frysinger
2004-12-29 21:54 ` Mike Frysinger
2004-12-29 22:03 ` Matthew Wilcox
2004-12-29 22:37 ` James Bottomley [this message]
2004-12-29 23:16 ` Mike Frysinger
2004-12-30 17:04 ` James Bottomley
2004-12-30 20:43 ` Mike Frysinger
[not found] ` <200501011839.13090.vapier@gentoo.org>
2005-01-02 0:58 ` Matthew Wilcox
2005-01-04 6:01 ` Randolph Chung
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=1104359873.5298.25.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=parisc-linux@parisc-linux.org \
--cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.