[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47D485EC.1060103@gmail.com>
Date: Mon, 10 Mar 2008 09:50:52 +0900
From: Tejun Heo <htejun@...il.com>
To: Guennadi Liakhovetski <g.liakhovetski@....de>
CC: Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
Jeff Garzik <jeff@...zik.org>, linux-ide@...r.kernel.org
Subject: Re: Unknown SATA PIIX PCI device ID 0x29b6
Guennadi Liakhovetski wrote:
> On Sun, 9 Mar 2008, Tejun Heo wrote:
>
>> Guennadi Liakhovetski wrote:
>>> On Fri, 7 Mar 2008, Tejun Heo wrote:
>>>
>>>>> Looks like almost a minute to me? On another occurence I see about 1.5
>>>>> minutes, then "port is slow to respond, please be patient (Status 0x80)"
>>>>> has been repeated 3 times. On cold-plug also 3 times, I think, about the
>>>>> same time then (time is not updated in the log).
>>>> I see. Does the attached patch make any difference?
>>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>>> index 4fbcce7..abebdcc 100644
>>> --- a/drivers/ata/libata-core.c
>>> +++ b/drivers/ata/libata-core.c
>>> @@ -6712,6 +6712,7 @@ int sata_link_init_spd(struct ata_link *link)
>>> spd = (scontrol >> 4) & 0xf;
>>> if (spd)
>>> link->hw_sata_spd_limit &= (1 << spd) - 1;
>>> + link->hw_sata_spd_limit = 1;
>>>
>>> ata_force_spd_limit(link);
>>>
>>> Hm, this would force 1.5Gbps on all ports and devices, right? Cannot I
>>> just boot with "libata.force=4:1.5Gbps"?
>> Yeap, you can do that. Wasn't sure you were using .25-rc or .24.
>
> Yctually it was 2.6.24 before, rebuilt 2.6.25-rc4, booted as above, it did
> say:
>
> ata4: FORCE: PHY spd limit set to 1.5Gbps
>
> but hot-plugging the drive still took 50 seconds to recover.
How about cold plugging?
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists