From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MYzFb-0004b6-OI for qemu-devel@nongnu.org; Thu, 06 Aug 2009 05:27:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MYzFW-0004ac-0J for qemu-devel@nongnu.org; Thu, 06 Aug 2009 05:27:06 -0400 Received: from [199.232.76.173] (port=60601 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MYzFV-0004aV-Ow for qemu-devel@nongnu.org; Thu, 06 Aug 2009 05:27:01 -0400 Received: from mail-yx0-f188.google.com ([209.85.210.188]:36807) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MYzFV-0005fi-H1 for qemu-devel@nongnu.org; Thu, 06 Aug 2009 05:27:01 -0400 Received: by yxe26 with SMTP id 26so878246yxe.4 for ; Thu, 06 Aug 2009 02:27:00 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Thu, 6 Aug 2009 11:26:59 +0200 Message-ID: Subject: Re: [Qemu-devel] sparc32 reset's regression From: Artyom Tarasenko Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel > The commit looks fine to me. Would this patch happen to fix the bug? Yes, this patch fixes the bug, thanks. It can be though that the bug is not directly related to the initial commit. There seems to be a race condition. Sometimes the bug didn't appear even without the fix if I put a lot of DPRINTFs in irq handling in sun4m.c and cpu-exec.c and turn the logging on. Unfortunately it's not always reproducible, so I can't tell yet which printf hides the problem.