From owner-freebsd-xen@FreeBSD.ORG  Tue Apr 14 09:34:22 2015
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
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 0D99ECA
 for <freebsd-xen@freebsd.org>; Tue, 14 Apr 2015 09:34:22 +0000 (UTC)
Received: from violet.upc.es (violet.upc.es [147.83.2.51])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "relay.upc.es", Issuer "TERENA SSL CA" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 6EBFE1CF
 for <freebsd-xen@freebsd.org>; Tue, 14 Apr 2015 09:34:21 +0000 (UTC)
Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244])
 by violet.upc.es (8.14.1/8.13.1) with ESMTP id t3E9YFnR023286
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL);
 Tue, 14 Apr 2015 11:34:15 +0200
Received: from [10.0.2.151] ([147.83.40.10]) (authenticated bits=0)
 by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id t3E9YFp3030777
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
 Tue, 14 Apr 2015 11:34:15 +0200
Message-ID: <552CDF17.109@entel.upc.edu>
Date: Tue, 14 Apr 2015 11:34:15 +0200
From: =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= <gperez@entel.upc.edu>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com>,
 freebsd-xen@freebsd.org
Subject: Fwd: Re: Fwd: Re: Unable to boot with the dom0 xen kernel
References: <552CDEF6.8070905@entel.upc.edu>
In-Reply-To: <552CDEF6.8070905@entel.upc.edu>
X-Forwarded-Message-Id: <552CDEF6.8070905@entel.upc.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by
 milter-greylist-4.4.3 (violet.upc.es [147.83.2.51]);
 Tue, 14 Apr 2015 11:34:16 +0200 (CEST)
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.4.3
 (ackerman2.upc.es [147.83.2.244]); Tue, 14 Apr 2015 11:34:15 +0200 (CEST)
X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244
X-Mail-Scanned: Criba 2.0 + Clamd
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
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 09:34:22 -0000


 

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.

   Best,

   G.