Bug 30835 - Windows 7 i386 BSOD with qxldd.dll
Summary: Windows 7 i386 BSOD with qxldd.dll
Status: RESOLVED WONTFIX
Alias: None
Product: Spice
Classification: Unclassified
Component: win32 qxl xddm (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-13 09:32 UTC by Joseph Callen
Modified: 2016-05-04 09:32 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
CrashDumpAnalysis (26.21 KB, text/plain)
2011-06-05 19:14 UTC, Gary Lucas
Details
Machine.xml file (1.96 KB, application/xml)
2011-06-05 19:31 UTC, Gary Lucas
Details
FC14.xml file (1.95 KB, application/xml)
2011-06-05 19:32 UTC, Gary Lucas
Details
KDM log that might be related. (4.46 KB, text/x-log)
2011-06-05 20:36 UTC, Gary Lucas
Details

Description Joseph Callen 2010-10-13 09:32:51 UTC
Crash seems to occur more often when using Firefox, but will happen with no applications running, just at idle.  Using the Microsoft VGA driver has no issues.  I didn't know exactly what to provide if any more information is needed please let me know.

Host OS: Fedora 13 x64 w/spice-unstable repo
Guest OS: Windows 7 with all available patches
QXL driver: Installed from spice-space.org 0.6.1

[callenj@usppkvm1 ~]$ qemu-spice --version
QEMU emulator version 0.13.50 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard

*************************** Windows 7 Patches *********************************

Description                                                 hotfixid
-----------                                                 --------
Security Update                                             KB207940
Update                                                      KB215856
Security Update                                             KB216032
Security Update                                             KB218346
Security Update                                             KB228619
Security Update                                             KB234729
Update                                                      KB239863
Security Update                                             KB241647
Update                                                      KB958488
Security Update                                             KB972270
Update                                                      KB974431
Security Update                                             KB974571
Hotfix                                                      KB975467
Security Update                                             KB975560
Update                                                      KB976662
Update                                                      KB977074
Security Update                                             KB977165
Security Update                                             KB978542
Security Update                                             KB978601
Security Update                                             KB978886
Security Update                                             KB979309
Security Update                                             KB979482
Update                                                      KB979900
Security Update                                             KB979916
Security Update                                             KB980195
Security Update                                             KB980218
Security Update                                             KB980232
Update                                                      KB980408
Security Update                                             KB980436
Security Update                                             KB981332
Security Update                                             KB981852
Security Update                                             KB982214
Security Update                                             KB982665
Security Update                                             KB982799
Security Update                                             KB983590

*************************  Windows MEMORY.DMP Analyze *************************

kd> !analyze -vv
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffc5a85c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8b9d1e34, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000000, (reserved)

Debugging Details:
------------------

*** ERROR: Module load completed but symbols could not be loaded for qxldd.dll
*** ERROR: Module load completed but symbols could not be loaded for xul.dll

BUILD_VERSION_STRING:  7600.16617.x86fre.win7_gdr.100618-1621

SYSTEM_MANUFACTURER:  Bochs

SYSTEM_PRODUCT_NAME:  Bochs

BIOS_VENDOR:  Bochs

BIOS_VERSION:  Bochs

OVERLAPPED_UNLOADED_MODULE: Address regions for 'dump_dumpfve' and 'dump_storport.sys (unloaded)' overlap

READ_ADDRESS:  ffc5a85c 

FAULTING_IP: 
qxldd+1e34
8b9d1e34 2b814c050e00    sub     eax,dword ptr [ecx+0E054Ch]

MM_INTERNAL_CODE:  0

IMAGE_NAME:  qxldd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4c7d0391

MODULE_NAME: qxldd

FAULTING_MODULE: 8b9d0000 qxldd

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  WIN7KVM

ANALYSIS_SESSION_TIME:  10-13-2010 11:57:48.0282

TRAP_FRAME:  811c9a2c -- (.trap 0xffffffff811c9a2c)
ErrCode = 00000000
eax=ffb7a270 ebx=fe6a2db0 ecx=ffb7a310 edx=ffc5aa2c esi=ffb851a8 edi=0061b42b
eip=8b9d1e34 esp=811c9aa0 ebp=811c9aa0 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
qxldd+0x1e34:
8b9d1e34 2b814c050e00    sub     eax,dword ptr [ecx+0E054Ch] ds:0023:ffc5a85c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81647638 to 81686903

STACK_TEXT:  
811c9a14 81647638 00000000 ffc5a85c 00000000 nt!MmAccessFault+0x106
811c9a14 8b9d1e34 00000000 ffc5a85c 00000000 nt!KiTrap0E+0xdc
WARNING: Stack unwind information not available. Following frames may be wrong.
811c9aa0 8b8da946 ffb7a270 0a8df88e 0061b42b qxldd+0x1e34
811c9ad8 8b7dd37c ffb7a270 ffb7a270 811c9b90 win32k!WatchdogDrvDeleteDeviceBitmap+0x31
811c9b6c 8b7de790 00000000 00000000 ffa8a010 win32k!SURFACE::bDeleteSurface+0x235
811c9b80 8b7be2a3 00000000 ffa8a010 fe6a2db0 win32k!SURFREF::bDeleteSurface+0x14
811c9b94 8b9e220c 400508ab 00000000 ffa8a010 win32k!bDeleteSurface+0x20
811c9bb4 8b9d1dd5 400508ab 0000045c 0000024e qxldd+0x1220c
811c9bec 8b8da8ad 00000000 0000045c 0000024e qxldd+0x1dd5
811c9c34 8b7b7a20 ffa8a010 0000045c 0000024e win32k!WatchdogDrvCreateDeviceBitmap+0x3f
811c9c90 8b7b7661 00000000 00000006 01080026 win32k!hsurfCreateCompatibleSurface+0x171
811c9d0c 8b7b76f3 ffb84008 0000045c 0000024e win32k!GreCreateCompatibleBitmap+0x1cd
811c9d20 8164444a 030101ba 0000045c 0000024e win32k!NtGdiCreateCompatibleBitmap+0x19
811c9d20 77b064f4 030101ba 0000045c 0000024e nt!KiFastCallEntry+0x12a
001aea04 765f73c6 765f73ae 030101ba 0000045c ntdll!KiFastSystemCallRet
001aea08 765f73ae 030101ba 0000045c 0000024e GDI32!NtGdiCreateCompatibleBitmap+0xc
001aee7c 6f3ce0d4 030101ba 0000045c 0000024e GDI32!CreateCompatibleBitmap+0xec
00000000 00000000 00000000 00000000 00000000 xul+0x28e0d4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
qxldd+1e34
8b9d1e34 2b814c050e00    sub     eax,dword ptr [ecx+0E054Ch]

FAULT_INSTR_CODE:  54c812b

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  qxldd+1e34

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x50_qxldd+1e34

BUCKET_ID:  0x50_qxldd+1e34

ANALYSIS_SESSION_ELAPSED_TIME: 4162

Followup: MachineOwner
---------
Comment 1 gvenkat 2011-05-11 02:03:57 UTC
Check how much memory is allocated to the video card of type qxl. The current virt-manager defaults to 9MB and cannot be changed from the virt-manager GUI. This needs to be at least 64MB for qxl drivers to work reliably as I found out by googling. You can go and change the .xml file for the VM to increase the memory and use virsh to define the vm again. virt-manager will then show the updated video memory and qxl becomes a lot more stable after that. This may or may not be related to your problem but worth checking.

(In reply to comment #0)
> Crash seems to occur more often when using Firefox, but will happen with no
> applications running, just at idle.  Using the Microsoft VGA driver has no
> issues.  I didn't know exactly what to provide if any more information is
> needed please let me know.
>
Comment 2 Gary Lucas 2011-06-05 19:14:34 UTC
Created attachment 47575 [details]
CrashDumpAnalysis

Crash dump analysis
Comment 3 Gary Lucas 2011-06-05 19:31:36 UTC
Created attachment 47576 [details]
Machine.xml file
Comment 4 Gary Lucas 2011-06-05 19:32:23 UTC
Created attachment 47577 [details]
FC14.xml file
Comment 5 Gary Lucas 2011-06-05 19:33:55 UTC
I've been having similar issues with my VM's.

My host is running FC15 stable.
- 1st VM is running WinXP (crashdump attached).  The driver QXL is definitly listed as the culprit.
-- This is somewhat reproducible... Open firefox (3 on my system) find a long web page with lots of graphics and scroll up and down quickly...  Eventually my VM will crash.

2nd VM is running FC14
-- Under similar circumstances the VM will log me out and kick me back to the login screen.  It is almost completely random when this will occur.

I haven't been able to track down anything meaningfull in the logs except this which may or may not be related:

[ 194.694] Cache contents: null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null 560 865 357 454 510 555 973 1014 837 total: 9
[ 194.706] - 1th attempt
[ 194.706] - OOM at 1033 849 32
[ 194.706] Cache contents: null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null 560 865 357 454 510 555 973 1014 837 total: 9
[ 194.717] - 2th attempt
[ 194.717] - OOM at 1033 849 32
[ 194.717] Cache contents: null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null null 560 865 357 454 510 555 973 1014 837 total: 9
[ 194.729] Out of video memory: Could not allocate 3512200 bytes
[ 212.525] Bad bpp: 1 (1)
[ 412.875] Bad bpp: 1 (1)

This has never happened when not using the QXL driver / device...  Both machine's XML's are included as attachments.

I don't think it's the 9MB issue detailed below, or if it is then I don't know how to check how much ram the virtual video device has.
Comment 6 Gary Lucas 2011-06-05 20:36:31 UTC
Created attachment 47578 [details]
KDM log that might be related.

This excerpt from the guest FC14 installation seems to be issueing an out of memory error.
Comment 7 Marc-Andre Lureau 2014-11-03 15:38:51 UTC
Can you please provide an update on this bug with current releases? thanks
Comment 8 Victor Toso 2016-05-04 09:32:13 UTC
I'm closing this due inactivity: NEEDINFO since 2014-11-03


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.