Control: reassign -1 src:linux 4.8.11-1 Control: severity -1 normal Control: tag -1 moreinfo On Sun, 2017-01-01 at 09:24 +0800, Liang Guo wrote: > Package: src:linux > Version: linux-image-4.8.0-2-amd64 > Severity: serious > > Hi, I found bpfcc-tools don't work on linux-image-4.8.0-2-amd64 and > linux-image-4.8.0-2-rt-amd64, for these kernels are signed kernel, I think > bpfcc-tools don't work on all signed kernels on x86_64 platform. bpfcc-tools > works on linux-image-4.8.0-2-amd64-unsigned, [...] The signed and unsigned kernels have exactly the same code. The only way they can differe in behaviour is on a system with Secure Boot enabled, where the signed one could be bootable (and then disable unsigned modules etc.) while the unsigned one does not. Given that you've been able to boot unsigned kernels, I don't believe signing has anything to do with this problem. You're not comparing the same versions of the signed and unsigned kernels, so perhaps there was a regression between 4.7 and 4.8 that was corrected between 4.8.11 and 4.8.15. Unfortunately we're not able to provide a signed image for 4.8.15-1 as it failed to build on one architecture. This should be corrected in the next version. Please report whether the next update to linux-signed-4.8.0-2-amd64 fixes this. Ben. -- Ben Hutchings All the simple programs have been written, and all the good names taken.
Attachment:
signature.asc
Description: This is a digitally signed message part