Bug#847325: Unable to copy symlinks with copy_file

[Vincent Bernat]

 ❦  8 décembre 2016 02:08 GMT, Ben Hutchings  :

> (Annoyingly, I couldn't reproduce this at first because I tried just
> adding nouveau to /etc/initramfs-tools/modules.  Since mkinitramfs does
> *not* use 'set -e' (unlike most hooks), the 'failure' of copy_file was
> not fatal.)

I should have said that I got the error through plymouth hook.
-- 
Civilization is the limitless multiplication of unnecessary necessities.
-- Mark Twain


signature.asc
Description: PGP signature

Bug#847425: linux-image-4.8.0-1-amd64: Oops on boot with unable to handle kernel paging request after software IO TLB mapping

[clemens . schwaighofer]

Package: src:linux
Version: 4.8.7-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

Booting Linux 4.8.0-1-amd64 kernel in a VMware ESX 6

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Tried to boot with various boot options (eg nomodeset), but oops always
appeared

   * What was the outcome of this action?

Kernel hangs during boot.

Output is only visible if all framebuffer settings are turned off.
Bug output was catched via COM port

Note:
I have another VMware with the same settings (memory 8GB, two cores) that also 
does not boot.
But I have three other VMwares with only 4GB of memory, two cores that boot.

DMESG output:

[0.00] Linux version 4.8.0-1-amd64 (debian-kernel@lists.debian.org) 
(gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 
(2016-11-13)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-1-amd64 
root=/dev/mapper/vg-root ro nomodeset console=tty0 console=ttyS0,19200n8
[0.00] Disabled fast string operations
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009f7ff] usable
[0.00] BIOS-e820: [mem 0x0009f800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xbfee] usable
[0.00] BIOS-e820: [mem 0xbfef-0xbfefefff] ACPI data
[0.00] BIOS-e820: [mem 0xbfeff000-0xbfef] ACPI NVS
[0.00] BIOS-e820: [mem 0xbff0-0xbfff] usable
[0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec0] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xfffe-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00023fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.4 present.
[0.00] Hypervisor detected: VMware
[0.00] e820: last_pfn = 0x24 max_arch_pfn = 0x4
[0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
[0.00] e820: last_pfn = 0xc max_arch_pfn = 0x4
[0.00] found SMP MP-table at [mem 0x000f6b30-0x000f6b3f] mapped at 
[a03d400f6b30]
[0.00] RAMDISK: [mem 0x35cbd000-0x36e55fff]
[0.00] ACPI: Early table checksum verification disabled
[0.00] ACPI: RSDP 0x000F6AC0 24 (v02 PTLTD )
[0.00] ACPI: XSDT 0xBFEF109B 5C (v01 INTEL  440BX
0604 VMW  01324272)
[0.00] ACPI: FACP 0xBFEFEE73 F4 (v04 INTEL  440BX
0604 PTL  000F4240)
[0.00] ACPI: DSDT 0xBFEF1349 00DB2A (v01 PTLTD  Custom   
0604 MSFT 0301)
[0.00] ACPI: FACS 0xBFEFFFC0 40
[0.00] ACPI: FACS 0xBFEFFFC0 40
[0.00] ACPI: BOOT 0xBFEF1321 28 (v01 PTLTD  $SBFTBL$ 
0604  LTP 0001)
[0.00] ACPI: APIC 0xBFEF12C3 5E (v01 PTLTD  ? APIC   
0604  LTP )
[0.00] ACPI: MCFG 0xBFEF1287 3C (v01 PTLTD  $PCITBL$ 
0604  LTP 0001)
[0.00] ACPI: SRAT 0xBFEF1197 F0 (v02 VMWARE MEMPLUG  
0604 VMW  0001)
[0.00] ACPI: HPET 0xBFEF115F 38 (v01 VMWARE VMW HPET 
0604 VMW  0001)
[0.00] ACPI: WAET 0xBFEF1137 28 (v01 VMWARE VMW WAET 
0604 VMW  0001)
[0.00] SRAT: PXM 0 -> APIC 0x00 -> Node 0
[0.00] SRAT: PXM 0 -> APIC 0x01 -> Node 0
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x-0x0009]
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x0010-0x0fff]
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x1000-0xbfff]
[0.00] ACPI: SRAT: Node 0 PXM 0 [mem 0x1-0x23fff]
[0.00] NUMA: Node 0 [mem 0x-0x0009] + [mem 
0x0010-0x0fff] -> [mem 0x-0x0fff]
[0.00] NUMA: Node 0 [mem 0x-0x0fff] + [mem 
0x1000-0xbfff] -> [mem 0x-0xbfff]
[0.00] NUMA: Node 0 [mem 0x-0xbfff] + [mem 
0x1-0x23fff] -> [mem 0x-0x23fff]
[0.00] NODE_DATA(0) allocated [mem 0x23fff8000-0x23fffcfff]
[0.

Processed: cloning 845302, reassign -1 to klibc-utils, block 845302 with -1, reassign -2 to busybox ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 845302 -1 -2
Bug #845302 [initramfs-tools] mount implementations from busybox and 
klibc-utils incomplete, fail to mount /usr when using auto option
Bug 845302 cloned as bugs 847423-847424
> reassign -1 klibc-utils 2.0.4-9
Bug #847423 [initramfs-tools] mount implementations from busybox and 
klibc-utils incomplete, fail to mount /usr when using auto option
Bug reassigned from package 'initramfs-tools' to 'klibc-utils'.
No longer marked as found in versions initramfs-tools/0.125.
Ignoring request to alter fixed versions of bug #847423 to the same values 
previously set
Bug #847423 [klibc-utils] mount implementations from busybox and klibc-utils 
incomplete, fail to mount /usr when using auto option
Marked as found in versions klibc/2.0.4-9.
> block 845302 with -1
Bug #845302 [initramfs-tools] mount implementations from busybox and 
klibc-utils incomplete, fail to mount /usr when using auto option
845302 was not blocked by any bugs.
845302 was not blocking any bugs.
Added blocking bug(s) of 845302: 847423
> reassign -2 busybox 1:1.22.0-19
Bug #847424 [initramfs-tools] mount implementations from busybox and 
klibc-utils incomplete, fail to mount /usr when using auto option
Bug reassigned from package 'initramfs-tools' to 'busybox'.
No longer marked as found in versions initramfs-tools/0.125.
Ignoring request to alter fixed versions of bug #847424 to the same values 
previously set
Bug #847424 [busybox] mount implementations from busybox and klibc-utils 
incomplete, fail to mount /usr when using auto option
Marked as found in versions busybox/1:1.22.0-19.
> block 845302 with -2
Bug #845302 [initramfs-tools] mount implementations from busybox and 
klibc-utils incomplete, fail to mount /usr when using auto option
845302 was blocked by: 847423
845302 was not blocking any bugs.
Added blocking bug(s) of 845302: 847424
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
845302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845302
847423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847423
847424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Hutchings]

On Thu, 2016-12-08 at 15:34 +1300, Ben Caradoc-Davies wrote:
> On 08/12/16 15:21, Ben Hutchings wrote:
> > Doesn't apt-listbugs see bugs that 'affect' a package?
> 
> I do not know. Does "affects" provide the version information that 
> apt-listbugs needs to filter bugs?

I don't think there's any way to specify which versions of the affected
package are affected.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



signature.asc
Description: This is a digitally signed message part

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Caradoc-Davies]

On 08/12/16 15:21, Ben Hutchings wrote:

Doesn't apt-listbugs see bugs that 'affect' a package?


I do not know. Does "affects" provide the version information that 
apt-listbugs needs to filter bugs?



(2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
0.125)" which it will need even after #847340 is fixed.

I won't add that Breaks line because:
- Only the combination of the new firmware-misc-nonfree *and* plymouth
  breaks with the unfixed initramfs-tools
- jessie and jessie-backports will never have a version of initramfs-
  tools that satisfies that
- jessie can get a fix for this in a stable update


Yes, that sounds fine to me. The Breaks: I wrote is too broad and this 
will all come out in the wash on unstable.



I agree we need to stop this version of firmware-nonfree going into
testing before initramfs-tools is fixed, so I'm assigning this bug
back.


Thanks very much.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Hutchings]

Control: unmerge -1
Control: reassign -1 firmware-misc-nonfree 20161130-1

On Thu, 2016-12-08 at 14:33 +1300, Ben Caradoc-Davies wrote:
> Ben,
> 
> you reassigned this bug to initramfs-tools and removed the version. As 
> detailed in #847343, I wanted to keep this bug on firmware-misc-nonfree 
> because:
> 
> (1) it protects apt-listbugs users from upgrading firmware-misc-nonfree 
> and being hit by #847340, and

Doesn't apt-listbugs see bugs that 'affect' a package?

> (2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
> 0.125)" which it will need even after #847340 is fixed.

I won't add that Breaks line because:
- Only the combination of the new firmware-misc-nonfree *and* plymouth
  breaks with the unfixed initramfs-tools
- jessie and jessie-backports will never have a version of initramfs-
  tools that satisfies that
- jessie can get a fix for this in a stable update

> If you are sure that you want this bug on initramfs-tools, I will defer 
> to your expertise, but I do not see how this addresses my points above.

I agree we need to stop this version of firmware-nonfree going into
testing before initramfs-tools is fixed, so I'm assigning this bug
back.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson


signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Debian Bug Tracking System]

Processing control commands:

> unmerge -1
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Disconnected #847343 from all other report(s).
> reassign -1 firmware-misc-nonfree 20161130-1
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Bug reassigned from package 'initramfs-tools-core' to 'firmware-misc-nonfree'.
No longer marked as found in versions initramfs-tools/0.125.
Ignoring request to alter fixed versions of bug #847343 to the same values 
previously set
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Marked as found in versions firmware-nonfree/20161130-1.

-- 
847325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847325
847340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 847325 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 847325 serious
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847325
847340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847325: Unable to copy symlinks with copy_file

[Ben Hutchings]

On Wed, 2016-12-07 at 11:46 +0100, Vincent Bernat wrote:
[...]
> I have this error on update-initramfs -u -vv:
> 
> Adding firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin
> Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin
> Adding firmware /usr/lib/firmware/nvidia/gm200/gr/gpccs_inst.bin
> Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
> Removing /boot/initrd.img-4.8.0-2-amd64.dpkg-bak
> update-initramfs: failed for /boot/initrd.img-4.8.0-2-amd64 with 1.
> 
> I have traced to this:
> 
> + copy_file firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + local type src target link_target
> + type=firmware
> + src=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + target=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + [ -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
> + [ -d /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin 
> ]
> + [ -e /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin 
> ]
> + mkdir -p /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr
> + [ -h /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
> + readlink -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + link_target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
> + [ /usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin != 
> /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
> + [ y = y ]
> + echo Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + ln -rs 
> /var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin 
> /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
> + src=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
> + target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
> + [ -e 
> /var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin ]
> + return 1
> 
> Maybe the check should also use cmp.

It should not.  copy_file is documented to return 1 in case the target
already exists, and some of its callers rely on that to skip looking at
the file's dependencies.

If copy_file copies a symlink, it then moves on to copying the link-
target.  It also returns 1 if that already exists in the initramfs, but
this is not obvious from the documentation.  It seems to make more
sense to return 0 in this case and reserve 1 for the case that nothing 
at all was copied.

(Annoyingly, I couldn't reproduce this at first because I tried just
adding nouveau to /etc/initramfs-tools/modules.  Since mkinitramfs does
*not* use 'set -e' (unlike most hooks), the 'failure' of copy_file was
not fatal.)

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



signature.asc
Description: This is a digitally signed message part

Processed: reassign 847340 to initramfs-tools-core, reassign 847343 to initramfs-tools-core ..., affects 847325 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 847340 initramfs-tools-core
Bug #847340 [initramfs-tools] initramfs-tools: fails to copy DRM modules with 
plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug reassigned from package 'initramfs-tools' to 'initramfs-tools-core'.
No longer marked as found in versions initramfs-tools/0.125.
Ignoring request to alter fixed versions of bug #847340 to the same values 
previously set
> reassign 847343 initramfs-tools-core
Bug #847343 [initramfs-tools] firmware-misc-nonfree: breaks update-initramfs 
(initramfs-tools <= 0.125) if plymouth installed
Bug reassigned from package 'initramfs-tools' to 'initramfs-tools-core'.
Ignoring request to alter found versions of bug #847343 to the same values 
previously set
Ignoring request to alter fixed versions of bug #847343 to the same values 
previously set
> forcemerge 847325 847340 847343
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Severity set to 'normal' from 'serious'
Marked as found in versions initramfs-tools/0.125.
Added tag(s) patch.
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Severity set to 'normal' from 'important'
Marked as found in versions initramfs-tools/0.125.
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Added tag(s) patch.
Merged 847325 847340 847343
> affects 847325 firmware-misc-nonfree
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Added indication that 847325 affects firmware-misc-nonfree
Added indication that 847340 affects firmware-misc-nonfree
Added indication that 847343 affects firmware-misc-nonfree
> affects 847325 plymouth
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Bug #847340 [initramfs-tools-core] initramfs-tools: fails to copy DRM modules 
with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Bug #847343 [initramfs-tools-core] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Added indication that 847325 affects plymouth
Added indication that 847340 affects plymouth
Added indication that 847343 affects plymouth
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847325
847340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Caradoc-Davies]

Ben,

you reassigned this bug to initramfs-tools and removed the version. As 
detailed in #847343, I wanted to keep this bug on firmware-misc-nonfree 
because:


(1) it protects apt-listbugs users from upgrading firmware-misc-nonfree 
and being hit by #847340, and


(2) firmware-misc-nonfree lacks "Breaks: initramfs-tools (<=
0.125)" which it will need even after #847340 is fixed.

If you are sure that you want this bug on initramfs-tools, I will defer 
to your expertise, but I do not see how this addresses my points above.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: retitle 847343 to firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 847343 firmware-misc-nonfree: breaks update-initramfs 
> (initramfs-tools <= 0.125) if plymouth installed
Bug #847343 [initramfs-tools] firmware-misc-nonfree: breaks update-initramfs 
(initramfs-tools <= 0.125) if plymouth installed
Ignoring request to change the title of bug#847343 to the same title
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 2 errors): reassign 847340 to initramfs-tools, reassign 847343 to initramfs-tools ..., affects 847325

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 847340 initramfs-tools
Bug #847340 [initramfs-tools] initramfs-tools: fails to copy DRM modules with 
plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8
Ignoring request to reassign bug #847340 to the same package
> reassign 847343 initramfs-tools
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs (initramfs-tools <= 0.125) if plymouth installed
Bug reassigned from package 'firmware-misc-nonfree' to 'initramfs-tools'.
No longer marked as found in versions firmware-nonfree/20161130-1.
Ignoring request to alter fixed versions of bug #847343 to the same values 
previously set
> forcemerge 847325 847340 847343
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Unable to merge bugs because:
package of #847340 is 'initramfs-tools' not 'initramfs-tools-core'
package of #847343 is 'initramfs-tools' not 'initramfs-tools-core'
Failed to forcibly merge 847325: Did not alter merged bugs.

> affects 847325 firmware-misc-nonfree
Failed to mark 847325 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/847325 -- Unable to lock 
/org/bugs.debian.org/spool/lock/847325 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/847325 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847325
847340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#815480: marked as done (Linux kernel crypto 'no key' patches break cryptsetup if not carefully backported)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2016 01:08:54 +
with message-id <1481159334.3013.0.ca...@decadent.org.uk>
and subject line Re: Bug#815480: cryptsetup: versions before 1.7.1 incompatible 
with latest batch of Linux kernels (mainline and stable)
has caused the Debian Bug report #815480,
regarding Linux kernel crypto 'no key' patches break cryptsetup if not 
carefully backported
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.)


-- 
815480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cryptsetup
Severity: important
Tags: upstream fixed-upstream

This bug is actually severity grave as it renders systems unbootable and
data unaccessible, but since it can only trigger on non-Debian kernels ATM,
I am reporting it at severity important.

https://gitlab.com/cryptsetup/cryptsetup/issues/284
https://bugzilla.kernel.org/show_bug.cgi?id=112631

cryptsetup is rendered useless by the latest batch of upstream stable
kernels, as well as by Linux mainline.

On systems with encrypted root, this renders the system unbootable.
Otherwise, it renders any encrypted partitions and media unaccessible.

Reproduced in Debian stable with a custom 3.18.27 kernel.

The issue has been fixed upstream in the cryptsetup master branch, and in
the cryptsetup v1_7_x branch.  The fix will land in the 1.7.1 release, I
think.

The kernel people did not reply yet due to the weekend, but I expect the
change will be made optional or reverted... for a while (and I hope for the
"optional").

Regardless, it would be nice to have updated cryptsetup uploaded to unstable
ASAP, and an eventual Debian stable backport...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
--- End Message ---
--- Begin Message ---
On Wed, 2016-12-07 at 12:49 +0100, Jonas Meurer wrote:
> Hi Ben,
> 
> > On Mon, 07 Mar 2016 03:45:17 + Ben Hutchings 
> wrote:
> > Control: retitle -1 Linux kernel crypto 'no key'Â patches break cryptsetup 
> > if not carefully backported
> > 
> > Linux 3.2.78 and 3.16.7-ckt25 have this problem, but I have fixed it
> > (at least, the result works on my machine!) before uploading stable
> > updates based on those versions.
> > 
> > If you use any other stable kernel branch, you'll need to either
> > upgrade to 4.4 or request the appropriate stable maintainer fixes their
> > backport of the 'no key' patches.
> 
> Probably this bugreport should be closed, no? To my understanding, the
> Linux kernels in Debian are all patched to fix this problem and besides,
> cryptsetup packages in Unstable and Stretch are fixed to work with the
> backwards-incompatible changes anyway since quite some time.

Right, I don't think this ever really affected the Debian package.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson



signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#847343: firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Ben Caradoc-Davies]

Grave severity is not justified because this package works fine if 
plymouth is not installed. I have set the severity to serious because 
firmware-misc-nonfree does not declare Breaks: initramfs-tools (<= 
0.125). I expect that adding this relationship is the cleanest way to 
ensure working upgrades.


Serious severity still meets my goal of warning apt-listbugs users, 
because RC bugs are reported by default.


I do not know if it is possible to include a conditional in a Breaks: 
(something like "and plymouth installed"). In any case, this is now a 
bona fide firmware-misc-nonfree bug.  :-)


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed (with 1 error): forcibly merging 847325 847340

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 847325 847340
Bug #847325 [initramfs-tools-core] Unable to copy symlinks with copy_file
Unable to merge bugs because:
package of #847340 is 'initramfs-tools' not 'initramfs-tools-core'
Failed to forcibly merge 847325: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847325
847340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 847343 to firmware-misc-nonfree: breaks update-initramfs (initramfs-tools <= 0.125) if plymouth installed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 847343 firmware-misc-nonfree: breaks update-initramfs 
> (initramfs-tools <= 0.125) if plymouth installed
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs if plymouth installed
Changed Bug title to 'firmware-misc-nonfree: breaks update-initramfs 
(initramfs-tools <= 0.125) if plymouth installed' from 'firmware-misc-nonfree: 
breaks update-initramfs if plymouth installed'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 847343 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 847343 serious
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs if plymouth installed
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847343: firmware-misc-nonfree: breaks update-initramfs if plymouth installed

[Ben Caradoc-Davies]

On Wed, 7 Dec 2016 11:57:54 -0500 Zack Weinberg  wrote:

FYI, on a system without plymouth, the package installs without any
complaint, and the computer boots successfully using the new
initramfs.


Thanks, Zack. I have updated the title to indicate that this bug only 
affects systems with plymouth installed.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: retitle 847343 to firmware-misc-nonfree: breaks update-initramfs if plymouth installed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 847343 firmware-misc-nonfree: breaks update-initramfs if plymouth 
> installed
Bug #847343 [firmware-misc-nonfree] firmware-misc-nonfree: breaks 
update-initramfs
Changed Bug title to 'firmware-misc-nonfree: breaks update-initramfs if 
plymouth installed' from 'firmware-misc-nonfree: breaks update-initramfs'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
847343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847340: initramfs-tools: fails to copy DRM modules with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8

[Ben Caradoc-Davies]

Also reported as grave bug #847343 against firmware-nonfree/20161130-1 
to warn apt-listbugs users against upgrading:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847343

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#847343: firmware-misc-nonfree: breaks update-initramfs

[Ben Caradoc-Davies]

This is the same bug reported in #847340 against initramfs-tools:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847340

The problem is in initramfs-tools; firmware-misc-nonfree is just the 
trigger. Rather than merging, I would like to leave this bug against 
firmware-misc-nonfree to protect apt-listbugs users from the breakage 
upgrading firmware-misc-nonfree triggers.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#847343: Same here

[Kai Lüke]

Hm, also no complaints or error messages with dracut instead of
initramfs-tools.
And plymouth is not installed.

Bug#847392: linux-image-4.8.0-1-amd64: Resume from suspend results in unrecoverable kernel panic.

[william l-k]

Package: src:linux
Version: 4.8.7-1
Severity: important

Dear maintainer,

Resume from suspend no longer works with this kernel. This is important
functionality for portable devices such as my laptop. I'd tried troubleshooting
bios, power, and wireless settings to no avail. After running from a tty:

sudo systemctl suspend

The system appears to suspend normally. However upon resume the caps lock
starts flashing and a kernel panic message appears on the terminal.

This problem is not evident on any of the following kernels:

linux-image-3.16.0-4-amd64
linux-image-4.6.0-1-amd64
linux-image-4.7.0-1-amd64

As a work around I set the grub/default kernel to 4.7.0-1 to correct the
suspend problem.

Let me know if you need any additional information.



-- Package-specific info:
** Version:
Linux version 4.8.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 
20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.0-1-amd64 root=/dev/mapper/lvmpool-root ro panic=5

** Not tainted

** Kernel log:
[   51.575356] [drm] UVD initialized successfully.
[   51.609568] media: Linux media interface: v0.10
[   51.684597] [drm] ring test on 6 succeeded in 12 usecs
[   51.684618] [drm] ring test on 7 succeeded in 2 usecs
[   51.684625] [drm] VCE initialized successfully.
[   51.687006] [drm] ib test on ring 0 succeeded in 0 usecs
[   51.991099] Linux video capture interface: v2.00
[   52.154202] kvm: Nested Virtualization enabled
[   52.154221] kvm: Nested Paging enabled
[   52.188068] [drm] ib test on ring 1 succeeded in 0 usecs
[   52.700251] [drm] ib test on ring 2 succeeded in 0 usecs
[   52.700362] [drm] ib test on ring 3 succeeded in 0 usecs
[   52.700436] [drm] ib test on ring 4 succeeded in 0 usecs
[   52.774853] ath9k :03:00.0: enabling device ( -> 0002)
[   52.781039] ath: phy0: Enable LNA combining
[   52.782153] ath: phy0: ASPM enabled: 0x42
[   52.782162] ath: EEPROM regdomain: 0x69
[   52.782163] ath: EEPROM indicates we should expect a direct regpair map
[   52.782165] ath: Country alpha2 being used: 00
[   52.782166] ath: Regpair used: 0x69
[   52.883641] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   52.884286] ieee80211 phy0: Atheros AR9485 Rev:1 mem=0xc3124210, 
irq=43
[   53.194350] uvcvideo: Found UVC 1.00 device TOSHIBA Web Camera - HD 
(04ca:7046)
[   53.197468] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not 
initialized!
[   53.197498] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not 
initialized!
[   53.197523] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not 
initialized!
[   53.197824] input: TOSHIBA Web Camera - HD as 
/devices/pci:00/:00:12.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input11
[   53.198044] usbcore: registered new interface driver uvcvideo
[   53.198059] USB Video Class driver (1.1.1)
[   53.216080] [drm] ib test on ring 5 succeeded
[   53.216602] [drm] ib test on ring 6 succeeded
[   53.217006] [drm] ib test on ring 7 succeeded
[   53.222187] [drm] radeon atom DIG backlight initialized
[   53.222197] [drm] Radeon Display Connectors
[   53.03] [drm] Connector 0:
[   53.09] [drm]   eDP-1
[   53.15] [drm]   HPD1
[   53.22] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 
0x653c
[   53.31] [drm]   Encoders:
[   53.37] [drm] LCD1: INTERNAL_UNIPHY
[   53.43] [drm] Connector 1:
[   53.48] [drm]   HDMI-A-1
[   53.54] [drm]   HPD2
[   53.60] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 
0x654c
[   53.69] [drm]   Encoders:
[   53.75] [drm] DFP1: INTERNAL_UNIPHY
[   53.81] [drm] Connector 2:
[   53.86] [drm]   VGA-1
[   53.92] [drm]   DDC: 0x65c0 0x65c0 0x65c4 0x65c4 0x65c8 0x65c8 0x65cc 
0x65cc
[   53.222302] [drm]   Encoders:
[   53.222307] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   54.237696] [drm] fb mappable at 0xC0722000
[   54.237715] [drm] vram apper at 0xC000
[   54.237726] [drm] size 4325376
[   54.237736] [drm] fb depth is 24
[   54.237745] [drm]pitch is 5632
[   54.237948] fbcon: radeondrmfb (fb0) is primary device
[   55.870116] ath9k :03:00.0 wlp3s0: renamed from wlan0
[   56.207788] Console: switching to colour frame buffer device 170x48
[   56.217389] radeon :00:01.0: fb0: radeondrmfb frame buffer device
[   56.241169] [drm] Initialized radeon 2.46.0 20080528 for :00:01.0 on 
minor 0
[   57.348657] Adding 33202172k swap on /dev/mapper/lvmpool-swap.  Priority:-1 
extents:1 across:33202172k FS
[   57.710633] EXT4-fs (dm-8): mounted filesystem with ordered data mode. Opts: 
errors=remount-ro
[   58.060511] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: 
(null)
[   70.610864] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[   70.854053] r8169 :02:00.0: firmware: direct-loading firmware 
rtl_nic/rtl8106e-1.fw
[   71.041264] r8169 :02:00.0 enp2s0: link down
[   71.042564] IPv6: ADDRCONF(NETDEV_UP): 

Customized debian kernel hangs during loading

[Roman Storozhenko]

I have __VMWare Workstation 12__ with installed __Debian Jessie__. I
use serial port to put kernel messages to a file.

I decided to customize kernel and made steps described in the __Debian
Administration handbook__. In particular I:

1) Installed __kernel headers, gcc, make, etc__...

2) Obtained the source code:

sudo apt-get install linux-source-3.16
3) Extracted source files from __/usr/source/__ to a __/home/kernel/__

4) Copied an old __.config__ file from /boot/

5) Ran __make menuconfig__

This is the diff with the standart file:

+CONFIG_CONSOLE_POLL=y
+CONFIG_FRAME_POINTER=y
+CONFIG_DEBUG_KOBJECT=y
+CONFIG_SAMPLES=y
+CONFIG_KGDB=y
+CONFIG_KGDB_SERIAL_CONSOLE=y
+CONFIG_KGDB_TESTS=y
+CONFIG_KGDB_TESTS_ON_BOOT=y
+CONFIG_KGDB_TESTS_BOOT_STRING="V1F100"
+CONFIG_KGDB_LOW_LEVEL_TRAP=y
+CONFIG_KGDB_KDB=y
+CONFIG_KDB_KEYBOARD=y
+CONFIG_KDB_CONTINUE_CATASTROPHIC=0
+CONFIG_X86_VERBOSE_BOOTUP=y
+CONFIG_X86_PTDUMP=y
+CONFIG_EFI_PGT_DUMP=y
+CONFIG_X86_DEBUG_STATIC_CPU_HAS=y

6) Built and installed resulted kernel to __grub__.

7) When I try to load a kernel it immediately hangs. This is the
output that VM put in the console file:

Entering kdb (current=0x88042e1cf2b0, pid 1) on processor 2
due to Keyboard Entry
[2]kdb> Loading, please wait...

Does anybody know how to fix that ?

Customized debian kernel hangs during loading

[Roman Storozhenko]

I have __VMWare Workstation 12__ with installed __Debian Jessie__. I use
serial port to put kernel messages to a file.

I decided to customize kernel and made steps described in the __Debian
Administration handbook__. In particular I:

1) Installed __kernel headers, gcc, make, etc__...

2) Obtained the source code:

sudo apt-get install linux-source-3.16
3) Extracted source files from __/usr/source/__ to a __/home/kernel/__

4) Copied an old __.config__ file from /boot/

5) Ran __make menuconfig__

This is the diff with the standart file:

+CONFIG_CONSOLE_POLL=y
+CONFIG_FRAME_POINTER=y
+CONFIG_DEBUG_KOBJECT=y
+CONFIG_SAMPLES=y
+CONFIG_KGDB=y
+CONFIG_KGDB_SERIAL_CONSOLE=y
+CONFIG_KGDB_TESTS=y
+CONFIG_KGDB_TESTS_ON_BOOT=y
+CONFIG_KGDB_TESTS_BOOT_STRING="V1F100"
+CONFIG_KGDB_LOW_LEVEL_TRAP=y
+CONFIG_KGDB_KDB=y
+CONFIG_KDB_KEYBOARD=y
+CONFIG_KDB_CONTINUE_CATASTROPHIC=0
+CONFIG_X86_VERBOSE_BOOTUP=y
+CONFIG_X86_PTDUMP=y
+CONFIG_EFI_PGT_DUMP=y
+CONFIG_X86_DEBUG_STATIC_CPU_HAS=y

6) Built and installed resulted kernel to __grub__.

7) When I try to load a kernel it immediately hangs. This is the output
that VM put in the console file:

Entering kdb (current=0x88042e1cf2b0, pid 1) on processor 2 due to
Keyboard Entry
[2]kdb> Loading, please wait...

Does anybody know how to fix that ?

-- 
Kind regards,
Roman

Bug#847360: linux-image-3.16.0-4-amd64: kernel panic

[root]

Package: src:linux
Version: 3.16.36-1+deb8u2
Severity: normal

Dear Maintainer,

Here is the kernel log and below the command to run the VM:

[4034701.675638] EXT4-fs (dm-4): mounted filesystem with ordered data mode. 
Opts: (null)
[4034701.918056] EXT4-fs (dm-4): mounted filesystem with ordered data mode. 
Opts: (null)
[4034702.037429] EXT4-fs (dm-4): mounted filesystem with ordered data mode. 
Opts: (null)
[4034702.057227] device veth18dc633 entered promiscuous mode
[4034702.058757] IPv6: ADDRCONF(NETDEV_UP): veth18dc633: link is not ready
[4034702.298634] BUG: unable to handle kernel NULL pointer dereference at 
0078
[4034702.300647] IP: [] check_preempt_wakeup+0xd4/0x1d0
[4034702.302079] PGD 6227f1067 PUD 624d93067 PMD 0
[4034702.302599] Oops:  [#1] SMP
[4034702.302599] Modules linked in: veth ipt_MASQUERADE xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 x
t_addrtype xt_conntrack nf_nat nf_conntrack bridge stp llc dm_thin_pool 
dm_persistent_data dm_bio_prison dm_bufio libcrc32c nls_utf8 n
ls_cp437 vfat fat xt_multiport binfmt_misc ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables ppdev ttm drm_kms_helper i2c_p
iix4 drm pvpanic parport_pc parport i2c_core virtio_balloon evdev serio_raw 
processor pcspkr thermal_sys button loop fuse autofs4 ext4
 crc16 mbcache jbd2 crc32c_generic btrfs xor raid6_pq dm_mod sg sr_mod cdrom 
ata_generic virtio_blk virtio_net uhci_hcd ata_piix ehci_
hcd libata floppy virtio_pci psmouse virtio_ring virtio scsi_mod usbcore 
usb_common
[4034702.302599] CPU: 1 PID: 29735 Comm: exe Not tainted 3.16.0-4-amd64 #1 
Debian 3.16.36-1+deb8u2
[4034702.302599] Hardware name: Unspecified (sysad...@collabora.co.uk) 
Unspecified, BIOS
[4034702.302599] task: 8806249469a0 ti: 880056398000 task.ti: 
880056398000
[4034702.302599] RIP: 0010:[]  [] 
check_preempt_wakeup+0xd4/0x1d0
[4034702.302599] RSP: :88063fc83e58  EFLAGS: 00010097
[4034702.302599] RAX:  RBX:  RCX: 
0008
[4034702.302599] RDX:  RSI: 8806258c2960 RDI: 
880625ee9300
[4034702.302599] RBP: 880155f6f700 R08: 816108c0 R09: 
0001
[4034702.302599] R10: 0008 R11: 0010 R12: 
8806249469a0
[4034702.302599] R13: 88063fc92f40 R14:  R15: 

[4034702.302599] FS:  7eff69401700() GS:88063fc8() 
knlGS:
[4034702.302599] CS:  0010 DS:  ES:  CR0: 80050033
[4034702.302599] CR2: 0078 CR3: 0006243b5000 CR4: 
06e0
[4034702.302599] Stack:
[4034702.302599]  8109ffe2 88063fc92f40 8806258c2960 
88063fc92f40
[4034702.302599]  0046 0001 0001 
81095b75
[4034702.302599]  8806258c2960 81095ba4 8806258c2960 
88063fc92f40
[4034702.302599] Call Trace:
[4034702.302599]  
[4034702.302599]  [] ? enqueue_task_fair+0x7f2/0xe20
[4034702.302599]  [] ? check_preempt_curr+0x85/0xa0
[4034702.302599]  [] ? ttwu_do_wakeup+0x14/0xf0
[4034702.302599]  [] ? try_to_wake_up+0x1b6/0x2f0
[4034702.302599]  [] ? hrtimer_get_res+0x50/0x50
[4034702.302599]  [] ? hrtimer_wakeup+0x1e/0x30
[4034702.302599]  [] ? __run_hrtimer+0x67/0x210
[4034702.302599]  [] ? hrtimer_interrupt+0xe9/0x220
[4034702.302599]  [] ? smp_apic_timer_interrupt+0x3b/0x50
[4034702.302599]  [] ? apic_timer_interrupt+0x6d/0x80
[4034702.302599]  
[4034702.302599] Code: 0f 1f 80 00 00 00 00 83 e8 01 48 8b 5b 70 39 d0 75 f5 48 
8b 7d 78 48 3b 7b 78 74 15 0f 1f 00 48 8b 6d 70 48 8b
5b 70 48 8b 7d 78 <48> 3b 7b 78 75 ee 48 85 ff 74 e9 e8 8c cb ff ff 48 85 db 0f 
84
[4034702.302599] RIP  [] check_preempt_wakeup+0xd4/0x1d0
[4034702.302599]  RSP 
[4034702.302599] CR2: 0078
[4034702.302599] ---[ end trace 73f2007f73e7ba1a ]---
[4034702.302599] Kernel panic - not syncing: Fatal exception in interrupt
[4034702.302599] Kernel Offset: 0x0 from 0x8100 (relocation range: 
0x8000-0x9fff)
[4034702.302599] ---[ end Kernel panic - not syncing: Fatal exception in 
interrupt



qemu-system-x86_64 -enable-kvm -name aurum -S -machine 
pc-i440fx-2.1,accel=kvm,usb=off -m 24576 -realtime mlock=off -smp 
4,sockets=4,cores=1,threads=1 -uuid 8139cb76-67fc-b1ea-726f-a326141e5659 
-smbios type=0,vendor=COLLABORA -smbios type=1,manufacturer=Unspecified 
(sysad...@collabora.co.uk),product=Unspecified,version=1.0.0,family=kumquat 
-no-user-config -nodefaults -chardev 
socket,id=charmonitor,path=/var/lib/libvirt/qemu/aurum.monitor,server,nowait 
-mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown 
-boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive 
file=/dev/mapper/mainvg-aurum,if=none,id=drive-virtio-disk0,format=raw -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
 -drive if=none,id=drive-ide0-1-0,readonly=o

Bug#847343: firmware-misc-nonfree: breaks update-initramfs

[Ben Caradoc-Davies]

Package: firmware-misc-nonfree
Version: 20161130-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the following upgrade breaks update-initramfs:

firmware-amd-graphics (20160824-1 => 20161130-1)
firmware-atheros (20160824-1 => 20161130-1)
firmware-brcm80211 (20160824-1 => 20161130-1)
firmware-linux (20160824-1 => 20161130-1)
firmware-linux-nonfree (20160824-1 => 20161130-1)
firmware-misc-nonfree (20160824-1 => 20161130-1)
firmware-realtek (20160824-1 => 20161130-1)

Processing triggers for initramfs-tools (0.125) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-2-amd64
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module
i915
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.8.0-2-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.24-8) ...
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Adding "set -x" to the plymouth hook results in a flood that ends with the
following, implicating firmware-misc-nonfree:

+ ln -rs /var/tmp/mkinitramfs_tAZsDU//lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
/var/tmp/mkinitramfs_tAZsDU//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ src=/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ target=/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ [ -e /var/tmp/mkinitramfs_tAZsDU//lib/firmware/nvidia/gm200/gr/gpccs_bl.bin ]
+ return 1
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-4.8.0-2-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

Downgrading the above firmware packages immediately triggers a successful
update-initramfs.

Kind regards,
Ben.



-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ih  initramfs-tools  0.125

-- no debconf information

Bug#815480: cryptsetup: versions before 1.7.1 incompatible with latest batch of Linux kernels (mainline and stable)

[Jonas Meurer]

Hi Ben,

On Mon, 07 Mar 2016 03:45:17 + Ben Hutchings 
wrote:
> Control: retitle -1 Linux kernel crypto 'no key'Â patches break cryptsetup if 
> not carefully backported
> 
> Linux 3.2.78 and 3.16.7-ckt25 have this problem, but I have fixed it
> (at least, the result works on my machine!) before uploading stable
> updates based on those versions.
> 
> If you use any other stable kernel branch, you'll need to either
> upgrade to 4.4 or request the appropriate stable maintainer fixes their
> backport of the 'no key' patches.

Probably this bugreport should be closed, no? To my understanding, the
Linux kernels in Debian are all patched to fix this problem and besides,
cryptsetup packages in Unstable and Stretch are fixed to work with the
backwards-incompatible changes anyway since quite some time.

Cheers,
 jonas




signature.asc
Description: OpenPGP digital signature

Bug#847340: initramfs-tools: fails to copy DRM modules with plymouth, firmware-misc-nonfree 20161130-1, kernel 4.9~rc8

[Simon McVittie]

Package: initramfs-tools
Version: 0.125
Severity: important
Tags: patch

With these package versions:

linux-image-4.9.0-rc8-amd64-unsigned 4.9~rc8-1~exp1
firmware-misc-nonfree 20161130-1
plymouth 0.9.2-3+b1

and plymouth enabled, my initramfs fails to rebuild with exit status 1
from the plymouth hook.

Editing the plymouth hook to "set -x" reveals that two nvidia-related
graphics drivers (gm206 and gm200) both want to include
/lib/firmware/nvidia/gm200/gr/gpcss_bl.bin in the initramfs. The first
one copies successfully, but for the second, copy_file() returns 1,
causing unsuccessful exit from the manual_add_modules() function.

I attach a possible patch.

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 27M Nov 25 22:54 /boot/initrd.img-3.16.0-4-amd64
-rw--- 1 root root 13M Jan 20  2016 /boot/initrd.img-4.3.0-1-amd64.dracut
-rw--- 1 root root 32M Jan 20  2016 
/boot/initrd.img-4.3.0-1-amd64.dracut.full
-rw-r--r-- 1 root root 30M Jan 20  2016 /boot/initrd.img-4.3.0-1-amd64.i-t
-rw-r--r-- 1 root root 33M Nov 25 22:53 /boot/initrd.img-4.7.0-1-amd64
-rw-r--r-- 1 root root 33M Dec  2 16:03 /boot/initrd.img-4.8.0-2-amd64
-rw-r--r-- 1 root root 34M Dec  7 10:53 /boot/initrd.img-4.9.0-rc8-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.9.0-rc8-amd64 root=/dev/mapper/perpetual_ssd-root ro 
rootflags=subvol=@ apparmor=1 security=apparmor net.ifnames=1 quiet splash

-- resume
RESUME=/dev/mapper/perpetual_ssd-swap
-- /proc/filesystems
btrfs
fuseblk
ext3
ext2
ext4
vfat

-- lsmod
Module  Size  Used by
cpuid  16384  0
rfcomm 77824  2
xt_CHECKSUM16384  1
tun28672  1
ctr16384  6
ccm20480  3
nf_conntrack_netbios_ns16384  2
nf_conntrack_broadcast16384  1 nf_conntrack_netbios_ns
xt_CT  16384  2
ipt_MASQUERADE 16384  4
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
xt_tcpudp  16384  59
ip6t_rpfilter  16384  1
ip6t_REJECT16384  2
nf_reject_ipv6 16384  1 ip6t_REJECT
ipt_REJECT 16384  4
nf_reject_ipv4 16384  1 ipt_REJECT
xt_conntrack   16384  60
ip_set 45056  0
nfnetlink  16384  1 ip_set
ebtable_broute 16384  1
bridge135168  1 ebtable_broute
stp16384  1 bridge
llc16384  2 bridge,stp
ebtable_nat16384  1
ip6table_mangle16384  1
ip6table_security  16384  1
ip6table_raw   16384  1
ip6table_nat   16384  1
nf_conntrack_ipv6  20480  32
nf_defrag_ipv6 36864  1 nf_conntrack_ipv6
nf_nat_ipv616384  1 ip6table_nat
iptable_mangle 16384  1
iptable_security   16384  1
iptable_raw16384  1
iptable_nat16384  1
nf_conntrack_ipv4  16384  32
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
nf_nat_ipv416384  1 iptable_nat
nf_nat 28672  3 nf_nat_ipv6,nf_nat_masquerade_ipv4,nf_nat_ipv4
nf_conntrack  114688  10 
nf_conntrack_ipv6,nf_conntrack_ipv4,nf_conntrack_broadcast,nf_conntrack_netbios_ns,xt_CT,nf_nat_ipv6,nf_nat_masquerade_ipv4,xt_conntrack,nf_nat_ipv4,nf_nat
ebtable_filter 16384  1
ebtables   36864  3 ebtable_filter,ebtable_nat,ebtable_broute
ip6table_filter16384  1
ip6_tables 28672  5 
ip6table_mangle,ip6table_filter,ip6table_security,ip6table_raw,ip6table_nat
iptable_filter 16384  1
cpufreq_userspace  16384  0
cpufreq_powersave  16384  0
cpufreq_conservative16384  0
bnep   20480  2
binfmt_misc20480  1
nls_ascii  16384  1
nls_cp437  20480  1
vfat   20480  1
fat69632  1 vfat
ext4  581632  2
jbd2  106496  1 ext4
fscrypto   28672  1 ext4
ecb16384  0
mbcache16384  3 ext4
iTCO_wdt   16384  0
iTCO_vendor_support16384  1 iTCO_wdt
intel_rapl 20480  0
x86_pkg_temp_thermal16384  0
intel_powerclamp   16384  0
coretemp   16384  0
arc4   16384  2
efi_pstore 16384  0
kvm_intel 192512  0
iwldvm139264  0
kvm   589824  1 kvm_intel
irqbypass  16384  1 kvm
joydev 20480  0
mac80211  667648  1 iwldvm
pcspkr 16384  0
serio_raw  16384  0
i2c_i801   24576  0
i2c_smbus  16384  1 i2c_i801
efivars20480  1 efi_pstore
sg 32768  0
snd_hda_codec_hdmi 45056  1
iwlwifi   147456  1 iwldvm
lpc_ich24576  0
snd_hda_codec_conexant24576  1
mfd_core   16384  1 lpc_ich
btusb  45056  0
btrtl  16384  1 btusb
btbcm   

Bug#783063: Xen domU freeze with "Guest Rx stalled"

[Emanuele Viale]

...maybe setting on the guest:

ethtool -K eth0 tx off




*Emanuele Viale*
System Manager

*im3D Clinic Srl*
Preventive Oncology Services
Environment Park Ed. “B/1”
Via Livorno n°60 - 10144 TORINO, Italy
Tel:  +39 011 19508773
Fax: +39 011 19508968
Web: http://www.i-m3d.com/

2016-12-07 11:28 GMT+01:00 Emanuele Viale :

> Hi all :-)
>
> Unfortunately I'm in trouble with this bug :-( ...do you know if there's
> any news about a fix or workaround?
>
> Thanks all for feedback
> Best regards
>
>
>
>
> *Emanuele Viale*
> System Manager
>
> *im3D Clinic Srl*
> Preventive Oncology Services
> Environment Park Ed. “B/1”
> Via Livorno n°60 - 10144 TORINO, Italy
> Tel:  +39 011 19508773
> Fax: +39 011 19508968
> Web: http://www.i-m3d.com/
>

Bug#847325: Unable to copy symlinks with copy_file

[Vincent Bernat]

Package: initramfs-tools-core
Version: 0.125
Severity: normal
File: /usr/share/initramfs-tools/hook-functions

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

Today, new firmware-misc-nonfree package contains some symlinks:

lrwxrwxrwx 1 root root   26 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_bl.bin -> ../../gm200/gr/fecs_bl.bin
- -rw-r--r-- 1 root root 1968 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_data.bin
lrwxrwxrwx 1 root root   28 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_inst.bin -> ../../gm200/gr/fecs_inst.bin
- -rw-r--r-- 1 root root   76 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/fecs_sig.bin
lrwxrwxrwx 1 root root   27 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin -> ../../gm200/gr/gpccs_bl.bin
- -rw-r--r-- 1 root root 2056 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_data.bin
lrwxrwxrwx 1 root root   29 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_inst.bin -> ../../gm200/gr/gpccs_inst.bin
- -rw-r--r-- 1 root root   76 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/gpccs_sig.bin
lrwxrwxrwx 1 root root   33 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin -> 
../../gm200/gr/sw_bundle_init.bin
lrwxrwxrwx 1 root root   25 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_ctx.bin -> ../../gm200/gr/sw_ctx.bin
lrwxrwxrwx 1 root root   33 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_method_init.bin -> 
../../gm200/gr/sw_method_init.bin
lrwxrwxrwx 1 root root   28 déc.   3 22:20 
/lib/firmware/nvidia/gm206/gr/sw_nonctx.bin -> ../../gm200/gr/sw_nonctx.bin

I have this error on update-initramfs -u -vv:

Adding firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin
Adding firmware /usr/lib/firmware/nvidia/gm200/gr/gpccs_inst.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
Removing /boot/initrd.img-4.8.0-2-amd64.dpkg-bak
update-initramfs: failed for /boot/initrd.img-4.8.0-2-amd64 with 1.

I have traced to this:

+ copy_file firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ local type src target link_target
+ type=firmware
+ src=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ target=/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ [ -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ -d /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ -e /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ mkdir -p /var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr
+ [ -h /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ readlink -f /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ link_target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ [ /usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin != 
/lib/firmware/nvidia/gm206/gr/gpccs_bl.bin ]
+ [ y = y ]
+ echo Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
Adding firmware-link /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ ln -rs 
/var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin 
/var/tmp/mkinitramfs_S838WR//lib/firmware/nvidia/gm206/gr/gpccs_bl.bin
+ src=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ target=/usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin
+ [ -e 
/var/tmp/mkinitramfs_S838WR//usr/lib/firmware/nvidia/gm200/gr/gpccs_bl.bin ]
+ return 1

Maybe the check should also use cmp.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 
'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools-core depends on:
ii  cpio 2.11+dfsg-6
ii  klibc-utils  2.0.4-9
ii  kmod 23-1
ii  udev 232-7

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.1-4.3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAlhH6JcSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5r14P/ReRizb2CEv6yNYqJXgwpM8BdwgRkOPJ
6xVzf/gLYuZaxEtCnH2bi9Z6Y3f1ExBJE9G5bNmfSrF9Q8Zpaignifp392a1/HS7
ZE2Q4g6O6LkOB/N29711jd9lEoJfuNYh1g3X77fFO27htZohpkR3sN39k3fJdajd
fTvlm7qnUIyeBT7iC2nq8AZMDWJuY5xZ5ziSDoYB9oxNvCGSJIg+0Q+4XTKmunvA
EcQHrM+0AvaEMkikgoM/Bg7HIEBSp0xtlHPT2hQf1R127zd8urUdpIwzxriWattg
UVdIPGY0GbpIGO8eWNEbsCaEP1oX0cQqnT+e9gqdqCkeFPbxqVGthRKfNX4IEzBc
ZnOFB38t5pt+J9DScj5ZpK2WFJTgaY1Q/ckdK2zRcnNb9hJdOHxUjDRFCI8AOvFx
ouNMxU1hnNgEf1GFri8xwYfDDyS1PoXREY6odYRsvZkrR7a0NWQV2EXf8HSQzewb
vB79DOFw5+vpkaW/RI3YHCMM7hiNOPCiIGw1JLmGA5TXRnsK++k4dtN+mZP5Eptd
ud7zpaCu2RyFaENdVca0yXvw8AenuxOXLEneGAKmElyWIIlwShGrKp5Ru0L56J0J
fz3vNvgf111CC5cQwNRV+FvqRoy+9vzgU9ZTSyAS4oVk2zwtgBfHA1xw+AN0Ub/b
qRH2Li4kr

Bug#783063: Xen domU freeze with "Guest Rx stalled"

[Emanuele Viale]

Hi all :-)

Unfortunately I'm in trouble with this bug :-( ...do you know if there's
any news about a fix or workaround?

Thanks all for feedback
Best regards




*Emanuele Viale*
System Manager

*im3D Clinic Srl*
Preventive Oncology Services
Environment Park Ed. “B/1”
Via Livorno n°60 - 10144 TORINO, Italy
Tel:  +39 011 19508773
Fax: +39 011 19508968
Web: http://www.i-m3d.com/

Bug#847204: Related bugs regarding systemctl status nfs-kernel-server

[Martin Steigerwald]

Hello Riccardo,

Bug#847204: nfs-kernel-server: `systemctl status` incorrectly reports server 
"active" even if not started

and

Bug#843063: systemd: does not show failed nfs mount when nfs server not 
available on booting the client

are likely related to one another.

Seems status reporting is completely broken regarding systemd service 
definition. Your choosing of nfs-kernel-server may be better fit tough than my 
choosing of systemd package, but lets see what maintainers say about this.

Thanks,

-- 
Martin Steigerwald  | Trainer

teamix GmbH
Südwestpark 43
90449 Nürnberg

Tel.:  +49 911 30999 55 | Fax: +49 911 30999 99
mail: martin.steigerw...@teamix.de | web:  http://www.teamix.de | blog: 
http://blog.teamix.de

Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard Müller

teamix Support Hotline: +49 911 30999-112
 
 *** Bitte liken Sie uns auf Facebook: facebook.com/teamix ***