hi, am I the only one seeing this, with unstable: ... Grant table initialized IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> Simple Boot Flag at 0x7a set to 0x80 Initializing Cryptographic API kernel BUG at arch/xen/kernel/evtchn.c:564 (shutdown_pirq)! [<c0105267>] shutdown_pirq+0xb7/0xd0 [<c01051b0>] shutdown_pirq+0x0/0xd0 [<c013958e>] teardown_irq+0x6e/0xe0 [<c01396b3>] free_irq+0xb3/0xe0 [<c0564624>] i8042_check_aux+0x54/0x190 [<c0564c33>] i8042_init+0x113/0x160 [<c054e8eb>] do_initcalls+0x2b/0xd0 [<c0104070>] init+0x0/0x110 [<c0104070>] init+0x0/0x110 [<c010409a>] init+0x2a/0x110 [<c0106df0>] kernel_thread_helper+0x0/0x10 [<c0106df5>] kernel_thread_helper+0x5/0x10 Kernel panic - not syncing: BUG! (XEN) Domain 0 shutdown: rebooting machine. Jacob _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 17 Oct 2005, at 15:29, Jacob Gorm Hansen wrote:> hi, > > am I the only one seeing this, with unstable:Noone else has reported it. It ought to be easy to track down the problem by adding tracing to startup_pirq and shutdown_pirq in arch/xen/kernel/evtchn.c. Also, perhaps worthwhile adding some tracing to the failure paths in __evtchn_close() in xen/common/event_channel.c. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel