public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.4.4-ac5; hpt370 & new dma setup
Date: Sat, 5 May 2001 14:37:53 -0400	[thread overview]
Message-ID: <01050514375300.14219@oscar> (raw)

thunder7@xs4all.nl wrote:

> On Fri, May 04, 2001 at 11:24:58PM +0100, Alan Cox wrote:
>> 
>> ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
>> 
>> Intermediate diffs are available from
>> 
>> http://www.bzimage.org
>> 
>> Please test this code **carefully** if using an HPT366/370 IDE controller as
>> there are driver changes there. Otherwise its mostly just catching up with
>> the bugfixes.
>> 
>> 2.4.4-ac5
>> o	Fix DMA setup on hpt366/370			(Tim Hockin)
> 
> I see definite changes; on heavy disk-access I got the following:
> 
> hdg: timeout waiting for dma
> ide_dmaproc: chipset supported ide_dma_timeout func only:14
> hdg: irq timeout: status = 0x58 { DriveReady SeekComplete DataRequest}
> 
> this was repeated several times, and ide3 was being reset, but the
> kernel hung anyway after 5 minutes of waiting.
> 
> I must have an unlucky set of hardware (via chipset VP6 board, Live!,
> ibm drives).

Funny I have had the same problem with 2.4.4 only with a pdc20267 (reported
to lkml with topic '[BUG] pdc20267 and dma timeouts')  Is there some problem 
with resets on ide2/3?

TIA
Ed Tomlinson <tomlins@cam.org>

Ed Tomlinson

             reply	other threads:[~2001-05-05 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05 18:37 Ed Tomlinson [this message]
2001-05-06  5:47 ` [lkml]Linux 2.4.4-ac5; hpt370 & new dma setup thunder7
  -- strict thread matches above, loose matches on Subject: below --
2001-05-04 22:24 Linux 2.4.4-ac5 Alan Cox
2001-05-05 15:17 ` Linux 2.4.4-ac5; hpt370 & new dma setup thunder7

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=01050514375300.14219@oscar \
    --to=tomlins@cam.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