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 1145441 - [virtio-win][whql][netkvm]guests bsod/hang when run job "NDISTest 6.5 - [2 Machine] - InvalidPackets"
Summary: [virtio-win][whql][netkvm]guests bsod/hang when run job "NDISTest 6.5 - [2 Ma...
Keywords:
Status: CLOSED DUPLICATE of bug 1147202
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Yossi Hindin
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-23 05:55 UTC by lijin
Modified: 2015-05-20 23:06 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-12 07:30:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description lijin 2014-09-23 05:55:38 UTC
Description of problem:
win7-32 guest bsod(8e) when run netkvm whql job "NDISTest 6.5 - [2 Machine] - InvalidPackets"

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.1.0-4.el7.x86_64
kernel-3.10.0-165.el7.x86_64
seabios-1.7.5-4.el7.x86_64
virtio-win-prewhql-92

How reproducible:
1/1

Steps to Reproduce:
1.boot guest with:
NIC1:
/usr/libexec/qemu-kvm -name 092NICWIN732CMB -enable-kvm -m 2G -smp 2 -uuid 862b1f66-dda0-4eb9-8173-c3bc3a76c21e -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/092NICWIN732CMB,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=092NICWIN732CMB,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=092NICWIN732CMB.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:52:2a:29:b5:68,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -vga cirrus -netdev tap,script=/etc/qemu-ifup-private,downscript=no,id=hostnet1,vhost=on -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:0a:65:a9:fe,bus=pci.0,mq=on
NIC2:
/usr/libexec/qemu-kvm -name 092NICWIN732SMB -enable-kvm -m 2G -smp 2 -uuid b43c3612-8df1-4d33-b8a0-0fff7de86f8e -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/092NICWIN732SMB,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -boot order=cd,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=092NICWIN732SMB,if=none,id=drive-ide0-0-0,format=raw,serial=mike_cao,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=en_windows_7_ultimate_with_sp1_x86_dvd_u_677460.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=092NICWIN732SMB.vfd,if=none,id=drive-fdc0-0-0,format=raw,cache=none -global isa-fdc.driveA=drive-fdc0-0-0 -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=00:52:0e:50:a7:ef,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:1 -vga cirrus -netdev tap,script=/etc/qemu-ifup-private,downscript=no,id=hostnet1,vhost=on -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:56:63:86:75,bus=pci.0,mq=on
2.submit this job in hck

Actual results:
gust bsod with 8e

Expected results:
no bsod,job can pass

Additional info:
windbg info:
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: 80000003, The exception code that was not handled
Arg2: 82701f71, The address that the exception occurred at
Arg3: 933bd91c, Trap Frame
Arg4: 00000000

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

Page 275bc 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!DbgPrompt+46
82701f71 cc              int     3

TRAP_FRAME:  933bd91c -- (.trap 0xffffffff933bd91c)
ErrCode = 00000000
eax=00000002 ebx=933bd9d4 ecx=9d74254e edx=00000044 esi=9d74254f edi=00000002
eip=82701f72 esp=933bd990 ebp=933bd9ac iopl=0         nv up ei pl nz ac pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000216
nt!DbgPrompt+0x47:
82701f72 5b              pop     ebx
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  ndistest.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 826bf08c to 826e8f20

STACK_TEXT:  
933bd484 826bf08c 0000008e 80000003 82701f71 nt!KeBugCheckEx+0x1e
933bd8ac 82648dd6 933bd8c8 00000000 933bd91c nt!KiDispatchException+0x1ac
933bd914 82649678 933bd9ac 82701f71 badb0d00 nt!CommonDispatchException+0x4a
933bd914 82701f72 933bd9ac 82701f71 badb0d00 nt!KiTrap03+0xb8
933bd9ac 9d69a081 9d74254e 933bd9d4 00000002 nt!DbgPrompt+0x47
WARNING: Stack unwind information not available. Following frames may be wrong.
933bd9dc 9d63c56e 00000001 9d726f42 0000055d NDProt62+0x6c081
933bda54 9d6410f4 84a84a28 00000001 00000000 NDProt62+0xe56e
933bda7c 9d6392cd 84a84a28 ffffffff ffffffff NDProt62+0x130f4
933bdab8 9d63794f 9ec06c28 938c45f0 3c000002 NDProt62+0xb2cd
933bdb08 9d631095 3c000002 00000000 9ec06c28 NDProt62+0x994f
933bdb50 9d69b05f 3c000002 00000000 9ec06c28 NDProt62+0x3095
933bdbbc 9d6357ef 8550e720 85348470 853484e0 NDProt62+0x6d05f
933bdbdc 8293b6c3 8550e720 85348470 8506fbe0 NDProt62+0x77ef
933bdc00 8264154a 00000000 85348470 8550e720 nt!IovCallDriver+0x258
933bdc14 8283599f 8506fbe0 85348470 853484e0 nt!IofCallDriver+0x1b
933bdc34 82838b71 8550e720 8506fbe0 00000000 nt!IopSynchronousServiceTail+0x1f8
933bdcd0 8287f3f4 8550e720 85348470 00000000 nt!IopXxxControlFile+0x6aa
933bdd04 826481ea 000007b4 000009d0 00000000 nt!NtDeviceIoControlFile+0x2a
933bdd04 771e70b4 000007b4 000009d0 00000000 nt!KiFastCallEntry+0x12a
06dfaeec 00000000 00000000 00000000 00000000 0x771e70b4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NDProt62+6c081
9d69a081 8b4de4          mov     ecx,dword ptr [ebp-1Ch]

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  NDProt62+6c081

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NDProt62

IMAGE_NAME:  NDProt62.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52cef9c9

FAILURE_BUCKET_ID:  0x8E_VRFOCA_NDProt62+6c081

BUCKET_ID:  0x8E_VRFOCA_NDProt62+6c081

Followup: MachineOwner
---------


Note You need to log in before you can comment on or make changes to this bug.