From: "Nick Evgeniev" <nick@octet.com>
To: <linux-kernel@vger.kernel.org>
Subject: 2.4.19-pre10-ac2 PDC20265 IDE BUGS.
Date: Fri, 7 Jun 2002 18:53:43 +0400 [thread overview]
Message-ID: <000701c20e33$1eb14450$baefb0d4@nick> (raw)
Hi,
2.4.19-pre10-ac2 still has bugs in its promise 20265 ide controller driver.
I've got ide lost interrupt messages on console just in a few hours after
reboot. (BTW could someone explain me what does it means for drives in
UDMA100 mode?)
Below is a kernel.log messages:
>----------------------------
Jun 7 17:43:16 vzhik kernel: hdg: status timeout: status=0xd0 { Busy }
Jun 7 17:43:16 vzhik kernel:
Jun 7 17:43:16 vzhik kernel: hdg: drive not ready for command
Jun 7 17:43:16 vzhik kernel: hdg: status timeout: status=0xd0 { Busy }
Jun 7 17:43:16 vzhik kernel:
Jun 7 17:43:16 vzhik kernel: hdg: DMA disabled
Jun 7 17:43:17 vzhik kernel: ide3: reset: success
Jun 7 17:43:18 vzhik kernel: PDC202XX: Secondary channel reset.
Jun 7 17:43:18 vzhik kernel: hdg: drive not ready for command
Jun 7 17:43:38 vzhik kernel: hde: timeout waiting for DMA
Jun 7 17:44:03 vzhik kernel: PDC202XX: Primary channel reset.
Jun 7 17:44:03 vzhik kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 16
Jun 7 17:44:03 vzhik kernel: hde: timeout waiting for DMA
Jun 7 17:44:03 vzhik kernel: PDC202XX: Primary channel reset.
Jun 7 17:44:03 vzhik kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 16
Jun 7 17:44:03 vzhik kernel: hde: status timeout: status=0xd1 { Busy }
Jun 7 17:44:03 vzhik kernel:
Jun 7 17:44:03 vzhik kernel: PDC202XX: Primary channel reset.
Jun 7 17:44:03 vzhik kernel: hde: drive not ready for command
Jun 7 17:44:03 vzhik kernel: ide2: reset: success
Jun 7 17:49:21 vzhik kernel: hdg: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Jun 7 17:49:21 vzhik kernel:
Jun 7 17:49:21 vzhik kernel: hdg: drive not ready for command
Jun 7 17:49:21 vzhik kernel: hdg: status timeout: status=0xd0 { Busy }
reply other threads:[~2002-06-07 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000701c20e33$1eb14450$baefb0d4@nick' \
--to=nick@octet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@octet.spb.ru \
/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.