Comment 7 for bug 2009594

Revision history for this message
Frode Nordahl (fnordahl) wrote :

This does indeed appear to be a serious issue, but it is unfortunately not a charm issue.

It appears to me to be an issue with the mlx5 driver in the kernel which is visible in this specific environment for yet to be uncovered reasons.