Skip to contentSkip to conversation

Linux 2.4.3-ac9

DISCUSSION Jason Thomas 4 participants 5 messages Apr 18, 2001

lore
Share & tools
lore
#0 lore raw

Alan,

This does not seem to fix the problem with "clock timer", which repeatedly prints the following message:

probable hardware bug: clock timer configuration lost - probably a VIA686a motherboard. probable hardware bug: restoring chip configuration.

The machine does not get any further than printing the above message. This message only appears with an SMP kernel, there are no ide devices in the machine.

a generic 2.4.3 kernel works on the machine.

Thanks.

Quoted 5 lines · Alan Cox

VIA users should test this kernel carefully. It has what are supposed to be
the right fixes for the VIA hardware bugs. Obviously the right fixes are not
as tested as the deduced ones.

Signature · 4 lines
Jason Thomas                           Phone:  +61 2 6257 7111
System Administrator  -  UID 0         Fax:    +61 2 6257 7311
tSA Consulting Group Pty. Ltd.         Mobile: 0418 29 66 81
1 Hall Street Lyneham ACT 2602         http://www.topic.com.au/
#1 lore raw
Quoted 11 lines · Jason Thomas

Alan,

This does not seem to fix the problem with "clock timer", which repeatedly prints the following message:

probable hardware bug: clock timer configuration lost - probably a VIA686a motherboard. probable hardware bug: restoring chip configuration.

The machine does not get any further than printing the above message. This message only appears with an SMP kernel, there are no ide devices in the machine.

I've seen this on my Dell P3 700 machine several times. Seems to happen at odd intervals after I use my CD burner, but that just might be coincidental. But I'd like to point out that I've never seen this on my VIA686a itself. The P3 machine is UP too, not SMP. I saw this ever since I switched the machine to 2.4.2-ac8 and beyond (previously 2.2.18).

-Byron

Signature · 3 lines
Byron Stanoszek                         Ph: (330) 644-3059
Systems Programmer                      Fax: (330) 644-8110
Commercial Timesharing Inc.             Email: [email protected]
#3 lore raw
In reply to Jason Thomas

This particular motherboard is an ASUS CUV4X-DLS, the chipset is a VIA694XDP, the IDE chipset however is a VIA686b.

I've seen this in all the kernels I've tried with the "ac" patches.

Any kernel I've tried that are NOT SMP work fine.

Quoted 13 lines · Byron Stanoszek
Quoted 5 lines

This does not seem to fix the problem with "clock timer", which repeatedly prints the following message:

probable hardware bug: clock timer configuration lost - probably a VIA686a motherboard. probable hardware bug: restoring chip configuration.

I've seen this on my Dell P3 700 machine several times. Seems to happen at odd intervals after I use my CD burner, but that just might be coincidental. But I'd like to point out that I've never seen this on my VIA686a itself. The P3 machine is UP too, not SMP. I saw this ever since I switched the machine to 2.4.2-ac8 and beyond (previously 2.2.18).

-Byron

Signature · 4 lines
Jason Thomas                           Phone:  +61 2 6257 7111
System Administrator  -  UID 0         Fax:    +61 2 6257 7311
tSA Consulting Group Pty. Ltd.         Mobile: 0418 29 66 81
1 Hall Street Lyneham ACT 2602         http://www.topic.com.au/
#4 lore raw
In reply to Jason Thomas
Quoted 2 lines · Byron Stanoszek

I've seen this on my Dell P3 700 machine several times. Seems to happen at odd intervals after I use my CD burner, but that just might be coincidental. But

I have seen this related to the cd burner as well. it's not a via board here, but is SMP.

Signature · 3 lines
Grobbebol's Home                   |  Don't give in to spammers.   -o)
http://www.xs4all.nl/~bengel       | Use your real e-mail address   /\
Linux 2.2.16 SMP 2x466MHz / 256 MB |        on Usenet.             _\_v  
#2 lore raw
In reply to Byron Stanoszek
Quoted 4 lines

intervals after I use my CD burner, but that just might be coincidental. But I'd like to point out that I've never seen this on my VIA686a itself. The P3 machine is UP too, not SMP. I saw this ever since I switched the machine to 2.4.2-ac8 and beyond (previously 2.2.18).

At the moment the test is too sensitive - its harmless when it triggers in error. Im still playing with it.