[TriLUG] Re: Problems with Redhat 9/2.4.20-19.9

[fgentili at ialeware.it]

Hi,

This is your question reporting a problem strange problem, here is possible
to find OOPS and debug messages ....
http://www.trilug.org/pipermail/trilug/Week-of-Mon-20030804/018952.html


I have the same problem with RedHat 7.3
It seem's that sometime the host reboot automatically or gone in kernel
panic.

this are my logs

Oct 28 09:48:33 lxmbl ntpd[557]: kernel time discipline status change 41
Oct 31 10:20:35 lxmbl syslogd 1.4.1: restart.
Oct 31 10:20:35 lxmbl syslog: syslogd startup succeeded
Oct 31 10:20:35 lxmbl syslog: klogd startup succeeded
Oct 31 10:20:35 lxmbl kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 31 10:20:35 lxmbl kernel: Linux version 2.4.18-3
(bhcompile at daffy.perf.redhat.com) (gcc version 2.96 20000731 (Red Hat Linux
7.3 2.96-110)) #1 Thu Apr 18
07:37:53 EDT 2002
Oct 31 10:20:35 lxmbl kernel: BIOS-provided physical RAM map:
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 0000000000000000 -
000000000009fc00 (usable)
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 000000000009fc00 -
00000000000a0000 (reserved)
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 00000000000e5400 -
0000000000100000 (reserved)
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 0000000000100000 -
000000000bef0000 (usable)
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 000000000bef0000 -
000000000beffc00 (ACPI data)
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 000000000beffc00 -
000000000bf00000 (ACPI NVS)
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 000000000bf00000 -
000000000c000000 (reserved)
Oct 31 10:20:35 lxmbl kernel:  BIOS-e820: 00000000fff00000 -
0000000100000000 (reserved)
Oct 31 10:20:35 lxmbl kernel: On node 0 totalpages: 48880


It seems that the problem depend on  Time Clock .... could it kill syslog
service ???

I have lot of this messages , look at the first line it's equal to one of
yours before the kernel panic ...
I'm Italian and, here, last friday National Clock was change back of 1
hour.
After I changed the time in another  linux RedHat 7.2 the machine was
crashed !!!!!

I'm not sure but I think that the problem is the Linux Time Clock access
....

I stopped NTPD  and i'm waiting for error  .....

Best Regard
Gentili Filippo