Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755253AbYJDVyd (ORCPT ); Sat, 4 Oct 2008 17:54:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753494AbYJDVy0 (ORCPT ); Sat, 4 Oct 2008 17:54:26 -0400 Received: from rv-out-0506.google.com ([209.85.198.239]:31881 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753421AbYJDVyZ convert rfc822-to-8bit (ORCPT ); Sat, 4 Oct 2008 17:54:25 -0400 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=bdnRQiSlpIgfrbpmpFk4mHAcqw5avTeNzfWai4s0+Q9W+MNucXogl6fIfJSJw2xDqH D8sF24vs21UIfB/hVZ/xyhfkzM5aU8zaeWqDhXzbklhfEEzTmslp5bIm1yf9lWRh7TLe 2YO6rHlHnVbDfbtY6hGf7/BW5MnAlxjXzOyfg= Message-ID: <86802c440810041454s500b66e8w165c0115a2284363@mail.gmail.com> Date: Sat, 4 Oct 2008 14:54:24 -0700 From: "Yinghai Lu" To: "=?ISO-8859-1?Q?J.A._Magall=F3n?=" Subject: Re: Strange mtrrs in Aspire One Cc: Linux-Kernel In-Reply-To: <86802c440810041055w17c42136l6884880acdb40e98@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-Disposition: inline References: <20080930015733.5c6ea984@werewolf.home> <86802c440809291805r71877ad1wc68525c1ca0603e1@mail.gmail.com> <20081004152235.387a6f61@werewolf.home> <86802c440810041055w17c42136l6884880acdb40e98@mail.gmail.com> X-Google-Sender-Auth: fbd98f592dc0af78 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2051 Lines: 50 On Sat, Oct 4, 2008 at 10:55 AM, Yinghai Lu wrote: > On Sat, Oct 4, 2008 at 6:22 AM, J.A. Magall?n wrote: >> On Mon, 29 Sep 2008 18:05:51 -0700, "Yinghai Lu" wrote: >> >>> On Mon, Sep 29, 2008 at 4:57 PM, J.A. Magall?n wrote: >>> > Hi all... >>> > >>> > My aspire one is giving some strange MTRR settings with rc7-git5 (and >>> > prevous kernels, but that is what I run now...): >>> > >>> > one:~> cat /proc/mtrr >>> > reg00: base=0xfffe0000 (4095MB), size= 128KB: write-protect, count=1 >>> > reg01: base=0xfffc0000 (4095MB), size= 128KB: uncachable, count=1 >>> >>> could make mtrr_cleanup to support 128K gran_size >>> >>> > reg02: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1 >>> > reg03: base=0x10000000 ( 256MB), size= 256MB: write-back, count=1 >>> > reg04: base=0x1f800000 ( 504MB), size= 8MB: uncachable, count=1 >>> > reg05: base=0x1f600000 ( 502MB), size= 2MB: uncachable, count=1 >>> > reg06: base=0x1f500000 ( 501MB), size= 1MB: uncachable, count=1 >>> >>> > reg07: base=0x00000000 ( 0MB), size= 128KB: uncachable, count=1 >>> .. >>> > BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) >>> >>> last entry is really sick... >>> >> >> I have applied the patches you have posted in other threads, and this >> give a very strange result. The mtrr cleanup did nothing, and I had to put >> some printk's all around. > > will have one patch to assume the [0, 1M) to be coverred by var mtrrs. > please check other three patches. [PATCH 1/3] x86: mtrr_cleanup: print out correct type [PATCH 2/3] x86: mtrr_cleanup: first 1M should be coverred in var mtrrs [PATCH 3/3] x86: mtrr_cleanup: treat WRPROT as UNCACHEABLE you may need to boot with "mtrr_gran_size=64k mtrr_chunk_size=64k" YH -- 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/