public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: matthieu castet <castet.matthieu@free.fr>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: libata PATA patch for 2.6.16-rc5
Date: Mon, 13 Mar 2006 20:52:49 +0100	[thread overview]
Message-ID: <4415CD91.5050200@free.fr> (raw)
In-Reply-To: <44061F96.80900@free.fr>

Hi,

matthieu castet wrote:
> Hi Alan
> 
> Alan Cox wrote:
> 
>> On Maw, 2006-02-28 at 23:36 +0100, matthieu castet wrote:
>>
>>> for the SIL680 I have a 100Mhz clock instead of a 133Mhz with ide/pci 
>>> driver [1]
>>
>>
>>
>> Fixed (missing break in switch)
>>
>>
>>> The ATAPI doesn't seem to work fine with VIA.
>>
>>
>>
>> Still investigating
>>
> If it can help you, I attach a log with debug enabled.
> 
Ok, I think I have a hint.

The drive that is failling is the secondary slave [1].
When I try to change xfermode with hdparm -X, it take some times (10 s) 
and I found an error in the kernel log.
But even with that error, it seem the xfermode is changed.

What happen with libata if we lose an interrupt ?


Matthieu




[1]
/dev/hdd:

ATAPI CD-ROM, with removable media
         Model Number:       CD-RW   CDR-6S48
         Serial Number:
         Firmware Revision:  SSG5
Standards:
         Used: ATAPI for CD-ROMs, SFF-8020i, r2.5
         Supported: CD-ROM ATAPI-2
Configuration:
         DRQ response: 50us.
         Packet size: 12 bytes
Capabilities:
         LBA, IORDY(cannot be disabled)
         DMA: mdma0 mdma1 mdma2 udma0 udma1 *udma2
              Cycle time: min=120ns recommended=120ns
         PIO: pio0 pio1 pio2 pio3 pio4
              Cycle time: no flow control=227ns  IORDY flow control=120ns

[2]
hdd: lost interrupt
hdd: CHECK for good STATUS

  parent reply	other threads:[~2006-03-13 19:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 15:32 libata PATA patch for 2.6.16-rc5 Alan Cox
2006-02-27 17:55 ` Mathieu Chouquet-Stringer
2006-02-28  0:19   ` Alan Cox
2006-02-28 12:12     ` Krzysztof Halasa
2006-02-28 13:32       ` Alan Cox
2006-02-28 13:34       ` Alan Cox
2006-02-27 20:46 ` Matthieu CASTET
     [not found]   ` <1141086963.3089.26.camel@localhost.localdomain>
2006-03-05 18:49     ` matthieu castet
     [not found]     ` <4404D05C.8070407@free.fr>
     [not found]       ` <1141231247.23170.0.camel@localhost.localdomain>
     [not found]         ` <44061F96.80900@free.fr>
2006-03-13 19:52           ` matthieu castet [this message]
2006-02-28  0:30 ` Christian Trefzer
2006-02-28  9:49   ` Alan Cox
2006-02-28 10:05     ` Christian Trefzer
2006-02-28 10:20     ` [PATCH] Add pata_pdc_2ß27x to Kconfig and Makefile (was: Re: libata PATA patch for 2.6.16-rc5) Christian Trefzer
2006-02-28 10:41       ` Christian Trefzer
2006-02-28 10:58         ` Christian Trefzer
2008-10-14  1:28         ` [PATCH] Add pata_pdc_2ß27x to Kconfig and Makefile Tejun Heo
2008-10-14  8:01           ` Christian Trefzer
2008-10-14  8:09             ` Tejun Heo
2006-02-28 22:32 ` libata PATA patch for 2.6.16-rc5 Francesco Biscani
2006-02-28 23:06 ` Francesco Biscani
  -- strict thread matches above, loose matches on Subject: below --
2006-02-28 23:42 Chris Boot

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=4415CD91.5050200@free.fr \
    --to=castet.matthieu@free.fr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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