Closing this bug with Won't fix as this kernel / release is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on
a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You
Hi,
We just completed an upgrade to precise across our instances and it
looks like the issue is still persisting on kernel 3.2.0-61-virtual.
Only have seen this on Amazon's m1.large instances so far. I've attached
a new stack trace
** Attachment added: precise_crash.txt
I am sorry, I unfortunately got distracted by trying to finish some feature for
the next release. And I must admit right now I have no good idea how to
proceed. The pages that got dumped at least to me show no pattern that points
to a certain process. You might be in a better position there
3 matches
Mail list logo
