Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752181Ab2FLNsM (ORCPT ); Tue, 12 Jun 2012 09:48:12 -0400 Received: from nm19-vm0.bullet.mail.sp2.yahoo.com ([98.139.91.216]:36160 "HELO nm19-vm0.bullet.mail.sp2.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751354Ab2FLNsL convert rfc822-to-8bit (ORCPT ); Tue, 12 Jun 2012 09:48:11 -0400 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 957086.80823.bm@omp1066.mail.sp2.yahoo.com DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=HZ93XIVwnv/k6t8N2qTgm1W+SBC/RFULcmmR3FyqCSKnOKDVI8quu6/xpGS3ffu6iAPMsrL1GyY9QULmmsZc1w8FA9s60N6110h2A2tSwqlAhnFtEPdcJoT4xqOH9D8xZwsLLWh3L+xa0ViJxVVWJCM3QxrB7+OkCjTmqtQdrbw=; X-YMail-OSG: kShGjR0VM1kqmjooF82veVpbDUnMX1.XIoKOXGCEPEzFBpu 6e.4s_MM5l_IuoczCANbxxU91vSkSVWVszCqGHSlcX4nm8XCRVSyuVtuVjWE 0s7JrLTo3NHPo_zhkrnvpzh2DEqWLozmicLMGZBiCBJ5aE8O6ufoiInyz_LJ Z28BNUFRE9ZOaslNAI2vYYJFVf6kv9tbf1xvVkFHwONNoy7drzPcobkIhDIz JNdyafsqbKp0r.mDfNUqs9y9Po4Zow0GYFsTYLak7d0nBHD8Y9YjrhJeWtQJ kMg2UBUo1FeOLvA3fnLE40og9ZPH_9mWVOdk7U.5C2MrAm3iytlNiGeRJmAc ct0SOPcC40WNgNn2viBHSw5CHQCseFpsfwK.4XN4nuxiVCZZFk8KNllj3U_R pKjGxdW27O7050.64m9Al2lPwrEGjlWLXI7nWDSGPCMWnpfu9G9eGnY0Q_p4 W7iiRAA-- X-Mailer: YahooMailWebService/0.8.118.349524 References: <1339493860.10145.YahooMailNeo@web111708.mail.gq1.yahoo.com> <20120612103954.GB10124@x1.osrc.amd.com> Message-ID: <1339508890.39685.YahooMailNeo@web111705.mail.gq1.yahoo.com> Date: Tue, 12 Jun 2012 06:48:10 -0700 (PDT) From: Mahmood Naderan Reply-To: Mahmood Naderan Subject: Re: CPU MTRRs and linux kernel To: Borislav Petkov Cc: "\"linux-kernel@vger.kernel.org\"" , Andreas Herrmann In-Reply-To: <20120612103954.GB10124@x1.osrc.amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3010 Lines: 79 Thanks Borislav, I want to know, should I upgrade to the latest kernel or it is possible to download the source of 2.6.32-24 from repository and modify cleanup.c and then recompile? ~MN ----- Original Message ----- From: Borislav Petkov To: Mahmood Naderan Cc: "linux-kernel@vger.kernel.org" ; Andreas Herrmann Sent: Tuesday, June 12, 2012 3:09 PM Subject: Re: CPU MTRRs and linux kernel On Tue, Jun 12, 2012 at 02:37:40AM -0700, Mahmood Naderan wrote: > Hi everybody, > Abour rhis warnning in boot log: > > WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 61952MB of RAM > > ? > I >? searched a lot however didn't find a clear solution. Does AMD new > processors (62XX) have problems with new kernels or old kernels?? > Mine is: > > Linux n1 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010 x86_64 GNU/Linux > > Should I upgrade? Yes, fix is below and it got backported to -stable AFAICT but obviously the ubuntus don't have it in the kernel you cite above. commit 3fdbf004c1706480a7c7fac3c9d836fa6df20d7d Author: Andreas Herrmann Date:? Thu Sep 30 14:32:35 2010 +0200 ? ? x86, mtrr: Assume SYS_CFG[Tom2ForceMemTypeWB] exists on all future AMD CPUs ? ? ? ? Instead of adapting the CPU family check in amd_special_default_mtrr() ? ? for each new CPU family assume that all new AMD CPUs support the ? ? necessary bits in SYS_CFG MSR. ? ? ? ? Tom2Enabled is architectural (defined in APM Vol.2). ? ? Tom2ForceMemTypeWB is defined in all BKDGs starting with K8 NPT. ? ? In pre K8-NPT BKDG this bit is reserved (read as zero). ? ? ? ? W/o this adaption Linux would unnecessarily complain about bad MTRR ? ? settings on every new AMD CPU family, e.g. ? ? ? ? [? ? 0.000000] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 4863MB of RAM. ? ? ? ? Cc: stable@kernel.org # .32.x, .35.x ? ? Signed-off-by: Andreas Herrmann ? ? LKML-Reference: <20100930123235.GB20545@loge.amd.com> ? ? Signed-off-by: H. Peter Anvin diff --git a/arch/x86/kernel/cpu/mtrr/cleanup.c b/arch/x86/kernel/cpu/mtrr/cleanup.c index c5f59d071425..ac140c7be396 100644 --- a/arch/x86/kernel/cpu/mtrr/cleanup.c +++ b/arch/x86/kernel/cpu/mtrr/cleanup.c @@ -827,7 +827,7 @@ int __init amd_special_default_mtrr(void) ? ? ? ? if (boot_cpu_data.x86_vendor != X86_VENDOR_AMD) ? ? ? ? ? ? ? ? return 0; -? ? ? if (boot_cpu_data.x86 < 0xf || boot_cpu_data.x86 > 0x11) +? ? ? if (boot_cpu_data.x86 < 0xf) ? ? ? ? ? ? ? ? return 0; ? ? ? ? /* In case some hypervisor doesn't pass SYSCFG through: */ ? ? ? ? if (rdmsr_safe(MSR_K8_SYSCFG, &l, &h) < 0) -- Regards/Gruss, Boris. -- 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/