Comment 28 for bug 1178707

Oh, right, I forgot that the version string came later. But since the symptom is distributed over such a variety of availability zones and even different instance types, it seems rather unlikely to be related to something on the host.

Unfortunately the kernel messages that are seen only tell us something failed to release/invalidate a page in the past and the stacks point to the process that stumbles over this when trying to use that page. So probably the only way to shed some light into this is to guess what may be different (configuration/usage). So first, is there anything different in resources compared to a standard instance?

The other thing that I thought of: if services running there are somewhat independent, maybe one could stop some on affected instances and see whether the problem remains or not.