From: Albert Lee <albertcc@tw.ibm.com>
To: matthieu castet <castet.matthieu@free.fr>
Cc: Jeff Garzik <jeff@garzik.org>,
akpm@osdl.org, alan@lxorguk.ukuu.org.uk,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
B.Zolnierkiewicz@elka.pw.edu.pl, htejun@gmail.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
Unicorn Chang <uchang@tw.ibm.com>, Doug Maxey <dwm@maxeymade.com>
Subject: Re: + via-pata-controller-xfer-fixes.patch added to -mm tree
Date: Fri, 30 Jun 2006 15:09:21 +0800 [thread overview]
Message-ID: <44A4CE21.30009@tw.ibm.com> (raw)
In-Reply-To: <449E5445.60008@free.fr>
matthieu castet wrote:
> Jeff Garzik wrote:
>
>> Data point #3 (or #0...):
>>
>> This appears to be a _device_ that sends its interrupt early.
Hi,
I've tested the 4KUS CDR-6S48 drive + Promise pdc20275 controller
with current libata upstream (to be 2.6.18. I guess current upstream doesn't
have the via-pata-controller-xfer-fixes.patch). However, cannot reproduce
the early interrupt problem on my machine.
>>
>> If that is the case, the device may appear on any controller, not just
>> VIA, and we would have to handle it globally via a device special-case
>> in libata-core.
>>
>
> For the record, the cdrom writer that need this quirk on pata via, works
> on pata sil680.
> But 3 microsecond is very short, and the problem could be hidden by the
> controller, or other stuffs.
>
>
If it is the problem of the specific ATAPI device, all controllers
should be affected, not only VIA. So, strange not seeing the problem on
Promise.
Could you please test the current libata-upstream tree and
turn on ATA_DEBUG and ATA_VERBOSE_DEBUG in include/linux/libata.h.
If possible, could you also submit the libata log related to the
early/lost irq.
(Heard about the ATAPI early interrupt problem, but never had chance to see
how libata behaves with such device. Really curious about this problem.)
Thanks,
Albert
---
boot dmesg of the CDR-6S48 on my box.
xfer mode set to UDMA/33 without problem.
pata_pdc2027x 0000:02:05.0: version 0.74-ac3
ACPI: PCI Interrupt 0000:02:05.0[A] -> Link [LNK1] -> GSI 10 (level, low) -> IRQ 10
pata_pdc2027x 0000:02:05.0: PLL input clock 16740 kHz
ata3: PATA max UDMA/133 cmd 0xE09E17C0 ctl 0xE09E1FDA bmdma 0xE09E1000 irq 10
ata4: PATA max UDMA/133 cmd 0xE09E15C0 ctl 0xE09E1DDA bmdma 0xE09E1008 irq 10
scsi2 : pata_pdc2027x
ata3.00: configured for UDMA/33
ata3.01: configured for UDMA/33
scsi3 : pata_pdc2027x
ata4.00: configured for UDMA/33
Vendor: LITE-ON Model: CD-RW SOHR-5238S Rev: 4S07
Type: CD-ROM ANSI SCSI revision: 05
Vendor: HL-DT-ST Model: DVDRAM GSA-4163B Rev: A101
Type: CD-ROM ANSI SCSI revision: 05
Vendor: CD-RW Model: CDR-6S48 Rev: 2SG1
Type: CD-ROM ANSI SCSI revision: 05
sr0: scsi3-mmc drive: 93x/52x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 2:0:0:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray
sr 2:0:1:0: Attached scsi CD-ROM sr1
sr2: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
sr 3:0:0:0: Attached scsi CD-ROM sr2
next prev parent reply other threads:[~2006-06-30 7:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606242214.k5OMEHCU005963@shell0.pdx.osdl.net>
2006-06-24 22:36 ` + via-pata-controller-xfer-fixes.patch added to -mm tree Jeff Garzik
2006-06-24 22:43 ` Jeff Garzik
2006-06-25 9:15 ` matthieu castet
2006-06-30 7:09 ` Albert Lee [this message]
2006-06-30 7:55 ` castet.matthieu
2006-06-30 8:26 ` Albert Lee
2006-07-02 8:36 ` matthieu castet
2006-07-02 10:32 ` matthieu castet
2006-07-02 12:46 ` Albert Lee
2006-07-02 13:06 ` matthieu castet
2006-07-02 14:17 ` Albert Lee
2006-06-30 10:03 ` Alan Cox
2006-07-02 13:59 ` Albert Lee
2006-06-24 23:17 ` Alan Cox
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=44A4CE21.30009@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=castet.matthieu@free.fr \
--cc=dwm@maxeymade.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uchang@tw.ibm.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;
as well as URLs for NNTP newsgroup(s).