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.
lots of netkvm whql jobs bsod with the same code;
And when run 2 machine jobs,the client guest cannot select the correct test job,job did not start at all.
This issue block QE's netkvm testing,we will continue to test after this issue is fixed.
Thanks
Comment 7Yvugenfi@redhat.com
2017-03-13 09:42:02 UTC
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://access.redhat.com/errata/RHBA-2017:2341
Description of problem: guests bsod(d1) when running job "NDISTest 6.0 - [1 Machine] - 1c_FaultHandling" Version-Release number of selected component (if applicable): virtio-win-prewhql-133 How reproducible: 100% Steps to Reproduce: 1. boot guest with net device /usr/libexec/qemu-kvm -name 133NIC201264CFW -enable-kvm -m 6G -smp 8 -uuid 36393bc9-dab8-4b2f-958c-24f5e2db9abc -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/tmp/133NIC201264CFW,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 -drive file=133NIC201264CFW,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_server_2012_x64_dvd_915478.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=133NIC201264CFW.vfd,if=floppy,id=drive-fdc0-0-0,format=raw,cache=none -netdev tap,script=/etc/qemu-ifup,downscript=no,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:52:15:36:f1:fa -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=isa_serial0 -device usb-tablet,id=input0 -vnc 0.0.0.0:0 -vga std -M pc -netdev tap,script=/etc/qemu-ifup-private,downscript=no,id=hostnet1,vhost=on,queues=8 -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:52:64:18:dd:00,bus=pci.0,mq=on,vectors=18 2. submit job 3. Actual results: BSOD Expected results: Pass without bsod Additional info: 1 hit this issue on win10-32 win2016 and win2012 till now ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff8800f6010ee, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: netkvm+10ee fffff880`0f6010ee 488b01 mov rax,qword ptr [rcx] DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT BUGCHECK_STR: AV PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre TRAP_FRAME: fffff88002fbe3f0 -- (.trap 0xfffff88002fbe3f0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800f6010ee rsp=fffff88002fbe580 rbp=0000000000000000 r8=fffffa80056b1440 r9=0000000000000000 r10=0000000000000000 r11=0000000000000005 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz ac po cy netkvm+0x10ee: fffff880`0f6010ee 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8038267d369 to fffff8038267e040 STACK_TEXT: fffff880`02fbe2a8 fffff803`8267d369 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`02fbe2b0 fffff803`8267bbe0 : 00000000`00000000 fffffa80`0add4400 00000000`00000000 fffff880`02fbe3f0 : nt!KiBugCheckDispatch+0x69 fffff880`02fbe3f0 fffff880`0f6010ee : 00000000`00000000 00000000`c000009a fffffa80`0add47c8 fffffa80`0add43d8 : nt!KiPageFault+0x260 fffff880`02fbe580 fffff880`0f602182 : 00000000`00000000 00000000`00000000 00000000`c000009a fffffa80`0add4000 : netkvm+0x10ee fffff880`02fbe5b0 fffff880`0f60db73 : 00000000`00000000 fffff880`02fbe6e0 00000000`c000009a fffffa80`0add4000 : netkvm+0x2182 fffff880`02fbe5e0 fffff880`00ac6169 : 00000000`00000010 fffffa80`0adce1a0 00000000`00000010 00000000`00010246 : netkvm+0xdb73 fffff880`02fbe780 fffff880`00af6612 : fffffa80`0adcef08 00000000`00000000 fffff980`00000000 fffffa80`0adce1a0 : NDIS!ndisMInvokeInitialize+0x39 fffff880`02fbe7c0 fffff880`00ac9946 : fffff980`046d4dc0 fffff8a0`01934430 00000000`000001f4 01d29654`2edf7eea : NDIS!ndisMInitializeAdapter+0x4a2 fffff880`02fbebb0 fffff880`00ac9fd8 : 00000000`000001f4 fffff8a0`01934430 00000000`000001f4 fffffa80`0adce1a0 : NDIS!ndisInitializeAdapter+0x5e fffff880`02fbebf0 fffff880`00aca196 : fffffa80`0adce1a0 fffffa80`0adce050 fffff980`046d4dc0 00000000`00000000 : NDIS!ndisPnPStartDevice+0x88 fffff880`02fbec40 fffff880`00aca0fd : 00000000`00000000 fffffa80`0adce1a0 fffff880`00aca0cc fffff980`06bcefd0 : NDIS!ndisStartDeviceSynchronous+0x56 fffff880`02fbec90 fffff803`826b6391 : fffffa80`056b1440 fffff980`06bcefd0 fffffa80`056fbd00 fffff803`82887000 : NDIS!ndisStartDeviceWorkItem+0x31 fffff880`02fbecc0 fffff803`82625521 : 004c0044`002e0031 00000000`00000080 fffff803`826b6250 fffffa80`056b1440 : nt!ExpWorkerThread+0x142 fffff880`02fbed50 fffff803`82663dd6 : fffff880`02ea4180 fffffa80`056b1440 fffff880`02eaff40 fffffa80`056f5640 : nt!PspSystemThreadStartup+0x59 fffff880`02fbeda0 00000000`00000000 : fffff880`02fbf000 fffff880`02fb9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: netkvm+10ee fffff880`0f6010ee 488b01 mov rax,qword ptr [rcx] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: netkvm+10ee FOLLOWUP_NAME: MachineOwner MODULE_NAME: netkvm IMAGE_NAME: netkvm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 58b2e9d8 FAILURE_BUCKET_ID: AV_VRF_netkvm+10ee BUCKET_ID: AV_VRF_netkvm+10ee ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_vrf_netkvm+10ee FAILURE_ID_HASH: {0e36e6ad-e318-625f-c51d-749fe42bed8c} Followup: MachineOwner