From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 6 13:40:13 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6725E1065676 for ; Fri, 6 Feb 2009 13:40:13 +0000 (UTC) (envelope-from c47g@gmx.at) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id ACBFE8FC1F for ; Fri, 6 Feb 2009 13:40:12 +0000 (UTC) (envelope-from c47g@gmx.at) Received: (qmail invoked by alias); 06 Feb 2009 13:13:31 -0000 Received: from cm56-152-15.liwest.at (EHLO bones) [86.56.152.15] by mail.gmx.net (mp011) with SMTP; 06 Feb 2009 14:13:31 +0100 X-Authenticated: #9978462 X-Provags-ID: V01U2FsdGVkX1/0UtZb1rX0Nra94gfpDP9jsAuD8TM8Ku7FLzy5jB cewt8XJ2nDFLLF From: Christian Gusenbauer To: freebsd-current@freebsd.org Date: Fri, 6 Feb 2009 14:13:52 +0100 User-Agent: KMail/1.9.10 References: <200902060925.n169PObG053288@lurza.secnetix.de> In-Reply-To: <200902060925.n169PObG053288@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902061413.53508.c47g@gmx.at> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.59 Cc: freebsd-hackers@freebsd.org, Oliver Fromme Subject: Re: CFT: Graphics support for /boot/loader X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2009 13:40:14 -0000 Hi Oliver! On Friday 06 February 2009, Oliver Fromme wrote: > Danny Braniss wrote: > > just tried it via pxe: > > > > panic: free: guard1 @ 0x7f3a4aec from /usr/src/lib/libstand/close.c:79 > > > > what changes are needed in pxeboot? > > The panic message means that the heap memory was corruped. > It could be caused by a buffer overflow or similar. > I'll try to look into it. I got this some years ago when I played with FreeBSD 6.1. It has something to do with reading/parsing the loader.conf file. Inserting some dummy lines (comments etc.) into loader.conf solves it (at least that's a workaround). As I've never seen it again since 6.1 I thought it has already been fixed :-(. Christian. > > When does that message appear? Could you provide a screen > shot? > > Best regards > Oliver