From: Gene Heskett <gene.heskett@verizon.net>
To: Dan Bernard <djb29@cwru.edu>
Cc: CN <cnliou9@fastmail.fm>, linux-kernel@vger.kernel.org
Subject: Re: kernel: i8253 counting too high! resetting..
Date: Fri, 31 Oct 2003 08:00:19 -0500 [thread overview]
Message-ID: <200310310800.19240.gene.heskett@verizon.net> (raw)
In-Reply-To: <20031031063636.GA61826@teraz.cwru.edu>
On Friday 31 October 2003 01:36, Dan Bernard wrote:
>On 20031031 0040, Gene Heskett wrote:
>> >ALi
>> >M1542 A1
>> >100MHz
>> >Uniform Multi-Platform E-IDE driver Revision: 6.31
>> >ide: Assuming 33MHz system bus speed for PIO modes; override with
>> >idebus=xx
>>
>> This is correct, and for 2.4.20, I don't think the override works.
>>
>> > ...
>>
>> And again, while slower, this is the default bus speed FOR PIO,
>> Programmed I/O, not DMA. Another animal entirely. Running at
>> this 33MHZ speed, but without any handshaking, it can move 132Mb a
>> second because each access is 32 bits, or 4 bytes, wide. Which is
>> still far faster than your drives can bring data past the heads.
>> You are confusing the UDMA66 mode which exists on the drive cable,
>> with the bus speed the IDE card is plugged into, 2 entirely
>> different animals.
>>
>> > ...
>>
>> You'll need good cables, and a lengthy read of the hdparm manpage.
>> Then you can put the correct hdparm command to enable the UDMA66
>> mode right into your /etc/rc.d/rc.local script.
>
>ALi M1542 chipset is probably not too different from mine. That's
> good, because if it were not ALi, then this would be much more
> complicated.
>
>The main problem here is not any kind of malfunction, but simply a
>component or group of components performing slightly below what is
>expected, and the software therefore generates unnecessary noise.
>
>I do not try to tweak any settings with hdparm unless something is
> broken. However, it looks like that may be your best bet in this
> particular case. I shall just continue putting up with the warnings
> for now.
>
>Still, if anyone gets these warnings without ALi chipsets, please do
> tell.
>
>Regards,
>Dan Bernard
Unforch, for this scene, both of my boards have VIA chipsets, so its
not from personal experience, I'm just a CET with 55 years of chasing
electrons for a living. I've looked at the top of a lot of chips
since IC's were invented. If the boards are really fresh, maybe you
could warranty the noisy one as being defective?
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2003-10-31 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 7:50 kernel: i8253 counting too high! resetting CN
2003-10-30 17:12 ` Dan Bernard
2003-10-31 5:04 ` CN
2003-10-31 5:40 ` Gene Heskett
2003-10-31 6:36 ` Dan Bernard
2003-10-31 13:00 ` Gene Heskett [this message]
2003-11-03 4:41 ` CN
2003-11-03 5:16 ` Willy Tarreau
2003-11-03 18:52 ` Dan Bernard
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=200310310800.19240.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--cc=cnliou9@fastmail.fm \
--cc=djb29@cwru.edu \
--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;
as well as URLs for NNTP newsgroup(s).