From: Martin Hicks <mort@bork.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: M-Systems SATA FFD fails IDENTIFY cmd
Date: Tue, 31 Oct 2006 09:57:43 -0500 [thread overview]
Message-ID: <20061031145743.GC4410@socrates.bork.org> (raw)
In-Reply-To: <45472328.4030504@gmail.com>
[-- 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 --]
prev parent reply other threads:[~2006-10-31 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061031145743.GC4410@socrates.bork.org \
--to=mort@bork.org \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).