Displaying 4 results from an estimated 4 matches for "time_32".
2009 Jul 07
1
Installation from source on Ubuntu 9.04, make kernel failure
..._MISMATCH=y''
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
arch/x86/kernel/built-in.o: In function `timer_interrupt'':
/usr/src/buildir/linux-2.6.29.4/arch/x86/kernel/time_32-xen.c:465: undefined reference to `__udivdi3''
make: *** [.tmp_vmlinux1] Error 1
---------------------------------------------------------
Installation steps:
1. Install Mercurial and Git (hg) :-
# apt-get install mercurial gitk
2. Building Xen:-
# cd /usr/src
# hg clone http://xenb...
2010 Jan 03
21
Re: Xenified linux kernel
...ON_MISMATCH=y''
GEN .version
CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
arch/x86/kernel/built-in.o: In function `timer_interrupt'':
/usr/src/build/linux-2.6.30.2/arch/x86/kernel/time_32-xen.c:463:
undefined reference to `__udivdi3''
make: *** [.tmp_vmlinux1] Error 1
--
Best Regards,
Mehdi Sheikhalishahi
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
2010 Jan 13
65
ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
On a selection of boxes, ntpd running in Xen Dom0 reproducibly
exhibits extermely high noise/jitter.
Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise.
Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0?
Is the problem a config issue, or a bug?
Already reported this downstream; everybody''s "stumped".
2010 Jan 13
65
ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
On a selection of boxes, ntpd running in Xen Dom0 reproducibly
exhibits extermely high noise/jitter.
Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise.
Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0?
Is the problem a config issue, or a bug?
Already reported this downstream; everybody''s "stumped".