Yup Tony, thats it.
Beofre actually detecting this panic we uses to just "hang" with the
last of the buffered output showing that Linux was processing the
dt_* tree (IIRC), now at least the panic flushed out put and shows
you why.
-JX
On Sep 14, 2006, at 3:11 AM, Tony Breeds wrote:
On Tue
On Tue, Sep 12, 2006 at 06:00:17PM +0200, Segher Boessenkool wrote:
> >Sometimes when Xen is booted and we let Linux init the MPIC for
> >"the second time" Xen could end up in a loop where the CPU is
> >constantly being interrupted by the MPIC.
> >
> >Because of console buffering, the last mess
Sometimes when Xen is booted and we let Linux init the MPIC for
"the second time" Xen could end up in a loop where the CPU is
constantly being interrupted by the MPIC.
Because of console buffering, the last message you see is some
message from early kernel boot.
Anyway.. we detect this now
Sometimes when Xen is booted and we let Linux init the MPIC for "the
second time" Xen could end up in a loop where the CPU is constantly
being interrupted by the MPIC.
Because of console buffering, the last message you see is some
message from early kernel boot.
Anyway.. we detect this now
# HG changeset patch
# User Jimi Xenidis <[EMAIL PROTECTED]>
# Node ID 5495e4525844250d5f359bd4d3bda8787e817711
# Parent a79b3252bbe46a13d91586081e7f6be278b07126
[POWERPC][XEN] Detect bad spurious interrupt condition and panic instead of hang
When handing off the MPIC from Xen to Dom0, which is t
