I ran through a suspend/resume now as well and that did immediately trigger the bug. Afterwards I had this really nasty error in the dmesg saying something about "corruption on low memory". There is even two kernel callstacks in my dmesg it seems.
I ran through a suspend/resume now as well and that did immediately trigger the bug. Afterwards I had this really nasty error in the dmesg saying something about "corruption on low memory". There is even two kernel callstacks in my dmesg it seems.