:
:Matthew Dillon wrote:
:>   At the moment the fix requires specifying a cpu option in your kernel 
config:
:>   
:>      options CPU_AMD64X2_INTR_SPAM
:what happens when I add this option to a non-shuttlepc/amd x2 box kernel?

    Bad things happen.  It doesn't yet check that the cpu id is correct.
    I will do that, as soon as I figure out the range of cpu IDs involved.

:>   Symptoms of the problem:
:>   
:>   * The 8259 never gets routed through to LINT0/LINT1, no matter how the
:>     IMCR is set or what the MPTable reports.
:>   * Every 8259 interrupt causes an additional spurious interrupt to occur.
:>   * Interrupt routing in general is more severely broken then usual.
:>   * The kernel is unable to get the 8254 clock interrupt routed.
:how can I check for such symptoms?
:
:TIA

    If you don't have a system with an AMD X2 based multi-core cpu, this
    fix won't help you.

    On SMP systems generally speaking a uni-processor kernel build will
    work while an SMP kernel build will not.

                                        -Matt
                                        Matthew Dillon 
                                        <[EMAIL PROTECTED]>

Reply via email to