From owner-freebsd-emulation@FreeBSD.ORG Fri Mar 27 13:17:32 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C492F106567A for ; Fri, 27 Mar 2009 13:17:32 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id CFDA88FC1A for ; Fri, 27 Mar 2009 13:17:31 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA24628; Fri, 27 Mar 2009 15:17:30 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <49CCD1E9.2060307@icyb.net.ua> Date: Fri, 27 Mar 2009 15:17:29 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090323) MIME-Version: 1.0 To: Chagin Dmitry References: <49CCBE43.5080309@icyb.net.ua> <20090327125852.GA6042@dchagin.static.corbina.ru> In-Reply-To: <20090327125852.GA6042@dchagin.static.corbina.ru> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-emulation@freebsd.org, Juergen Lock Subject: Re: qemu+kqemu: hard lockup with windows guest (32-bit on 64-bit) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2009 13:17:33 -0000 on 27/03/2009 14:58 Chagin Dmitry said the following: > On Fri, Mar 27, 2009 at 01:53:39PM +0200, Andriy Gapon wrote: >> System: >> stable/7 amd64 r190321 >> qemu-0.10.0_1 >> kqemu-kmod-devel-1.4.0.p1_1 >> >> I experience rare complete system lockups while running windows (98, win2k) guests >> with kqemu enabled. The guests are obviously 32-bit. >> I can't provide any diagnostics because it's a total freeze and there is no useful >> info after rebooting. >> > > SW_WATCHDOG can help you with debugging of similar bugs. It's an interesting idea. Now that you mentioned it I realized something else - I have a hardware watchdog and it is tested to work, but this time it didn't fire. So either watchdogd process was able to keep running or even chipset for so screwed so badly that it could not reset system. I have hard time believing in the second case, but the first one is also under suspicion - system didn't respond to any input (even power button press), it couldn't be pinged, etc. -- Andriy Gapon