From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AmLUZ-0000cU-6t for qemu-devel@nongnu.org; Thu, 29 Jan 2004 18:22:35 -0500 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AmLU1-0000SM-P1 for qemu-devel@nongnu.org; Thu, 29 Jan 2004 18:22:32 -0500 Received: from [193.252.22.28] (helo=mwinf0302.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AmLTX-0000MI-Rh for qemu-devel@nongnu.org; Thu, 29 Jan 2004 18:21:31 -0500 Received: from free.fr (ATuileries-112-1-1-135.w80-11.abo.wanadoo.fr [80.11.167.135]) by mwinf0302.wanadoo.fr (SMTP Server) with ESMTP id 4EC18C000298 for ; Fri, 30 Jan 2004 00:21:30 +0100 (CET) Message-ID: <401995C7.1040404@free.fr> Date: Fri, 30 Jan 2004 00:22:47 +0100 From: Fabrice Bellard MIME-Version: 1.0 Subject: Re: [Qemu-devel] Knoppix results References: <200401282211.00224.kyle@silverbeach.net> <20040129141247.GA13654@cs.unibo.it> In-Reply-To: <20040129141247.GA13654@cs.unibo.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Renzo Davoli wrote: >>After a couple of tries, I got the disk image ready and partitioned. Whenever >>cfdisk hung QEMU, I had to kill the emulator and restart the process. I found >>that the changes that were successfully written to the disk image were good, >>so I was able to make forward progress. > > > I have installed a complete debian. > > I have had the very same problem: sometimes qemu freezes. > There is no apparent cause-effect relationship, qemu freezed at random > stages of the installation process any time the procedure was restarted. > I succeeded in installing the debian but after several attempts. > > It seems to be a timing fault on the simulated ide. > When it freezes, it stops into a low level infinite loop: neither > clicking on the window to grab the mouse nor ctrl-c on the calling > terminal produce effects. It seems there is a problem in TB invalidation during asynchronous interrupts (I have already seen random infinite loops in tb_reset_jump_recursive()). I have no idea of the exact cause of the problem. Fabrice.