> mind either, so to narrow this down does reverting the patch on> 2.6.38 also fix it? The revert isn't quite trivial due to changes> since then, so here's the patch I came up with:This patch does fix the problem.