From owner-freebsd-current@FreeBSD.ORG Thu Sep 4 03:43:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 770D1106567D for ; Thu, 4 Sep 2008 03:43:09 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 2F1D78FC08 for ; Thu, 4 Sep 2008 03:43:08 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1738586yxb.13 for ; Wed, 03 Sep 2008 20:43:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=3ul4HS2ccayxlHURXaCiy1eh127E2B0I3ehGUx6F49I=; b=BYT4R66mBia4S0dagzKKAkI1bW+U5x5mHnCdm53Xtl6Hp+XefoAf4ApTM0Bfb27Y0R BrSoXYGjJylAgSwKDGBr43VVAe7c4J4Ndp4tkdn2CSi/iByMB+YXwfh6O2ArebY9ZsnK wYp5DzrANowjGbheFtDT2AQ/SN+WLLHQIo9AA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=lW5IcDzt0Opn4u5h8Jk5UOawOsgpxpBbBFvD5ly2rPrRr4+OL7tl8FZnt8t6CLvqff y2b3UpygNVfywN2JZNRQ7DWN1nF6p8aOp9/EVx+79v53QiBcOQolraMU9JO89gZhtUev vXy3cndywF5aZt3qJlLEMxhGUMO3kfv6EL3aU= Received: by 10.151.158.2 with SMTP id k2mr13647048ybo.118.1220499788275; Wed, 03 Sep 2008 20:43:08 -0700 (PDT) Received: by 10.150.140.14 with HTTP; Wed, 3 Sep 2008 20:43:08 -0700 (PDT) Message-ID: <8cb6106e0809032043x7eeb7aaeoc29473c028a8220f@mail.gmail.com> Date: Wed, 3 Sep 2008 23:43:08 -0400 From: "Josh Carroll" To: freebsd-current@freebsd.org In-Reply-To: <48BF17CE.1070507@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080903034943.GD11548@cicely7.cicely.de> <20080903204759.GA4898@walton.maths.tcd.ie> <8cb6106e0809031446i3e2a47dar385125ecfb0275dc@mail.gmail.com> <48BF1218.6000504@samsco.org> <8cb6106e0809031550o4960a4fanaf2ef5fe9130fc5b@mail.gmail.com> <48BF17CE.1070507@samsco.org> Cc: David Malone , Bernd Walter , ticso@cicely.de Subject: Re: MTRR fixup? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Sep 2008 03:43:09 -0000 > The SMAP table, printed early during boot when bootverbose is set, will > tell you what is mapped where. Ok, here is my SMAP (I had to transcribe it by hand from a picture, it doesn't appear in dmesg or get written to /var/run/dmesg.boot): SMAP type=01 base=0000000000000000 len=000000000009ec00 SMAP type=02 base=000000000009ec00 len=0000000000001400 SMAP type=02 base=00000000000e4000 len=000000000001c000 SMAP type=01 base=0000000000100000 len=00000000cfe80000 SMAP type=03 base=00000000cff80000 len=000000000000e000 SMAP type=04 base=00000000cff8e000 len=0000000000052000 SMAP type=02 base=00000000cffe0000 len=0000000000020000 SMAP type=02 base=00000000fee00000 len=0000000000001000 SMAP type=02 base=00000000ffe00000 len=0000000000200000 SMAP type=01 base=0000000100000000 len=0000000030000000 Comparing that to the memcontrol list output for uncacheable address ranges (the large high-order ones): 0xd0000000/0x10000000 BIOS uncacheable set-by-firmware active 0xe0000000/0x20000000 BIOS uncacheable set-by-firmware active It looks like there is only overlap for type 02 (which is "reserved" from sys/amd64/include/pc/bios.h) and of just 4K and 2M respectively: SMAP type=02 base=00000000fee00000 len=0000000000001000 (4 KB) resides inside uncacheable range [e0000000,100000000] SMAP type=02 base=00000000ffe00000 len=0000000000200000 (2048 KB) resides inside uncacheable range [e0000000,100000000] So I guess for this particular board/BIOS it is not an issue. >>> At best, nothing will happen. But more likely, your box won't boot. Yes, it caused a deadlock after some increased memory usage. Lesson learned. Josh