From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) by kanga.kvack.org (Postfix) with ESMTP id D28516B0254 for ; Thu, 6 Aug 2015 20:09:00 -0400 (EDT) Received: by igbij6 with SMTP id ij6so21663280igb.1 for ; Thu, 06 Aug 2015 17:09:00 -0700 (PDT) Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net. [2001:558:fe21:29:69:252:207:35]) by mx.google.com with ESMTPS id h16si1007901igt.23.2015.08.06.17.08.59 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Thu, 06 Aug 2015 17:08:59 -0700 (PDT) Subject: Re: PROBLEM: 4.1.4 -- Kernel Panic on shutdown References: <55C18D2E.4030009@rjmx.net> <20150805162436.GD25159@twins.programming.kicks-ass.net> <20150805163609.GE25159@twins.programming.kicks-ass.net> <55C2BC00.8020302@rjmx.net> From: Ron Murray Message-ID: <55C3F70E.2050202@rjmx.net> Date: Thu, 6 Aug 2015 20:08:46 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Lameter Cc: Peter Zijlstra , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , linux-mm@kvack.org, Ingo Molnar On 8/5/2015 23:31, Christoph Lameter wrote: > On Wed, 5 Aug 2015, Ron Murray wrote: > >> 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 > Hmmm... Crash early on? Could you attach a serial console and try > "earlyprintk" as an option as well? Might be difficult, since the box doesn't have a serial port. I think I have a USB serial port somewhere, but I don't know if it'll work. I will see what I can do. >> 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. > Subtle corruption issue. If slub_debug does not get it then other > debugging techniques may have to be used. > >>> [ 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? > Hmmm... Thats a message from user space. That's what I thought. I'll see if that message shows up in 4.0.9, and try to find out what it is. .....Ron -- 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: email@kvack.org