In reply to comments #73 and #74, I believe my erlang issue to be identical to the java issue in this report because the kernel oops is identical. Do you have the same oops or a different one? Is there any benefit to filing this against erlang and postgresql now the underlying hypervisor issue has been found/fixed? In principle practically any package could provoke this oops.
Does anyone have a pointer to the corresponding Amazon issue?
In reply to comments #73 and #74, I believe my erlang issue to be identical to the java issue in this report because the kernel oops is identical. Do you have the same oops or a different one? Is there any benefit to filing this against erlang and postgresql now the underlying hypervisor issue has been found/fixed? In principle practically any package could provoke this oops.
Does anyone have a pointer to the corresponding Amazon issue?