Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Apr 2015 15:07:57 +0200
From:      =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= <roger.pau@citrix.com>
To:        =?UTF-8?B?R3VzdGF1IFDDqXJleg==?= <gperez@entel.upc.edu>
Cc:        freebsd-xen@freebsd.org
Subject:   Re: Fwd: Re: Unable to boot with the dom0 xen kernel
Message-ID:  <5525282D.8060808@citrix.com>
In-Reply-To: <5523FD07.1000707@entel.upc.edu>
References:  <5523D56B.9040706@entel.upc.edu> <5523D5A7.5040809@entel.upc.edu> <5523EDBE.70709@FreeBSD.org> <5523FD07.1000707@entel.upc.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,

El 07/04/15 a les 17.51, Gustau PĂ©rez ha escrit:
>    Removing the assert prevents the panic and thus the machine boots.
> However I believe the assert was there for a reason, wouldn't it break
> somewhere else?
> 
>    OTOH, I see the machine has problems handling the interruption from
> all devices. I see watchdog timeouts from the mpt controller, usb, and
> network. Even shutting down the machine via ACPI fails (I had to unplug
> the two PS to shut it down). Probably related with the iommu=no-intremap
> in the xen_cmdline, isn't it?

The interrupt timeouts are probably related to the IOMMU errata, the
ACPI poweroff problem is because we need to negotiate the shutdown with
the hypervisor, which we currently don't do. I have a very hacky patch
for FreeBSD that should fix it, but I haven't found time to properly
integrate it:

http://xenbits.xen.org/gitweb/?p=people/royger/freebsd.git;a=patch;h=612509976d5d2af7633547e0279aae08a6508d7c

Leaving this aside, I have a patch for Xen I would like you to try on
this box, it *should* fix the INS/OUTS problem (not the poweroff). I've
pushed it to a branch on my git repo, you can find it at:

http://xenbits.xen.org/gitweb/?p=people/royger/xen.git;a=shortlog;h=refs/heads/pvh_io_ports.v1

or

git://xenbits.xen.org/people/royger/xen.git branch pvh_io_ports.v1

If you still get the timeouts please post the full boot log and we can
try to figure out if there's any workaround.

Thanks, Roger.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5525282D.8060808>