Ubuntu
linux package

  1. Bug #1684054
  2. Comment #10

Comment 10 for bug 1684054

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2017-07-27 18:33 EDT-------
I just opened another BZ 157097 for the same issue. I was referred to this bug and I see that it addresses the same issue I was debugging. But we need the upstream commit be5c5e843c4afa1c8397cb740b6032bd4142f32d pulled into Xenial 16.04.3 HWE v4.10 kernel also.

Bad commit 2337d207288f163e10bd8d4d7eeb0c1c75046a0c is included in 16.04.3 HWE v4.10 kernel, so we need the fixing upstream commit in Xenial (16.04.3) also if possible. I know we are cutting close to 16.04.3 release date but this is a regression, so it would be good to have the fixing commit if possible.