It's an IBM x440 that is not recognised by that check. Later in the log,we see

IBM eserver xSeries 440 detected: force use of acpi=ht

> And is it expected that ZONE_NORMAL only has 384MB? That seems awfully low> for a 64GB x86 machine. Could be that we went oom because we chose to> allocate really big hash tables, based on the total amount of memory?>

The log reports 392MB LOWMEM available. As it is 32 bit machine, it startedwith about 896MB but consumes much of it with mem_maps. The log showscalculate_numa_remap_pages() reporting

That is 400MB gone already which is mapped to lowmem. A little later in thelog, it says

min_low_pfn = 1140, max_low_pfn = 100352, highstart_pfn = 100352

so about 4MB is missing from the beginning (probably the kernel image),so we're down to 396ish. Not sure where the last 4MB is exactly but youget the idea.

While it is possible we are going OOM due to the size of lowmem, it'sdoubtful to be the only cause.http://test.kernel.org/functional/index.html shows that elm3b67 (themachine in question) has passed loads of tests in the past.