From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Balaji Calidas <balaji@techsource.com>
Subject: Re: IDE DMA problem [WAS: Re: Getting lousy NFS + tar-pipe throughput on 2.4.20]
Date: Sat, 14 Feb 2004 01:54:54 +0100 [thread overview]
Message-ID: <200402140154.54307.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <402D68CB.2030803@techsource.com>
On Saturday 14 of February 2004 01:16, Timothy Miller wrote:
> I have discovered one major problem that I didn't think to check
> before. I have never before had trouble using DMA with WD drives, VIA
> chipsets, or RH9, so I didn't think to check before, but hdparm reports
> that DMA is disabled for the disk on the workstation I mentioned in my
> earlier post.
>
> So, I tried this:
> hdparm -d1 /dev/hda
>
> And I got this result:
> /dev/hda:
> Setting using_dma to 1 (on)
> HDIO_SET_DMA failed: Operation not permitted
> using_dma = 0 (off)
>
> How do I fix this? Do I have to unmount the filesystem before I can
> change the dma setting? Why would it be off to begin with? I know that
> the BIOS is set up right. Does 2.4.20 not work well with the KT600
> chipset?
It doesn't, upgrade to 2.4.24.
next prev parent reply other threads:[~2004-02-14 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 23:48 Getting lousy NFS + tar-pipe throughput on 2.4.20 Timothy Miller
2004-02-14 0:16 ` IDE DMA problem [WAS: Re: Getting lousy NFS + tar-pipe throughput on 2.4.20] Timothy Miller
2004-02-14 0:54 ` Bartlomiej Zolnierkiewicz [this message]
2004-02-16 17:09 ` 2.4.24 problems [WAS: Re: IDE DMA problem [WAS: Re: Getting lousy NFS + tar-pipe throughput on 2.4.20]] Timothy Miller
2004-02-16 17:20 ` Bartlomiej Zolnierkiewicz
2004-02-16 19:10 ` Jeff Garzik
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=200402140154.54307.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=balaji@techsource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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®