On Thu, Dec 22, 2016 at 11:27:25AM +0100, Michal Hocko wrote: > On Thu 22-12-16 11:10:29, Nils Holland wrote: > > > However, the log comes from machine #2 again today, as I'm > > unfortunately forced to try this via VPN from work to home today, so I > > have exactly one attempt per machine before it goes down and locks up > > (and I can only restart it later tonight). > > This is really surprising to me. Are you sure that you have sysrq > configured properly. At least sysrq+b shouldn't depend on any memory > allocations and should allow you to reboot immediately. A sysrq+m right > before the reboot might turn out being helpful as well. Well, the issue is that I could only do everything via ssh today and don't have any physical access to the machines. In fact, both seem to have suffered a genuine kernel panic, which is also visible in the last few lines of the log I provided today. So, basically, both machines are now sitting at my home in panic state and I'll only be able to resurrect them wheh I'm physically there again tonight. But that was expected; I could have waited with the test until I'm at home, which makes things easier, but I thought the sooner I can provide a log for you to look at, the better. ;-) Greetings Nils -- 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>