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? > 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. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>