From: "Michael B. Allen" <mballen@erols.com>
To: Wayne Whitney <whitney@math.berkeley.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.17 Lockup and ATA-66/100 forced bit set (WARNING)
Date: Wed, 21 Feb 2001 18:33:13 -0500 [thread overview]
Message-ID: <20010221183313.A3487@angus.foo.net> (raw)
In-Reply-To: <20010221173439.A3178@angus.foo.net> <200102212348.f1LNm6X02792@adsl-209-76-109-63.dsl.snfc21.pacbell.net>
In-Reply-To: <200102212348.f1LNm6X02792@adsl-209-76-109-63.dsl.snfc21.pacbell.net>; from whitney@math.berkeley.edu on Wed, Feb 21, 2001 at 03:48:06PM -0800
On Wed, Feb 21, 2001 at 03:48:06PM -0800, Wayne Whitney wrote:
> > append="idebus=66 ide0=ata66"
>
> The idebus=66 part is incorrect. This option refers to the clock of
> the PCI bus the IDE controller is on and should rarely be changed from
> the default of 33MHz (i.e., only if you are overclocking the PCI bus).
Ah, well I just added that based on the end of this boot message:
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> >kernel: VP_IDE: ATA-66/100 forced bit set (WARNING)!!
>
> I'm sure this is just telling you that you passed the ide0=ata66
> parameter. Usually it is best not to do this--the driver should run
> your chipset/drive as fast as possible without 'forcing' the
> configuration. Of course, testing with hdparm -t is considered the
> definitive way to check how fast the interface is running.
If I don't add it hdparm -t /dev/hda reports:
Timing buffered disk reads: 64 MB in 16.46 seconds = 3.89 MB/sec
Then if I do hdparm -d1 -X66 /dev/hda I get:
/dev/hda:
setting using_dma to 1 (on)
setting xfermode to 66 (UltraDMA mode2)
using_dma = 1 (on)
[root@nano /root]# hdparm -t /dev/hda
/dev/hda:
Timing buffered disk reads: 64 MB in 4.04 seconds = 15.84 MB/sec
Now if I add it via append, reboot and do hdparm -t I get:
Timing buffered disk reads: 64 MB in 3.70 seconds = 17.30 MB/sec
This last difference is consistently better. Weird.
All your other bets were right too.
Thanks Wayne,
Mike
--
signature pending
next prev parent reply other threads:[~2001-02-22 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 22:34 Michael B. Allen
2001-02-21 1:33 ` Tim Moore
[not found] ` <200102212348.f1LNm6X02792@adsl-209-76-109-63.dsl.snfc21.pacbell.net>
2001-02-21 23:33 ` Michael B. Allen [this message]
2001-02-21 23:36 ` Dan Hollis
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=20010221183313.A3487@angus.foo.net \
--to=mballen@erols.com \
--cc=linux-kernel@vger.kernel.org \
--cc=whitney@math.berkeley.edu \
/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®