Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932415AbXIEXaX (ORCPT ); Wed, 5 Sep 2007 19:30:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754784AbXIEXaL (ORCPT ); Wed, 5 Sep 2007 19:30:11 -0400 Received: from mx1.redhat.com ([66.187.233.31]:51616 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754205AbXIEXaJ (ORCPT ); Wed, 5 Sep 2007 19:30:09 -0400 Message-ID: <46DF3BFF.9000809@redhat.com> Date: Wed, 05 Sep 2007 19:30:07 -0400 From: Chuck Ebbert Organization: Red Hat User-Agent: Thunderbird 1.5.0.12 (X11/20070719) MIME-Version: 1.0 To: linux-kernel Subject: Why do so many machines need "noapic"? Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 690 Lines: 15 Some systems lock up without the noapic option. 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 Sometimes it will boot up and then freeze during the startup scripts. Passing the noapic option fixes all that, but it then gets 1000 spurious interrupts per second on IRQ7 (which only shows ehci using it.) Kernel version is 2.6.22. - 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/