Comment 14 for bug 1094173

On 02/08/2013 05:31 AM, Luis Henriques wrote:
> This bug is awaiting verification that the kernel for Quantal in
> -proposed solves the problem (3.5.0-24.37). Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-needed-quantal' to 'verification-done-quantal'.

OK, I have installed that kernel and I am running it now. Recall,
however, that this bug is not reliably reproducible and can take several
weeks to manifest,

That said, here's what we have now:

- Upstream believes that commit b4a98e57 fixes this bug.
- A backport of that commit was released in v3.7.3.
- After a mouth and a half, I can vouch for the fact that this bug is
  fixed as of v3.7.3. (I didn't check if it was present in v3.7.2,
  though.)
- A backport of the same commit was also released in v3.5.7.3, and I'm
  of the understanding this should have trickled down into this
  -proposed kernel.

Based on that, I'm around 95% confident that this kernel does indeed fix
this bug. If this isn't good enough, then I would need to run this
kernel for at least a month to empirically verify this.

> If verification is not done by one week from today, this fix will be
> dropped from the source code, and this bug will be closed.

I'm not sure what the standards are here -- I'm tempted to just declare
this "verified", but I don't know if that's justified. If it isn't,
then a week will not be enough time. Please advise.