From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N8HvU-0007nQ-Gn for qemu-devel@nongnu.org; Wed, 11 Nov 2009 13:28:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N8HvP-0007gr-Js for qemu-devel@nongnu.org; Wed, 11 Nov 2009 13:28:16 -0500 Received: from [199.232.76.173] (port=36727 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N8HvP-0007gR-Bl for qemu-devel@nongnu.org; Wed, 11 Nov 2009 13:28:11 -0500 Received: from mx20.gnu.org ([199.232.41.8]:46310) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1N8HvO-0002yW-9G for qemu-devel@nongnu.org; Wed, 11 Nov 2009 13:28:10 -0500 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N8HvK-0007vz-91 for qemu-devel@nongnu.org; Wed, 11 Nov 2009 13:28:06 -0500 From: Paul Brook Subject: Re: [Qemu-devel] arm, mips and mipsel broken Date: Wed, 11 Nov 2009 18:28:03 +0000 References: <20091110205040.GF9052@hall.aurel32.net> <20091110213538.GG9052@hall.aurel32.net> In-Reply-To: <20091110213538.GG9052@hall.aurel32.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200911111828.03660.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Blue Swirl , Aurelien Jarno On Tuesday 10 November 2009, Aurelien Jarno wrote: > On Tue, Nov 10, 2009 at 11:19:40PM +0200, Blue Swirl wrote: > > On Tue, Nov 10, 2009 at 10:50 PM, Aurelien Jarno wrote: > > > Please note that at least qemu-system-arm, qemu-system-mips and > > > qemu-system-mipsel are broken by this commit: > > > > Given that none of the devices touched by the commit should be used by > > these targets, the breakage comes from just the single new call to > > qemu_system_reset in vl.c. This means that the reset functions for > > those boards and devices must be awfully buggy. > > I'll try to have a closer look at the problem tomorrow, if I can't find > the problem, it's what I'll commit. This is latent breakage introduced by 45a50b1. See commits 97fe84f5 (makes breakage obvious) and f2d7497 (fixed ARM). MIPS still needs fixing. Paul