linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Tejun Heo <htejun@gmail.com>,
	jeff@garzik.org, linux-ide@vger.kernel.org,
	linux-kernel@vger.kernel.org, garyhade@us.ibm.com
Subject: Re: libata reset-seq merge broke sata_sil on sh
Date: Wed, 16 May 2007 09:30:02 +0900	[thread overview]
Message-ID: <20070516003002.GA18863@linux-sh.org> (raw)
In-Reply-To: <20070512034928.GB29259@linux-sh.org>

On Sat, May 12, 2007 at 12:49:28PM +0900, Paul Mundt wrote:
> On Fri, May 11, 2007 at 11:39:20AM +0200, Tejun Heo wrote:
> > Paul Mundt wrote:
> > > Bumping the hardreset delay up does indeed fix it, I've had to bump it up
> > > to 1200 before it started working (at 600 it still fails):
> > > 
> > > [    0.967379] scsi0 : sata_sil
> > > [    0.970425] scsi1 : sata_sil
> > > [    0.973298] ata1: SATA max UDMA/100 cmd 0xfd000280 ctl 0xfd00028a bmdma 0xfd000200 irq 0
> > > [    0.981331] ata2: SATA max UDMA/100 cmd 0xfd0002c0 ctl 0xfd0002ca bmdma 0xfd000208 irq 0
> > > [    1.299353] ata1: device not ready (errno=-19), forcing hardreset
> > > [    2.817893] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> > > [    2.826284] ata1.00: ata_hpa_resize 1: sectors = 39070080, hpa_sectors = 39070080
> > > [    2.831052] ata1.00: ATA-5: HHD424020F7SV00, 00MLA0A5, max UDMA/100
> > > [    2.837548] ata1.00: 39070080 sectors, multi 0: LBA
> > > [    2.842702] ata1.00: applying bridge limits
> > > [    2.854162] ata1.00: ata_hpa_resize 1: sectors = 39070080, hpa_sectors = 39070080
> > > [    2.858938] ata1.00: configured for UDMA/100
> > > [    3.172602] ata2: SATA link down (SStatus 0 SControl 310)
> > > [    3.175736] scsi 0:0:0:0: Direct-Access     ATA      HHD424020F7SV00  00ML PQ: 0 ANSI: 5
> > > 
> > > I'm not sure if it matters or not, but this is an iVDR drive, so that
> > > might also have additional implications.
> > 
> > Don't have the flimsiest idea what an iVDR drive is but I take it that
> > it's some sort of special purpose thing.  :-)
> > 
> http://www.ivdr.org
> 
> The GoVault appears to be a similar device, in that they're both
> removeable cartridges.
> 
> > Gary, IIRC, the requirement for GoVault was 3secs, right?  Paul, can you
> > try to estimate the minimum required delay?  Please go down by 100ms and
> > report where it breaks.
> > 
> 800ms was the lowest it would work at, 700ms still breaks.

Ping?

  reply	other threads:[~2007-05-16  0:30 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  7:20 libata reset-seq merge broke sata_sil on sh Paul Mundt
2007-05-10 11:28 ` Tejun Heo
2007-05-10 11:53   ` Tejun Heo
2007-05-10 12:46   ` Paul Mundt
2007-05-10 13:08     ` Tejun Heo
2007-05-11  0:52       ` Paul Mundt
2007-05-11  9:39         ` Tejun Heo
2007-05-12  3:49           ` Paul Mundt
2007-05-16  0:30             ` Paul Mundt [this message]
2007-05-16 16:44               ` [PATCH] libata: implement ata_wait_after_reset() Tejun Heo
2007-05-17  0:50                 ` Paul Mundt
2007-05-17  0:59                 ` Paul Mundt
2007-05-19 15:54                 ` Indan Zupancic
2007-05-19 18:23                   ` Tejun Heo
2007-05-19 22:54                     ` Indan Zupancic
2007-05-20  9:50                       ` Tejun Heo
2007-05-20 13:26                         ` Indan Zupancic
2007-05-20 17:09                           ` Tejun Heo
2007-05-20 19:35                             ` Indan Zupancic
2007-05-19 16:39                 ` Indan Zupancic
2007-05-19 18:43                   ` Tejun Heo
2007-05-19 19:04                     ` Tejun Heo
2007-05-19 22:33                       ` sd_resume redundant? [was: [PATCH] libata: implement ata_wait_after_reset()] Indan Zupancic
2007-05-20  9:54                         ` Tejun Heo
2007-05-20 14:27                           ` Indan Zupancic
2007-05-20 17:17                             ` Tejun Heo
2007-05-20 19:47                               ` Indan Zupancic
2007-05-21  6:02                       ` [PATCH] libata: implement ata_wait_after_reset() Paul Mundt
2007-05-29  1:31                 ` Jeff Garzik
2007-05-29  7:33                   ` Tejun Heo

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=20070516003002.GA18863@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=garyhade@us.ibm.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).