Hi, Dann,
First of all, I think the bug title is misleading, as this issue happens on all kernels we tested (4.4.0-45..66, 4.8.0-x, 4.10.0-x etc).
To be fair, we haven't this exact bug (or at least I don't think we did) in practice, i.e. without running stress-ng, 4.4.0-x never ever crashed.
The VM use case turned out to be a different bug [1], triggered 100% by AAVMF + vhost.
Let me know if I can provide anything else.
I consider this particular bug minor (if we don't poke it with stress-ng, everything works well), compared to AAVMF + vhost [1].
Hi, Dann,
First of all, I think the bug title is misleading, as this issue happens on all kernels we tested (4.4.0-45..66, 4.8.0-x, 4.10.0-x etc).
To be fair, we haven't this exact bug (or at least I don't think we did) in practice, i.e. without running stress-ng, 4.4.0-x never ever crashed.
The VM use case turned out to be a different bug [1], triggered 100% by AAVMF + vhost.
Let me know if I can provide anything else.
I consider this particular bug minor (if we don't poke it with stress-ng, everything works well), compared to AAVMF + vhost [1].
Thanks,
Alex
[1] https:/ /bugs.launchpad .net/ubuntu/ +source/ edk2/+bug/ 1673564