I gave libata a shot. Hardisk works fine. However the CDROM doesn't.
It would seem that the CDROM is detected, but the device node is not
created.
I do have libata.atapi_enabled=1 as a kernel parameter. This is a Vaio
laptop, with SiS 5513, PATA only, no SATA ports.
Did I miss anything?
Here's a chunk of the lspci.
libata version 2.00 loaded.
pata_sis 0000:00:02.5: version 0.4.4
ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1000 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1008 irq 15
scsi0 : pata_sis
ATA: abnormal status 0x7F on port 0x1F7
ATA: abnormal status 0x7F on port 0x1F7
ata1.00: ATA-5, max UDMA/100, 78140160 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/33
scsi1 : pata_sis
ata2.00: ATAPI, max UDMA/33
ata2.00: configured for UDMA/33
scsi 0:0:0:0: Direct-Access ATA HITACHI_DK23EA-4 00K3 PQ: 0 ANSI: 5
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4
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 MATSHITA UJDA740 DVD/CDRW 1.00 PQ: 0 ANSI: 5
scsi 1:0:0:0: Attached scsi generic sg1 type 5
Yenta: CardBus bridge found at 0000:00:0a.0 [104d:814e]
lspci -vv and dmesg attached.
Regards,
Ioan
On Thu, 16 Nov 2006 18:22:47 -0500
"Ioan Ionita" <[email protected]> wrote:
> I gave libata a shot. Hardisk works fine. However the CDROM doesn't.
> It would seem that the CDROM is detected, but the device node is not
> created.
>
> I do have libata.atapi_enabled=1 as a kernel parameter. This is a Vaio
> laptop, with SiS 5513, PATA only, no SATA ports.
>
> Did I miss anything?
>From the trace looks like the SCSI CD-ROM Driver is not compiled in
and/or loaded.
On 11/16/06, Alan <[email protected]> wrote:
> On Thu, 16 Nov 2006 18:22:47 -0500
> "Ioan Ionita" <[email protected]> wrote:
>
> > I gave libata a shot. Hardisk works fine. However the CDROM doesn't.
> > It would seem that the CDROM is detected, but the device node is not
> > created.
> >
> > I do have libata.atapi_enabled=1 as a kernel parameter. This is a Vaio
> > laptop, with SiS 5513, PATA only, no SATA ports.
> >
> > Did I miss anything?
>
> From the trace looks like the SCSI CD-ROM Driver is not compiled in
> and/or loaded.
Yes. I'm sorry I missed that. I enabled it, but it still doesn't work.
Some timeouts are occurring when I try to mount the CD-ROM. The CD-ROM
works fine with the old IDE framework. Here's the dmesg errors that
occur with libata and scsi cdrom support:
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x20)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
ata2: port is slow to respond, please be patient (Status 0xd0)
ata2: port failed to respond (30 secs, Status 0xd0)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x20)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
ata2: port is slow to respond, please be patient (Status 0xd0)
ata2: port failed to respond (30 secs, Status 0xd0)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x20)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
ata2: port is slow to respond, please be patient (Status 0xd0)
ata2: port failed to respond (30 secs, Status 0xd0)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: limiting speed to UDMA/25
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x20)
ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
On 11/16/06, Ioan Ionita <[email protected]> wrote:
> On 11/16/06, Alan <[email protected]> wrote:
> > On Thu, 16 Nov 2006 18:22:47 -0500
> > "Ioan Ionita" <[email protected]> wrote:
> >
> > > I gave libata a shot. Hardisk works fine. However the CDROM doesn't.
> > > It would seem that the CDROM is detected, but the device node is not
> > > created.
> > >
> > > I do have libata.atapi_enabled=1 as a kernel parameter. This is a Vaio
> > > laptop, with SiS 5513, PATA only, no SATA ports.
> > >
> > > Did I miss anything?
> >
> > From the trace looks like the SCSI CD-ROM Driver is not compiled in
> > and/or loaded.
>
> Yes. I'm sorry I missed that. I enabled it, but it still doesn't work.
> Some timeouts are occurring when I try to mount the CD-ROM. The CD-ROM
> works fine with the old IDE framework. Here's the dmesg errors that
> occur with libata and scsi cdrom support:
>
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (BMDMA stat 0x20)
> ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
> ata2: port is slow to respond, please be patient (Status 0xd0)
> ata2: port failed to respond (30 secs, Status 0xd0)
> ata2: soft resetting port
> ata2.00: configured for UDMA/33
> ata2: EH complete
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (BMDMA stat 0x20)
> ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
> ata2: port is slow to respond, please be patient (Status 0xd0)
> ata2: port failed to respond (30 secs, Status 0xd0)
> ata2: soft resetting port
> ata2.00: configured for UDMA/33
> ata2: EH complete
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (BMDMA stat 0x20)
> ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
> ata2: port is slow to respond, please be patient (Status 0xd0)
> ata2: port failed to respond (30 secs, Status 0xd0)
> ata2: soft resetting port
> ata2.00: configured for UDMA/33
> ata2: EH complete
> ata2.00: qc timeout (cmd 0xa0)
> ata2.00: limiting speed to UDMA/25
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: (BMDMA stat 0x20)
> ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
>
Oh, forgot to include the CD-ROM detection part. Are those abnormal
status errors a red flag?
eth0: SiS 900 PCI Fast Ethernet at 0x2000, IRQ 18, 08:00:46:a9:50:21.
libata version 2.00 loaded.
pata_sis 0000:00:02.5: version 0.4.4
ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0x1000 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1008 irq 15
scsi0 : pata_sis
ATA: abnormal status 0x7F on port 0x1F7
ATA: abnormal status 0x7F on port 0x1F7
ata1.00: ATA-5, max UDMA/100, 78140160 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/100
scsi1 : pata_sis
ata2.00: ATAPI, max UDMA/33
ata2.00: configured for UDMA/33
scsi 0:0:0:0: Direct-Access ATA HITACHI_DK23EA-4 00K3 PQ: 0 ANSI: 5
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 78140160 512-byte hdwr sectors (40008 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4
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 MATSHITA UJDA740 DVD/CDRW 1.00 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 24x/24x 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
Yenta: CardBus bridge found at 0000:00:0a.0 [104d:814e]
On Thu, Nov 16, 2006 at 08:34:03PM -0500, Ioan Ionita wrote:
> >ata2.00: limiting speed to UDMA/25
> >ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> >ata2.00: (BMDMA stat 0x20)
> >ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
etc.. - yes known. Something in the core code but not yet fixed (and I've
not had time to look at this).
On 11/17/06, Alan Cox <[email protected]> wrote:
> On Thu, Nov 16, 2006 at 08:34:03PM -0500, Ioan Ionita wrote:
> > >ata2.00: limiting speed to UDMA/25
> > >ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> > >ata2.00: (BMDMA stat 0x20)
> > >ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
>
> etc.. - yes known. Something in the core code but not yet fixed (and I've
> not had time to look at this).
>
OK. I'm glad it's been reported. In case you need any kind of testing
performed, don't hesitate to contact me.
Regards,
Ioan
Hello Alan, Jeff,
Reading a paper on this new libata, I just want to try but failled yet for what said this thread "ATAPI CDROM" ;_(.
I first test the latest stable 2.6.19.1 without luck, so I also want to try latest 2.6.20-rc2 unfortunately without more
success.
Here it was the test of new libata with 2.6.19.1:
[snip]
ata_piix 0000:00:07.1: version 2.00ac6
ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi3 : ata_piix
ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.01: ATAPI, max MWDMA1
ata1.00: configured for UDMA/33
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: limiting speed to PIO3
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: disabled
ata1: failed to recover some devices, retrying in 5 secs
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: limiting speed to UDMA/25
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.00: configured for UDMA/25
scsi4 : ata_piix
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
[snip]
And today with 2.6.20-rc2:
ata_piix 0000:00:07.1: version 2.00ac7
ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi3 : ata_piix
ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.01: ATAPI, max MWDMA1
ata1.00: configured for UDMA/33
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: limiting speed to PIO3
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: disabled
ata1: failed to recover some devices, retrying in 5 secs
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: limiting speed to UDMA/25
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.00: configured for UDMA/25
scsi4 : ata_piix
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
[snip]
seems to look like same kind of pb this thread speak about (i.e. hd seems to works fine but not atapi cdrom (r/w)) but not sure?
Any idea/advise?
Tia,
Joel
PS0: I check that scsi cdrom was well selected
PS1: with traditional ide support I get (with same 2.6.19.1 kernel):
[snip]
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: QUANTUM FIREBALLlct10 15, ATA DISK drive
hdb: PHILIPS CDD3610 CD-R/RW, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 29336832 sectors (15020 MB) w/418KiB Cache, CHS=29104/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14 hda15 hda16 hda17 hda18 hda19 hda20 hda21 hda22
hda23 hda24 >
hdb: ATAPI 6X CD-ROM CD-R/RW drive, 768kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
[snip]
Alan Cox wrote:
> On Thu, Nov 16, 2006 at 08:34:03PM -0500, Ioan Ionita wrote:
>>> ata2.00: limiting speed to UDMA/25
>>> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>>> ata2.00: (BMDMA stat 0x20)
>>> ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
>
> etc.. - yes known. Something in the core code but not yet fixed (and I've
> not had time to look at this).
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
Hello Alan, Jeff,
Reading a paper on this new libata, I just want to try but failled yet for what said this thread "ATAPI CDROM" ;_(.
I first test the latest stable 2.6.19.1 without luck, so I also want to try latest 2.6.20-rc2 unfortunately without more
success.
Here it was the test of new libata with 2.6.19.1:
[snip]
ata_piix 0000:00:07.1: version 2.00ac6
ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi3 : ata_piix
ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.01: ATAPI, max MWDMA1
ata1.00: configured for UDMA/33
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: limiting speed to PIO3
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: disabled
ata1: failed to recover some devices, retrying in 5 secs
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: limiting speed to UDMA/25
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.00: configured for UDMA/25
scsi4 : ata_piix
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: drive cache: write back
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
[snip]
And today with 2.6.20-rc2:
ata_piix 0000:00:07.1: version 2.00ac7
ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi3 : ata_piix
ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.01: ATAPI, max MWDMA1
ata1.00: configured for UDMA/33
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: limiting speed to PIO3
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: disabled
ata1: failed to recover some devices, retrying in 5 secs
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: limiting speed to UDMA/25
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.00: configured for UDMA/25
scsi4 : ata_piix
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
[snip]
seems to look like same kind of pb this thread speak about (i.e. hd seems to works fine but not atapi cdrom (r/w)) but not sure?
Any idea/advise?
Tia,
Joel
PS0: I check that scsi cdrom was well selected
PS1: with traditional ide support I get (with same 2.6.19.1 kernel):
[snip]
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: QUANTUM FIREBALLlct10 15, ATA DISK drive
hdb: PHILIPS CDD3610 CD-R/RW, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 29336832 sectors (15020 MB) w/418KiB Cache, CHS=29104/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14 hda15 hda16 hda17 hda18 hda19 hda20 hda21 hda22
hda23 hda24 >
hdb: ATAPI 6X CD-ROM CD-R/RW drive, 768kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
[snip]
Joel Soete wrote:
> Hello Alan, Jeff,
>
> Reading a paper on this new libata, I just want to try but failled yet
> for what said this thread "ATAPI CDROM" ;_(.
>
> I first test the latest stable 2.6.19.1 without luck, so I also want to
> try latest 2.6.20-rc2 unfortunately without more success.
>
> Here it was the test of new libata with 2.6.19.1:
> [snip]
> ata_piix 0000:00:07.1: version 2.00ac6
> ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
> ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
> scsi3 : ata_piix
> ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
> ata1.00: ata1: dev 0 multi count 16
> ata1.01: ATAPI, max MWDMA1
> ata1.00: configured for UDMA/33
> ata1.01: qc timeout (cmd 0xa1)
> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1.01: revalidation failed (errno=-5)
> ata1.01: limiting speed to PIO3
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1.01: qc timeout (cmd 0xa1)
> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1.01: revalidation failed (errno=-5)
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1.01: qc timeout (cmd 0xa1)
> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1.01: revalidation failed (errno=-5)
> ata1.01: disabled
> ata1: failed to recover some devices, retrying in 5 secs
> ata1.00: failed to set xfermode (err_mask=0x40)
> ata1.00: limiting speed to UDMA/25
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1.00: configured for UDMA/25
> scsi4 : ata_piix
> scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0
> ANSI: 5
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: drive cache: write back
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: drive cache: write back
> sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14
> sdc15 >
> sd 3:0:0:0: Attached scsi disk sdc
> sd 3:0:0:0: Attached scsi generic sg2 type 0
> [snip]
>
> And today with 2.6.20-rc2:
> ata_piix 0000:00:07.1: version 2.00ac7
> ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
> ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
> scsi3 : ata_piix
> ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
> ata1.00: ata1: dev 0 multi count 16
> ata1.01: ATAPI, max MWDMA1
> ata1.00: configured for UDMA/33
> ata1.01: qc timeout (cmd 0xa1)
> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1.01: revalidation failed (errno=-5)
> ata1.01: limiting speed to PIO3
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1.01: qc timeout (cmd 0xa1)
> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1.01: revalidation failed (errno=-5)
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1.01: qc timeout (cmd 0xa1)
> ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata1.01: revalidation failed (errno=-5)
> ata1.01: disabled
> ata1: failed to recover some devices, retrying in 5 secs
> ata1.00: failed to set xfermode (err_mask=0x40)
> ata1.00: limiting speed to UDMA/25
> ata1: failed to recover some devices, retrying in 5 secs
> ata1: port is slow to respond, please be patient (Status 0xd0)
> ata1: port failed to respond (30 secs, Status 0xd0)
> ata1.00: configured for UDMA/25
> scsi4 : ata_piix
> scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0
> ANSI: 5
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14
> sdc15 >
> sd 3:0:0:0: Attached scsi disk sdc
> sd 3:0:0:0: Attached scsi generic sg2 type 0
> [snip]
>
> seems to look like same kind of pb this thread speak about (i.e. hd
> seems to works fine but not atapi cdrom (r/w)) but not sure?
>
> Any idea/advise?
>
>
> Tia,
> Joel
>
> PS0: I check that scsi cdrom was well selected
>
> PS1: with traditional ide support I get (with same 2.6.19.1 kernel):
> [snip]
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PIIX4: IDE controller at PCI slot 0000:00:07.1
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
> ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
> Probing IDE interface ide0...
> hda: QUANTUM FIREBALLlct10 15, ATA DISK drive
> hdb: PHILIPS CDD3610 CD-R/RW, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Probing IDE interface ide1...
> Probing IDE interface ide1...
> hda: max request size: 128KiB
> hda: 29336832 sectors (15020 MB) w/418KiB Cache, CHS=29104/16/63, UDMA(33)
> hda: cache flushes not supported
> hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 hda14
> hda15 hda16 hda17 hda18 hda19 hda20 hda21 hda22
> hda23 hda24 >
> hdb: ATAPI 6X CD-ROM CD-R/RW drive, 768kB Cache, DMA
> Uniform CD-ROM driver Revision: 3.20
> [snip]
>
> Alan Cox wrote:
>> On Thu, Nov 16, 2006 at 08:34:03PM -0500, Ioan Ionita wrote:
>>>> ata2.00: limiting speed to UDMA/25
>>>> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
>>>> ata2.00: (BMDMA stat 0x20)
>>>> ata2.00: tag 0 cmd 0xa0 Emask 0x5 stat 0x51 err 0x51 (timeout)
>>
>> etc.. - yes known. Something in the core code but not yet fixed (and I've
>> not had time to look at this).
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>>
>
>
Joel Soete wrote:
> Hello Alan, Jeff,
>
> Reading a paper on this new libata, I just want to try but failled yet
> for what said this thread "ATAPI CDROM" ;_(.
>
> I first test the latest stable 2.6.19.1 without luck, so I also want to
> try latest 2.6.20-rc2 unfortunately without more success.
I'm attaching two patches. One against 2.6.19 the other against
2.6.20-rc3. Both have about the same effect. Please apply and report
what happens and full dmesg.
Thanks and happy new year.
--
tejun
0000000000000000 size: 000000000009fc00 end: 000000000009fc00 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000009fc00 size: 0000000000000400 end: 00000000000a0000 type: 2
copy_e820_map() start: 00000000000f0000 size: 0000000000010000 end: 0000000000100000 type: 2
copy_e820_map() start: 0000000000100000 size: 000000000fef0000 end: 000000000fff0000 type: 1
copy_e820_map() type is E820_RAM
copy_e820_map() start: 000000000fff0000 size: 0000000000003000 end: 000000000fff3000 type: 4
copy_e820_map() start: 000000000fff3000 size: 000000000000d000 end: 0000000010000000 type: 3
copy_e820_map() start: 00000000ffff0000 size: 0000000000010000 end: 0000000100000000 type: 2
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000fff0000 (usable)
BIOS-e820: 000000000fff0000 - 000000000fff3000 (ACPI NVS)
BIOS-e820: 000000000fff3000 - 0000000010000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
255MB LOWMEM available.
Entering add_active_range(0, 0, 65520) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 65520
early_node_map[1] active PFN ranges
0: 0 -> 65520
On node 0 totalpages: 65520
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 479 pages used for memmap
Normal zone: 60945 pages, LIFO batch:15
DMI 2.3 present.
Allocating PCI resources starting at 20000000 (gap: 10000000:efff0000)
Detected 551.291 MHz processor.
Built 1 zonelists. Total pages: 65009
Kernel command line: -s libata.atapi_enabled=1 root=/dev/md2 profile=2
kernel profiling enabled (shift: 2)
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffd000 (01201000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 252896k/262080k available (2590k kernel code, 8720k reserved, 826k data, 276k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfffbc000 - 0xfffff000 ( 268 kB)
vmalloc : 0xd0800000 - 0xfffba000 ( 759 MB)
lowmem : 0xc0000000 - 0xcfff0000 ( 255 MB)
.init : 0xc045a000 - 0xc049f000 ( 276 kB)
.data : 0xc038781d - 0xc0456250 ( 826 kB)
.text : 0xc0100000 - 0xc038781d (2590 kB)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1103.39 BogoMIPS (lpj=2206781)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: Intel Pentium III (Katmai) stepping 03
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfb240, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
SCSI subsystem initialized
libata version 2.00 loaded.
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 4000-403f claimed by PIIX4 ACPI
PCI quirk: region 5000-500f claimed by PIIX4 SMB
Boot video device is 0000:01:00.0
PCI: Using IRQ router PIIX/ICH [8086/7110] at 0000:00:07.0
PCI: Bridge: 0000:00:01.0
IO window: c000-cfff
MEM window: e4000000-e7ffffff
PREFETCH window: disabled.
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
Machine check exception polling timer started.
Installing knfsd (copyright (C) 1996 [email protected]).
Installing v9fs 9P2000 file system support
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Limiting direct PCI/PCI transfers.
lp: driver loaded but no devices found
Real Time Clock Driver v1.12ac
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 440BX Chipset.
agpgart: AGP aperture is 64M @ 0xe0000000
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
lp0: using parport0 (polling).
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
loop: loaded (max 8 devices)
PCI: setting IRQ 9 as level-triggered
PCI: Found IRQ 9 for device 0000:00:0b.0
hp100: Busmaster mode enabled.
hp100: at 0xe000, IRQ 9, PCI bus, 32k SRAM (rx/tx 75%).
hp100: Adapter is attached to 10Mb/s network (10baseT).
PCI: setting IRQ 10 as level-triggered
PCI: Found IRQ 10 for device 0000:00:0c.0
PCI: Sharing IRQ 10 with 0000:00:07.2
hp100: Busmaster mode enabled.
hp100: at 0xe400, IRQ 10, PCI bus, 32k SRAM (rx/tx 75%).
hp100: Warning! Link down.
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
NET: Registered protocol family 24
PCI: setting IRQ 11 as level-triggered
PCI: Found IRQ 11 for device 0000:00:09.0
sym0: <875> rev 0x14 at pci 0000:00:09.0 irq 11
sym0: Symbios NVRAM, ID 7, Fast-20, HVD, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware.
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.3
scsi 0:0:6:0: Direct-Access SEAGATE ST336605LSUN36G 0238 PQ: 0 ANSI: 3
target0:0:6: tagged command queuing enabled, command queue depth 16.
target0:0:6: Beginning Domain Validation
target0:0:6: asynchronous
target0:0:6: wide asynchronous
target0:0:6: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 16)
target0:0:6: Domain Validation skipping write tests
target0:0:6: Ending Domain Validation
PCI: setting IRQ 5 as level-triggered
PCI: Found IRQ 5 for device 0000:00:09.1
PCI: Sharing IRQ 5 with 0000:00:0a.0
sym1: <875> rev 0x14 at pci 0000:00:09.1 irq 5
sym1: Symbios NVRAM, ID 7, Fast-20, HVD, parity checking
sym1: open drain IRQ line driver, using on-chip SRAM
sym1: using LOAD/STORE-based firmware.
sym1: SCSI BUS has been reset.
scsi1 : sym-2.2.3
PCI: Found IRQ 5 for device 0000:00:0a.0
PCI: Sharing IRQ 5 with 0000:00:09.1
sym2: <875> rev 0x26 at pci 0000:00:0a.0 irq 5
sym2: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
sym2: open drain IRQ line driver, using on-chip SRAM
sym2: using LOAD/STORE-based firmware.
sym2: SCSI BUS has been reset.
scsi2 : sym-2.2.3
target2:0:0: Multiple LUNs disabled in NVRAM
scsi 2:0:0:0: Direct-Access QUANTUM ATLAS_V_18_WLS 0230 PQ: 0 ANSI: 3
target2:0:0: tagged command queuing enabled, command queue depth 16.
target2:0:0: Beginning Domain Validation
target2:0:0: asynchronous
target2:0:0: wide asynchronous
target2:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 16)
target2:0:0: Domain Validation skipping write tests
target2:0:0: Ending Domain Validation
target2:0:1: Multiple LUNs disabled in NVRAM
target2:0:2: Multiple LUNs disabled in NVRAM
target2:0:3: Multiple LUNs disabled in NVRAM
target2:0:4: Multiple LUNs disabled in NVRAM
target2:0:5: Multiple LUNs disabled in NVRAM
target2:0:6: Multiple LUNs disabled in NVRAM
target2:0:8: Multiple LUNs disabled in NVRAM
target2:0:9: Multiple LUNs disabled in NVRAM
target2:0:10: Multiple LUNs disabled in NVRAM
target2:0:11: Multiple LUNs disabled in NVRAM
target2:0:12: Multiple LUNs disabled in NVRAM
target2:0:13: Multiple LUNs disabled in NVRAM
target2:0:14: Multiple LUNs disabled in NVRAM
target2:0:15: Multiple LUNs disabled in NVRAM
st: Version 20061107, fixed bufsize 32768, s/g segs 256
SCSI device sda: 71132959 512-byte hdwr sectors (36420 MB)
sda: Write Protect is off
sda: Mode Sense: d3 00 10 08
SCSI device sda: write cache: disabled, read cache: enabled, supports DPO and FUA
SCSI device sda: 71132959 512-byte hdwr sectors (36420 MB)
sda: Write Protect is off
sda: Mode Sense: d3 00 10 08
SCSI device sda: write cache: disabled, read cache: enabled, supports DPO and FUA
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
sd 0:0:6:0: Attached scsi disk sda
SCSI device sdb: 35861388 512-byte hdwr sectors (18361 MB)
sdb: Write Protect is off
sdb: Mode Sense: e3 00 10 08
SCSI device sdb: write cache: enabled, read cache: enabled, supports DPO and FUA
SCSI device sdb: 35861388 512-byte hdwr sectors (18361 MB)
sdb: Write Protect is off
sdb: Mode Sense: e3 00 10 08
SCSI device sdb: write cache: enabled, read cache: enabled, supports DPO and FUA
sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 sdb8 sdb9 sdb10 >
sd 2:0:0:0: Attached scsi disk sdb
sd 0:0:6:0: Attached scsi generic sg0 type 0
sd 2:0:0:0: Attached scsi generic sg1 type 0
ata_piix 0000:00:07.1: version 2.00ac7
ata1: PATA max UDMA/33:PIO4 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/33:PIO4 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi3 : ata_piix
ata1.00: ATA-4, max UDMA/66:PIO4, 29336832 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.01: ATAPI, max MWDMA1:PIO3
ata1.00: configured for UDMA/33:PIO0
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: limiting speed to PIO3
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.01: qc timeout (cmd 0xa1)
ata1.01: failed to IDENTIFY (I/O error, err_mask=0x4)
ata1.01: revalidation failed (errno=-5)
ata1.01: disabled
ata1: failed to recover some devices, retrying in 5 secs
ata1.00: failed to set xfermode (err_mask=0x40)
ata1.00: limiting speed to UDMA/25:PIO3
ata1: failed to recover some devices, retrying in 5 secs
ata1: port is slow to respond, please be patient (Status 0xd0)
ata1: port failed to respond (30 secs, Status 0xd0)
ata1.00: configured for UDMA/25:PIO0
scsi4 : ata_piix
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
usbmon: debugfs is not available
USB Universal Host Controller Interface driver v3.0
PCI: Found IRQ 10 for device 0000:00:07.2
PCI: Sharing IRQ 10 with 0000:00:0c.0
uhci_hcd 0000:00:07.2: UHCI Host Controller
uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:07.2: irq 10, io base 0x0000d000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
/usr/src/linux-2.6.20-rc3/drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbhid
/usr/src/linux-2.6.20-rc3/drivers/usb/input/hid-core.c: v2.6:USB HID core driver
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input0
md: raid1 personality registered for level 1
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: [email protected]
EISA: Probing bus 0 at eisa.0
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
NET: Registered protocol family 17
Using IPI Shortcut mode
Time: tsc clocksource has been installed.
logips2pp: Detected unknown logitech mouse model 1
input: PS/2 Logitech Mouse as /class/input/input1
md: Autodetecting RAID arrays.
md: autorun ...
md: considering sda8 ...
md: adding sda8 ...
md: sda7 has different UUID to sda8
md: sda6 has different UUID to sda8
md: sda5 has different UUID to sda8
md: sda3 has different UUID to sda8
md: sda2 has different UUID to sda8
md: sda1 has different UUID to sda8
md: created md6
md: bind<sda8>
md: running: <sda8>
raid1: raid set md6 active with 1 out of 2 mirrors
md: considering sda7 ...
md: adding sda7 ...
md: sda6 has different UUID to sda7
md: sda5 has different UUID to sda7
md: sda3 has different UUID to sda7
md: sda2 has different UUID to sda7
md: sda1 has different UUID to sda7
md: created md5
md: bind<sda7>
md: running: <sda7>
raid1: raid set md5 active with 1 out of 2 mirrors
md: considering sda6 ...
md: adding sda6 ...
md: sda5 has different UUID to sda6
md: sda3 has different UUID to sda6
md: sda2 has different UUID to sda6
md: sda1 has different UUID to sda6
md: created md4
md: bind<sda6>
md: running: <sda6>
raid1: raid set md4 active with 1 out of 2 mirrors
md: considering sda5 ...
md: adding sda5 ...
md: sda3 has different UUID to sda5
md: sda2 has different UUID to sda5
md: sda1 has different UUID to sda5
md: created md3
md: bind<sda5>
md: running: <sda5>
raid1: raid set md3 active with 1 out of 2 mirrors
md: considering sda3 ...
md: adding sda3 ...
md: sda2 has different UUID to sda3
md: sda1 has different UUID to sda3
md: created md2
md: bind<sda3>
md: running: <sda3>
raid1: raid set md2 active with 1 out of 2 mirrors
md: considering sda2 ...
md: adding sda2 ...
md: sda1 has different UUID to sda2
md: created md1
md: bind<sda2>
md: running: <sda2>
raid1: raid set md1 active with 1 out of 2 mirrors
md: considering sda1 ...
md: adding sda1 ...
md: created md0
md: bind<sda1>
md: running: <sda1>
raid1: raid set md0 active with 1 out of 2 mirrors
md: ... autorun DONE.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 276k freed
Adding 255928k swap on /dev/md1. Priority:-1 extents:1 across:255928k
EXT3 FS on md2, internal journal
Hello all,
I just tested libata with this newest 2.6.20-rc6 but no changes ;-(
Any news?
Thanks,
Joel
Joel Soete wrote:
> Hello Tejun,
>
> Tejun Heo wrote:
>> Joel Soete wrote:
>>> Hello Alan, Jeff,
>>>
>>> Reading a paper on this new libata, I just want to try but failled yet
>>> for what said this thread "ATAPI CDROM" ;_(.
>>>
>>> I first test the latest stable 2.6.19.1 without luck, so I also want to
>>> try latest 2.6.20-rc2 unfortunately without more success.
>>
>> I'm attaching two patches. One against 2.6.19 the other against
>> 2.6.20-rc3. Both have about the same effect. Please apply and report
>> what happens and full dmesg.
>>
>> Thanks and happy new year.
>>
> Happy new year too ;-)
>
> Because of lack of time I only test your patch against 2.6.20-rc3.
>
> Unfortunately it doesn't help yet, sorry (i would very like to be of
> more help).
>
> I here attache the full dmesg of my i386 boxe.
>
> Thanks again,
> Joel
>
>
Does acpi=off make cdrom work?
On 1/27/07, Joel Soete <[email protected]> wrote:
> Hello all,
>
> I just tested libata with this newest 2.6.20-rc6 but no changes ;-(
>
> Any news?
>
> Thanks,
> Joel
>
> Joel Soete wrote:
> > Hello Tejun,
> >
> > Tejun Heo wrote:
> >> Joel Soete wrote:
> >>> Hello Alan, Jeff,
> >>>
> >>> Reading a paper on this new libata, I just want to try but failled yet
> >>> for what said this thread "ATAPI CDROM" ;_(.
> >>>
> >>> I first test the latest stable 2.6.19.1 without luck, so I also want to
> >>> try latest 2.6.20-rc2 unfortunately without more success.
> >>
> >> I'm attaching two patches. One against 2.6.19 the other against
> >> 2.6.20-rc3. Both have about the same effect. Please apply and report
> >> what happens and full dmesg.
> >>
> >> Thanks and happy new year.
> >>
> > Happy new year too ;-)
> >
> > Because of lack of time I only test your patch against 2.6.20-rc3.
> >
> > Unfortunately it doesn't help yet, sorry (i would very like to be of
> > more help).
> >
> > I here attache the full dmesg of my i386 boxe.
> >
> > Thanks again,
> > Joel
> >
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Luming Yu wrote:
> Does acpi=off make cdrom work?
>
Unfortunately not :_(
(for more details I attached a compressed dmesg trace?)
Thanks,
Joel
> On 1/27/07, Joel Soete <[email protected]> wrote:
>> Hello all,
>>
>> I just tested libata with this newest 2.6.20-rc6 but no changes ;-(
>>
>> Any news?
>>
>> Thanks,
>> Joel
>>
Please test the attached patch over 2.6.20.
Thanks.
--
tejun
Tejun Heo wrote:
> Please test the attached patch over 2.6.20.
>
> Thanks.
>
It's already too late so quick and dirty rebuild of 2.6.20-git6 (failled before your patch) but now your patch fixe the pb:
[snip]
ata_piix 0000:00:07.1: version 2.00ac7
ata1: PATA max UDMA/33 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14
ata2: PATA max UDMA/33 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15
scsi3 : ata_piix
ata1.00: ATA-4: QUANTUM FIREBALLlct10 15, A03.0900, max UDMA/66
ata1.00: 29336832 sectors, multi 16: LBA
ata1.00: configured for UDMA/33
scsi4 : ata_piix
ata2.01: ATAPI, max MWDMA1
ata2.01: configured for MWDMA1
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
scsi 4:0:1:0: CD-ROM PHILIPS CDD3610 CD-R/RW 3.09 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 6x/6x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:1:0: Attached scsi CD-ROM sr0
sr 4:0:1:0: Attached scsi generic sg3 type 5
[snip]
cool ;-)
Sorry, I will try later against 2.6.20 (i guess it will also fixe the pb) and attempt to burn a cd.
I will advise you asap.
Thanks again,
Joel
Hello Tejun,
A small update:
your patch also works against 2.6.20
but seems that open the door to numerous other pb:
1/ pb to burn cd:
# md5sum cd060213.iso
6a1248783a21722816b972aa9bae9d5e cd060213.iso
# ll cd060213.iso
-rwxr-xr-x 1 root root 3213312 Feb 13 2006 cd060213.iso
# dd if=/dev/sr0 bs=1 count=3213312 | md5sum
dd: reading `/dev/sr0': Input/output error
0337e9846d17779945c5c252d4f897f0 -
3129344+0 records in
3129344+0 records out
3129344 bytes (3.1 MB) copied, 36.6963 seconds, 85.3 kB/s
eventhought cdrecord seems to be successfull???
2/ (but that should be much more related to scsi api) sdcXX > sdc15 doesn't works ;-(
# sfdisk -l /dev/sdc
Disk /dev/sdc: 1826 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdc1 * 0+ 195 196- 1574338+ b W95 FAT32
/dev/sdc2 196 1825 1630 13092975 5 Extended
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty
/dev/sdc5 * 196+ 197 2- 16033+ 83 Linux
/dev/sdc6 * 198+ 199 2- 16033+ 83 Linux
/dev/sdc7 200+ 201 2- 16033+ 83 Linux
/dev/sdc8 202+ 217 16- 128488+ 82 Linux swap / Solaris
/dev/sdc9 218+ 478 261- 2096451 83 Linux
/dev/sdc10 479+ 486 8- 64228+ 83 Linux
/dev/sdc11 487+ 488 2- 16033+ 83 Linux
/dev/sdc12 489+ 504 16- 128488+ 83 Linux
/dev/sdc13 505+ 618 114- 915673+ 83 Linux
/dev/sdc14 619+ 620 2- 16033+ 83 Linux
/dev/sdc15 621+ 636 16- 128488+ 83 Linux
/dev/sdc16 637+ 644 8- 64228+ 83 Linux
/dev/sdc17 645+ 646 2- 16033+ 83 Linux
/dev/sdc18 647+ 654 8- 64228+ 83 Linux
/dev/sdc19 655+ 656 2- 16033+ 83 Linux
/dev/sdc20 657+ 773 117- 939771 83 Linux
/dev/sdc21 774+ 789 16- 128488+ 83 Linux
/dev/sdc22 790+ 880 91- 730926 83 Linux
/dev/sdc23 881+ 1533 653- 5245191 83 Linux
/dev/sdc24 1795 1825 31 249007+ 83 Linux
# mount /dev/sdc22 /4free
mount: /dev/sdc22 is not a valid block device
# ll /dev/sdc*
brw-rw---- 1 root disk 8, 32 Dec 1 2001 /dev/sdc
brw-rw---- 1 root disk 8, 33 Dec 1 2001 /dev/sdc1
brw-rw---- 1 root disk 8, 42 Dec 1 2001 /dev/sdc10
brw-rw---- 1 root disk 8, 43 Dec 1 2001 /dev/sdc11
brw-rw---- 1 root disk 8, 44 Dec 1 2001 /dev/sdc12
brw-rw---- 1 root disk 8, 45 Dec 1 2001 /dev/sdc13
brw-rw---- 1 root disk 8, 46 Dec 1 2001 /dev/sdc14
brw-rw---- 1 root disk 8, 47 Dec 1 2001 /dev/sdc15
brw-r--r-- 1 root root 8, 48 Feb 13 16:26 /dev/sdc16
brw-r--r-- 1 root root 8, 49 Feb 13 16:26 /dev/sdc17
brw-r--r-- 1 root root 8, 50 Feb 13 16:26 /dev/sdc18
brw-r--r-- 1 root root 8, 51 Feb 13 16:27 /dev/sdc19
brw-rw---- 1 root disk 8, 34 Dec 1 2001 /dev/sdc2
brw-r--r-- 1 root root 8, 52 Feb 13 16:27 /dev/sdc20
brw-r--r-- 1 root root 8, 53 Feb 13 16:27 /dev/sdc21
brw-r--r-- 1 root root 8, 54 Feb 13 16:27 /dev/sdc22
brw-r--r-- 1 root root 8, 55 Feb 13 16:27 /dev/sdc23
brw-r--r-- 1 root root 8, 56 Feb 13 16:27 /dev/sdc24
brw-rw---- 1 root disk 8, 35 Dec 1 2001 /dev/sdc3
brw-rw---- 1 root disk 8, 36 Dec 1 2001 /dev/sdc4
brw-rw---- 1 root disk 8, 37 Dec 1 2001 /dev/sdc5
brw-rw---- 1 root disk 8, 38 Dec 1 2001 /dev/sdc6
brw-rw---- 1 root disk 8, 39 Dec 1 2001 /dev/sdc7
brw-rw---- 1 root disk 8, 40 Dec 1 2001 /dev/sdc8
brw-rw---- 1 root disk 8, 41 Dec 1 2001 /dev/sdc9
# dmesg
[snip]
scsi3 : ata_piix
ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/33
scsi4 : ata_piix
ata2.01: ATAPI, max MWDMA1
ata2.01: configured for MWDMA1
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
[snip]
I will try to have a look later.
Cheers,
Joel
Joel Soete wrote:
>
>
> Tejun Heo wrote:
>> Please test the attached patch over 2.6.20.
>>
>> Thanks.
>>
> It's already too late so quick and dirty rebuild of 2.6.20-git6 (failled
> before your patch) but now your patch fixe the pb:
> [snip]
> ata_piix 0000:00:07.1: version 2.00ac7
> ata1: PATA max UDMA/33 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000
> irq 14
> ata2: PATA max UDMA/33 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008
> irq 15
> scsi3 : ata_piix
> ata1.00: ATA-4: QUANTUM FIREBALLlct10 15, A03.0900, max UDMA/66
> ata1.00: 29336832 sectors, multi 16: LBA
> ata1.00: configured for UDMA/33
> scsi4 : ata_piix
> ata2.01: ATAPI, max MWDMA1
> ata2.01: configured for MWDMA1
> scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0
> ANSI: 5
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14
> sdc15 >
> sd 3:0:0:0: Attached scsi disk sdc
> sd 3:0:0:0: Attached scsi generic sg2 type 0
> scsi 4:0:1:0: CD-ROM PHILIPS CDD3610 CD-R/RW 3.09 PQ: 0
> ANSI: 5
> sr0: scsi3-mmc drive: 6x/6x writer cd/rw xa/form2 cdda tray
> Uniform CD-ROM driver Revision: 3.20
> sr 4:0:1:0: Attached scsi CD-ROM sr0
> sr 4:0:1:0: Attached scsi generic sg3 type 5
> [snip]
>
> cool ;-)
>
> Sorry, I will try later against 2.6.20 (i guess it will also fixe the
> pb) and attempt to burn a cd.
> I will advise you asap.
>
> Thanks again,
> Joel
>
>
Hi,
On Tuesday 13 February 2007 18:35, Joel Soete wrote:
> scsi3 : ata_piix
> ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
> ata1.00: ata1: dev 0 multi count 16
> ata1.00: configured for UDMA/33
<...>
> scsi 3:0:0:0: Direct-Access ? ? ATA ? ? ?QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
IDE driver with CONFIG_IDEDMA_IVB=y should give you UDMA/66.
Could you send me output of "hdparm --Istdout /dev/sdc" command?
> scsi4 : ata_piix
> ata2.01: ATAPI, max MWDMA1
> ata2.01: configured for MWDMA1
and "hdparm --Istdout /dev/sr0"
[ max speed == MWDMA1 is possible but quite unusual ]
Thanks,
Bart
> Could you send me output of "hdparm --Istdout /dev/sdc" command?
Ditto - if this is one of the odd few quantums that need compile time
hacks in the old IDE its also one we need to do runtime handling for in
*both*.
Hello, Joel.
Joel Soete wrote:
> A small update:
> your patch also works against 2.6.20
Glad to hear that.
> but seems that open the door to numerous other pb:
> 1/ pb to burn cd:
> # md5sum cd060213.iso
> 6a1248783a21722816b972aa9bae9d5e cd060213.iso
>
> # ll cd060213.iso
> -rwxr-xr-x 1 root root 3213312 Feb 13 2006 cd060213.iso
>
> # dd if=/dev/sr0 bs=1 count=3213312 | md5sum
> dd: reading `/dev/sr0': Input/output error
> 0337e9846d17779945c5c252d4f897f0 -
> 3129344+0 records in
> 3129344+0 records out
> 3129344 bytes (3.1 MB) copied, 36.6963 seconds, 85.3 kB/s
>
> eventhought cdrecord seems to be successfull???
Hmm... 82K difference. Can you burn an iso and md5sum the files
contained in the image and burned cd?
> 2/ (but that should be much more related to scsi api) sdcXX > sdc15
> doesn't works ;-(
> # sfdisk -l /dev/sdc
>
> Disk /dev/sdc: 1826 cylinders, 255 heads, 63 sectors/track
> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
>
> Device Boot Start End #cyls #blocks Id System
> /dev/sdc1 * 0+ 195 196- 1574338+ b W95 FAT32
> /dev/sdc2 196 1825 1630 13092975 5 Extended
> /dev/sdc3 0 - 0 0 0 Empty
> /dev/sdc4 0 - 0 0 0 Empty
> /dev/sdc5 * 196+ 197 2- 16033+ 83 Linux
> /dev/sdc6 * 198+ 199 2- 16033+ 83 Linux
> /dev/sdc7 200+ 201 2- 16033+ 83 Linux
> /dev/sdc8 202+ 217 16- 128488+ 82 Linux swap / Solaris
> /dev/sdc9 218+ 478 261- 2096451 83 Linux
> /dev/sdc10 479+ 486 8- 64228+ 83 Linux
> /dev/sdc11 487+ 488 2- 16033+ 83 Linux
> /dev/sdc12 489+ 504 16- 128488+ 83 Linux
> /dev/sdc13 505+ 618 114- 915673+ 83 Linux
> /dev/sdc14 619+ 620 2- 16033+ 83 Linux
> /dev/sdc15 621+ 636 16- 128488+ 83 Linux
> /dev/sdc16 637+ 644 8- 64228+ 83 Linux
> /dev/sdc17 645+ 646 2- 16033+ 83 Linux
> /dev/sdc18 647+ 654 8- 64228+ 83 Linux
> /dev/sdc19 655+ 656 2- 16033+ 83 Linux
> /dev/sdc20 657+ 773 117- 939771 83 Linux
> /dev/sdc21 774+ 789 16- 128488+ 83 Linux
> /dev/sdc22 790+ 880 91- 730926 83 Linux
> /dev/sdc23 881+ 1533 653- 5245191 83 Linux
> /dev/sdc24 1795 1825 31 249007+ 83 Linux
Whee, you have 24 partitions? Due to the way SCSI block device numbers
are laid out, SCSI supports only upto 15 partitions per device.
--
tejun
On Tue, Feb 13, 2007 at 05:35:32PM +0000, Joel Soete wrote:
> A small update:
> your patch also works against 2.6.20
>
> but seems that open the door to numerous other pb:
> 1/ pb to burn cd:
> # md5sum cd060213.iso
> 6a1248783a21722816b972aa9bae9d5e cd060213.iso
>
> # ll cd060213.iso
> -rwxr-xr-x 1 root root 3213312 Feb 13 2006 cd060213.iso
>
> # dd if=/dev/sr0 bs=1 count=3213312 | md5sum
> dd: reading `/dev/sr0': Input/output error
> 0337e9846d17779945c5c252d4f897f0 -
> 3129344+0 records in
> 3129344+0 records out
> 3129344 bytes (3.1 MB) copied, 36.6963 seconds, 85.3 kB/s
>
> eventhought cdrecord seems to be successfull???
Has that ever worked by any method? I have always had to use readcd
along with passing the correct number of sectors on the CD to get a
proper matching image. dd always seems to end up reading some junk past
the end of the disc.
> 2/ (but that should be much more related to scsi api) sdcXX > sdc15 doesn't
> works ;-(
> # sfdisk -l /dev/sdc
>
> Disk /dev/sdc: 1826 cylinders, 255 heads, 63 sectors/track
> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
>
> Device Boot Start End #cyls #blocks Id System
> /dev/sdc1 * 0+ 195 196- 1574338+ b W95 FAT32
> /dev/sdc2 196 1825 1630 13092975 5 Extended
> /dev/sdc3 0 - 0 0 0 Empty
> /dev/sdc4 0 - 0 0 0 Empty
> /dev/sdc5 * 196+ 197 2- 16033+ 83 Linux
> /dev/sdc6 * 198+ 199 2- 16033+ 83 Linux
> /dev/sdc7 200+ 201 2- 16033+ 83 Linux
> /dev/sdc8 202+ 217 16- 128488+ 82 Linux swap / Solaris
> /dev/sdc9 218+ 478 261- 2096451 83 Linux
> /dev/sdc10 479+ 486 8- 64228+ 83 Linux
> /dev/sdc11 487+ 488 2- 16033+ 83 Linux
> /dev/sdc12 489+ 504 16- 128488+ 83 Linux
> /dev/sdc13 505+ 618 114- 915673+ 83 Linux
> /dev/sdc14 619+ 620 2- 16033+ 83 Linux
> /dev/sdc15 621+ 636 16- 128488+ 83 Linux
> /dev/sdc16 637+ 644 8- 64228+ 83 Linux
> /dev/sdc17 645+ 646 2- 16033+ 83 Linux
> /dev/sdc18 647+ 654 8- 64228+ 83 Linux
> /dev/sdc19 655+ 656 2- 16033+ 83 Linux
> /dev/sdc20 657+ 773 117- 939771 83 Linux
> /dev/sdc21 774+ 789 16- 128488+ 83 Linux
> /dev/sdc22 790+ 880 91- 730926 83 Linux
> /dev/sdc23 881+ 1533 653- 5245191 83 Linux
> /dev/sdc24 1795 1825 31 249007+ 83 Linux
I have to ask: What are all those partitions?
> # mount /dev/sdc22 /4free
> mount: /dev/sdc22 is not a valid block device
>
> # ll /dev/sdc*
> brw-rw---- 1 root disk 8, 32 Dec 1 2001 /dev/sdc
> brw-rw---- 1 root disk 8, 33 Dec 1 2001 /dev/sdc1
> brw-rw---- 1 root disk 8, 42 Dec 1 2001 /dev/sdc10
> brw-rw---- 1 root disk 8, 43 Dec 1 2001 /dev/sdc11
> brw-rw---- 1 root disk 8, 44 Dec 1 2001 /dev/sdc12
> brw-rw---- 1 root disk 8, 45 Dec 1 2001 /dev/sdc13
> brw-rw---- 1 root disk 8, 46 Dec 1 2001 /dev/sdc14
> brw-rw---- 1 root disk 8, 47 Dec 1 2001 /dev/sdc15
> brw-r--r-- 1 root root 8, 48 Feb 13 16:26 /dev/sdc16
> brw-r--r-- 1 root root 8, 49 Feb 13 16:26 /dev/sdc17
> brw-r--r-- 1 root root 8, 50 Feb 13 16:26 /dev/sdc18
> brw-r--r-- 1 root root 8, 51 Feb 13 16:27 /dev/sdc19
> brw-rw---- 1 root disk 8, 34 Dec 1 2001 /dev/sdc2
> brw-r--r-- 1 root root 8, 52 Feb 13 16:27 /dev/sdc20
> brw-r--r-- 1 root root 8, 53 Feb 13 16:27 /dev/sdc21
> brw-r--r-- 1 root root 8, 54 Feb 13 16:27 /dev/sdc22
> brw-r--r-- 1 root root 8, 55 Feb 13 16:27 /dev/sdc23
> brw-r--r-- 1 root root 8, 56 Feb 13 16:27 /dev/sdc24
> brw-rw---- 1 root disk 8, 35 Dec 1 2001 /dev/sdc3
> brw-rw---- 1 root disk 8, 36 Dec 1 2001 /dev/sdc4
> brw-rw---- 1 root disk 8, 37 Dec 1 2001 /dev/sdc5
> brw-rw---- 1 root disk 8, 38 Dec 1 2001 /dev/sdc6
> brw-rw---- 1 root disk 8, 39 Dec 1 2001 /dev/sdc7
> brw-rw---- 1 root disk 8, 40 Dec 1 2001 /dev/sdc8
> brw-rw---- 1 root disk 8, 41 Dec 1 2001 /dev/sdc9
Hmm, using udev? Any chance udev incorrectly doesn't check for going
past the end of the block devices allowed (each scsi device has 16
minors assigned, which gives you 15 partitions per device). Last device
for sdc is 8,47. 8,48 (your sdc16) is actually sdd.
> # dmesg
> [snip]
> scsi3 : ata_piix
> ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
> ata1.00: ata1: dev 0 multi count 16
> ata1.00: configured for UDMA/33
> scsi4 : ata_piix
> ata2.01: ATAPI, max MWDMA1
> ata2.01: configured for MWDMA1
> scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 3a 00 00
> SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14
> sdc15 >
> sd 3:0:0:0: Attached scsi disk sdc
> sd 3:0:0:0: Attached scsi generic sg2 type 0
> [snip]
>
> I will try to have a look later.
At least there it realized sdc15 is the last one by the looks of it.
--
Len Sorensen
Hello Tejun,
Sorry for delay but I was a bit busy this week.
Tejun Heo wrote:
> Hello, Joel.
>
> Joel Soete wrote:
>> A small update:
>> your patch also works against 2.6.20
>
> Glad to hear that.
>
>> but seems that open the door to numerous other pb:
>> 1/ pb to burn cd:
>> # md5sum cd060213.iso
>> 6a1248783a21722816b972aa9bae9d5e cd060213.iso
>>
>> # ll cd060213.iso
>> -rwxr-xr-x 1 root root 3213312 Feb 13 2006 cd060213.iso
>>
>> # dd if=/dev/sr0 bs=1 count=3213312 | md5sum
>> dd: reading `/dev/sr0': Input/output error
>> 0337e9846d17779945c5c252d4f897f0 -
>> 3129344+0 records in
>> 3129344+0 records out
>> 3129344 bytes (3.1 MB) copied, 36.6963 seconds, 85.3 kB/s
>>
>> eventhought cdrecord seems to be successfull???
>
> Hmm... 82K difference. Can you burn an iso and md5sum the files
> contained in the image and burned cd?
>
Ok comparing the content of the original image:
# mount -t iso9660 -o ro -o loop /MultiCd/cd060213.iso /mnt/cd
# find /mnt/cd -type f -exec md5sum {} \;
37149d4961c0484f2cceb1a1614b253d /mnt/cd/boot.cat
4ab996554b0e7ade115a3f284b876612 /mnt/cd/boot.msg
fbdc51c29d54dd227427b2ef90e1961e /mnt/cd/initrd.cgz
92c9a50bed71257c29f069ec5dd819fc /mnt/cd/isolinux.bin
927ce1096693b3a44af0e0d8a2ad720c /mnt/cd/isolinux.cfg
4afcf65ff8259a3bccd0cf9f91675529 /mnt/cd/scsi.cgz
4714742585da795c3a69c262ce8c35ef /mnt/cd/vmlinuz
and the content of the burned cd:
# mount /cdrom
# find /cdrom -type f -exec md5sum {} \;
37149d4961c0484f2cceb1a1614b253d /cdrom/boot.cat
4ab996554b0e7ade115a3f284b876612 /cdrom/boot.msg
fbdc51c29d54dd227427b2ef90e1961e /cdrom/initrd.cgz
92c9a50bed71257c29f069ec5dd819fc /cdrom/isolinux.bin
927ce1096693b3a44af0e0d8a2ad720c /cdrom/isolinux.cfg
4afcf65ff8259a3bccd0cf9f91675529 /cdrom/scsi.cgz
4714742585da795c3a69c262ce8c35ef /cdrom/vmlinuz
it seems ok?
What is it lost???
>> 2/ (but that should be much more related to scsi api) sdcXX > sdc15
>> doesn't works ;-(
>> # sfdisk -l /dev/sdc
>>
>> Disk /dev/sdc: 1826 cylinders, 255 heads, 63 sectors/track
>> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
>>
>> Device Boot Start End #cyls #blocks Id System
>> /dev/sdc1 * 0+ 195 196- 1574338+ b W95 FAT32
>> /dev/sdc2 196 1825 1630 13092975 5 Extended
[snip]
>> /dev/sdc23 881+ 1533 653- 5245191 83 Linux
>> /dev/sdc24 1795 1825 31 249007+ 83 Linux
>
> Whee, you have 24 partitions?
yes: it was dated from the early time I was testing various distro to choose one ;-)
> Due to the way SCSI block device numbers
> are laid out, SCSI supports only upto 15 partitions per device.
>
Ah, I never had chance to use a disk array with fc connection on one of my linux boxe, so I don't know how can it works with
up to 255 luns?
Thanks again,
Joel
Hello Lennart,
Lennart Sorensen wrote:
> On Tue, Feb 13, 2007 at 05:35:32PM +0000, Joel Soete wrote:
>> A small update:
>> your patch also works against 2.6.20
>>
>> but seems that open the door to numerous other pb:
>> 1/ pb to burn cd:
>> # md5sum cd060213.iso
>> 6a1248783a21722816b972aa9bae9d5e cd060213.iso
>>
>> # ll cd060213.iso
>> -rwxr-xr-x 1 root root 3213312 Feb 13 2006 cd060213.iso
>>
>> # dd if=/dev/sr0 bs=1 count=3213312 | md5sum
>> dd: reading `/dev/sr0': Input/output error
>> 0337e9846d17779945c5c252d4f897f0 -
>> 3129344+0 records in
>> 3129344+0 records out
>> 3129344 bytes (3.1 MB) copied, 36.6963 seconds, 85.3 kB/s
>>
>> eventhought cdrecord seems to be successfull???
>
> Has that ever worked by any method?
Yes here was some test made some time ago (not so far):
>> On Sun January 8 2006 09:28, you wrote:
> cdrecord: No write mode specified.
> cdrecord: Asuming -tao mode.
> cdrecord: Future versions of cdrecord may have different drive dependent
> defaults.
> cdrecord: Continuing in 5 seconds...
> cdrecord: Warning: Running on Linux-2.6.15-686
> cdrecord: There are unsettled issues with Linux-2.5 and newer.
> cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
> scsidev: '/dev/hdb'
> devname: '/dev/hdb'
> scsibus: -2 target: -2 lun: -2
> Warning: Open by 'devname' is unintentional and not supported.
> Linux sg driver version: 3.5.27
> cdrecord: Warning: using inofficial version of libscg (ubuntu-0.8ubuntu1
> '@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J.
> Schilling').
> SCSI buffer size: 64512
> cdrecord: Asked for SCSI I/O buffer size 64512 bytes, could only get 20480.
> Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C) 1995-2005
> Joerg Schilling
> NOTE: this version of cdrecord is an inofficial (modified) release of
> cdrecord
> and thus may have bugs that are not present in the original version.
> Please send bug reports and support requests to
> <[email protected]>.
> The original author should not be bothered with problems of this
> version.
>
> TOC Type: 1 = CD-ROM
> Using libscg version 'ubuntu-0.8ubuntu1'.
> atapi: 1
> Device type : Removable CD-ROM
> Version : 0
> Response Format: 1
> Vendor_info : 'PHILIPS '
> Identifikation : 'CDD3610 CD-R/RW '
> Revision : '3.09'
> Device seems to be: Generic mmc CD-RW.
> Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
> Driver flags : MMC SWABAUDIO
> Supported modes: TAO PACKET RAW/R16
> Drive buf size : 786432 = 768 KB
> FIFO size : 4194304 = 4096 KB
> Track 01: data 546 MB
> Total size: 627 MB (62:11.78) = 279884 sectors
> Lout start: 628 MB (62:13/59) = 279884 sectors
> Current Secsize: 2048
> ATIP start of lead in: -11637 (97:26/63)
> ATIP start of lead out: 337350 (75:00/00)
> Disk type: Phase change
> Manuf. index: 3
> Manufacturer: CMC Magnetics Corporation
> Blocks total: 337350 Blocks current: 337350 Blocks remaining: 57466
> Starting to write CD/DVD at speed 2 in real TAO mode for single session.
> Waiting for reader process to fill input buffer ... input buffer ready.
> Performing OPC...
> Starting new track at sector: 0
> Track 01: 546 of 546 MB written (fifo 100%) [buf 94%] 2.0x.
> Track 01: Total bytes read/written: 573198336/573198336 (279882 sectors).
> Writing time: 1878.179s
> Average write speed 2.0x.
> Min drive buffer fill was 94%
> Fixating...
> Fixating time: 167.622s
> cdrecord: fifo had 27989 puts and 27989 gets.
> cdrecord: fifo was 0 times empty and 27757 times full, min fill was 98%.
>
[snip]
> # readcd dev=/dev/hdb f=- | md5sum
> Read speed: 1059 kB/s (CD 6x, DVD 0x).
> Write speed: 353 kB/s (CD 2x, DVD 0x).
> Capacity: 279884 Blocks = 559768 kBytes = 546 MBytes = 573 prMB
> Sectorsize: 2048 Bytes
> Copy from SCSI (0,1,0) disk to file '-'
> end: 279884
> readcd: Success. read_g1: scsi sendcmd: no error
> CDB: 28 00 00 04 45 48 00 00 04 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes:
> Sense Key: 0xFFFFFFFF [], Segment 0
> Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.005s timeout 40s
> readcd: Success. Cannot read source disk
> readcd: Retrying from sector 279880.
> ....~~-~~~+~~~-~~~+~~~-~~~+~
>
[snip]
> # ll
> total 1150848
> [...]
> -rw-r----- 1 root root 604082176 Jan 15 12:22 hppa-cvs-20060115.iso
>
> i.e. Block_Number = 604082176 / 2048 = 294962
>
>
> # md5sum hppa-cvs-20060115.iso
> 1141489a8b914daff5cca790882fe277 hppa-cvs-20060115.iso
>
> # dd bs=2048 count=294962 if=/dev/hdb | md5sum
> 294962+0 records in
> 294962+0 records out
> 604082176 bytes (604 MB) copied, 676.972 seconds, 892 kB/s
> 1141489a8b914daff5cca790882fe277 -
>
> ;<)
more same method here:
# dd if=/dev/hdd bs=2048 count=1569 | md5sum
dd: reading `/dev/hdd': Input/output error
1528+0 records in
1528+0 records out
3129344 bytes (3.1 MB) copied, 10.1961 seconds, 307 kB/s
0337e9846d17779945c5c252d4f897f0 -
is the same wrong results.
> I have always had to use readcd
> along with passing the correct number of sectors on the CD to get a
> proper matching image. dd always seems to end up reading some junk past
> the end of the disc.
>
mmm I always used successfully dd method at my office with scsi cdrom drive (even for bootable disk).
>> 2/ (but that should be much more related to scsi api) sdcXX > sdc15 doesn't
>> works ;-(
>> # sfdisk -l /dev/sdc
>>
>> Disk /dev/sdc: 1826 cylinders, 255 heads, 63 sectors/track
>> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
>>
>> Device Boot Start End #cyls #blocks Id System
>> /dev/sdc1 * 0+ 195 196- 1574338+ b W95 FAT32
>> /dev/sdc2 196 1825 1630 13092975 5 Extended
>> /dev/sdc3 0 - 0 0 0 Empty
[snip]
>> /dev/sdc23 881+ 1533 653- 5245191 83 Linux
>> /dev/sdc24 1795 1825 31 249007+ 83 Linux
>
> I have to ask: What are all those partitions?
>
It came from an age (see >> brw-rw---- 1 root disk 8, 32 Dec 1 2001 /dev/sdc)
when 15Gb disk was enough to test severall Linux distro ;-)
At the same time I was also working with a distro runing on a x486 100Mhz, a few ram and 128Mb of disk ;-)
>> # mount /dev/sdc22 /4free
>> mount: /dev/sdc22 is not a valid block device
>>
>> # ll /dev/sdc*
>> brw-rw---- 1 root disk 8, 32 Dec 1 2001 /dev/sdc
>> brw-rw---- 1 root disk 8, 33 Dec 1 2001 /dev/sdc1
>> brw-rw---- 1 root disk 8, 42 Dec 1 2001 /dev/sdc10
>> brw-rw---- 1 root disk 8, 43 Dec 1 2001 /dev/sdc11
>> brw-rw---- 1 root disk 8, 44 Dec 1 2001 /dev/sdc12
>> brw-rw---- 1 root disk 8, 45 Dec 1 2001 /dev/sdc13
>> brw-rw---- 1 root disk 8, 46 Dec 1 2001 /dev/sdc14
>> brw-rw---- 1 root disk 8, 47 Dec 1 2001 /dev/sdc15
>> brw-r--r-- 1 root root 8, 48 Feb 13 16:26 /dev/sdc16
>> brw-r--r-- 1 root root 8, 49 Feb 13 16:26 /dev/sdc17
>> brw-r--r-- 1 root root 8, 50 Feb 13 16:26 /dev/sdc18
>> brw-r--r-- 1 root root 8, 51 Feb 13 16:27 /dev/sdc19
>> brw-rw---- 1 root disk 8, 34 Dec 1 2001 /dev/sdc2
>> brw-r--r-- 1 root root 8, 52 Feb 13 16:27 /dev/sdc20
>> brw-r--r-- 1 root root 8, 53 Feb 13 16:27 /dev/sdc21
>> brw-r--r-- 1 root root 8, 54 Feb 13 16:27 /dev/sdc22
>> brw-r--r-- 1 root root 8, 55 Feb 13 16:27 /dev/sdc23
>> brw-r--r-- 1 root root 8, 56 Feb 13 16:27 /dev/sdc24
>> brw-rw---- 1 root disk 8, 35 Dec 1 2001 /dev/sdc3
>> brw-rw---- 1 root disk 8, 36 Dec 1 2001 /dev/sdc4
>> brw-rw---- 1 root disk 8, 37 Dec 1 2001 /dev/sdc5
>> brw-rw---- 1 root disk 8, 38 Dec 1 2001 /dev/sdc6
>> brw-rw---- 1 root disk 8, 39 Dec 1 2001 /dev/sdc7
>> brw-rw---- 1 root disk 8, 40 Dec 1 2001 /dev/sdc8
>> brw-rw---- 1 root disk 8, 41 Dec 1 2001 /dev/sdc9
>
> Hmm, using udev? Any chance udev incorrectly doesn't check for going
> past the end of the block devices allowed (each scsi device has 16
> minors assigned, which gives you 15 partitions per device). Last device
> for sdc is 8,47. 8,48 (your sdc16) is actually sdd.
>
Ah ok I wasn't aware.
Thanks for help,
Joel
Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> On Tuesday 13 February 2007 18:35, Joel Soete wrote:
>
>> scsi3 : ata_piix
>> ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
>> ata1.00: ata1: dev 0 multi count 16
>> ata1.00: configured for UDMA/33
>
> <...>
>
>> scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
>
> IDE driver with CONFIG_IDEDMA_IVB=y should give you UDMA/66.
>
I didn't find this config option but most probably because I remove IDE support from my kernel to test this libata?
mmm btw, I still have to check how to access my floppy with libata?
that said as far as:
# dmesg
[snip]
ata_piix 0000:00:07.1: version 2.00ac7
ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
scsi3 : ata_piix
[snip]
(sorry, it seems that I forgot to copy it)
it make sense to me to limit to this bus capability?
> Could you send me output of "hdparm --Istdout /dev/sdc" command?
>
# hdparm --Istdout /dev/sdc
/dev/sdc:
045a 3fff 0000 0010 7e00 5332 003f 0000
0000 5154 3937 3330 3036 3332 3633 3937
2020 2020 2020 2020 0003 0344 0004 4130
332e 3039 3030 5155 414e 5455 4d20 4649
5245 4241 4c4c 6c63 7431 3020 3135 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 0f00 4000 0200 0200 0007 3fff 0010
003f fc10 00fb 0110 a500 01bf 0000 0007
0003 0078 0078 0078 0078 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
001e 0011 346b 4001 4000 3468 0001 4000
041f 0008 0000 0000 fffe 0040 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0001 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
>> scsi4 : ata_piix
>> ata2.01: ATAPI, max MWDMA1
>> ata2.01: configured for MWDMA1
>
> and "hdparm --Istdout /dev/sr0"
>
# hdparm --Istdout /dev/sr0
/dev/sr0:
HDIO_DRIVE_CMD(identify) failed: Input/output error
> [ max speed == MWDMA1 is possible but quite unusual ]
>
sorry that wouldn't help ;-(
Thanks for feedback,
Joel
> Thanks,
> Bart
>
>
On Saturday 17 February 2007 13:07, Joel Soete wrote:
>
> Bartlomiej Zolnierkiewicz wrote:
> > Hi,
> >
> > On Tuesday 13 February 2007 18:35, Joel Soete wrote:
> >
> >> scsi3 : ata_piix
> >> ata1.00: ATA-4, max UDMA/66, 29336832 sectors: LBA
> >> ata1.00: ata1: dev 0 multi count 16
> >> ata1.00: configured for UDMA/33
> >
> > <...>
> >
> >> scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
> >
> > IDE driver with CONFIG_IDEDMA_IVB=y should give you UDMA/66.
> >
> I didn't find this config option but most probably because I remove IDE support from my kernel to test this libata?
Yes, it is the last option in the IDE config menu.
> mmm btw, I still have to check how to access my floppy with libata?
>
> that said as far as:
> # dmesg
> [snip]
> ata_piix 0000:00:07.1: version 2.00ac7
> ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
> ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
> scsi3 : ata_piix
> [snip]
> (sorry, it seems that I forgot to copy it)
>
> it make sense to me to limit to this bus capability?
Yes, since the controller's max UDMA mode is UDMA/33.
> > Could you send me output of "hdparm --Istdout /dev/sdc" command?
> >
> # hdparm --Istdout /dev/sdc
>
> /dev/sdc:
> 045a 3fff 0000 0010 7e00 5332 003f 0000
> 0000 5154 3937 3330 3036 3332 3633 3937
> 2020 2020 2020 2020 0003 0344 0004 4130
> 332e 3039 3030 5155 414e 5455 4d20 4649
> 5245 4241 4c4c 6c63 7431 3020 3135 2020
> 2020 2020 2020 2020 2020 2020 2020 8010
> 0000 0f00 4000 0200 0200 0007 3fff 0010
> 003f fc10 00fb 0110 a500 01bf 0000 0007
> 0003 0078 0078 0078 0078 0000 0000 0000
> 0000 0000 0000 0000 0000 0000 0000 0000
> 001e 0011 346b 4001 4000 3468 0001 4000
> 041f 0008 0000 0000 fffe 0040 0000 0000
the word 88 == 0x041f => max UDMA mode is UDMA/66
the word 93 == 0x0040 => no 80-wire cable detected
However it doesn't really matter because controller itself
is limited to UDMA/33.
Thanks,
Bart
On Sat, Feb 17, 2007 at 11:33:53AM +0000, Joel Soete wrote:
> Hello Lennart,
>
> Lennart Sorensen wrote:
> >On Tue, Feb 13, 2007 at 05:35:32PM +0000, Joel Soete wrote:
> >>A small update:
> >>your patch also works against 2.6.20
> >>
> >>but seems that open the door to numerous other pb:
> >>1/ pb to burn cd:
> >># md5sum cd060213.iso
> >>6a1248783a21722816b972aa9bae9d5e cd060213.iso
> >>
> >># ll cd060213.iso
> >>-rwxr-xr-x 1 root root 3213312 Feb 13 2006 cd060213.iso
> >>
> >># dd if=/dev/sr0 bs=1 count=3213312 | md5sum
> >>dd: reading `/dev/sr0': Input/output error
> >>0337e9846d17779945c5c252d4f897f0 -
> >>3129344+0 records in
> >>3129344+0 records out
> >>3129344 bytes (3.1 MB) copied, 36.6963 seconds, 85.3 kB/s
> >>
> >>eventhought cdrecord seems to be successfull???
> >
> >Has that ever worked by any method?
>
> Yes here was some test made some time ago (not so far):
> >> On Sun January 8 2006 09:28, you wrote:
> > cdrecord: No write mode specified.
> > cdrecord: Asuming -tao mode.
> > cdrecord: Future versions of cdrecord may have different drive dependent
> > defaults.
> > cdrecord: Continuing in 5 seconds...
> > cdrecord: Warning: Running on Linux-2.6.15-686
> > cdrecord: There are unsettled issues with Linux-2.5 and newer.
> > cdrecord: If you have unexpected problems, please try Linux-2.4 or
> Solaris.
> > scsidev: '/dev/hdb'
> > devname: '/dev/hdb'
> > scsibus: -2 target: -2 lun: -2
> > Warning: Open by 'devname' is unintentional and not supported.
> > Linux sg driver version: 3.5.27
> > cdrecord: Warning: using inofficial version of libscg (ubuntu-0.8ubuntu1
> > '@(#)scsitransp.c 1.91 04/06/17 Copyright 1988,1995,2000-2004 J.
> > Schilling').
> > SCSI buffer size: 64512
> > cdrecord: Asked for SCSI I/O buffer size 64512 bytes, could only get
> 20480.
> > Cdrecord-Clone 2.01.01a03 (i686-pc-linux-gnu) Copyright (C) 1995-2005
> > Joerg Schilling
> > NOTE: this version of cdrecord is an inofficial (modified) release of
> > cdrecord
> > and thus may have bugs that are not present in the original version.
> > Please send bug reports and support requests to
> > <[email protected]>.
> > The original author should not be bothered with problems of this
> > version.
> >
> > TOC Type: 1 = CD-ROM
> > Using libscg version 'ubuntu-0.8ubuntu1'.
> > atapi: 1
> > Device type : Removable CD-ROM
> > Version : 0
> > Response Format: 1
> > Vendor_info : 'PHILIPS '
> > Identifikation : 'CDD3610 CD-R/RW '
> > Revision : '3.09'
> > Device seems to be: Generic mmc CD-RW.
> > Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
> > Driver flags : MMC SWABAUDIO
> > Supported modes: TAO PACKET RAW/R16
> > Drive buf size : 786432 = 768 KB
> > FIFO size : 4194304 = 4096 KB
> > Track 01: data 546 MB
> > Total size: 627 MB (62:11.78) = 279884 sectors
> > Lout start: 628 MB (62:13/59) = 279884 sectors
> > Current Secsize: 2048
> > ATIP start of lead in: -11637 (97:26/63)
> > ATIP start of lead out: 337350 (75:00/00)
> > Disk type: Phase change
> > Manuf. index: 3
> > Manufacturer: CMC Magnetics Corporation
> > Blocks total: 337350 Blocks current: 337350 Blocks remaining: 57466
> > Starting to write CD/DVD at speed 2 in real TAO mode for single session.
> > Waiting for reader process to fill input buffer ... input buffer ready.
> > Performing OPC...
> > Starting new track at sector: 0
> > Track 01: 546 of 546 MB written (fifo 100%) [buf 94%] 2.0x.
> > Track 01: Total bytes read/written: 573198336/573198336 (279882 sectors).
> > Writing time: 1878.179s
> > Average write speed 2.0x.
> > Min drive buffer fill was 94%
> > Fixating...
> > Fixating time: 167.622s
> > cdrecord: fifo had 27989 puts and 27989 gets.
> > cdrecord: fifo was 0 times empty and 27757 times full, min fill was 98%.
> >
> [snip]
> > # readcd dev=/dev/hdb f=- | md5sum
> > Read speed: 1059 kB/s (CD 6x, DVD 0x).
> > Write speed: 353 kB/s (CD 2x, DVD 0x).
> > Capacity: 279884 Blocks = 559768 kBytes = 546 MBytes = 573 prMB
> > Sectorsize: 2048 Bytes
> > Copy from SCSI (0,1,0) disk to file '-'
> > end: 279884
> > readcd: Success. read_g1: scsi sendcmd: no error
> > CDB: 28 00 00 04 45 48 00 00 04 00
> > status: 0x2 (CHECK CONDITION)
> > Sense Bytes:
> > Sense Key: 0xFFFFFFFF [], Segment 0
> > Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
> > Sense flags: Blk 0 (not valid)
> > cmd finished after 0.005s timeout 40s
> > readcd: Success. Cannot read source disk
> > readcd: Retrying from sector 279880.
> > ....~~-~~~+~~~-~~~+~~~-~~~+~
Hmm, readcd was trying to read 279884 blocks, while cdrecord said it
wrote 279882 blocks.
> [snip]
> > # ll
> > total 1150848
> > [...]
> > -rw-r----- 1 root root 604082176 Jan 15 12:22 hppa-cvs-20060115.iso
> >
> > i.e. Block_Number = 604082176 / 2048 = 294962
> >
> >
> > # md5sum hppa-cvs-20060115.iso
> > 1141489a8b914daff5cca790882fe277 hppa-cvs-20060115.iso
> >
> > # dd bs=2048 count=294962 if=/dev/hdb | md5sum
> > 294962+0 records in
> > 294962+0 records out
> > 604082176 bytes (604 MB) copied, 676.972 seconds, 892 kB/s
> > 1141489a8b914daff5cca790882fe277 -
> >
> > ;<)
> more same method here:
> # dd if=/dev/hdd bs=2048 count=1569 | md5sum
> dd: reading `/dev/hdd': Input/output error
> 1528+0 records in
> 1528+0 records out
> 3129344 bytes (3.1 MB) copied, 10.1961 seconds, 307 kB/s
> 0337e9846d17779945c5c252d4f897f0 -
There always seems to have been any issue with reading blocks from a cd
getting broken by the kernel doing readahead and getting failures by
trying to read past the end of the disc even though the user never asked
it to. Sometimes your size just happens to hit a safe block size so the
readahead doesn't break.
> is the same wrong results.
>
> mmm I always used successfully dd method at my office with scsi cdrom drive
> (even for bootable disk).
Well it seems some disks can be read that way, others can not.
> It came from an age (see >> brw-rw---- 1 root disk 8, 32 Dec 1 2001
> /dev/sdc)
> when 15Gb disk was enough to test severall Linux distro ;-)
> At the same time I was also working with a distro runing on a x486 100Mhz,
> a few ram and 128Mb of disk ;-)
Well that makes some sense. I always though testing a distribution
meant installing it and using it a bit, andif it wasn't right, you
installed the next one. I have never had more than one installed at a
time myself.
--
Len Sorensen
[snip]
>
> Hmm, readcd was trying to read 279884 blocks, while cdrecord said it
> wrote 279882 blocks.
>
yes and seems to be always the same:
with new burned cd I got:
# ll /MultiCd/cd060213.iso
-rwxr-xr-x 1 root root 3213312 Feb 13 2006 /MultiCd/cd060213.iso
i.e. 3213312/2048 == 1569
while:
readcd dev=/dev/hdd f=- | md5sum
Read speed: 1059 kB/s (CD 6x, DVD 0x).
Write speed: 353 kB/s (CD 2x, DVD 0x).
Capacity: 1571 Blocks = 3142 kBytes = 3 MBytes = 3 prMB
Sectorsize: 2048 Bytes
Copy from SCSI (1,1,0) disk to file '-'
end: 1571
Errno: 0 (Success), read_g1 scsi sendcmd: no error
CDB: 28 00 00 00 06 00 00 00 23 00
status: 0x2 (CHECK CONDITION)
Sense Bytes:
Sense Key: 0xFFFFFFFF [], Segment 0
Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.014s timeout 40s
readcd: Success. Cannot read source disk
readcd: Retrying from sector 1536.
so always Capacity == original image size + 2 ?
[snip]
>
> There always seems to have been any issue with reading blocks from a cd
> getting broken by the kernel doing readahead and getting failures by
> trying to read past the end of the disc even though the user never asked
> it to. Sometimes your size just happens to hit a safe block size so the
> readahead doesn't break.
>
btw this tips:
readcd dev=/dev/hdd sectors=0-1569 f=- | md5sum
Read speed: 1059 kB/s (CD 6x, DVD 0x).
Write speed: 353 kB/s (CD 2x, DVD 0x).
Capacity: 1571 Blocks = 3142 kBytes = 3 MBytes = 3 prMB
Sectorsize: 2048 Bytes
Copy from SCSI (1,1,0) disk to file '-'
end: 1569
addr: 1569 cnt: 33
Time total: 5.436sec
Read 3138.00 kB at 577.3 kB/sec.
6a1248783a21722816b972aa9bae9d5e -
(adding sectors=0-1569 : 1569 being the size of the original image)
seems to work fine
# md5sum /MultiCd/cd060213.iso
6a1248783a21722816b972aa9bae9d5e /MultiCd/cd060213.iso
>> is the same wrong results.
>>
>> mmm I always used successfully dd method at my office with scsi cdrom drive
>> (even for bootable disk).
>
> Well it seems some disks can be read that way, others can not.
>
I would be curious to read same cd on scsi cdrom (at the office)?
Cheers,
Joel
> [snip]
> >
> > Hmm, readcd was trying to read 279884 blocks, while cdrecord said it
> > wrote 279882 blocks.
> >
> yes and seems to be always the same:
> with new burned cd I got:
> # ll /MultiCd/cd060213.iso
> -rwxr-xr-x 1 root root 3213312 Feb 13 2006 /MultiCd/cd060213.iso
>
> i.e. 3213312/2048 == 1569
>
> while:
> readcd dev=/dev/hdd f=- | md5sum
> Read speed: 1059 kB/s (CD 6x, DVD 0x).
> Write speed: 353 kB/s (CD 2x, DVD 0x).
> Capacity: 1571 Blocks = 3142 kBytes = 3 MBytes = 3 prMB
> Sectorsize: 2048 Bytes
> Copy from SCSI (1,1,0) disk to file '-'
> end: 1571
> Errno: 0 (Success), read_g1 scsi sendcmd: no error
> CDB: 28 00 00 00 06 00 00 00 23 00
> status: 0x2 (CHECK CONDITION)
> Sense Bytes:
> Sense Key: 0xFFFFFFFF [], Segment 0
> Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0
> Sense flags: Blk 0 (not valid)
> cmd finished after 0.014s timeout 40s
> readcd: Success. Cannot read source disk
> readcd: Retrying from sector 1536.
>
> so always Capacity == original image size + 2 ?
>
> [snip]
> >
> > There always seems to have been any issue with reading blocks from a cd
> > getting broken by the kernel doing readahead and getting failures by
> > trying to read past the end of the disc even though the user never asked
> > it to. Sometimes your size just happens to hit a safe block size so the
> > readahead doesn't break.
> >
> btw this tips:
> readcd dev=/dev/hdd sectors=0-1569 f=- | md5sum
> Read speed: 1059 kB/s (CD 6x, DVD 0x).
> Write speed: 353 kB/s (CD 2x, DVD 0x).
> Capacity: 1571 Blocks = 3142 kBytes = 3 MBytes = 3 prMB
> Sectorsize: 2048 Bytes
> Copy from SCSI (1,1,0) disk to file '-'
> end: 1569
> addr: 1569 cnt: 33
> Time total: 5.436sec
> Read 3138.00 kB at 577.3 kB/sec.
> 6a1248783a21722816b972aa9bae9d5e -
>
> (adding sectors=0-1569 : 1569 being the size of the original image)
>
> seems to work fine
> # md5sum /MultiCd/cd060213.iso
> 6a1248783a21722816b972aa9bae9d5e /MultiCd/cd060213.iso
>
> >> is the same wrong results.
> >>
> >> mmm I always used successfully dd method at my office with scsi cdrom drive
> >> (even for bootable disk).
> >
> > Well it seems some disks can be read that way, others can not.
> >
> I would be curious to read same cd on scsi cdrom (at the office)?
>
well here are the results with the cd I burned at home and in a scsi cd rw drive:
# dd if=/dev/rdsk/c1t4d0 bs=2048 | md5sum
1569+0 records in
1569+0 records out
6a1248783a21722816b972aa9bae9d5e -
and also with readcd but an older release:
# readcd -version
readcd 1.11a19 (hppa1.1-hp-hpux11.00) Copyright (C) 1987, 1995-2002 J?rg Schilling
# readcd dev=1,4,0 f=- | md5sum
Capacity: 1569 Blocks = 3138 kBytes = 3 MBytes = 3 prMB
Sectorsize: 2048 Bytes
Copy from SCSI (1,4,0) disk to file '-'
end: 1569
addr: 1569 cnt: 19
Time total: 6.239sec
Read 3138.00 kB at 503.0 kB/sec.
6a1248783a21722816b972aa9bae9d5e -
I am very confused: cdrecord finaly do well its job on ide drive but what went
wrong for the check (cdrom drive? (but I don't have another model to test) or
some code in the kernel? (I don't think to have a small chance to put this ide
drive on a *nix system which could support ide and scsi hw)).
Any idea?
Cheers,
Joel
>
>
---
Scarlet One Unlimited
Free national calls, surf up to 6 Mbit/s, 50 GB download volume
For only EUR 49,95 per month. No Belgacom subscription needed. All in!
http://www.scarlet.be
Joel Soete wrote:
> Ok comparing the content of the original image:
> # mount -t iso9660 -o ro -o loop /MultiCd/cd060213.iso /mnt/cd
> # find /mnt/cd -type f -exec md5sum {} \;
> 37149d4961c0484f2cceb1a1614b253d /mnt/cd/boot.cat
> 4ab996554b0e7ade115a3f284b876612 /mnt/cd/boot.msg
> fbdc51c29d54dd227427b2ef90e1961e /mnt/cd/initrd.cgz
> 92c9a50bed71257c29f069ec5dd819fc /mnt/cd/isolinux.bin
> 927ce1096693b3a44af0e0d8a2ad720c /mnt/cd/isolinux.cfg
> 4afcf65ff8259a3bccd0cf9f91675529 /mnt/cd/scsi.cgz
> 4714742585da795c3a69c262ce8c35ef /mnt/cd/vmlinuz
>
> and the content of the burned cd:
> # mount /cdrom
> # find /cdrom -type f -exec md5sum {} \;
> 37149d4961c0484f2cceb1a1614b253d /cdrom/boot.cat
> 4ab996554b0e7ade115a3f284b876612 /cdrom/boot.msg
> fbdc51c29d54dd227427b2ef90e1961e /cdrom/initrd.cgz
> 92c9a50bed71257c29f069ec5dd819fc /cdrom/isolinux.bin
> 927ce1096693b3a44af0e0d8a2ad720c /cdrom/isolinux.cfg
> 4afcf65ff8259a3bccd0cf9f91675529 /cdrom/scsi.cgz
> 4714742585da795c3a69c262ce8c35ef /cdrom/vmlinuz
>
> it seems ok?
>
> What is it lost???
Probably length got screwed somewhere. Hmm... will do some testing.
>>> 2/ (but that should be much more related to scsi api) sdcXX > sdc15
>>> doesn't works ;-(
>>> # sfdisk -l /dev/sdc
>>>
>>> Disk /dev/sdc: 1826 cylinders, 255 heads, 63 sectors/track
>>> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting
>>> from 0
>>>
>>> Device Boot Start End #cyls #blocks Id System
>>> /dev/sdc1 * 0+ 195 196- 1574338+ b W95 FAT32
>>> /dev/sdc2 196 1825 1630 13092975 5 Extended
> [snip]
>>> /dev/sdc23 881+ 1533 653- 5245191 83 Linux
>>> /dev/sdc24 1795 1825 31 249007+ 83 Linux
>>
>> Whee, you have 24 partitions?
> yes: it was dated from the early time I was testing various distro to
> choose one ;-)
>
>> Due to the way SCSI block device numbers are laid out, SCSI supports
>> only upto 15 partitions per device.
>>
> Ah, I never had chance to use a disk array with fc connection on one of
> my linux boxe, so I don't know how can it works with up to 255 luns?
Each lun is handled as a separate scsi device and as such allocated 16
minor numbers if it is a block device. Will check if the minor number
limit can be worked around somehow.
--
tejun
On 2/11/07, Tejun Heo <[email protected]> wrote:
> Please test the attached patch over 2.6.20.
No luck for me. I'm using pata_sis. Some error bits:
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 16x mode
agpgart: SiS delay workaround: giving bridge time to recover.
agpgart: Putting AGP V3 device at 0000:01:00.0 into 16x mode
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x24)
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x28 data 4096 in
res 51/51:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
ata2: port is slow to respond, please be patient (Status 0xd0)
ata2: port failed to respond (30 secs, Status 0xd0)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x24)
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x28 data 4096 in
res 51/51:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
ata2: port is slow to respond, please be patient (Status 0xd0)
ata2: port failed to respond (30 secs, Status 0xd0)
ata2: soft resetting port
ata2.00: configured for UDMA/33
ata2: EH complete
ata2.00: qc timeout (cmd 0xa0)
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: (BMDMA stat 0x24)
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x28 data 4096 in
res 51/51:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
ata2: port is slow to respond, please be patient (Status 0xd0)
Compressed dmesg attached. Thanks.