From: Sander Eikelenboom <linux@eikelenboom.it>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen-unstable: xen panic RIP: dpci_softirq
Date: Fri, 14 Nov 2014 15:34:04 +0100 [thread overview]
Message-ID: <688701120.20141114153404@eikelenboom.it> (raw)
In-Reply-To: <546618620200007800047AD1@mail.emea.novell.com>
Friday, November 14, 2014, 2:57:38 PM, you wrote:
>>>> On 14.11.14 at 14:11, <linux@eikelenboom.it> wrote:
>> (XEN) [2014-11-14 13:00:06.810] ----[ Xen-4.5.0-rc x86_64 debug=y Not tainted ]----
>> (XEN) [2014-11-14 13:00:06.810] CPU: 3
>> (XEN) [2014-11-14 13:00:06.810] RIP: e008:[<ffff82d080148f14>] dpci_softirq+0x9c/0x231
>> (XEN) [2014-11-14 13:00:06.810] RFLAGS: 0000000000010283 CONTEXT: hypervisor
>> (XEN) [2014-11-14 13:00:06.811] rax: 0000000000100100 rbx: ffff830515c86d90 rcx: 0000000000000001
> This and ...
>> (XEN) [2014-11-14 13:00:06.811] Pagetable walk from 0000000000100108:
>> (XEN) [2014-11-14 13:00:06.811] L4[0x000] = 000000055d09a063 ffffffffffffffff
>> (XEN) [2014-11-14 13:00:06.811] L3[0x000] = 000000055d099063 ffffffffffffffff
>> (XEN) [2014-11-14 13:00:06.811] L2[0x000] = 000000055d098063 ffffffffffffffff
> ... this suggest it hit a poisoned list entry, due to
> #define LIST_POISON1 ((void *) 0x00100100)
> But without you helping out with associating the crash location with
> a source line (or allowing us to do so by making xen-syms available
> somewhere) this is going to remain guesswork.
> Jan
Hi Jan,
# addr2line -e ./xen-syms ffff82d080148f14
/usr/src/new/xen-unstable/xen/include/xen/list.h:175
Which turns out to be this assert:
/**
* list_del - deletes entry from list.
* @entry: the element to delete from the list.
* Note: list_empty on entry does not return true after this, the entry is
* in an undefined state.
*/
static inline void list_del(struct list_head *entry)
{
ASSERT(entry->next->prev == entry);
The other lines from the stacktrace point to:
# addr2line -e ./xen-syms ffff82d08012bd91
/usr/src/new/xen-unstable/xen/common/softirq.c:52
# addr2line -e ./xen-syms ffff82d08012bde9
/usr/src/new/xen-unstable/xen/common/softirq.c:66
# addr2line -e ./xen-syms ffff82d0801623d5
/usr/src/new/xen-unstable/xen/arch/x86/domain.c:119
# addr2line -e ./xen-syms ffff82d08012bd91
/usr/src/new/xen-unstable/xen/common/softirq.c:52
--
Sander
next prev parent reply other threads:[~2014-11-14 14:34 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 [this message]
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
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=688701120.20141114153404@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=JBeulich@suse.com \
--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.