From: Tim Hockin <thockin@sun.com>
To: Mike Panetta <mpanetta@applianceware.com>, linux-kernel@vger.kernel.org
Subject: Re: HPT366 IDE DMA error question.
Date: Fri, 27 Apr 2001 10:29:40 -0700 [thread overview]
Message-ID: <3AE9AC84.B0D8682A@sun.com> (raw)
In-Reply-To: <20010426131846.A29148@tetsuo.applianceware.com>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
Mike Panetta wrote:
> hdi: timeout waiting for DMA
> ide_dmaproc: chipset supported ide_dma_timeout func only: 14
> hdi: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hdi: DMA disabled
> ide4: reset: success
>
> I get this message on all my off board HPT366 based controller
> cards. I am using these cards with seagate Barracuda ATA III
> Model ST320414A 20GB drives. Are there any known issues with
> these drives and the HPT366 based controllers? Are there any
we have a system with hpt 370's (366 driver) that we found the following
obvious bug in. If you read the spec carefuly, it is obviously correct.
You have to set DMA up for read vs. write. Does this make your problems go
away? DIff against 2.4.3
--
Tim Hockin
Systems Software Engineer
Sun Microsystems, Cobalt Server Appliances
thockin@sun.com
[-- Attachment #2: hpt.diff --]
[-- Type: text/plain, Size: 1245 bytes --]
diff -u dist-2.4.3/drivers/ide/hpt366.c linux-2.4/drivers/ide/hpt366.c
--- dist-2.4.3/drivers/ide/hpt366.c Sat Jan 27 08:45:58 2001
+++ linux-2.4/drivers/ide/hpt366.c Thu Apr 26 20:15:17 2001
@@ -523,9 +638,11 @@
void hpt370_rw_proc (ide_drive_t *drive, ide_dma_action_t func)
{
- if ((func != ide_dma_write) || (func != ide_dma_read))
+ if ((func != ide_dma_write && func != ide_dma_read)
+ || drive->rwproc_cache == (void *)func)
return;
hpt370_tune_chipset(drive, drive->current_speed, (func == ide_dma_write));
+ drive->rwproc_cache = (void *)func;
}
static int config_drive_xfer_rate (ide_drive_t *drive)
diff -u dist-2.4.3/include/linux/ide.h linux-2.4/include/linux/ide.h
--- dist-2.4.3/include/linux/ide.h Mon Jan 29 23:25:32 2001
+++ linux-2.4/include/linux/ide.h Thu Apr 26 20:16:00 2001
@@ -284,6 +284,7 @@
unsigned long service_time; /* service time of last request */
unsigned long timeout; /* max time to wait for irq */
special_t special; /* special action flags */
+ void *rwproc_cache; /* last rwproc update */
byte keep_settings; /* restore settings after drive reset */
byte using_dma; /* disk is using dma for read/write */
byte waiting_for_dma; /* dma currently in progress */
next prev parent reply other threads:[~2001-04-27 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-26 20:18 HPT366 IDE DMA error question Mike Panetta
2001-04-27 17:29 ` Tim Hockin [this message]
2001-04-27 23:46 ` [PATCH] hpt366.c, *bad_ata66_4 additions (2.2.19 + ide.2.2.19.04092001.patch) Tim Moore
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=3AE9AC84.B0D8682A@sun.com \
--to=thockin@sun.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpanetta@applianceware.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