Messages in this thread | | | Date | Wed, 29 May 2002 14:05:15 +0200 | From | Vojtech Pavlik <> | Subject | Re: odd timer bug, similar to VIA 686a symptoms |
| |
On Wed, May 29, 2002 at 01:46:27PM +0100, Alan Cox wrote: > On Wed, 2002-05-29 at 10:25, Neale Banks wrote: > >> May 28 11:19:54 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65485 [0xffcd] > > May 28 11:19:55 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce] > > May 28 11:19:56 gull kernel: timer.c: VIA bug check triggered. Value read 65500 [0xffdc], re-read 65486 [0xffce] > > May 28 11:19:57 gull kernel: timer.c: VIA bug check triggered. Value read 65499 [0xffdb], re-read 65484 [0xffcc] > > May 28 11:19:58 gull kernel: timer.c: VIA bug check triggered. Value read 65497 [0xffd9], re-read 65483 [0xffcb] > > > > Anyone got any good theories what's going on here, given that this is a > > ~1995 vintage laptop with a Pentium-120 (which I'm assured doesn't have a > > VIA 686a ;-)? > > Neptune chipsets at least had latching bugs on timer reads. What chipset > is the laptop ?
This is unlikely to be the latching bug - note the values are near to 65535 - that means the timer is reprogrammed to count from 0xffff down instead from LATCH. That is because of the suspend I presume. What's weird is that the VIA fix doesn't program it to the correct value, or perhaps is that missing from the patch?
-- Vojtech Pavlik SuSE Labs - 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/
| |