From owner-freebsd-xen@FreeBSD.ORG Mon Jan 14 06:43:21 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 0118CA13 for ; Mon, 14 Jan 2013 06:43:20 +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 AF5EB6C3 for ; Mon, 14 Jan 2013 06:43:20 +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=DC3it0tjwNdV+ObcOriqTYM2ou/GgxpDiEVHSi2S6oE=; b=ndn8OZRbFeKkBGWiL1/alLisTjyykoRcoDSzxe1ZC1kTKgYpRplEkrjmdAL6Xn34cw18xYvHatq2YzHFJ8MKDPWphHE5UpdJx+48nIvPMc7ogKqobxJXJmmiqHSdUn08sMA0bayXd9ZNbb+WVmDIeX26wFhg3+pfKmhvRL6Dwdk=; 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 1TudlG-0003lo-NK; Mon, 14 Jan 2013 06:43:17 +0000 X-Spam-Status: No, score=-4.2 required=2.0 tests=ALL_TRUSTED, AWL, BAYES_00, DKIM_POLICY_SIGNALL, TW_TX 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 1TudlB-0006n8-2J; Mon, 14 Jan 2013 06:43:10 +0000 Message-ID: <50F3A8F8.7050809@pyro.eu.org> Date: Mon, 14 Jan 2013 06:43:04 +0000 From: Steven Chamberlain User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 To: Egoitz Aurrekoetxea Aurre Subject: Re: Fwd: xenbusb_nop_confighook_cb timeout and cd issue References: <4AD92DFA-7153-4E79-B906-1CBEAAC6B6A3@sarenet.es> In-Reply-To: X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" , Christoph Egger 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: Mon, 14 Jan 2013 06:43:21 -0000 Hi, > kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb It is not really a FreeBSD bug but some regression in Xen 4.1.3. It only affects FreeBSD kernels if built with the XENHVM option. On 06/12/12 11:04, Egoitz Aurrekoetxea Aurre wrote: > The patch of the URL is : http://postfixquotareject.ramattack.net/xen-x86-interrupt-pointer-missmatch.diff Thank you! I just tested it on a NetBSD-6 Xen dom0 and it does indeed fix this (I started seeing this problem after an upgrade to pkgsrc-2012Q4; Christoph: would you be interested in this patch?) The patch originally comes from: http://patch-tracker.debian.org/patch/series/view/xen/4.1.3-7/xen-x86-interrupt-pointer-missmatch.diff A lot of Debian-FreeBSD-NetBSD collaboration seems to be happening here :) Regards, -- Steven Chamberlain steven@pyro.eu.org From owner-freebsd-xen@FreeBSD.ORG Mon Jan 14 11:06:58 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 7668D61F for ; Mon, 14 Jan 2013 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 4B54C66C for ; Mon, 14 Jan 2013 11:06:58 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r0EB6wkv086614 for ; Mon, 14 Jan 2013 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0EB6vcY086612 for freebsd-xen@FreeBSD.org; Mon, 14 Jan 2013 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Jan 2013 11:06:57 GMT Message-Id: <201301141106.r0EB6vcY086612@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Subject: Current problem reports assigned to freebsd-xen@FreeBSD.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: Mon, 14 Jan 2013 11:06:58 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/171873 xen [xen] xn network device floods warning in dmesg o kern/171138 xen [xen] [panic] Deactivating network interface produces o kern/171118 xen [xen] FreeBSD XENHVM guest doesn't shutdown cleanly o kern/166174 xen [xen] Problems ROOT MOUNT ERROR o kern/165418 xen [xen] Problems mounting root filesystem from XENHVM o kern/164630 xen [xen] XEN HVM kernel: run_interrupt_driven_hooks: stil o kern/164450 xen [xen] Failed to install FreeeBSD 9.0-RELEASE from CD i o kern/162677 xen [xen] FreeBSD not compatible with "Current Stable Xen" o kern/161318 xen [xen] sysinstall crashes with floating point exception o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 31 problems total. From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 07:36:12 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 5D883D47 for ; Thu, 17 Jan 2013 07:36:12 +0000 (UTC) (envelope-from christoph_egger@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by mx1.freebsd.org (Postfix) with ESMTP id CA14D9E3 for ; Thu, 17 Jan 2013 07:36:11 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.16]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MUiOI-1TS5e23SsG-00Y6B5 for ; Thu, 17 Jan 2013 08:36:10 +0100 Received: (qmail invoked by alias); 17 Jan 2013 07:36:10 -0000 Received: from dslb-088-074-135-071.pools.arcor-ip.net (EHLO [10.1.0.3]) [88.74.135.71] by mail.gmx.net (mp016) with SMTP; 17 Jan 2013 08:36:10 +0100 X-Authenticated: #6616588 X-Provags-ID: V01U2FsdGVkX18p7k5DUSIpvhtg8s4m823vfkFOEXuV4OQCi/QpOM tSTy2GarTeoY7+ Message-ID: <50F7A9E8.4030007@gmx.de> Date: Thu, 17 Jan 2013 08:36:08 +0100 From: Christoph Egger User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.28) Gecko/20120306 Lightning/1.0b2 Thunderbird/3.1.20 MIME-Version: 1.0 To: Steven Chamberlain , "xen-devel@lists.xen.org" Subject: Re: Fwd: xenbusb_nop_confighook_cb timeout and cd issue References: <4AD92DFA-7153-4E79-B906-1CBEAAC6B6A3@sarenet.es> <50F3A8F8.7050809@pyro.eu.org> In-Reply-To: <50F3A8F8.7050809@pyro.eu.org> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: "freebsd-xen@freebsd.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 07:36:12 -0000 On 14.01.13 07:43, Steven Chamberlain wrote: > Hi, > >> kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb > > > It is not really a FreeBSD bug but some regression in Xen 4.1.3. It > only affects FreeBSD kernels if built with the XENHVM option. > > On 06/12/12 11:04, Egoitz Aurrekoetxea Aurre wrote: >> The patch of the URL is : http://postfixquotareject.ramattack.net/xen-x86-interrupt-pointer-missmatch.diff > > Thank you! I just tested it on a NetBSD-6 Xen dom0 and it does indeed > fix this (I started seeing this problem after an upgrade to > pkgsrc-2012Q4; Christoph: would you be interested in this patch?) > > The patch originally comes from: > http://patch-tracker.debian.org/patch/series/view/xen/4.1.3-7/xen-x86-interrupt-pointer-missmatch.diff > > A lot of Debian-FreeBSD-NetBSD collaboration seems to be happening here :) > > Regards, Thanks for this patch. I am adding xen-devel for upstream. Christoph From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 11:19:26 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 065766BC for ; Thu, 17 Jan 2013 11:19:26 +0000 (UTC) (envelope-from Andrew.Cooper3@citrix.com) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) by mx1.freebsd.org (Postfix) with ESMTP id 8828B3E5 for ; Thu, 17 Jan 2013 11:19:25 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,484,1355097600"; d="scan'208";a="3852332" Received: from ftlpex01cl01.citrite.net ([10.13.107.78]) by FTLPIPO02.CITRIX.COM with ESMTP/TLS/AES128-SHA; 17 Jan 2013 11:19:23 +0000 Received: from ukmail1.uk.xensource.com (10.80.16.128) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.318.1; Thu, 17 Jan 2013 06:19:23 -0500 Received: from andrewcoop.uk.xensource.com ([10.80.2.18]) by ukmail1.uk.xensource.com with esmtp (Exim 4.69) (envelope-from ) id 1TvnVD-000855-87; Thu, 17 Jan 2013 11:19:23 +0000 Message-ID: <50F7DE3A.7080102@citrix.com> Date: Thu, 17 Jan 2013 11:19:22 +0000 From: Andrew Cooper User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121127 Icedove/10.0.11 MIME-Version: 1.0 To: Christoph Egger Subject: Re: [Xen-devel] 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 Content-Type: text/plain; charset="ISO-8859-1" 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:19:26 -0000 On 17/01/13 07:36, Christoph Egger wrote: > On 14.01.13 07:43, Steven Chamberlain wrote: > >> Hi, >> >>> kernel: run_interrupt_driven_hooks: still waiting after 60 seconds for xenbusb_nop_confighook_cb >> >> >> It is not really a FreeBSD bug but some regression in Xen 4.1.3. It >> only affects FreeBSD kernels if built with the XENHVM option. >> >> On 06/12/12 11:04, Egoitz Aurrekoetxea Aurre wrote: >>> The patch of the URL is : http://postfixquotareject.ramattack.net/xen-x86-interrupt-pointer-missmatch.diff >> Thank you! I just tested it on a NetBSD-6 Xen dom0 and it does indeed >> fix this (I started seeing this problem after an upgrade to >> pkgsrc-2012Q4; Christoph: would you be interested in this patch?) >> The patch originally comes from: >> http://patch-tracker.debian.org/patch/series/view/xen/4.1.3-7/xen-x86-interrupt-pointer-missmatch.diff >> >> A lot of Debian-FreeBSD-NetBSD collaboration seems to be happening here :) >> >> Regards, > > Thanks for this patch. > I am adding xen-devel for upstream. > > Christoph config.h defines asmlinkage as nothing. So I am really struggling to find how this code will alter the code in Xen at all once the preprocessor has been completed. ~Andrew > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel 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 From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 14:36:07 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D2690736 for ; Thu, 17 Jan 2013 14:36:07 +0000 (UTC) (envelope-from christoph_egger@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by mx1.freebsd.org (Postfix) with ESMTP id 65BED2A5 for ; Thu, 17 Jan 2013 14:36:07 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.1]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Laq3S-1TBoWU1R16-00kQJB for ; Thu, 17 Jan 2013 15:36:06 +0100 Received: (qmail invoked by alias); 17 Jan 2013 14:36:06 -0000 Received: from 87-238-84-64.amazon.com (EHLO [10.50.170.238]) [87.238.84.64] by mail.gmx.net (mp001) with SMTP; 17 Jan 2013 15:36:06 +0100 X-Authenticated: #6616588 X-Provags-ID: V01U2FsdGVkX19ywT1erQhyFUokmHgZBop9ixvxJGn826tcbD/lSD xx5Hn2qCa80mKV Message-ID: <50F80C4C.7040905@gmx.de> Date: Thu, 17 Jan 2013 15:35:56 +0100 From: Christoph Egger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Steven Chamberlain 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> <50F7DE55.8060101@pyro.eu.org> In-Reply-To: <50F7DE55.8060101@pyro.eu.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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 14:36:07 -0000 Am 17.01.2013 12:19, schrieb Steven Chamberlain: > 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, > I compiled a clean checked out xen-4.1-testing.hg with and without the patch. I created a objdump -S -D from each xen-syms. A diff -u between both objdump's shows this: --- xen-syms-unpatched.objdump 2013-01-17 12:47:25.000000000 +0000 +++ xen-syms-patched.objdump 2013-01-17 12:52:26.000000000 +0000 @@ -1,5 +1,5 @@ -xen-syms-unpatched: file format elf64-x86-64 +xen-syms-patched: file format elf64-x86-64 Disassembly of section .text: @@ -435776,16 +435776,20 @@ ffff82c480215a03: 20 31 ffff82c480215a05: 37 (bad) ffff82c480215a06: 20 31 and %dh,(%rcx) ffff82c480215a08: 32 3a xor (%rdx),%bh -ffff82c480215a0a: 33 33 xor (%rbx),%esi -ffff82c480215a0c: 3a 33 cmp (%rbx),%dh -ffff82c480215a0e: 35 20 55 54 43 xor $0x43545520,%eax -ffff82c480215a13: 20 32 and %dh,(%rdx) +ffff82c480215a0a: 33 30 xor (%rax),%esi +ffff82c480215a0c: 3a 30 cmp (%rax),%dh +ffff82c480215a0e: 39 20 cmp %esp,(%rax) +ffff82c480215a10: 55 push %rbp +ffff82c480215a11: 54 push %rsp +ffff82c480215a12: 43 20 32 rexYZ and %sil,(%r10) ffff82c480215a15: 30 31 xor %dh,(%rcx) ffff82c480215a17: 33 00 xor (%rax),%eax ffff82c480215a19: 31 32 xor %esi,(%rdx) ffff82c480215a1b: 3a 33 cmp (%rbx),%dh -ffff82c480215a1d: 33 3a xor (%rdx),%edi -ffff82c480215a1f: 33 35 00 63 68 65 xor 1701339904(%rip),%esi # ffff82c4e589bd25 <_end+0x655de725> +ffff82c480215a1d: 30 3a xor %bh,(%rdx) +ffff82c480215a1f: 30 39 xor %bh,(%rcx) +ffff82c480215a21: 00 63 68 add %ah,0x68(%rbx) +ffff82c480215a24: 65 gs ffff82c480215a25: 67 addr32 ffff82c480215a26: 67 addr32 ffff82c480215a27: 65 gs The fact that this patch causes gcc (4.1.3 on a redhat box in my case) to generate different assembly code makes me think that there is something wrong with gcc. The fact that FreeBSD hangs even when Xen is compiled with gcc 4.6 tells me that also gcc 4.6 is affected. It is interesting to know that doing things semantically correct works around it. So I would take build fixes for gcc 4.7 more serious than just a "build fixes". I think this should be shown to gcc dev folk to have a look into this. In xen-unstable Jan Beulich moved the interrupt array into the .init.data section. I would like to know if FreeBSD 9.1 hangs or boots fine with xen-unstable. Christoph From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 14:51:36 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 BC0C4BBD for ; Thu, 17 Jan 2013 14:51:36 +0000 (UTC) (envelope-from juergen.gross@ts.fujitsu.com) Received: from dgate20.ts.fujitsu.com (dgate20.ts.fujitsu.com [80.70.172.51]) by mx1.freebsd.org (Postfix) with ESMTP id F300D364 for ; Thu, 17 Jan 2013 14:51:35 +0000 (UTC) DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=sIwBrv5qi1ugo36GXE4Et+TaOm7hvOU+7XJ5LUjmUyoEsrf9NG1LRqvo QH0Zf4kb59nQqQk2ovGoRXSOXHRaWbMck39Wwd1vpMlKQCkN5v41Mbbe6 YANWvb90lDIX0vs1vYIFar0t3SMMAmkQGkswNng196HkItwm8ouvcADsE XlQjywfWo1jlsvEJerLDyvHTetFkdtvhbEmYtSGBpewcBQhkcL+xDuvrW dd7Uudvh1v43Lk9ZGA+BMaVVFPWGp; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1358434296; x=1389970296; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Ke9lifzbZfwg5qIVsENHnEjSDWyDMJ2HRmm6k1a2I+E=; b=rC3kJ6TLz3Rq5vB3qflE5LEFWm05DjAzKib4/jtI+Q17R7EXiu7NqHRJ mbLOH/TtGiQhmJ1jzWCIAlK0dNgHHTpbVj+W/OxwdLcl90XRI0SgtCABP /Q2FKPjbMQMTPuX8RA6QSMDNd0NAxjTVm1M5zTw/uBbqpks7920fdlSDZ EheKQ0HwizewC35rNUQqFswndQ924YceRTBp5hEUwGeNdD6FzE3Q8A3jm brASPYn6+VfdggVk23naXf85ey2O5; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,486,1355094000"; d="scan'208";a="113643924" Received: from abgdgate30u.abg.fsc.net ([172.25.138.66]) by dgate20u.abg.fsc.net with ESMTP; 17 Jan 2013 15:50:26 +0100 X-IronPort-AV: E=Sophos;i="4.84,486,1355094000"; d="scan'208";a="155880080" Received: from sanpedro.mch.fsc.net ([172.17.20.6]) by abgdgate30u.abg.fsc.net with SMTP; 17 Jan 2013 15:50:26 +0100 Received: from [172.17.21.50] (verdon.osd.mch.fsc.net [172.17.21.50]) by sanpedro.mch.fsc.net (Postfix) with ESMTP id 5225096114A; Thu, 17 Jan 2013 15:50:26 +0100 (CET) Message-ID: <50F80FB2.4060908@ts.fujitsu.com> Date: Thu, 17 Jan 2013 15:50:26 +0100 From: Juergen Gross Organization: Fujitsu Technology Solutions GmbH User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11 MIME-Version: 1.0 To: Christoph Egger Subject: Re: [Xen-devel] 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> <50F7DE55.8060101@pyro.eu.org> <50F80C4C.7040905@gmx.de> In-Reply-To: <50F80C4C.7040905@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 14:51:36 -0000 Am 17.01.2013 15:35, schrieb Christoph Egger: > Am 17.01.2013 12:19, schrieb Steven Chamberlain: >> 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, >> > > I compiled a clean checked out xen-4.1-testing.hg with and without the patch. > > I created a objdump -S -D from each xen-syms. > A diff -u between both objdump's shows this: > > --- xen-syms-unpatched.objdump 2013-01-17 12:47:25.000000000 +0000 > +++ xen-syms-patched.objdump 2013-01-17 12:52:26.000000000 +0000 > @@ -1,5 +1,5 @@ > > -xen-syms-unpatched: file format elf64-x86-64 > +xen-syms-patched: file format elf64-x86-64 > > Disassembly of section .text: > > @@ -435776,16 +435776,20 @@ ffff82c480215a03: 20 31 > ffff82c480215a05: 37 (bad) > ffff82c480215a06: 20 31 and %dh,(%rcx) > ffff82c480215a08: 32 3a xor (%rdx),%bh > -ffff82c480215a0a: 33 33 xor (%rbx),%esi > -ffff82c480215a0c: 3a 33 cmp (%rbx),%dh > -ffff82c480215a0e: 35 20 55 54 43 xor $0x43545520,%eax > -ffff82c480215a13: 20 32 and %dh,(%rdx) > +ffff82c480215a0a: 33 30 xor (%rax),%esi > +ffff82c480215a0c: 3a 30 cmp (%rax),%dh > +ffff82c480215a0e: 39 20 cmp %esp,(%rax) > +ffff82c480215a10: 55 push %rbp > +ffff82c480215a11: 54 push %rsp > +ffff82c480215a12: 43 20 32 rexYZ and %sil,(%r10) > ffff82c480215a15: 30 31 xor %dh,(%rcx) > ffff82c480215a17: 33 00 xor (%rax),%eax > ffff82c480215a19: 31 32 xor %esi,(%rdx) > ffff82c480215a1b: 3a 33 cmp (%rbx),%dh > -ffff82c480215a1d: 33 3a xor (%rdx),%edi > -ffff82c480215a1f: 33 35 00 63 68 65 xor 1701339904(%rip),%esi # ffff82c4e589bd25<_end+0x655de725> > +ffff82c480215a1d: 30 3a xor %bh,(%rdx) > +ffff82c480215a1f: 30 39 xor %bh,(%rcx) > +ffff82c480215a21: 00 63 68 add %ah,0x68(%rbx) > +ffff82c480215a24: 65 gs > ffff82c480215a25: 67 addr32 > ffff82c480215a26: 67 addr32 > ffff82c480215a27: 65 gs Are you sure? This looks like different ASCII texts to me: -"12:33:35 UTC 2013" -"12:33:35" +"12:30:39 UTC 2013" +"12:30:39" "chegge..." Seems to be related to the time the file was generated. Juergen -- Juergen Gross Principal Developer Operating Systems PBG PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967 Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com Domagkstr. 28 Internet: ts.fujitsu.com D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 14:54:05 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AF82CC2D for ; Thu, 17 Jan 2013 14:54:05 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7C5F7385 for ; Thu, 17 Jan 2013 14:54:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:Cc:To:Content-Type; bh=wNlviAumABl5ysNFK9Jww10EjqMWxi8S4qkIp3I9MNM=; b=ceIOw+U7bae/TnTDuFMHPC0BMcGrktF7doacUSblzeRkXLNvmGbrE3OEL9ROJfUv/+xAM8V/s4EbgOV/eGh0ibLz92dfEFF3S5fBaH3gVI/yDL3HHIb7cqCNg7UHmD++; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Tvqqk-0008yd-8i; Thu, 17 Jan 2013 08:53:50 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1358434424-86880-86877/5/3; Thu, 17 Jan 2013 14:53:44 +0000 Content-Type: text/plain; format=flowed; delsp=yes To: Christoph Egger , Steven Chamberlain 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> <50F7DE55.8060101@pyro.eu.org> Date: Thu, 17 Jan 2013 08:53:44 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <50F7DE55.8060101@pyro.eu.org> User-Agent: Opera Mail/12.12 (FreeBSD) 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 14:54:05 -0000 Citrix has an open internal bug for this because of my incessant nagging. I'm going to direct them to this patch. If I can get their build manager to spin up a copy of XCP 1.6 with this patch included I'll make sure I get the ISO linked onto this mailing list. From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 15:04:56 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 79256C5 for ; Thu, 17 Jan 2013 15:04:56 +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 2FB6C661 for ; Thu, 17 Jan 2013 15:04:55 +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=AtgFi+Rud38qGzWDKUZG6S2Y947ryxRdm2DiNr4ZrF0=; b=PnittvD3qO4lO/AyTiBLtQIvsElSG94T2Is1tjKWmO6SwVrY5q6IhAUqjb1/ZddUQOf1qFOFoEactwJykp8idvxqSYdFPgMe1+MoYT4/UqN0U6JWOdG2UJIw8xjvsaTOZctrJUIkfrmm5QaczNIU4EpnDUREW8VhAQkpHPzSgGg=; 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 1Tvr1G-0003Q7-Fj; Thu, 17 Jan 2013 15:04:47 +0000 X-Spam-Status: No, score=-4.4 required=2.0 tests=ALL_TRUSTED, AWL, BAYES_00, DKIM_POLICY_SIGNALL, TW_GF 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 1Tvr1B-0003Sr-90; Thu, 17 Jan 2013 15:04:41 +0000 Message-ID: <50F81304.4020701@pyro.eu.org> Date: Thu, 17 Jan 2013 15:04:36 +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: Mark Felder 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> <50F7DE55.8060101@pyro.eu.org> In-Reply-To: X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org, Christoph Egger , 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 15:04:56 -0000 On 17/01/13 14:53, Mark Felder wrote: > Citrix has an open internal bug for this because of my incessant > nagging. I'm going to direct them to this patch. I'm afraid the patch can't be what really fixed this. Andrew Cooper is right that the pre-processed output is identical (except for a space), and so are all the object files except for version.o My gcc 4.5 builds on NetBSD; and gcc 4.7 on Debian Wheezy; seem to be the same with/without the patch. Maybe it was something as trivial as the reboot that made it go away? I notice now that gcc 4.7 was updated on Debian buildds, so a compiler bugfix may be what really fixed the issue there. My NetBSD pkgsrc build still differs from the distributed binary package in a strange way, when the chroot build environments should be the same. (This is a diff of 'strings') --- netbsd-binary/xen41-kernel/xen.s 2013-01-17 13:45:08.000000000 +0000 +++ netbsd-local-unpatched/xen41-kernel/xen.s 2013-01-17 13:45:13.000000000 +0000 @@ -9641,10 +9636,10 @@ hadow_ pars allo -page_ ched_ ister compa +page_ entr .clone. clone. @@ -12250,7 +12245,6 @@ PoD entries=%d cachesize=%d %s: Out of populate-on-demand memory! tot_pages %u pod_entries %i pg error: %s(): p2m already allocated for this domain -%s: gfn_to_mfn returned type %d! <1>%s:%d:d%d Adding bad mfn to p2m map (%#lx -> %#lx) <0>%s:%d:d%d set_mmio_p2m_entry: set_p2m_entry failed! mfn=%08lx <0>%s:%d:d%d clear_mmio_p2m_entry: gfn_to_mfn failed! gfn=%08lx Regards, -- Steven Chamberlain steven@pyro.eu.org From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 15:08:04 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 52962224 for ; Thu, 17 Jan 2013 15:08:04 +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 083B06AC for ; Thu, 17 Jan 2013 15:08:04 +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=jmRyHCcFZXaJRutvXGJ0jeaTmIetqu8eGUQwO7rVNE8=; b=LBA+sY4sIxwgmJo1rEF9Jfy51vv+qWTZtsrkyQOOHq1BSBg2ak0KXMBMa095Z0+q5WL7PVLmmmNQyPtq2hIKhGXzXuzVJYKMGZ6fG+Zjt7HgF2Lx7mcqKUxq/tXv2hpPXJFVmgpP/OEyhFw6aIS84JZEiO6azzEuvWwRo/Oud0M=; 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 1Tvr4R-0003Qv-VN; Thu, 17 Jan 2013 15:08:01 +0000 X-Spam-Status: No, score=-4.4 required=2.0 tests=ALL_TRUSTED, AWL, 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 1Tvr4N-0003b6-HD; Thu, 17 Jan 2013 15:07:59 +0000 Message-ID: <50F813CB.7050801@pyro.eu.org> Date: Thu, 17 Jan 2013 15:07:55 +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: Mark Felder 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> <50F7DE55.8060101@pyro.eu.org> In-Reply-To: X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org, Christoph Egger , 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 15:08:04 -0000 On 17/01/13 14:53, Mark Felder wrote: > Citrix has an open internal bug for this because of my incessant > nagging. Actually - Mark I'm sure you've tried many reboots and are still able to reproduce it? So this must be something to do with the build Xen kernel image after all. Regards, -- Steven Chamberlain steven@pyro.eu.org From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 15:55:10 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4C5B553C for ; Thu, 17 Jan 2013 15:55:10 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 2021A9D1 for ; Thu, 17 Jan 2013 15:55:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=Message-Id:Cc:To:Date:From:Subject:Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To; bh=60perT5OEGV5ih9FUACP0i5htvQph6t9USekBzRRj0Q=; b=P2H5v77wanK5HdxDyxMcLeobvIZyc5VR94QWSwDLxqHbBw7SdQM9dhYCoR/ShqrjhRfL9yXw5nAoCFG/joBB1WtCD8+xrrri2X1j0SQzrPJbjRaw98B3BuukpMq03HeB; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Tvrnx-000OUk-HL; Thu, 17 Jan 2013 09:55:01 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1358438095-89422-89420/5/1; Thu, 17 Jan 2013 15:54:55 +0000 User-Agent: K-9 Mail for Android In-Reply-To: <50F813CB.7050801@pyro.eu.org> References: <4AD92DFA-7153-4E79-B906-1CBEAAC6B6A3@sarenet.es> <50F3A8F8.7050809@pyro.eu.org> <50F7A9E8.4030007@gmx.de> <50F7DE55.8060101@pyro.eu.org> <50F813CB.7050801@pyro.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Fwd: xenbusb_nop_confighook_cb timeout and cd issue From: Mark Felder Date: Thu, 17 Jan 2013 09:24:09 -0600 To: Steven Chamberlain Message-Id: <7ba7ddf7-3034-4422-8eed-5299318454a9@email.android.com> Cc: freebsd-xen@freebsd.org, Christoph Egger , 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 15:55:10 -0000 I no longer have that environment that I was using to test the viability = of upgrading to XCP 1.6 but it was reproducible every boot. From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 15:56:44 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 92E1F582 for ; Thu, 17 Jan 2013 15:56:44 +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 4A36E9E6 for ; Thu, 17 Jan 2013 15:56:44 +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=+HWIp7WQ0kIPLmb7YFN2q1goMVWMENKjwrcf4iZpvuQ=; b=if2IggWoBlV6rZP0Vr4jwqCQeHcLHxBEp7wqe6BEClC3nIEyWfM43hMg8XlZIbH7arPsYdn3FeVv6HhOjvuLKKpov9g+0Krj8kb9Usi/mdcLzCioMY6Rk3KlVoEo3uwT6TDxfHtWIbKIqHFOOjDGsc+MWaYXfryQ1pDEa0sxfGw=; 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 1TvrpW-0003Wr-6S; Thu, 17 Jan 2013 15:56:41 +0000 X-Spam-Status: No, score=-4.4 required=2.0 tests=ALL_TRUSTED, AWL, 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 1TvrpR-0006ZL-QW; Thu, 17 Jan 2013 15:56:37 +0000 Message-ID: <50F81F31.3070103@pyro.eu.org> Date: Thu, 17 Jan 2013 15:56:33 +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: Mark Felder 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> <50F7DE55.8060101@pyro.eu.org> <50F813CB.7050801@pyro.eu.org> <7ba7ddf7-3034-4422-8eed-5299318454a9@email.android.com> In-Reply-To: <7ba7ddf7-3034-4422-8eed-5299318454a9@email.android.com> X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org, Christoph Egger , 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 15:56:44 -0000 On 17/01/13 15:24, Mark Felder wrote: > I no longer have that environment that I was using to test the viability of upgrading to XCP 1.6 but it was reproducible every boot. Just to clarify - you rebooted the dom0/hypervisor also? I know the bug is reproducible on every FreeBSD domU boot, at least. Regards, -- Steven Chamberlain steven@pyro.eu.org From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 17:50:17 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 29E75E87 for ; Thu, 17 Jan 2013 17:50:17 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id E9EDD6B9 for ; Thu, 17 Jan 2013 17:50:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:Cc:To:Content-Type; bh=w1ky7fYtUhkkuPAaER3GybzKnHc9O+J0KBIN1e1L8SQ=; b=kgzUeO4/kYLdJgwCmfedN3V/mcjKrAjNqnYZqvUxXyV7MUQQNPCtaKq7MnT9VFUGksvZ8S+k6Op9rZYfE5d65b3y3bH54jEEM2IXS5D/PmZjZNqNj6y7QeLxOjL0otQG; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1TvtbM-000462-6U; Thu, 17 Jan 2013 11:50:08 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1358445001-14285-89420/5/1; Thu, 17 Jan 2013 17:50:01 +0000 Content-Type: text/plain; format=flowed; delsp=yes To: Steven Chamberlain , 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> <50F7DE55.8060101@pyro.eu.org> <50F80C4C.7040905@gmx.de> Date: Thu, 17 Jan 2013 11:50:01 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <50F80C4C.7040905@gmx.de> User-Agent: Opera Mail/12.12 (FreeBSD) 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 17:50:17 -0000 For anyone running XCP 1.6 please try to use these RPMs which are patched. I'll be trying this myself later today. http://downloads.xen.org/XCP/freebsd-xen-fix/ Cheers! From owner-freebsd-xen@FreeBSD.ORG Thu Jan 17 18:53:52 2013 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6041E48A for ; Thu, 17 Jan 2013 18:53:52 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 39A50A50 for ; Thu, 17 Jan 2013 18:53:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:Cc:To:Content-Type; bh=KiUs1fbi6eX6CgofXapMCW/sy3SWcPa2NEIoQB6iymY=; b=bBFrFiypQfFHnCYOiuTriHSxpS/okg5qntr6wWZh6VzuuciFul3lg1GZlzcSvUxN6bahuz2b+7l4tXUcIohXC0eS5gcnX345x2glxUe9UhTFuL8Gyo8G2Tqf70/fY+pt; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1Tvuaz-000663-El; Thu, 17 Jan 2013 12:53:49 -0600 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpsa id 1358448823-14285-89420/5/2; Thu, 17 Jan 2013 18:53:43 +0000 Content-Type: text/plain; format=flowed; delsp=yes To: Steven Chamberlain Subject: Re: [Xen-devel] 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> <50F7DE55.8060101@pyro.eu.org> <50F813CB.7050801@pyro.eu.org> <7ba7ddf7-3034-4422-8eed-5299318454a9@email.android.com> <50F81F31.3070103@pyro.eu.org> Date: Thu, 17 Jan 2013 12:53:43 -0600 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <50F81F31.3070103@pyro.eu.org> User-Agent: Opera Mail/12.12 (FreeBSD) Cc: freebsd-xen@freebsd.org, Christoph Egger , 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 18:53:52 -0000 On Thu, 17 Jan 2013 09:56:33 -0600, Steven Chamberlain wrote: > On 17/01/13 15:24, Mark Felder wrote: >> I no longer have that environment that I was using to test the >> viability of upgrading to XCP 1.6 but it was reproducible every boot. > > Just to clarify - you rebooted the dom0/hypervisor also? > > I know the bug is reproducible on every FreeBSD domU boot, at least. > We did reboot the dom0 more than once but I didn't test that specifically to see if the problem would subside after a few reboots.