From owner-freebsd-current@FreeBSD.ORG Thu Jan 22 13:31:52 2009 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 9EEB9106564A; Thu, 22 Jan 2009 13:31:52 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 0D3C58FC16; Thu, 22 Jan 2009 13:31:50 +0000 (UTC) (envelope-from bra@fsn.hu) Received: by people.fsn.hu (Postfix, from userid 125) id 5405112A53D; Thu, 22 Jan 2009 14:29:41 +0100 (CET) Received: from [172.27.51.1] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 4BA78120F12; Sun, 18 Jan 2009 22:17:49 +0100 (CET) Message-ID: <49739C7C.10700@fsn.hu> Date: Sun, 18 Jan 2009 22:17:48 +0100 From: Attila Nagy User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Gavin Atkinson References: <496B115F.1000105@fsn.hu> <4970BB63.7030601@andric.com> <4970E8C0.1080005@FreeBSD.org> <49720DFE.3080808@fsn.hu> <20090118164930.R24894@ury.york.ac.uk> In-Reply-To: <20090118164930.R24894@ury.york.ac.uk> X-Stationery: 0.4.8.12 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (people.fsn.hu [0.0.0.0]); Sun, 18 Jan 2009 22:17:49 +0100 (CET) Cc: Maxim Sobolev , Dimitry Andric , freebsd-current@FreeBSD.org Subject: Re: FreeBSD panics with 64GiB of RAM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2009 13:31:52 -0000 Gavin Atkinson wrote: > On Sat, 17 Jan 2009, Attila Nagy wrote: > >> Hello, >> >> I've already tried something similar. The effect of the patch is this: >> http://people.fsn.hu/~bra/freebsd/20090107-freebsd-x4540/Screenshot-70.png >> >> >> BTW, this: >> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200812/8.0-CURRENT-200812-amd64-bootonly.iso >> >> boots up fine (to sysinstall). >> I haven't installed FreeBSD for years (I'm using netboot), is this i386? >> That could explain the situation. > > I'm confused. That link is a snapshot of amd64 -CURRENT from > December. The first email in this thread said you were trying -CURRENT > anmd64 and it wasn't working. > > So, which ones work and which don't? Are we looking at a regression > since December or has this been fixed between whatever image you first > tested and the December snapshot? The screenshots were made with an up to date (at that point of course) 8-CURRENT. But I've tried to boot with the snapshot ISO, which boots fine. Summary: - the original problem: with a fresh pxeloader, the machine halts at this point: http://people.fsn.hu/~bra/freebsd/20090107-freebsd-x4540/Screenshot-6.png - 8-CURRENT, booting with an older pxeloader panics with this: http://people.fsn.hu/~bra/freebsd/20090107-freebsd-x4540/Screenshot-55.png - the 640kB patch panics with this (8-CURRENT, older pxeloader): http://people.fsn.hu/~bra/freebsd/20090107-freebsd-x4540/Screenshot-70.png - with safe mode, I get this (8-CURRENT, older pxeloader, apparently no NICs recognized): http://people.fsn.hu/~bra/freebsd/20090107-freebsd-x4540/Screenshot-78-safemode.png - the December snapshot ISO with CD-ROM redirection boots fine, and it seems the SMAP is OK too: http://people.fsn.hu/~bra/freebsd/20090107-freebsd-x4540/Screenshot-78-fbsd8-amd64-livefs.png According to these, I think my problem is the pxeloader's inability to boot on this machine. An older one can't boot because of the memory-related difference, a newer one can not boot because of another changes, happening in-between. Somebody please help. :) I don't know if there is a version, which can get to the loader prompt AND initialize what need to be initialized correctly to overcome the SMAP-panic.