Bug#841419: linux-source-4.7: debian linux source package incompatible with default gcc6 in unstable?
Package: linux-source-4.7 Version: 4.7.8-1 Severity: important Dear Maintainer, this morning the update of my debian sid system brought me a "medium" upgrade for the linux source package. I therefore proceeded to (try to) rebuild it, via a standard "make oldconfig" using the previous (it's a minor revision, no big configuration change, so I did not expect problems with it). Unfortunately, compilation immediately complained about hardening that would not work because it's broken in the compiler, but still went on, just to stop immediately thereafter with an unrecoverable error: kernel/bounds.c:1:0: error: code model kernel does not support PIC mode A bit of googling showed that this is apparently due to the recent upgrade of the default gcc compiler in sid (6.2.0-7). Indeed, I verified that I cannot even recompile the previous debian kernel source version, the one I am currently running, and that compiled flawlessly not more that a week ago. I was able to get around the problem by forcing the use of gcc-5 instead of gcc-6 via the MAKEFLAGS="CC=gcc-5" environment variable. While I see that this problem cannot be really blamed on the debian linux source package, it still makes it at least hard to use on a sid installation with the default debian compiler, and should be fixed somewhere. Either by requesting a different compiler than the one that does not work and explaining how to use it instead of the default one, or by adding some workaround compiler options if possible/necessary. Or by filing a critical/important bug against the default compiler (I would say "fails to build the kernel" is critical enough for the default compiler...). Thanks in advance, bye Giacomo Mulas -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (401, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.5-jak (SMP w/4 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL set to it_IT.utf8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-source-4.7 depends on: ii binutils 2.27-9 ii xz-utils 5.2.2-1.2 Versions of packages linux-source-4.7 recommends: ii bc1.06.95-9+b2 ii gcc 4:6.1.1-1 ii libc6-dev [libc-dev] 2.24-5 ii make 4.1-9 Versions of packages linux-source-4.7 suggests: ii libncurses5-dev [ncurses-dev] 6.0+20160917-1 ii libqt4-dev 4:4.8.7+dfsg-9 ii pkg-config 0.29-4 ii pkgconf [pkg-config] 0.9.12-1 -- no debconf information -- debsums errors found: debsums: missing file /usr/src/linux-source-4.7.tar.xz (from linux-source-4.7 package)
Bug#841423: LVM: raid1 kernel module not loaded
Package: initramfs-tools Version: 0.125 Severity: normal Initially i thought to file this bug to lvm2 package but now i suspect it's more related with kernel modules dependencies and the manual_add_modules() hook of initramfs-tools. Suppose your system has lvm2 installed but not mdadm. Now search for the raid modules installed in the initramfs image: lsinitramfs IMG | grep raid You will notice that there are various raid modules loaded but not raid1. LVM is a very flexible system that let's you convert your volume setup from linear to raidN and viceversa, with mounted filesystem. So if you, for example, try to you convert your single disk volume to a two disks raid1 volume, you will have an unbootable system, due to failure of volume activation caused by the missing raid1 module. The workaround it to add "raidi1" to /etc/initramfs-tools/modules and update the initramfs before rebooting. The issue is also described here: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1509717 Indeed it can be asked to the lvm2 maintainer to add "raid1" module to the initramfs hook. Currently /usr/share/initramfs-tools/hooks/lvm2 load these modules: dm_mod dm_snapshot dm_mirror dm_raid But since with the above modules, various raid modules get loaded as dependencies, i wonder why raid1 is not. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 19M Oct 20 13:26 /boot/initrd.img-4.6.0-1-amd64 -rw-r--r-- 1 root root 19M Oct 20 13:25 /boot/initrd.img-4.7.0-1-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/vg0-debian--root ro systemd.show_status=1 quiet -- resume RESUME=UUID=165d521e-0cc9-4bf4-bc12-a995e826a649 -- /proc/filesystems ext3 ext2 ext4 vfat -- lsmod Module Size Used by cpuid 16384 0 nls_ascii 16384 1 nls_cp437 20480 1 snd_hda_codec_realtek86016 1 snd_hda_codec_hdmi 45056 1 snd_hda_codec_generic69632 1 snd_hda_codec_realtek vfat 20480 1 fat69632 1 vfat amdkfd126976 1 efi_pstore 16384 0 kvm_amd73728 0 kvm 573440 1 kvm_amd irqbypass 16384 1 kvm efivars20480 1 efi_pstore snd_hda_intel 36864 0 radeon 1490944 1 snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel serio_raw 16384 0 pcspkr 16384 0 snd_hda_core 81920 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel evdev 24576 2 k10temp16384 0 ttm98304 1 radeon snd_hwdep 16384 1 snd_hda_codec nuvoton_cir24576 0 drm_kms_helper147456 1 radeon snd_pcm 110592 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core snd_timer 32768 1 snd_pcm drm 364544 4 ttm,drm_kms_helper,radeon sp5100_tco 16384 0 snd81920 8 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel sg 32768 0 soundcore 16384 1 snd i2c_piix4 24576 0 shpchp 36864 0 rc_core28672 1 nuvoton_cir i2c_algo_bit 16384 1 radeon button 16384 0 acpi_cpufreq 20480 0 tpm_tis20480 0 tpm45056 1 tpm_tis xt_tcpudp 16384 1 nf_conntrack_ipv4 20480 5 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 5 nf_conntrack 114688 2 xt_conntrack,nf_conntrack_ipv4 iptable_filter 16384 1 sch_fq_codel 20480 3 efivarfs 16384 1 ip_tables 24576 1 iptable_filter x_tables 36864 4 ip_tables,xt_tcpudp,xt_conntrack,iptable_filter autofs440960 2 ext4 589824 2 ecb16384 0 glue_helper16384 0 lrw16384 0 gf128mul 16384 1 lrw ablk_helper16384 0 cryptd 20480 1 ablk_helper aes_x86_64 20480 0 crc16 16384 1 ext4 jbd2 106496 1 ext4 mbcache16384 3 ext4 sr_mod 24576 0 cdrom 57344 1 sr_mod hid_generic16384 0 raid1 36864 2 usbhid 49152 0 hid 118784 2 hid_generic,usbhid dm_raid28672 2 raid456 106496 1 dm_raid async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 as
Bug#841423: LVM: raid1 kernel module not loaded
Control: reassign -1 dmsetup 2:1.02.133-1 On Thu, 2016-10-20 at 14:27 +0200, Cesare Leonardi wrote: > Package: initramfs-tools > Version: 0.125 > Severity: normal > > Initially i thought to file this bug to lvm2 package but now i suspect > it's more related with kernel modules dependencies and the > manual_add_modules() hook of initramfs-tools. > > Suppose your system has lvm2 installed but not mdadm. > Now search for the raid modules installed in the initramfs image: > lsinitramfs IMG | grep raid > You will notice that there are various raid modules loaded but not > raid1. > > LVM is a very flexible system that let's you convert your volume setup > from linear to raidN and viceversa, with mounted filesystem. > > So if you, for example, try to you convert your single disk volume to > a two disks raid1 volume, you will have an unbootable system, due to > failure of volume activation caused by the missing raid1 module. > > The workaround it to add "raidi1" to /etc/initramfs-tools/modules and > update the initramfs before rebooting. [...] OK, so there is a hidden module dependency: dm-raid depends on md-mod, which will request other md-RAID modules as needed. We can't discover that through static inspection of the modules or looking at sysfs. I think this ought to be handled in dmsetup's initramfs hook. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#841423: LVM: raid1 kernel module not loaded
Processing control commands: > reassign -1 dmsetup 2:1.02.133-1 Bug #841423 [initramfs-tools] LVM: raid1 kernel module not loaded Bug reassigned from package 'initramfs-tools' to 'dmsetup'. No longer marked as found in versions initramfs-tools/0.125. Ignoring request to alter fixed versions of bug #841423 to the same values previously set Bug #841423 [dmsetup] LVM: raid1 kernel module not loaded Marked as found in versions lvm2/2.02.164-1. -- 841423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#841420: --enable-default-pie breaks kernel builds
Processing control commands: > reassign -1 linux 4.7.8-1 Bug #841420 [gcc-6] --enable-default-pie breaks kernel builds Bug reassigned from package 'gcc-6' to 'linux'. No longer marked as found in versions gcc-6/6.2.0-7. Ignoring request to alter fixed versions of bug #841420 to the same values previously set Bug #841420 [linux] --enable-default-pie breaks kernel builds There is no source info for the package 'linux' at version '4.7.8-1' with architecture '' Unable to make a source version for version '4.7.8-1' Marked as found in versions 4.7.8-1. > severity -1 serious Bug #841420 [linux] --enable-default-pie breaks kernel builds Severity set to 'serious' from 'important' > tags -1 patch Bug #841420 [linux] --enable-default-pie breaks kernel builds Added tag(s) patch. -- 841420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841420: --enable-default-pie breaks kernel builds
Hello, with this version of gcc-6 I can't build vanilla kernels any more. It fails with even with CC_STACKPROTECTOR_STRONG disabled: scripts/kconfig/mconf Kconfig configuration written to .config *** End of the configuration. *** Execute 'make' to start the build or try 'make help'. ksrc@ei:~/build/kernels/linux-4.8.3$ make scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h CC kernel/bounds.s kernel/bounds.c:1:0: error: code model kernel does not support PIC mode /* Kbuild:45: recipe for target 'kernel/bounds.s' failed make[1]: *** [kernel/bounds.s] Error 1 Makefile:1015: recipe for target 'prepare0' failed make: *** [prepare0] Error 2 I think this is a major regression if you can't build vanilla and stable kernels any more. Regards, -- Wolfgang Walter Studentenwerk München Anstalt des öffentlichen Rechts
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 841368 linux 4.8.1-1 Bug #841368 [gcc-6] gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled Bug reassigned from package 'gcc-6' to 'linux'. No longer marked as found in versions gcc-6/6.2.0-7. Ignoring request to alter fixed versions of bug #841368 to the same values previously set Bug #841368 [linux] gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled There is no source info for the package 'linux' at version '4.8.1-1' with architecture '' Unable to make a source version for version '4.8.1-1' Marked as found in versions 4.8.1-1. > forcemerge 841420 841368 Bug #841420 [linux] --enable-default-pie breaks kernel builds Bug #841368 [linux] gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled Severity set to 'serious' from 'normal' There is no source info for the package 'linux' at version '4.7.8-1' with architecture '' Unable to make a source version for version '4.7.8-1' There is no source info for the package 'linux' at version '4.8.1-1' with architecture '' Unable to make a source version for version '4.8.1-1' Marked as found in versions 4.7.8-1. Added tag(s) patch. Bug #841420 [linux] --enable-default-pie breaks kernel builds There is no source info for the package 'linux' at version '4.7.8-1' with architecture '' Unable to make a source version for version '4.7.8-1' There is no source info for the package 'linux' at version '4.8.1-1' with architecture '' Unable to make a source version for version '4.8.1-1' Marked as found in versions 4.8.1-1. Merged 841368 841420 > thanks Stopping processing here. Please contact me if you need assistance. -- 841368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841368 841420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841420: --enable-default-pie breaks kernel builds
Concurring with Wolfgang; pulling the source straight from kernel.org and using identical .config files will work with 6.2.0-6 but fail with 6.2.0-7. I was able to build and install 4.8.3 with no issues after back-revving gcc et. al. to 6.2.0-6 -- sRw On 10/20/16 11:09, Wolfgang Walter wrote: Hello, with this version of gcc-6 I can't build vanilla kernels any more. It fails with even with CC_STACKPROTECTOR_STRONG disabled: scripts/kconfig/mconf Kconfig configuration written to .config *** End of the configuration. *** Execute 'make' to start the build or try 'make help'. ksrc@ei:~/build/kernels/linux-4.8.3$ make scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h UPD include/generated/utsrelease.h CC kernel/bounds.s kernel/bounds.c:1:0: error: code model kernel does not support PIC mode /* Kbuild:45: recipe for target 'kernel/bounds.s' failed make[1]: *** [kernel/bounds.s] Error 1 Makefile:1015: recipe for target 'prepare0' failed make: *** [prepare0] Error 2 I think this is a major regression if you can't build vanilla and stable kernels any more. Regards,
Bug#841420: --enable-default-pie breaks kernel builds
On 2016-10-20 17:54 +0200, Bálint Réczey wrote: > Control: reassign -1 linux 4.7.8-1 > Control: severity -1 serious > Control: tags -1 patch > > Hi David, > > 2016-10-20 14:02 GMT+02:00 David Weinehall : >> Package: gcc-6 >> Severity: important >> Version: 6.2.0-7 >> >> --enable-default-pie (first enabled in gcc-6 6.2.0-7) causes kernel >> builds to fail. If the kernel is configured with the stack protector >> enabled it'll fail with a rather unhelpful error message claiming >> that the compiler doesn't support -fstack-protector, >> but the problem is in fact caused by: >> >> kernel/bounds.c:1:0: error: code model kernel does not support PIC mode >> >> (The kernel is built with -mcmodel=kernel) >> >> I think it's fair to say that the kernel is kind of an important piece >> of software and that it's imperative that we don't break kernel builds... > > The kernel is very important indeed and it did break in our build test. > I'm sorry, somehow I missed filing bug for the linux package, just for > user-mode-linux. > The following patch fixes the FTBFS: > > --- linux-4.7.8/debian/rules.d/Makefile.inc > +++ linux-4.7.8/debian/rules.d/Makefile.inc > @@ -5,7 +5,8 @@ > > SHELL = /bin/sh -e > > -CC = $(CROSS_COMPILE)gcc > +CC = $(CROSS_COMPILE)gcc -no-pie > +LD = $(CROSS_COMPILE)ld -no-pie > CXX = $(CROSS_COMPILE)g++ > CFLAGS := $(shell dpkg-buildflags --get CFLAGS) -Wall > CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) \ > > Maybe the ld part is obsolete, I have not checked that. That patch might work for the Debian package, but has anybody contacted the upstream kernel developers about that? At least the 4.8.3 vanilla kernel fails in the same way, I haven't tested 4.9-rc1 yet. FWIW, this issue has been discussed in Ubuntu for six months(!), see https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982. Cheers, Sven
Processed: --enable-default-pie breaks kernel build on amd64
Processing control commands: > severity -1 normal Bug #841438 [gcc-6] --enable-default-pie breaks kernel build on amd64 Ignoring request to change severity of Bug 841438 to the same value. > reassign -1 src:linux Bug #841438 [gcc-6] --enable-default-pie breaks kernel build on amd64 Bug reassigned from package 'gcc-6' to 'src:linux'. No longer marked as found in versions gcc-6/6.2.0-7. Ignoring request to alter fixed versions of bug #841438 to the same values previously set > affects -1 gcc-6 Bug #841438 [src:linux] --enable-default-pie breaks kernel build on amd64 Added indication that 841438 affects gcc-6 -- 841438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841453: linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty
Package: linux-image-4.7.0-1-amd64 Version: 4.7.6-1 Severity: serious I you have linux-image-4.7.0-1-amd64 installed, then upgrading to linux-image-4.7.0-1-amd64-unsigned fails: # apt-get install linux-image-4.7.0-1-amd64-unsigned Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: linux-doc-4.7 (4.7.8-1) debian-kernel-handbook (1.0.17) grub-pc (2.02~beta3-1) | grub-efi-amd64 (2.02~beta3-1) | extlinux (3:6.03+dfsg-14) Recommended packages: firmware-linux-free (3.4) irqbalance (1.1.0-2) The following packages will be REMOVED: linux-image-4.7.0-1-amd64* (4.7.6-1) The following NEW packages will be installed: linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) 0 upgraded, 1 newly installed, 1 to remove and 35 not upgraded. Need to get 36.8 MB of archives. After this operation, 1709 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ftp.debian.org/debian unstable/main amd64 linux-image-4.7.0-1-amd64-unsigned amd64 4.7.8-1 [36.8 MB] Fetched 36.8 MB in 1s (28.7 MB/s) debconf: delaying package configuration, since apt-utils is not installed (Reading database ... 14226 files and directories currently installed.) Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ... W: Last kernel image has been removed, so removing the default symlinks /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-4.7.0-1-amd64 Selecting previously unselected package linux-image-4.7.0-1-amd64-unsigned. (Reading database ... 10177 files and directories currently installed.) Preparing to unpack .../linux-image-4.7.0-1-amd64-unsigned_4.7.8-1_amd64.deb ... Unpacking linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ... Setting up linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.7.0-1-amd64 I: /initrd.img.old is now a symlink to boot/initrd.img-4.7.0-1-amd64 I: /vmlinuz is now a symlink to boot/vmlinuz-4.7.0-1-amd64 I: /initrd.img is now a symlink to boot/initrd.img-4.7.0-1-amd64 /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64 cp: cannot stat '/etc/modprobe.d/*': No such file or directory (Reading database ... 14224 files and directories currently installed.) Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ... Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.6-1) ... W: Last kernel image has been removed, so removing the default symlinks rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty dpkg: error processing package linux-image-4.7.0-1-amd64 (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-4.7.0-1-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages linux-image-4.7.0-1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.125 ii kmod22-1.1 ii linux-base 4.5 -- Jakub Wilk
Processed: reassign 841453 to src:linux-signed
Processing commands for cont...@bugs.debian.org: > reassign 841453 src:linux-signed 2.7 Bug #841453 [linux-image-4.7.0-1-amd64] linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty Bug reassigned from package 'linux-image-4.7.0-1-amd64' to 'src:linux-signed'. No longer marked as found in versions linux-signed/2.7. Ignoring request to alter fixed versions of bug #841453 to the same values previously set Bug #841453 [src:linux-signed] linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty Marked as found in versions linux-signed/2.7. > thanks Stopping processing here. Please contact me if you need assistance. -- 841453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841438: This is agcc bug : upstream kernel irself fails to build with this gcc so reassigne to gcc-6
I never use debian kernel and connaot compile upstream kernel with gcc-6 now. --eric
Processed: Re: Bug#841420: --enable-default-pie breaks kernel builds
Processing control commands: > tags -1 - patch Bug #841420 [linux] --enable-default-pie breaks kernel builds Bug #841368 [linux] gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled Removed tag(s) patch. Removed tag(s) patch. -- 841368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841368 841420: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841420 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841420: --enable-default-pie breaks kernel builds
Control: tags -1 - patch 2016-10-20 18:48 GMT+02:00 Sven Joachim : > On 2016-10-20 17:54 +0200, Bálint Réczey wrote: > >> Control: reassign -1 linux 4.7.8-1 >> Control: severity -1 serious >> Control: tags -1 patch >> >> Hi David, >> >> 2016-10-20 14:02 GMT+02:00 David Weinehall : >>> Package: gcc-6 >>> Severity: important >>> Version: 6.2.0-7 >>> >>> --enable-default-pie (first enabled in gcc-6 6.2.0-7) causes kernel >>> builds to fail. If the kernel is configured with the stack protector >>> enabled it'll fail with a rather unhelpful error message claiming >>> that the compiler doesn't support -fstack-protector, >>> but the problem is in fact caused by: >>> >>> kernel/bounds.c:1:0: error: code model kernel does not support PIC mode >>> >>> (The kernel is built with -mcmodel=kernel) >>> >>> I think it's fair to say that the kernel is kind of an important piece >>> of software and that it's imperative that we don't break kernel builds... >> >> The kernel is very important indeed and it did break in our build test. >> I'm sorry, somehow I missed filing bug for the linux package, just for >> user-mode-linux. >> The following patch fixes the FTBFS: >> >> --- linux-4.7.8/debian/rules.d/Makefile.inc >> +++ linux-4.7.8/debian/rules.d/Makefile.inc >> @@ -5,7 +5,8 @@ >> >> SHELL = /bin/sh -e >> >> -CC = $(CROSS_COMPILE)gcc >> +CC = $(CROSS_COMPILE)gcc -no-pie >> +LD = $(CROSS_COMPILE)ld -no-pie >> CXX = $(CROSS_COMPILE)g++ >> CFLAGS := $(shell dpkg-buildflags --get CFLAGS) -Wall >> CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) \ >> >> Maybe the ld part is obsolete, I have not checked that. > > That patch might work for the Debian package, but has anybody contacted > the upstream kernel developers about that? At least the 4.8.3 vanilla > kernel fails in the same way, I haven't tested 4.9-rc1 yet. Fixing it upstream would certainly be better. I also haven't booted the built image, thus please use this patch only as inspiration. :-) Cheers, Balint > > FWIW, this issue has been discussed in Ubuntu for six months(!), see > https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982. > > Cheers, >Sven
Processed: reassign 841419 to src:linux, forcibly merging 841438 841419
Processing commands for cont...@bugs.debian.org: > reassign 841419 src:linux Bug #841419 [linux-source-4.7] linux-source-4.7: debian linux source package incompatible with default gcc6 in unstable? Bug reassigned from package 'linux-source-4.7' to 'src:linux'. No longer marked as found in versions linux/4.7.8-1. Ignoring request to alter fixed versions of bug #841419 to the same values previously set > forcemerge 841438 841419 Bug #841438 [src:linux] --enable-default-pie breaks kernel build on amd64 Bug #841419 [src:linux] linux-source-4.7: debian linux source package incompatible with default gcc6 in unstable? Severity set to 'normal' from 'important' Added indication that 841419 affects gcc-6 Merged 841419 841438 > thanks Stopping processing here. Please contact me if you need assistance. -- 841419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841419 841438: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841438 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841438: --enable-default-pie breaks kernel build on amd64
On Thu, 20 Oct 2016 19:05:51 +0200 Gianfranco Costamagna
wrote:
> control: severity -1 normal
> control: reassign -1 src:linux
> control: affects -1 gcc-6
>
> Hi Linux Kernel maintainers,
> as you already know, the default PIE flag breaks the kernel build, can I
> suggest you to apply a similar patch
> to the one that Ubuntu appplied some time ago?
> https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982/comments/39
Many Debian users do not use our packaged kernel, so working around
this in src:linux does not solve the problem. The default compiler in
Debian *must* be able to compile the upstream Linux kernel. I will not
accept any patches for this that have not been accepted upstream.
A better approach might be to make -mcmodel=kernel automatically
override the default of -fPIE.
Ben.
> --- a/Makefile
> +++ b/Makefile
> @@ -612,6 +612,12 @@ endif # $(dot-config)
> # Defaults to vmlinux, but the arch makefile usually adds further targets
> all: vmlinux
>
> +# force no-pie for distro compilers that enable pie by default
> +KBUILD_CFLAGS += $(call cc-option, -fno-pie)
> +KBUILD_CFLAGS += $(call cc-option, -no-pie)
> +KBUILD_AFLAGS += $(call cc-option, -fno-pie)
> +KBUILD_CPPFLAGS += $(call cc-option, -fno-pie)
> +
> # The arch Makefile can set ARCH_{CPP,A,C}FLAGS to override the default
> # values of the respective KBUILD_* variables
> ARCH_CPPFLAGS :=
>
> thanks
>
> Gianfranco
>
--
Ben Hutchings
Never put off till tomorrow what you can avoid all togethe
signature.asc
Description: This is a digitally signed message part
Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
It's not a GCC bug but kind of new feature. Take a look at this changelog entry: gcc-6 (6.2.0-7) unstable; urgency=medium [ Matthias Klose ] * Configure with --enable-default-pie and pass -z now when pie is enabled; on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x. Closes: #835148. Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in beginning of CFLAGS to build kernel successfully. I'm currently looking for correct way to do this trick. -- SY, Konstantin Demin
Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote: > It's not a GCC bug but kind of new feature. It's a bug when a compiler fails to compile valid code. Ben. > Take a look at this changelog entry: > gcc-6 (6.2.0-7) unstable; urgency=medium > > [ Matthias Klose ] > * Configure with --enable-default-pie and pass -z now when pie is enabled; > on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x. > Closes: #835148. > > Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in > beginning of CFLAGS to build kernel successfully. > > I'm currently looking for correct way to do this trick. > > -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: This is a digitally signed message part
Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
I agree. When the version changes from 6.2.0-6 to 6.2.0-7, only bug fixes should be included, not changes in functionality. In this case setting enable-default-pie essentially broke backwards compatibility. Kernel code that built in -6 failed to build in -7. That, I agree, should be considered a bug, and the change should be rolled back. -- sRw On 10/20/2016 05:49 PM, Ben Hutchings wrote: On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote: It's not a GCC bug but kind of new feature. It's a bug when a compiler fails to compile valid code. Ben. Take a look at this changelog entry: gcc-6 (6.2.0-7) unstable; urgency=medium [ Matthias Klose ] * Configure with --enable-default-pie and pass -z now when pie is enabled; on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x. Closes: #835148. Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in beginning of CFLAGS to build kernel successfully. I'm currently looking for correct way to do this trick.
Bug#841473: linux-image-4.7.0-1-amd64: Nouveau driver stops working freezing system
Package: src:linux Version: 4.7.6-1 Severity: important Dear Maintainer, * What led up to the situation? System video froze without any notice, all i could savage from the log files: Oct 21 00:29:58 elektrum kernel: [98341.161363] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Oct 21 00:29:58 elektrum kernel: [98341.161369] nouveau :01:00.0: fifo: gr engine fault on channel 2, recovering... * What exactly did you do (or not do) that was effective (or ineffective)? Video was broken, not even changing video modes (going to the console) worked This has been happening at random intervals. Tanking you for your time and attention, Andre Esteves -- Package-specific info: ** Version: Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.6-1 (2016-10-07) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.7.0-1-amd64 root=/dev/mapper/elektrum--vg-root ro quiet ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [6.122988] usb 3-9: New USB device found, idVendor=05e3, idProduct=0608 [6.122989] usb 3-9: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [6.122989] usb 3-9: Product: USB2.0 Hub [6.123628] hub 3-9:1.0: USB hub found [6.123900] hub 3-9:1.0: 4 ports detected [6.233897] usb 4-5: new SuperSpeed USB device number 2 using xhci_hcd [6.250568] usb 4-5: New USB device found, idVendor=067b, idProduct=2773 [6.250569] usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6.250569] usb 4-5: Product: USB3.0 DUAL DOCK [6.250570] usb 4-5: Manufacturer: Prolific [6.250570] usb 4-5: SerialNumber: PROLIFICM3 [6.251086] usb 4-5: Set SEL for device-initiated U1 failed. [6.251168] usb 4-5: Set SEL for device-initiated U2 failed. [6.264676] usb-storage 4-5:1.0: USB Mass Storage device detected [6.264714] scsi host10: usb-storage 4-5:1.0 [6.264754] usbcore: registered new interface driver usb-storage [6.265491] usbcore: registered new interface driver uas [6.269997] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [6.361901] usb 3-13: new low-speed USB device number 15 using xhci_hcd [6.497420] nouveau :01:00.0: fb1: nouveaufb frame buffer device [6.497423] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 1 [6.558895] usb 3-13: New USB device found, idVendor=045e, idProduct=0780 [6.558897] usb 3-13: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.558898] usb 3-13: Product: Comfort Curve Keyboard 3000 [6.558899] usb 3-13: Manufacturer: Microsoft [6.729907] usb 3-14: new low-speed USB device number 16 using xhci_hcd [6.896263] usb 3-14: New USB device found, idVendor=1bcf, idProduct=0005 [6.896265] usb 3-14: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [6.896266] usb 3-14: Product: USB Optical Mouse [6.913253] hidraw: raw HID events driver (C) Jiri Kosina [6.925224] media: Linux media interface: v0.10 [6.926292] Bluetooth: Core ver 2.21 [6.926306] NET: Registered protocol family 31 [6.926307] Bluetooth: HCI device and connection manager initialized [6.926309] Bluetooth: HCI socket layer initialized [6.926311] Bluetooth: L2CAP socket layer initialized [6.926316] Bluetooth: SCO socket layer initialized [6.929517] usblp 3-5.1.1:1.0: usblp0: USB Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0027 [6.929540] usbcore: registered new interface driver usblp [6.929665] Linux video capture interface: v2.00 [6.930036] usbcore: registered new interface driver btusb [6.939646] usbcore: registered new interface driver usbhid [6.939647] usbhid: USB HID core driver [6.940890] input: Ver 1.0 USB To RS232 Interface (V1.0) BaudRate 2400bps as /devices/pci:00/:00:14.0/usb3/3-5/3-5.1/3-5.1.2/3-5.1.2:1.0/0003:0F03:0001.0001/input/input24 [6.965120] usb 3-5.3: set resolution quirk: cval->res = 384 [6.965375] usbcore: registered new interface driver snd-usb-audio [6.965376] uvcvideo: Found UVC 1.00 device HD Webcam C525 (046d:0826) [6.977518] uvcvideo 3-5.3:1.2: Entity type for entity Extension 5 was not initialized! [6.977520] uvcvideo 3-5.3:1.2: Entity type for entity Camera 1 was not initialized! [6.977522] uvcvideo 3-5.3:1.2: Entity type for entity Extension 6 was not initialized! [6.977523] uvcvideo 3-5.3:1.2: Entity type for entity Extension 7 was not initialized! [6.977524] uvcvideo 3-5.3:1.2: Entity type for entity Extension 8 was not initialized! [6.977638] input: HD Webcam C525 as /devices/pci:00/:00:14.0/usb3/3-5/3-5.3/3-5.3:1.2/input/input25 [6.994083] hid-generic 0003:0F03:0001.0001: input,hidraw0: USB HID v1.00 Gamepad [Ver 1.0 USB To RS232 Interface (V1.0) BaudRate 2400bps] on usb-:00:14.0-5.1.2/input0 [6.994131] usbcore: registered
Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled
2016-10-21 1:49 GMT+03:00 Ben Hutchings : > It's a bug when a compiler fails to compile valid code. > > Ben. > > -- > Ben Hutchings > Never put off till tomorrow what you can avoid all together. Dear Ben, there are no actual bug in compiler, just a caveat to work with it. Some time ago i had experience to build fully hardened nginx build, and I was forced to build shared libraries with -fPIC but not -fPIE due to linker errors. Solution was to separate build to executable only and shared-libraries only; this is semi-true: executable is successfully linked with -fPIC flag, but it's not used in packaging because of executable already built with -fPIE. This bug report is just another round of game with compiler/linker flags. In my turn, I would rather define protective flags to provide backward and forward compatibility. -- SY, Konstantin Demin --- a/debian/rules.real +++ b/debian/rules.real @@ -168,6 +168,7 @@ else echo 'override CROSS_COMPILE = $$(DEB_HOST_GNU_TYPE)-' >> '$(DIR)/.kernelvariables' echo 'endif' >> '$(DIR)/.kernelvariables' endif + echo 'KCFLAGS += -fno-PIC -fno-PIE' >> '$(DIR)/.kernelvariables' ifdef CFLAGS_KERNEL echo 'CFLAGS_KERNEL += $(CFLAGS_KERNEL)' >> '$(DIR)/.kernelvariables' echo 'CFLAGS_MODULE += $(CFLAGS_KERNEL)' >> '$(DIR)/.kernelvariables' endif
Processing of linux-signed_2.8_source.changes
linux-signed_2.8_source.changes uploaded successfully to localhost along with the files: linux-signed_2.8.dsc linux-signed_2.8.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)
Re: Bug#841261: ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard
Control: reassign -1 src:linux 4.8~rc8-1~exp1 Control: retitle -1 linux: 4.8 causes crashes in ulogd2 due to bug in netfilter code On Thu, 2016-10-20 at 11:00 +0200, Julien Cristau wrote: > I think this should just be reassigned, there's not much point working > around a kernel bug. Doing that with this mail. Linux folks: please close this bug when this netfilter patch for Linux 4.8 reaches Debian. https://patchwork.ozlabs.org/patch/680773/ It is needed for acker.d.o and aagaard.d.o, which run the Linux 4.8 version from Debian experimental. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#841261: ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard
Processing control commands: > reassign -1 src:linux 4.8~rc8-1~exp1 Bug #841261 [ulogd2] ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard Bug reassigned from package 'ulogd2' to 'src:linux'. No longer marked as found in versions ulogd2/2.0.4-2+deb8u1. Ignoring request to alter fixed versions of bug #841261 to the same values previously set Bug #841261 [src:linux] ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard Marked as found in versions linux/4.8~rc8-1~exp1. > retitle -1 linux: 4.8 causes crashes in ulogd2 due to bug in netfilter code Bug #841261 [src:linux] ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard Changed Bug title to 'linux: 4.8 causes crashes in ulogd2 due to bug in netfilter code' from 'ulogd2: reliably crashes (SIGSEGV) on Debian's new arm64 nodes: acker/aagaard'. -- 841261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#841453: marked as done (linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty)
Your message dated Fri, 21 Oct 2016 04:26:45 + with message-id and subject line Bug#841453: fixed in linux-signed 2.8 has caused the Debian Bug report #841453, regarding linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 841453: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-4.7.0-1-amd64 Version: 4.7.6-1 Severity: serious I you have linux-image-4.7.0-1-amd64 installed, then upgrading to linux-image-4.7.0-1-amd64-unsigned fails: # apt-get install linux-image-4.7.0-1-amd64-unsigned Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: linux-doc-4.7 (4.7.8-1) debian-kernel-handbook (1.0.17) grub-pc (2.02~beta3-1) | grub-efi-amd64 (2.02~beta3-1) | extlinux (3:6.03+dfsg-14) Recommended packages: firmware-linux-free (3.4) irqbalance (1.1.0-2) The following packages will be REMOVED: linux-image-4.7.0-1-amd64* (4.7.6-1) The following NEW packages will be installed: linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) 0 upgraded, 1 newly installed, 1 to remove and 35 not upgraded. Need to get 36.8 MB of archives. After this operation, 1709 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ftp.debian.org/debian unstable/main amd64 linux-image-4.7.0-1-amd64-unsigned amd64 4.7.8-1 [36.8 MB] Fetched 36.8 MB in 1s (28.7 MB/s) debconf: delaying package configuration, since apt-utils is not installed (Reading database ... 14226 files and directories currently installed.) Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ... W: Last kernel image has been removed, so removing the default symlinks /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-4.7.0-1-amd64 Selecting previously unselected package linux-image-4.7.0-1-amd64-unsigned. (Reading database ... 10177 files and directories currently installed.) Preparing to unpack .../linux-image-4.7.0-1-amd64-unsigned_4.7.8-1_amd64.deb ... Unpacking linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ... Setting up linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.7.0-1-amd64 I: /initrd.img.old is now a symlink to boot/initrd.img-4.7.0-1-amd64 I: /vmlinuz is now a symlink to boot/vmlinuz-4.7.0-1-amd64 I: /initrd.img is now a symlink to boot/initrd.img-4.7.0-1-amd64 /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64 cp: cannot stat '/etc/modprobe.d/*': No such file or directory (Reading database ... 14224 files and directories currently installed.) Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ... Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.6-1) ... W: Last kernel image has been removed, so removing the default symlinks rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty dpkg: error processing package linux-image-4.7.0-1-amd64 (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-4.7.0-1-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages linux-image-4.7.0-1-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.125 ii kmod22-1.1 ii linux-base 4.5 -- Jakub Wilk --- End Message --- --- Begin Message --- Source: linux-signed Source-Version: 2.8 We believe that the bug you reported is fixed in the latest version of linux-signed, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 841...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings (supplier of updated linux-signed package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-
linux-signed_2.8_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Oct 2016 00:55:00 +0100 Source: linux-signed Binary: kernel-image-4.7.0-1-amd64-di nic-modules-4.7.0-1-amd64-di nic-wireless-modules-4.7.0-1-amd64-di nic-shared-modules-4.7.0-1-amd64-di serial-modules-4.7.0-1-amd64-di usb-serial-modules-4.7.0-1-amd64-di ppp-modules-4.7.0-1-amd64-di pata-modules-4.7.0-1-amd64-di cdrom-core-modules-4.7.0-1-amd64-di firewire-core-modules-4.7.0-1-amd64-di scsi-core-modules-4.7.0-1-amd64-di scsi-modules-4.7.0-1-amd64-di loop-modules-4.7.0-1-amd64-di btrfs-modules-4.7.0-1-amd64-di ext4-modules-4.7.0-1-amd64-di isofs-modules-4.7.0-1-amd64-di jfs-modules-4.7.0-1-amd64-di ntfs-modules-4.7.0-1-amd64-di xfs-modules-4.7.0-1-amd64-di fat-modules-4.7.0-1-amd64-di md-modules-4.7.0-1-amd64-di multipath-modules-4.7.0-1-amd64-di usb-modules-4.7.0-1-amd64-di usb-storage-modules-4.7.0-1-amd64-di pcmcia-storage-modules-4.7.0-1-amd64-di fb-modules-4.7.0-1-amd64-di input-modules-4.7.0-1-amd64-di event-modules-4.7.0-1-amd64-di mouse-modules-4.7.0-1-amd64-di nic-pcmcia-modules-4.7.0-1-amd64-di pcmcia-modules-4.7.0-1-amd64-di nic-usb-modules-4.7.0-1-amd64-di sata-modules-4.7.0-1-amd64-di acpi-modules-4.7.0-1-amd64-di i2c-modules-4.7.0-1-amd64-di crc-modules-4.7.0-1-amd64-di crypto-modules-4.7.0-1-amd64-di crypto-dm-modules-4.7.0-1-amd64-di efi-modules-4.7.0-1-amd64-di ata-modules-4.7.0-1-amd64-di mmc-core-modules-4.7.0-1-amd64-di mmc-modules-4.7.0-1-amd64-di nbd-modules-4.7.0-1-amd64-di squashfs-modules-4.7.0-1-amd64-di speakup-modules-4.7.0-1-amd64-di virtio-modules-4.7.0-1-amd64-di uinput-modules-4.7.0-1-amd64-di sound-modules-4.7.0-1-amd64-di hyperv-modules-4.7.0-1-amd64-di udf-modules-4.7.0-1-amd64-di fuse-modules-4.7.0-1-amd64-di linux-image-4.7.0-1-amd64 kernel-image-4.7.0-1-arm64-di nic-modules-4.7.0-1-arm64-di nic-wireless-modules-4.7.0-1-arm64-di nic-shared-modules-4.7.0-1-arm64-di ppp-modules-4.7.0-1-arm64-di cdrom-core-modules-4.7.0-1-arm64-di scsi-core-modules-4.7.0-1-arm64-di scsi-modules-4.7.0-1-arm64-di loop-modules-4.7.0-1-arm64-di btrfs-modules-4.7.0-1-arm64-di ext4-modules-4.7.0-1-arm64-di isofs-modules-4.7.0-1-arm64-di jfs-modules-4.7.0-1-arm64-di xfs-modules-4.7.0-1-arm64-di fat-modules-4.7.0-1-arm64-di md-modules-4.7.0-1-arm64-di multipath-modules-4.7.0-1-arm64-di usb-modules-4.7.0-1-arm64-di usb-storage-modules-4.7.0-1-arm64-di fb-modules-4.7.0-1-arm64-di input-modules-4.7.0-1-arm64-di event-modules-4.7.0-1-arm64-di nic-usb-modules-4.7.0-1-arm64-di sata-modules-4.7.0-1-arm64-di i2c-modules-4.7.0-1-arm64-di crc-modules-4.7.0-1-arm64-di crypto-modules-4.7.0-1-arm64-di crypto-dm-modules-4.7.0-1-arm64-di efi-modules-4.7.0-1-arm64-di ata-modules-4.7.0-1-arm64-di mmc-modules-4.7.0-1-arm64-di nbd-modules-4.7.0-1-arm64-di squashfs-modules-4.7.0-1-arm64-di virtio-modules-4.7.0-1-arm64-di uinput-modules-4.7.0-1-arm64-di leds-modules-4.7.0-1-arm64-di udf-modules-4.7.0-1-arm64-di fuse-modules-4.7.0-1-arm64-di linux-image-4.7.0-1-arm64 kernel-image-4.7.0-1-armmp-di nic-modules-4.7.0-1-armmp-di nic-wireless-modules-4.7.0-1-armmp-di nic-shared-modules-4.7.0-1-armmp-di ppp-modules-4.7.0-1-armmp-di pata-modules-4.7.0-1-armmp-di scsi-core-modules-4.7.0-1-armmp-di scsi-modules-4.7.0-1-armmp-di loop-modules-4.7.0-1-armmp-di btrfs-modules-4.7.0-1-armmp-di ext4-modules-4.7.0-1-armmp-di isofs-modules-4.7.0-1-armmp-di jfs-modules-4.7.0-1-armmp-di fat-modules-4.7.0-1-armmp-di md-modules-4.7.0-1-armmp-di multipath-modules-4.7.0-1-armmp-di usb-modules-4.7.0-1-armmp-di usb-storage-modules-4.7.0-1-armmp-di fb-modules-4.7.0-1-armmp-di input-modules-4.7.0-1-armmp-di event-modules-4.7.0-1-armmp-di nic-usb-modules-4.7.0-1-armmp-di sata-modules-4.7.0-1-armmp-di crc-modules-4.7.0-1-armmp-di crypto-modules-4.7.0-1-armmp-di crypto-dm-modules-4.7.0-1-armmp-di efi-modules-4.7.0-1-armmp-di ata-modules-4.7.0-1-armmp-di mmc-modules-4.7.0-1-armmp-di nbd-modules-4.7.0-1-armmp-di squashfs-modules-4.7.0-1-armmp-di virtio-modules-4.7.0-1-armmp-di uinput-modules-4.7.0-1-armmp-di zlib-modules-4.7.0-1-armmp-di leds-modules-4.7.0-1-armmp-di udf-modules-4.7.0-1-armmp-di fuse-modules-4.7.0-1-armmp-di mtd-modules-4.7.0-1-armmp-di linux-image-4.7.0-1-armmp linux-image-4.7.0-1-armmp-lpae kernel-image-4.7.0-1-686-di nic-modules-4.7.0-1-686-di nic-wireless-modules-4.7.0-1-686-di nic-shared-modules-4.7.0-1-686-di serial-modules-4.7.0-1-686-di usb-serial-modules-4.7.0-1-686-di ppp-modules-4.7.0-1-686-di pata-modules-4.7.0-1-686-di cdrom-core-modules-4.7.0-1-686-di firewire-core-modules-4.7.0-1-686-di scsi-core-modules-4.7.0-1-686-di scsi-modules-4.7.0-1-686-di loop-modules-4.7.0-1-686-di btrfs-modules-4.7.0-1-686-di ext4-modules-4.7.0-1-686-di isofs-modules-4.7.0-1-686-di jfs-modules-4.7.0-1-686-di ntfs-modules-4.7.0-1-686-di xfs-modules-4.7.0-1-686-di fat-modules-4.7.0-1-686-di md-modules-4.7.0-1-686-di multipath-modules-4.7.0-1-686-di usb-modules-4.7.0-1-686-di usb-stora
