* M-Systems SATA FFD fails IDENTIFY cmd
@ 2006-10-24 18:20 Martin Hicks
2006-10-31 10:19 ` Tejun Heo
0 siblings, 1 reply; 3+ messages in thread
From: Martin Hicks @ 2006-10-24 18:20 UTC (permalink / raw)
To: linux-ide
[-- Attachment #1: Type: text/plain, Size: 2989 bytes --]
Hi,
I've got a few M-Systems SATA FFD 2.5" solid state disks that behave
strangely with some drivers.
When probing the disks on an Asus P5P800-MX motherboard's onboard SATA
and with an embedded PPC440gx machine with an on-board Intel 31244
(sata_vsc) SATA controller I get the following:
mort@seaking:~$ sudo modprobe ata_piix
Oct 24 12:54:15 localhost kernel: ata_piix 0000:00:1f.2: version 2.00ac6
Oct 24 12:54:15 localhost kernel: ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
Oct 24 12:54:15 localhost kernel: PCI: Enabling device 0000:00:1f.2 (0000 -> 0001)
Oct 24 12:54:15 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
Oct 24 12:54:15 localhost kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
Oct 24 12:54:15 localhost kernel: ata11: SATA max UDMA/133 cmd 0xAC00 ctl 0xA882 bmdma 0xA400 irq 16
Oct 24 12:54:15 localhost kernel: ata12: SATA max UDMA/133 cmd 0xA800 ctl 0xA482 bmdma 0xA408 irq 16
Oct 24 12:54:15 localhost kernel: scsi10 : ata_piix
Oct 24 12:54:45 localhost kernel: ata11.00: qc timeout (cmd 0xec)
Oct 24 12:54:45 localhost kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Oct 24 12:54:46 localhost kernel: ata11.00: ATA-6, max UDMA/100, 16074752 sectors: LBA
Oct 24 12:54:46 localhost kernel: ata11.00: ata11: dev 0 multi count 2
Oct 24 12:54:46 localhost kernel: ata11.00: applying bridge limits
Oct 24 12:54:46 localhost kernel: ata11.00: configured for UDMA/100
Oct 24 12:54:46 localhost kernel: scsi11 : ata_piix
Oct 24 12:54:46 localhost kernel: ATA: abnormal status 0x7F on port 0xA807
Oct 24 12:54:46 localhost kernel: scsi 10:0:0:0: Direct-Access ATA M-Systems FFD Se 1.03 PQ: 0 ANSI: 5
Oct 24 12:54:46 localhost kernel: SCSI device sda: 16074752 512-byte hdwr sectors (8230 MB)
Oct 24 12:54:46 localhost kernel: sda: Write Protect is off
Oct 24 12:54:46 localhost kernel: sda: Mode Sense: 00 3a 00 00
Oct 24 12:54:46 localhost kernel: SCSI device sda: drive cache: write back
Oct 24 12:54:46 localhost kernel: SCSI device sda: 16074752 512-byte hdwr sectors (8230 MB)
Oct 24 12:54:46 localhost kernel: sda: Write Protect is off
Oct 24 12:54:46 localhost kernel: sda: Mode Sense: 00 3a 00 00
Oct 24 12:54:46 localhost kernel: SCSI device sda: drive cache: write back
Oct 24 12:54:46 localhost kernel: sda: unknown partition table
Oct 24 12:54:46 localhost kernel: sd 10:0:0:0: Attached scsi disk sda
As you can see the INQUIRY command fails after 30 seconds. The x86/ata_piix
machine is running 2.6.19-rc3. The PPC/sata_vsc machine is running
2.6.18.
Two other controllers were tested on the x86 machine and they both
worked as expected:
Silicon Image, Inc. Adaptec AAR-1210SA SATA HostRAID Controller (rev 02)
Promise Technology, Inc. PDC20575 (SATAII150 TX2plus) (rev 02)
Is this likely a problem with the M-Systems drive or a libata/driver problem?
mh
--
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: M-Systems SATA FFD fails IDENTIFY cmd
2006-10-24 18:20 M-Systems SATA FFD fails IDENTIFY cmd Martin Hicks
@ 2006-10-31 10:19 ` Tejun Heo
2006-10-31 14:57 ` Martin Hicks
0 siblings, 1 reply; 3+ messages in thread
From: Tejun Heo @ 2006-10-31 10:19 UTC (permalink / raw)
To: Martin Hicks; +Cc: linux-ide
Martin Hicks wrote:
> Hi,
>
> I've got a few M-Systems SATA FFD 2.5" solid state disks that behave
> strangely with some drivers.
>
> When probing the disks on an Asus P5P800-MX motherboard's onboard SATA
> and with an embedded PPC440gx machine with an on-board Intel 31244
> (sata_vsc) SATA controller I get the following:
>
> mort@seaking:~$ sudo modprobe ata_piix
> Oct 24 12:54:15 localhost kernel: ata_piix 0000:00:1f.2: version 2.00ac6
> Oct 24 12:54:15 localhost kernel: ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
> Oct 24 12:54:15 localhost kernel: PCI: Enabling device 0000:00:1f.2 (0000 -> 0001)
> Oct 24 12:54:15 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
> Oct 24 12:54:15 localhost kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
> Oct 24 12:54:15 localhost kernel: ata11: SATA max UDMA/133 cmd 0xAC00 ctl 0xA882 bmdma 0xA400 irq 16
> Oct 24 12:54:15 localhost kernel: ata12: SATA max UDMA/133 cmd 0xA800 ctl 0xA482 bmdma 0xA408 irq 16
> Oct 24 12:54:15 localhost kernel: scsi10 : ata_piix
> Oct 24 12:54:45 localhost kernel: ata11.00: qc timeout (cmd 0xec)
> Oct 24 12:54:45 localhost kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> Oct 24 12:54:46 localhost kernel: ata11.00: ATA-6, max UDMA/100, 16074752 sectors: LBA
> Oct 24 12:54:46 localhost kernel: ata11.00: ata11: dev 0 multi count 2
> Oct 24 12:54:46 localhost kernel: ata11.00: applying bridge limits
> Oct 24 12:54:46 localhost kernel: ata11.00: configured for UDMA/100
> Oct 24 12:54:46 localhost kernel: scsi11 : ata_piix
> Oct 24 12:54:46 localhost kernel: ATA: abnormal status 0x7F on port 0xA807
> Oct 24 12:54:46 localhost kernel: scsi 10:0:0:0: Direct-Access ATA M-Systems FFD Se 1.03 PQ: 0 ANSI: 5
> Oct 24 12:54:46 localhost kernel: SCSI device sda: 16074752 512-byte hdwr sectors (8230 MB)
> Oct 24 12:54:46 localhost kernel: sda: Write Protect is off
> Oct 24 12:54:46 localhost kernel: sda: Mode Sense: 00 3a 00 00
> Oct 24 12:54:46 localhost kernel: SCSI device sda: drive cache: write back
> Oct 24 12:54:46 localhost kernel: SCSI device sda: 16074752 512-byte hdwr sectors (8230 MB)
> Oct 24 12:54:46 localhost kernel: sda: Write Protect is off
> Oct 24 12:54:46 localhost kernel: sda: Mode Sense: 00 3a 00 00
> Oct 24 12:54:46 localhost kernel: SCSI device sda: drive cache: write back
> Oct 24 12:54:46 localhost kernel: sda: unknown partition table
> Oct 24 12:54:46 localhost kernel: sd 10:0:0:0: Attached scsi disk sda
>
>
> As you can see the INQUIRY command fails after 30 seconds. The x86/ata_piix
> machine is running 2.6.19-rc3. The PPC/sata_vsc machine is running
> 2.6.18.
Can you try 2.6.19-rc3-mm1 and report the result? Thanks.
--
tejun
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: M-Systems SATA FFD fails IDENTIFY cmd
2006-10-31 10:19 ` Tejun Heo
@ 2006-10-31 14:57 ` Martin Hicks
0 siblings, 0 replies; 3+ messages in thread
From: Martin Hicks @ 2006-10-31 14:57 UTC (permalink / raw)
To: Tejun Heo; +Cc: linux-ide
[-- Attachment #1: Type: text/plain, Size: 3231 bytes --]
On Tue, Oct 31, 2006 at 07:19:20PM +0900, Tejun Heo wrote:
> Martin Hicks wrote:
> >Hi,
> >
> >As you can see the INQUIRY command fails after 30 seconds. The x86/ata_piix
> >machine is running 2.6.19-rc3. The PPC/sata_vsc machine is running
> >2.6.18.
>
> Can you try 2.6.19-rc3-mm1 and report the result? Thanks.
Its even worse because in this version it has to wait for two commands
to time out.
mort@seaking:~$ cat /proc/version
Linux version 2.6.19-rc3-mm1 (mort@seaking) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #1 SMP Tue Oct 31 09:18:36 EST 2006
Oct 31 09:44:31 localhost kernel: ata_piix 0000:00:1f.2: version 2.00ac7
Oct 31 09:44:31 localhost kernel: ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
Oct 31 09:44:31 localhost kernel: PCI: Enabling device 0000:00:1f.2 (0000 -> 0001)
Oct 31 09:44:31 localhost kernel: ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 16
Oct 31 09:44:31 localhost kernel: PCI: Setting latency timer of device 0000:00:1f.2 to 64
Oct 31 09:44:31 localhost kernel: ata3: SATA max UDMA/133 cmd 0xBC00 ctl 0xB882 bmdma 0xB400 irq 16
Oct 31 09:44:31 localhost kernel: ata4: SATA max UDMA/133 cmd 0xB800 ctl 0xB482 bmdma 0xB408 irq 16
Oct 31 09:44:31 localhost kernel: scsi2 : ata_piix
Oct 31 09:44:32 localhost kernel: ATA: abnormal status 0x7F on port 0xBC07
Oct 31 09:44:32 localhost kernel: scsi3 : ata_piix
Oct 31 09:44:32 localhost kernel: ata4.00: ATA-6, max UDMA/100, 8022016 sectors: LBA
Oct 31 09:44:32 localhost kernel: ata4.00: ata4: dev 0 multi count 2
Oct 31 09:44:32 localhost kernel: ata4.00: applying bridge limits
Oct 31 09:45:02 localhost kernel: ata4.00: qc timeout (cmd 0xef)
Oct 31 09:45:02 localhost kernel: ata4.00: failed to set xfermode (err_mask=0x4)
Oct 31 09:45:02 localhost kernel: ata4.00: limiting speed to UDMA/66
Oct 31 09:45:02 localhost kernel: ata4: failed to recover some devices, retrying in 5 secs
Oct 31 09:45:37 localhost kernel: ata4.00: qc timeout (cmd 0xec)
Oct 31 09:45:37 localhost kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Oct 31 09:45:37 localhost kernel: ata4.00: revalidation failed (errno=-5)
Oct 31 09:45:37 localhost kernel: ata4: failed to recover some devices, retrying in 5 secs
Oct 31 09:45:42 localhost kernel: ata4.00: configured for UDMA/66
Oct 31 09:45:42 localhost kernel: scsi 3:0:0:0: Direct-Access ATA M-Systems FFD Se 1.02 PQ: 0 ANSI: 5
Oct 31 09:45:42 localhost kernel: SCSI device sda: 8022016 512-byte hdwr sectors (4107 MB)
Oct 31 09:45:42 localhost kernel: sda: Write Protect is off
Oct 31 09:45:42 localhost kernel: sda: Mode Sense: 00 3a 00 00
Oct 31 09:45:42 localhost kernel: SCSI device sda: drive cache: write back
Oct 31 09:45:42 localhost kernel: SCSI device sda: 8022016 512-byte hdwr sectors (4107 MB)
Oct 31 09:45:42 localhost kernel: sda: Write Protect is off
Oct 31 09:45:42 localhost kernel: sda: Mode Sense: 00 3a 00 00
Oct 31 09:45:42 localhost kernel: SCSI device sda: drive cache: write back
Oct 31 09:45:42 localhost kernel: sda: unknown partition table
Oct 31 09:45:42 localhost kernel: sd 3:0:0:0: Attached scsi disk sda
--
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-10-31 14:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-24 18:20 M-Systems SATA FFD fails IDENTIFY cmd Martin Hicks
2006-10-31 10:19 ` Tejun Heo
2006-10-31 14:57 ` Martin Hicks
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).