Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1002879

Summary: [WHQL][netkvm]2c_Mini6RSSSendRecv failed on win7 32/64 guest because support guest got BSOD[0x0000007E]
Product: Red Hat Enterprise Linux 6 Reporter: Min Deng <mdeng>
Component: virtio-winAssignee: Yvugenfi <yvugenfi>
Status: CLOSED CANTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: acathrow, bcao, bsarathy, chayang, dfleytma, juzhang, lijin, michen, yvugenfi
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-17 07:08:36 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 Min Deng 2013-08-30 07:08:24 UTC 
Description of problem:
2c_Mini6RSSSendRecv failed on win7 guest because support guest got BSOD 

Version-Release number of selected component (if applicable):
build 67
kernel-2.6.32-414.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.397.el6.x86_64
How reproducible:
4 times

Steps to Reproduce:
1.boot up guests
  with the following CLI
  /usr/libexec/qemu-kvm -M rhel6.5.0 -m 2G -smp 2,cores=2 -cpu cpu64-rhel6,+x2apic -usb -device usb-tablet -drive file=win7-64-nic2.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=00:42:53:c2:12:21,bus=pci.0,addr=0x4,id=virtio-net-pci0,ctrl_guest_offloads=on -netdev tap,sndbuf=0,id=hostnet2,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet2,mac=00:23:a3:12:41:12,bus=pci.0,addr=0x6 -uuid 5bc19b23-6b42-4ee1-a637-23eacd325391 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win7-64-nic2,server,nowait -mon chardev=111a,mode=readline -spice port=5932,disable-ticketing -vga qxl -name win7-64-nic2-67-HCK -rtc base=localtime,clock=host,driftfix=slew -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio
root     32305 38.7 17.7 2735876 2159396 pts/3 Sl+  Aug29 545:19 /usr/libexec/qemu-kvm -M rhel6.5.0 -m 2G -smp 2,cores=2 -cpu cpu64-rhel6,+x2apic -usb -device usb-tablet -drive file=win7-64-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=00:22:44:32:32:11,bus=pci.0,addr=0x4,id=virtio-net-pci0,ctrl_guest_offloads=on -netdev tap,sndbuf=0,id=hostnet2,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet2,mac=00:42:05:13:41:12,bus=pci.0,addr=0x6 -uuid e50f263f-8eb4-4e3b-9722-559564889c5d -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win7-64-nic1,server,nowait -mon chardev=111a,mode=readline -spice port=5931,disable-ticketing -vga qxl -name win7-64-nic1-67-HCK -rtc base=localtime,clock=host,driftfix=slew -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio
2.submit the job to HCK
3.

Actual results:
The job can fail because support guest got BSOD.


Expected results:
The job can pass.
Comment 1 Min Deng 2013-08-30 07:10:51 UTC 
Additional info:
*******************************************************************************
*                                                                             *
*                        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: 89693b6a, The address that the exception occurred at
Arg3: 9e34bc2c, Exception Record Address
Arg4: 9e34b810, Context Record Address

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


OVERLAPPED_MODULE: Address regions for 'ndprot62' and 'ndprot62.sys' overlap

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

FAULTING_IP: 
ndprot62+66b6a
89693b6a cc              int     3

EXCEPTION_RECORD:  9e34bc2c -- (.exr 0xffffffff9e34bc2c)
ExceptionAddress: 89693b6a (ndprot62+0x00066b6a)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 00000000
   Parameter[1]: 8476f1c0
   Parameter[2]: 00000001

CONTEXT:  9e34b810 -- (.cxr 0xffffffff9e34b810)
eax=848bb200 ebx=00000000 ecx=848bb200 edx=00000001 esi=00004e20 edi=00000000
eip=89693b6a esp=9e34bcf4 ebp=9e34bd30 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000282
ndprot62+0x66b6a:
89693b6a cc              int     3
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  8476f1c0

EXCEPTION_PARAMETER3:  00000001

LAST_CONTROL_TRANSFER:  from 896a6cd0 to 89693b6a

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
9e34bd30 896a6cd0 7633621a 00000000 00000000 ndprot62+0x66b6a
9e34bd50 8282412b 849d699c 806d29a4 00000000 ndprot62+0x79cd0
9e34bd90 826cb559 896a6c90 849d699c 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


FOLLOWUP_IP: 
ndprot62+66b6a
89693b6a cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ndprot62+66b6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ndprot62

IMAGE_NAME:  ndprot62.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5049be80

STACK_COMMAND:  .cxr 0xffffffff9e34b810 ; kb

FAILURE_BUCKET_ID:  0x7E_ndprot62+66b6a

BUCKET_ID:  0x7E_ndprot62+66b6a

Followup: MachineOwner
Comment 4 Yvugenfi@redhat.com 2013-09-01 08:50:43 UTC 
We have manual errata for this crash.

Best regards,
Yan.
Comment 5 Yvugenfi@redhat.com 2013-09-01 08:53:20 UTC 
We have manual errata for this crash.

Best regards,
Yan.
Comment 11 Mike Cao 2013-09-16 09:55:40 UTC 
Yan ,Could you help to check my comment on comment #10?

Thanks,
Mike
Comment 12 Yvugenfi@redhat.com 2013-09-16 11:05:25 UTC 
(In reply to Mike Cao from comment #11)
> Yan ,Could you help to check my comment on comment #10?
> 
> Thanks,
> Mike

You are right - we need new errata.

Please provide hck logs for the errata process.

Thanks,
Yan.
Comment 14 Dmitry Fleytman 2013-09-17 07:02:40 UTC 
Our errata covers all Windows versions so it includes NDPROT62.SYS crashes also.
Comment 15 Mike Cao 2013-09-17 07:08:36 UTC 
(In reply to Dmitry Fleytman from comment #14)
> Our errata covers all Windows versions so it includes NDPROT62.SYS crashes
> also.

Thanks ! Manual Errata 3162 can cover this crash too ,Closing