Bug 720546
| Summary: | [WHQL][BSOD]Device Path Exerciser failed -[Job ID - 281] | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Min Deng <mdeng> | ||||||||
| Component: | virtio-win | Assignee: | Vadim Rozenfeld <vrozenfe> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6.2 | CC: | bcao, dawu, juzhang, michen, qzhang, vrozenfe | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | 6.1 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | virtio-win-prewhql-0.1-15 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2011-09-12 08:57:30 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Min Deng
2011-07-12 02:27:59 UTC
Created attachment 512315 [details]
BSOD screenshot
(In reply to comment #0) > Description of problem: > Guest hit BSOD while doing Device Path Exerciser[Job ID - 281] > > Version-Release number of selected component (if applicable): qemu: qemu-kvm-0.12.1.2-2.167.el6.x86_64 > kernel :2.6.32-164.el6.x86_64 > virtio-win-1.2.0-1.el6 > > How reproducible: > Sometimes > > Steps to Reproduce: > 1.Configure WHQL testing environment > 2.Run jobs on DTM > > Actual results: > The job hit BSOD > > > Expected results: > The job can pass > > > Additional info: > DTM version > 1.6.8367.0000 Created attachment 512319 [details]
Dump Analysis
can provide dump file if necessary.thank you!
Comment on attachment 512319 [details]
Dump Analysis
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {c0000005, 0, b8a30bc4, 0}
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
Probably caused by : ntkrpamp.exe ( nt!KiDispatchException+3b1 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: b8a30bc4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd800c). Type ".hh dbgerr001" for details
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+0
00000000 ?? ???
TRAP_FRAME: b8a30bc4 -- (.trap 0xffffffffb8a30bc4)
ErrCode = 00000010
eax=8a2faf00 ebx=00000000 ecx=8a2fa000 edx=00000100 esi=89bc7478 edi=b8a30c88
eip=00000000 esp=b8a30c38 ebp=b8a30c4c iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
00000000 ?? ???
Resetting default scope
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x8E
PROCESS_NAME: devpathexer.exe
LAST_CONTROL_TRANSFER: from 804fe817 to 804f9f33
STACK_TEXT:
b8a3078c 804fe817 0000008e c0000005 00000000 nt!KeBugCheckEx+0x1b
b8a30b54 80542085 b8a30b70 00000000 b8a30bc4 nt!KiDispatchException+0x3b1
b8a30bbc 80542036 b8a30c4c 00000000 badb0d00 nt!CommonDispatchException+0x4d
b8a30c4c 8065f5d3 b8a30c74 89bc7478 00000000 nt!KiExceptionExit+0x18a
b8a30c6c 806585bb 00000000 00000000 89bc7478 nt!VerifierIoAllocateIrp1+0x3f
b8a30ca4 8057c2bf 00000004 00000001 b8a30d64 nt!IovAllocateIrp+0x1d
b8a30d48 8054161c 000039a0 00c1ff74 00b14cd0 nt!NtSetVolumeInformationFile+0x1cb
b8a30d48 7c90e4f4 000039a0 00c1ff74 00b14cd0 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c1ff8c 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiDispatchException+3b1
804fe817 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiDispatchException+3b1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x8E_VRF_nt!KiDispatchException+3b1
BUCKET_ID: 0x8E_VRF_nt!KiDispatchException+3b1
Followup: MachineOwner
---------
Created attachment 512328 [details]
Latest dump analysis
(In reply to comment #4) > Created attachment 512319 [details] > Dump Analysis > > can provide dump file if necessary.thank you! Yes, please. Thank you, Vadim. Hi Vadim, QE cannot reproduce the issue via the virtio-win-prewhql-0.1-15 Thanks Min (In reply to comment #11) > Hi Vadim, > > QE cannot reproduce the issue via the virtio-win-prewhql-0.1-15 > > Thanks > Min Thank you, Min. Closing this bug. Best regards, Vadim. |