On Fri, Nov 4, 2016 at 6:44 AM, Jan Beulich wrote:
On 13.09.16 at 17:54, wrote:
>> While a hard hang in atom_asic_init() likely points at a deeper problem
>> in the driver, restore the capability to boot a Xen Dom0 by simply
>> avoiding the call there: Other than for Xen DomU, Dom0 owning a
>>> On 04.11.16 at 15:32, wrote:
> On Fri, Nov 4, 2016 at 6:44 AM, Jan Beulich wrote:
> On 13.09.16 at 17:54, wrote:
>>> While a hard hang in atom_asic_init() likely points at a deeper problem
>>> in the driver, restore the capability to boot a Xen Dom0 by simply
>>> avoiding the call
>>> On 13.09.16 at 17:54, wrote:
> While a hard hang in atom_asic_init() likely points at a deeper problem
> in the driver, restore the capability to boot a Xen Dom0 by simply
> avoiding the call there: Other than for Xen DomU, Dom0 owning a device
> does not really mean is has got passed through
While a hard hang in atom_asic_init() likely points at a deeper problem
in the driver, restore the capability to boot a Xen Dom0 by simply
avoiding the call there: Other than for Xen DomU, Dom0 owning a device
does not really mean is has got passed through to it.
In case it is of interest for
