From: Rene Herman <rene.herman@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: PATA -- pata_amd on 2.6.19 fails to IDENTIFY my DVD-ROM
Date: Wed, 20 Dec 2006 14:37:49 +0100 [thread overview]
Message-ID: <45893CAD.9050909@gmail.com> (raw)
Good day.
I just tried the PATA driver for my AMD756 chip. During boot, it hangs
for 3 minutes failing to identify my DVD-ROM (secondary slave) and does
not give me access to it after it timed out.
Situation is AMD756 (a UDMA66 chipset), both channels 80w cables:
1. Primary Master : UDMA133 disk, works fine
2. Primary Slave : Empty
3. Secondary Master : Plextor Premium CD-RW (UDMA33), works fine
4. Secondary Slave : Plextor PX-116A DVD-ROM (UDMA66), does not
All are using cable select and work fine with the old IDE driver and
also with an earlier version of the PATA code; I used 2.6.17-rc4-ide1
(which I see is still the latest standalone patch) without problems before.
The 2.6.17-rc4-ide pata_amd version was 0.1.7 and current is 0.2.4. Did
try a quick diff between them, but it seems the difference is mostly
infrastructural, so the problem is probably further on up.
Excerpt from boot-log (this takes 3 minutes):
===
pata_amd 0000:00:07.1: version 0.2.4
ata1: PATA max UDMA/66 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/66 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi0 : pata_amd
ata1.00: ATA-7, max UDMA/133, 240121728 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/66
scsi1 : pata_amd
ata2.00: ATAPI, max UDMA/33
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2: port is slow to respond, please be patient (Status 0xd8)
ata2: port failed to respond (30 secs, Status 0xd8)
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2: port is slow to respond, please be patient (Status 0xd8)
ata2: port failed to respond (30 secs, Status 0xd8)
ata2.01: qc timeout (cmd 0xa1)
ata2.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata2: failed to recover some devices, retrying in 5 secs
ata2: port is slow to respond, please be patient (Status 0xd8)
ata2: port failed to respond (30 secs, Status 0xd8)
ata2.00: configured for UDMA/33
scsi 0:0:0:0: Direct-Access ATA Maxtor 6Y120P0 YAR4 PQ: 0 ANSI: 5
SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 < sda5 sda6 sda7 sda8 > sda2 sda3 sda4
sda2: <minix: sda9 sda10 >
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: CD-ROM PLEXTOR CD-R PREMIUM 1.07 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 1:0:0:0: Attached scsi CD-ROM sr0
sr 1:0:0:0: Attached scsi generic sg1 type 5
===
By the way -- PATA interfaces (ata1, ata2) start counting at 1 while
their devices (.00, .01) start counting at 0 which sort of sucks. While
looking at "ata2.01" during boot (with the rest scrolled away) I thought
I was looking at secondary master initially. If they can still be named
ata0 and ata1, I'd consider that better.
Anyways, as said, all worked fine on 2.6.17-rc4-ide1 including I believe
with secondary master tuned to UDMA33 and slave to UDMA66 according to
their device capabilities.
Happy to provide more or other information if needed.
Rene.
next reply other threads:[~2006-12-20 13:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 13:37 Rene Herman [this message]
2006-12-27 7:19 ` PATA -- pata_amd on 2.6.19 fails to IDENTIFY my DVD-ROM Tejun Heo
2006-12-27 17:50 ` Rene Herman
2006-12-28 2:24 ` Tejun Heo
2007-01-01 22:46 ` 2.6.20-rc2+: CFQ halving disk throughput Rene Herman
2007-01-01 22:56 ` Rene Herman
2007-01-01 23:30 ` Linus Torvalds
2007-01-01 23:28 ` Mark Lord
2007-01-02 8:34 ` Jens Axboe
2007-01-02 15:01 ` Mark Lord
2007-01-02 16:53 ` Tejun Heo
2007-01-02 17:35 ` Mark Lord
2007-01-02 17:53 ` Tejun Heo
2007-01-02 18:10 ` Mark Lord
2007-01-02 21:50 ` ATA_12 support for libata/ATAPI devices Mark Lord
2007-01-02 17:09 ` 2.6.20-rc2+: CFQ halving disk throughput Jan Engelhardt
2007-01-02 5:36 ` Andrew Morton
2007-01-02 8:44 ` Jens Axboe
2007-01-02 10:24 ` Rene Herman
2007-01-02 11:57 ` Jens Axboe
2007-01-02 12:10 ` Jens Axboe
2007-01-02 15:12 ` Mark Lord
2007-01-02 15:14 ` Jens Axboe
2007-01-02 15:40 ` Mark Lord
2007-01-02 15:45 ` Jens Axboe
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=45893CAD.9050909@gmail.com \
--to=rene.herman@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.