From: Ron Murray <rjmx@rjmx.net>
To: Christoph Lameter <cl@linux.com>, Peter Zijlstra <peterz@infradead.org>
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>
Subject: Re: PROBLEM: 4.1.4 -- Kernel Panic on shutdown
Date: Wed, 5 Aug 2015 21:44:32 -0400 [thread overview]
Message-ID: <55C2BC00.8020302@rjmx.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1508051201280.29823@east.gentwo.org>
On 08/05/2015 01:01 PM, Christoph Lameter wrote:
> On Wed, 5 Aug 2015, Peter Zijlstra wrote:
>
>> On Wed, Aug 05, 2015 at 11:32:31AM -0500, Christoph Lameter wrote:
>>> On Wed, 5 Aug 2015, Peter Zijlstra wrote:
>>>
>>>> I'll go have a look; but the obvious question is, what's the last known
>>>> good kernel?
>>> 4.0.9 according to the original report.
>> Weird, there have been no changes to this area in v4.0..v4.1.
> Rerunning this with "slub_debug" may reveal additional info. Maybe there
> is some data corrupting going on.
>
OK, tried that (with no parameters though. Should I try some?). That got
me a crash with a blank screen and no panic report. The thing is clearly
touchy: small changes in memory positions make a difference. That's
probably why I didn't get a panic message until 4.1.4: the gods have to
all be looking in the right direction.
One thing I did notice on the original report, though:
> [ OK ] Deactivated swap /dev/dm-1.
> [ OK ] Stopped ACPI event daemon.
> [ OK ] Stopped LSB: Starts the GNUnet server at boot time..
> [ OK ] Stopped LSB: start Samba SMB/CIFS daemon (smbd).
> [ OK ] Stopped LSB: start Samba daemons for the AD DC.
> Stopping CUPS Scheduler...
> Stopping LSB: start Samba NetBIOS nameserver (nmbd)...
> [ OK ] Stopped CUPS Scheduler.
> [ OK ] Stopped (null).
> ------------[ cut here ]------------
Note the "Stopped (null)" before the "cut here" line. I wonder whether
that has anything to do with the problem, or is it a red herring?
.....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-06 1:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 4:12 PROBLEM: 4.1.4 -- Kernel Panic on shutdown 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 [this message]
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=55C2BC00.8020302@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 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.