From: Vojtech Pavlik <vojtech@suse.cz>
To: Neale Banks <neale@lowendale.com.au>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: odd timer bug, similar to VIA 686a symptoms
Date: Wed, 29 May 2002 14:58:57 +0200 [thread overview]
Message-ID: <20020529145857.A9813@ucw.cz> (raw)
In-Reply-To: <20020529140515.A8522@ucw.cz> <Pine.LNX.4.05.10205292319090.3388-100000@marina.lowendale.com.au>
On Wed, May 29, 2002 at 11:40:40PM +1000, Neale Banks wrote:
> On Wed, 29 May 2002, Vojtech Pavlik wrote:
>
> [...]
> > On Wed, May 29, 2002 at 01:46:27PM +0100, Alan Cox wrote:
> [...]
> > > 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?
>
> Yes, my version of your patch includes an option to disable the via686a
> fix (and this was in effect at the time - I'm still cringing in fear from
> nasty FS corruption that ensued after a "probable hardware bug: restoring
> chip configuration" message last October :-( - yes it may be unlikely
> that it's related, but I don't yet have any other suspects. FWIW, the
> machine also locked up then).
It shouldn't be able to do anything like that ...
> Any suggestions smarter than backing up everything "important" and running
> the battery down with the VIA fix enabled?
Nope. ;)
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2002-05-29 12:59 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
2002-05-29 13:40 ` Neale Banks
2002-05-29 12:58 ` Vojtech Pavlik [this message]
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=20020529145857.A9813@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.