From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759630AbZANGHh (ORCPT ); Wed, 14 Jan 2009 01:07:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754789AbZANGH2 (ORCPT ); Wed, 14 Jan 2009 01:07:28 -0500 Received: from rv-out-0506.google.com ([209.85.198.228]:56490 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754741AbZANGH1 (ORCPT ); Wed, 14 Jan 2009 01:07:27 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=LSgV6a40MX5R4/54DyABr7oMrQY/4PIQMhbIyBXwUPfi+rGMT3vpkv2quaNc0WMtX2 KzVyVgfEsn6greb2PEndjU2X0U+zeIfc0g3+IrwucZV7hoGWQ+YpxQaLZXphZa42+Y7n yZQtYYErHMc4hHcoSS73t+96aGMaPxHGkRVOQ= Message-ID: <86802c440901132207l433227d9nf149506012a5721e@mail.gmail.com> Date: Tue, 13 Jan 2009 22:07:26 -0800 From: "Yinghai Lu" To: "James Kirin" Subject: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y Cc: "Roland Dreier" , linux-kernel@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: a3e92477756868ae Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 13, 2009 at 7:10 PM, James Kirin wrote: > Thank you for your reply, Roland. Unfortunately, this continues > happening after having installed the most recent version of the BIOS > available from Dell. > > I understand this is a problem in the BIOS and not the kernel, but is > there a way to have the kernel work around this bug in the BIOS and > make that memory accessible? Eg, > > http://www.gossamer-threads.com/lists/linux/kernel/991748#991748 please do 1. boot linux with "disable_mtrr_trim" in grub.conf etc 2. after booting input: echo "base=0x100000000 size=0x20000000 type=write-back" >/proc/mtrr later you could put that line in one scripts and call it from inittab # grep mtrrfixup /etc/inittab mtrr:345:once:/root/mtrrfixup.sh YH