Very Computer

1. i8253 count too high! resetting..

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

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. VIA KT133A driver

3. A7A266 motherboard and i8253 count

4. Help with CP command

5. cvs kernel: i8253 count too high!

6. FreeBSD Dial-In

7. Additional information on "Invisible cursor"

8. sard patch for 2.4 - again

9. Additional Information ----- Make File --- VPATH usage problem

10. Apache 1.3.3 and Servlets additional information

11. Additional information: Connected, Inc.

12. rh9 2.5 kernel additional information

13. Additional Information in case of core dump