From owner-freebsd-current@FreeBSD.ORG Fri Sep 2 22:17:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA09516A41F; Fri, 2 Sep 2005 22:17:10 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 603D243D48; Fri, 2 Sep 2005 22:17:10 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 0020117348E; Sat, 3 Sep 2005 00:17:08 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 15F3E4080; Sat, 3 Sep 2005 00:17:25 +0200 (CEST) Date: Sat, 3 Sep 2005 00:17:24 +0200 From: Jeremie Le Hen To: Edwin Brown Message-ID: <20050902221724.GC659@obiwan.tataz.chchile.org> References: <8b6eae9605090106151a81174d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8b6eae9605090106151a81174d@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD6.0 and VMWare 5.0.. No go 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: Fri, 02 Sep 2005 22:17:10 -0000 Hi Edwin, [ Please either post on -stable@ or -current@, not both. In this case you should have post on -current@ only, since 6.0 isn't stable yet. ] > This morning I tried to install FreeBSD6.0 under VMWare 5. I got > the following message when it was extracting the base into \ > directory: > > Panic: duplicate free of item 0xc1c5a210 from zone 0xc143f000(g_bio) > > cpuid=0 > KDB: enter: panic > [thread pid 3 tid 100034 ] > stopped at kdb_enter+0x2b: nop > db> > > Is this a known issue? Don't know if it's a known issue, but can you use the "trace" DDB command and post the output here please, this will greatly help debugging for kernel hackers. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >