From: "David Grant" <davidgrant79@hotmail.com>
To: "Maxwell Spangler" <maxwax@mindspring.com>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Greg Ward" <gward@python.net>, <linux-kernel@vger.kernel.org>
Subject: Re: "hde: timeout waiting for DMA": message gone, same behaviour
Date: Tue, 25 Sep 2001 19:02:36 -0700 [thread overview]
Message-ID: <OE326eDIBlgb8hMppUY00003821@hotmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109251614330.5310-100000@tyan.doghouse.com>
Those messages are almost identical to the ones I get. Except it happens to
me when I try to install Linux. Just curious, Max, when did this start
happening? You say it's an otherwise rock solid system, but was there ever
a time when it didn't do this? Some people have suspected (with my system)
that the problem may come from IRQ sharing problems. It looks like Max
isn't using any IRQ sharing with his Promise card, but he is with his Intel
on-board IDE controller, from the lspci listing. So my other question for
Max is, where are your two hard drives connected to??? I hope I don't sound
completely like I don't know what I'm talking about.
David Grant
>
> Sep 13 22:19:50 tyan kernel: hde: timeout waiting for DMA
> Sep 13 22:19:52 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 13 22:19:52 tyan kernel: hde: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 13 22:20:12 tyan kernel: hde: timeout waiting for DMA
> Sep 13 22:20:13 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 13 22:20:13 tyan kernel: hde: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 13 22:20:34 tyan kernel: hde: timeout waiting for DMA
> Sep 13 22:20:35 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 13 22:20:35 tyan kernel: hde: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 13 22:20:56 tyan kernel: hde: timeout waiting for DMA
> Sep 13 22:20:56 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 13 22:20:56 tyan kernel: hde: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 13 22:20:59 tyan kernel: hde: DMA disabled
> Sep 13 22:20:59 tyan kernel: ide2: reset: success
> Sep 14 04:02:19 tyan kernel: hdg: timeout waiting for DMA
> Sep 14 04:02:20 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 14 04:02:20 tyan kernel: hdg: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 14 04:02:29 tyan kernel: hde: lost interrupt
> Sep 14 04:02:41 tyan kernel: hdg: timeout waiting for DMA
> Sep 14 04:02:42 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 14 04:02:42 tyan kernel: hdg: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 14 04:03:03 tyan kernel: hdg: timeout waiting for DMA
> Sep 14 04:03:04 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 14 04:03:04 tyan kernel: hdg: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 14 04:03:13 tyan kernel: hde: lost interrupt
> Sep 14 04:03:25 tyan kernel: hdg: timeout waiting for DMA
> Sep 14 04:03:25 tyan kernel: ide_dmaproc: chipset supported
ide_dma_timeout func only: 14
> Sep 14 04:03:25 tyan kernel: hdg: irq timeout: status=0x50 { DriveReady
SeekComplete }
> Sep 14 04:03:25 tyan kernel: hdg: DMA disabled
> Sep 14 04:03:26 tyan kernel: ide3: reset: success
> Sep 14 04:04:17 tyan kernel: hde: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
> Sep 14 04:04:17 tyan kernel: hde: drive not ready for command
> Sep 14 04:04:34 tyan kernel: hde: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
> Sep 14 04:04:34 tyan kernel: hde: drive not ready for command
> Sep 14 04:04:42 tyan kernel: hdg: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
> Sep 14 04:04:42 tyan kernel: hdg: drive not ready for command
> Sep 14 10:20:33 tyan kernel: hde: irq timeout: status=0xd0 { Busy }
> Sep 14 10:20:34 tyan kernel: ide2: reset: success
>
[root@tyan /root]# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge
(rev
03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev
03)
00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02)
00:11.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev 20)
00:12.0 Unknown mass storage controller: Promise Technology, Inc. 20262 (rev
01)
00:13.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 02)
00:14.0 SCSI storage controller: BusLogic BT-946C (BA80C30) [MultiMaster 10]
(rev 08)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev
82)
next prev parent reply other threads:[~2001-09-26 2:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 17:44 Greg Ward
2001-09-21 18:53 ` Vojtech Pavlik
2001-09-21 19:08 ` Greg Ward
2001-09-21 19:49 ` Greg Ward
2001-09-21 19:56 ` Vojtech Pavlik
2001-09-21 20:43 ` Greg Ward
2001-09-22 8:04 ` Vojtech Pavlik
2001-09-22 10:53 ` David Grant
2001-09-22 13:40 ` Eyal Lebedinsky
2001-09-22 15:09 ` Greg Ward
2001-09-22 15:58 ` Alan Cox
2001-09-25 20:23 ` Maxwell Spangler
2001-09-26 2:02 ` David Grant [this message]
2001-09-26 2:18 ` Maxwell Spangler
2001-09-22 20:07 ` David Grant
2001-09-24 8:35 ` Vojtech Pavlik
2001-09-24 18:37 ` Eric W. Biederman
2001-09-24 22:44 ` Vojtech Pavlik
2001-09-25 0:15 ` Kevin P. Fleming
2001-10-01 14:03 ` Greg Ward
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=OE326eDIBlgb8hMppUY00003821@hotmail.com \
--to=davidgrant79@hotmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gward@python.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxwax@mindspring.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
all inboxes | Powered by JetHome®