From: Alan Pope <alan.pope@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: DMA & PDC202XX issue
Date: Mon, 15 Nov 2004 23:56:10 +0000 [thread overview]
Message-ID: <8e93903b04111515567dc162f3@mail.gmail.com> (raw)
Hi,
I have a Via based mobo with Promise PDC20265 controller with a
Seagate ST3200822A disk attached, giving me IO errors whenever I touch
the disk. I'm using the PDC202XX_OLD driver and have forced DMA on. I
have tried 2.6.8 through up to 2.6.9-ac9 and 2.6.10-rc2, all give the
same error. I can easily reproduce it with a simple "hdparm -t -T
/dev/hde" but under "normal" use such as copying files from another
disk on another channel, the same thing happens.
hde: dma_intr: status=0xff { Busy }
ide: failed opcode was: unknown
hde: DMA disabled
PDC202XX: Primary channel reset.
PDC202XX: Secondary channel reset.
(a number of times)
ide2: reset timed-out, status=0xff
end_request: I/O error, dev hde, sector 11776
Buffer I/O error on device hde, logical block 1472
(many times)
Any ideas greatfully received.
I have put some system details at http://www.popey.com/promise.htm if
that helps.
Cheers,
Al.
reply other threads:[~2004-11-15 23:59 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=8e93903b04111515567dc162f3@mail.gmail.com \
--to=alan.pope@gmail.com \
--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