Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: Dan Slagle on February 03, 2002, 07:32:34 AM
-
Since upgrading to SME 5.1 I have been seeing the following in the message.log. From what I have found out this is some type of bug with the 2.4 kernel. Anyone know the trick to get it to stop?
Feb 2 22:21:50 raverx kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a.
Feb 2 22:21:50 raverx kernel: probable hardware bug: restoring chip configuration.
Feb 2 22:57:12 raverx kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a.
Feb 2 22:57:12 raverx kernel: probable hardware bug: restoring chip configuration.
Feb 2 22:58:30 raverx kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a.
Feb 2 22:58:30 raverx kernel: probable hardware bug: restoring chip configuration.
Feb 2 23:00:35 raverx kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a.
Feb 2 23:00:35 raverx kernel: probable hardware bug: restoring chip configuration.
-
Update. The SME server is now crashing about once a day. I was running solid on e-smith 4.x for quite some time before this. Disappointing.
-
System was too unstable. Reverted to 5.02. No issues.
-
Opps I was incorrect.
Feb 4 11:44:28 raverx kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a.
Feb 4 11:44:28 raverx kernel: probable hardware bug: restoring chip configuration.
-
Dan Slagle wrote:
>
> Since upgrading to SME 5.1 I have been seeing the following
> in the message.log. From what I have found out this is some
> type of bug with the 2.4 kernel.
SME 5.1 does not use the 2.4 kernel. And it uses exactly the same kernel which is used in SME 5.0 too. Are you sure that you don't have a hardware problem?
Charlie
-
Opps I was incorrect.
Feb 4 11:44:28 raverx kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a.
Feb 4 11:44:28 raverx kernel: probable hardware bug: restoring chip configuration.
> Hi.
>
> That's a VIA timer bug. The patch that fixes it was inthe kernel some
> time ago, but was removed because the workaround was being triggered
> when it shouldn't, if I remember correctly.
>
> Here:
>
>
> --- linux-2.4.15-pre3/arch/i386/kernel/time.cSun Nov 11 21:33:31 2001
> +++ linux-2.4.15-pre3-new/arch/i386/kernel/time.cMon Nov 12 14:04:20 2001
> @@ -501,6 +501,19 @@
>
> count = inb_p(0x40); /* read the latched count */
> count |= inb(0x40) << 8;
> +
> + /*
> + * When using some via chipsets (as the vt82c686a, for example)
> + * the system timer counter (i8253) should be reprogrammed in
> + * this case, otherwise it may be reset to a wrong value.
> + */
> +if (count > LATCH-1) {
> +outb_p(0x34, 0x43);
> + outb_p(LATCH & 0xff, 0x40);
> +outb(LATCH >> 8, 0x40);
> +count = LATCH - 1;
> +}
> +
> spin_unlock(&i8253_lock);
>
> count = ((LATCH-1) - count) * TICK_SIZE;
> I tested this patch with 2.4.17rc[1|2] - and I couldn't find any
problem. The systemtime has always been correct.
-
I am not saying I do not have a hardware issue, but the timimg of this would be amazing! It only took 10 minutes to do a clean install of 5.1 and started happening almost immediatly. I had a least, five(5), hard, no-sync, crashes yesterday with it.
I DO KNOW that the system has not crashed since the downgrade to 5.03. I have only seen this error 19 times in 18 hours. It was like every minute with 5.1. What would you like me to do??? It is not a production box so I am free to test. Let me know.
[root@raverx /boot]# grep VIA686a. /var/log/messages|wc -l
19
[root@raverx /boot]# uptime
5:47pm up 18:10, 1 user, load average: 1.04, 1.03, 1.00
-
Had 20 more notices in the last 4 hours then.... crash! Damn. Ah well I made it 22 hours.
-
Downgrade to 4.1.2. No errors, as of yet. At least it is not a hardware issue! If I am stuck here in 2.2 land, what is the best way to stay current with security patches?
-
Welcome to the March Networks SME Server V5.0
Kernel 2.2.19-7.0.8 on an i686
[root@server /root]# grep VIA686a /var/log/messages|wc -l
5
[root@server /root]#
I've had a few of those pop up as well but the server hasn't gone belly up over it yet.
-
Anyone?