[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Random guest crashes since 5c34d002dcc7 ("virtio_pci: use shared interrupts for virtqueues")
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]