clock timer configuration lost - probably a VIA686a motherboard

Hallo all,

I found some posts in this list to the problem mentioned in the subject and want to tell about my experiences. Maybe it can help to detect the problem.

I got a lot of messages while continuous writing / reading datas from one a harddisk to another harddisk (both at 1. ide-channel) during backup with rsync. Both harddisks use udma4. The data-stream was between 0,5 MB/s and 20MB/s.
I never got these messages before and after the backup finished I couldn't see them anymore.

Apr 22 10:41:38 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 10:41:38 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 10:44:29 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 10:44:29 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 10:44:34 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 10:44:34 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 10:44:43 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 10:44:43 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:08:23 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:08:23 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:11:51 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:11:51 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:13:30 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:13:30 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:17:38 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:17:38 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:17:39 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:17:39 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:17:41 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:17:41 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:17:46 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:17:46 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:18:39 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:18:39 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:18:44 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:18:44 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:20:33 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:20:33 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:20:38 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:20:38 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:20:56 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:20:56 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:21:20 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:21:20 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:21:25 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:21:25 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:21:28 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:21:28 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:21:33 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:21:33 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:21:39 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:21:39 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:35:07 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:35:07 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:38:03 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:38:03 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:38:32 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:38:32 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:38:52 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:38:52 athlon kernel: probable hardware bug: restoring chip 
configuration.
Apr 22 11:44:40 athlon kernel: probable hardware bug: clock timer 
configuration lost - probably a VIA686a motherboard.
Apr 22 11:44:40 athlon kernel: probable hardware bug: restoring chip 

configuration.

I have a EP7KXA-Board with VIA-KX133-chipset.

cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:

    Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 2).
      Prefetchable 32 bit memory at 0xd6000000 [0xd7ffffff].

Bus 0, device 1, function 0:
PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP] (rev 0).
Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 34).
Bus 0, device 7, function 1:
IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 16).
Master Capable. Latency=32.
I/O at 0xd000 [0xd00f].
Bus 0, device 7, function 2:
USB Controller: VIA Technologies, Inc. UHCI USB (rev 16).
IRQ 9.
Master Capable. Latency=32.
I/O at 0xd400 [0xd41f].
Bus 0, device 7, function 4:
Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 48).
IRQ 9.
Bus 0, device 7, function 5:
Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller
(rev 32).

      IRQ 5.
      I/O at 0xdc00 [0xdcff].
      I/O at 0xe000 [0xe003].
      I/O at 0xe400 [0xe403].
  Bus  0, device   8, function  0:
    Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 
Ethernet (rev 2).
      IRQ 10.
      Master Capable.  Latency=32.  Min Gnt=52.Max Lat=11.
      I/O at 0xe800 [0xe8ff].
      Non-prefetchable 32 bit memory at 0xd9000000 [0xd9000fff].
  Bus  0, device   9, function  0:
    Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 16).
      IRQ 11.
      Master Capable.  Latency=32.  Min Gnt=32.Max Lat=64.
      I/O at 0xec00 [0xecff].
      Non-prefetchable 32 bit memory at 0xd9001000 [0xd90010ff].
  Bus  1, device   0, function  0:
    VGA compatible controller: ATI Technologies Inc Rage 128 PF (rev 0).
      IRQ 10.
      Master Capable.  Latency=32.  Min Gnt=8.
      Prefetchable 32 bit memory at 0xd0000000 [0xd3ffffff].
      I/O at 0xc000 [0xc0ff].
      Non-prefetchable 32 bit memory at 0xd5000000 [0xd5003fff]

Regards,
Andreas Hartmann

Thy do trigger to easily. Im still investigating that

Well... I remember this message showing on my console, although I was doing nothing special...

Apr 18 14:37:01 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:37:01 blackbird kernel: probable hardware bug: restoring chip
configuration.
--
Apr 18 14:41:18 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:41:18 blackbird kernel: probable hardware bug: restoring chip
configuration.
--
Apr 18 14:47:10 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:47:10 blackbird kernel: probable hardware bug: restoring chip
configuration.
--
Apr 18 14:48:28 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:48:28 blackbird kernel: probable hardware bug: restoring chip
configuration.
--
Apr 18 14:49:02 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:49:02 blackbird kernel: probable hardware bug: restoring chip
configuration.
--
Apr 18 14:51:06 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:51:06 blackbird kernel: probable hardware bug: restoring chip
configuration.
--
Apr 18 14:51:48 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:51:48 blackbird kernel: probable hardware bug: restoring chip
configuration.
--
Apr 18 14:52:01 blackbird kernel: probable hardware bug: clock timer
configuration lost - probably a VIA686a.
Apr 18 14:52:01 blackbird kernel: probable hardware bug: restoring chip

configuration.
--

[root@blackbird log]# uname -a
Linux blackbird.tecnoera.com 2.2.19 #2 Wed Apr 11 12:23:14 CLT 2001 i686 unknown
[root@blackbird log]#

This should have gone on my last email:

[root@blackbird log]# cat /proc/pci
PCI devices found:
Bus 0, device 0, function 0:
Host bridge: VIA Technologies Unknown device (rev 68).
Vendor id=1106. Device id=691.
Medium devsel. Master Capable. No bursts. Prefetchable 32 bit memory at 0xd0000000 [0xd0000008].
Bus 0, device 1, function 0:
PCI bridge: VIA Technologies VT 82C598 Apollo MVP3 AGP (rev 0).
Medium devsel. Master Capable. No bursts. Min Gnt=12.
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies Unknown device (rev 34).
Vendor id=1106. Device id=686.
Medium devsel. Master Capable. No bursts.
Bus 0, device 7, function 1:
IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 16).
Medium devsel. Fast back-to-back capable. Master Capable.
Latency=32.

      I/O at 0xe000 [0xe001].

Bus 0, device 7, function 2:
USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16).
Medium devsel. IRQ 10. Master Capable. Latency=32. I/O at 0xe400 [0xe401].
Bus 0, device 7, function 3:
USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 16).
Medium devsel. IRQ 10. Master Capable. Latency=32. I/O at 0xe800 [0xe801].
Bus 0, device 7, function 4:
Bridge: VIA Technologies Unknown device (rev 48).
Vendor id=1106. Device id=3057.
Medium devsel. Fast back-to-back capable.
Bus 0, device 11, function 0:
Ethernet controller: Intel 82557 (rev 8).
Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable.
Latency=32. Min Gnt=8.Max Lat=56.

      Non-prefetchable 32 bit memory at 0xdb100000 [0xdb100000].
      I/O at 0xec00 [0xec01].
      Non-prefetchable 32 bit memory at 0xdb000000 [0xdb000000].
  Bus  1, device   0, function  0:
    VGA compatible controller: 3Dfx Unknown device (rev 1).
      Vendor id=121a. Device id=5.
      Fast devsel.  Fast back-to-back capable.  IRQ 11.
      Non-prefetchable 32 bit memory at 0xd4000000 [0xd4000000].
      Prefetchable 32 bit memory at 0xd8000000 [0xd8000008].
      I/O at 0xd000 [0xd001].

[root@blackbird log]#

sorry to write so many messages for the same thing... but I fotgot to mention that I'm using 2.2.19, not 2.4.x

that's it.

Am Sonntag, 22. April 2001 14:46 schrieb Alan Cox:

I just read in a german newsgroup from another user, having the same problem, but not with a VIA-chipset, but with a GA-5AX with Ali V Chipsatz + iP 200 MMX. Unfortunately he didn't tell, which kernel he's using and at which situation the message occurs.

Regards,
Andreas Hartmann