From owner-freebsd-xen@FreeBSD.ORG Tue Apr 14 09:51:19 2015 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A351D350 for ; Tue, 14 Apr 2015 09:51:19 +0000 (UTC) Received: from SMTP02.CITRIX.COM (smtp02.citrix.com [66.165.176.63]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "Cybertrust Public SureServer SV CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 57F355EF for ; Tue, 14 Apr 2015 09:51:18 +0000 (UTC) X-IronPort-AV: E=Sophos;i="5.11,575,1422921600"; d="scan'208";a="254808070" Message-ID: <552CE313.2070706@citrix.com> Date: Tue, 14 Apr 2015 11:51:15 +0200 From: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= CC: FreeBSD XEN Subject: Re: Fwd: Re: Unable to boot with the dom0 xen kernel References: <5523D56B.9040706@entel.upc.edu> <5523D5A7.5040809@entel.upc.edu> <5523EDBE.70709@FreeBSD.org> <5523FD07.1000707@entel.upc.edu> <5525282D.8060808@citrix.com> <552CC45B.7070503@entel.upc.edu> <552CD188.8070000@citrix.com> <552CDEF6.8070905@entel.upc.edu> In-Reply-To: <552CDEF6.8070905@entel.upc.edu> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-DLP: MIA2 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 14 Apr 2015 09:51:19 -0000 Hello, Re-adding freebsd-xen ;). El 14/04/15 a les 11.33, Gustau Pérez ha escrit: > > > On 14/04/2015 10:36, Roger Pau Monné wrote: >>> >>> Hello, >>> >>> I've tried the IN/OUT patch (I haven't tested the acpi shutdown patch >>> yet) but the problem remains the same. In the serial console I can see >>> different interruption problems (USB_ERR_TIMEOUTS, mpt0, bce0, etc). >> Can you paste the full boot log (including Xen and FreeBSD)? Also, can >> you switch to the Xen console when all those time outs start happening >> and paste the output of the 'i' debug key? >> > > Sure, it is here: > > http://dpaste.com/30VTA0B > > sorry about the mangled parts, it happens when capturing from the > serial console. It is the boot of a patched kernel in verbose mode, at > the end you'll find the interruption information provided by xen itself. Thanks, could you add ioapic_ack=old to your xen_cmdline and try again? I have a similar system (two IO-APICs, Nehalem series), and without this option I also see interrupt timeouts (although mine only happen on heavy load). Roger.