mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tim Moore <timothymoore@bigfoot.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: "clock timer configuration lost" error?
Date: Mon, 26 Feb 2001 01:18:19 -0800	[thread overview]
Message-ID: <3A9A1F5B.AF529C8F@bigfoot.com> (raw)

For no apparent reason:

...
Feb 26 00:15:50 abit xntpd[886]: synchronized to 192.6.38.127, stratum=1
Feb 26 00:19:52 abit kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a. 
Feb 26 00:19:52 abit kernel: probable hardware bug: restoring chip
configuration. 
Feb 26 00:26:53 abit xntpd[886]: synchronized to 132.239.254.5,
stratum=2
...

Anyone have a clue about the 'probable hdw bug' messages?  No disk
activity to speak of, no other symptoms and/or messages.

rgds,
tim.

# cat proc/version; lspci
Linux version 2.2.19pre8+IDE (root@abit) (gcc version egcs-2.91.66
19990314/Linux (egcs-1.1.2 release)) #8 Thu Feb 22 18:12:29 PST 2001

00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0391 (rev
02)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8391
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev
22)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev
10)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
(rev 30)
00:08.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 OHCI Compliant
IEEE-1394 Controller
00:09.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI]
00:0b.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
20)
01:00.0 VGA compatible controller: nVidia Corporation Riva TNT2 Model 64
(rev 11)

--

             reply	other threads:[~2001-02-26 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26  9:18 Tim Moore [this message]
2001-02-26 14:57 ` Alan Cox
2001-02-26 15:51   ` Tim Moore
2001-05-13 21:49 Gab

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=3A9A1F5B.AF529C8F@bigfoot.com \
    --to=timothymoore@bigfoot.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®