Ubuntu
linux package

  1. Xenial (16.04)
  2. Bug #1649821
  3. Comment #15

Comment 15 for bug 1649821

Revision history for this message
Ross Lagerwall (rosslagerwall) wrote :

> It seems like an obvious fix. Both call traces look identical. I can
> certainly produce a test kernel and get the reporter to produce some
> results.

Just to be clear, both call traces look identical because I wrote that patch to fix this particular issue, but unfortunately didn't get it backported to the stable releases.

I'm not sure why we haven't seen it on trusty. Perhaps some initialization ordering or kernel config options changed which exposed the race.