# 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). reassign 547503 linux-2.6 2.6.31~rc9 fixed 547503 linux-2.6/2.6.32~rc8-1~experimental.1 thanks
Hi kernel team, Here's a bug report on armel I forgot to pass on a few months ago: | $ git clone git://git.sugarlabs.org/sugar-jhbuild/mainline.git sugar-jhbuild | Initialized empty Git repository in /home/sascha.silbe/sugar-jhbuild/.git/ | remote: Counting objects: 4772, done. | remote: Compressing objects: 100% (2079/2079), done. | error: inflate: data stream error (invalid distance too far back) | fatal: pack has bad object at offset 616818: inflate returned -3 | fatal: index-pack failed | $ git clone git://git.gnome.org/jhbuild | Initialized empty Git repository in /home/sascha.silbe/jhbuild/.git/ | remote: Counting objects: 19804, done. | remote: Compressing objects: 100% (6374/6374), done. | fatal: pack has bad object at offset 487227: inflate returned -5 | fatal: index-pack failed | $ Upgrading the kernel fixed the problem. See http://bugs.debian.org/547503 for more details. I wrote: > 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. and I still stand by that. The bug is in your hands now. :) If you want to try to reproduce it, I'd suggest reverting that commit on an armel machine and watching the fireworks. If you don't want to reproduce it, I think it should be pretty safe to close. Regards, Jonathan -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
