linux-signed_3.4_source.changes ACCEPTED into unstable

2017-01-05 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Jan 2017 04:14:11 +
Source: linux-signed
Binary: kernel-image-4.8.0-2-amd64-di nic-modules-4.8.0-2-amd64-di 
nic-wireless-modules-4.8.0-2-amd64-di nic-shared-modules-4.8.0-2-amd64-di 
serial-modules-4.8.0-2-amd64-di usb-serial-modules-4.8.0-2-amd64-di 
ppp-modules-4.8.0-2-amd64-di pata-modules-4.8.0-2-amd64-di 
cdrom-core-modules-4.8.0-2-amd64-di firewire-core-modules-4.8.0-2-amd64-di 
scsi-core-modules-4.8.0-2-amd64-di scsi-modules-4.8.0-2-amd64-di 
loop-modules-4.8.0-2-amd64-di btrfs-modules-4.8.0-2-amd64-di 
ext4-modules-4.8.0-2-amd64-di isofs-modules-4.8.0-2-amd64-di 
jfs-modules-4.8.0-2-amd64-di ntfs-modules-4.8.0-2-amd64-di 
xfs-modules-4.8.0-2-amd64-di fat-modules-4.8.0-2-amd64-di 
md-modules-4.8.0-2-amd64-di multipath-modules-4.8.0-2-amd64-di 
usb-modules-4.8.0-2-amd64-di usb-storage-modules-4.8.0-2-amd64-di 
pcmcia-storage-modules-4.8.0-2-amd64-di fb-modules-4.8.0-2-amd64-di 
input-modules-4.8.0-2-amd64-di event-modules-4.8.0-2-amd64-di 
mouse-modules-4.8.0-2-amd64-di nic-pcmcia-modules-4.8.0-2-amd64-di
 pcmcia-modules-4.8.0-2-amd64-di nic-usb-modules-4.8.0-2-amd64-di 
sata-modules-4.8.0-2-amd64-di acpi-modules-4.8.0-2-amd64-di 
i2c-modules-4.8.0-2-amd64-di crc-modules-4.8.0-2-amd64-di 
crypto-modules-4.8.0-2-amd64-di crypto-dm-modules-4.8.0-2-amd64-di 
efi-modules-4.8.0-2-amd64-di ata-modules-4.8.0-2-amd64-di 
mmc-core-modules-4.8.0-2-amd64-di mmc-modules-4.8.0-2-amd64-di 
nbd-modules-4.8.0-2-amd64-di squashfs-modules-4.8.0-2-amd64-di 
speakup-modules-4.8.0-2-amd64-di virtio-modules-4.8.0-2-amd64-di 
uinput-modules-4.8.0-2-amd64-di sound-modules-4.8.0-2-amd64-di 
hyperv-modules-4.8.0-2-amd64-di udf-modules-4.8.0-2-amd64-di 
fuse-modules-4.8.0-2-amd64-di linux-image-4.8.0-2-amd64 
linux-image-4.8.0-2-rt-amd64 kernel-image-4.8.0-2-arm64-di 
nic-modules-4.8.0-2-arm64-di nic-wireless-modules-4.8.0-2-arm64-di 
nic-shared-modules-4.8.0-2-arm64-di ppp-modules-4.8.0-2-arm64-di 
cdrom-core-modules-4.8.0-2-arm64-di scsi-core-modules-4.8.0-2-arm64-di 
scsi-modules-4.8.0-2-arm64-di
 loop-modules-4.8.0-2-arm64-di btrfs-modules-4.8.0-2-arm64-di 
ext4-modules-4.8.0-2-arm64-di isofs-modules-4.8.0-2-arm64-di 
jfs-modules-4.8.0-2-arm64-di xfs-modules-4.8.0-2-arm64-di 
fat-modules-4.8.0-2-arm64-di md-modules-4.8.0-2-arm64-di 
multipath-modules-4.8.0-2-arm64-di usb-modules-4.8.0-2-arm64-di 
usb-storage-modules-4.8.0-2-arm64-di fb-modules-4.8.0-2-arm64-di 
input-modules-4.8.0-2-arm64-di event-modules-4.8.0-2-arm64-di 
nic-usb-modules-4.8.0-2-arm64-di sata-modules-4.8.0-2-arm64-di 
i2c-modules-4.8.0-2-arm64-di crc-modules-4.8.0-2-arm64-di 
crypto-modules-4.8.0-2-arm64-di crypto-dm-modules-4.8.0-2-arm64-di 
efi-modules-4.8.0-2-arm64-di ata-modules-4.8.0-2-arm64-di 
mmc-modules-4.8.0-2-arm64-di nbd-modules-4.8.0-2-arm64-di 
squashfs-modules-4.8.0-2-arm64-di virtio-modules-4.8.0-2-arm64-di 
uinput-modules-4.8.0-2-arm64-di leds-modules-4.8.0-2-arm64-di 
udf-modules-4.8.0-2-arm64-di fuse-modules-4.8.0-2-arm64-di 
linux-image-4.8.0-2-arm64 kernel-image-4.8.0-2-armmp-di
 nic-modules-4.8.0-2-armmp-di nic-wireless-modules-4.8.0-2-armmp-di 
nic-shared-modules-4.8.0-2-armmp-di ppp-modules-4.8.0-2-armmp-di 
pata-modules-4.8.0-2-armmp-di scsi-core-modules-4.8.0-2-armmp-di 
scsi-modules-4.8.0-2-armmp-di loop-modules-4.8.0-2-armmp-di 
btrfs-modules-4.8.0-2-armmp-di ext4-modules-4.8.0-2-armmp-di 
isofs-modules-4.8.0-2-armmp-di jfs-modules-4.8.0-2-armmp-di 
fat-modules-4.8.0-2-armmp-di md-modules-4.8.0-2-armmp-di 
multipath-modules-4.8.0-2-armmp-di usb-modules-4.8.0-2-armmp-di 
usb-storage-modules-4.8.0-2-armmp-di fb-modules-4.8.0-2-armmp-di 
input-modules-4.8.0-2-armmp-di event-modules-4.8.0-2-armmp-di 
nic-usb-modules-4.8.0-2-armmp-di sata-modules-4.8.0-2-armmp-di 
crc-modules-4.8.0-2-armmp-di crypto-modules-4.8.0-2-armmp-di 
crypto-dm-modules-4.8.0-2-armmp-di efi-modules-4.8.0-2-armmp-di 
ata-modules-4.8.0-2-armmp-di mmc-modules-4.8.0-2-armmp-di 
nbd-modules-4.8.0-2-armmp-di squashfs-modules-4.8.0-2-armmp-di 
virtio-modules-4.8.0-2-armmp-di
 uinput-modules-4.8.0-2-armmp-di zlib-modules-4.8.0-2-armmp-di 
leds-modules-4.8.0-2-armmp-di udf-modules-4.8.0-2-armmp-di 
fuse-modules-4.8.0-2-armmp-di mtd-modules-4.8.0-2-armmp-di 
linux-image-4.8.0-2-armmp linux-image-4.8.0-2-armmp-lpae 
kernel-image-4.8.0-2-686-di nic-modules-4.8.0-2-686-di 
nic-wireless-modules-4.8.0-2-686-di nic-shared-modules-4.8.0-2-686-di 
serial-modules-4.8.0-2-686-di usb-serial-modules-4.8.0-2-686-di 
ppp-modules-4.8.0-2-686-di pata-modules-4.8.0-2-686-di 
cdrom-core-modules-4.8.0-2-686-di firewire-core-modules-4.8.0-2-686-di 
scsi-core-modules-4.8.0-2-686-di scsi-modules-4.8.0-2-686-di 
loop-modules-4.8.0-2-686-di btrfs-modules-4.8.0-2-686-di 
ext4-modules-4.8.0-2-686-di isofs-modules-4.8.0-2-686-di 
jfs-modules-4.8.0-2-686-di ntfs-modules-4.8.0-2-686-di 
xfs-modules-4.8.0-2-686-di fat-modules-4.8.0-2-686-di md-modules-4.8.0-2-686-di 
multipath-modules-4.8.0-2-686-di 

Processing of linux-signed_3.4_source.changes

2017-01-05 Thread Debian FTP Masters
linux-signed_3.4_source.changes uploaded successfully to localhost
along with the files:
  linux-signed_3.4.dsc
  linux-signed_3.4.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)



Bug#846488: marked as done (linux-signed: broken Built-Using fields)

2017-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 04:52:09 +
with message-id 
and subject line Bug#846488: fixed in linux-signed 3.4
has caused the Debian Bug report #846488,
regarding linux-signed: broken Built-Using fields
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.)


-- 
846488: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-signed
Version: 3.2
Severity: important

Hi,

Your packages includes broken Built-Using fields, e.g.:

Package: linux-image-4.8.0-1-amd64
Source: linux-signed (3.2)
Built-Using: linux (4.8.7-1)

That should have been: linux (= 4.8.7-1)

See Debian Policy 7.8:

A Built-Using field must list the corresponding source package for any
such binary package incorporated during the build [56], including an
"exactly equal" ("=") version relation on the version that was used to
build that binary package[57].

Cheers,
Emilio

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

Kernel: Linux 4.7.0-1-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)
--- End Message ---
--- Begin Message ---
Source: linux-signed
Source-Version: 3.4

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 846...@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-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 06 Jan 2017 04:14:11 +
Source: linux-signed
Binary: kernel-image-4.8.0-2-amd64-di nic-modules-4.8.0-2-amd64-di 
nic-wireless-modules-4.8.0-2-amd64-di nic-shared-modules-4.8.0-2-amd64-di 
serial-modules-4.8.0-2-amd64-di usb-serial-modules-4.8.0-2-amd64-di 
ppp-modules-4.8.0-2-amd64-di pata-modules-4.8.0-2-amd64-di 
cdrom-core-modules-4.8.0-2-amd64-di firewire-core-modules-4.8.0-2-amd64-di 
scsi-core-modules-4.8.0-2-amd64-di scsi-modules-4.8.0-2-amd64-di 
loop-modules-4.8.0-2-amd64-di btrfs-modules-4.8.0-2-amd64-di 
ext4-modules-4.8.0-2-amd64-di isofs-modules-4.8.0-2-amd64-di 
jfs-modules-4.8.0-2-amd64-di ntfs-modules-4.8.0-2-amd64-di 
xfs-modules-4.8.0-2-amd64-di fat-modules-4.8.0-2-amd64-di 
md-modules-4.8.0-2-amd64-di multipath-modules-4.8.0-2-amd64-di 
usb-modules-4.8.0-2-amd64-di usb-storage-modules-4.8.0-2-amd64-di 
pcmcia-storage-modules-4.8.0-2-amd64-di fb-modules-4.8.0-2-amd64-di 
input-modules-4.8.0-2-amd64-di event-modules-4.8.0-2-amd64-di 
mouse-modules-4.8.0-2-amd64-di nic-pcmcia-modules-4.8.0-2-amd64-di
 pcmcia-modules-4.8.0-2-amd64-di nic-usb-modules-4.8.0-2-amd64-di 
sata-modules-4.8.0-2-amd64-di acpi-modules-4.8.0-2-amd64-di 
i2c-modules-4.8.0-2-amd64-di crc-modules-4.8.0-2-amd64-di 
crypto-modules-4.8.0-2-amd64-di crypto-dm-modules-4.8.0-2-amd64-di 
efi-modules-4.8.0-2-amd64-di ata-modules-4.8.0-2-amd64-di 
mmc-core-modules-4.8.0-2-amd64-di mmc-modules-4.8.0-2-amd64-di 
nbd-modules-4.8.0-2-amd64-di squashfs-modules-4.8.0-2-amd64-di 
speakup-modules-4.8.0-2-amd64-di virtio-modules-4.8.0-2-amd64-di 
uinput-modules-4.8.0-2-amd64-di sound-modules-4.8.0-2-amd64-di 
hyperv-modules-4.8.0-2-amd64-di udf-modules-4.8.0-2-amd64-di 
fuse-modules-4.8.0-2-amd64-di linux-image-4.8.0-2-amd64 
linux-image-4.8.0-2-rt-amd64 kernel-image-4.8.0-2-arm64-di 
nic-modules-4.8.0-2-arm64-di nic-wireless-modules-4.8.0-2-arm64-di 
nic-shared-modules-4.8.0-2-arm64-di ppp-modules-4.8.0-2-arm64-di 
cdrom-core-modules-4.8.0-2-arm64-di scsi-core-modules-4.8.0-2-arm64-di 
scsi-modules-4.8.0-2-arm64-di
 loop-modules-4.8.0-2-arm64-di btrfs-modules-4.8.0-2-arm64-di 
ext4-modules-4.8.0-2-arm64-di isofs-modules-4.8.0-2-arm64-di 
jfs-modules-4.8.0-2-arm64-di xfs-modules-4.8.0-2-arm64-di 
fat-modules-4.8.0-2-arm64-di md-modules-4.8.0-2-arm64-di 

Bug#850380: marked as done (firmware-brcm80211 breaks wlan0 on Raspbian)

2017-01-05 Thread Debian Bug Tracking System
Your message dated Fri, 06 Jan 2017 04:17:43 +
with message-id <1483676263.3983.102.ca...@decadent.org.uk>
and subject line Re: Bug#850380: firmware-brcm80211 breaks wlan0 on Raspbian
has caused the Debian Bug report #850380,
regarding firmware-brcm80211 breaks wlan0 on Raspbian
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.)


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

Package: firmware-brcm80211
Version: 20161130-2 (testing)

After upgrading Raspbian from jessie to testing wlan0 disappears on a 
Raspberry Pi 3 with a similar error message reported in e.g. Debian Bug 
#821400 or at 
https://www.raspberrypi.org/forums/viewtopic.php?f=28=138629=25:
brcmfmac_sdio mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43430-sdio.bin failed with error -2


After downgrading to version: 043+rpi5 (stable) wlan0 appears and works 
again.


043+rpi5 (stable) provides the same version of brcmfmac43430-sdio.bin 
found at 
https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211/brcm/. 
20161130-2 (testing) provides something else that doesn't work on a 
Raspberry Pi 3.


I wonder if this package could be changed to have wireless working on a 
Raspberry Pi.


I am using Raspbian GNU/Linux stretch/sid with kernel 4.4.38-v7+ #938 
SMP Thu Dec 15 15:22:21 GMT 2016 armv7l.
--- End Message ---
--- Begin Message ---
On Fri, 2017-01-06 at 04:13 +0100, Frank Breitling wrote:
> Package: firmware-brcm80211
> Version: 20161130-2 (testing)
> 
> After upgrading Raspbian from jessie to testing wlan0 disappears on a 
> Raspberry Pi 3 with a similar error message reported in e.g. Debian Bug 
> #821400 or at 
> https://www.raspberrypi.org/forums/viewtopic.php?f=28=138629=25:
> brcmfmac_sdio mmc1:0001:1: Direct firmware load for 
> brcm/brcmfmac43430-sdio.bin failed with error -2
> 
> After downgrading to version: 043+rpi5 (stable) wlan0 appears and works 
> again.
> 
> 043+rpi5 (stable) provides the same version of brcmfmac43430-sdio.bin 
> found at 
> https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211/brcm/. 
> 20161130-2 (testing) provides something else that doesn't work on a 
> Raspberry Pi 3.
> 
> I wonder if this package could be changed to have wireless working on a 
> Raspberry Pi.
> 
> I am using Raspbian GNU/Linux stretch/sid with kernel 4.4.38-v7+ #938 
> SMP Thu Dec 15 15:22:21 GMT 2016 armv7l.

Then you need to report this to Raspbian, not to Debian.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert
Coveyou



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


Bug#850380: firmware-brcm80211 breaks wlan0 on Raspbian

2017-01-05 Thread Frank Breitling

Package: firmware-brcm80211
Version: 20161130-2 (testing)

After upgrading Raspbian from jessie to testing wlan0 disappears on a 
Raspberry Pi 3 with a similar error message reported in e.g. Debian Bug 
#821400 or at 
https://www.raspberrypi.org/forums/viewtopic.php?f=28=138629=25:
brcmfmac_sdio mmc1:0001:1: Direct firmware load for 
brcm/brcmfmac43430-sdio.bin failed with error -2


After downgrading to version: 043+rpi5 (stable) wlan0 appears and works 
again.


043+rpi5 (stable) provides the same version of brcmfmac43430-sdio.bin 
found at 
https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm80211/brcm/. 
20161130-2 (testing) provides something else that doesn't work on a 
Raspberry Pi 3.


I wonder if this package could be changed to have wireless working on a 
Raspberry Pi.


I am using Raspbian GNU/Linux stretch/sid with kernel 4.4.38-v7+ #938 
SMP Thu Dec 15 15:22:21 GMT 2016 armv7l.




Buildd selection for linux on powerpc

2017-01-05 Thread Ben Hutchings
Please can you arrange that linux is not built on porpora or poulenc? 
It takes much longer to build there, and this delays preparation of the
linux-signed package.

Alternately, I can disable module signing for powerpc.  (It will have
to be disabled anyway if powerpc is moved from the main archive to
debian-ports.)

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert
Coveyou



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


Bug#850339: initramfs-tools: Support Linux Integrity

2017-01-05 Thread Stefan Berger
Package: initramfs-tools
Version: 0.103ubuntu4.3
Severity: wishlist

Linux implements the Integrity Measurement Architecture (IMA) and the Extended
Verfication Module (EVM).

IMA measures application and libraries as they are started and, using a policy,
it can also verify the signatures associated with the applications and
libraries. For this to work the operating system has load a policy and keys
into the kernel. This should be done when the system is booted.

EVM protects file metadata against offline tampering. It does this by signing
(HMAC, public key signature) file attributes. For this to work the operating
system has to load the key used for verfication and signing into the kernel.
This should be done when the system is booted.



-- Package-specific info:
-- initramfs sizes
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.2.0-18-generic root=/dev/mapper/sbct--5--vg-root ro

-- resume
RESUME=/dev/mapper/sbct--5--vg-swap_1
-- /proc/filesystems
ext3
ext2
ext4
vfat
fuseblk
btrfs

-- lsmod
Module  Size  Used by
binfmt_misc20480  1 
xt_recent  20480  0 
xt_nat 16384  1 
veth   16384  0 
ipt_MASQUERADE 16384  21 
nf_nat_masquerade_ipv416384  1 ipt_MASQUERADE
iptable_nat16384  1 
nf_nat_ipv416384  1 iptable_nat
br_netfilter   24576  0 
bridge114688  1 br_netfilter
stp16384  1 bridge
llc16384  2 stp,bridge
pci_stub   16384  1 
vboxpci24576  0 
vboxnetadp 28672  0 
vboxnetflt 28672  0 
vboxdrv   413696  3 vboxnetadp,vboxnetflt,vboxpci
cmac   16384  0 
rmd160 20480  0 
dm_thin_pool   61440  3 
dm_persistent_data 65536  1 dm_thin_pool
dm_bio_prison  16384  1 dm_thin_pool
dm_bufio   28672  1 dm_persistent_data
libcrc32c  16384  1 dm_persistent_data
joydev 20480  0 
xfrm_user  32768  2 
ah620480  0 
ah416384  0 
esp6   20480  0 
esp4   20480  0 
xfrm4_mode_beet16384  0 
xfrm4_tunnel   16384  0 
tunnel416384  1 xfrm4_tunnel
xfrm4_mode_tunnel  16384  0 
xfrm4_mode_transport16384  0 
xfrm6_mode_transport16384  0 
xfrm6_mode_ro  16384  0 
xfrm6_mode_beet16384  0 
xfrm6_mode_tunnel  16384  0 
ipcomp 16384  0 
ipcomp616384  0 
xfrm6_tunnel   16384  1 ipcomp6
tunnel616384  1 xfrm6_tunnel
xfrm_ipcomp16384  2 ipcomp,ipcomp6
af_key 36864  0 
xfrm_algo  16384  7 ah4,ah6,esp4,esp6,af_key,xfrm_user,xfrm_ipcomp
camellia_generic   32768  0 
camellia_x86_6453248  0 
cast6_generic  24576  0 
cast5_generic  24576  0 
cast_common16384  2 cast5_generic,cast6_generic
deflate16384  0 
cts16384  0 
ctr16384  0 
gcm20480  0 
crypto_null16384  1 gcm
ccm20480  0 
serpent_sse2_x86_6453248  0 
serpent_generic32768  1 serpent_sse2_x86_64
blowfish_generic   16384  0 
blowfish_x86_6424576  0 
blowfish_common20480  2 blowfish_generic,blowfish_x86_64
twofish_generic20480  0 
twofish_x86_64_3way28672  0 
xts16384  3 
camellia_x86_64,serpent_sse2_x86_64,twofish_x86_64_3way
twofish_x86_64 16384  1 twofish_x86_64_3way
twofish_common 24576  3 
twofish_generic,twofish_x86_64_3way,twofish_x86_64
xcbc   16384  0 
sha256_ssse3   24576  0 
sha512_ssse3   45056  0 
des_generic24576  0 
ip6t_REJECT16384  1 
nf_reject_ipv6 16384  1 ip6t_REJECT
nf_log_ipv616384  5 
xt_hl  16384  6 
ip6t_rt16384  3 
nf_conntrack_ipv6  20480  8 
nf_defrag_ipv6 36864  1 nf_conntrack_ipv6
ipt_REJECT 16384  1 
nf_reject_ipv4 16384  1 ipt_REJECT
nf_log_ipv416384  5 
nf_log_common  16384  2 nf_log_ipv4,nf_log_ipv6
xt_LOG 16384  10 
xt_limit   16384  13 
xt_tcpudp  16384  30 
xt_addrtype16384  6 
nf_conntrack_ipv4  16384  28 
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
xt_conntrack   16384  35 
ip6table_filter16384  1 
ip6_tables 28672  1 ip6table_filter
cdc_ether  16384  0 
usbnet 40960  1 cdc_ether
input_leds 16384  0 
mii16384  1 usbnet
nf_conntrack_netbios_ns16384  0 
nf_conntrack_broadcast16384  1 nf_conntrack_netbios_ns
nf_nat_ftp 16384  0 
nf_nat 24576  4 
nf_nat_ftp,nf_nat_ipv4,xt_nat,nf_nat_masquerade_ipv4

Re: LED on keyboard

2017-01-05 Thread Ben Hutchings
On Fri, 2017-01-06 at 00:38 +0100, Jan Niggemann wrote:
> Hello,
> 
> I'm building a 4.8.15 kernel (which is working great) for my Thinkpad  
> T460s. What bothers me, is that I can't get the LEDs on the F1 and F4  
> key working ((F1=mute, F4=mic on/off). I checked CONFIG_ directives  
> that seem relevant to me, but - well, I'm missing something. I have  
> enabled LED-related options as well as GPIO options.

I don't think these are controlled by an LED class driver.

> The relevant LEDs work fine using the backports 4.8 kernel  
> (4.8.0-0.bpo.2-amd64 #1 SMP Debian 4.8.11-1~bpo8+1 (2016-12-14) x86_64  
> GNU/Linux). I have diffed both configs, but didn't spot the relevant  
> option.
> 
> Which driver is needed for this, or which CONFIG_ directive?
> I'd be grateful for a pointer in the right direction on this.

Check CONFIG_THINKPAD_ACPI and related config symbols.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert
Coveyou



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


LED on keyboard

2017-01-05 Thread Jan Niggemann

Hello,

I'm building a 4.8.15 kernel (which is working great) for my Thinkpad  
T460s. What bothers me, is that I can't get the LEDs on the F1 and F4  
key working ((F1=mute, F4=mic on/off). I checked CONFIG_ directives  
that seem relevant to me, but - well, I'm missing something. I have  
enabled LED-related options as well as GPIO options.


The relevant LEDs work fine using the backports 4.8 kernel  
(4.8.0-0.bpo.2-amd64 #1 SMP Debian 4.8.11-1~bpo8+1 (2016-12-14) x86_64  
GNU/Linux). I have diffed both configs, but didn't spot the relevant  
option.


Which driver is needed for this, or which CONFIG_ directive?
I'd be grateful for a pointer in the right direction on this.

Best regards
jan

--
gpg --keyserver pgp.mit.edu --recv-keys 0x514FCA9C
F013 93C0 306C 1E31 4E00  09FA 21EC A2F6 514F CA9C



Processed: [bts-link] source package src:linux

2017-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #840678 (http://bugs.debian.org/840678)
> # Bug title: linux-image-3.16.0-4-amd64: Kernel Bug 109051 - 
> intel_idle.max_cstate=1
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=109051
> #  * remote status changed: (?) -> NEEDINFO
> usertags 840678 + status-NEEDINFO
There were no usertags set.
Usertags are now: status-NEEDINFO.
> # remote status report for #840678 (http://bugs.debian.org/840678)
> # Bug title: linux-image-3.16.0-4-amd64: Kernel Bug 109051 - 
> intel_idle.max_cstate=1
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=109051
> #  * remote status changed: (?) -> NEEDINFO
> usertags 840678 + status-NEEDINFO
Usertags were: status-NEEDINFO.
Usertags are now: status-NEEDINFO.
> # remote status report for #846792 (http://bugs.debian.org/846792)
> # Bug title: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=70891
> #  * remote status changed: (?) -> CLOSED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 846792 + fixed-upstream
Bug #846792 [src:linux] linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay 
on boot
Added tag(s) fixed-upstream.
> usertags 846792 + status-CLOSED resolution-CODE-FIX
There were no usertags set.
Usertags are now: status-CLOSED resolution-CODE-FIX.
> # remote status report for #848967 (http://bugs.debian.org/848967)
> # Bug title: linux-image: Power button of Dell XPS13 does not send any events
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=190871
> #  * remote status changed: NEEDINFO -> RESOLVED
> #  * remote resolution changed: (?) -> INVALID
> #  * closed upstream
> tags 848967 + fixed-upstream
Bug #848967 {Done: Ben Hutchings } [src:linux] 
linux-image: Power button of Dell XPS13 does not send any events
Added tag(s) fixed-upstream.
> usertags 848967 - status-NEEDINFO
Usertags were: status-NEEDINFO.
Usertags are now: .
> usertags 848967 + status-RESOLVED resolution-INVALID
There were no usertags set.
Usertags are now: status-RESOLVED resolution-INVALID.
> thanks
Stopping processing here.

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



Bug#845075: kernel-image-4.8.0-1-armmp-di: Lamobo R1 cannot access network

2017-01-05 Thread Heinrich Schuchardt
On 01/05/2017 08:52 AM, Vagrant Cascadian wrote:
> On 2017-01-04, Ben Hutchings wrote:
>>> I want to install Debian Stretch on my Lamobo R1 using the network
>>> installer.
>>>
>>> It is unable to connect to the DHCP server.
>>>
>>> Please, add the b53 module to the kernel.
>>>
>>> CONFIG_B53=y
>>> CONFIG_B53_SPI_DRIVER=y
>>
>> I think we already enabled the necessary options:
>>
>>   * [armhf] dsa: Enable drivers for Lamobo R1 (aka BPi-R1): B53,
>> B53_MDIO_DRIVER as modules (Closes: #836231, thanks to Vagrant Cascadian)
>>
>> From the device tree, it seems pretty clear that we do want
>> B53_MDIO_DRIVER and not B53_SPI_DRIVER.  Are you sure the installer
>> version you used had a verison 4.8 kernel, not 4.7?

I used
https://d-i.debian.org/daily-images/armhf/daily/netboot/SD-card-images/
as of 2016-11-20.

According to
https://packages.qa.debian.org/l/linux-signed/news/20161116T173404Z.html
on Debian was using Kernel 4.8 since 2016-11-16.

> 
> I had very mixed luck with the switch driver with 4.7.x and 4.8.x, but
> ethernet generally worked ok. With 4.9.x, I was able to get all ports
> working well.
> 
> Were you plugging into the WAN port, or one of the switch ports?

I tried both, none worked.

> 
> Is the b53 module listed in nic-modules udeb? I don't see mention of it
> at a quick glance, or is it pulled in with some globbing?
> 
> 
> live well,
>   vagrant
> 
> p.s. I've haven't been tracking the udebs as much lately, tired of
> playing whack-a-mole with the exact right modules in the exact right
> udeb... instead I've been manually appending all the drivers into the
> initrd as an additional cpio archive...
> 




signature.asc
Description: OpenPGP digital signature


Processed: Re: Bug#845075: kernel-image-4.8.0-1-armmp-di: Lamobo R1 cannot access network

2017-01-05 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 - moreinfo
Bug #845075 [src:linux] kernel-image-4.8.0-1-armmp-di: Lamobo R1 cannot access 
network
Removed tag(s) moreinfo.

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



Bug#845075: kernel-image-4.8.0-1-armmp-di: Lamobo R1 cannot access network

2017-01-05 Thread Ben Hutchings
Control: tag -1 - moreinfo

On Wed, 2017-01-04 at 23:52 -0800, Vagrant Cascadian wrote:
> On 2017-01-04, Ben Hutchings wrote:
> > > I want to install Debian Stretch on my Lamobo R1 using the network
> > > installer.
> > > 
> > > It is unable to connect to the DHCP server.
> > > 
> > > Please, add the b53 module to the kernel.
> > > 
> > > CONFIG_B53=y
> > > CONFIG_B53_SPI_DRIVER=y
> > 
> > I think we already enabled the necessary options:
> > 
> >   * [armhf] dsa: Enable drivers for Lamobo R1 (aka BPi-R1): B53,
> > B53_MDIO_DRIVER as modules (Closes: #836231, thanks to Vagrant 
> > Cascadian)
> > 
> > From the device tree, it seems pretty clear that we do want
> > B53_MDIO_DRIVER and not B53_SPI_DRIVER.  Are you sure the installer
> > version you used had a verison 4.8 kernel, not 4.7?
> 
> I had very mixed luck with the switch driver with 4.7.x and 4.8.x, but
> ethernet generally worked ok. With 4.9.x, I was able to get all ports
> working well.
> 
> Were you plugging into the WAN port, or one of the switch ports?
> 
> Is the b53 module listed in nic-modules udeb? I don't see mention of it
> at a quick glance, or is it pulled in with some globbing?

Oh, good point, we don't include it because it's under drivers/net/dsa/
and not drivers/net/ethernet/.  I'll fix that.

Ben.

> p.s. I've haven't been tracking the udebs as much lately, tired of
> playing whack-a-mole with the exact right modules in the exact right
> udeb... instead I've been manually appending all the drivers into the
> initrd as an additional cpio archive...
-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of
incompetence.



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


linux_4.8.15-2_multi.changes ACCEPTED into unstable, unstable

2017-01-05 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Jan 2017 19:39:36 +
Source: linux
Binary: linux-source-4.8 linux-support-4.8.0-2 linux-doc-4.8 linux-manual-4.8 
linux-kbuild-4.8 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.8 
libusbip-dev usbip hyperv-daemons linux-libc-dev linux-headers-4.8.0-2-all 
linux-headers-4.8.0-2-all-alpha kernel-image-4.8.0-2-alpha-generic-di 
nic-modules-4.8.0-2-alpha-generic-di 
nic-wireless-modules-4.8.0-2-alpha-generic-di 
nic-shared-modules-4.8.0-2-alpha-generic-di 
serial-modules-4.8.0-2-alpha-generic-di 
usb-serial-modules-4.8.0-2-alpha-generic-di 
ppp-modules-4.8.0-2-alpha-generic-di pata-modules-4.8.0-2-alpha-generic-di 
cdrom-core-modules-4.8.0-2-alpha-generic-di 
scsi-core-modules-4.8.0-2-alpha-generic-di 
scsi-modules-4.8.0-2-alpha-generic-di loop-modules-4.8.0-2-alpha-generic-di 
btrfs-modules-4.8.0-2-alpha-generic-di ext4-modules-4.8.0-2-alpha-generic-di 
isofs-modules-4.8.0-2-alpha-generic-di jfs-modules-4.8.0-2-alpha-generic-di 
xfs-modules-4.8.0-2-alpha-generic-di fat-modules-4.8.0-2-alpha-generic-di
 md-modules-4.8.0-2-alpha-generic-di multipath-modules-4.8.0-2-alpha-generic-di 
usb-modules-4.8.0-2-alpha-generic-di 
usb-storage-modules-4.8.0-2-alpha-generic-di 
fb-modules-4.8.0-2-alpha-generic-di input-modules-4.8.0-2-alpha-generic-di 
event-modules-4.8.0-2-alpha-generic-di mouse-modules-4.8.0-2-alpha-generic-di 
nic-pcmcia-modules-4.8.0-2-alpha-generic-di 
pcmcia-modules-4.8.0-2-alpha-generic-di 
nic-usb-modules-4.8.0-2-alpha-generic-di sata-modules-4.8.0-2-alpha-generic-di 
crc-modules-4.8.0-2-alpha-generic-di crypto-modules-4.8.0-2-alpha-generic-di 
crypto-dm-modules-4.8.0-2-alpha-generic-di ata-modules-4.8.0-2-alpha-generic-di 
nbd-modules-4.8.0-2-alpha-generic-di squashfs-modules-4.8.0-2-alpha-generic-di 
virtio-modules-4.8.0-2-alpha-generic-di zlib-modules-4.8.0-2-alpha-generic-di 
fuse-modules-4.8.0-2-alpha-generic-di srm-modules-4.8.0-2-alpha-generic-di 
linux-headers-4.8.0-2-common linux-image-4.8.0-2-alpha-generic 
linux-headers-4.8.0-2-alpha-generic
 linux-image-4.8.0-2-alpha-generic-dbgsym linux-image-4.8.0-2-alpha-smp 
linux-headers-4.8.0-2-alpha-smp linux-image-4.8.0-2-alpha-smp-dbgsym 
linux-headers-4.8.0-2-all-amd64 linux-image-4.8.0-2-amd64-unsigned 
linux-headers-4.8.0-2-amd64 linux-image-4.8.0-2-amd64-dbgsym 
xen-linux-system-4.8.0-2-amd64 linux-headers-4.8.0-2-common-rt 
linux-image-4.8.0-2-rt-amd64-unsigned linux-headers-4.8.0-2-rt-amd64 
linux-image-4.8.0-2-rt-amd64-dbgsym linux-headers-4.8.0-2-all-arm64 
linux-image-4.8.0-2-arm64-unsigned linux-headers-4.8.0-2-arm64 
linux-image-4.8.0-2-arm64-dbgsym linux-headers-4.8.0-2-all-armel 
kernel-image-4.8.0-2-marvell-di nic-modules-4.8.0-2-marvell-di 
nic-shared-modules-4.8.0-2-marvell-di usb-serial-modules-4.8.0-2-marvell-di 
ppp-modules-4.8.0-2-marvell-di cdrom-core-modules-4.8.0-2-marvell-di 
scsi-core-modules-4.8.0-2-marvell-di loop-modules-4.8.0-2-marvell-di 
ipv6-modules-4.8.0-2-marvell-di btrfs-modules-4.8.0-2-marvell-di 
ext4-modules-4.8.0-2-marvell-di
 isofs-modules-4.8.0-2-marvell-di jffs2-modules-4.8.0-2-marvell-di 
jfs-modules-4.8.0-2-marvell-di fat-modules-4.8.0-2-marvell-di 
minix-modules-4.8.0-2-marvell-di md-modules-4.8.0-2-marvell-di 
multipath-modules-4.8.0-2-marvell-di usb-modules-4.8.0-2-marvell-di 
usb-storage-modules-4.8.0-2-marvell-di fb-modules-4.8.0-2-marvell-di 
input-modules-4.8.0-2-marvell-di event-modules-4.8.0-2-marvell-di 
mouse-modules-4.8.0-2-marvell-di nic-usb-modules-4.8.0-2-marvell-di 
sata-modules-4.8.0-2-marvell-di crc-modules-4.8.0-2-marvell-di 
crypto-modules-4.8.0-2-marvell-di crypto-dm-modules-4.8.0-2-marvell-di 
mmc-modules-4.8.0-2-marvell-di nbd-modules-4.8.0-2-marvell-di 
squashfs-modules-4.8.0-2-marvell-di uinput-modules-4.8.0-2-marvell-di 
zlib-modules-4.8.0-2-marvell-di leds-modules-4.8.0-2-marvell-di 
udf-modules-4.8.0-2-marvell-di fuse-modules-4.8.0-2-marvell-di 
mtd-modules-4.8.0-2-marvell-di kernel-image-4.8.0-2-versatile-di 
nic-modules-4.8.0-2-versatile-di
 nic-shared-modules-4.8.0-2-versatile-di 
usb-serial-modules-4.8.0-2-versatile-di ppp-modules-4.8.0-2-versatile-di 
cdrom-core-modules-4.8.0-2-versatile-di scsi-core-modules-4.8.0-2-versatile-di 
scsi-modules-4.8.0-2-versatile-di loop-modules-4.8.0-2-versatile-di 
btrfs-modules-4.8.0-2-versatile-di ext4-modules-4.8.0-2-versatile-di 
isofs-modules-4.8.0-2-versatile-di fat-modules-4.8.0-2-versatile-di 
md-modules-4.8.0-2-versatile-di multipath-modules-4.8.0-2-versatile-di 
usb-modules-4.8.0-2-versatile-di usb-storage-modules-4.8.0-2-versatile-di 
nic-usb-modules-4.8.0-2-versatile-di sata-modules-4.8.0-2-versatile-di 
crc-modules-4.8.0-2-versatile-di crypto-modules-4.8.0-2-versatile-di 
crypto-dm-modules-4.8.0-2-versatile-di nbd-modules-4.8.0-2-versatile-di 
squashfs-modules-4.8.0-2-versatile-di virtio-modules-4.8.0-2-versatile-di 
zlib-modules-4.8.0-2-versatile-di udf-modules-4.8.0-2-versatile-di 
fuse-modules-4.8.0-2-versatile-di 

Bug#849674: marked as done (linux-latest: Add Dell modules)

2017-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2017 16:00:10 +
with message-id 
and subject line Bug#849674: fixed in linux 4.8.15-2
has caused the Debian Bug report #849674,
regarding linux-latest: Add Dell modules
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.)


-- 
849674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-latest
Severity: wishlist

Dear Maintainer,

I've recently bought a Dell XPS 13 (9360). Before installing Debian, I
saw under Fedora that the keyboard backlight was configurable in
gnome-settings (under Power).

After my Sid installation, this option was not available.

Apparently, the current kernel shipped with unstable lacks some modules
(at least dell-laptop and dell-led).

Is it possible to add them to the debian linux image ?

Thanks

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

Kernel: Linux 4.9.0-rc8-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.8.15-2

We believe that the bug you reported is fixed in the latest version of
linux, 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 849...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Jan 2017 19:39:36 +
Source: linux
Binary: linux-source-4.8 linux-support-4.8.0-2 linux-doc-4.8 linux-manual-4.8 
linux-kbuild-4.8 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.8 
libusbip-dev usbip hyperv-daemons linux-libc-dev linux-headers-4.8.0-2-all 
linux-headers-4.8.0-2-all-alpha kernel-image-4.8.0-2-alpha-generic-di 
nic-modules-4.8.0-2-alpha-generic-di 
nic-wireless-modules-4.8.0-2-alpha-generic-di 
nic-shared-modules-4.8.0-2-alpha-generic-di 
serial-modules-4.8.0-2-alpha-generic-di 
usb-serial-modules-4.8.0-2-alpha-generic-di 
ppp-modules-4.8.0-2-alpha-generic-di pata-modules-4.8.0-2-alpha-generic-di 
cdrom-core-modules-4.8.0-2-alpha-generic-di 
scsi-core-modules-4.8.0-2-alpha-generic-di 
scsi-modules-4.8.0-2-alpha-generic-di loop-modules-4.8.0-2-alpha-generic-di 
btrfs-modules-4.8.0-2-alpha-generic-di ext4-modules-4.8.0-2-alpha-generic-di 
isofs-modules-4.8.0-2-alpha-generic-di jfs-modules-4.8.0-2-alpha-generic-di 
xfs-modules-4.8.0-2-alpha-generic-di fat-modules-4.8.0-2-alpha-generic-di
 md-modules-4.8.0-2-alpha-generic-di multipath-modules-4.8.0-2-alpha-generic-di 
usb-modules-4.8.0-2-alpha-generic-di 
usb-storage-modules-4.8.0-2-alpha-generic-di 
fb-modules-4.8.0-2-alpha-generic-di input-modules-4.8.0-2-alpha-generic-di 
event-modules-4.8.0-2-alpha-generic-di mouse-modules-4.8.0-2-alpha-generic-di 
nic-pcmcia-modules-4.8.0-2-alpha-generic-di 
pcmcia-modules-4.8.0-2-alpha-generic-di 
nic-usb-modules-4.8.0-2-alpha-generic-di sata-modules-4.8.0-2-alpha-generic-di 
crc-modules-4.8.0-2-alpha-generic-di crypto-modules-4.8.0-2-alpha-generic-di 
crypto-dm-modules-4.8.0-2-alpha-generic-di ata-modules-4.8.0-2-alpha-generic-di 
nbd-modules-4.8.0-2-alpha-generic-di squashfs-modules-4.8.0-2-alpha-generic-di 
virtio-modules-4.8.0-2-alpha-generic-di zlib-modules-4.8.0-2-alpha-generic-di 
fuse-modules-4.8.0-2-alpha-generic-di srm-modules-4.8.0-2-alpha-generic-di 
linux-headers-4.8.0-2-common linux-image-4.8.0-2-alpha-generic 
linux-headers-4.8.0-2-alpha-generic
 linux-image-4.8.0-2-alpha-generic-dbgsym linux-image-4.8.0-2-alpha-smp 
linux-headers-4.8.0-2-alpha-smp linux-image-4.8.0-2-alpha-smp-dbgsym 
linux-headers-4.8.0-2-all-amd64 linux-image-4.8.0-2-amd64-unsigned 
linux-headers-4.8.0-2-amd64 linux-image-4.8.0-2-amd64-dbgsym 
xen-linux-system-4.8.0-2-amd64 linux-headers-4.8.0-2-common-rt 
linux-image-4.8.0-2-rt-amd64-unsigned linux-headers-4.8.0-2-rt-amd64 

Bug#848851: marked as done (linux: FTBFS on ppc64el)

2017-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2017 16:00:10 +
with message-id 
and subject line Bug#848851: fixed in linux 4.8.15-2
has caused the Debian Bug report #848851,
regarding linux: FTBFS on ppc64el
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.)


-- 
848851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.8.15-1
Severity: serious
Justification: FTBFS

Hi

src:linux 4.8.15-1 FTBFS on ppc64el.

Log: 
https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64el=4.8.15-1=1482184049

[...]
  CC  crypto/af_alg.mod.o
  CC  crypto/algif_aead.mod.o
ld: arch/powerpc/boot/zImage.pseries: Not enough room for program headers, try 
linking with -N
ld: final link failed: Bad value
/«PKGBUILDDIR»/arch/powerpc/boot/Makefile:323: recipe for target 
'arch/powerpc/boot/zImage.pseries' failed
make[6]: *** [arch/powerpc/boot/zImage.pseries] Error 1
make[6]: *** Waiting for unfinished jobs
  CC  crypto/algif_hash.mod.o
arch/powerpc/Makefile:285: recipe for target 'zImage' failed
make[5]: *** [zImage] Error 2
make[5]: *** Waiting for unfinished jobs
  CC  crypto/algif_skcipher.mod.o
[...]

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.8.15-2

We believe that the bug you reported is fixed in the latest version of
linux, 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 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Jan 2017 19:39:36 +
Source: linux
Binary: linux-source-4.8 linux-support-4.8.0-2 linux-doc-4.8 linux-manual-4.8 
linux-kbuild-4.8 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.8 
libusbip-dev usbip hyperv-daemons linux-libc-dev linux-headers-4.8.0-2-all 
linux-headers-4.8.0-2-all-alpha kernel-image-4.8.0-2-alpha-generic-di 
nic-modules-4.8.0-2-alpha-generic-di 
nic-wireless-modules-4.8.0-2-alpha-generic-di 
nic-shared-modules-4.8.0-2-alpha-generic-di 
serial-modules-4.8.0-2-alpha-generic-di 
usb-serial-modules-4.8.0-2-alpha-generic-di 
ppp-modules-4.8.0-2-alpha-generic-di pata-modules-4.8.0-2-alpha-generic-di 
cdrom-core-modules-4.8.0-2-alpha-generic-di 
scsi-core-modules-4.8.0-2-alpha-generic-di 
scsi-modules-4.8.0-2-alpha-generic-di loop-modules-4.8.0-2-alpha-generic-di 
btrfs-modules-4.8.0-2-alpha-generic-di ext4-modules-4.8.0-2-alpha-generic-di 
isofs-modules-4.8.0-2-alpha-generic-di jfs-modules-4.8.0-2-alpha-generic-di 
xfs-modules-4.8.0-2-alpha-generic-di fat-modules-4.8.0-2-alpha-generic-di
 md-modules-4.8.0-2-alpha-generic-di multipath-modules-4.8.0-2-alpha-generic-di 
usb-modules-4.8.0-2-alpha-generic-di 
usb-storage-modules-4.8.0-2-alpha-generic-di 
fb-modules-4.8.0-2-alpha-generic-di input-modules-4.8.0-2-alpha-generic-di 
event-modules-4.8.0-2-alpha-generic-di mouse-modules-4.8.0-2-alpha-generic-di 
nic-pcmcia-modules-4.8.0-2-alpha-generic-di 
pcmcia-modules-4.8.0-2-alpha-generic-di 
nic-usb-modules-4.8.0-2-alpha-generic-di sata-modules-4.8.0-2-alpha-generic-di 
crc-modules-4.8.0-2-alpha-generic-di crypto-modules-4.8.0-2-alpha-generic-di 
crypto-dm-modules-4.8.0-2-alpha-generic-di ata-modules-4.8.0-2-alpha-generic-di 
nbd-modules-4.8.0-2-alpha-generic-di squashfs-modules-4.8.0-2-alpha-generic-di 
virtio-modules-4.8.0-2-alpha-generic-di zlib-modules-4.8.0-2-alpha-generic-di 
fuse-modules-4.8.0-2-alpha-generic-di srm-modules-4.8.0-2-alpha-generic-di 
linux-headers-4.8.0-2-common linux-image-4.8.0-2-alpha-generic 
linux-headers-4.8.0-2-alpha-generic
 linux-image-4.8.0-2-alpha-generic-dbgsym linux-image-4.8.0-2-alpha-smp 
linux-headers-4.8.0-2-alpha-smp linux-image-4.8.0-2-alpha-smp-dbgsym 
linux-headers-4.8.0-2-all-amd64 linux-image-4.8.0-2-amd64-unsigned 
linux-headers-4.8.0-2-amd64 linux-image-4.8.0-2-amd64-dbgsym 
xen-linux-system-4.8.0-2-amd64 linux-headers-4.8.0-2-common-rt 
linux-image-4.8.0-2-rt-amd64-unsigned linux-headers-4.8.0-2-rt-amd64 

Bug#848967: marked as done (linux-image: Power button of Dell XPS13 does not send any events)

2017-01-05 Thread Debian Bug Tracking System
Your message dated Thu, 05 Jan 2017 16:00:10 +
with message-id 
and subject line Bug#848967: fixed in linux 4.8.15-2
has caused the Debian Bug report #848967,
regarding linux-image: Power button of Dell XPS13 does not send any events
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.)


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

Package: src:linux
Version: 4.8.11-1
Severity: normal

Dear Debian folk,


pressing the power button on the Dell XPS13 no event is sent.

Neither `xev` nor `acpi_listen` shows something.

If I remember correctly, it worked on the shipped Ubuntu 16.04 from Dell.


Kind regards,

Paul Menzel

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


** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.8.0-2-amd64 
root=UUID=2809c0c6-7152-4e35-a6da-a26e7400e556 ro quiet


** Not tainted

** Kernel log:
[2.356558] Bluetooth: HCI UART protocol Intel registered
[2.356568] Bluetooth: HCI UART protocol BCM registered
[2.356568] Bluetooth: HCI UART protocol QCA registered
[2.362373] ACPI: Battery Slot [BAT0] (battery present)
[2.362520] wmi: Mapper loaded
[2.363711] idma64 idma64.0: Found Intel integrated DMA 64-bit
[2.364301] intel-lpss :00:15.1: enabling device ( -> 0002)
[2.364519] idma64 idma64.1: Found Intel integrated DMA 64-bit
[2.364872] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[2.366919] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:2234.0001/input/input8

[2.368091] mei_me :00:16.0: enabling device ( -> 0002)
[2.368133] hid-multitouch 0003:04F3:2234.0001: 
input,hiddev0,hidraw0: USB HID v1.10 Device [ELAN Touchscreen] on 
usb-:00:14.0-4/input0

[2.369771] input: PC Speaker as /devices/platform/pcspkr/input/input10
[2.381350] usbcore: registered new interface driver btusb
[2.382577] bluetooth hci0: firmware: failed to load 
qca/rampatch_usb_0302.bin (-2)
[2.382751] bluetooth hci0: Direct firmware load for 
qca/rampatch_usb_0302.bin failed with error -2
[2.382753] Bluetooth: hci0: failed to request rampatch file: 
qca/rampatch_usb_0302.bin (-2)

[2.383359] i801_smbus :00:1f.4: SMBus using PCI interrupt
[2.471578] dcdbas dcdbas: Dell Systems Management Base Driver 
(version 5.6.0-3.2)

[2.480502] [drm] Memory usable by graphics device = 4096M
[2.480504] [drm] Replacing VGA console driver
[2.483581] ath10k_pci :3a:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 0

[2.484252] Console: switching to colour dummy device 80x25
[2.487901] intel_rapl: Found RAPL domain package
[2.487903] intel_rapl: Found RAPL domain core
[2.487903] intel_rapl: Found RAPL domain uncore
[2.487904] intel_rapl: Found RAPL domain dram
[2.490884] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[2.490885] [drm] Driver supports precise vblank timestamp query.
[2.492445] iTCO_vendor_support: vendor-support=0
[2.493325] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[2.493484] iTCO_wdt: Found a Intel PCH TCO device (Version=4, 
TCOBASE=0x0400)

[2.493628] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[2.496855] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[2.497712] i915 :00:02.0: firmware: direct-loading firmware 
i915/kbl_dmc_ver1_01.bin

[2.498292] [drm] Finished loading i915/kbl_dmc_ver1_01.bin (v1.1)
[2.504002] [drm] GuC firmware load skipped
[2.542973] ACPI: Video Device [GFX0] (multi-head: yes  rom: no 
post: no)
[2.543853] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input11
[2.544275] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[2.544279] [drm] Initialized i915 1.6.0 20160711 for :00:02.0 on 
minor 0

[2.553300] fbcon: inteldrmfb (fb0) is primary device
[2.608135] snd_hda_codec_realtek hdaudioC0D0: autoconfig for 
ALC3246: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[2.608136] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[2.608137] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)

[2.608137] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[

Processed: bug 850064 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=189851

2017-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 850064 https://bugzilla.kernel.org/show_bug.cgi?id=189851
Bug #850064 {Done: Ben Hutchings } [src:linux] 
/boot/vmlinuz-4.8.0-2-amd64: kernel NULL pointer dereference in icmp6_send 
related to bridge port link changes
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=189851'.
> thanks
Stopping processing here.

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