From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:37973) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCc0f-0001iX-EG for qemu-devel@nongnu.org; Mon, 04 Mar 2013 15:29:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UCc0d-0005rF-3z for qemu-devel@nongnu.org; Mon, 04 Mar 2013 15:29:21 -0500 Received: from v220110690675601.yourvserver.net ([78.47.199.172]:41063) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UCc0c-0005qt-To for qemu-devel@nongnu.org; Mon, 04 Mar 2013 15:29:19 -0500 Message-ID: <51350411.5040103@weilnetz.de> Date: Mon, 04 Mar 2013 21:29:05 +0100 From: Stefan Weil MIME-Version: 1.0 References: <51293E4A.1040100@weilnetz.de> <20130304163731.GA23040@ohm.aurel32.net> In-Reply-To: <20130304163731.GA23040@ohm.aurel32.net> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] TCG assertion with qemu-system-mipsel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-15?Q?Aur=E9lien_Jarno?= Cc: qemu-devel , Richard Henderson Am 04.03.2013 17:37, schrieb Aur=E9lien Jarno: > Hi, > > On Sat, Feb 23, 2013 at 11:10:18PM +0100, Stefan Weil wrote: >> This assertion occured with latest git master: >> >> qemu-system-mipsel: /src/qemu/tcg/tcg-op.h:2589: >> tcg_gen_goto_tb: Assertion `(tcg_ctx.goto_tb_issue_mask & (1 << idx)) >> =3D=3D 0' failed. >> Aborted >> >> QEMU was built with --enable-debug and running a Debian MIPS Lenny (NF= S >> root). >> The assertion happened when running "apt-get update" in the guest. >> > Is it something reproductible or more or less random? Have you Cc:ed > Richard because it's related to the latest patches? > > On my side I am experiencing random segfaults in various guests (at > least PowerPC, MIPS, SH4 and ARM). I have found a way to bisect it, eve= n > if it is quite long (building Perl + the testsuite). Currently I know > that 1.3 is affected, while 1.2 is not. Hi, either it is fixed now or it is not reproducible: I tried it twice on Feb. 23 and got the same assertion in both cases, but now I tried it with the current git master and had no problem. Sorry that I cannot run more tests or a bisect - I'm currently rather busy with other work. Stefan