From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 11:20:02 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AFF0B6EA for ; Thu, 17 Jan 2013 11:20:02 +0000 (UTC) (envelope-from steven@pyro.eu.org) Received: from falkenstein-2.sn.de.cluster.ok24.net (falkenstein-2.sn.de.cluster.ok24.net [IPv6:2002:4e2f:2f89:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 531803EE for ; Thu, 17 Jan 2013 11:20:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/simple; d=pyro.eu.org; s=01.2013; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=CzDDwbWNE/xZVYZZgcX57JINTn2f1oFmJLJQWurrVE8=; b=E6T/5XhMSeS+Rjtk66OaY6+6ks+twfaMSmP7n4lZZ19RLMKov30KB3fgLerrsXHqu3eH+QIkDo/o4C2jPtz7GypbLho+6mWyr2LmkXKoH3rJSDTZDlVTAbr945NDZbdNooll2xluKw9Rh9UIr+SAgzYLzAhaHsp5ZWqwcKHvs9E=; X-Spam-Status: No, score=-1.1 required=2.0 tests=ALL_TRUSTED, BAYES_00, DKIM_ADSP_DISCARD, TVD_RCVD_IP Received: from 188-220-33-66.zone11.bethere.co.uk ([188.220.33.66] helo=guisborough-1.rcc.uk.cluster.ok24.net) by falkenstein-2.sn.de.cluster.ok24.net with esmtp (Exim 4.72) (envelope-from ) id 1TvnVj-00031G-3L; Thu, 17 Jan 2013 11:19:58 +0000 X-Spam-Status: No, score=-4.4 required=2.0 tests=ALL_TRUSTED, BAYES_00, DKIM_POLICY_SIGNALL Received: from [192.168.0.110] (helo=[192.168.0.9]) by guisborough-1.rcc.uk.cluster.ok24.net with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1TvnVd-00089z-Uf; Thu, 17 Jan 2013 11:19:54 +0000 Message-ID: <50F7DE55.8060101@pyro.eu.org> Date: Thu, 17 Jan 2013 11:19:49 +0000 From: Steven Chamberlain User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12 MIME-Version: 1.0 To: Christoph Egger Subject: Re: Fwd: xenbusb_nop_confighook_cb timeout and cd issue References: <4AD92DFA-7153-4E79-B906-1CBEAAC6B6A3@sarenet.es> <50F3A8F8.7050809@pyro.eu.org> <50F7A9E8.4030007@gmx.de> In-Reply-To: <50F7A9E8.4030007@gmx.de> X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" , "xen-devel@lists.xen.org" X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 11:20:02 -0000 Hi, A little more background to this: An error was first seen on Debian's i386 autobuilders when building Xen 4.1.2 (Debian package 4.1.2-7), but only after a switch from gcc-4.6 to gcc-4.7 which seems to be what prompted this. I'm not sure if it would have affected amd64 builds as we don't have logs for those: https://buildd.debian.org/status/fetch.php?pkg=xen&arch=i386&ver=4.1.3-7&stamp=1355254810 : > gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -Wno-unused-but-set-variable -DNDEBUG -nostdinc -fno-builtin -fno-common -Wredundant-decls -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/build/buildd-xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1-i386-iqa4wM/xen-4.1.3~rc1+hg-20120614.a9c0a89c08f2/debian/build/build-hypervisor_i386_i386/xen/include -I/build/buildd-xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1-i386-iqa4wM/xen-4.1.3~rc1+hg-20120614.a9c0a89c08f2/debian/build/build-hypervisor_i386_i386/xen/include/asm-x86/mach-generic -I/build/buildd-xen_4.1.3~rc1+hg-20120614.a9c0a89c08f2-1-i386-iqa4wM/xen-4.1.3~rc1+hg-20120614.a9c0a89c08f2/debian/build/build-hypervisor_i386_i386/xen/include/asm-x86/mach-default -msoft-float -fno-stack-protector -fno-exceptions -g -D__XEN__ -MMD -MF .i8259.o.d -c i8259.c -o i8259.o > i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] > i8259.c:66:9: error: (near initialization for 'interrupt[0]') [-Werror] > i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] > i8259.c:66:9: error: (near initialization for 'interrupt[1]') [-Werror] > i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] > i8259.c:66:9: error: (near initialization for 'interrupt[2]') [-Werror] In order to fix the build issue, this patch was written, and is still used when building Debian's Xen 4.1.3 packages: http://patch-tracker.debian.org/patch/series/view/xen/4.1.3-7/xen-x86-interrupt-pointer-missmatch.diff Since October 2012 many FreeBSD (9.x) users reported an issue booting on Xenserver 6.1 / XCP 1.6 (incl. -BETA) but not affecting XCP 1.5: http://lists.freebsd.org/pipermail/freebsd-xen/2012-October/001374.html There were prior reports of identical symptoms triggered by guest CD-ROM drives without media, but this seems to be an unrelated bug. Egoitz, who has done a lot of work porting FreeBSD to XCP recently, found that Debian's (Wheezy) Xen kernel didn't have this bug; realised that the above patch fixes it. I experienced the bug when booting the FreeBSD 9.0 kernel on a NetBSD 6.0.1 dom0 after upgrading to pkgsrc-2012Q4 (Xen 4.1.3, from a binary package, unsure which compiler was used to build it). Likewise the patch fixed the issue for me; I used gcc 4.5.3. Regards, -- Steven Chamberlain steven@pyro.eu.org