From: Clemens Koller <clemens.koller@anagramm.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE: PDC20275 turning on/off DMA dangerous?
Date: Mon, 19 Dec 2005 15:45:20 +0100 [thread overview]
Message-ID: <43A6C780.5070000@anagramm.de> (raw)
In-Reply-To: <58cb370e0512190440p3889a489sbc82f0c482fd9db9@mail.gmail.com>
Hello, Bartolmiej!
>>I am working on an embedded ppc (mpc8540) using a pretty common Promise IDE
>>PCI controller w/ a PDC20275 on it (it's called Ultra TX2).
>>I have an otherwise good Maxtor 6B120P0 (160GB) connected to it.
>>
>>But sometimes (expecially with more than zero disk-i/o-load), when I
>>turn on DMA by
>>
>>$hdparm -X69 -d1 /dev/hda
>>I get
>>
>>hda: task_out_intr: status=0x58 { DriveReady SeekComplete DataRequest }
>>ide: failed opcode was: unknown
>>hda: CHECK for good STATUS
>>
>>And when I turn off DMA with
>>$hdparm -d0 /dev/hda
>>I get sometimes a
>>
>>hda: DMA disabled
>>
>>which is fine but sometimes I also get:
>>
>>hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>>ide: failed opcode was: unknown
>>hda: drive not ready for command
>>hda: CHECK for good STATUS
>>
>>which is not so nice.
>>Can you tell me if this is dangerous?
>
>
> Is there any particular reason why you are using hdparm with '-d' and '-X'?
I want to test it with DMA before fixing it into the kernel.
> Your IDE host driver (pdc202xx_new in this case) should configure
> best xfer mode and enable DMA so you shouldn't need to use hdparm.
I didn't enable automatic turning on of DMA it in the kernel by default
in the past because I had problems with this hdd controller and
interrupts (some PCI IRQ mapping issues). The interrupt issues are
solved now, so I've tried to enable DMA. DMA works pretty fine,
I was just worried about the severity of the message. It doesn't
really tell anything useful for non-ide-hackers. (whether it's
dangerous or not.)
> Given that IDE driver code for changing xfer mode and DMA setting
> is racy and actually quite hard to fix, it will probably be removed in
> the future (after auditing IDE host drivers).
So, I guess the answer is: DMA itself seems to work and it
isn't really dangerous - it's working as it's supposed to.
But if you do it the way you do, you can run into problems due
to races. Right? So, if I enable DMA as usual in the kernel,
I don't usually risk my data?!
> BTW please use linux-ide@vger.kernel.org for IDE problems
Okay, in next thread.
Thanks,
--
Clemens Koller
_______________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Str. 45/1
81379 Muenchen
Germany
http://www.anagramm.de
Phone: +49-89-741518-50
Fax: +49-89-741518-19
next prev parent reply other threads:[~2005-12-19 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 15:33 IDE: PDC20275 turning on/off DMA dangerous? Clemens Koller
2005-12-19 12:40 ` Bartlomiej Zolnierkiewicz
2005-12-19 14:45 ` Clemens Koller [this message]
2005-12-19 15:46 ` Bartlomiej Zolnierkiewicz
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=43A6C780.5070000@anagramm.de \
--to=clemens.koller@anagramm.de \
--cc=bzolnier@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 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.