Re: PROBLEM: 4.1.4 -- Kernel Panic on shutdown

[Laura Abbott <labbott@redhat.com>]

On 08/06/2015 05:08 PM, Ron Murray wrote:
> 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.
>
>

There was a similar report about a crash on reboot with 4.1.3[1]
where that reporter linked it to a bluetooth mouse. Hopefully this
isn't a red herring but it might be a similar report?

Thanks,
Laura

[1]https://bugzilla.redhat.com/show_bug.cgi?id=1248741

--
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>