From owner-freebsd-current Sat Oct 12 16:37:43 2002 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 931) id B043F37B401; Sat, 12 Oct 2002 16:37:42 -0700 (PDT) Date: Sat, 12 Oct 2002 16:37:42 -0700 From: Juli Mallett To: Frode Nordahl Cc: current@FreeBSD.ORG Subject: Re: dmesg showing garbage Message-ID: <20021012163742.A31504@FreeBSD.org> References: <1034464124.624.2.camel@samwise.xu.nordahl.net> <20021012161159.A30348@FreeBSD.org> <1034465799.627.7.camel@samwise.xu.nordahl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1034465799.627.7.camel@samwise.xu.nordahl.net>; from frode@nordahl.net on Sun, Oct 13, 2002 at 01:36:38AM +0200 Organisation: The FreeBSD Project X-Alternate-Addresses: , , , , X-Towel: Yes X-LiveJournal: flata, jmallett X-Negacore: Yes 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 * De: Frode Nordahl [ Data: 2002-10-12 ] [ Subjecte: Re: dmesg showing garbage ] > Anyway, it could show that FreeBSD could do a better job initializing > memory on bootup? This is a job of the BIOS, and I wasn't trying to explain the garbage, merely why there's stuff from the previous boot. I didn't quote the bits asking why there was corruption. -- Juli Mallett | FreeBSD: The Power To Serve Will break world for fulltime employment. | finger jmallett@FreeBSD.org http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message