It happened really often to me with 2.6.28.x kernel, and now it doesn't happen at all (tried everything to reproduce, but I couldn't) with a 2.6.29-1 kernel, and also the 2.6.29 kernel is ok.
So we should just find the right patch that fixed it and apply to the current kernel.
It happened really often to me with 2.6.28.x kernel, and now it doesn't happen at all (tried everything to reproduce, but I couldn't) with a 2.6.29-1 kernel, and also the 2.6.29 kernel is ok.
So we should just find the right patch that fixed it and apply to the current kernel.