From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: Xen-unstable: xen panic RIP: dpci_softirq
Date: Fri, 14 Nov 2014 12:05:28 -0500 [thread overview]
Message-ID: <20141114170528.GC8198@laptop.dumpdata.com> (raw)
In-Reply-To: <1393541150.20141114175923@eikelenboom.it>
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!
next prev parent reply other threads:[~2014-11-14 17:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 13:11 Xen-unstable: xen panic RIP: dpci_softirq Sander Eikelenboom
2014-11-14 13:32 ` Andrew Cooper
2014-11-14 13:37 ` Andrew Cooper
2014-11-14 13:57 ` Jan Beulich
2014-11-14 14:34 ` Sander Eikelenboom
2014-11-14 15:09 ` Jan Beulich
2014-11-14 15:20 ` Sander Eikelenboom
2014-11-14 15:43 ` Jan Beulich
2014-11-14 16:59 ` Sander Eikelenboom
2014-11-14 17:05 ` Konrad Rzeszutek Wilk [this message]
2014-11-14 19:56 ` Sander Eikelenboom
2014-11-14 20:25 ` Konrad Rzeszutek Wilk
2014-11-14 22:09 ` Sander Eikelenboom
2014-11-17 16:34 ` Konrad Rzeszutek Wilk
2014-11-17 17:04 ` Sander Eikelenboom
2014-11-17 20:43 ` Konrad Rzeszutek Wilk
2014-11-17 22:40 ` Sander Eikelenboom
2014-11-18 8:28 ` Jan Beulich
[not found] ` <20141118024927.GA32256@andromeda.dapyr.net>
2014-11-18 11:07 ` Sander Eikelenboom
2014-11-18 15:09 ` Sander Eikelenboom
2014-11-18 16:06 ` Sander Eikelenboom
2014-11-18 16:16 ` Konrad Rzeszutek Wilk
2014-11-18 17:03 ` Sander Eikelenboom
2014-11-18 17:20 ` Jan Beulich
2014-11-18 20:34 ` Konrad Rzeszutek Wilk
2014-11-18 20:56 ` Konrad Rzeszutek Wilk
2014-11-18 22:12 ` Sander Eikelenboom
2014-11-19 1:55 ` Konrad Rzeszutek Wilk
2014-11-19 11:16 ` Sander Eikelenboom
2014-11-19 15:04 ` Konrad Rzeszutek Wilk
2014-11-19 17:27 ` Sander Eikelenboom
2014-11-17 18:01 ` Sander Eikelenboom
2014-11-18 9:30 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141114170528.GC8198@laptop.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.