From: Michael Stone <mstone@mathom.us>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: scsi negotiation problem on aic79xx (39320A) in 2.6.14
Date: Fri, 24 Mar 2006 07:27:17 -0500 [thread overview]
Message-ID: <20060324122715.GG15140@mathom.us> (raw)
In-Reply-To: <1143139044.3415.26.camel@mulgrave.il.steeleye.com>
On Thu, Mar 23, 2006 at 01:37:23PM -0500, James Bottomley wrote:
>Well, since the driver works normally for most people, it sounds like
>there's some issue with this configuration. First of all, look
>in /sys/class/spi_transport/target2:0:0 and tell me what min_period,
>max_offset and max_width are. Then, if min_period is too high, echo
>12.5 to it and 1 to revalidate. Finally, see if you can set the period
>yourself using the period file. Also, what does /proc/scsi/aic79xx/2
>say? If none of that works, we can try debug the negotiation.
Thanks for the reply, it's finally working. The min_period was 6.5,
changing it to 12.5 & revalidating made it properly negotiate 160MB/s
instead of asynchronous. max_offset was 254 & max_width was 1. Is there
a way to make that permenant beside setting the proc entries on each
boot?
Mike Stone
next prev parent reply other threads:[~2006-03-24 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:45 scsi negotiation problem on aic79xx (39320A) in 2.6.14 Michael Stone
2006-03-23 18:09 ` Michael Stone
2006-03-23 18:37 ` James Bottomley
2006-03-24 12:27 ` Michael Stone [this message]
2006-03-24 12:30 ` Hannes Reinecke
2006-03-24 12:32 ` Michael Stone
2006-03-24 18:05 ` Stephen Degler
2006-03-24 13:50 ` James Bottomley
2006-05-20 5:10 ` Denny Page
2006-05-20 13:51 ` James Bottomley
2006-05-20 14:20 ` James Bottomley
2006-05-20 17:12 ` Denny Page
-- strict thread matches above, loose matches on Subject: below --
2005-11-16 21:09 Alan D. Brunelle
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=20060324122715.GG15140@mathom.us \
--to=mstone@mathom.us \
--cc=James.Bottomley@SteelEye.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;
as well as URLs for NNTP newsgroup(s).