From: James Bottomley <James.Bottomley@SteelEye.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Graham Knap <graham.knap@rogers.com>, Horms <horms@debian.org>,
338089@bugs.debian.org, linux-scsi@vger.kernel.org
Subject: Bug#338089: New aic7xxx driver fails spectacularly on 2940UW
Date: Sun, 13 Nov 2005 11:46:45 -0600 [thread overview]
Message-ID: <1131904005.3291.5.camel@mulgrave> (raw)
In-Reply-To: <43777ACC.8070503@redhat.com>
On Sun, 2005-11-13 at 12:41 -0500, Doug Ledford wrote:
> If the drive is unaccessible after the DV failure, even on a warm reboot
> (which includes a SCSI bus reset), then the drive is flat hung.
> Something done in the current code is breaking it. Can you get a boot
> with DV turned off and capture the log messages and post them here
> please? You already said it didn't help with the problem, but I'd like
> to see the failure scenario with it off, that might help determine the
> true root cause of the issue.
Yes, you're right ... the sequencer code seems to identify the
WRITE_BUFFER as the failing command. Can you try with the attached
patch, which will force DV to ignore the echo buffer write tests?
Thanks,
James
diff --git a/drivers/scsi/scsi_transport_spi.c b/drivers/scsi/scsi_transport_spi.c
--- a/drivers/scsi/scsi_transport_spi.c
+++ b/drivers/scsi/scsi_transport_spi.c
@@ -816,8 +816,10 @@ spi_dv_device_internal(struct scsi_devic
* do the SPI pattern write tests */
len = 0;
+#if 0
if (scsi_device_dt(sdev))
len = spi_dv_device_get_echo_buffer(sdev, buffer);
+#endif
retry:
next prev parent reply other threads:[~2005-11-13 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051108024523.35622.qmail@web88006.mail.re2.yahoo.com>
2005-11-08 3:31 ` Bug#338089: New aic7xxx driver fails spectacularly on 2940UW Horms
2005-11-08 14:10 ` James Bottomley
2005-11-09 1:47 ` Graham Knap
2005-11-13 4:16 ` James Bottomley
2005-11-13 16:47 ` Graham Knap
2005-11-13 17:41 ` Doug Ledford
2005-11-13 17:46 ` James Bottomley [this message]
2005-11-15 0:45 ` Graham Knap
2005-11-16 2:37 ` Horms
2005-11-13 18:03 ` Graham Knap
2005-11-13 18:21 ` James Bottomley
2005-11-13 19:42 ` Doug Ledford
2005-11-13 21:51 ` James Bottomley
2005-11-14 10:15 emmanuel.fuste
-- strict thread matches above, loose matches on Subject: below --
2005-11-21 2:21 Graham Knap
2005-11-28 21:41 ` James Bottomley
2005-11-28 22:26 ` Doug Ledford
2005-12-05 1:49 ` Graham Knap
2005-12-12 17:53 ` Florian Ernst
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=1131904005.3291.5.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=338089@bugs.debian.org \
--cc=dledford@redhat.com \
--cc=graham.knap@rogers.com \
--cc=horms@debian.org \
--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 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.