Comment 10 for bug 1190295

A1an (alan-b) wrote :

I see and I'll try to flie the new report as soon as possible, even though I think it is the same cause as this one.

I've had a look at the kernel log and see that only two patches affected the md component between 2.6.32-46 (working kernel) and 2.6.32-47 (broken kernel, reported in this bug):

A notification to the author might help solve this even quicker.