Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Red Hat Customer
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Attachment 851443 Details for
Bug 1054640
[virtio-win][netkvm]windows 8.1 x86 BSOD on DRIVER_POWER_STATE_FAILURE (9f)
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh90 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
BSOD log
DRIVER_POWER_STATE_FAILURE.txt (text/plain), 13.93 KB, created by
Chao Yang
on 2014-01-17 07:43:50 UTC
(
hide
)
Description:
BSOD log
Filename:
MIME Type:
Creator:
Chao Yang
Created:
2014-01-17 07:43:50 UTC
Size:
13.93 KB
patch
obsolete
>Probably caused by : netkvm.sys ( netkvm+5f6f ) > >Followup: MachineOwner >--------- > >0: kd> !analyze -v >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >DRIVER_POWER_STATE_FAILURE (9f) >A driver has failed to complete a power IRP within a specific time. >Arguments: >Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp > subsystem. >Arg2: 0000012c, Timeout in seconds. >Arg3: 86064400, The thread currently holding on to the Pnp lock. >Arg4: 82698b50, nt!TRIAGE_9F_PNP on Win7 and higher > >Debugging Details: >------------------ > >***** Kernel symbols are WRONG. Please fix symbols to do analysis. > >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: NT!_ETHREAD *** >*** *** >************************************************************************* >Implicit thread is now 86064400 >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: nt!_ETHREAD *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: nt!_TRIAGE_9F_PNP *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: nt!_KPRCB *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: nt!_KPRCB *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: nt!_KPRCB *** >*** *** >************************************************************************* > >ADDITIONAL_DEBUG_TEXT: >You can run '.symfix; .reload' to try to fix the symbol path and load symbols. > >MODULE_NAME: netkvm > >FAULTING_MODULE: 8141d000 nt > >DEBUG_FLR_IMAGE_TIMESTAMP: 528c66a9 > >DRVPOWERSTATE_SUBCODE: 4 > >FAULTING_THREAD: 86064400 > >CUSTOMER_CRASH_COUNT: 1 > >DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT > >BUGCHECK_STR: 0x9F > >CURRENT_IRQL: 0 > >ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre > >LAST_CONTROL_TRANSFER: from 81465501 to 81532869 > >STACK_TEXT: >WARNING: Stack unwind information not available. Following frames may be wrong. >a32c3790 81465501 a32c38a0 86064400 00000000 nt+0x115869 >a32c37c4 814634d6 00000000 00000000 a32c38a0 nt+0x48501 >a32c387c 8ca9775a a32c38a0 00000000 00000000 nt+0x464d6 >a32c38cc 81fddf6f 004c4b40 00000000 81fe85b0 ndis+0x7575a >a32c38e4 81fdad6c 86b4a1c8 856c60e8 a32c3908 netkvm+0x5f6f >a32c38f4 81fe0b0e 86b4a1c8 85d73010 856c60e8 netkvm+0x2d6c >a32c3908 8ca85a09 86b4a1c8 00000000 856c60e8 netkvm+0x8b0e >a32c3960 8ca85a58 85d73010 856c60e8 856c60e8 ndis+0x63a09 >a32c3a98 8ca8deb8 856c60e8 00000000 81463360 ndis+0x63a58 >a32c3ad4 8ca8a4da 867e7c58 a32c3afa a32c3afb ndis+0x6beb8 >a32c3afc 81461aff 856c6030 867e7c58 856c6030 ndis+0x684da >a32c3b18 816c2e8e 85757a50 85673b80 00000002 nt+0x44aff >a32c3b54 816fba39 c00000bb 00000000 00000000 nt+0x2a5e8e >a32c3bb0 814b3a91 00000000 85673b80 85673b01 nt+0x2dea39 >a32c3be4 816fd8fa a3c53988 00000000 85673b80 nt+0x96a91 >a32c3bf8 816fd89a 0000002f a3c53988 00000000 nt+0x2e08fa >a32c3c34 816fccbd 00000002 00000001 0000002f nt+0x2e089a >a32c3cd8 816f450a 00000000 a7e95530 00000001 nt+0x2dfcbd >a32c3cf8 816f0fab 816f0d10 86064400 84cae498 nt+0x2d750a >a32c3d24 814a9611 84cae498 00000000 86064400 nt+0x2d3fab >a32c3d70 814b777a 00000000 dbb38df0 00000000 nt+0x8c611 >a32c3db0 81532fe1 814a9512 00000000 00000000 nt+0x9a77a >a32c3db4 814a9512 00000000 00000000 00000000 nt+0x115fe1 >a32c3db8 00000000 00000000 00000000 a32c3dfc nt+0x8c512 > > >STACK_COMMAND: .thread 0xffffffff86064400 ; kb > >FOLLOWUP_IP: >netkvm+5f6f >81fddf6f ?? ??? > >SYMBOL_STACK_INDEX: 4 > >SYMBOL_NAME: netkvm+5f6f > >FOLLOWUP_NAME: MachineOwner > >IMAGE_NAME: netkvm.sys > >BUCKET_ID: WRONG_SYMBOLS > >FAILURE_BUCKET_ID: WRONG_SYMBOLS > >ANALYSIS_SOURCE: KM > >FAILURE_ID_HASH_STRING: km:wrong_symbols > >FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8} > >Followup: MachineOwner >---------
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1054640
: 851443 |
852598
|
853068