Skip to contentSkip to conversation

probable hardware bug: clock timer ... (Asus board)?!?

DISCUSSION Andreas K. Huettel 1 participant 1 message Dec 26, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 000801c18abb$593ef460$0101a8c0@home

#1 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[Since lots of people are asking me similar questions, I'm cc-ing this to the linux-kernel list.]

Hi Bruno,

I never found any solution for the "probable hardware bug: clock timer ... on Asus A7A266 board" error message.

However, I solved the problem of growing logfiles, by just using an old kernel that does not yet check for this error condition (2.4.4-4GB as shipped with SuSE72).

The machine is a web and file server (apache, samba, kernel-nfs), and apart from some minor graphics-related difficulties, it has been running rock-solid since then. So whatever internal problem the message exactly indicates, it seems to have no real world effect in this case?!?

kind regards,
Andreas

On Sat, 22 Dec 2001, Bruno Quoitin wrote:

#]Date: Sat, 22 Dec 2001 08:36:19 +0100
#]From: Bruno Quoitin <[email protected]>
#]To: [email protected]
#]Subject: Re: probable hardware bug: clock timer ... (Asus board)?!? #]
#]I have the same problem than the one you described in the follofing #]mail (found in #]http://www.uwsg.iu.edu/hypermail/linux/kernel/0106.1/0014.html). Did #]you get any answer ?
#]
#]Bruno.
#]
#]-- your mail --
#]
#]Dear kernel specialists,
#]
#]
#]Jun 8 03:00:39 qubit kernel: probable hardware bug: clock timer #]configuration lost - probably a VIA686a.
#]Jun 8 03:00:39 qubit kernel: probable hardware bug: restoring chip #]configuration.
#]
#]
#]can anybody please tell me what is the exact _impact_ of this problem? I #]get these messages on an idle machine with Asus A7A266 motherboard (not #]VIA) (planned nfs server) about every 2-5 minutes. Kernel 2.2.18 as #]shipped with SuSE 7.1 (k_default).
#]
#]
#]- From code snippets I have seen, this means the clock is jumping #]around?!? Has anybody found a way to get rid of this problem? #](Yes, I know, this has been discussed before, but I did not see any #]resolution). For /proc/pci see below, if you need any more info, feel free #]to contact me.
#]
#]
#]best regards, Andreas
#]
#]

- ---------------------------------------------------------------------
Dipl.-Phys. Andreas K. Huettel tel. +49 89 2180 3349 (univ.)
Sektion Physik der LMU fax +49 89 2180 2069 (univ.)
LS Prof. J.P. Kotthaus
Geschwister-Scholl-Platz 1 [email protected]
80539 Muenchen [email protected]
Germany http://www.akhuettel.de/research/
- --------------------------------------------------------------------- Please use GNUPG or PGP for signed and encrypted email. My public key can be found at http://www.akhuettel.de/pgp_key.html
- ---------------------------------------------------------------------

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8KbHvL+gLs3iH94cRAjzpAJ9rqAHtyCsed5Y075qYmKFNe9drcACeNris R+0/4nMrYRvbNuieyKq6Ux0=
=9WWB
-----END PGP SIGNATURE-----