Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761433AbXIJTol (ORCPT ); Mon, 10 Sep 2007 15:44:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761349AbXIJToY (ORCPT ); Mon, 10 Sep 2007 15:44:24 -0400 Received: from one.firstfloor.org ([213.235.205.2]:45735 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761347AbXIJToX (ORCPT ); Mon, 10 Sep 2007 15:44:23 -0400 Date: Mon, 10 Sep 2007 21:44:21 +0200 From: Andi Kleen To: Chuck Ebbert Cc: Prakash Punnoor , Andi Kleen , linux-kernel Subject: Re: Why do so many machines need "noapic"? Message-ID: <20070910194421.GA1819@one.firstfloor.org> References: <46DF3BFF.9000809@redhat.com> <46E1A7B5.6000104@redhat.com> <200709080717.58271.prakash@punnoor.de> <46E59716.6020404@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46E59716.6020404@redhat.com> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 687 Lines: 22 > > Yes, it has an hpet. And I tried every combination of options I could > think of. > > But, even stranger, x86_64 works (only i386 fails.) x86-64 has quite different time code (at least until the dyntick patches currently in mm) Obvious thing would be to diff the boot messages and see if anything jumps out (e.g. in interrupt routing). Or check with mm and if x86-64 is broken there too then it's likely the new time code. -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/