[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843

To: Roger Pau Monné <roger.pau@xxxxxxxxxx>
From: Manuel Bouyer <bouyer@xxxxxxxxxxxxxxx>
Date: Fri, 13 Nov 2020 17:00:31 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 13 Nov 2020 16:00:46 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Fri, Nov 13, 2020 at 04:14:28PM +0100, Manuel Bouyer wrote:
> I can try a kernel without this driver, to see if other devices reports
> interrupt.

This didn't change anything, I don't get more interrupts with this driver
commented out.

-- 
Manuel Bouyer <bouyer@xxxxxxxxxxxxxxx>
     NetBSD: 26 ans d'experience feront toujours la difference
--

References:
- dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
  - From: Manuel Bouyer
- Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
  - From: Roger Pau Monné
- Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
  - From: Manuel Bouyer
- Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
  - From: Roger Pau Monné
- Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
  - From: Manuel Bouyer
- Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
  - From: Roger Pau Monné
- Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
  - From: Manuel Bouyer

Prev by Date: [linux-5.4 test] 156722: tolerable FAIL - PUSHED
Next by Date: Re: [PATCH V2 20/23] xen/ioreq: Make x86's send_invalidate_req() common
Previous by thread: Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
Next by thread: Re: dom0 PVH: 'entry->arch.pirq != INVALID_PIRQ' failed at vmsi.c:843
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.