Sascha Silbe wrote: > Confirmed, it still breaks with the old kernel > (2.6.31-rc9-flatty-ocf-1-00293-g53a104c), but works with the current > one (2.6.32-rc4-flatty-ocf-1-00488-g4b69b78).
Thanks! >> The only possibly relevant kernel change I could find was commit >> 5a3a29f (ARM: 5691/1: fix cache aliasing issues between kmap() and >> kmap_atomic() with highmem, commit 7929eb9 upstream) from 2.6.31.1. >> So though I also have my doubts, we _could_ be lucky. > > I'd prefer not to track this down to a specific commit as this is a > production server now, but can try if you convince me there's some > benefit. That's okay. I don't think you should bother. I am satisfied, because now it's clear (1) the problem was in the kernel, (2) the problem is actually fixed (not just a change in what the remote repos were serving, for example), and (3) there was at least one kernel change meant to address similar problems. It would be lovely to confirm on some other machine that reverting that patch introduces the errors, but even that does not seem necessary to me. > Can rule out my own patches, though, since they haven't changed > between the two kernels (only been rebased). Thanks for tracking this down. Pleased, Jonathan -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
