Changes between Version 23 and Version 24 of TestingGuide


Ignore:
Timestamp:
Jan 14, 2012, 1:27:15 AM (13 years ago)
Author:
David Azarewicz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TestingGuide

    v23 v24  
    1101104. Boot the system under test. When it stops take a picture of the screen and attach the picture to your ticket.
    111111
    112 = Internal Processing Errors (IPE) =
     112= Internal Processing Errors reported by the kernel =
    113113
    114 One of the changes made to the PSD that is different from versions prior to 3.19.14 is that the PSD now checks for certain unsupported things and reports a failure back to the kernel. This provides for a more graceful, more reliable, and more informative failure.  Previous PSDs blindly continued on and would eventually fail in more obscure, usually non-traceable ways. The kernel's method of reporting such failures is the Internal Processing Error (IPE).  If you see an Internal Processing Error with the code 60004, 6009, this is the PSD reporting that it found something it couldn't handle. Unfortunately, because this part of the PSD executes so early in the boot process, there is not really a better way of informing the user of what the problem was. If your system has a serial port, you could install the debug version of the PSD, enable output to the serial port and the specific failure will be shown. Otherwise, this is a list of the possible reasons why the PSD might report a failure back to the kernel:
     114What if you get an error that says "The system detected an internal processing error at location" and a bunch of numbers?
     115
     116One of the changes made to the PSD that is different from versions prior to 3.19.14 is that the PSD now checks for certain unsupported things and reports a failure back to the kernel. This provides for a more graceful, more reliable, and more informative failure.  Previous PSDs blindly continued on and would eventually fail in more obscure, usually non-traceable ways. The kernel's method of reporting such failures is the Internal Processing Error (IPE).  If you see an Internal Processing Error with the code "60004, 6009", this is the PSD reporting that it found something it couldn't handle. Unfortunately, because this part of the PSD executes so early in the boot process, there is not really a better way of informing the user of what the problem was. If your system has a serial port, you could install the debug version of the PSD, enable output to the serial port and the specific failure will be shown. Otherwise, this is a list of the possible reasons why the PSD might report a failure back to the kernel:
    115117 - A failure to allocate required memory. A memory error, for example.
    116118 - A bad return code from any of the ACPI initialization routines. A bad return code usually means that the ACPI on your machine is defective.
    117  - A failure to map any the APICS.  This would be caused by a bad ACPI on our machine.
    118  - A failure to initialize any of the APICS.  This would be cause by bad hardware.
     119 - A failure to map any the APICs.  This would be caused by a bad ACPI on our machine.
     120 - A failure to initialize any of the APICs.  This would be cause by bad hardware.
    119121 - An unsupported kernel is detected, or if any of the patches to the kernel fail,
    120122 - An interrupt number specified by ACPI is higher than the maximum supported number.
    121123
    122 
     124The most likely reason is the last one listed above. Please note that getting an IPE does NOT indicate a defect in the PSD. It either indicates that something about your hardware is not supported, or that your hardware is broken. If you choose to open a ticket regarding IPE "60004, 6009", please open an enhancement ticket, not a defect ticket.