Kevin Eilers wrote:
Hi!
Got any time to use
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
to determine which patch fixed it?
Yep, I'm currently working on it. But it will take some time.
I'm currently at the 2nd bisection, so expect my result in 3 or four days.
I tested a few more kernels:
2.6.15.7 is affected
2.6.16.20 is NOT affected.
2.6.16.1 seems not to be affected, but I didn't test it for long enough
to be 100% sure about this.
It seems, the bug diasspeared between 2.6.15.7 and 2.6.16.1.
Kevin
If you haven't looked then take a look at this thread
http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/1320
To sum up :
"O.K., what has 48 byte bursts? Hmmm. I think not CPU and memory.
Also this definitiely is not bit-corruption in the memory.
It is also not a single encrypted block, since 48 * 8 = 384,
which is more then the block size.
The number is odd. Could be hardware, could be software.
I think I cannot help much more on debugging this. Does any
developer know anything that is done in 48 Byte pices
in dm-crypt? "
The "48 byte pieces"-part might help.
---------------------------------------------------------------------
- http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx
