linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "CN" <cnliou9@fastmail.fm>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel: i8253 counting too high! resetting..
Date: Sun, 02 Nov 2003 20:41:55 -0800	[thread overview]
Message-ID: <20031103044155.8D0067DF67@server2.messagingengine.com> (raw)
In-Reply-To: <20031031063636.GA61826@teraz.cwru.edu>

On Fri, 31 Oct 2003 06:36:36 +0000, "Dan Bernard" <djb29@cwru.edu> said:
> 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.

I'm sorry for the late follow up as I lost Internet connection during the
period of OS reinstallation. The following symptom I have newly noticed
is a follow up to my first post in this thread.

As reported in my first message, the box running kernel 2.4.22 and
Fjuitsu HD generated i8253 message while the other box running 2.4.20 and
Maxtor did not. During the past 3 days I wiped out everything from the HD
and reinstalled Debian woody on to the "normal" box (with Maxtor) and
rebuilt the kernel to 2.4.22. This used-to-be normal box started to
generate the i8253 message since then.

Then I downgraded both boxes to kernel 2.4.20. Now both boxes are running
woody and kernel 2.4.20 on identical hardware exept HD's and RAM's. Well,
both boxes completely stop the i8253 message since the OS downgrade :). I
don't have any knowledge regarding the technical details but I think
reporting this "history" to this list should be a good idea.

Best Regards,
CN

-- 
http://www.fastmail.fm - Send your email first class

  parent reply	other threads:[~2003-11-03  4:42 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
2003-11-03  4:41         ` CN [this message]
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=20031103044155.8D0067DF67@server2.messagingengine.com \
    --to=cnliou9@fastmail.fm \
    --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).