Hi again, I now tested various upstream kernels and was able to reproduce the issue with upstream v3.16, but *not* with upstream v3.15 or v3.14.
I will try some more times and then report this upstream. It seems to me that the issue is introduced by a patch that Debian already shipped with v3.14, but that only landed upstream two releases later. Is there a good way to use this information to narrow down which patch it could have been? Kind regards, Ralf -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
