On 10/08/15 14:40, Jason A. Donenfeld wrote:
> It turns out that domU also requires the Xen APIC driver. Otherwise we
> get stuck in busy loops that never exit, such as in this stack trace:
Applied to for-linus-4.2 and tagged for stable, thanks.
David
--
To unsubscribe from this list: send the li
On Mon, Aug 10, 2015 at 3:41 PM, David Vrabel wrote:
> On 10/08/15 14:40, Jason A. Donenfeld wrote:
>> It turns out that domU also requires the Xen APIC driver. Otherwise we
>> get stuck in busy loops that never exit, such as in this stack trace:
>
> What's the difference between v3 and v2?
I did
On 10/08/15 14:40, Jason A. Donenfeld wrote:
> It turns out that domU also requires the Xen APIC driver. Otherwise we
> get stuck in busy loops that never exit, such as in this stack trace:
What's the difference between v3 and v2?
David
--
To unsubscribe from this list: send the line "unsubscrib
It turns out that domU also requires the Xen APIC driver. Otherwise we
get stuck in busy loops that never exit, such as in this stack trace:
(gdb) target remote localhost:
Remote debugging using localhost:
__xapic_wait_icr_idle () at ./arch/x86/include/asm/ipi.h:56
56 while (n
