From owner-freebsd-current Sat May 26 18:48:23 2001 Delivered-To: freebsd-current@freebsd.org Received: from gate.lustig.com (lustig.ne.mediaone.net [24.91.125.166]) by hub.freebsd.org (Postfix) with SMTP id 59C2137B423 for ; Sat, 26 May 2001 18:48:18 -0700 (PDT) (envelope-from barry@lustig.com) Received: (qmail 1876 invoked from network); 27 May 2001 01:50:15 -0000 Received: from gate.lustig.com (HELO lustig.com) (barry@205.246.2.242) by gate.lustig.com with SMTP; 27 May 2001 01:50:15 -0000 Message-ID: <3B105D56.1A637EF@lustig.com> Date: Sat, 26 May 2001 21:50:14 -0400 From: Barry Lustig Organization: Barry Lustig & Associates, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Valentin Nechayev Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Boot time memory issue References: <3B0858F9.1E483EEE@lustig.com> <20010525091937.B774@iv.nn.kiev.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Valentin Nechayev wrote: > > Sun, May 20, 2001 at 19:53:29, barry (Barry Lustig) wrote about "Boot time memory issue": > > Do verbose boot (`boot -v') with large SC_HISTORY_SIZE (1000 at least, > 2000 at most), and after boot check for "SMAP ..." lines at the very > beginning of the kernel boot log at /dev/console. (They are not written > to log viewable with dmesg.) Another way is to use serial console. > With this SMAP lines one can say more concrete diagnosis. Here are the SMAP lines: SMAP type=01 base=00000000 00000000 len=00000000 0009f800 SMAP type=02 base=00000000 0009f800 len=00000000 00000800 SMAP type=02 base=00000000 000e8400 len=00000000 00017c00 SMAP type=01 base=00000000 00100000 len=00000000 13ef0000 SMAP type=03 base=00000000 13ff0000 len=00000000 0000f800 SMAP type=04 base=00000000 13fff800 len=00000000 00000800 SMAP type=02 base=00000000 fff80000 len=00000000 00080000 Too many holes in the physical address space, giving up > > > I was curious whether the memory limitation on the Sony VAIO Z505 > > machines was an actual hardware limitation or a marketing issue. I just > > tried adding a 256MB module to my machine. The BIOS seemed to mostly > > recognize it. > > It did see 320MB of RAM, but had problems when testing all of it. > > Current (from > > a couple of weeks ago) boots, but gives me: > > Too many holes in the physical address space, giving up > > > > and comes up showing 64MB of RAM. Is this something that can be worked > > around, or have I run up against an actual hardware limit on the > > machine? > > /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message