Bug#797955: initramfs-tools: initramfs fails to activate swap on encrypted LVM2 partition; fails boot

2015-09-03 Thread Arnaud Installe 
Package: initramfs-tools
Version: 0.120
Severity: critical
Justification: breaks the whole system

All my partitions (except /boot) are on encrypted LVM2 partitions.

When booting, initramfs asks for the passwords to unlock the /root & /usr
partitions, which are mounted successfully. It then fails to ask for the swap
partition password, instead looping a few minutes, posting messages that it is
waiting for all volumes to become available and "/run/lvm/lvmetad.socket:
connect failed". Disabling lvmetad did not help.

Workaround:

Eventually, it dropped to a shell, which allowed me to run cryptsetup for the
swap partition. After that, I exited the shell, and the system booted
successfully.

My setup:

/etc/crypttab:
==
boulez-_home__crypt UUID=70967099-611f-4082-aad4-3d3e9966fad6 /etc/secretkey
luks
boulez-_root__crypt UUID=b8806964-812e-4239-8914-60b1c33c0491 none luks
boulez-_swap__crypt UUID=d7b4dcc6-3d5d-408b-a5cf-60af0fe9260f none luks
boulez-_usr__crypt UUID=386fb30f-389d-4feb-9c59-352628c0de6b none luks
boulez-_var__crypt UUID=97d4e051-a1b8-4ecc-9dd3-5a69eeed4686 /etc/secretkey
luks
==

/etc/fstab:
==
proc  /proc   procdefaults
0   0
/dev/mapper/boulez-_root__crypt   /   ext4
noatime,errors=remount-ro 0   1
# /boot was on /dev/sda1 during installation
UUID=b3cbbc88-4911-42aa-ba25-dce6a6222ae7 /boot   ext3noatime
0   2
/dev/mapper/boulez-_home__crypt   /home   ext4noatime
0   2
/dev/mapper/boulez-_usr__crypt/usrext4noatime
0   2
/dev/mapper/boulez-_var__crypt/varext4noatime
0   2
/dev/mapper/boulez-_swap__crypt   noneswapsw
0   0
==



-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 19M Aug 17 16:54 /boot/initrd.img-4.0.0-1-amd64
-rw-r--r-- 1 root root 19M Sep  3 22:41 /boot/initrd.img-4.1.0-2-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.1.0-2-amd64 root=/dev/mapper/boulez-_root__crypt ro quiet 
atkbd.reset

-- resume
RESUME=/dev/mapper/boulez-_swap__crypt
-- /proc/filesystems
btrfs
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
rfcomm 61440  14
fuse   86016  3
ctr16384  2
ccm20480  2
ipt_MASQUERADE 16384  1
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
iptable_nat16384  1
nf_nat_ipv416384  1 iptable_nat
xt_addrtype16384  2
br_netfilter   24576  0
nf_nat 20480  2 nf_nat_ipv4,nf_nat_masquerade_ipv4
bridge102400  1 br_netfilter
stp16384  1 bridge
llc16384  2 stp,bridge
dm_thin_pool   61440  1
dm_persistent_data 53248  1 dm_thin_pool
dm_bio_prison  16384  1 dm_thin_pool
libcrc32c  16384  1 dm_persistent_data
cpufreq_stats  16384  0
cpufreq_conservative16384  0
cpufreq_userspace  16384  0
cpufreq_powersave  16384  0
bnep   20480  2
binfmt_misc20480  1
pci_stub   16384  1
vboxpci24576  0
vboxnetadp 28672  0
vboxnetflt 28672  0
vboxdrv   385024  3 vboxnetadp,vboxnetflt,vboxpci
ip6t_REJECT16384  2
nf_reject_ipv6 16384  1 ip6t_REJECT
nf_log_ipv616384  3
nf_conntrack_ipv6  20480  1
nf_defrag_ipv6 36864  1 nf_conntrack_ipv6
ip6table_filter16384  1
ip6_tables 28672  1 ip6table_filter
ipt_REJECT 16384  2
nf_reject_ipv4 16384  1 ipt_REJECT
xt_limit   16384  2
nf_log_ipv416384  3
nf_log_common  16384  2 nf_log_ipv4,nf_log_ipv6
xt_LOG 16384  6
xt_tcpudp  16384  32
nf_conntrack_ipv4  20480  3
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
xt_conntrack   16384  3
nf_conntrack   94208  6 
nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4,nf_conntrack_ipv6
iptable_filter 16384  1
ip_tables  28672  2 iptable_filter,iptable_nat
x_tables   28672  12 
ip6table_filter,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_limit,xt_conntrack,xt_LOG,iptable_filter,ipt_REJECT,ip6_tables,xt_addrtype,ip6t_REJECT
qmi_wwan   24576  0
cdc_wdm20480  2 qmi_wwan
usbnet 36864  1 qmi_wwan
mii16384  1 usbnet
qcserial   20480  0
usb_wwan   20480  1 qcserial
uvcvideo   86016  0
videobuf2_vmalloc  16384  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_core 40960  1 uvcvideo
v4l2_common16384  1 videobuf2_core
videodev  131072  3 uvcvideo,v4l2_common,videobuf2_core
media  20480  2 uvcvideo,videodev
usbserial

Bug#797949: linux: CONFIG_PINCTRL_BAYTRAIL=y needed for microSD slot to function on Intel Compute Stick

2015-09-03 Thread Henry Hallam 
Source: linux
Version: 4.2-1~exp1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
   Installing Debian jessie or sid on an Intel Compute Stick (STCK1A32WFC),
   a miniature amd64 system based on the Atom Z3735F system-on-chip
   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   Tried to use the external Micro SDXC socket, which should appear as
   /dev/mmcblk1
   
   * What was the outcome of this action?
   /dev/mmcblk1 does not exist, only /dev/mmcblk0 (the internal eMMC)
   
   * What outcome did you expect instead?
   /dev/mmcblk1 exists and is usable.

I tried the following kernel packages which all present the same problem:
linux-image-3.16.0-4-amd64
linux-image-4.0.0-2-amd64
linux-image-4.1.0-2-amd64
linux-image-4.2.0-trunk-amd64

Suggested fix:

After some research into similar platforms I tried rebuilding the
kernel package with the CONFIG_PINCTRL_BAYTRAIL option enabled.  This
resolved the issue.  It appears to enable some kind of memory-mapped
GPIO that is required to set up or use the external MicroSD socket.

I have successfully tried this fix on the 4.0.0 and 4.1.0 kernel
packages from the unstable repository and 4.2.0 from the experimental
repository.  It does not work on 3.16.0 as the config option was
introduced in kernel version 3.19. 

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-2+baytrail.1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Thanks,
Henry Hallam

Bug#797880: QNAP TS-219P II with linux-image-4.1.0-0.bpo.1-kirkwood "loses" one hard disk from the RAID while flashing initramfs, causing read-only remount and dpkg to fail

2015-09-03 Thread Robert Schlabbach 
Package: linux-image-4.1.0-0.bpo.1-kirkwood
Version: 4.1.3-1~bpo8+1

Bad things happen when flash-kernel (3.45) flashes the initramfs with this 
Linux kernel on my QNAP TS-219P II:

1. The NAS is equipped with 2 HDDs 3TB in size in RAID 1 mode (mirroring).
2. After the flashing, dpkg errors out stating it is unable to write to a file 
under the /var tree.
3. cat /proc/mdstat reveals that the partitions of HDD /dev/sdb are marked with 
[F].
4. As a result, the RAID partitions have been remounted as read-only, including 
the root partitions, rendering the system inoperable.
5. Regular shutdown is not possible at this point. The NAS has to be 
force-powered off by holding the power button on the device for several seconds.
6. After reboot, dpkg is in an intermediate state. Following the advice to use 
"dpkg --configure -a" results in the flashing operation being carried out again 
with the same result, i.e. the user is caught in a loop.
7. Using "dpkg --configure" instead allows other package install/remove 
operations.

Removing the Linux kernel 4.1, reverting to Linux kernel 3.16.7-ckt11-1+deb8u3 
from debian jessie fixes the problem. In Linux kernel 3.16.7, the same version 
of flash-kernel (3.45) works without the problems mentioned above. So the 
culprit appears not to be the flash-kernel package, but rather the Linux kernel 
4.1 package.

Best Regards,
Robert Schlabbach

Bug#797878: QNAP TS-219P II bricked by linux-image-4.1.0-0.bpo.1-kirkwood (4.1.3-1~bpo8+1) from jessie-backports: missing dependency on updated flash-kernel package

2015-09-03 Thread Robert Schlabbach 
Package: linux-image-4.1.0-0.bpo.1-kirkwood
Version: 4.1.3-1~bpo8+1

Installing this package from the jessie-backports distribution "bricked" my 
QNAP TS-219P II. The Linux kernel no longer boots. Attaching a serial console 
revealed that the Linux kernel did not recognize the machine id.

Further investigation revealed that the flash-kernel package version 3.35 in 
debian jessie neglected to append the DTB to the Linux kernel when flashing it. 
flash-kernel package version 3.45 from the unstable distribution has additional 
entries in its database, stating that this machine needs to have a DTB appended 
for Linux kernel versions 3.17 or later.

Proposed fix: Add flash-kernel 3.45 to jessie-backports and add a dependency of 
any Linux kernels 3.17 or later on at least this package version.

Best Regards,
Robert Schlabbach

Bug#797881: QNAP TS-219P II: qcontrol no longer works after upgrading to linux-image-4.1.0-0.bpo.1-kirkwood

2015-09-03 Thread Robert Schlabbach 
Package: linux-image-4.1.0-0.bpo.1-kirkwood
Version: 4.1.3-1~bpo8+1
 
After installing this Linux kernel on my QNAP TS-219P II, qcontrol no longer 
works:
 
1. The status LED remains in red/green blink mode (as set by the boot loader). 
It should be set to solid green when the kernel is loaded.
2. The buzzer does not buzz. It should buzz when the kernel is loaded and when 
the kernel is shutting down.
 
Removing and reinstalling the qcontrol package did not help.
 
Solely reverting to the debian jessie kernel 3.16.7-ckt11-1+deb8u3 fixes these 
problems, i.e. the LED status is correctly set and the buzzer buzzes again.
 
Best Regards,
Robert Schlabbach

Bug#797023: Fwd: [3.16.y-ckt stable] Patch "s390/sclp: fix compile error" has been added to staging queue

2015-09-03 Thread Stephen Powell 
Forwarding the below message to the relevant Debian Bug Log

- Forwarded Message -
From: Luis Henriques 
To: Sebastian Ott 
Cc: Martin Schwidefsky , Stephen Powell 
, Luis Henriques , 
kernel-t...@lists.ubuntu.com
Sent: Thu, 03 Sep 2015 06:38:07 -0400 (EDT)
Subject: [3.16.y-ckt stable] Patch "s390/sclp: fix compile error" has been 
added to staging queue

This is a note to let you know that I have just added a patch titled

s390/sclp: fix compile error

to the linux-3.16.y-queue branch of the 3.16.y-ckt extended stable tree 
which can be found at:

http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.16.y-queue

This patch is scheduled to be released in version 3.16.7-ckt17.

If you, or anyone else, feels it should not be added to this tree, please 
reply to this email.

For more information about the 3.16.y-ckt tree, see
https://wiki.ubuntu.com/Kernel/Dev/ExtendedStable

Thanks.
-Luis

--

>From 2741d9ee96a36721b961a7c99594b1d9248e8edb Mon Sep 17 00:00:00 2001
From: Sebastian Ott 
Date: Thu, 25 Jun 2015 09:32:22 +0200
Subject: s390/sclp: fix compile error

commit a313bdc5310dd807655d3ca3eb2219cd65dfe45a upstream.

Fix this error when compiling with CONFIG_SMP=n and
CONFIG_DYNAMIC_DEBUG=y:

drivers/s390/char/sclp_early.c: In function 'sclp_read_info_early':
drivers/s390/char/sclp_early.c:87:19: error: 'EBUSY' undeclared (first use in 
this function)
   } while (rc == -EBUSY);
   ^

Signed-off-by: Sebastian Ott 
Signed-off-by: Martin Schwidefsky 
Cc: Stephen Powell 
Signed-off-by: Luis Henriques 
---
 drivers/s390/char/sclp_early.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/s390/char/sclp_early.c b/drivers/s390/char/sclp_early.c
index 1918d9dff45d..45c3d7041c81 100644
--- a/drivers/s390/char/sclp_early.c
+++ b/drivers/s390/char/sclp_early.c
@@ -7,6 +7,7 @@
 #define KMSG_COMPONENT "sclp_early"
 #define pr_fmt(fmt) KMSG_COMPONENT ": " fmt

+#include 
 #include 
 #include 
 #include 

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

Processed: Re: Bug#797955: initramfs-tools: initramfs fails to activate swap on encrypted LVM2 partition; fails boot

2015-09-03 Thread Debian Bug Tracking System 
Processing control commands:

> severity -1 important
Bug #797955 [initramfs-tools] initramfs-tools: initramfs fails to activate swap 
on encrypted LVM2 partition; fails boot
Severity set to 'important' from 'critical'
> reassign -1 lvm2
Bug #797955 [initramfs-tools] initramfs-tools: initramfs fails to activate swap 
on encrypted LVM2 partition; fails boot
Bug reassigned from package 'initramfs-tools' to 'lvm2'.
No longer marked as found in versions initramfs-tools/0.120.
Ignoring request to alter fixed versions of bug #797955 to the same values 
previously set

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

Bug#797955: initramfs-tools: initramfs fails to activate swap on encrypted LVM2 partition; fails boot

2015-09-03 Thread Ben Hutchings 
Control: severity -1 important
Control: reassign -1 lvm2

On Thu, 2015-09-03 at 23:30 +0200, Arnaud Installe wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: critical
> Justification: breaks the whole system
> 
> All my partitions (except /boot) are on encrypted LVM2 partitions.
> 
> When booting, initramfs asks for the passwords to unlock the /root & /usr
> partitions, which are mounted successfully. It then fails to ask for the swap
> partition password, instead looping a few minutes, posting messages that it is
> waiting for all volumes to become available and "/run/lvm/lvmetad.socket:
> connect failed". Disabling lvmetad did not help.
[...]

The initramfs has never been responsible for setting up the swap
partition.

It sounds like the fault is with lvm2 though it could be cryptsetup.

Reducing severity because this is not a normal configuration and you
have a workaround for it.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today, ignorance or apathy?
A.  I don't know and I couldn't care less.



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