Bug 967802
| Summary: | [WHQL][Serial][WLK]Device Path Exerciser job faild as BSOD(3B) on win2k8-64 guest | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | lijin <lijin> |
| Component: | virtio-win | Assignee: | Gal Hammer <ghammer> |
| Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.5 | CC: | acathrow, bcao, bsarathy, dyasny, lijin, qzhang, rhod |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-06-05 08:20:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
windbg info: 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff800016e84dd, Address of the instruction which caused the bugcheck Arg3: fffffa60037b7e40, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ Page d99f7 not present in the dump file. Type ".hh dbgerr004" for details Page da077 not present in the dump file. Type ".hh dbgerr004" for details EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!KiUnwaitThread+19 fffff800`016e84dd 48099180000000 or qword ptr [rcx+80h],rdx CONTEXT: fffffa60037b7e40 -- (.cxr 0xfffffa60037b7e40) rax=fffffa60037b86c8 rbx=fffff980051f4e10 rcx=0eb8000c67b3e801 rdx=0000000000000100 rsi=fffffa60037b8990 rdi=0000000000000000 rip=fffff800016e84dd rsp=fffffa60037b86a0 rbp=fffff980051f4e88 r8=0000000000000000 r9=fffffa60037b87c0 r10=fffff80001abe440 r11=fffffa60037b89b0 r12=0000000000000000 r13=0000000000000001 r14=0000000000000000 r15=000000000000000c iopl=0 nv up ei ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286 nt!KiUnwaitThread+0x19: fffff800`016e84dd 48099180000000 or qword ptr [rcx+80h],rdx ds:002b:0eb8000c`67b3e881=???????????????? Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: devpathexer.exe CURRENT_IRQL: c LAST_CONTROL_TRANSFER: from fffff8000165d3cc to fffff800016e84dd STACK_TEXT: fffffa60`037b86a0 fffff800`0165d3cc : fffff980`051f4e10 fffff980`051f4e88 fffffa60`037b8990 00000000`00000000 : nt!KiUnwaitThread+0x19 fffffa60`037b86d0 fffff800`016cc1ce : fffff980`051f4e10 fffffa80`06da9700 fffffa60`037b8830 fffff980`051f4e10 : nt! ?? ::FNODOBFM::`string'+0x277e0 fffffa60`037b8790 fffff800`016cfc23 : fffffa60`037b88b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x19e fffffa60`037b8830 fffff800`0167a887 : fffffa80`064b8f20 00000000`00000000 fffffa80`05f05d20 fffffa80`06dcf910 : nt!KiApcInterrupt+0x103 fffffa60`037b89c0 fffff800`018a7e4d : 00000000`c0000010 fffffa60`037b8bc8 fffffa60`037b8ae8 fffffa60`037b8ca0 : nt! ?? ::FNODOBFM::`string'+0x27464 fffffa60`037b8a70 fffff800`01899453 : 00000000`00000000 fffff980`00000002 00000000`00000000 fffffa60`037b8c01 : nt!IoGetRelatedTargetDevice+0x19 fffffa60`037b8aa0 fffff800`016aa573 : fffffa80`05b63d01 fffffa80`06dba7d0 00000000`00000440 00000000`000007d0 : nt!NtSetVolumeInformationFile+0x175 fffffa60`037b8bb0 00000000`76e1854a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`02c4f978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e1854a FOLLOWUP_IP: nt!KiUnwaitThread+19 fffff800`016e84dd 48099180000000 or qword ptr [rcx+80h],rdx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiUnwaitThread+19 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4f79ae26 STACK_COMMAND: .cxr 0xfffffa60037b7e40 ; kb FAILURE_BUCKET_ID: X64_0x3B_VRF_nt!KiUnwaitThread+19 BUCKET_ID: X64_0x3B_VRF_nt!KiUnwaitThread+19 Followup: MachineOwner --------- Created attachment 753883 [details]
win2k8-64 guest bsod dump file
What is the virtio-win drivers version? l(In reply to Gal Hammer from comment #4) > What is the virtio-win drivers version? virtio-win-prewhql-62 1/2 failed I was unable to reproduce it after the guest was updated using "Windows Update". Was your guest had all Windows' updates installed as well? (In reply to Gal Hammer from comment #6) > I was unable to reproduce it after the guest was updated using "Windows > Update". > > Was your guest had all Windows' updates installed as well? Note that QE only hit this one time , then we can not reproduce on the same image . We report this issue in case of missing bugs (In reply to Mike Cao from comment #7) > (In reply to Gal Hammer from comment #6) > > I was unable to reproduce it after the guest was updated using "Windows > > Update". > > > > Was your guest had all Windows' updates installed as well? > > Note that QE only hit this one time , then we can not reproduce on the same > image . > We report this issue in case of missing bugs That didn't answer my question. Did you install the Windows updates on that image? (In reply to Gal Hammer from comment #8) > (In reply to Mike Cao from comment #7) > > (In reply to Gal Hammer from comment #6) > > > I was unable to reproduce it after the guest was updated using "Windows > > > Update". > > > > > > Was your guest had all Windows' updates installed as well? > > > > Note that QE only hit this one time , then we can not reproduce on the same > > image . > > We report this issue in case of missing bugs > > That didn't answer my question. Did you install the Windows updates on that > image? Yes , We do windows update before we put the image to QE's NFS Server (The last time we update it should be 2 month ago) Closing after running the test ~10 times without hitting this issue. I did reproduce this bug at first but it stopped occurring after Windows was updated. |
Created attachment 753861 [details] win2k8-64 guest bsod screenshot Description of problem: guest bsod with error code 3B during whql job Device Path Exerciser Version-Release number of selected component (if applicable): qemu-kvm-rhev-0.12.1.2-2.359.el6.x86_64 kernel-2.6.32-369.el6.x86_64 seabios-0.6.1.2-27.el6.x86_64 vgabios-0.6b-3.7.el6.noarch How reproducible: once Steps to Reproduce: 1.boot win2k8-64 guest: /usr/libexec/qemu-kvm -M rhel6.4.0 -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic -usb -device usb-tablet -drive file=win2k8-64-816-actived.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,id=hostnet0,script=/etc/qemu-ifup -device rtl8139,netdev=hostnet0,mac=00:52:4f:15:34:06,id=net0 -uuid bc70cb3f-e54c-497e-974b-14b5c8f7a3f5 -rtc-td-hack -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-64-serial,server,nowait -mon chardev=111a,mode=readline -name win2k8-64-serial -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=4,bus=pci.0 -chardev pty,id=channel0 -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0 -vnc :1 -vga cirrus -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 2.run job "Device Path Exerciser" Actual results: guest bsod with code:3B Expected results: no bsod,job can pass Additional info: the debug info will be update later