WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Fedora-xen-ia64 test status

To: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, ia64 Fedora Core Development <fedora-ia64-list@xxxxxxxxxx>, fedora-xen@xxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx, Aron Griffis <aron@xxxxxx>, Juan Quintela <quintela@xxxxxxxxxx>, Chris Wright <chrisw@xxxxxxxxxxxx>, Dave Jones <davej@xxxxxxxxxx>, jean-paul.pigache@xxxxxxxx
Subject: Re: [Xen-ia64-devel] Fedora-xen-ia64 test status
From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Fri, 04 Aug 2006 05:34:50 +0900
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Delivery-date: Thu, 03 Aug 2006 13:43:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <79C6B734D72AA4takebe_akio@xxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <79C6B734D72AA4takebe_akio@xxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
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?
If we need CONFIG_DEBUG_SPINLOCK_SLEEP, we must modify __might_sleep().

6073 void __might_sleep(char *file, int line)
6074 {
6075 #if defined(in_atomic)
6076         static unsigned long prev_jiffy;        /* ratelimiting */
6077 
6078         if ((in_atomic() || irqs_disabled()) &&
6079             system_state == SYSTEM_RUNNING && !oops_in_progress) {
6080                 if (time_before(jiffies, prev_jiffy + HZ) && prev_jiffy) 
<<<<this
6081                         return;
6082                 prev_jiffy = jiffies;
6083                 printk(KERN_ERR "Debug: sleeping function called from 
invalid"
6084                                 " context at %s:%d\n", file, line);
6085                 printk("in_atomic():%d, irqs_disabled():%d\n",
6086                         in_atomic(), irqs_disabled());
6087                 dump_stack();
6088         }
6089 #endif
6090 }


Best Regards,

Akio Takebe

Attachment: xen-unstable10920.log
Description: Binary data

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel