[Xen-users] Re: Xorg problem with xen

[Ivan Shmakov <oneingray@xxxxxxxxx>]

>>>>> edu gargiulo <egargiulo+lists@xxxxxxxxx> writes:

 > After install xen-linux-system (2.6.26-1) on a running system, I
 > can't start X.  The X log says

 > xf86MapVidMem: Could not mmap framebuffer (0xfbfd0000,0x4000)
 > (Invalid argument)

        This may be related to Debian Bug#509733 [1] I've filed two
        weeks ago.  (The report also contains a simplistic program with
        an mmap () call triggering this bug.)

        Could you please check /var/log/kern.log (or dmesg(8) output)
        for a kernel call trace similar to the following?

[76187.443823] CPA: called for zero pte. vaddr = ffff880075ea4000 cpa->vaddr = 
ffff880075ea4000
[76187.444428] ------------[ cut here ]------------
[76187.444669] WARNING: at arch/x86/mm/pageattr-xen.c:571 
__change_page_attr_set_clr+0x84/0xad5()
[76187.444989] Modules linked in: tcp_diag inet_diag it87 hwmon_vid eeprom 
i2c_dev bridge nfsd auth_rpcgss exportfs ac battery ipv6 nfs lockd nfs_acl 
sunrpc loop parport_pc parport floppy k8temp pcspkr snd_hda_intel usblp snd_pcm 
snd_timer snd soundcore snd_page_alloc button i2c_nforce2 i2c_core evdev ext3 
jbd mbcache dm_mirror dm_log dm_snapshot dm_mod ide_generic ide_disk ide_cd_mod 
cdrom usb_storage sd_mod usbhid hid ff_memless amd74xx ide_core ata_generic 
ahci libata scsi_mod dock r8169 ehci_hcd via_rhine mii ohci_hcd thermal 
processor fan thermal_sys
[76187.455489] Pid: 28950, comm: Xorg Tainted: G        W 
2.6.26-bpo.1-xen-amd64 #1
[76187.455776] 
[76187.455836] Call Trace:
[76187.456146]  [<ffffffff8022cda7>] warn_on_slowpath+0x51/0x7b
[76187.456621]  [<ffffffff8022d8cd>] printk+0x4e/0x56
[76187.457790]  [<ffffffff8029bc57>] __d_lookup+0xb7/0x131
[76187.458239]  [<ffffffff8021962f>] __change_page_attr_set_clr+0x84/0xad5
[76187.458672]  [<ffffffff8021a95c>] phys_mem_access_prot_allowed+0xdb/0x247
[76187.459021]  [<ffffffff8023db4e>] search_exception_tables+0x1d/0x2f
[76187.459401]  [<ffffffff80218fdb>] fixup_exception+0x10/0x29
[76187.460250]  [<ffffffff8021a142>] change_page_attr_set_clr+0xc2/0x1d6
[76187.461099]  [<ffffffff8021a9af>] phys_mem_access_prot_allowed+0x12e/0x247
[76187.461988]  [<ffffffff80386320>] xen_mmap_mem+0x2f/0x6b
[76187.462376]  [<ffffffff8027a1ba>] mmap_region+0x218/0x425
[76187.463344]  [<ffffffff8027a9e4>] do_mmap_pgoff+0x2e8/0x34d
[76187.464036]  [<ffffffff8020fb39>] sys_mmap+0x8b/0x110
[76187.464548]  [<ffffffff8020b714>] tracesys+0xab/0xb0
[76187.465192] 
[76187.465309] ---[ end trace 19b4f9892ac648e5 ]---
[76187.465766] Xorg:28950 /dev/mem ioremap_change_attr failed write-back for 
e0000000-e1000000

        Apparently, similar issues were reported for GNU/Linux
        distributions other than Debian as well.  For instance, the
        following reports both mention similarly-looking issues:

https://bugzilla.novell.com/show_bug.cgi?id=422081
https://bugzilla.novell.com/show_bug.cgi?id=438610

        Both of the reports are solved, and the latter looks
        particularly close to Debian Bug#509733.  It additionally
        states:

--cut--
   ------- Comment #22 From Jan Beulich 2008-12-02 01:51:39 MST -------
Yes, thanks. So Stephan/Oliver - the bnx2 issue *is* fixed. The GUI issue,
however, will only be after the next Xen patch commit to the kernel cvs.

   ------- Comment #24 From Jan Beulich 2008-12-22 02:30:05 MST -------
Kernel patches to fix the remaining issues here have been committed and will be
available with a future kernel maintenance update.
--cut--

        However, I didn't manage to find these patches.

 > I'm running unstable on amd64 and using nv video card driver. How can
 > I fix this? I need to run X for domUs.

        I'm not sure that X server could be started in a domU when using
        paravirtualization.

[1] http://bugs.debian.org/509733
-- 
FSF associate member #7257

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