Comment 4 for bug 1898091

Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :

Hi Chris,

Thanks for reporting this bug.

The faulting memory addresses alone are not sufficient to have an idea of what is going on.

Also, they might not necessarily indicate a memory problem, but incorrect code in whatever part of the kernel, targeting a memory address that is incorrectly calculated or no longer valid.

Could you please upload the crash dmesg files?
They should contain stack traces that provide more context about the faulty memory address.