From: Christoph Lameter <cl@linux.com>
To: Ron Murray <rjmx@rjmx.net>
Cc: Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: PROBLEM: 4.1.4 -- Kernel Panic on shutdown
Date: Wed, 5 Aug 2015 11:09:22 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.11.1508051105070.29534@east.gentwo.org> (raw)
In-Reply-To: <55C18D2E.4030009@rjmx.net>
> [1.] One line summary of the problem:
> 4.1.4 -- Kernel Panic on shutdown
This is a kfree of an object that was not allocated via the slab
allocators or was already freed. If you boot with the kernel command line
argument "slub_debug" then you could get some more information. Could also
be that memory was somehow corrupted.
The backtrace shows that this is a call occurring in the
scheduler.
CCing scheduler developers.
Call Trace:
<IRQ>
[<ffffffff81072189>] free_sched_group+0x29/0x30
[<ffffffff810721a0>] free_sched_group+rcu+0x10/0x20
[<ffffffff81099771>] rcu_process_callbacks+0x231/0x510
[<ffffffff81055cee>] __do_softirq+0xee/0x1e0
[<ffffffff81055ef5>] irq_exit+0x55/0x60
[<ffffffff810382f5>] smp_apic_timer_interrupt+0x45/0x60
[<ffffffff815e4f5b>] apic_timer_interrupt+0x6b/0x70
<EOI>
[<ffffffff81071b61>] ? finish_task_switch+0x61/0x100
[<ffffffff814ddc7d>] ? cpuidle_enter_state+0xad/0x170
[<ffffffff814ddc76>] ? cpuidle_enter_state+0xa6/0x170
[<ffffffff814ddd62>] cpuidle_enter+0x12/0x20
[<ffffffff810883a8>] cpu_startup_entry+0x268/0x2e0
[<ffffffff81036437>] start_secondary+0x167/0x170
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-08-05 16:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 4:12 Ron Murray
2015-08-05 16:09 ` Christoph Lameter [this message]
2015-08-05 16:24 ` Peter Zijlstra
2015-08-05 16:32 ` Christoph Lameter
2015-08-05 16:36 ` Peter Zijlstra
2015-08-05 17:01 ` Christoph Lameter
2015-08-06 1:44 ` Ron Murray
2015-08-06 3:31 ` Christoph Lameter
2015-08-07 0:08 ` Ron Murray
2015-08-07 14:55 ` Laura Abbott
2015-08-08 2:07 ` Ron Murray
2015-08-09 13:48 ` Laura Abbott
2015-08-10 1:30 ` Ron Murray
2015-08-05 18:38 ` Ron Murray
2015-08-05 19:06 ` Christoph Lameter
2015-08-05 19:27 ` Ron Murray
2015-08-05 19:34 ` Christoph Lameter
2015-08-05 21:30 ` Ron Murray
2015-08-05 16:57 ` Ron Murray
2015-08-05 17:06 ` Christoph Lameter
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=alpine.DEB.2.11.1508051105070.29534@east.gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=rjmx@rjmx.net \
/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