On Wed, 2006-03-01 at 17:14 -0500, Dave Jones wrote: > In light of Matthew's comments in this thread though, I'm also wondering > if we can now get by without this diff, and just enable it by default now > that the kernel respects that the BIOS and leaves it alone if it's been > disabled. Actually, it seems that there are Lenovo ThinkCenter P4 machines with buggy BIOSes that tell us that we can enable the APIC ... but doing so eventually causes the system to hang. Granted, the Google-recommended fixes are "noapic" or "Update the BIOS", but perhaps it would be best to leave it off _except_ for the few cases where we know that we need it. (Then again, the correct solution in this case is to fix the BIOS...) --D
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- Re: [PATCH] leave APIC code inactive by default on i386
- From: Dave Jones <[email protected]>
- Re: [PATCH] leave APIC code inactive by default on i386
- References:
- [PATCH] leave APIC code inactive by default on i386
- From: "Darrick J. Wong" <[email protected]>
- Re: [PATCH] leave APIC code inactive by default on i386
- From: "Michael Ellerman" <[email protected]>
- Re: [PATCH] leave APIC code inactive by default on i386
- From: Dave Jones <[email protected]>
- Re: [PATCH] leave APIC code inactive by default on i386
- From: "Darrick J. Wong" <[email protected]>
- Re: [PATCH] leave APIC code inactive by default on i386
- From: Dave Jones <[email protected]>
- [PATCH] leave APIC code inactive by default on i386
- Prev by Date: 2.6.16rc5 'found' an extra CPU.
- Next by Date: Re: + proc-dont-lock-task_structs-indefinitely-cpuset-fix-2.patch added to -mm tree
- Previous by thread: Re: [PATCH] leave APIC code inactive by default on i386
- Next by thread: Re: [PATCH] leave APIC code inactive by default on i386
- Index(es):