diff -r 7a31f7298d8f -r 0c91f0baec58 crashanalysercmd/Libraries/Engine/ErrorLibrary/Resources/PLAT_generic_Kernel.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/crashanalysercmd/Libraries/Engine/ErrorLibrary/Resources/PLAT_generic_Kernel.xml Wed Apr 21 09:51:02 2010 +0300 @@ -0,0 +1,135 @@ + + + PLAT (generic Kernel) + These panics represent represent errors which are detected by generic Kernel code. Typically, they are caused by passing bad or contradictory parameters to functions.The thread causing the panic is terminated. + + + 0 + This panic is raised at system startup time if the secondary process cannot be created. + + + 2 + This panic is raised when a semaphore, a <code>DPlatSemaphore</code>, is created and a negative count value is passed to the member function creating it. + + + 3 + This panic is raised when a semaphore, a <code>DPlatSemaphore</code>, is signalled and the count value, if specified, is negative. + + + 6 + This panic is raised when fetching the home address of a specified address relative to the thread's process and the specified address is invalid. + + + 7 + These panics are raised when an illegal attempt is made to kill a thread, a <code>DPlatThread</code>; the thread may already be dead or its status may be unknown. + + + 8 + These panics are raised when an illegal attempt is made to kill a thread, a <code>DPlatThread</code>; the thread may already be dead or its status may be unknown. + + + 9 + These panics are raised when an illegal attempt is made to kill a thread, a <code>DPlatThread</code>; the thread may already be dead or its status may be unknown. + + + 12 + This panic is raised when an attempt is made to resume the first thread in a process, a <code>DPlatProcess</code>, when that process has not been loaded. + + + 15 + This panic is raised when looking up a function by ordinal in a library, a <code>DPlatLibrary</code>. The panic occurs when the specified ordinal number is zero or negative. + + + 16 + This panic is raised because of a failure in the initialization of the Hardware Abstraction Layer (the HAL); specifically, the startup reason is not recognized. + + + 17 + This panic is raised because of a failure in the initialization of the Hardware Abstraction Layer (the HAL); specifically, the keyboard could not be initialized. + + + 18 + This panic is raised because of a failure in the initialization of the Hardware Abstraction Layer (the HAL); specifically, the x-y input device could not be initialized. + + + 19 + These panics are raised by failures during system startup. + + + 20 + These panics are raised by failures during system startup. + + + 21 + These panics are raised by failures during system startup. + + + 22 + This panic is raised when a failure occurs in dispatching an exception. + + + 64 + This panic is raised when an attempt is made to create a hardware chunk when that chunk has already been created. + + + 80 + This panic is raised when a Kernel fixed heap is being created and the specified maximum length is negative. + + + 81 + This panic is raised when the Kernel attempts to mutate a fixed heap into a chunk heap and the specified minimum length is different from the current minimum length. + + + 83 + This panic is raised in debug builds only.This panic is raised by the millisecond timer when a call back has already been queued. + + + 87 + This panic is raised in debug builds only. This panic is raised during debugging when handling an exception via <code>Debug::HandleException</code> and a write operation to the remote thread running the monitor program fails. + + + 88 + This panic is raised when setting up the context for a newly created thread and the specified thread type, which defines the context, is not recognized. + + + 90 + This panic is raised if there is no screen-switch-on handler. + + + 91 + This panic is raised if a system thread has been panicked. + + + 92 + This panic is raised when an attempt is made to move a fixed address chunk. + + + 93 + These panics are raised during initialization of the MMU if creation of various components fails; for example, the domain allocator or the page table linear allocator. + + + 94 + These panics are raised during initialization of the MMU if creation of various components fails; for example, the domain allocator or the page table linear allocator. + + + 95 + These panics are raised during initialization of the MMU if creation of various components fails; for example, the domain allocator or the page table linear allocator. + + + 96 + These panics are raised during initialization of the MMU if creation of various components fails; for example, the domain allocator or the page table linear allocator. + + + 97 + These panics are raised during initialization of the MMU if creation of various components fails; for example, the domain allocator or the page table linear allocator. + + + 98 + These panics are raised during initialization of the MMU if creation of various components fails; for example, the domain allocator or the page table linear allocator. + + + 99 + These panics are raised during initialization of the MMU if creation of various components fails; for example, the domain allocator or the page table linear allocator. + + + \ No newline at end of file