From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org
Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6
Date: Tue, 11 Mar 2008 12:13:05 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0803111210010.5775@axis700.grange> (raw)
In-Reply-To: <47D66071.7010906@gmail.com>
On Tue, 11 Mar 2008, Tejun Heo wrote:
> Hello,
>
> Guennadi Liakhovetski wrote:
> > Well, I am not sure, whether it helps, tried booting with both 1.5Gbps and
> > this patch, it recovers now within 30 sec in both cold- and hot-plug
> > cases. To really state, that it has improved from about 55 sec down to 30
> > sec one would need more testing. Is this the kind of improvement you
> > expected?
>
> Not really. :-P
>
> > Can it be, that with this hardware it just cannot get better?
> > Remember, the disk is an external eSATA enclosure with a (relatively new)
> > PATA disk inside.
>
> Can you try out a shorter cable? I had a lot of troubles with eSATA +
> long cable + PMP combinations. Using shorter cable usually solves the
> problem for me.
Well, this cable is only about 50cm long, or even shorter, and using a
shorter one would be difficult there, even if I manage to get hold of one.
But, in principle, if this is not a generic ahci problem that needs to be
solved, I personally can somehow live with it. Having to wait 1 minute is
not very nice, but so far not critical.
Thanks for your help
Guennadi
---
Guennadi Liakhovetski
next prev parent reply other threads:[~2008-03-11 11:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:37 Unknown SATA PIIX PCI device ID 0x29b6 Guennadi Liakhovetski
2008-02-28 22:56 ` Alan Cox
2008-02-28 23:33 ` Guennadi Liakhovetski
2008-03-06 8:39 ` Tejun Heo
2008-03-06 11:57 ` Guennadi Liakhovetski
2008-03-06 18:02 ` Gaston, Jason D
2008-03-06 18:05 ` Jeff Garzik
2008-03-06 18:40 ` Guennadi Liakhovetski
2008-04-02 23:49 ` Gaston, Jason D
2008-04-03 0:44 ` Tejun Heo
2008-04-03 15:16 ` Gaston, Jason D
2008-04-03 16:03 ` Tejun Heo
2008-04-19 1:02 ` Gaston, Jason D
2008-04-23 6:37 ` Tejun Heo
2008-04-03 16:04 ` Jeff Garzik
2008-04-03 18:01 ` Gaston, Jason D
2008-03-07 4:51 ` Tejun Heo
2008-03-08 22:47 ` Guennadi Liakhovetski
2008-03-09 5:14 ` Tejun Heo
2008-03-09 21:24 ` Guennadi Liakhovetski
2008-03-10 0:50 ` Tejun Heo
2008-03-10 7:22 ` Guennadi Liakhovetski
2008-03-10 13:05 ` Tejun Heo
2008-03-11 10:11 ` Guennadi Liakhovetski
2008-03-11 10:35 ` Tejun Heo
2008-03-11 11:13 ` Guennadi Liakhovetski [this message]
2008-03-11 11:37 ` Tejun Heo
2008-02-29 0:23 ` Felix Miata
2008-02-29 3:50 ` Gaston, Jason D
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=Pine.LNX.4.64.0803111210010.5775@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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