Bug 1058121
Summary: | [whql][netkvm]win2k8-32 BSOD with 7E code when run WLK job "Ethernet - NDISTest 6.5 (MPE)" | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | lijin <lijin> |
Component: | virtio-win | Assignee: | Yvugenfi <yvugenfi> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | dfleytma, knoel, michen, rbalakri, virt-maint, vrozenfe, yvugenfi |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
NO_DOCS
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-24 08:39:48 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: |
Description
lijin
2014-01-27 04:25:39 UTC
dump file debug info: 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) 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. Arguments: Arg1: 80000003, The exception code that was not handled Arg2: 81913b73, The address that the exception occurred at Arg3: 978d9bcc, Exception Record Address Arg4: 978d98c8, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid FAULTING_IP: nt!DbgPrompt+46 81913b73 cc int 3 EXCEPTION_RECORD: 978d9bcc -- (.exr 0xffffffff978d9bcc) ExceptionAddress: 81913b73 (nt!DbgPrompt+0x00000046) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 3 Parameter[0]: 00000002 Parameter[1]: 945045b8 Parameter[2]: 00000044 CONTEXT: 978d98c8 -- (.cxr 0xffffffff978d98c8) eax=00000002 ebx=978d9cd8 ecx=945045b8 edx=00000044 esi=945045b9 edi=00000002 eip=81913b73 esp=978d9c94 ebp=978d9cb0 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206 nt!DbgPrompt+0x46: 81913b73 cc int 3 Resetting default scope DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x7E PROCESS_NAME: System CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_PARAMETER1: 00000002 EXCEPTION_PARAMETER2: 945045b8 EXCEPTION_PARAMETER3: 00000044 LAST_CONTROL_TRANSFER: from 94491a34 to 81913b73 STACK_TEXT: 978d9cb0 94491a34 945045b8 978d9cd8 00000002 nt!DbgPrompt+0x46 WARNING: Stack unwind information not available. Following frames may be wrong. 978d9ce4 944b0834 00000001 945103d8 00000156 ndprot60+0x55a34 978d9d08 944b1990 00000001 000dbba0 9716c2e0 ndprot60+0x74834 978d9d68 944e3c00 00000000 927ad534 927ad550 ndprot60+0x75990 978d9d7c 81a0cc42 927ad550 9e17cb25 00000000 ndprot60+0xa7c00 978d9dc0 81875efe 944e3bc0 927ad550 00000000 nt!PspSystemThreadStartup+0x9d 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 FOLLOWUP_IP: ndprot60+55a34 94491a34 8b4de8 mov ecx,dword ptr [ebp-18h] SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: ndprot60+55a34 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ndprot60 IMAGE_NAME: ndprot60.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4d4be8f5 STACK_COMMAND: .cxr 0xffffffff978d98c8 ; kb FAILURE_BUCKET_ID: 0x7E_VRF_ndprot60+55a34 BUCKET_ID: 0x7E_VRF_ndprot60+55a34 Followup: MachineOwner --------- test with virtio-win-prewhql-100,2k8-32/64 guests passed the job "Ethernet - NDISTest 6.5 (MPE)",no bsod,no error package info: virtio-win-prewhql-0.1-100 qemu-kvm-rhev-2.1.2-20.el7.x86_64 kernel-3.10.0-223.el7.x86_64 seabios-1.7.5-7.el7.x86_64 spice-server-0.12.4-9.el7.x86_64 Move to Verified status according to comment#16. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2513.html |