On Fri, Aug 04, 2006 at 05:34:50AM +0900, Akio Takebe wrote: Content-Description: Mail message body > Hi, Xen/IA64 people > > When I boot the dom0, I get some __might_sleep()'s messages. > > BUG: sleeping function called from invalid context at kernel/rwsem.c:20 > in_atomic():0, irqs_disabled():1 > > Call Trace: > [<a00000010001c7a0>] show_stack+0x40/0xa0 > sp=e00000002f7dfbb0 bsp=e00000002f7d91a8 > [<a00000010001c830>] dump_stack+0x30/0x60 > sp=e00000002f7dfd80 bsp=e00000002f7d9190 > [<a00000010006c920>] __might_sleep+0x2a0/0x2c0 > sp=e00000002f7dfd80 bsp=e00000002f7d9168 > [<a0000001000bce80>] down_read+0x20/0x60 > sp=e00000002f7dfd80 bsp=e00000002f7d9148 > [<a0000001005b14f0>] ia64_do_page_fault+0x110/0x9e0 > sp=e00000002f7dfd80 bsp=e00000002f7d90f8 > [<a000000100064be0>] xen_leave_kernel+0x0/0x3b0 > sp=e00000002f7dfe30 bsp=e00000002f7d90f8 > > > Do we need CONFIG_DEBUG_SPINLOCK_SLEEP? Yes, because it highlights bugs like the above. > If we need CONFIG_DEBUG_SPINLOCK_SLEEP, we must modify __might_sleep(). No, you must fix ia64 so that it doesn't call down_read with interrupts disabled. Dave -- http://www.codemonkey.org.uk -- Fedora-xen@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-xen
