Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753640AbdDDNiL (ORCPT ); Tue, 4 Apr 2017 09:38:11 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38690 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752518AbdDDNiJ (ORCPT ); Tue, 4 Apr 2017 09:38:09 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 58A0B7EBBC Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=mst@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 58A0B7EBBC Date: Tue, 4 Apr 2017 16:38:03 +0300 From: "Michael S. Tsirkin" To: Mike Galbraith Cc: Christoph Hellwig , Thorsten Leemhuis , virtio-dev@lists.oasis-open.org, Linux Kernel Mailing List , rjones@redhat.com Subject: Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues") Message-ID: <20170404163725-mutt-send-email-mst@kernel.org> References: <1490843414.4167.11.camel@gmx.de> <1490858435.4696.25.camel@gmx.de> <20170331041959-mutt-send-email-mst@kernel.org> <20170331032231.GA2471@redhat.com> <20170331082049.GA4485@lst.de> <20170331194416-mutt-send-email-mst@kernel.org> <20170403141823.GA24747@lst.de> <1491242192.5638.111.camel@gmx.de> <20170403210931-mutt-send-email-mst@kernel.org> <1491278572.5198.28.camel@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1491278572.5198.28.camel@gmx.de> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Tue, 04 Apr 2017 13:38:09 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1487 Lines: 36 On Tue, Apr 04, 2017 at 06:02:52AM +0200, Mike Galbraith wrote: > On Mon, 2017-04-03 at 21:11 +0300, Michael S. Tsirkin wrote: > > On Mon, Apr 03, 2017 at 07:56:32PM +0200, Mike Galbraith wrote: > > > On Mon, 2017-04-03 at 16:18 +0200, Christoph Hellwig wrote: > > > > Mike, > > > > > > > > can you try the patch below? > > > > > > No more spinning kworker woes, but I still have a warning on hibernate, > > > threadirqs invariant. I'm also seeing intermittent post hibernate hang > > > funnies in virgin source +- this patch, and without threadirqs. > > > > > > [ 110.223953] WARNING: CPU: 5 PID: 452 at drivers/pci/msi.c:1261 pci_irq_vector+0xb1/0xe0 > > > > > > > > -Mike > > > > I just sent a patch fixing that. > > However I think we want to print a message when MSI fails to work so we > > know guest is falling back on legacy interrupts. > > The warning persists. > > [ 137.656423] WARNING: CPU: 1 PID: 535 at drivers/pci/msi.c:1261 pci_irq_vector+0xb1/0xe0 Can you post the rest of the backtrace? Is it still in the console? > WRT the post hibernate hang business, that is apparently not part of > the 4.11 woes (at least not solely), as 4.10.8 did not survive a 10 > hibernate cycle loop. RT is better at reproducing trouble (shrug, it > frequently is), but it matters not whether I'm running 4.10, master or > master-rt, they will all hang. > > WRT gripe, I wedged virtio_pci-fix-msix-vector-tracking-on-cleanup in > on top, but it wasn't impressed. > > -Mike