Linux PARISC architecture development
 help / color / mirror / Atom feed
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 15:28:29 -0600	[thread overview]
Message-ID: <1104355710.5298.16.camel@mulgrave> (raw)
In-Reply-To: <200412291419.36568.vapier@gentoo.org>

On Wed, 2004-12-29 at 14:19 -0500, Mike Frysinger wrote:
>  target0:0:9: Write Buffer failure 8000002
>  target0:0:9: Domain Validation detected failure, dropping back

So now I'd like to see what this is ... it causes your nice ultra3 drive
only to work at async speeds (about 4MB/s).  Can you apply the patch and
send back the output?

Thanks,

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 15:18:12 -06:00
@@ -33,6 +33,7 @@
 #include <scsi/scsi_request.h>
 #include <scsi/scsi_transport.h>
 #include <scsi/scsi_transport_spi.h>
+#include <scsi/scsi_dbg.h>
 
 #define SPI_PRINTK(x, l, f, a...)	dev_printk(l, &(x)->dev, f , ##a)
 
@@ -440,6 +441,7 @@
 		if(sreq->sr_result || !scsi_device_online(sdev)) {
 			scsi_device_set_state(sdev, SDEV_QUIESCE);
 			SPI_PRINTK(sdev->sdev_target, KERN_ERR, "Write Buffer failure %x\n", sreq->sr_result);
+			scsi_print_req_sense("DV", sreq);
 			return 0;
 		}
 
@@ -642,6 +644,7 @@
 		SPI_PRINTK(sdev->sdev_target, KERN_INFO, "Domain Validation skipping write tests\n");
 		return;
 	}
+	SPI_PRINTK(sdev->sdev_target, KERN_INFO, "Domain Validation write buffer length %d\n", len);
 	if (len > SPI_MAX_ECHO_BUFFER_SIZE) {
 		SPI_PRINTK(sdev->sdev_target, KERN_WARNING, "Echo buffer size %d is too big, trimming to %d\n", len, SPI_MAX_ECHO_BUFFER_SIZE);
 		len = SPI_MAX_ECHO_BUFFER_SIZE;


_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2004-12-29 21:28 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 [this message]
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
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=1104355710.5298.16.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox