From owner-freebsd-current@FreeBSD.ORG Sat Feb 16 19:10:39 2008 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 245DD16A419 for ; Sat, 16 Feb 2008 19:10:39 +0000 (UTC) (envelope-from mfl-commissioner@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) by mx1.freebsd.org (Postfix) with ESMTP id E8A0F13C457 for ; Sat, 16 Feb 2008 19:10:38 +0000 (UTC) (envelope-from mfl-commissioner@marino.st) Received: from [192.168.0.11] (ram31-1-82-234-78-29.fbx.proxad.net [82.234.78.29]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id A6C184356E; Sat, 16 Feb 2008 13:10:37 -0600 (CST) Message-ID: <47B7352B.1040302@marino.st> Date: Sat, 16 Feb 2008 20:10:35 +0100 From: MFL Commissioner User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Juergen Lock References: <43555.82.234.78.29.1203154742.squirrel@secure.synsport.net> <20080216175811.GA33393@saturn.kn-bremen.de> In-Reply-To: <20080216175811.GA33393@saturn.kn-bremen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 16 Feb 2008 20:12:17 +0000 Cc: freebsd-current@freebsd.org Subject: Re: 7.0 RC2 kernel panic with Kqemu/AMD64 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: Sat, 16 Feb 2008 19:10:39 -0000 Juergen, I would be happy to help debug this, although someone would have to give me step by step instructions on what to do exactly. This is a development machine that (roughly) mirrors a production setup, so I have maintain the SMP/AMD64 configuration. What I am still not quite clear on is this: Is this a Qemu problem or FreeBSD kernel problem? Anyway, I'll do what you ask to provide you with my backtraces, but I doubt that I will be able to interpret the results. John Juergen Lock wrote: > On Sat, Feb 16, 2008 at 03:39:02AM -0600, John Marino wrote: > > Looks like you are running amd64 SMP, it is a known problem that kqemu > doesn't really work in that case (see pkg-message of the qemu port); > the exact cause of this is still unknown - the backtraces I got are rather > weird and not really helpful, see this thread: > http://lists.freebsd.org/pipermail/freebsd-emulation/2007-November/004182.html > and there also is: > http://www.freebsd.org/cgi/query-pr.cgi?pr=113430 > If you or anyone else wants to help debug this you are very welcome of > course (it was suggested this might be a cache coherency issue, so maybe > your backtraces will look different since you're on an AMD CPU - mine is > Intel), otherwise your best bet probably is to use an UP kernel, or an > i386 install, interestingly there kqemu works also with SMP. (well or > disable kqemu of course.) > > Oh, another reason for my weird backtraces might be the minidump race, > and if I read the commitlogs right it is not actually fixed (I obtained > my dumps before it was discovered), the patches only made sure not to > write over the end of swap. So maybe I should try again with minidumps > disabled (if thats possible), one of these days... > > Sorry, > Juergen >