From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Xen-unstable: xen panic RIP:   dpci_softirq
Date: Fri, 14 Nov 2014 12:05:28 -0500
Message-ID: <20141114170528.GC8198@laptop.dumpdata.com>
References: <193010671.20141114141112@eikelenboom.it>
	<546618620200007800047AD1@mail.emea.novell.com>
	<688701120.20141114153404@eikelenboom.it>
	<546629510200007800047BC3@mail.emea.novell.com>
	<1224708950.20141114162052@eikelenboom.it>
	<5466314E0200007800047C90@mail.emea.novell.com>
	<1393541150.20141114175923@eikelenboom.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <konrad.wilk@oracle.com>) id 1XpKJW-0005uK-7F
	for xen-devel@lists.xenproject.org; Fri, 14 Nov 2014 17:05:38 +0000
Content-Disposition: inline
In-Reply-To: <1393541150.20141114175923@eikelenboom.it>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xenproject.org>, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On Fri, Nov 14, 2014 at 05:59:23PM +0100, Sander Eikelenboom wrote:
> 
> Friday, November 14, 2014, 4:43:58 PM, you wrote:
> 
> >>>> On 14.11.14 at 16:20, <linux@eikelenboom.it> wrote:
> >> If it still helps i could try Andrews suggestion and try out with only 
> >> commit aeeea485 ..
> 
> > Yes, even if it's pretty certain it's the second of the commits, verifying
> > this would be helpful (or if the assumption is wrong, the pattern it's
> > dying with would change and hence perhaps provide further clues).
> 
> > Jan
> 
> 
> Ok with a revert of f6dd295 .. it survived cooking and eating a nice bowl of 
> pasta without a panic. So it would probably be indeed that specific commit.

Thank you for confirmation.

Could you give some specifics on the guests? As in what kind of devices you
are giving it - and more interestingly - what type of interrupt mechanism
do they use (/proc/interrupts along with 'dmesg' | grep <name of driver> should
give some ideas).

I wouldn't worry about the PV case as that bypasses the dpci codebase - just
on the HVM side.

Thanks again!