Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764145AbXHCV5R (ORCPT ); Fri, 3 Aug 2007 17:57:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763434AbXHCV5E (ORCPT ); Fri, 3 Aug 2007 17:57:04 -0400 Received: from smtp2.linux-foundation.org ([207.189.120.14]:54729 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763097AbXHCV5B (ORCPT ); Fri, 3 Aug 2007 17:57:01 -0400 Date: Fri, 3 Aug 2007 14:56:23 -0700 (PDT) From: Linus Torvalds To: Cal Peake cc: Chuck Ebbert , Gabriel C , Frank Hale , Kernel Mailing List , Kernel ACPI Mailing List , len.brown@intel.com, Thomas Gleixner , Ingo Molnar , Andrew Morton , Andi Kleen Subject: Re: ACPI on Averatec 2370 In-Reply-To: Message-ID: References: <5ebbd9b50707291105w316f98e5h3fa17204c9119a2f@mail.gmail.com> <46ACD8DB.2020108@googlemail.com> <46B22BDA.8090604@redhat.com> <46B23E08.4070106@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1564 Lines: 48 On Thu, 2 Aug 2007, Cal Peake wrote: > On Thu, 2 Aug 2007, Linus Torvalds wrote: > > > > That said, the "AMD Turion(tm) 64 X2 Mobile Technology TL-52" _should_ be > > a REV-F CPU afaik, and it should have thus fallen through to the > > "ENABLE_C1E_MASK" logic. Afaik that's broken. > > > > Cal - can you > > (a) test that forcing a "return 1" from that amd_apic_timer_broken() > > function fixes it for you. > > ACK > > > (b) make that function print out the values it uses for debugging (ie the > > xtended family and model numbers, and the MSR_K8_ENABLE_C1E MSR > > values)? > > eax & CPUID_XFAM == 0x00000000 > eax & CPUID_XMOD == 0x00040000 Yeah, that's a REV-F > MSR_K8_ENABLE_C1E lo == 0x04c14015 > MSR_K8_ENABLE_C1E hi == 0x00000000 > lo & ENABLE_C1E_MASK == 0 And yeah, that claims that C1E is not on, but: > amd_apic_timer_broken: forcing return value of 1 since this makes it all work for you, it does appear that the AMD local timer stops in C1 even when that isn't true, and as such is not useful. Sad. It probably means that we have to disable the local timer for *all* modern AMD CPU's. Thomas/Ingo - did something change in the local apic programming? Or why did this work before? Was it just that we didn't use the local timer apic for some other reason? Linus - 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/