From: Tejun Heo <htejun@gmail.com>
To: Torsten Kaiser <just.for.lkml@googlemail.com>
Cc: "Ip, Clarence" <CIP@harris.com>,
linux-ide@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: FW: LIBATA issue with SATA drive
Date: Fri, 19 Oct 2007 14:05:53 +0900 [thread overview]
Message-ID: <47183B31.4080002@gmail.com> (raw)
In-Reply-To: <64bb37e0710182151j6992cde3u4f9ae60aa70e22eb@mail.gmail.com>
Torsten Kaiser wrote:
> On 10/19/07, Tejun Heo <htejun@gmail.com> wrote:
>> Torsten Kaiser wrote:
>>> I'm currently using 2.6.23-mm1 and 16 boots where all good.
>>> (Apart from the unrelated failure with sata_nv and swncq...)
>> I see, a different issue then. It's just weird to see similar issues
>> popping up now after allterm the time sata_sil24 has been around.
>
> Just remebered another thing about sata_sil24 that popped up with 2.6.23-mm1.
> With this kernel version (comparing to 2.6.23-rc8-mm1) the port
> probing time goes up from ~0.5 seconds per port/drive to ~2 seconds.
> Also the SControl changed:
>
> 2.6.23-rc8-mm1:
> [ 4.110000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> 2.6.23-mm1:
> [ 5.930000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
>
> But except for increased delay during boot no errors can seen, the
> drives work normally.
Yeah, PARTIAL / SLUMBER mode restriction is lifted. Dunno whether
that's related to the increased delay tho. Will investigate.
--
tejun
next prev parent reply other threads:[~2007-10-19 5:06 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
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 [this message]
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=47183B31.4080002@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.