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 920928 - [whql][Netkvm][0x9F] BSOD always happen on Job of "NDISTest6.5-[2 Machine]-MPE_Ethernet.xml" failed on HCK for win2k8-32
Summary: [whql][Netkvm][0x9F] BSOD always happen on Job of "NDISTest6.5-[2 Machine]-MP...
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-03-13 06:00 UTC by dawu
Modified: 2014-01-01 16:30 UTC (History)
12 users (show)

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

Attachments (Terms of Use)
dump file-win2k8-32-61 (39.63 MB, application/x-zip-compressed)
2013-05-28 03:41 UTC, guo jiang 		no flags Details
View All

Description dawu 2013-03-13 06:00:37 UTC 
Description of problem:
BSOD with error 9F always happened on Job "NDISTest6.5-[2 Machine]-MPE_Ethernet.xml" failed on HCK for win2k8-32. Ran 4 times, one time passed.It's hard to pass.

Version-Release number of selected component (if applicable):
kernel-2.6.32-362.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.331.el6.x86_64
virtio-win-prewhql-54

How reproducible:
4 times, 1 time passed.

Steps to Reproduce:
1. Boot guest with CLI:
/usr/libexec/qemu-kvm -m 6G -smp 4 -cpu cpu64-rhel6,+x2apic -usbdevice tablet -drive file=win2k8-32-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:13:10:26:49:11,bus=pci.0,addr=0x4,id=virtio-net-pci0 -netdev tap,sndbuf=0,id=hostnet1,vhost=on,script=/etc/qemu-ifup-private,downscript=no -device virtio-net-pci,netdev=hostnet1,mac=00:23:4b:42:49:12,bus=pci.0,addr=0x5,id=virtio-net-pci1 -netdev tap,sndbuf=0,id=hostnet2,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet2,mac=00:11:12:c1:49:13,bus=pci.0,addr=0x6 -uuid d9591675-2132-4570-9d7d-93c40acd8337 -no-kvm-pit-reinjection -chardev socket,id=111a,path=/tmp/monitor-win2k8-32-nic1,server,nowait -mon chardev=111a,mode=readline -vnc :1 -vga cirrus -rtc base=localtime,clock=host,driftfix=slew -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0  -monitor stdio

2. Run job "NDISTest6.5-[2 Machine]-MPE_Ethernet.xml"

3. Run task "Run NDISTest Client"


Actual results:
BSOD with 9F code always happened. From qemu side, always prompt as following error:
(qemu) virtio_ioport_write: unexpected address 0x13 value 0x1
virtio_ioport_write: unexpected address 0x13 value 0x1

Expected results:
Job should pass without any error.

Additional info:
this issue also happened in OVS network configuration environment, ran 5 times, all failed without pass.
Comment 2 dawu 2013-03-13 06:17:08 UTC 
This bug is reported for *Bridge* network configuration environment.
Comment 4 Dmitry Fleytman 2013-04-29 06:43:09 UTC 
With fix for BZ#957505 and BIOS that includes 9F-related fixes we cannot reproduce this problem anymore.
Comment 5 Yvugenfi@redhat.com 2013-04-29 15:13:41 UTC 
Please retest according to comment #4.

Thanks,
Yan.
Comment 7 Mike Cao 2013-05-02 06:55:05 UTC 
(In reply to comment #4)
> With fix for BZ#957505 and BIOS that includes 9F-related fixes we cannot
> reproduce this problem anymore.

QE Do full cycle for build59 netkvm WHQL Test and find 7E BSOD bug happened that blocks QE to verify this bug ,I will report a new bug to track it and keep this bug open
Comment 8 lijin 2013-05-08 11:38:29 UTC 
win2k8-R2 hit the same issue once when run netkvm job "NDISTest6.5-[2 Machine]-MPE_Ethernet.xml" with virtio-win-prewhql-59.
BSOD happened with 9F code.
Comment 9 lijin 2013-05-08 11:39:31 UTC 
(In reply to comment #8)
> win2k8-R2 hit the same issue once when run netkvm job "NDISTest6.5-[2
> Machine]-MPE_Ethernet.xml" with virtio-win-prewhql-59.
> BSOD happened with 9F code.

windbg info:

3: 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: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
	subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006adb1a0, The thread currently holding on to the Pnp lock.
Arg4: fffff88001ef4510, nt!TRIAGE_9F_PNP on Win7

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

Implicit thread is now fffffa80`06adb1a0

DRVPOWERSTATE_SUBCODE:  4

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

MODULE_NAME: pci

FAULTING_MODULE: fffff88001197000 pci

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

STACK_TEXT:  
fffff880`01ef44d8 fffff800`01520e86 : 00000000`0000009f 00000000`00000004 00000000`00000258 fffffa80`06adb1a0 : nt!KeBugCheckEx
fffff880`01ef44e0 fffff800`016d234c : fffff880`00000000 fffff880`00000000 00000000`00000200 fffff800`0149d81a : nt!PnpBugcheckPowerTimeout+0x76
fffff880`01ef4540 fffff800`014a2e3c : 00000000`00000000 fffffa80`04f12e70 00000002`00000000 00000000`0000000e : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff880`01ef4570 fffff800`014a2cd6 : fffffa80`04f02148 fffffa80`04f02148 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff880`01ef45e0 fffff800`014a2bbe : 00000011`617c9a80 fffff880`01ef4c58 00000000`00074a40 fffff880`01eced88 : nt!KiProcessExpiredTimerList+0xc6
fffff880`01ef4c30 fffff800`014a29a7 : 00000006`38cf7bc2 00000006`00074a40 00000006`38cf7b51 00000000`00000040 : nt!KiTimerExpiration+0x1be
fffff880`01ef4cd0 fffff800`0148feca : fffff880`01ecc180 fffff880`01ed6fc0 00000000`00000000 fffff880`00ed7a00 : nt!KiRetireDpcList+0x277
fffff880`01ef4d80 00000000`00000000 : fffff880`01ef5000 fffff880`01eef000 fffff880`01ef4d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_VRFOCA_4_netkvm_IMAGE_pci.sys

BUCKET_ID:  X64_0x9F_VRFOCA_4_netkvm_IMAGE_pci.sys

Followup: MachineOwner
---------
Comment 10 lijin 2013-05-08 12:08:57 UTC 
(In reply to comment #8)
> win2k8-R2 hit the same issue once when run netkvm job "NDISTest6.5-[2
> Machine]-MPE_Ethernet.xml" with virtio-win-prewhql-59.
> BSOD happened with 9F code.

the memory.dump file can be found in \\smamit.eng.lab.tlv.redhat.com\win-team\Public\QE\Bug920928\build59-MEMORY_MPE-9F.DMP
Comment 13 guo jiang 2013-05-28 03:41:48 UTC 
Created attachment 753719 [details]
dump file-win2k8-32-61
Comment 14 Dmitry Fleytman 2013-05-28 06:32:51 UTC 
Hello,

Unfortunately it is not clear which BIOS was used for the last test cycle.
We believe this problem occurs due to a BIOS bug, did you use BIOS from here: https://bugzilla.redhat.com/show_bug.cgi?id=912561#c3

Thanks,
Dmitry
Comment 15 guo jiang 2013-05-28 07:37:46 UTC 
QE disable S3/S4(-global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1), This job passed, no BSOD.
Comment 16 Mike Cao 2013-05-28 10:09:10 UTC 
(In reply to Dmitry Fleytman from comment #14)
> Hello,
> 
> Unfortunately it is not clear which BIOS was used for the last test cycle.
> We believe this problem occurs due to a BIOS bug, did you use BIOS from
> here: https://bugzilla.redhat.com/show_bug.cgi?id=912561#c3
> 
> Thanks,
> Dmitry

Hi, Dima 

We use seabios build 27 
Based on comment #11 ,re-assign this issue 

Thanks,
Mike
Comment 22 guo jiang 2013-09-04 05:06:34 UTC 
Verified this issue on virtio-win-prewhql-67.

other package version:
  kernel-2.6.32-414.el6.x86_64
  qemu-kvm-rhev-0.12.1.2-2.398.el6.x86_64
  spice-server-0.12.4-2.el6.x86_64  
  seabios-0.6.1.2-28.el6.x86_64
  vgabios-0.6b-3.7.el6.noarch

Step as comment #0

Actual result:
MPE job could pass without bsod

Based on the above, this issue has been fixed already.
Comment 23 Mike Cao 2013-09-04 06:36:42 UTC 
Move status to VERIFIED according to comment #22.
Note You need to log in before you can comment on or make changes to this bug.