Compiling CURRENT with XEN config fails

2009-03-27 Thread Mister Olli
Hi,

I just tried to compile CURRENT kernel with the XEN kernel config that
is shipped with it, but it fails with the following error:

cc -c -O -pipe  -std=c99 -g -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-Wundef -Wno-pointer-sign -fformat-extensions -nostdinc  -I.  -I/usr/src/sys 
-I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include 
opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 
--param large-function-growth=1000  -mno-align-long-strings 
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 
-ffreestanding -fstack-protector -Werror  /usr/src/sys/xen/evtchn/evtchn.c
/usr/src/sys/xen/evtchn/evtchn.c:516: error: conflicting types for 
'bind_virq_to_irqhandler'
/usr/src/sys/xen/xen_intr.h:61: error: previous declaration of 
'bind_virq_to_irqhandler' was here
/usr/src/sys/xen/evtchn/evtchn.c: In function 'bind_virq_to_irqhandler':
/usr/src/sys/xen/evtchn/evtchn.c:523: error: 'arg' undeclared (first use in 
this function)
/usr/src/sys/xen/evtchn/evtchn.c:523: error: (Each undeclared identifier is 
reported only once
/usr/src/sys/xen/evtchn/evtchn.c:523: error: for each function it appears in.)
*** Error code 1

Stop in /usr/obj/usr/src/sys/XEN.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
template-8_CURRENT# svn info http://svn.freebsd.org/base/head /usr/src
Path: head
URL: http://svn.freebsd.org/base/head
Repository Root: http://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 190466
Node Kind: directory
Last Changed Author: jamie
Last Changed Rev: 190466
Last Changed Date: 2009-03-27 14:13:59 +0100 (Fri, 27 Mar 2009)

Path: /usr/src
URL: http://svn.freebsd.org/base/head
Repository Root: http://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 190464
Node Kind: directory
Schedule: normal
Last Changed Author: dds
Last Changed Rev: 190464
Last Changed Date: 2009-03-27 12:03:02 +0100 (Fri, 27 Mar 2009)



Anybody knows how to fix this??? ;-))

greetz
Olli

___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: 8-CURRENT does not build without WITNESS activated

2009-02-05 Thread Mister Olli
Hi,

thanks, worked great for me...

I'm glad to see that CURRENT makes so fast progress. Great work :-))

--
Mr. Olli


Am Mittwoch, den 04.02.2009, 20:04 -0800 schrieb Kip Macy:
 adding lock.h will fix that - sorry about it
 
 Thanks,
 Kip
 
 
 On Tue, Feb 3, 2009 at 10:59 AM, Mister Olli mister.o...@googlemail.com 
 wrote:
  Hi.
 
  I'm currently unable to build the 8-CURRENT kernel in a PV domU, without
  options WITNESS in my kernel config.
 
  The output is the following:
  ==
  make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES |  MKDEP_CPP=cc -E
  CC=cc xargs mkdep -a -f .newdep -O -pipe  -std=c99 -g -Wall
  -Wredundant-decls -Wnested-externs -Wstrict-prototypes
  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
  -Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/usr/src/sys
  -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
  -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath
  -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
  -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD
  -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs
  -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb
  -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
  -finline-limit=8000 --param inline-unit-growth=100 --param
  large-function-growth=1000  -mno-align-long-strings
  -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
  -mno-sse3 -ffreestanding -fstack-protector
  In file included from /usr/src/sys/dev/xen/netfront/netfront.c:32:
  /usr/src/sys/sys/sx.h:210:2: error: #error LOCK_DEBUG not defined,
  include sys/lock.h before sys/sx.h
  mkdep: compile failed
  *** Error code 1
 
  Stop in /usr/obj/usr/src/sys/XEN.
  *** Error code 1
 
  Stop in /usr/src.
  *** Error code 1
 
  Stop in /usr/src.
  template_8-CURRENT#
  ==
 
  --
  Mr. Olli
 
 
 
 
  ___
  freebsd-xen@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-xen
  To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org
 

___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: Instable 32bit domU on 64bit dom0 (w/Xen 3.3.1)

2009-02-03 Thread Mister Olli
Hi,

 This should be fixed by r188042. Interrupts need to be disabled on
 entry to the page fault handler or we risk being preempted prior to
 reading cr2 (the faulting address).

Sounds great. I will try to test it as soon as possible, since I ran in
a lot of seg-faults during compiling world under Xen, too.


 There is still another fundamental stability bug whereby timer
 interrupts appear to sometimes be left disabled until another
 interrupt (console, network, disk) comes in at which point they're
 re-enabled. You may or may not hit that, I only have one configuration
 where I'm able to reproduce that issue.

Sounds like the problem I gave up using FreeBSD7 in Xen. My domU halted
(does nothing but was running, even SSH sessions timed out) sometimes
and the only way to get it back to work, was to hit a key on the
console.

I did a temporary fix by 'while (true); do echo e; sleep 10s; done |
xm console domU_name.

--
Mr. Olli


 
 Cheers,
 Kip
 
 
 On Thu, Jan 29, 2009 at 7:34 AM, Kai Mosebach x...@komadev.de wrote:
  Hi,
 
  i recently got my first FreeBSD 8 domU working and i am quite happy to see 
  that there is eventually progress on the important Xen topic for FreeBSD.
  Since this domU as a svn -head checkout from 23.01.09 still segfaults here 
  and there i startet to rebuild the whole world with debugging symbols in 
  the hope that the backtraces give more info's on where to find bugs.
 
  Here are the first results from several core files which hang around in the 
  system after a world build and i hope the developers here can make more 
  sense out of it than me.
 
  If you need further dumps/traces or have some advises how to go on from 
  here, please let me know!
 
  Best Kai
 
  /usr/obj/usr/src/make.core
 
  Program terminated with signal 11, Segmentation fault.
  #0  0x0804da01 in Cmd_Exec (
cmd=0x2812df00 /usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin make   
  __MAKE_CONF=/etc/make.conf  -f /dev/null -V MAKEOBJDIRPREFIX dummy,
error=0xbf7fdb18) at /usr/src/usr.bin/make/job.c:2713
  2713if ((ps.child_pid = vfork()) == -1) {
  (gdb) bt
  #0  0x0804da01 in Cmd_Exec (
cmd=0x2812df00 /usr/bin/env -i PATH=/sbin:/bin:/usr/sbin:/usr/bin make   
  __MAKE_CONF=/etc/make.conf  -f /dev/null -V MAKEOBJDIRPREFIX dummy,
error=0xbf7fdb18) at /usr/src/usr.bin/make/job.c:2713
  #1  0x080544ed in Parse_DoVar (line=0x28128b00 _MAKEOBJDIRPREFIX,
ctxt=0x2810e200) at /usr/src/usr.bin/make/parse.c:1520
  #2  0x08055a1a in Parse_File (name=0xbf7fdbf8 /usr/src/Makefile,
stream=0x80a4960) at /usr/src/usr.bin/make/parse.c:2457
  #3  0x08051e68 in ReadMakefile (p=Variable p is not available.
  ) at /usr/src/usr.bin/make/main.c:323
  #4  0x08051f24 in TryReadMakefile (p=0x8094744 Makefile)
at /usr/src/usr.bin/make/main.c:342
  #5  0x080527c3 in main (argc=1, argv=0xbf7feddc)
at /usr/src/usr.bin/make/main.c:1209
  (gdb)
 
 
 
  /usr/src/sbin/atacontrol/sh.core
 
  Core was generated by `sh'.
  Program terminated with signal 11, Segmentation fault.
  Reading symbols from /lib/libedit.so.6...done.
  Loaded symbols for /lib/libedit.so.6
  Reading symbols from /lib/libncurses.so.7...done.
  Loaded symbols for /lib/libncurses.so.7
  Reading symbols from /lib/libc.so.7...done.
  Loaded symbols for /lib/libc.so.7
  Reading symbols from /libexec/ld-elf.so.1...done.
  Loaded symbols for /libexec/ld-elf.so.1
  #0  0x080555e6 in forkshell (jp=0x2830c0c0, n=0x28304d94, mode=0) at 
  /usr/src/bin/sh/jobs.c:746
  746 pid = fork();
  (gdb) bt
  #0  0x080555e6 in forkshell (jp=0x2830c0c0, n=0x28304d94, mode=0) at 
  /usr/src/bin/sh/jobs.c:746
  #1  0x0804d759 in evalcommand (cmd=0x28304d94, flags=0, backcmd=0x0) at 
  /usr/src/bin/sh/eval.c:747
  #2  0x0804e725 in evaltree (n=0x28304d94, flags=0) at 
  /usr/src/bin/sh/eval.c:267
  #3  0x0804e4ff in evaltree (n=0x28304da4, flags=0) at 
  /usr/src/bin/sh/eval.c:238
  #4  0x0804e86c in evaltree (n=0x28304210, flags=0) at 
  /usr/src/bin/sh/eval.c:341
  #5  0x0804eba7 in evalstring (
 s=0xbf7fea84 for entry in adjkerntz  atacontrol  atm  badsect  bsdlabel 
   camcontrol  ccdconfig  clri  comcontrol  conscontrol  ddb  devd  devfs  
  dhclient  dmesg  dump  dumpfs  dumpon  fdiskffsinfo  fsck   fsck_...) 
  at /usr/src/bin/sh/eval.c:169
  #6  0x08056d98 in main (argc=3, argv=0xbf7fe9a8) at 
  /usr/src/bin/sh/main.c:181
 
 
 
 
  /usr/obj/usr/src/libexec/ftpd/make.core
 
  Program terminated with signal 11, Segmentation fault.
  #0  0x080898bf in memset ()
  (gdb) bt
  #0  0x080898bf in memset ()
  #1  0x000c in ?? ()
  #2  0x0806f8b2 in arena_malloc ()
  #3  0x0807106b in malloc ()
  #4  0x0805a2d1 in emalloc (len=256) at /usr/src/usr.bin/make/util.c:234
  #5  0x08049d3f in Buf_Init (size=0) at /usr/src/usr.bin/make/buf.c:184
  #6  0x0805a63a in VarCreate (name=0x2810d118 .CURDIR, value=0xbf7fe0b6 
  /usr/src/libexec/ftpd, flags=0) at /usr/src/usr.bin/make/var.c:214
  #7  0x0805a68d in VarAdd (name=0x2810d118 

8-CURRENT does not build without WITNESS activated

2009-02-03 Thread Mister Olli
Hi.

I'm currently unable to build the 8-CURRENT kernel in a PV domU, without
options WITNESS in my kernel config.

The output is the following:
==
make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES |  MKDEP_CPP=cc -E
CC=cc xargs mkdep -a -f .newdep -O -pipe  -std=c99 -g -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef
-Wno-pointer-sign -fformat-extensions -nostdinc  -I. -I/usr/src/sys
-I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter
-I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath
-I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm
-I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD
-I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs
-I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb
-D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000  -mno-align-long-strings
-mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mno-sse2
-mno-sse3 -ffreestanding -fstack-protector
In file included from /usr/src/sys/dev/xen/netfront/netfront.c:32:
/usr/src/sys/sys/sx.h:210:2: error: #error LOCK_DEBUG not defined,
include sys/lock.h before sys/sx.h
mkdep: compile failed
*** Error code 1

Stop in /usr/obj/usr/src/sys/XEN.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
template_8-CURRENT# 
==

--
Mr. Olli




___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org


Re: sysctl machdep.independent_wallclock

2009-01-15 Thread Mister Olli
hi...


 what is the exact function of this sysctl setting?
 
 I'm guessing it's something to do with Xen, having seen a few
 references in Linux for xen.machdep.independent_wallclock. 
 
 Have a look here:
 http://docs.xensource.com/XenServer/4.0.1/guest/ch04s06.html

yeah, I know that sysctl from linux, but I wasn't quite sure if it is
the same in FreeBSD, since it's known as 'xen.independent_wallclock' in
linux and 'machdep.independent_wallclock' in FreeBSD.

I started reading the C-code of FreeBSD, and from my understanding the
function 'should' be the same, as it's really linked to the clock
handling with XEN in FreeBSD.

but from my understanding it's not completly implemented in 8-CURRENT
(as of 15 jan 2009; see the last lines):

/*
 * Write system time back to RTC.  
 */
static void
domu_resettodr(void)
{
unsigned long tm;
int s;
dom0_op_t op;
struct shadow_time_info *shadow;

shadow = per_cpu(shadow_time, smp_processor_id());
if (xen_disable_rtc_set)
return;

s = splclock();
tm = time_second;
splx(s);

tm -= tz_minuteswest * 60 + (wall_cmos_clock ? adjkerntz : 0);

if ((xen_start_info-flags  SIF_INITDOMAIN) 
!independent_wallclock)
{
op.cmd = DOM0_SETTIME;
op.u.settime.secs= tm;
op.u.settime.nsecs   = 0;
op.u.settime.system_time = shadow-system_timestamp;
HYPERVISOR_dom0_op(op);
update_wallclock();
} else if (independent_wallclock) {
/* notyet */
;
}   
}

is that correct???

greetz
olli
 

___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org