From: Tejun Heo <htejun@gmail.com>
To: "Ip, Clarence" <CIP@harris.com>
Cc: linux-ide@vger.kernel.org, just.for.lkml@googlemail.com,
jens.axboe@oracle.com
Subject: Re: FW: LIBATA issue with SATA drive
Date: Thu, 18 Oct 2007 13:09:33 +0900 [thread overview]
Message-ID: <4716DC7D.6050007@gmail.com> (raw)
In-Reply-To: <AF1760336DB49F43983B755855C2A46702AF744B@troe2k1.cs.myharris.net>
Hello, all.
Torsten, Clarence is reporting similar problem on 2.6.22. The original
message follows.
> I'm using the 2.6.22 sources with a Sii3132 SATA controller and a Seagate HDD.
> What I've noticed is that it often fails to boot with this configuration.
> Warm boots appear to always fail while cold boots (power-cycles) fail maybe
> 20%-50% of the time. Here's a log from my last attempt:
>
> Loading iSCSI transport class v2.0-724.
> PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
> scsi0 : sata_sil24
> scsi1 : sata_sil24
> ata1: SATA max UDMA/100 cmd 0xe1258000 ctl 0x00000000 bmdma 0x00000000 irq 0
> ata2: SATA max UDMA/100 cmd 0xe125a000 ctl 0x00000000 bmdma 0x00000000 irq 0
> ata1: SATA link down (SStatus 0 SControl 0)
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 0)
> ata2.00: qc timeout (cmd 0xec)
> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata2: failed to recover some devices, retrying in 5 secs
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 0)
> ata2.00: qc timeout (cmd 0xec)
> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata2: limiting SATA link speed to 1.5 Gbps
> ata2.00: limiting speed to UDMA7:PIO5
> ata2: failed to recover some devices, retrying in 5 secs
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 10)
> ata2.00: qc timeout (cmd 0xec)
> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
> ata2: failed to recover some devices, retrying in 5 secs
> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 10)
> ata2: EH pending after completion, repeating EH (cnt=4)
> i2c /dev entries driver
> IBM IIC driver v2.1
>
> If the boot succeeds, I have no further problems with HDD access.
> I also did not see this problem with the 2.6.17 kernel. Do you have
> any ideas as to what may be happening? We're running on a PPC440SPE
> processor.
>
> Thanks in advance,
The symptom seems very similar to yours but the kernel is 2.6.22 which
doesn't have the SG change which you found out to be broken. Can you
update us on how the testing of patched kernel went?
--
tejun
next prev parent reply other threads:[~2007-10-18 4:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 16:13 FW: LIBATA issue with SATA drive Ip, Clarence
2007-10-18 4:09 ` Tejun Heo [this message]
2007-10-18 18:52 ` Torsten Kaiser
2007-10-19 1:13 ` Tejun Heo
2007-10-19 1:32 ` Jeff Garzik
2007-10-19 2:36 ` Tejun Heo
2007-10-19 4:51 ` Torsten Kaiser
2007-10-19 5:05 ` Tejun Heo
2007-10-19 16:21 ` Torsten Kaiser
2007-10-23 2:58 ` Tejun Heo
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=4716DC7D.6050007@gmail.com \
--to=htejun@gmail.com \
--cc=CIP@harris.com \
--cc=jens.axboe@oracle.com \
--cc=just.for.lkml@googlemail.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).