From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BqPQc-0007bJ-Ps for qemu-devel@nongnu.org; Fri, 30 Jul 2004 00:55:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BqPQZ-0007b7-9E for qemu-devel@nongnu.org; Fri, 30 Jul 2004 00:55:34 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BqPQZ-0007b4-55 for qemu-devel@nongnu.org; Fri, 30 Jul 2004 00:55:31 -0400 Received: from [64.233.170.207] (helo=mproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BqPN5-0000dD-Nh for qemu-devel@nongnu.org; Fri, 30 Jul 2004 00:51:55 -0400 Received: by mproxy.gmail.com with SMTP id 74so64735rnk for ; Thu, 29 Jul 2004 21:51:55 -0700 (PDT) Message-ID: <2ad73a04072921514f824d5a@mail.gmail.com> Date: Fri, 30 Jul 2004 01:51:55 -0300 From: =?ISO-8859-1?Q?Andr=E9_Braga?= Subject: Re: [Qemu-devel] QEMU crashes host system In-Reply-To: <20040729221330.GA3537@chown.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20040729221330.GA3537@chown.ath.cx> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Maybe SDL is doing something wrong? Are you running the softmmu version of QEMU? Or is it QEMU-fast? Ah, and check out the signature in the bottom of this message: I guess you'll love it! :D On Fri, 30 Jul 2004 00:13:30 +0200, Grigori Goronzy wrote: > Hi, > > on two of my boxes qemu reliably crashes the whole host system. It seems > to be independent of the used OS, it happens in FreeBSD 4.10 and 5.2.1 > as well as in Linux. Either this appears as a hard crash or the kernel > panics. > > Both machines are quite different from each other; the first has an AMD > Duron, the other is an older Pentium3-based machine. The only similarity > between them is that they both use a Via chipset and have an NVidia > graphics card. I don't think the hardware is at failure--both machines > work stably for everything I use them for, one of them even runs 24/7 > without problems. Still, I wanted to be sure and checked the RAM and > CPU using memtest86 and mprime. Even after long runtime, these tools did > not report any problems. > > So, what could it be? This is really driving me mad. I'm not really > asking for a "solution" as I already have given up on this, but merely > for people who have experienced similar problems. > > greg -- "Structure is nothing if it is all you've got. Skeletons spook people if they try to walk around on their own; I really wonder why XML does not" Erik Naggum