11-14-2008
'Many lost ticks' has nothing to do with the motherboard battery, since the clock in question is not a real-time clock but a high-resolution CPU clock. My guess is the error is exactly what it says it is -- some kernel driver went awry and was hogging interrupts, and eventually caused a kernel panic. Did you upgrade or reconfigure your kernel recently?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi!!!
I installed the patch: DUV40F16-C0040500-10245-Manual-20010328 to avoid a reboot problem in my server, AlphaServer 4100 with Tru64 4.0F.
When the patch instalation finished I rebuild the kernel like this:
# duconfig -c ORACLE-TEST
Start de rebuild and a few minutes after appear... (0 Replies)
Discussion started by: irasela
0 Replies
2. Red Hat
helo,
my system is runing on redhat 9.0.
but now when i run my machine i got the following error.
Kernel Panic:No init found.
try passing init = option to kernel.
i dont have any idea about linux administration.
can u help me to solve this error
Thanks and Regards,... (2 Replies)
Discussion started by: amitpansuria
2 Replies
3. SCO
Hi All,
While installing a Service Pack on my Unix Solaris machine, i got the following error:
UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY
UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME"
UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Discussion started by: am_yadav
9 Replies
4. Solaris
Hi gurus
Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value
Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies
5. Debian
I'm using Debian 5.0.4 Lenny. Daily my logs kern.log, messages, and syslog are filled with errors regarding dircolors:
I've googled this to death and still haven't found a solution to fix or stop this.
I read on man dircolors to: dircolors --version
The output I receive on this cmd is... (0 Replies)
Discussion started by: juliej
0 Replies
6. Red Hat
Hi Guys,
I'm working with a down RedHat Server. Whenever the server tries to boot, there's an error stating:
Kernel panic: No init found. Try passing init= option to kernel.
In addition to this, the "Caps Lock" and "Scroll Lock" lights start flashing. The server doesn't boot pass this... (1 Reply)
Discussion started by: bbbngowc
1 Replies
7. Ubuntu
Hi
I'm compiling a real-time kernel in linux, but after I type make bzImage things end with this:
(Things going well doing CC and things)....
CC arch/x86/kernel/kgdb.o
CC arch/x86/kernel/vm86_32.o
CC arch/x86/kernel/early_printk.o
CC arch/x86/kernel/ipipe.o... (2 Replies)
Discussion started by: mdop
2 Replies
8. UNIX for Dummies Questions & Answers
Hi I m using redhat 6 with kernel release
2.6.32-71.el6.i686
I have downloaded latest kernel 3.3.1 from kernel.org .
when i run make module_install i get below error.
# make modules_install
/usr/src/kernels/linux-3.3.1/scripts/depmod.sh: line 37: 11314 Killed ... (0 Replies)
Discussion started by: pinga123
0 Replies
9. SCO
SCO Unix 5.0.5
wd Srom 1
/var/opt/K/SCO/link/1.1.0Eb/etc/conf/cf.d/msci - parameter count
Idbuild idscsi had errors
System build failed.
Any idea ? (1 Reply)
Discussion started by: lakicevic
1 Replies
10. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
LEARN ABOUT NETBSD
inittodr
INITTODR(9) BSD Kernel Developer's Manual INITTODR(9)
NAME
inittodr -- initialize system time
SYNOPSIS
void
inittodr(time_t base);
DESCRIPTION
The inittodr() function determines the time and sets the system clock. It tries to pick the correct time using a set of heuristics that
examine the system's battery-backed clock and the time reported by the file system, as given in base. Those heuristics include:
o If the battery-backed clock has a valid time, and is not significantly behind the time provided by base, it is used.
o If the battery-backed clock does not have a valid time, or is significantly behind the time provided in base, and the time provided in
base is within reason, base is used as the current time.
o If the battery-backed clock appears invalid, and base appears non-sensical or was not provided (was given as zero), an arbitrary base
(typically some time within the same year that the kernel was last updated) will be used.
Once a system time has been determined, it is stored in the time variable.
DIAGNOSTICS
The inittodr() function prints diagnostic messages if it has trouble figuring out the system time. Conditions that can cause diagnostic mes-
sages to be printed include:
o There is no battery-backed clock present on the system.
o The battery-backed clock's time appears nonsensical.
o The base time appears nonsensical.
o The base time and the battery-backed clock's time differ by a large amount.
SEE ALSO
clock_ymdhms_to_secs(9), resettodr(9), time_second(9)
BUGS
Some systems use heuristics for picking the correct time that are slightly different.
BSD
September 6, 2006 BSD