kern/98694: alternate system clock dies
Lars Köller
lars.koeller at uni-bielefeld.de
Thu Jun 8 02:44:15 PDT 2006
>Number: 98694
>Category: kern
>Synopsis: alternate system clock dies
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Jun 08 08:00:35 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Lars Köller
>Release: 5.5-RELEASE-p1, i386
>Organization:
University Bielefeld
>Environment:
FreeBSD xxxxxxx 5.5-RELEASE-p1 FreeBSD 5.5-RELEASE-p1 #1: Thu Jun 1 14:41:54 CEST 2006 yyyyyyyy :/opt/tmp/obj/usr/src/sys/PMX i386
>Description:
Server Hardware: FSC RX300 (Fujitsu Siemens Computers)
After an uptime of approx. 5 days I get the message when running
systat -vmstat
The alternate system clock has died!
Reverting to ``pigs'' display.
The "CPU states" line in top is also broken (all values are zero),
dito vmstat CPU values.
All runs well with FreeBSD 4.1 on the same hardware.
BIOS, BMC, etc. is up to date.
The problem is critical for us, cause the Sophos PureMessage collects several statistical OS data of the server with vmstat, etc. These values are all broken after the "clock died".
Reboot fixes the problem for some days.
Kernel Config is:
#
# PMX-Server kernel configuration file for FreeBSD/i386 SMP
#
include GENERIC
#
ident PMX
#
# To make an SMP kernel, the next line is needed
#
options SMP # Symmetric MultiProcessor Kernel
#
# asr old ioctls support, needed by raidutils
#
options ASR_COMPAT
#
#
#
options MAXSSIZ="(2000*1024*1024)"
options MAXDSIZ="(2000*1024*1024)"
options DFLDSIZ="(2000*1024*1024)"
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list