From: Tejun Heo <htejun@gmail.com>
To: Sergey Dolgov <dolgovs@gmail.com>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ata_piix, laptop cdrom, ICH7: EH, limiting speed to PIO
Date: Mon, 17 Sep 2007 13:37:14 +0200 [thread overview]
Message-ID: <46EE66EA.3090902@gmail.com> (raw)
In-Reply-To: <ac0be4d70709170257o62e856f4re049c968ab5590a7@mail.gmail.com>
Sergey Dolgov wrote:
> On 9/16/07, Tejun Heo <htejun@gmail.com> wrote:
>> 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@gmail.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?
>>
>
> What's the best way to tell whether it does or not? (the log says
> "selected mode 0x22", see below)
Yes, that's MWDMA2. Hmm... We're seeing many cases where MWDMA doesn't
work with libata while it works fine with IDE but have no idea what's
going on yet. :-(
--
tejun
next prev parent reply other threads:[~2007-09-17 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 21:21 ata_piix, laptop cdrom, ICH7: EH, limiting speed to PIO Sergey Dolgov
2007-09-12 16:33 ` Michal Piotrowski
2007-09-12 20:07 ` Sergey Dolgov
2007-09-12 20:19 ` Michal Piotrowski
2007-09-12 21:20 ` Sergey Dolgov
2007-09-12 22:20 ` Michal Piotrowski
2007-09-16 11:56 ` Tejun Heo
2007-09-17 9:57 ` Sergey Dolgov
2007-09-17 11:37 ` Tejun Heo [this message]
2007-09-17 12:05 ` Sergey Dolgov
2007-09-17 17:18 ` Alexey Zaytsev
2007-09-18 18:05 ` Sergey Dolgov
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=46EE66EA.3090902@gmail.com \
--to=htejun@gmail.com \
--cc=dolgovs@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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).