> I also built a 4.10 based test kernel(16.04.3). [snip]
Thanks.
> Can you test this kernel and see if it resolves this bug?
Yes, it does.
I have verified both the patched one (4.10.0-35.39~lp1721070), which passes,
and its original version (4.10.0-35.39), which fails; so the patches are OK.
Similarly to @breno-leitao, the main problem is resolved (and that's really good enough for now), and a few test-cases report failures, which can likely be resolved with some other apparently unrelated commits which we are digging, and would like to submit later on.
Hi @jsalisbury
> I also built a 4.10 based test kernel(16.04.3). [snip]
Thanks.
> Can you test this kernel and see if it resolves this bug?
Yes, it does.
I have verified both the patched one (4.10.0- 35.39~lp1721070 ), which passes,
and its original version (4.10.0-35.39), which fails; so the patches are OK.
Similarly to @breno-leitao, the main problem is resolved (and that's really good enough for now), and a few test-cases report failures, which can likely be resolved with some other apparently unrelated commits which we are digging, and would like to submit later on.
cheers,
Mauricio