Skip to contentSkip to conversation

Bug or my setup?

DISCUSSION Citroklar 3 participants 4 messages Oct 28, 2004 – Oct 29, 2004 libata

lore
Share & tools
lore

Citroklar

author
#0 lore raw

Hi there,

I posted that before, but I didn't get an answer, so I post again, this time with a more recent kernel (2.6.10-rc1-bk6). I wonder if this is a bug or just my setup.

I have a dvd writer (parallel ata) connected to a PATA/SATA converter which in turn is connected to a Silicon Image 3114 PCI Card.

Now, funny thing is, the device gets detected somehow, but no /dev/sd* is attached to it!

this is the dmesg output that troubles me:

ata1: SATA max UDMA/100 cmd 0xE881AC80 ctl 0xE881AC8A bmdma 0xE881AC00 irq 19
ata2: SATA max UDMA/100 cmd 0xE881ACC0 ctl 0xE881ACCA bmdma 0xE881AC08 irq 19
ata3: SATA max UDMA/100 cmd 0xE881AE80 ctl 0xE881AE8A bmdma 0xE881AE00 irq 19
ata4: SATA max UDMA/100 cmd 0xE881AEC0 ctl 0xE881AECA bmdma 0xE881AE08 irq 19
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata2: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_sil
ata3: dev 0 cfg 49:0f00 82:421c 83:0000 84:0000 85:0000 86:0000 87:0000 88:0007
ata3: dev 0 ATAPI, max UDMA/33
ata3: dev 0 configured for UDMA/33
scsi2 : sata_sil
ata4: no device found (phy stat 00000000)
scsi3 : sata_sil
Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB) SCSI device sda: drive cache: write back
sda: sda1 sda2 < sda5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 320173056 512-byte hdwr sectors (163929 MB) SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2 < sdb5 >
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0

And that's it. no attaching scsi cdrom drive at scsi2. :(

Is it a bug or is it a feature that will come later or is it just my setup?

thanks,
Tobias Ottmar

#1 lore raw
Quoted 57 lines · Citroklar

Hi there,

I posted that before, but I didn't get an answer, so I post again, this time with a more recent kernel (2.6.10-rc1-bk6). I wonder if this is a bug or just my setup.

I have a dvd writer (parallel ata) connected to a PATA/SATA converter which in turn is connected to a Silicon Image 3114 PCI Card.

Now, funny thing is, the device gets detected somehow, but no /dev/sd* is attached to it!

this is the dmesg output that troubles me:

ata1: SATA max UDMA/100 cmd 0xE881AC80 ctl 0xE881AC8A bmdma 0xE881AC00 irq 19
ata2: SATA max UDMA/100 cmd 0xE881ACC0 ctl 0xE881ACCA bmdma 0xE881AC08 irq 19
ata3: SATA max UDMA/100 cmd 0xE881AE80 ctl 0xE881AE8A bmdma 0xE881AE00 irq 19
ata4: SATA max UDMA/100 cmd 0xE881AEC0 ctl 0xE881AECA bmdma 0xE881AE08 irq 19
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata2: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_sil
ata3: dev 0 cfg 49:0f00 82:421c 83:0000 84:0000 85:0000 86:0000 87:0000 88:0007
ata3: dev 0 ATAPI, max UDMA/33
ata3: dev 0 configured for UDMA/33
scsi2 : sata_sil
ata4: no device found (phy stat 00000000)
scsi3 : sata_sil
Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB) SCSI device sda: drive cache: write back
sda: sda1 sda2 < sda5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 320173056 512-byte hdwr sectors (163929 MB) SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2 < sdb5 >
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0

And that's it. no attaching scsi cdrom drive at scsi2. :(

Is it a bug or is it a feature that will come later or is it just my setup?

Quoted 8 lines

thanks,
Tobias Ottmar

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi Tobias

The support for ATAPI over SATA is there, however since it is still quite buggy, it is disabled by default.
You can enable the support by replacing "#undef ATA_ENABLE_ATAPI" in /include/linux/libata.h in you kernel source, with "#define ATA_ENABLE_ATAPI"
Personally I've noticed that since linux-2.6.9-bk3 it have been working without almost stalling the kernel.
Be aware though, that the support is apparently still somewhat limited. At least just about everything but ordinary mounting and handling of CD-ROM's on my DVD (also on SiI3112) causes the applications to stall until a couple of timeouts have occured. So no DVD viewing and no burning, but ordinary CD-ROM handling is working.

--
Peter Christensen

#2 lore raw
Quoted 69 lines · Peter Christensen
Quoted 57 lines · Citroklar

Hi there,

I posted that before, but I didn't get an answer, so I post again, this time with a more recent kernel (2.6.10-rc1-bk6). I wonder if this is a bug or just my setup.

I have a dvd writer (parallel ata) connected to a PATA/SATA converter which in turn is connected to a Silicon Image 3114 PCI Card.

Now, funny thing is, the device gets detected somehow, but no /dev/sd* is attached to it!

this is the dmesg output that troubles me:

ata1: SATA max UDMA/100 cmd 0xE881AC80 ctl 0xE881AC8A bmdma 0xE881AC00 irq 19
ata2: SATA max UDMA/100 cmd 0xE881ACC0 ctl 0xE881ACCA bmdma 0xE881AC08 irq 19
ata3: SATA max UDMA/100 cmd 0xE881AE80 ctl 0xE881AE8A bmdma 0xE881AE00 irq 19
ata4: SATA max UDMA/100 cmd 0xE881AEC0 ctl 0xE881AECA bmdma 0xE881AE08 irq 19
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4003 85:7c69 86:3e01 87:4003 88:207f
ata2: dev 0 ATA, max UDMA/133, 320173056 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_sil
ata3: dev 0 cfg 49:0f00 82:421c 83:0000 84:0000 85:0000 86:0000 87:0000 88:0007
ata3: dev 0 ATAPI, max UDMA/33
ata3: dev 0 configured for UDMA/33
scsi2 : sata_sil
ata4: no device found (phy stat 00000000)
scsi3 : sata_sil
Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 320173056 512-byte hdwr sectors (163929 MB) SCSI device sda: drive cache: write back
sda: sda1 sda2 < sda5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sdb: 320173056 512-byte hdwr sectors (163929 MB) SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2 < sdb5 >
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0

And that's it. no attaching scsi cdrom drive at scsi2. :(

Is it a bug or is it a feature that will come later or is it just my setup?

Quoted 8 lines

thanks,
Tobias Ottmar

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Quoted 3 lines

Hi Tobias

The support for ATAPI over SATA is there, however since it is still quite buggy, it is disabled by default.

What bugs are left in 2.6.10-rc1?

author
#3 lore raw
Quoted 2 lines

What bugs are left in 2.6.10-rc1?
-

I recompiled with #define ATA_ENABLE_ATAPI - and got only this:

ata3: command 0xa0 timeout, stat 0xf8 host_stat 0x0

Drive was not accessible. Then I tried recompiling with #define ATA_DEBUG and #define ATA_VERBOSE_DEBUG but the only thing I got are millions of message lines rolling over my screen, and the log entries on that million lines about ata3 where my DVD is is only one line:

ata_host_intr: ata3: host_stat 0x0

Then, I tried with #define ATA_ENABLE_PATA and #define ATA_ENABLE_DMADIR which gave the following: the kernel would boot up finding my SATA harddisks and finding the name of the DVD drive! Something new! but then it hang with a 0xa0 error on that dvd drive and the kernel didn't boot further. I'm sorry there are no logs.

If there's anything I can do in particular, please tell me, but I am new to kernel debugging although I have some experience in making it work for my setups :)

Tobias.