From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kamk1-0007ko-3m for qemu-devel@nongnu.org; Wed, 03 Sep 2008 03:25:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kamjz-0007jL-NQ for qemu-devel@nongnu.org; Wed, 03 Sep 2008 03:25:24 -0400 Received: from [199.232.76.173] (port=45555 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kamjz-0007jG-JR for qemu-devel@nongnu.org; Wed, 03 Sep 2008 03:25:23 -0400 Received: from mx20.gnu.org ([199.232.41.8]:58239) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Kamjy-0005lQ-UU for qemu-devel@nongnu.org; Wed, 03 Sep 2008 03:25:23 -0400 Received: from ns6.enix.org ([193.19.211.1] helo=the-doors.enix.org) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Kamjr-0002ml-PJ for qemu-devel@nongnu.org; Wed, 03 Sep 2008 03:25:16 -0400 Date: Wed, 3 Sep 2008 09:25:11 +0200 From: Thomas Petazzoni Subject: Re: [Qemu-devel] MIPS kernel hanging when loaded through U-Boot in qemu Message-ID: <20080903092511.4918f2d6@surf> In-Reply-To: <20080828110042.1d27e8bb@surf> References: <20080828110042.1d27e8bb@surf> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/m1SqK_Fv+GFMG==57=e_Ppo"; protocol="application/pgp-signature"; micalg=PGP-SHA1 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 --Sig_/m1SqK_Fv+GFMG==57=e_Ppo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Le Thu, 28 Aug 2008 11:00:42 +0200, Thomas Petazzoni a =C3=A9crit : > It always hangs around the same place, but not exactly. Sometimes > after "PID hash table entries", sometimes after "Console: colour dummy > devices", sometimes one or two messages later, or before. It seems to hang when the first interrupt occurs, which might explain why it hangs at a random place, but always around the same point. I've added a small debug message in target-mips/helper.c:do_interrupt() to see what's happening: http://toulibre.org/~thomas/qemu/qemu-interrupt-log-patch With just the kernel (booted with -kernel), everything is fine, we see a couple of interrupt of type "interrupt", and the boot proceeds: http://toulibre.org/~thomas/qemu/qemu-interrupt-log-kernel-only But with U-Boot, once the first interrupt of type "interrupt" is fired, it is followed by an interrupt of type "syscall", and then of type "interrupt" again, and so on and so on, indefinitely: http://toulibre.org/~thomas/qemu/qemu-interrupt-log-with-u-boot As I'm not a MIPS expert, I don't know what's happening here. Is it a bug in U-Boot that leaves an incorrect CPU state ? Is it a Qemu emulation problem ? Thanks, Thomas --=20 Thomas Petazzoni, thomas.petazzoni@enix.org, http://thomas.enix.org Jabber, thomas.petazzoni@jabber.dk Toulibre, http://www.toulibre.org - APRIL, http://www.april.org Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E 1624 F653 CB30 98D3 F7A7 --Sig_/m1SqK_Fv+GFMG==57=e_Ppo Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIvjvX9lPLMJjT96cRAihUAJ0f43lWuvOpmVs2iIkdnlLX4JYI7QCeKU9H CPXdtsEXrA5bTLqGIJVdSfE= =t+vm -----END PGP SIGNATURE----- --Sig_/m1SqK_Fv+GFMG==57=e_Ppo--