Messages in this thread | | | Subject | Re: Why do so many machines need "noapic"? | From | Andi Kleen <> | Date | 06 Sep 2007 13:31:50 +0200 |
| |
Chuck Ebbert <cebbert@redhat.com> writes:
> Some systems lock up without the noapic option.
Please find patterns: cpu type, chipsets, mainboard vendors etc.
> I found one > that will freeze while trying to set up the timer interrupt. > Passing 'nolapic' makes it freeze just after: > > Setting up timer through ExtINT... works
Always boot with apic=debug
The messages means the primary timer setup methods already didn't work. ExtInt is really a crappy fallback that was originally only needed for some early SMP systems which where the timer was not wired according to specs.
But the real problem is that the standard timer access method through the local APIC didn't work.
I had a rewrite of the timer probing some time ago that tried more combinations automatically. It had some problems so it never went in, but perhaps it's worth revisiting.
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |