[Xen-users] Re: Xorg problem with xen

["edu gargiulo" <egargiulo+lists@xxxxxxxxx>]

On Wed, Jan 7, 2009 at 4:05 PM, Ivan Shmakov <oneingray@xxxxxxxxx> wrote:
>>>>>> 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?

cut from /var/log/Xorg.0.log

(II) Primary Device is: PCI 00:05:0
(--) Chipset GeForce 6150 found
(II) Setting vga for screen 0.
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) NV(0): Initializing int10
(II) NV(0): Primary V_BIOS segment is: 0xc000
(--) NV(0): Chipset: "GeForce 6150"
(**) NV(0): Depth 24, (--) framebuffer bpp 32
(==) NV(0): RGB weight 888
(==) NV(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
        compiled for 1.4.2, module version = 0.1.0
        ABI class: X.Org Video Driver, version 2.0
(==) NV(0): Using HW cursor
(--) NV(0): Linear framebuffer at 0xD0000000
(--) NV(0): MMIO registers at 0xFC000000


amd64x2:~$ sudo lspci -v | grep -A 7 -F VGA
00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce
6150] (rev a2) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. A8N-VM CSM
        Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 5
        Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at fb000000 (64-bit, non-prefetchable) [size=16M]
        [virtual] Expansion ROM at c2000000 [disabled] [size=128K]
        Capabilities: [48] Power Management version 2


and finnaly the trace from /var/log/kern.log

Jan  9 21:35:34 amd64x2 kernel: [   42.782123] CPA: called for zero
pte. vaddr = ffff8800b2e32000 cpa->vaddr = ffff8800b2e32000
Jan  9 21:35:34 amd64x2 kernel: [   42.782140] ------------[ cut here
]------------
Jan  9 21:35:34 amd64x2 kernel: [   42.782144] WARNING: at
arch/x86/mm/pageattr-xen.c:571 __change_page_attr_set_clr+0x84/0xa7f()
Jan  9 21:35:34 amd64x2 kernel: [   42.782147] Modules linked in:
bridge ipv6 loop snd_hda_intel parport_pc parport snd_pcm snd_seq
snd_timer snd_seq_device snd pcspkr psmouse soundcore snd_page_alloc
serio_raw i2c_nforce2 k8temp i2c_core button evdev ext3 jbd mbcache
dm_mirror dm_log dm_snapshot dm_mod sd_mod ide_cd_mod cdrom sata_nv
ata_generic libata scsi_mod dock amd74xx forcedeth ide_pci_generic
ohci_hcd ide_core ehci_hcd thermal processor fan thermal_sys
Jan  9 21:35:34 amd64x2 kernel: [   42.782196] Pid: 3112, comm: Xorg
Tainted: G        W 2.6.26-1-xen-amd64 #1
Jan  9 21:35:34 amd64x2 kernel: [   42.782199]
Jan  9 21:35:34 amd64x2 kernel: [   42.782200] Call Trace:
Jan  9 21:35:34 amd64x2 kernel: [   42.782208]  [<ffffffff8022cba2>]
warn_on_slowpath+0x51/0x78
Jan  9 21:35:34 amd64x2 kernel: [   42.782214]  [<ffffffff8022d6ae>]
printk+0x4e/0x56
Jan  9 21:35:34 amd64x2 kernel: [   42.782225]  [<ffffffff8029b43e>]
__d_lookup+0xba/0x134
Jan  9 21:35:34 amd64x2 kernel: [   42.782230]  [<ffffffff8021950b>]
__change_page_attr_set_clr+0x84/0xa7f
Jan  9 21:35:34 amd64x2 kernel: [   42.782235]  [<ffffffff8021a7dc>]
phys_mem_access_prot_allowed+0xdb/0x247
Jan  9 21:35:34 amd64x2 kernel: [   42.782239]  [<ffffffff8023d7ca>]
search_exception_tables+0x1d/0x2f
Jan  9 21:35:34 amd64x2 kernel: [   42.782243]  [<ffffffff80218eb3>]
fixup_exception+0x10/0x29
Jan  9 21:35:34 amd64x2 kernel: [   42.782248]  [<ffffffff8029aa34>]
dput+0x21/0x13e
Jan  9 21:35:34 amd64x2 kernel: [   42.782257]  [<ffffffff80219fc2>]
change_page_attr_set_clr+0xbc/0x1d0
Jan  9 21:35:34 amd64x2 kernel: [   42.782266]  [<ffffffff8021a82f>]
phys_mem_access_prot_allowed+0x12e/0x247
Jan  9 21:35:34 amd64x2 kernel: [   42.782274]  [<ffffffff80384f1c>]
xen_mmap_mem+0x2f/0x6b
Jan  9 21:35:34 amd64x2 kernel: [   42.782278]  [<ffffffff80279b4c>]
mmap_region+0x218/0x425
Jan  9 21:35:34 amd64x2 kernel: [   42.782289]  [<ffffffff8027a376>]
do_mmap_pgoff+0x2e8/0x34d
Jan  9 21:35:34 amd64x2 kernel: [   42.782297]  [<ffffffff8020fb10>]
sys_mmap+0x8b/0x110
Jan  9 21:35:34 amd64x2 kernel: [   42.782302]  [<ffffffff8020b528>]
system_call+0x68/0x6d
Jan  9 21:35:34 amd64x2 kernel: [   42.782307]  [<ffffffff8020b4c0>]
system_call+0x0/0x6d
Jan  9 21:35:34 amd64x2 kernel: [   42.782312]
Jan  9 21:35:34 amd64x2 kernel: [   42.782314] ---[ end trace
a730a95416026273 ]---
Jan  9 21:35:34 amd64x2 kernel: [   42.782318] Xorg:3112 /dev/mem
ioremap_change_attr failed write-back for fc000000-fd000000

>        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.

Sorry for my english, I was talking about running X on my dom0,
because I want HVM domU runing windows.

regards,

--
edu

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