From: Ron Murray <rjmx@rjmx.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Christoph Lameter <cl@linux.com>,
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" <linux-mm@kvack.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: PROBLEM: 4.1.4 -- Kernel Panic on shutdown
Date: Wed, 5 Aug 2015 14:38:57 -0400 [thread overview]
Message-ID: <81C750EC-F4D4-4890-894A-1D92E5CF3A31@rjmx.net> (raw)
In-Reply-To: <20150805162436.GD25159@twins.programming.kicks-ass.net>
> On Aug 5, 2015, at 12:24, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Wed, Aug 05, 2015 at 11:09:22AM -0500, Christoph Lameter wrote:
>>> [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.
>
> I'll go have a look; but the obvious question is, what's the last known
> good kernel?
>
>>
>>
4.0.x series still work for me. I had wondered about a memory fault (on the idea that a small shift in memory position might hit the fault), but memtest86 turned up nothing.
I will try re-compiling to use the SLAB allocator and see if that helps.
.....Ron
--
Ron Murray <rjmx@rjmx.net>
PGP Fingerprint: 0ED0 C1D1 615C FCCE 7424 9B27 31D8 AED5 AF6D 0D4A
--
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 18:39 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
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 [this message]
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=81C750EC-F4D4-4890-894A-1D92E5CF3A31@rjmx.net \
--to=rjmx@rjmx.net \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--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 \
/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