Having looked through the log file /var/adm/messages i've noticed these kernel warning messages and i don't know what they mean:
I have looked google to find an explanation and from the few bits i have found i seems as though it relates to bios. But in the posts i found, those people were using multi-core processors where as i am not (don't know if that's relevant or not).
I'm using a Dell OptiPlex 170L and the processor is Intel Pentium 4.
Does anyone know what they mean and if it means there's a problem what i can do to correct it?
Hi,
I have a SunFire V490, Solaris 10 with XP1024 storage and HP Library. I have noticed the following error messages in the /var/adm/messages file. These errors are being generated constantly. Also commands like devfsadm, format cfgadm etc are getting hung. After a reboot it works fine for a... (1 Reply)
Hi
I've been using solaris for a few days now. During the install process i had some problems configuring my nic as i needed to install a third-party driver, which i got from a a linked site from the Sun Device Detector tool a ran prior to installing. I got it working eventually, but i'm... (1 Reply)
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
Hello,
I am using Solaris 10 and I'm geting the folowing error in /var/adm/messages.
Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) set threshold to default values
Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) threshold values... (4 Replies)
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
Hi folks,
In what circumstance does the log move to
/var/adm/messages.0.......messages.1,messages.2,messages.3 .......etc
---------- Post updated at 06:23 PM ---------- Previous update was at 06:17 PM ----------
To make my questions more understandable,
What are the processes that... (4 Replies)
This is isolated to just 1 non-global zone out of many zones managed
This is a Solaris 11 system on SPARC
This is NOT a branded zone
syslogd is active
This came to our attention when one of our scripts didn't run over the weekend prompting us to check our messages logging in... (6 Replies)
Discussion started by: samthewildone
6 Replies
LEARN ABOUT FREEBSD
timecounters
TIMECOUNTERS(4) BSD Kernel Interfaces Manual TIMECOUNTERS(4)NAME
timecounters -- kernel time counters subsystem
SYNOPSIS
The kernel uses several types of time-related devices, such as: real time clocks, time counters and event timers. Real time clocks are
responsible for tracking real world time, mostly when the system is down. Time counters are responsible for tracking purposes, when the sys-
tem is running. Event timers are responsible for generating interrupts at a specified time or periodically, to run different time-based
events. This page is about the second.
DESCRIPTION
Time counters are the lowest level of time tracking in the kernel. They provide monotonically increasing timestamps with known width and
update frequency. They can overflow, drift, etc and so in raw form can be used only in very limited performance-critical places like the
process scheduler.
More usable time is created by scaling the values read from the selected time counter and combining it with some offset, regularly updated by
tc_windup() on hardclock() invocation.
Different platforms provide different kinds of timer hardware. The goal of the time counters subsystem is to provide a unified way to access
that hardware.
Each driver implementing time counters registers them with the subsystem. It is possible to see the list of present time counters, via the
kern.timecounter sysctl(8) variable:
kern.timecounter.choice: TSC-low(-100) HPET(950)i8254(0)ACPI-fast(900) dummy(-1000000)
kern.timecounter.tc.ACPI-fast.mask: 16777215
kern.timecounter.tc.ACPI-fast.counter: 13467909
kern.timecounter.tc.ACPI-fast.frequency: 3579545
kern.timecounter.tc.ACPI-fast.quality: 900
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.i8254.counter: 62692
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.HPET.counter: 3013495652
kern.timecounter.tc.HPET.frequency: 14318180
kern.timecounter.tc.HPET.quality: 950
kern.timecounter.tc.TSC-low.mask: 4294967295
kern.timecounter.tc.TSC-low.counter: 4067509463
kern.timecounter.tc.TSC-low.frequency: 11458556
kern.timecounter.tc.TSC-low.quality: -100
The output nodes are defined as follows:
kern.timecounter.tc.X.mask is a bitmask, defining valid counter bits,
kern.timecounter.tc.X.counter is a present counter value,
kern.timecounter.tc.X.frequency is a counter update frequency,
kern.timecounter.tc.X.quality is an integral value, defining the quality of this time counter compared to others. A negative value means
this time counter is broken and should not be used.
The time management code of the kernel chooses one time counter from that list. The current choice can be read and affected via the
kern.timecounter.hardware tunable/sysctl.
SEE ALSO attimer(4), eventtimers(4), ffclock(4), hpet(4)BSD April 12, 2014 BSD