On Mon, Jul 31, 2017 at 04:08:10PM +0200, Michal Hocko wrote: > On Mon 31-07-17 09:56:48, Liam R. Howlett wrote: > > * Michal Hocko <mhocko@xxxxxxxxxx> [170731 05:10]: > > > On Fri 28-07-17 21:56:38, Liam R. Howlett wrote: > > > > The case I raise is a correctly configured system which has a memory > > > > module failure. > > > > > > So you are concerned about MCEs due to failing memory modules? If yes > > > why do you care about hugetlb in particular? > > > > No, I am concerned about a failed memory module. The system will > > detect certain failures, mark the memory as bad and automatically > > reboot. Up on rebooting, that module will not be used. > > How do you detect/configure this? We do have HWPoison infrastructure > > > My focus on hugetlb is that it can stop the automatic recovery of the > > system. > > How? Let me try to explain the situation as I understand it. The customer has purchased a 128TB machine in order to run a database. They reserve 124TB of memory for use by the database cache. Everything works great. Then a 4TB memory module goes bad. The machine reboots itself in order to return to operation, now having only 124TB of memory and having 124TB of memory reserved. It OOMs during boot. The current output from our OOM machinery doesn't point the sysadmin at the kernel command line parameter as now being the problem. So they file a priority 1 problem ticket ... -- 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>
