From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45903) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLUi8-0004AM-7s for qemu-devel@nongnu.org; Tue, 19 Jan 2016 06:44:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aLUi4-00012F-Vx for qemu-devel@nongnu.org; Tue, 19 Jan 2016 06:44:32 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48535) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aLUi4-00010w-RR for qemu-devel@nongnu.org; Tue, 19 Jan 2016 06:44:28 -0500 Message-ID: <1453203864.18326.47.camel@redhat.com> From: Gerd Hoffmann Date: Tue, 19 Jan 2016 12:44:24 +0100 In-Reply-To: References: <1452608259.29014.26.camel@redhat.com> <20160112143640.GF4841@noname.redhat.com> <20160112145655.GO17626@redhat.com> <1452701626.11179.3.camel@redhat.com> <1453109923.23289.4.camel@redhat.com> <1453125345.23289.37.camel@redhat.com> <1453187584.18326.9.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] usb-storage assertions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrey Korolyov Cc: Kevin Wolf , hdegoede@redhat.com, "qemu-devel@nongnu.org" Hi, > Probably not enough with driver subsystem to point even at the obvious > issue in the EHCI driver. I`d start with slowing down an emulated CPU > 10...100 times via its thread cg, leaving emulator code hanging with > enough CPU cycles and check if the issue is still here. If roots of > the crash or endless loop are timing-related, they either would change > appearance significanly or disappear completely (or vice versa, slow > an emulator thread). If you don`t have enough time for such blind > testing, I may check it in a next few days. Since I`ve seen interrupt > storm complaint on FreeBSD within same conditions, I strongly prefer > the idea of a race-driven behavior. Ha! That nailed it. /me was looking for a loop in the code, waiting for the device having finished reset or something like that. But it turned out to be a interrupt storm indeed. cheers, Gerd