All of lore.kernel.org
 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: Mon, 27 Dec 2004 21:30:20 -0600	[thread overview]
Message-ID: <1104204620.7447.33.camel@mulgrave> (raw)
In-Reply-To: <200412272045.34143.vapier@gentoo.org>

On Mon, 2004-12-27 at 20:45 -0500, Mike Frysinger wrote:
> it didnt panic, but it looks like the kernel went into an infinite loop ...

Well, I think that's the fault of your drive:

> sym0:9:ppr msgout: 1-6-4-c-0-10-1-0.

This is where the 875 offers an offset of 16 at FAST-20 which is the
best it can do.

> sym0:9:ppr msgin: 1-6-4-a-0-10-1-0.

This is where your WD says I accept your offer at offset 16 and FAST-40
(which is beyond the 875's capabilities).

This is illegal under the SCSI spec (you can only accept at a period of
greater than the offer, not less than).  The patch I gave you spots the
problem and rejects the bogus offer.  Unfortunately, apparently now the
drive throws a wobbly and refuses to talk any more.

The question is how we coax it to negotiate within the rules...It's
possible it would work correctly if the negotiation used WDTR and SDTR
instead of PPR, so could you try the attached hack.

James

===== sym_hipd.c 1.22 vs edited =====
--- 1.22/drivers/scsi/sym53c8xx_2/sym_hipd.c	2004-10-24 11:08:18 -05:00
+++ edited/sym_hipd.c	2004-12-27 21:28:35 -06:00
@@ -1538,7 +1538,7 @@
 	/*
 	 *  negotiate using PPR ?
 	 */
-	if (scsi_device_dt(sdev)) {
+	if (0 && scsi_device_dt(sdev)) {
 		nego = NS_PPR;
 	} else {
 		/*




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

  reply	other threads:[~2004-12-28  3:30 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 [this message]
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
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=1104204620.7447.33.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.