mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jasmeet Sidhu <jsidhu@arraycomm.com>
To: "Daniela Engert" <dani@ngrt.de>,
	"Jason Rappleye" <rappleye@cse.Buffalo.EDU>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "jonesm@ccr.buffalo.edu" <jonesm@ccr.buffalo.edu>
Subject: Re: timeout waiting for DMA
Date: Tue, 27 Feb 2001 11:47:11 -0800	[thread overview]
Message-ID: <5.0.2.1.2.20010227114430.026f9008@pop.arraycomm.com> (raw)
In-Reply-To: <20010227063147.3F8674F06@mail.medav.de>
In-Reply-To: <Pine.GSO.4.21.0102261526330.15135-100000@pollux.cse.Buffalo.EDU>

Iv'e seen this on a system with 36" IDE ata/100 cables.  I have the same 
exact system using 24" IDE ultra ata/100 cables and I get no such 
errors.  These two systems are exactly the same and are using the same 
drivers, same hardware.
The only difference is the type of cable used.  Could this be due to bad 
cables as well?  (I know tha CRC errors are caused by bad cables, but this 
is the only difference in the two boxes that I have).

Keep the cables as short as possible, 18" is supposed to be the limit.

And please post again if you successfully troubleshoot this problem.

Jasmeet.

At 07:35 AM 2/27/2001 +0100, Daniela Engert wrote:
>Hi Jason!
>
>On Mon, 26 Feb 2001 15:41:04 -0500 (EST), Jason Rappleye wrote:
>
> >I'm running kernel 2.4.2 on an SGI 1100 (dual PIIIs) with a Serverworks
> >III LE based motherboard. The disk is a Seagate ST330630A. The disk has
> >DMA enabled at boot time :
>
> >hda: ST330630A, ATA DISK drive
> >hda: 59777640 sectors (30606 MB) w/2048KiB Cache, CHS=3720/255/63, UDMA(33)
>
> >but after a while (eg partway through running bonnie with a 1GB file) I
> >get the following errors:
>
> >Feb 24 22:51:02 nash2 kernel: hda: timeout waiting for DMA
> >Feb 24 22:51:02 nash2 kernel: ide_dmaproc: chipset supported 
> ide_dma_timeout
> >func only: 14
> >Feb 24 22:51:02 nash2 kernel: hda: irq timeout: status=0x58 { DriveReady
> >SeekComplete DataRequest }
> ><repeats a few times>
> >Feb 24 22:51:32 nash2 kernel: hda: DMA disabled
>
> >I can reenable DMA without any problems, but after some additional disk
> >activity (eg running bonnie again), the error occurs again.
>
> >Additional information on my hardware is given below. Any suggestions on
> >how this can be resolved?
>
>Reduce the IDE channel speed to UltraDMA mode 1 or less.
>
>Ciao,
>   Dani
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Daniela Engert, systems engineer at MEDAV GmbH
>Gräfenberger Str. 34, 91080 Uttenreuth, Germany
>Phone ++49-9131-583-348, Fax ++49-9131-583-11
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/


- - -
Jasmeet Sidhu
Unix Systems Administrator
ArrayComm, Inc.
jsidhu@arraycomm.com
www.arraycomm.com



  parent reply	other threads:[~2001-02-27 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 20:41 Jason Rappleye
2001-02-27  6:35 ` Daniela Engert
2001-02-27 19:47 ` Jasmeet Sidhu [this message]
2001-03-06 19:51 ` [RECAP] " Jason Rappleye
2001-03-20  6:48 Jason Gillis

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=5.0.2.1.2.20010227114430.026f9008@pop.arraycomm.com \
    --to=jsidhu@arraycomm.com \
    --cc=dani@ngrt.de \
    --cc=jonesm@ccr.buffalo.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rappleye@cse.Buffalo.EDU \
    /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

all inboxes | Powered by JetHome®