Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760193AbXHBU1t (ORCPT ); Thu, 2 Aug 2007 16:27:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757746AbXHBU1k (ORCPT ); Thu, 2 Aug 2007 16:27:40 -0400 Received: from mx1.redhat.com ([66.187.233.31]:48608 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754953AbXHBU1i (ORCPT ); Thu, 2 Aug 2007 16:27:38 -0400 Message-ID: <46B23E08.4070106@redhat.com> Date: Thu, 02 Aug 2007 16:26:48 -0400 From: Chuck Ebbert Organization: Red Hat User-Agent: Thunderbird 1.5.0.12 (X11/20070719) MIME-Version: 1.0 To: Cal Peake CC: Gabriel C , Frank Hale , Kernel Mailing List , Kernel ACPI Mailing List , len.brown@intel.com, Thomas Gleixner , Ingo Molnar , Andrew Morton , Linus Torvalds , Andi Kleen Subject: Re: ACPI on Averatec 2370 References: <5ebbd9b50707291105w316f98e5h3fa17204c9119a2f@mail.gmail.com> <46ACD8DB.2020108@googlemail.com> <46B22BDA.8090604@redhat.com> In-Reply-To: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1260 Lines: 30 On 08/02/2007 03:42 PM, Cal Peake wrote: > On Thu, 2 Aug 2007, Chuck Ebbert wrote: > >> On 08/02/2007 01:50 PM, Cal Peake wrote: >>> This problem seems to be getting worse. With the latest linus tree, after >>> the initial hang where the power button is needed to bring the system back >>> to life, the boot process slows to a crawl. >>> >>> Although if I repeatedly press the shift key it'll help move things along. >>> I'm guessing the keyboard interrupt firing off is doing something to help >>> it. The system seems OK though after booting is finished. >>> >>> Upon shutdown it actually stalls out without help from the shift key. >>> >>> Any thoughts on this, or tips to help debug it further? >> Try the 'nolapic_timer' option. > > Ah, thank you Chuck! This looks to have fixed the stalling/hanging > problems I was having. > > Now I'm wondering if arch/i386/kernel/cpu/amd.c:amd_apic_timer_broken() > can (or needs to) be updated for this particular CPU revision. What does your /proc/cpuinfo say? - 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/