From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Minjun Hong <nickeysgo@gmail.com>, xen-devel@lists.xen.org
Subject: Re: kernel panic with no call trace
Date: Wed, 6 Sep 2017 08:45:05 +0100 [thread overview]
Message-ID: <7a1c005f-a470-3a86-6b22-db128a2b7876@citrix.com> (raw)
In-Reply-To: <CAFX_q-Ebma3addzuOO7FJXoS73eTAyXGnRF_Cvj3m6bxG2xakA@mail.gmail.com>
On 06/09/2017 03:39, Minjun Hong wrote:
> Hello~~
> I'm struggling to resolve a kernel panic problem during developing
> scheduler code.
> But I have not made any progress since I can not get any meaningful
> information from the serial log.
> When the panic occurred, always there is no call trace and only panic
> notification like following:
>
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) cpu:20, vcpu:20 in csched_schedule(1891)
> (XEN) cpu:21, vcpu:21 in csched_schedule(1891)
> (XEN) cpumask_test_cpu(cpu, prv->in_cosched) in csched_schedule(1907)
> (XEN) cpumask_test_cpu(cpu, prv->in_cosched) in csched_schedule(1907)
> (XEN) cpumask_test_cpu(cpu, prv->in_cosched) in csched_schedule(1907)
> (XEN) cpumask_test_cpu(cpu, prv->in_cosched) in csched_schedule(1907)
> (XEN) FATAL PAGE FAULT
> (XEN) [error_code=0000]
> (XEN) Faulting linear address: ffff830078efcc98
> (XEN) ****************************************
> (XEN)
> (XEN) Reboot in five seconds...
>
> I'm using Xen-4.5.0 on my server having 2 Intel Xeon E5-2620 v4 cpus,
> 128 GB RAM(16 GB DDR4 * 4) and 1 TB HDD and, using Ubuntu 14.04 LTS.
>
> Is there any method to make the call trace show up or
> when there is no call trace, please tell me from where I should start
> to debug.
>
> Thanks in advance and I wait for your comments.
There is a call trace, but as you've clearly added printk()'s to the
scheduler, the calltrace will be getting lost in the spew of logging
beforehand.
From what you've printed, you've fallen over a bad pointer which isn't
present, although the offset into the directmap does look semi
plausible. Either way, you've got memory corruption of some kind.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-06 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 2:39 kernel panic with no call trace Minjun Hong
2017-09-06 7:45 ` Andrew Cooper [this message]
2017-09-07 16:29 ` Minjun Hong
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=7a1c005f-a470-3a86-6b22-db128a2b7876@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=nickeysgo@gmail.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).