RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 959154 - [959154][netkvm]BSOD occurs (7E) when running NDIS MPE job or NIDS reset job
Summary: [959154][netkvm]BSOD occurs (7E) when running NDIS MPE job or NIDS reset job
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Yvugenfi@redhat.com
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 957505
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-03 08:57 UTC by Mike Cao
Modified: 2015-11-23 03:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-01 16:40:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mike Cao 2013-05-03 08:57:26 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
2.6.32-369.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.359.el6.x86_64
seabios-0.6.1.2-27.el6.x86_64
vgabios-0.6b-3.7.el6.noarch
spice-server-0.12.0-12.el6.x86_
virito-win-prewhql-59
win2012 
How reproducible:
100%

Steps to Reproduce:
1.Start VM w/ virito-net-pci
CLI:usr/libexec/qemu-kvm -m 6G -smp 8 -cpu cpu64-rhel6,+x2apic -usb -device
usb-tablet -drive
file=win2012-nic1.raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none
-device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -netdev
tap,sndbuf=0,id=hostnet0,vhost=on,script=/etc/qemu-ifup-private,downscript=no
-device
virtio-net-pci,netdev=hostnet0,mac=03:27:43:25:23:41,bus=pci.0,addr=0x4,id=virtio-net-pci0
-netdev tap,sndbuf=0,id=hostnet2,script=/etc/qemu-ifup,downscript=no -device
e1000,netdev=hostnet2,mac=00:34:12:ca:4e:30,bus=pci.0,addr=0x6 -uuid
09b02095-48d0-4dba-ad58-279f028097a1 -no-kvm-pit-reinjection -chardev
socket,id=111a,path=/tmp/monitor-win2012-nic1,server,nowait -mon
chardev=111a,mode=readline -vnc :1 -rtc base=localtime,clock=host,driftfix=slew
-global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
2.BSOD occurs (7E) when running NDIS MPE job or  NIDS reset job
3.
  
Actual results:
job failed w/ BSOD

Expected results:
job pass


Additional info:
QE did not find this issue on virtio-win-prewhql-54 ,So it is a regression
Comment 1 Mike Cao 2013-05-03 09:01:03 UTC 
0: 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: ffffffff80000003, The exception code that was not handled
Arg2: fffff8032bcfd678, The address that the exception occurred at
Arg3: fffff8800595d958, Exception Record Address
Arg4: fffff8800595d190, Context Record Address

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

Page 18fc86 not present in the dump file. Type ".hh dbgerr004" for details

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP: 
nt!DebugPrompt+18
fffff803`2bcfd678 c3              ret

EXCEPTION_RECORD:  fffff8800595d958 -- (.exr 0xfffff8800595d958)
ExceptionAddress: fffff8032bcfd678 (nt!DebugPrompt+0x0000000000000018)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000002

CONTEXT:  fffff8800595d190 -- (.cxr 0xfffff8800595d190)
rax=0000000000000002 rbx=fffffa800bb77480 rcx=fffff88006f97050
rdx=fffff88005950044 rsi=fffffa800b687078 rdi=fffffa800be2fb00
rip=fffff8032bcfd677 rsp=fffff8800595db98 rbp=fffff8800595dc40
 r8=fffff8800595dc28  r9=0000000000000002 r10=0000000000000000
r11=0000000000000000 r12=fffff8032bc88000 r13=000000021063ebcb
r14=fffff88006f61f00 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
nt!DebugPrompt+0x17:
fffff803`2bcfd677 cc              int     3
Resetting default scope

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_PARAMETER1:  0000000000000002

LAST_CONTROL_TRANSFER:  from fffff8032be20201 to fffff8032bcfd677

STACK_TEXT:  
fffff880`0595db98 fffff803`2be20201 : fffff880`0595dc40 fffff803`2bd821c0 fffffa80`0bb77480 fffffa80`0b687078 : nt!DebugPrompt+0x17
fffff880`0595dba0 fffff880`06ee986f : fffffa80`0b676fe0 fffff880`06fa0c50 fffff880`06f96ff0 81010101`01010100 : nt!DbgPrompt+0x35
fffff880`0595dbf0 fffff880`06f0e823 : fffff880`00000001 fffff880`06fa0c50 ffffffff`0000039d 81010101`01010100 : ndprot630+0x8b86f
fffff880`0595dc50 fffff880`06f61f57 : fffffa80`0b687040 fffffa80`0756d7a0 00000000`00b75700 fffff803`2bc47f19 : ndprot630+0xb0823
fffff880`0595dd00 fffff803`2bcaa535 : fffffa80`0b687078 fffff880`031a33b8 00000000`b2d0ef09 fffffa80`0756d990 : ndprot630+0x103f57
fffff880`0595dd50 fffff803`2bce8e16 : fffff803`2bf7e180 fffffa80`0bb77480 fffffa80`0be2fb00 fffffa80`04f0e100 : nt!PspSystemThreadStartup+0x59
fffff880`0595dda0 00000000`00000000 : fffff880`0595e000 fffff880`05958000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


FOLLOWUP_IP: 
ndprot630+8b86f
fffff880`06ee986f 8b442448        mov     eax,dword ptr [rsp+48h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ndprot630+8b86f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ndprot630

IMAGE_NAME:  ndprot630.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5049c61b

STACK_COMMAND:  .cxr 0xfffff8800595d190 ; kb

FAILURE_BUCKET_ID:  AV_ndprot630+8b86f

BUCKET_ID:  AV_ndprot630+8b86f

Followup: MachineOwner
---------
Comment 6 Dmitry Fleytman 2013-05-13 08:05:44 UTC 
Fixed by BZ#957505.
Please verify.
Comment 7 Min Deng 2013-05-24 04:42:09 UTC 
Hi all,

   QE already test the bug via build 61.And the get the following testing results,

   Actual results,the job can pass without any errors.
   Expected results,the job will pass.

   So the issue has be fixed on build61,thanks
Best Regards,
Min
Comment 8 Mike Cao 2013-05-28 06:00:24 UTC 
Based on comment #7 ,Move status to VERIFIED
Note You need to log in before you can comment on or make changes to this bug.