From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: mm.c:777:d2 Non-privileged (2) attempt to map I/O space 000f995a Date: Mon, 9 Nov 2009 18:50:51 -0500 Message-ID: <20091109235051.GA20408@phenom.dumpdata.com> References: <481249.38422.qm@web25602.mail.ukl.yahoo.com> <4A78CA69.3090105@goop.org> <0E87C0E865217944860BB378D2898000E1467F@srv-mail.apnos.int> <0E87C0E865217944860BB378D2898000E146B1@srv-mail.apnos.int> <4A7B306D.5080108@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4A7B306D.5080108@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: Olivier NOEL , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > > (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): kernel="/mnt/tmp/fc11/vmlinuz-2.6.31.5" #kernel="/mnt/tmp/fc11/bzImage-domU.3" ramdisk="/mnt/tmp/fc11/initrd-2.6.31.5.img" name="fc11" extra="root=/dev/mapper/VolGroup-lv_root ro earlycon=xen console=hvc0 debug loglevel=10 iommu=off" memory=4096 vcpus=1 on_poweroff="destroy" on_reboot="restart" on_crash="preserve" 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: vfb=['type=vnc,vnclisten=0.0.0.0,vncunused=1'] 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 Stack: 0000000000008000 0000000000000000 ffffffff8100c873 ffffc9000000b060 ffffc9000000c160 0000000000000000 00000000c1bce2a6 ffffffff8100d722 0000000000000001 0000000000007ff1 80000000f995a467 ffffc9000000c160 ffffea0003698bb0 ffff8800f912bcc8 ffffffff8100dd5b ffffea000367b4c8 Call Trace: [] _stext+0x1aa <-- [] xen_mc_flush+0xf4 [] get_phys_to_machine+0x30 [] xen_mc_issue+0x2e [] xen_set_domain_pte+0x8a [] xen_set_pte_at+0x37 [] __raw_callee_save_xen_make_pte+0x11 [] __do_fault+0x4a1 [] __raw_callee_save_xen_pmd_val+0x11 [] handle_mm_fault+0x253 [] xen_restore_fl_direct_reloc+0x4 [] _spin_unlock_irq+0x3e [] xen_force_evtchn_callback+0x27 [] notifier_call_chain+0x30 [] 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-2.6.18.8.hg tree, same parameters, and it worked fine.