From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Geller Sandor <wildy@petra.hos.u-szeged.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: HPT374 IDE problem with 2.6.21.* kernels
Date: Sat, 02 Jun 2007 01:26:22 +0400 [thread overview]
Message-ID: <46608EFE.1030202@ru.mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0706012311320.16639@petra.hos.u-szeged.hu>
Hello.
Geller Sandor wrote:
>>>> I saw a similar report yesterday with '2.6.21.1 - 97% wait time on
>>>> IDE operations' subject.
>>>> After upgrading from 2.6.20.7 kernel to 2.6.21.1 my system started
>>>> to reset infrequenly the IDE bus. In the syslog DMA timeout,
>>>> resetting IDE bus messages appeared. I've changed the two disks
>>>> attached to the HPT374 controller, and always the first disk had
>>>> problems. I've replaced cables, plugged the disks into other IDE
>>>> ports, but it was only a matter of time to experience an IDE reset.
>>>> When I upgraded to 2.6.21.3 the resets became much more frequent,
>>>> this time even DMA was disabled too on the first disk. I turned DMA
>>>> back Manually with hdparm, and a few seconds of intense IO activity
>>>> resulted in another IDE reset.
>>
>>
>>>> Reverting back to 2.6.20.12 the problem seems to be gone. BTW I'm
>>>> using the PATA driver for the HTP374, not the libata one.
>>
>>
>>>> Is this a known problem/ is there a way I can help locating the
>>>> cause of the problem?
>> Yes, please post the boot log and the IDE reset log too for starters...
>>> (cc's added)
> The log of a typical IDE reset is available here:
> http://petra.hos.u-szeged.hu/~wildy/syslog.gz
> This was the worst case: the IDE bus was resetted during the system boot.
Could you try setting HPT374_ALLOW_ATA133_6 to 0 in
drivers/ide/pci/hpt366.c and rebuild/reboot the kernel?
MBR, Sergei
next prev parent reply other threads:[~2007-06-01 21:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 9:30 HPT374 IDE problem with 2.6.21.* kernels Geller Sandor
2007-06-01 20:46 ` Andrew Morton
2007-06-01 20:53 ` Sergei Shtylyov
2007-06-01 21:13 ` Geller Sandor
2007-06-01 21:26 ` Sergei Shtylyov [this message]
2007-06-01 22:41 ` Geller Sandor
2007-06-02 23:38 ` Bartlomiej Zolnierkiewicz
2007-06-03 10:37 ` Geller Sandor
2007-06-03 17:36 ` Sergei Shtylyov
2007-06-05 1:00 ` Bartlomiej Zolnierkiewicz
2007-06-05 12:45 ` Sergei Shtylyov
2007-06-05 14:14 ` Sergei Shtylyov
2007-06-08 12:33 ` Bartlomiej Zolnierkiewicz
2007-06-09 10:13 ` Sergei Shtylyov
2007-06-05 20:08 ` Sergei Shtylyov
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=46608EFE.1030202@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wildy@petra.hos.u-szeged.hu \
/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.