Alright, I am officially convinced that the aforementioned commit does indeed fix this bug. During the past month and a half, I made sure that I was always running a kernel that included that patch, and I have not seen this bug in that time.
For the record, the patch was released in longterm kernel v3.7.3 as commit
41c8765e911cf54ad0c71bf3a1642b918af937e8
and in Ubuntu's extended longterm kernel v3.5.7.3 as commit
13938a31f36fa72027928eddb159327ab5568a46
Alright, I am officially convinced that the aforementioned commit does indeed fix this bug. During the past month and a half, I made sure that I was always running a kernel that included that patch, and I have not seen this bug in that time.
For the record, the patch was released in longterm kernel v3.7.3 as commit 54ad0c71bf3a164 2b918af937e8 72027928eddb159 327ab5568a46
41c8765e911cf
and in Ubuntu's extended longterm kernel v3.5.7.3 as commit
13938a31f36fa
Thanks!