Return-Path: <linux-kernel-owner+w=401wt.eu-S1754813AbYCKAlU@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754813AbYCKAlU (ORCPT <rfc822;w@1wt.eu>);
	Mon, 10 Mar 2008 20:41:20 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751637AbYCKAlN
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 10 Mar 2008 20:41:13 -0400
Received: from mail.gmx.net ([213.165.64.20]:56270 "HELO mail.gmx.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP
	id S1751463AbYCKAlM convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 10 Mar 2008 20:41:12 -0400
X-Authenticated: #7313500
X-Provags-ID: V01U2FsdGVkX19JVRtmvcNJjRv21ib5+IEzEQCegUE19CuybI9Ys5
	+kO5OxpsQdjcMz
From: Jan-Simon =?iso-8859-1?q?M=F6ller?= <dl9pf@gmx.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 2.6.24] mm: BadRAM support for broken memory
Date: Tue, 11 Mar 2008 01:41:08 +0100
User-Agent: KMail/1.9.9
Cc: Pavel Machek <pavel@ucw.cz>, Jiri Kosina <jkosina@suse.cz>,
       Ingo Molnar <mingo@elte.hu>, devzero@web.de,
       linux-kernel@vger.kernel.org, rick@vanrein.org
References: <182234194@web.de> <200803101523.03620.dl9pf@gmx.de> <47D56DD3.8060108@zytor.com>
In-Reply-To: <47D56DD3.8060108@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200803110141.08863.dl9pf@gmx.de>
X-Y-GMX-Trusted: 0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 921
Lines: 37

Am Montag 10 M?rz 2008 18:20:19 schrieb H. Peter Anvin:
> Jan-Simon M?ller wrote:
> > badram=0x18690000,0xffff0000
> > (which means a whole from 0x18690000 to 0x1869ffff )
>
> memmap=0x18690000$64K
>
> 	or
>
> memmap=0x18690000$0x10000
>
> 	-hpa


Hmmm reading the kernel-parameters again and again ...

<QUOTE>
        memmap=nn[KMG]$ss[KMG]
                        [KNL,ACPI] Mark specific memory as reserved.
                        Region of memory to be used, from ss to ss+nn.
</QUOTE>


nn would be 0x18690000   or ~409MB
ss would be 0x10000      or 64k

quite big hole ???

I'm not in front of the faulty box, but something is wrong there ...

Best regards,
Jan-Simon
--
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/