From: Dan Bernard <djb29@cwru.edu>
To: CN <cnliou9@fastmail.fm>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel: i8253 counting too high! resetting..
Date: Thu, 30 Oct 2003 17:12:35 +0000 [thread overview]
Message-ID: <20031030171235.GA59683@teraz.cwru.edu> (raw)
In-Reply-To: <20031029075010.596C57A6C6@smtp.us2.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
On 20031028 2350, CN wrote:
> entries in syslog from kernel 2.4.22 upgraded from Debian woody (gcc
> 2.95.4) running on AMD K6II 450MHz with 64MB RAM. I don't have such
> problem in kernel 2.4.20 upgraded from Slackware (gcc 2.95.3) running on
> another box with the identical CPU and main board (but with 192MB RAM).
> Does this message hurt anything?
Can you please provide additional details about your hardware?
What kind of main board are you using, and what southbridge?
What is the reported latency of your IDE interface?
These messages always appear on virtual consoles of one particular machine.
These messages are kernel warnings regarding some kind of locking/timing
issue with a certain bridge controller, as far as I know. I suspect one
of the ALi chips on my TransMeta TM5800 (ALi M1535 integrated southbridge)
to be the culprit, likely the M1533 PCI-ISA bridge or M5229 IDE controller,
which claims to be bridged with an ALi M7101 PMU, although I have a number
of other unidentified ALi chips on that board, including an ALi M5819P,
which I'm guessing is some kind of timing chip that doesn't register
with the kernel.
Details aside, this message is an increasingly common problem. Simply
do a Google search for i8253 and you'll see what I mean. As far as I
can tell, since my LFS system running 2.4.21-xfs on this hardware has
been up for over 63 days and counting, these reset messages are not
harmful. They are only a bit of a nuisance as they constantly overflow
my /proc/kmsg, rendering dmesg rather useless. Anyway, I would be very
interested to see what other hardware on which this may be seen.
Regards,
Dan Bernard
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
next prev parent reply other threads:[~2003-10-30 17:23 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 [this message]
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
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=20031030171235.GA59683@teraz.cwru.edu \
--to=djb29@cwru.edu \
--cc=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