Hi, On 08/02/2017 11:58 PM, Christian Seiler wrote: > - first of all I'll try to upgrade qemu and then reboot > the entire system before restarting the VM (to make sure > it's not some caching issue you mentioned)
Rebooting after upgrading qemu doesn't change anything. > - recompile both 1:2.8+dfsg-6 and 1:2.8+dfsg-6+deb9u1 > in a clean Stretch build environment and see if I can > reproduce the issue with self-built packages I've recompiled both 1:2.8+dfsg-6 and 1:2.8+dfsg-6+deb9u1 in a clean stretch sbuild environment (I can provide sbuild logs if necessary) and I get the same results: - the version without +deb9u1 works - the version with +deb9u1 has precisely this bug This is really weird. I even debdiff'd the source packages (to see if perhaps the uploaded package didn't correspond to the git repo, but the source package in the archive is fine) - and I really don't understand it: nothing in the debdiff touches any file that has to do with CPU features, as far as I can tell... Any ideas? My guess would be to selectively enable different patches in debian/patches/series and try to figure out which once of these actually causes the issue. (Could take me a while though.) Or do you have any better suggestions? Regards, Christian
