This bug should have been fixed in 2.6.31-17.54. Can anyone confirm that they get this on a kernel later than that? Please make sure that you actually get this oops, and not another similar one.
This bug should have been fixed in 2.6.31-17.54. Can anyone confirm that they get this on a kernel later than that? Please make sure that you actually get this oops, and not another similar one.