From: William Thompson <wt@electro-mechanical.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.20 libata cdrom
Date: Mon, 30 Apr 2007 16:21:07 -0400 [thread overview]
Message-ID: <20070430202107.GF5942@electro-mechanical.com> (raw)
In-Reply-To: <4635C35D.1020807@gmail.com>
On Mon, Apr 30, 2007 at 12:22:21PM +0200, Tejun Heo wrote:
> William Thompson wrote:
> > I've been playing with libata on a few machines and I found that this machine
> > (An old Dell Dimension L866r) gives me this when it loads and does not give me
> > access to the cdrom. This is the only machine that I've tested that I know
> > for a fact cannot do DMA on the cdrom. I searched and noticed a similar
> > problem with 2.6.19-rc versions but I'm not sure if it's the same problem.
> >
> > dmesg output:
> > libata version 2.00 loaded.
> > ata_piix 0000:00:1f.1: version 2.00ac7
> > PCI: Setting latency timer of device 0000:00:1f.1 to 64
> > ata1: PATA max UDMA/66 cmd 0x1F0 ctl 0x3F6 bmdma 0xFFA0 irq 14
> > ata2: PATA max UDMA/66 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15
> > scsi0 : ata_piix
> > ata1.00: ATA-4, max UDMA/33, 10018890 sectors: LBA
> > ata1.00: ata1: dev 0 multi count 16
> > ata1.00: configured for UDMA/33
> > scsi1 : ata_piix
> > ata2.00: failed to IDENTIFY (I/O error, err_mask=0x1)
>
> Hmm... IDENTIFY failed on the second port. How reproducible is the
> problem? Every time? Does it work with the IDE driver? If so, please
> post the result of 'hdparm -I /dev/hdX'.
Reproducible? Everytime
Yes, it works fine with the IDE driver, so long as DMA is disabled.
hdparm -I:
/dev/hdc:
ATAPI CD-ROM, with removable media
Model Number: Lite-On LTN483S 48x Max
Serial Number:
Firmware Revision: PD02
Standards:
Used: ATAPI for CD-ROMs, SFF-8020i, r2.5
Supported: CD-ROM ATAPI-1
Configuration:
DRQ response: <=10ms with INTRQ
Packet size: 12 bytes
Capabilities:
LBA, IORDY(can be disabled)
DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
next prev parent reply other threads:[~2007-04-30 20:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 17:52 2.6.20 libata cdrom William Thompson
2007-04-30 10:22 ` Tejun Heo
2007-04-30 20:21 ` William Thompson [this message]
2007-05-01 4:32 ` Tejun Heo
2007-05-01 12:17 ` William Thompson
2007-05-01 13:04 ` Mark Lord
2007-05-01 13:18 ` William Thompson
2007-05-01 13:24 ` Mark Lord
2007-05-01 13:36 ` Alan Cox
2007-05-01 13:40 ` Tejun Heo
2007-05-01 13:51 ` Mark Lord
2007-05-01 14:19 ` Jeff Garzik
2007-05-01 14:23 ` Mark Lord
2007-05-01 14:28 ` Alan Cox
2007-05-01 17:21 ` William Thompson
2007-05-07 16:42 ` [PATCH] libata: fallback to the other IDENTIFY on device error Tejun Heo
2007-05-07 17:34 ` William Thompson
2007-05-07 18:05 ` William Thompson
2007-05-08 8:02 ` Tejun Heo
2007-05-10 0:08 ` Jeff Garzik
2007-05-11 12:35 ` [PATCH] libata: fallback to the other IDENTIFY on device error, take#2 Tejun Heo
2007-05-11 22:10 ` Jeff Garzik
2007-05-11 22:10 ` Jeff Garzik
2007-05-13 12:57 ` Tejun Heo
2007-05-13 16:13 ` Dave Jones
2007-05-13 17:50 ` Tejun Heo
2007-05-13 18:13 ` Dave Jones
2007-05-01 18:11 ` 2.6.20 libata cdrom Bartlomiej Zolnierkiewicz
2007-05-01 12:54 ` Mark Lord
2007-05-01 12:55 ` Mark Lord
2007-05-01 13:32 ` Tejun Heo
2007-05-01 13:41 ` Mark Lord
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=20070430202107.GF5942@electro-mechanical.com \
--to=wt@electro-mechanical.com \
--cc=htejun@gmail.com \
--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