public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Torsten Wolf <t.wolf@tu-bs.de>
To: linux-kernel@vger.kernel.org
Subject: CD-Writing and DMA problems with KT266A and 2.4.16-20
Date: Fri, 7 Feb 2003 18:32:10 +0100	[thread overview]
Message-ID: <20030207173210.GA11196@b147> (raw)

Hi,

at present, I have an Epox 8KHA+ with VIA's KT266A chipset (VT8367,
VT8233) with 3 harddrives (hda,b,c) and a Teac IDE CD-RW (hdd) attached.
DMA ist activated on all devices via hdparm at boottime. Ripping a CD
eats half of the CPU (Athlon XP1600+), but as I have heard so far, this
is "normal", at least for 2.4.x. Unfortunately, the ide-akpm-patch gave
no improvement. What really makes me wonder is the following:

As soon as I enable CONFIG_BLK_DEV_VIA82CXXX and try to burn data
residing on hdc onto CD, I get the following messages:

hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: drive not ready for command
[...]
hdd: DMA disabled
hdd: drive not ready for command
hdd: ATAPI reset complete

Thus, burning fails. After removing the support for the chipset writing
to the CD is no problem, no matter which source is used. hdparm shows
DMA activated before and after the write process.

This happens with versions at least from 2.4.16 up to 2.4.20. Could you
please give me a hint, whether I'm doing something terribly wrong. Is
this yet another proof, that VIA-Hardware is under certain circumstances
somewhat... flaky?

Best wishes
Torsten

                 reply	other threads:[~2003-02-07 17:22 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=20030207173210.GA11196@b147 \
    --to=t.wolf@tu-bs.de \
    --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