From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IGxwm-0007iu-5B for qemu-devel@nongnu.org; Fri, 03 Aug 2007 10:16:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IGxwk-0007i9-Ji for qemu-devel@nongnu.org; Fri, 03 Aug 2007 10:16:07 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IGxwk-0007i5-Bz for qemu-devel@nongnu.org; Fri, 03 Aug 2007 10:16:06 -0400 Received: from hall.aurel32.net ([88.191.38.19]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IGxwk-0001Rf-22 for qemu-devel@nongnu.org; Fri, 03 Aug 2007 10:16:06 -0400 Received: from anguille.univ-lyon1.fr ([134.214.4.207]) by hall.aurel32.net with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1IGxwi-0004VG-6R for qemu-devel@nongnu.org; Fri, 03 Aug 2007 16:16:04 +0200 Message-ID: <46B3389E.8000803@aurel32.net> Date: Fri, 03 Aug 2007 16:15:58 +0200 From: Aurelien Jarno MIME-Version: 1.0 Subject: Re: [Qemu-devel] Sparc guest - SCSI References: <46B2EB20.4080501@bandsman.co.uk> <46B316FB.30001@aurel32.net> <56A2CC80-861E-41D5-8341-0889A374A383@web.de> In-Reply-To: <56A2CC80-861E-41D5-8341-0889A374A383@web.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit 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 Andreas Färber a écrit : > Am 03.08.2007 um 13:52 schrieb Aurelien Jarno: > >> The problem appears when one interrupt on the SCSI controller is >> triggered twice by the interrupt controller, the second interrupt >> disturb the driver. >> >> I have fixed one problem like that a few months ago in the CVS, so it >> happens less often, but there is still a problem somewhere. > > Do you know under which circumstances this happens? And is there any > way to avoid it? I suggest to read the description of the problem from last time: http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html I guess there is still one case when this can happen. The only solution I see to avoid that is to fix the bug (the problem doesn't occurs on real hardware, so the emulation is buggy). -- .''`. Aurelien Jarno | GPG: 1024D/F1BCDB73 : :' : Debian developer | Electrical Engineer `. `' aurel32@debian.org | aurelien@aurel32.net `- people.debian.org/~aurel32 | www.aurel32.net