public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Uprooter <uprooter@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Fusion MPT Ultra320 disks  detected as Ultra2
Date: Sun, 13 Dec 2009 12:50:42 +0100	[thread overview]
Message-ID: <1260705043.2709.285.camel@mulgrave.site> (raw)
In-Reply-To: <200912131258.27052.uprooter@gmail.com>

On Sun, 2009-12-13 at 12:58 +0200, Uprooter wrote:
> Hello James and thanks for trying to help.
> 
> Unfortunately changing min_period  didn't solve anything.
> # pwd
> /sys/class/spi_transport/target2:0:1
> 
> localhost target2:0:1 # echo 25 > min_period
> localhost target2:0:1 # echo 1 > revalidate
> I did it for both disks.
> #dmesg | tail -10
> target2:0:0: Beginning Domain Validation
>  target2:0:0: Domain Validation skipping write tests
>  target2:0:0: Ending Domain Validation
>  target2:0:0: Beginning Domain Validation
>  target2:0:0: Domain Validation skipping write tests
>  target2:0:0: Ending Domain Validation
>  target2:0:1: Beginning Domain Validation
>  target2:0:1: Domain Validation skipping write tests
>  target2:0:1: Ending Domain Validation
>  target2:0:1: Beginning Domain Validation
>  target2:0:1: Domain Validation skipping write tests
>  target2:0:1: Ending Domain Validation
> 
> # cat min_period
> 25
> # cat period
> 50

OK, so I'd suspect a cabling problem.  50ns is the minimum period for a
single ended bus.  You have to move to LVD to get anything beyond.  I'd
say something in your SCSI cable chain is keeping the bus SE.

James



  reply	other threads:[~2009-12-13 11:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-12 22:38 Fusion MPT Ultra320 disks detected as Ultra2 uprooter
2009-12-13  9:29 ` James Bottomley
2009-12-13 10:58   ` Uprooter
2009-12-13 11:50     ` James Bottomley [this message]
2009-12-14 19:58       ` Uprooter

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=1260705043.2709.285.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=uprooter@gmail.com \
    /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