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/
Home Products Support Community News


Re: [Xen-devel] Help!!! mm.c:566: Non-privileged (5) attempt to map I/Os

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Help!!! mm.c:566: Non-privileged (5) attempt to map I/Ospace 00000000
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 30 May 2007 11:04:47 +0100
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, Xin Zhao <zhaoxin@xxxxxxxxxxxxxx>
Delivery-date: Wed, 30 May 2007 03:03:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <465BD4DD.3010206@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <465A2CEC.1070700@xxxxxxxxxxxxxx> <8A87A9A84C201449A0C56B728ACF491E0BA814@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <465BD4DD.3010206@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6
> Thanks for your reply.
> Only Domu crashes. My setting is as follows. Dom0 runs NFS server, DomU
> runs NFS client. Both the dom0 and domu run FC4. I am using xen-unstable
> cloned in January, 2007. I have worked on this version for quite a
> while, but don't know which changeset it is.
> I got the following error message and then system hang up :
> BUG: soft lockup detected on CPU#0!
> Pid: 1579, comm:                 bash
> EIP: 0061:[<c02c0eda>] CPU: 0
> EIP is at _spin_lock+0xa/0x20
>  EFLAGS: 00000286    Not tainted  ( #6)
> EAX: dc09ace8 EBX: 00000000 ECX: 00000000 EDX: 00000000
> ESI: 00000000 EDI: dc09ac20 EBP: dc64be4c DS: 007b ES: 007b
> CR0: 8005003b CR2: 080e9c14 CR3: 1c5fc000 CR4: 00000640
>  [<c0105de3>] show_trace+0x13/0x20
>  [<c01032b0>] show_regs+0x190/0x1e0
>  [<c013bfe8>] softlockup_tick+0x88/0xa0
>  [<c01268bd>] do_timer+0x20d/0x400
>  [<c010903c>] timer_interrupt+0x1bc/0x690
>  [<c013c13f>] handle_IRQ_event+0x3f/0xd0
>  [<c013c261>] __do_IRQ+0x91/0x110
>  [<c0106bcd>] do_IRQ+0x1d/0x30
>  [<c025809b>] evtchn_do_upcall+0x9b/0xb0
>  [<c0105301>] hypervisor_callback+0x3d/0x48
>  [<e089ac73>] nfs_wait_on_requests+0x33/0xe0 [nfs]
>  [<e089bcc1>] nfs_sync_inode+0x41/0x80 [nfs]
>  [<e0895bfe>] nfs_getattr+0x2e/0xc0 [nfs]
>  [<c0169265>] vfs_getattr+0x35/0xa0
>  [<c01697c1>] vfs_stat_fd+0x41/0x60
>  [<c01698c0>] vfs_stat+0x20/0x30
>  [<c01698e9>] sys_stat64+0x19/0x30
>  [<c010512d>] syscall_call+0x7/0xb

Interesting.  I doubt this has anything to do with the IO space mapping error 
(unless you only see this on occasions when the IO space mapping error 
occurs...  I'm guessing you see the mapping error every time you boot, but 
just get the soft lockup occasionally later on?)

Do any particular usage patterns trigger this, or does it just happen anyway?  
Are you using NFS root?  Do you have any custom network configuration?


Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

Xen-devel mailing list