From: Vojtech Pavlik <vojtech@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Neale Banks <neale@lowendale.com.au>, linux-kernel@vger.kernel.org
Subject: Re: odd timer bug, similar to VIA 686a symptoms
Date: Wed, 29 May 2002 14:05:15 +0200 [thread overview]
Message-ID: <20020529140515.A8522@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.05.10205291912340.2523-100000@marina.lowendale.com.au> <1022676387.4124.162.camel@irongate.swansea.linux.org.uk>
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
next prev parent reply other threads:[~2002-05-29 12:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 9:25 odd timer bug, similar to VIA 686a symptoms Neale Banks
2002-05-29 12:46 ` Alan Cox
2002-05-29 12:05 ` Vojtech Pavlik [this message]
2002-05-29 13:40 ` Neale Banks
2002-05-29 12:58 ` Vojtech Pavlik
2002-05-29 13:18 ` Neale Banks
2002-05-29 13:48 ` Alan Cox
2002-05-29 13:47 ` Neale Banks
2002-05-29 14:55 ` Alan Cox
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=20020529140515.A8522@ucw.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=neale@lowendale.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.