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


[Xen-devel] mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 9 Nov 2009 18:50:51 -0500
Cc: Olivier NOEL <ONOEL@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 09 Nov 2009 15:55:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A7B306D.5080108@xxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <481249.38422.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A78CA69.3090105@xxxxxxxx> <0E87C0E865217944860BB378D2898000E1467F@xxxxxxxxxxxxxxxxxx> <0E87C0E865217944860BB378D2898000E146B1@xxxxxxxxxxxxxxxxxx> <4A7B306D.5080108@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
> > (XEN) mm.c:645:d50 Non-privileged (50) attempt to map I/O space 00000000
> > (XEN) mm.c:645:d51 Non-privileged (51) attempt to map I/O space 00000000

I can get this with the most recent kernel when PV and QEMU are involved.
But _not_ if only PV is booted and QEMU is not present.

With this entry (basically a FC11 with the latest PV-OPS kernel compiled):

extra="root=/dev/mapper/VolGroup-lv_root ro earlycon=xen console=hvc0 debug 
loglevel=10 iommu=off"
disk=[ 'phy:/dev/vg_guest/FC11,hda,w' ]
vif=[ 'mac=00:16:3e:00:00:12,bridge=eth1' ]
pci = ['0000:04:00.0']

it boots fine. If I add:

I get a stream off:

(XEN) mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a

and this is what the xenctx tells me:

[root@tst002 fc11]# ~/xen-unstable.hg/tools/xentrace/xenctx -s 
/local2/System.map  2
rip: ffffffff810091aa _stext+0x1aa 
flags: 00001212 i nz a
rsp: ffff8800f912bc40
rax: 0000000000000000   rcx: ffffffff810091aa   rdx: ffffc9000000b0a0
rbx: ffffc9000000b060   rsi: 00000000deadbeef   rdi: 00000000deadbeef
rbp: ffff8800f912bca8    r8: 0000000000000000    r9: ffffc9000000b060
r10: 0000000000000000   r11: 0000000000000212   r12: 0000000000007ff1
r13: 80000000f995a467   r14: ffffc9000000c160   r15: 0000000000000060
 cs: e033        ss: e02b        ds: 0000        es: 0000
 fs: 0000 @ 00007f77e69fa6f0
 gs: 0000 @ ffffc90000000000/0000000000000000
Code (instr addr ffffffff810091aa)
cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 0d 00 00 00 0f 05 <41> 5b 59 c3 cc 
cc cc cc cc cc cc 

 0000000000008000 0000000000000000 ffffffff8100c873 ffffc9000000b060
 ffffc9000000c160 0000000000000000 00000000c1bce2a6 ffffffff8100d722
 0000000000000001 0000000000007ff1 80000000f995a467 ffffc9000000c160
 ffffea0003698bb0 ffff8800f912bcc8 ffffffff8100dd5b ffffea000367b4c8

Call Trace:
  [<ffffffff810091aa>] _stext+0x1aa  <--
  [<ffffffff8100c873>] xen_mc_flush+0xf4 
  [<ffffffff8100d722>] get_phys_to_machine+0x30 
  [<ffffffff8100dd5b>] xen_mc_issue+0x2e 
  [<ffffffff8100fcf0>] xen_set_domain_pte+0x8a 
  [<ffffffff8100fdc8>] xen_set_pte_at+0x37 
  [<ffffffff8100ccb1>] __raw_callee_save_xen_make_pte+0x11 
  [<ffffffff81150a0d>] __do_fault+0x4a1 
  [<ffffffff8100cced>] __raw_callee_save_xen_pmd_val+0x11 
  [<ffffffff81151700>] handle_mm_fault+0x253 
  [<ffffffff81010dff>] xen_restore_fl_direct_reloc+0x4 
  [<ffffffff816bcd4a>] _spin_unlock_irq+0x3e 
  [<ffffffff8100ffdf>] xen_force_evtchn_callback+0x27 
  [<ffffffff816c091c>] notifier_call_chain+0x30 
  [<ffffffff816bd585>] paranoid_swapgs+0x8 

Looking at the xm console, it is stuck at: "Creating initial devices."

The next invocation of 'xm create' (without changing anything) changes the 
printout to:
(XEN) mm.c:841:d5 Error getting mfn 7c1b3 (pfn 784e1) from L1 entry 
800000007c1b3467 for l1e_owner=5, pg_owner=32753
which also loops around forever.

I booted up RHEL5U4 with the linux- tree, same parameters, and it 
worked fine.

Xen-devel mailing list