On 05/17/2012 03:55 PM, Chris J Arges wrote:
> On 05/16/2012 01:42 PM, Ben Myers wrote:
>> Hey Chris,
>> On Thu, May 10, 2012 at 04:11:27PM +0000, Chris J Arges wrote:
>>>> Canonical attached them to the bug report that they filed yesterday:
>>> I am able to reproduce this bug with the instructions posted in this bug.
>>> Let me
>>> know what I can do to help.
>> The bug shows:
>> |This has been tested on the following kernels which all exhibit the same
>> |- 3.2.0-24 (Ubuntu Precise)
>> |- 3.4.0-rc4
>> |- 3.0.29
>> |- 3.1.10
>> |- 3.2.15
>> |- 3.3.2
>> Can you find an older kernel that isn't broken?
> Tested with Ubuntu Lucid 2.6.32-38-generic #38 (upstream 188.8.131.52), so
> far I am able to run the test for 5 hours, which on the same machine I
> have typically been able to reproduce in 2 hours. Will continue to run
> this, and on another system to verify.
Tested with Ubuntu Lucid 2.6.32-38-generic #38 (upstream 184.108.40.206).
This also fails, attaching the dmesg output as the backtrace looks
similar. Let me know if you'd like me to try any other versions.
The first test I did with lucid, it ran for 7 hours, and I stopped the
test. This morning I re-ran and it failed within 10 minutes. I guess I
got lucky the second time.
Description: Text document