[Spice-devel] Out of surface in Xorg.0.log

[Frédéric Grelot]

Hi spice developpers, 

The problem came back, and won't leave....
It happens quickly when I start "digikam" (version 2.0.0-rc, built from source, works perfectly on an other physical PC). The guest is Fedora 15, everything up-to-date. I even use seabios version that Gerd suggested.
As soon as digikam is launched, I see "bad bpp" messages (I think I launched it at time "100" in the following log) and, when the program is initialized, "Out of surfaces" messages flood the log. I don't know what digikam does, but I can say it's certainly not too much : it is a fresh install, without any collection yet! The flood starts at the "tip of the day" screen.
I think libvirt log may be useful to, so I pasted it afterward.

See Xorg.0.log :
[    52.550] primary is 0x1f62e40
[    54.060]    Bad bpp: 1 (1)
[    54.101]    Bad bpp: 1 (1)
[    96.725]    Zero width or height
[   100.723]    Bad bpp: 1 (1)
[   100.723]    Bad bpp: 1 (1)
[   101.551]    Bad bpp: 1 (1)
[   101.551]    Bad bpp: 1 (1)
[   101.555]    Bad bpp: 1 (1)
[   101.555]    Bad bpp: 1 (1)
[   101.560]    Bad bpp: 1 (1)
[   101.560]    Bad bpp: 1 (1)
[   101.564]    Bad bpp: 1 (1)
[   101.564]    Bad bpp: 1 (1)
[   101.568]    Bad bpp: 1 (1)
[   101.568]    Bad bpp: 1 (1)
[   101.572]    Bad bpp: 1 (1)
[   101.572]    Bad bpp: 1 (1)
[   101.575]    Bad bpp: 1 (1)
[   101.576]    Bad bpp: 1 (1)
[   101.582]    Bad bpp: 1 (1)
[   101.582]    Bad bpp: 1 (1)
[   101.585]    Bad bpp: 1 (1)
[   101.585]    Bad bpp: 1 (1)
[   101.588]    Bad bpp: 1 (1)
[   101.588]    Bad bpp: 1 (1)
[   101.592]    Bad bpp: 1 (1)
[   101.592]    Bad bpp: 1 (1)
[   101.710]    Bad bpp: 1 (1)
[   101.710]    Bad bpp: 1 (1)
[   101.937]    Bad bpp: 1 (1)
[   101.943]    Bad bpp: 1 (1)
[   104.492]    Bad bpp: 1 (1)
[   104.492]    Bad bpp: 1 (1)
[   110.228]   Out of surfaces
[   110.979]   Out of surfaces
[   111.039]   Out of surfaces
[   111.164]   Out of surfaces
[   111.187]   Out of surfaces
[   111.212]   Out of surfaces
[   111.236]   Out of surfaces
[   111.260]   Out of surfaces
[   111.284]   Out of surfaces
[   111.307]   Out of surfaces
(doesn't really stop)

libvirt qemu log :
Note : "oom" number escalation happens exactly when the "Out of surfaces" flood starts.
red_dispatcher_set_cursor_peer: 
handle_dev_input: cursor connect
spice_server_add_interface: SPICE_INTERFACE_TABLET
handle_dev_input: mouse mode 2
handle_dev_destroy_surfaces: 
handle_dev_destroy_surfaces: 
handle_dev_input: oom current 7 pipe 0
handle_dev_destroy_surfaces: 
handle_dev_input: oom current 34 pipe 0
handle_dev_input: oom current 25 pipe 0
handle_dev_input: oom current 830 pipe 0
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 1000 pipe 0
(snip ... this line repeats roughly 60 times)
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 1000 pipe 0
handle_dev_input: oom current 950 pipe 0
handle_dev_input: oom current 894 pipe 0
handle_dev_input: oom current 830 pipe 0
handle_dev_input: oom current 784 pipe 0
handle_dev_input: oom current 727 pipe 0
handle_dev_input: oom current 675 pipe 0
handle_dev_input: oom current 612 pipe 0
handle_dev_input: oom current 548 pipe 0
handle_dev_input: oom current 484 pipe 0
handle_dev_input: oom current 420 pipe 0
handle_dev_input: oom current 356 pipe 0
handle_dev_input: oom current 292 pipe 0
handle_dev_input: oom current 228 pipe 0
handle_dev_input: oom current 164 pipe 0
handle_dev_input: oom current 100 pipe 0
handle_dev_input: oom current 36 pipe 0
handle_dev_input: oom current 0 pipe 0
handle_dev_input: oom current 1 pipe 0
handle_dev_input: oom current 0 pipe 0
handle_dev_input: oom current 1 pipe 0
(then, there are lots of similar messages, with alternatively "current 1" and "current 0").



I tried to increase video size to 256Mb, but X doesn't start : Xorg.0.log says :

[    22.197] (II) qxl(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    22.197] (==) qxl(0): Depth 24, (--) framebuffer bpp 32
[    22.197] (==) qxl(0): RGB weight 888
[    22.197] (==) qxl(0): Default visual is TrueColor
[    22.197] (==) qxl(0): Using gamma correction (1.0, 1.0, 1.0)
[    22.236] (II) UnloadModule: "qxl"
[    22.236] (II) Unloading qxl
[    22.236] (EE) Screen(s) found, but none have a usable configuration.
[    22.236] 
Fatal server error:
[    22.236] no screens found
[    22.236] 


I hope there is a solution to this, so tell me if there is anything I can do to help!

Frederic.

----- Mail original -----
> 
> > How does /proc/iomem look like with 128Mb?
> 
> I couldn't log in to the guest, since the host was overloaded with
> the MSI-X message. I should try with logging deactivated.
> 
> Anyway, the problem occured again (still with 64Mb), and here is
> iomem :
> 
> 00000000-0000ffff : reserved
> 00010000-0009f3ff : System RAM
> 0009f400-0009ffff : reserved
> 000f0000-000fffff : reserved
> 00100000-dfffcfff : System RAM
>   01000000-0147e0ed : Kernel code
>   0147e0ee-01b4137f : Kernel data
>   01c34000-01daffff : Kernel bss
> dfffd000-dfffffff : reserved
> f0000000-f3ffffff : 0000:00:02.0
> f4000000-f7ffffff : 0000:00:02.0
> f8000000-f8001fff : 0000:00:02.0
> f8010000-f801ffff : 0000:00:02.0
> f8020000-f8020fff : 0000:00:03.0
>   f8020000-f8020fff : virtio-pci
> f8030000-f803ffff : 0000:00:03.0
> f8040000-f8043fff : 0000:00:04.0
>   f8040000-f8043fff : ICH HD audio
> f8044000-f8044fff : 0000:00:05.0
>   f8044000-f8044fff : virtio-pci
> f8045000-f8045fff : 0000:00:06.0
>   f8045000-f8045fff : virtio-pci
> fec00000-fec003ff : IOAPIC 0
> fed00000-fed003ff : HPET 0
> fee00000-fee00fff : Local APIC
> fffbc000-ffffffff : reserved
> 100000000-11fffffff : System RAM
> 
> At the same time, libvirt log had about 10 "handle_dev_input: oom
> current X pipe 0" message per second.
> 
> 
> > Using the bios from http://spice-space.org/download/seabios/ might
> > help.
> 
> I just downloaded it, and actually it helps : the vm starts without
> problem with 128Mb. It seems to be working fine after few minutes,
> including when I'm watching a video in youtube (this is my usual
> test...).
> By the way, I noticed that upscaling seems to work in windows guests,
> but not linuxes : is it expected? (actually, the video seen in linux
> is very slow in fullscreen and very smooth in normal mode, while it
> is always smooth with windows guests).
> 
> Thanks for your help,
> 
> Frederic.
> 
> > 
> > cheers,
> >    Gerd
> > 
>