I've tested 2.6.37.6 and 3.0.0-rc2 and the bug is still reproducible
in both kernels. I'll try a 2.6.36 to see if it was present in it too.
Has this been tested on other hardware ? I'm still unsure if it's a
driver issue or if it's something else.
On Tue, Jun 14, 2011 at 9:31 AM, Antoine Reversat [off-list ref] wrote:
On Mon, Jun 13, 2011 at 7:43 PM, Andrew Morton
[off-list ref] wrote:
quoted
From which kernel version did we regress? Was 2.6.38 OK?
I can confirm this bug is present in 2.6.38.6
I'll try and see if I can reproduce it on a 2.6.37