linux-kernel - Re: ata_piix, laptop cdrom, ICH7: EH, limiting speed to PIO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46ED19F0.8060205@gmail.com>
Date:	Sun, 16 Sep 2007 13:56:32 +0200
From:	Tejun Heo <htejun@...il.com>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
CC:	Sergey Dolgov <dolgovs@...il.com>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: ata_piix, laptop cdrom, ICH7: EH, limiting speed to PIO

Michal Piotrowski wrote:
> Sergey Dolgov pisze:
>> On Wed, Sep 12, 2007 at 10:19:03PM +0200, Michal Piotrowski wrote:
>>> Sergey Dolgov pisze:
>>>> Hi Michal,
>>>>
>>>> On Wed, Sep 12, 2007 at 06:33:20PM +0200, Michal Piotrowski wrote:
>>>>> Hi Sergey,
>>>>>
>>>>> On 11/09/2007, Sergey Dolgov <dolgovs@...il.com> wrote:
>>>>>> Hi!
>>>>>>
>>>>>> On my hp nx7300 laptop, 2 following scenarios can happen during bootup
>>>>>> (see attachments for the full logs): the "good" one [1] and the one
>>>>>> where multiple EHs lead to limiting the speed [2].
>>>>>>
>>>>>> [1] one is more rare, but it seems to be persistent over reboots: once
>>>>>> it happened, just rebooting the machine always results in behaviour
>>>>>> like [1].
>>>>>>
>>>>>> [1] results in a working cdrom from the start. An attempt to use cdrom
>>>>>> after [2] happened results in even more EHs, resulting in "configured
>>>>>> for PIO4", after which the cdrom is finaly working.
>>>>>>
>>>>>> The version I'm using is 2.6.23-rc6, but the same used to happen with
>>>>>> the previous rc's, and probably with 2.6.22 too (I can check).
>>>>> It would be great if you could check it.
>>>> I've just built 2.6.22.6 with basically the same configuration, and
>>>> the behaviour is just the same, i.e. both [1] and [2] still can
>>>> happen.
>>> Ok, thanks.
>>>
>>> BTW please check cables and PCU.
>> What's a PCU?
> 
> s/PCU/PSU - power supply unit
> 
>> BTW, this only happens when using libata of course. The
>> old CONFIG_IDE stuff works fine every time.
> 
> This maybe one of libata weirdness (I really don't get it why some hardware
> works perfectly fine with an old IDE and don't work well with libata).

Hmmm... Is MWDMA2 mode used with ide driver too?

-- 
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/