Bug 1058115
| Summary: | [whql][netkvm]win2k8-32 BSOD with code 9F when run WLK job "Ethernet - NDISTest 6.5 (MPE)" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | lijin <lijin> |
| Component: | virtio-win | Assignee: | Gerd Hoffmann <kraxel> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 | CC: | dfleytma, knoel, kraxel, lijin, 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:40 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: | |||
the first 9F BSOD dump analyze: 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). Arguments: Arg1: 00000003, A device object has been blocking an Irp for too long a time Arg2: 8867fb70, Physical Device Object of the stack Arg3: 893f0028, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: 920c6f20, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49e01a44 MODULE_NAME: pci FAULTING_MODULE: 81e58000 pci DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: 8193eacc 8187a3ab 0000009f 00000003 8867fb70 nt!KeBugCheckEx+0x1e 8193eb28 81879fc8 8193eb94 91c90190 91c90100 nt!PopCheckIrpWatchdog+0x1ad 8193eb68 818f32eb 819574e0 00000000 10849c40 nt!PopCheckForIdleness+0x343 8193ec88 818f2eab 8193ecd0 89d55202 8193ecd8 nt!KiTimerListExpire+0x367 8193ece8 818f3615 00000000 00000000 0003f0de nt!KiTimerExpiration+0x22a 8193ed50 818f187d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba 8193ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0x9F_VRF_3_usbuhci_IMAGE_pci.sys BUCKET_ID: 0x9F_VRF_3_usbuhci_IMAGE_pci.sys Followup: MachineOwner --------- the second 9F BSOD dump analyze: 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time (usually 10 minutes). Arguments: Arg1: 00000003, A device object has been blocking an Irp for too long a time Arg2: 88bbd030, Physical Device Object of the stack Arg3: 892b1030, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: 962daeb8, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: pci.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49e01a44 MODULE_NAME: pci FAULTING_MODULE: 81e63000 pci DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: 81934acc 818703ab 0000009f 00000003 88bbd030 nt!KeBugCheckEx+0x1e 81934b28 8186ffc8 81934b94 90dd0cd0 90dd0c00 nt!PopCheckIrpWatchdog+0x1ad 81934b68 818e92eb 8194d4e0 00000000 156b9640 nt!PopCheckForIdleness+0x343 81934c88 818e8eab 81934cd0 8aa0f402 81934cd8 nt!KiTimerListExpire+0x367 81934ce8 818e9615 00000000 00000000 00035458 nt!KiTimerExpiration+0x22a 81934d50 818e787d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba 81934d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: 0x9F_VRF_3_netkvm_IMAGE_pci.sys BUCKET_ID: 0x9F_VRF_3_netkvm_IMAGE_pci.sys Followup: MachineOwner --------- Is this bug still reproducible? After adding multi-queue feature to virtio-net on Windows guest we run WHQL certification for the driver and didn't encounter power management related crashes. (In reply to Yan Vugenfirer from comment #8) > Is this bug still reproducible? No,job can pass with build 101,no crash > After adding multi-queue feature to virtio-net on Windows guest we run WHQL > certification for the driver and didn't encounter power management related > crashes. Move status to Verified based on comment#8& #9 (In reply to lijin from comment #9) > (In reply to Yan Vugenfirer from comment #8) > > Is this bug still reproducible? > > No,job can pass with build 101,no crash > > > After adding multi-queue feature to virtio-net on Windows guest we run WHQL > > certification for the driver and didn't encounter power management related > > crashes. Can you please indicate what version of QEMU was used for the test? Thanks. according to our test repor,we used following package :
virtio-win-prewhql-0.1-101
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
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 |
Created attachment 855888 [details] win2k8-32-netkvm-1.6.7-2-hck-log Description of problem: win2k8-32 BSOD with 9F code when run WLK job "Ethernet - NDISTest 6.5 (MPE)" Version-Release number of selected component (if applicable): qemu-kvm-rhev-1.5.3-30.el7.x86_64 kernel-3.10.0-64.el7.x86_64 seabios-1.7.2.2-7.el7.x86_64 virtio-win-prewhql-1.6.7-2 How reproducible: 2/5 Steps to Reproduce: 1.boot guest with: nic1: /usr/libexec/qemu-kvm -m 6G -M pc -smp 8,cores=8 -cpu SandyBridge,hv_spinlocks=0x1fff,hv_relaxed,hv_vapic -usb -device usb-tablet -drive file=win2k8-32-nic1.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -uuid b225ae8b-d9dd-4976-9a66-2e76c87fb24a -rtc-td-hack -no-kvm-pit-reinjection -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=a11,path=/tmp/monitor-win2k8-32-netkvm-1.6.7-2,server,nowait -mon chardev=a11,mode=readline -vnc :13 -vga cirrus -chardev socket,id=channel0,path=/tmp/tt,server,nowait -name win2k8-32-netkvm-1.6.7-2-nic1 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio -cdrom /usr/share/virtio-win/virtio-win.iso -netdev tap,sndbuf=0,id=hostnet0,vhost=on,script=/etc/qemu-ifup-private,downscript=no -device virtio-net-pci,netdev=hostnet0,mac=00:52:a2:e2:92:22 -netdev tap,sndbuf=0,id=hostnet1,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet1,mac=00:52:a2:e2:92:23 -netdev tap,sndbuf=0,id=hostnet2,vhost=on,script=/etc/qemu-ifup-private,downscript=no -device virtio nic2: /usr/libexec/qemu-kvm -m 2G -M pc -smp 2,cores=2 -cpu SandyBridge,hv_spinlocks=0x1fff,hv_relaxed,hv_vapic -usb -device usb-tablet -drive file=win2k8-32-nic2.raw,format=raw,if=none,id=drive-ide0-0-0,werror=stop,rerror=stop,cache=none -device ide-drive,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -uuid e22c777b-76ff-4c74-bca8-e43c9067b1e3 -rtc-td-hack -no-kvm-pit-reinjection -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=a11,path=/tmp/monitor-win2k8R2-netkvm-1.6.7-2,server,nowait -mon chardev=a11,mode=readline -vnc :14 -vga cirrus -chardev socket,id=channel0,path=/tmp/tt,server,nowait -name win2k8-32-netkvm-1.6.7-2-nic2 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -monitor stdio -cdrom /usr/share/virtio-win/virtio-win.iso -netdev tap,sndbuf=0,id=hostnet0,vhost=on,script=/etc/qemu-ifup-private,downscript=no -device virtio-net-pci,netdev=hostnet0,mac=00:23:a8:e0:e1:e2 -netdev tap,sndbuf=0,id=hostnet1,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet1,mac=00:23:a8:29:90:91-net-pci,netdev=hostnet2,mac=00:52:a2:71:93:13 2.submit jobs in WLK Actual results: guest BSOD,job failed Expected results: job can pass,no BSOD Additional info: 1.Job can pass with S4 disabled; 2.Will upload the dump file later. 3.There is another bsod code(7E) when run this job,I will report a new bug.