From: timothy parkinson <t@timothyparkinson.com>
To: john stultz <johnstul@us.ibm.com>
Cc: hauan@cmu.edu, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1 "clock preempt"?
Date: Thu, 22 Jan 2004 15:00:44 -0500 [thread overview]
Message-ID: <20040122200044.GA593@h00a0cca1a6cf.ne.client2.attbi.com> (raw)
In-Reply-To: <1074801242.21658.71.camel@cog.beaverton.ibm.com>
su -c "/usr/sbin/hdparm /dev/hda"
Password:
/dev/hda:
multcount = 16 (on)
IO_support = 1 (32-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 65535/16/63, sectors = 156301488, start = 0
but...
su -c "/usr/sbin/hdparm -d1 /dev/hda"
Password:
/dev/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
it's an 80gig western digital from about 2-3 years ago.
On Thu, Jan 22, 2004 at 11:54:02AM -0800, john stultz wrote:
> On Thu, 2004-01-22 at 11:50, timothy parkinson wrote:
> > well, it does *say* the following:
> >
> > ..... host bus clock speed is 133.0266 MHz.
> > checking TSC synchronization across 2 CPUs: passed.
> > Starting migration thread for cpu 0
>
> That looks fine then.
>
> > is there a good way to check IDE PIO?
>
> Run "/sbin/hdparm /dev/hdX" and look for "using_dma = 0".
>
> thanks
> -john
>
>
>
>
>
>
next prev parent reply other threads:[~2004-01-22 20:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:36 2.6.1 "clock preempt"? Steinar Hauan
2004-01-20 21:26 ` john stultz
2004-01-21 15:06 ` Steinar Hauan
2004-01-21 18:19 ` john stultz
2004-01-22 19:37 ` timothy parkinson
2004-01-22 19:42 ` john stultz
2004-01-22 19:50 ` timothy parkinson
2004-01-22 19:54 ` john stultz
2004-01-22 20:00 ` timothy parkinson [this message]
2004-01-22 21:21 ` john stultz
2004-01-23 19:02 ` timothy parkinson
2004-01-23 19:17 ` john stultz
2004-01-23 19:36 ` timothy parkinson
2004-01-23 20:06 ` john stultz
2004-01-23 20:38 ` timothy parkinson
2004-01-23 21:04 ` john stultz
2004-01-27 21:30 ` markus reichelt
2004-01-30 23:32 ` Bartlomiej Zolnierkiewicz
2004-01-31 0:24 ` timothy parkinson
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=20040122200044.GA593@h00a0cca1a6cf.ne.client2.attbi.com \
--to=t@timothyparkinson.com \
--cc=hauan@cmu.edu \
--cc=johnstul@us.ibm.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.