Date: Thu, 12 Dec 2002 14:39:03 +0100
From: Roger Luethi <rl@hellgate.ch>
To: Alan Cox <alan@ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: i8253 count too high! resetting..
Message-ID: <20021212133903.GB3224@k3.hellgate.ch>
Mail-Followup-To: Alan Cox <alan@ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1110
Lines: 28

I'm getting my sys log filled with "i8253 count too high! resetting.." in
2.4.21-pre1.

The same happened in 2.2.19 with the kernel suggesting the culprit was a
VIA686a -- which it wasn't, the chipset's ALi. The trigger differs only
so slightly: 2.2.19 tests for
count > LATCH-1
whereas 2.4.21-pre1 checks
count > LATCH

The rate is high enough to be quite annoying -- here's a syslog snippet:

Dec 12 14:02:33 k3 kernel: i8253 count too high! resetting..
Dec 12 14:05:23 k3 kernel: i8253 count too high! resetting..
Dec 12 14:05:51 k3 kernel: i8253 count too high! resetting..
Dec 12 14:06:29 k3 kernel: i8253 count too high! resetting..
Dec 12 14:07:30 k3 kernel: i8253 count too high! resetting..

FWIW the board (an Asus A7A266) has worked reasonably well for over a year
and I hadn't gotten the impression so far that the timer needs fixing
desperately.

Roger
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/