Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 952410 Details for
Bug 1159192
The guest will hang while doing iozone for longevity testing on win2k8-64 guest with virtio-win drivers installed
[?]
New
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.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
DUMPanalysisbywindbg
1159192 (text/plain), 35.92 KB, created by
Min Deng
on 2014-10-31 07:57:41 UTC
(
hide
)
Description:
DUMPanalysisbywindbg
Filename:
MIME Type:
Creator:
Min Deng
Created:
2014-10-31 07:57:41 UTC
Size:
35.92 KB
patch
obsolete
> >Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64 >Copyright (c) Microsoft Corporation. All rights reserved. > > >Loading Dump File [I:\mdeng-Dumps\long-hang\MEMORY-long-hang-issue.DMP] >Kernel Complete Dump File: Full address space is available > >Symbol search path is: *** Invalid *** >**************************************************************************** >* Symbol loading may be unreliable without a symbol search path. * >* Use .symfix to have the debugger choose a symbol path. * >* After setting your symbol path, use .reload to refresh symbol locations. * >**************************************************************************** >Executable search path is: >********************************************************************* >* Symbols can not be loaded because symbol path is not initialized. * >* * >* The Symbol Path can be set by: * >* using the _NT_SYMBOL_PATH environment variable. * >* using the -y <symbol_path> argument when starting the debugger. * >* using .sympath and .sympath+ * >********************************************************************* >*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - >Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64 >Product: Server, suite: TerminalServer DataCenter SingleUserTS >Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830 >Machine Name: >Kernel base = 0xfffff800`01651000 PsLoadedModuleList = 0xfffff800`01815dd0 >Debug session time: Tue Oct 28 21:45:06.346 2014 (UTC + 8:00) >System Uptime: 12 days 22:50:42.407 >********************************************************************* >* Symbols can not be loaded because symbol path is not initialized. * >* * >* The Symbol Path can be set by: * >* using the _NT_SYMBOL_PATH environment variable. * >* using the -y <symbol_path> argument when starting the debugger. * >* using .sympath and .sympath+ * >********************************************************************* >*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - >Loading Kernel Symbols >............................................................... >................................................................ >.. >Loading User Symbols >..... >Loading unloaded module list >....*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll > > >************* Symbol Loading Error Summary ************** >Module name Error >ntkrnlmp The system cannot find the file specified >ntdll The system cannot find the file specified > >You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. >You should also verify that your symbol search path (.sympath) is correct. >*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll - >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >Use !analyze -v to get detailed debugging information. > >BugCheck 80, {4f4454, 0, 0, 0} > >***** 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!_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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** 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 *** >*** *** >************************************************************************* >Probably caused by : ntkrnlmp.exe ( nt!WheaReportHwError+243 ) > >Followup: MachineOwner >--------- > >0: kd> !analyze -v >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >NMI_HARDWARE_FAILURE (80) >This is typically due to a hardware malfunction. The hardware supplier should >be called. >Arguments: >Arg1: 00000000004f4454 >Arg2: 0000000000000000 >Arg3: 0000000000000000 >Arg4: 0000000000000000 > >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!_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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** 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 *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** 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: nt > >FAULTING_MODULE: fffff80001651000 nt > >DEBUG_FLR_IMAGE_TIMESTAMP: 49e0237f > >DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT > >BUGCHECK_STR: 0x80 > >CURRENT_IRQL: 0 > >ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre > >LAST_CONTROL_TRANSFER: from fffff800016169fe to fffff800016ab450 > >STACK_TEXT: >fffff800`026cab88 fffff800`016169fe : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx >fffff800`026cab90 fffff800`01612948 : 00000000`00000000 fffffa80`02efd9e0 00000000`00000000 00000000`00000000 : hal!HalGetInterruptVector+0x70e >fffff800`026cac00 fffff800`01772033 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalBugCheckSystem+0x1bc >fffff800`026cac70 fffff800`01616b44 : 00000000`000001f8 00000000`00000001 fffff800`026cad30 00000000`00000003 : nt!WheaReportHwError+0x243 >fffff800`026cacd0 fffff800`016e4d47 : 00000000`00000001 fffff800`026cad30 fffffa60`005eccc0 00000000`00000000 : hal!HalHandleNMI+0x11c >fffff800`026cad00 fffff800`016a9447 : 00000000`00000200 fffff800`026caef0 fffffa60`005eccc0 00000000`00000000 : nt!InbvCheckDisplayOwnership+0x18c7 >fffff800`026cad30 fffff800`016a92b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ZwUnloadKeyEx+0x627 >fffff800`026cae70 fffff800`016a9ec0 : 00000000`00000000 fffff800`016a57c2 00000000`00000010 00000000`00010202 : nt!ZwUnloadKeyEx+0x494 >fffffa60`03f67740 fffff800`016a57c2 : 00000000`00000200 fffff800`0178589b fffffa80`0303e5a0 fffffa80`036206c8 : nt!ZwUnloadKeyEx+0x10a0 >fffffa60`03f67770 fffff800`0178589b : fffffa80`0303e5a0 fffffa80`036206c8 00000000`00f8000e fffff880`05318af4 : nt!ExpInterlockedPopEntrySList+0x22 >fffffa60`03f67780 fffff800`018ecd7c : 00000000`00000011 00000000`00000001 00000000`01380000 00000000`000007ff : nt!ExAllocatePoolWithTag+0xfb >fffffa60`03f67850 fffff800`018c683e : 00000000`01394fff fffffa80`02fa9f30 fffff880`05060a28 fffffa80`0303e5a0 : nt!NtOpenProcess+0x1ac >fffffa60`03f67890 fffff800`018e3cf1 : 00000000`00000000 fffffa80`027d3c10 00000000`00000001 fffffa80`036204f8 : nt!RtlInt64ToUnicodeString+0x1bc2 >fffffa60`03f67940 fffff800`019163ce : fffff880`0616acf0 00000000`00000000 00000000`04b2f760 00000000`04b2f780 : nt!SeSetSecurityDescriptorInfo+0x221 >fffffa60`03f679c0 fffff800`01914156 : fffff880`0616acf0 fffff880`0616acf0 00000000`04b2f780 00000000`04b2f764 : nt!NtWriteFile+0x218e >fffffa60`03f67a20 fffff800`0190c0f1 : 00000000`00000000 00000000`00000000 00000000`04b2f760 fffff880`0616acf0 : nt!SeUnlockSubjectContext+0x25d6 >fffffa60`03f67a60 fffff800`0190d34a : fffffa80`030726e0 fffffa60`00000000 00000000`00000000 fffffa80`030726e0 : nt!NtQueryInformationThread+0x8d1 >fffffa60`03f67b00 fffff800`016aaef3 : fffffa80`0303e5a0 fffffa60`03f67ca0 00000000`04b2f6f8 fffff800`01915314 : nt!NtQueryInformationThread+0x1b2a >fffffa60`03f67bb0 00000000`774f756a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ZwUnloadKeyEx+0x20d3 >00000000`04b2f6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll+0x4756a > > >STACK_COMMAND: kb > >FOLLOWUP_IP: >nt!WheaReportHwError+243 >fffff800`01772033 eb42 jmp nt!WheaReportHwError+0x287 (fffff800`01772077) > >SYMBOL_STACK_INDEX: 3 > >SYMBOL_NAME: nt!WheaReportHwError+243 > >FOLLOWUP_NAME: MachineOwner > >IMAGE_NAME: ntkrnlmp.exe > >IMAGE_VERSION: 6.0.6002.18005 > >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 1159192
: 952410 |
952411