From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C1VoE-00082t-9t for qemu-devel@nongnu.org; Sun, 29 Aug 2004 15:57:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C1VoC-00082K-Cj for qemu-devel@nongnu.org; Sun, 29 Aug 2004 15:57:49 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C1VoC-000823-9Z for qemu-devel@nongnu.org; Sun, 29 Aug 2004 15:57:48 -0400 Received: from [151.189.21.46] (helo=mail-in-01.arcor-online.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1C1Vik-0007G2-Dn for qemu-devel@nongnu.org; Sun, 29 Aug 2004 15:52:10 -0400 Received: from hatatitla.NotaMusica.com (dsl-082-082-143-089.arcor-ip.net [82.82.143.89]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 2B7FD1A932 for ; Sun, 29 Aug 2004 21:52:08 +0200 (CEST) Received: from hatatitla.NotaMusica.com (jmartin@localhost [127.0.0.1]) by hatatitla.NotaMusica.com (8.12.3/8.12.3/Debian-6.6) with ESMTP id i7TJq7pr002319 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 29 Aug 2004 21:52:07 +0200 Received: from localhost (jmartin@localhost) by hatatitla.NotaMusica.com (8.12.3/8.12.3/Debian-6.6) with ESMTP id i7TJq746002314 for ; Sun, 29 Aug 2004 21:52:07 +0200 Date: Sun, 29 Aug 2004 21:52:07 +0200 (CEST) From: Johannes Martin Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [Qemu-devel] OS/2 lockups during bootup 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 Hi everybody, I'm having some trouble booting up OS/2 in qemu (CVS, Linux host). OS/2 frequently hangs during bootup when loading one of the following device drivers: IBM1FLPY.ADD IBM1S506.ADD IBMIDECD.FLT IBMDASD.DMD The lockup may occur randonmly in any of these drivers or not at all. When I reboot OS/2 or restart qemu a couple of times, I usually get past these drivers eventually. It takes patience though. I know that something has gone wrong when qemu starts using 99% of CPU time while loading these drivers. I assume the drivers are in some kind of loop waiting for some event to happen - I guess it's a timing problem and sometimes things don't happen in the right sequence. Any hints? Thanks Johannes