Comment 40 for bug 1318551

Revision history for this message
Rafael David Tinoco (rafaeldtinoco) wrote :

Maxim,

Good to know you are able to reproduce this behaviour and that you found a workaround. When you say "noautogroup" fixed the "problem".. was you problem kernel panics due to NMIs ? Could you share stack trace and/or kernel panic output so I can take a look ? Are you using Intel 26xx v2 CPU series ? Do you mind providing me a sosreport ? Can you check if this behaviour happens with 3.16 and/or 3.19 kernel also ?

Thank you

Rafael