Give back linux (4.9.10-1) on i386

[Ben Hutchings]

linux 4.9.10-1 failed to build on x86-csail-01 due to a full disk. 
Please give it back to another buildd or free up more disk space there.

gb linux_4.9.10-1 . i386

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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

Bug#855017: [PATCH] ARM: dts: kirkwood: Fix SATA pinmux-ing for TS419

[Ben Hutchings]

The old board code for the TS419 assigns MPP pins 15 and 16 as SATA
activity signals (and none as SATA presence signals).  Currently the
device tree assigns the SoC's default pinmux groups for SATA, which
conflict with the second Ethernet port.

Reported-by: g...@gazeta.pl
Tested-by: g...@gazeta.pl
References: https://bugs.debian.org/855017
Cc: sta...@vger.kernel.org # 3.15+
Fixes: 934b524b3f49 ("ARM: Kirkwood: Add DT description of QNAP 419")
Signed-off-by: Ben Hutchings 
---
 arch/arm/boot/dts/kirkwood-ts419.dtsi | 8 
 1 file changed, 8 insertions(+)

diff --git a/arch/arm/boot/dts/kirkwood-ts419.dtsi 
b/arch/arm/boot/dts/kirkwood-ts419.dtsi
index 02bd53762705..532506cb0f4a 100644
--- a/arch/arm/boot/dts/kirkwood-ts419.dtsi
+++ b/arch/arm/boot/dts/kirkwood-ts419.dtsi
@@ -73,3 +73,11 @@
phy-handle = <>;
};
 };
+
+_sata0 {
+   marvell,pins = "mpp15";
+};
+
+_sata1 {
+   marvell,pins = "mpp16";
+};


signature.asc
Description: Digital signature

Bug#853110: [PATCH] [media] dvb-usb-dibusb-mc-common: Add MODULE_LICENSE

[Ben Hutchings]

dvb-usb-dibusb-mc-common is licensed under GPLv2, and if we don't say
so then it won't even load since it needs a GPL-only symbol.

Reported-by: Dominique Dumont 
References: https://bugs.debian.org/853110
Cc: sta...@vger.kernel.org # 4.9+
Fixes: e91455a1495a ("[media] dvb-usb: split out common parts of dibusb")
Signed-off-by: Ben Hutchings 
---
 drivers/media/usb/dvb-usb/dibusb-mc-common.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/media/usb/dvb-usb/dibusb-mc-common.c 
b/drivers/media/usb/dvb-usb/dibusb-mc-common.c
index c989cac9343d..0c2bc97436d5 100644
--- a/drivers/media/usb/dvb-usb/dibusb-mc-common.c
+++ b/drivers/media/usb/dvb-usb/dibusb-mc-common.c
@@ -11,6 +11,8 @@
 
 #include "dibusb.h"
 
+MODULE_LICENSE("GPL");
+
 /* 3000MC/P stuff */
 // Config Adjacent channels  Perf -cal22
 static struct dibx000_agc_config dib3000p_mt2060_agc_config = {


signature.asc
Description: Digital signature

Bug#855017: linux-image-4.9.0-1-marvell: eth1 not detected/available on QNAP TS-419pII

[Ben Hutchings]

On Fri, 2017-02-17 at 22:30 +0100, g...@gazeta.pl wrote:
> On 17.02.2017 02:57, Ben Hutchings wrote:
> > This seems to be a bug in the device tree for the TS419 - it doesn't
> > quite match the board code it replaced.  Should be easy to fix.
> 
> After applying patch, eth1 is recognized, but it behaves strange. It
> looks like it is using a correct MAC during DHCP phase, but after
> getting IP from DHCP it clones(?) eth0 MAC.

I don't think so.

[...]
> Here is an relevant output from dmesg:
> 
> [0.045321] [Firmware Info]:
> /ocp@f100/ethernet-controller@72000/ethernet0-port@0:
> local-mac-address is not set
> [0.045412] [Firmware Info]:
> /ocp@f100/ethernet-controller@76000/ethernet1-port@0:
> local-mac-address is not set
> [   60.981436] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
> [   61.917900] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC
> address 00:08:9b:cb:ae:be
> [   62.441157] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC
> address 00:08:9b:cb:ae:bf

OK, so this worked.

[...]
> And here is an output from arp on router:
> 
> IP address   HW type Flags   HW addressMask
> Device
> 192.168.1.1010x1 0x2 00:08:9b:cb:ae:be *
> br-lan
> 192.168.1.1000x1 0x2 00:08:9b:cb:ae:be *
> br-lan
> 
> both IP addresses have same MAC (from eth0).
>
> I'm not sure what is going here...

This is not a driver issue.  See:
https://serverfault.com/questions/22253/ubuntu-linux-multiple-nics-same-lan-arp-responses-always-go-out-a-single-n
(which has two possible solutions).

(I do wonder whether having two links to the same VLAN without bonding
is at all sensible, anyway.)

> BTW. Is this .dtsi file responsible for GPIO configuration?

All model-specific stuff is now defined by device trees.  The
definition for this model is spread across kirkwood-ts419-6282.dts and
four other files you can see listed at the top of it.

> I've also noticed a strange behavior with qcontrol:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795558

So far as I can remember, device trees do not have a way to request
that a GPIO should be automatically exported to userland.  That will
have to be done by qcontrol.

Ben.

-- 
Ben Hutchings
Any sufficiently advanced bug is indistinguishable from a feature.


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

Bug#855017: linux-image-4.9.0-1-marvell: eth1 not detected/available on QNAP TS-419pII

[gmbh]

On 17.02.2017 02:57, Ben Hutchings wrote:
> This seems to be a bug in the device tree for the TS419 - it doesn't
> quite match the board code it replaced.  Should be easy to fix.

After applying patch, eth1 is recognized, but it behaves strange. It
looks like it is using a correct MAC during DHCP phase, but after
getting IP from DHCP it clones(?) eth0 MAC.

---

Here is an output from flashing:

kirkwood-qnap: machine: QNAP TS419 family
Using DTB: kirkwood-ts419-6282.dtb
Installing /usr/lib/linux-image-4.9.0-1-marvell/kirkwood-ts419-6282.dtb
into /boot/dtbs/4.9.0-1-marvell/kirkwood-ts419-6282.dtb
Taking backup of kirkwood-ts419-6282.dtb.
Installing new kirkwood-ts419-6282.dtb.
Installing /usr/lib/linux-image-4.9.0-1-marvell/kirkwood-ts419-6282.dtb
into /boot/dtbs/4.9.0-1-marvell/kirkwood-ts419-6282.dtb
Taking backup of kirkwood-ts419-6282.dtb.
Installing new kirkwood-ts419-6282.dtb.
flash-kernel: installing version 4.9.0-1-marvell
flash-kernel: appending
/usr/lib/linux-image-4.9.0-1-marvell/kirkwood-ts419-6282.dtb to kernel
Generating kernel u-boot image... done.
Flashing kernel (using 2056012/2097152 bytes)... done.
Flashing initramfs (using 4777366/9437184 bytes)... done.

---

Here is an relevant output from dmesg:

[0.045321] [Firmware Info]:
/ocp@f100/ethernet-controller@72000/ethernet0-port@0:
local-mac-address is not set
[0.045412] [Firmware Info]:
/ocp@f100/ethernet-controller@76000/ethernet1-port@0:
local-mac-address is not set
[   60.981436] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   61.917900] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC
address 00:08:9b:cb:ae:be
[   62.441157] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC
address 00:08:9b:cb:ae:bf

---

Configuration /etc/network/interfaces:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

# The secondary network interface
allow-hotplug eth1
iface eth1 inet dhcp

---

ifconfig output, note that MAC and IP addresses are correct:

eth0: flags=4163  mtu 1500
inet 192.168.1.100  netmask 255.255.255.0  broadcast 192.168.1.255
inet6 fe80::208:9bff:fecb:aebe  prefixlen 64  scopeid 0x20
ether 00:08:9b:cb:ae:be  txqueuelen 1000  (Ethernet)
RX packets 1693441  bytes 2370511659 (2.2 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 386537  bytes 63194040 (60.2 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 41

eth1: flags=4163  mtu 1500
inet 192.168.1.101  netmask 255.255.255.0  broadcast 192.168.1.255
inet6 fe80::208:9bff:fecb:aebf  prefixlen 64  scopeid 0x20
ether 00:08:9b:cb:ae:bf  txqueuelen 1000  (Ethernet)
RX packets 412  bytes 58481 (57.1 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 48  bytes 4776 (4.6 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 42

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1  (Local Loopback)
RX packets 376  bytes 24942 (24.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 376  bytes 24942 (24.3 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

---

And here is an output from arp on router:

IP address   HW type Flags   HW addressMask
Device
192.168.1.1010x1 0x2 00:08:9b:cb:ae:be *
br-lan
192.168.1.1000x1 0x2 00:08:9b:cb:ae:be *
br-lan

both IP addresses have same MAC (from eth0).

I'm not sure what is going here...

BTW. Is this .dtsi file responsible for GPIO configuration? I've also
noticed a strange behavior with qcontrol:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795558

Best Regards,
Marek

Processed: reassign 847652

[Debian Bug Tracking System]

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

> severity 847652 wishlist
Bug #847652 [nvidia-kernel-dkms] nvidia-kernel-dkms fails to compile for 
rt-kernel 4.8.0-1-rt
Bug #848005 [nvidia-kernel-dkms] nvidia-driver: nvidia-drm.ko don't build with 
rt kernel
Severity set to 'wishlist' from 'important'
Severity set to 'wishlist' from 'important'
> tags 847652 patch
Bug #847652 [nvidia-kernel-dkms] nvidia-kernel-dkms fails to compile for 
rt-kernel 4.8.0-1-rt
Bug #848005 [nvidia-kernel-dkms] nvidia-driver: nvidia-drm.ko don't build with 
rt kernel
Added tag(s) patch.
Added tag(s) patch.
> retitle 847652 rt_mutex_destroy is GPL_ONLY unlike mutex_destroy, breaks 
> non-GPL modules
Bug #847652 [nvidia-kernel-dkms] nvidia-kernel-dkms fails to compile for 
rt-kernel 4.8.0-1-rt
Bug #848005 [nvidia-kernel-dkms] nvidia-driver: nvidia-drm.ko don't build with 
rt kernel
Changed Bug title to 'rt_mutex_destroy is GPL_ONLY unlike mutex_destroy, breaks 
non-GPL modules' from 'nvidia-kernel-dkms fails to compile for rt-kernel 
4.8.0-1-rt'.
Changed Bug title to 'rt_mutex_destroy is GPL_ONLY unlike mutex_destroy, breaks 
non-GPL modules' from 'nvidia-driver: nvidia-drm.ko don't build with rt kernel'.
> reassign 847652 linux-image-4.9.0-1-rt-amd64
Bug #847652 [nvidia-kernel-dkms] rt_mutex_destroy is GPL_ONLY unlike 
mutex_destroy, breaks non-GPL modules
Bug #848005 [nvidia-kernel-dkms] rt_mutex_destroy is GPL_ONLY unlike 
mutex_destroy, breaks non-GPL modules
Bug reassigned from package 'nvidia-kernel-dkms' to 
'linux-image-4.9.0-1-rt-amd64'.
Bug reassigned from package 'nvidia-kernel-dkms' to 
'linux-image-4.9.0-1-rt-amd64'.
No longer marked as found in versions nvidia-graphics-drivers/375.20-4.
No longer marked as found in versions nvidia-graphics-drivers/375.20-4.
Ignoring request to alter fixed versions of bug #847652 to the same values 
previously set
Ignoring request to alter fixed versions of bug #848005 to the same values 
previously set
> thanks
Stopping processing here.

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

linux_4.9.10-1_multi.changes ACCEPTED into unstable, unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Feb 2017 13:18:17 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 
btrfs-modules-4.9.0-2-alpha-generic-di ext4-modules-4.9.0-2-alpha-generic-di 
isofs-modules-4.9.0-2-alpha-generic-di jfs-modules-4.9.0-2-alpha-generic-di
 xfs-modules-4.9.0-2-alpha-generic-di fat-modules-4.9.0-2-alpha-generic-di 
md-modules-4.9.0-2-alpha-generic-di multipath-modules-4.9.0-2-alpha-generic-di 
usb-modules-4.9.0-2-alpha-generic-di 
usb-storage-modules-4.9.0-2-alpha-generic-di 
fb-modules-4.9.0-2-alpha-generic-di input-modules-4.9.0-2-alpha-generic-di 
event-modules-4.9.0-2-alpha-generic-di mouse-modules-4.9.0-2-alpha-generic-di 
nic-pcmcia-modules-4.9.0-2-alpha-generic-di 
pcmcia-modules-4.9.0-2-alpha-generic-di 
nic-usb-modules-4.9.0-2-alpha-generic-di sata-modules-4.9.0-2-alpha-generic-di 
crc-modules-4.9.0-2-alpha-generic-di crypto-modules-4.9.0-2-alpha-generic-di 
crypto-dm-modules-4.9.0-2-alpha-generic-di ata-modules-4.9.0-2-alpha-generic-di 
nbd-modules-4.9.0-2-alpha-generic-di squashfs-modules-4.9.0-2-alpha-generic-di 
virtio-modules-4.9.0-2-alpha-generic-di zlib-modules-4.9.0-2-alpha-generic-di 
fuse-modules-4.9.0-2-alpha-generic-di srm-modules-4.9.0-2-alpha-generic-di 
linux-image-4.9.0-2-alpha-generic
 linux-headers-4.9.0-2-alpha-generic linux-image-4.9.0-2-alpha-generic-dbgsym 
linux-image-4.9.0-2-alpha-smp linux-headers-4.9.0-2-alpha-smp 
linux-image-4.9.0-2-alpha-smp-dbgsym linux-headers-4.9.0-2-all-amd64 
linux-image-4.9.0-2-amd64-unsigned linux-headers-4.9.0-2-amd64 
linux-image-4.9.0-2-amd64-dbgsym linux-image-4.9.0-2-rt-amd64-unsigned 
linux-headers-4.9.0-2-rt-amd64 linux-image-4.9.0-2-rt-amd64-dbgsym 
linux-headers-4.9.0-2-all-arm64 linux-image-4.9.0-2-arm64-unsigned 
linux-headers-4.9.0-2-arm64 linux-image-4.9.0-2-arm64-dbgsym 
linux-headers-4.9.0-2-all-armel kernel-image-4.9.0-2-marvell-di 
nic-modules-4.9.0-2-marvell-di nic-shared-modules-4.9.0-2-marvell-di 
usb-serial-modules-4.9.0-2-marvell-di ppp-modules-4.9.0-2-marvell-di 
cdrom-core-modules-4.9.0-2-marvell-di scsi-core-modules-4.9.0-2-marvell-di 
loop-modules-4.9.0-2-marvell-di ipv6-modules-4.9.0-2-marvell-di 
btrfs-modules-4.9.0-2-marvell-di ext4-modules-4.9.0-2-marvell-di 
isofs-modules-4.9.0-2-marvell-di
 jffs2-modules-4.9.0-2-marvell-di jfs-modules-4.9.0-2-marvell-di 
fat-modules-4.9.0-2-marvell-di minix-modules-4.9.0-2-marvell-di 
md-modules-4.9.0-2-marvell-di multipath-modules-4.9.0-2-marvell-di 
usb-modules-4.9.0-2-marvell-di usb-storage-modules-4.9.0-2-marvell-di 
fb-modules-4.9.0-2-marvell-di input-modules-4.9.0-2-marvell-di 
event-modules-4.9.0-2-marvell-di mouse-modules-4.9.0-2-marvell-di 
nic-usb-modules-4.9.0-2-marvell-di sata-modules-4.9.0-2-marvell-di 
crc-modules-4.9.0-2-marvell-di crypto-modules-4.9.0-2-marvell-di 
crypto-dm-modules-4.9.0-2-marvell-di mmc-modules-4.9.0-2-marvell-di 
nbd-modules-4.9.0-2-marvell-di squashfs-modules-4.9.0-2-marvell-di 
uinput-modules-4.9.0-2-marvell-di zlib-modules-4.9.0-2-marvell-di 
leds-modules-4.9.0-2-marvell-di udf-modules-4.9.0-2-marvell-di 
fuse-modules-4.9.0-2-marvell-di mtd-modules-4.9.0-2-marvell-di 
linux-image-4.9.0-2-marvell linux-headers-4.9.0-2-marvell 
linux-image-4.9.0-2-marvell-dbgsym linux-headers-4.9.0-2-all-armhf
 linux-image-4.9.0-2-armmp-unsigned linux-headers-4.9.0-2-armmp 
linux-image-4.9.0-2-armmp-dbgsym linux-image-4.9.0-2-armmp-lpae-unsigned 
linux-headers-4.9.0-2-armmp-lpae linux-image-4.9.0-2-armmp-lpae-dbgsym 
linux-headers-4.9.0-2-all-hppa kernel-image-4.9.0-2-parisc-di 
nic-modules-4.9.0-2-parisc-di nic-shared-modules-4.9.0-2-parisc-di 
serial-modules-4.9.0-2-parisc-di usb-serial-modules-4.9.0-2-parisc-di 
ppp-modules-4.9.0-2-parisc-di pata-modules-4.9.0-2-parisc-di 
cdrom-core-modules-4.9.0-2-parisc-di scsi-core-modules-4.9.0-2-parisc-di 
scsi-modules-4.9.0-2-parisc-di loop-modules-4.9.0-2-parisc-di 
btrfs-modules-4.9.0-2-parisc-di ext4-modules-4.9.0-2-parisc-di 
isofs-modules-4.9.0-2-parisc-di jfs-modules-4.9.0-2-parisc-di 
xfs-modules-4.9.0-2-parisc-di fat-modules-4.9.0-2-parisc-di 
md-modules-4.9.0-2-parisc-di multipath-modules-4.9.0-2-parisc-di 
usb-modules-4.9.0-2-parisc-di 

Bug#855153: marked as done (linux-image-4.9.0-1-amd64: kernel 4.9 does not check route protocol when deleting ipv6 routes)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#855153: fixed in linux 4.9.10-1
has caused the Debian Bug report #855153,
regarding linux-image-4.9.0-1-amd64: kernel 4.9 does not check route protocol 
when deleting ipv6 routes
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.)


-- 
855153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855153
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.6-3
Severity: important
Tags: ipv6

Dear Debian Kernel Maintainers,

when trying to delete an IPv6 route with a specific route protocol field
in a kernel 4.9, the kernel does not actually check the protocol of the
route and just deletes all the routes that match the other attributes.

This leads to various issues with routing daemons, for example BIRD.
E.g. when a BGP withdraw update is being received with a prefix matching
a kernel route, both "proto bird" and "proto kernel" get deleted.

The only workaround is currently to maintain a manual blacklist in the
routing daemon, however a proper fix at kernel level would be definitely
appreciated. As a patch was already committed to the Linux Kernel Git
Repository, I recommend backporting into the Debian Stretch kernel, as
the patch is both overseeable and easy to implement.

The bug itself can be easily reproduced on any Linux running kernel
version 4.9 or lower by executing these commands:

~$ ip -6 route add ff::/64 dev eth0 proto kernel
~$ ip -6 route
(check the routing table, the newly added route is visible)
~$ ip -6 route del ff::/64 proto boot
~$ ip -6 route
(the route is gone, although it should still be there!)

A link to the Git commit fixing this specific issue can be found at the
following URL and was already merged into kernel 4.10 since rc1:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c2ed1880fd61a998e3ce40254a99a2ad000f1a7d

-- Package-specific info:
** Version:
Linux version 4.9.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-1-amd64 root=/dev/mapper/vg--main-lv--root ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: QEMU
product_name: Standard PC (i440FX + PIIX, 1996)
product_version: pc-i440fx-2.7
chassis_vendor: QEMU
chassis_version: pc-i440fx-2.7
bios_vendor: SeaBIOS
bios_version: rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org

** Loaded modules:
binfmt_misc
nf_log_ipv6
ip6t_REJECT
nf_reject_ipv6
nf_conntrack_ipv6
nf_defrag_ipv6
ip6table_filter
ip6_tables
nf_log_ipv4
nf_log_common
xt_LOG
xt_limit
ipt_REJECT
nf_reject_ipv4
xt_tcpudp
nf_conntrack_ipv4
nf_defrag_ipv4
xt_multiport
xt_recent
xt_addrtype
xt_conntrack
nf_conntrack
iptable_filter
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
hid_generic
cirrus
ppdev
ttm
drm_kms_helper
usbhid
joydev
hid
evdev
serio_raw
pcspkr
sg
drm
virtio_balloon
shpchp
parport_pc
parport
acpi_cpufreq
tpm_tis
tpm_tis_core
tpm
button
nfsd
auth_rpcgss
nfs_acl
lockd
grace
sunrpc
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
mbcache
sr_mod
cdrom
ata_generic
dm_mod
virtio_blk
virtio_net
crc32c_intel
aesni_intel
aes_x86_64
glue_helper
lrw
gf128mul
ablk_helper
cryptd
psmouse
ata_piix
uhci_hcd
libata
floppy
ehci_hcd
virtio_pci
virtio_ring
virtio
i2c_piix4
usbcore
usb_common
scsi_mod

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] 
[8086:1237] (rev 02)
Subsystem: Red Hat, Inc Qemu virtual machine [1af4:1100]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:0a.0 SCSI storage controller [0100]: Red Hat, Inc Virtio block device 
[1af4:1001]
Subsystem: Red Hat, Inc Virtio block device [1af4:0002]
Physical Slot: 10
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: virtio-pci
Kernel modules: virtio_pci

00:12.0 Ethernet controller [0200]: Red Hat, Inc Virtio network device 
[1af4:1000]
Subsystem: Red 

Bug#854855: marked as done (linux-image-4.9.0-1-amd64: GPU hang (after resuming from hibernation) in Xorg since 4.9.0 [with patch])

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#855055: fixed in linux 4.9.10-1
has caused the Debian Bug report #855055,
regarding linux-image-4.9.0-1-amd64: GPU hang (after resuming from hibernation) 
in Xorg since 4.9.0 [with patch]
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.)


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

Package: src:linux
Version: 4.9.6-3
Severity: normal

Hello,

Since kernel 4.9.0 replaced 4.8.0 in stretch, my notebook was unable
to resume from hibernation. Hardware is a Lenovo Thinkpad X1 Carbon
Gen4. The issue first came up with 4.9.2, but is still present in the 
4.9.6 version of linux-image-4.9.0-1-amd64.


While the system appears to succesfully return from hibernation, soon as 
the system switch to X it starts freezing and locks more and more.


At the same time, the following messages appear in the kernel ring buffer:

[   62.815665] [drm] GPU HANG: ecode 9:1:0xc28d04b4, in Xorg [1830],
reason: Hang on blitter ring, action: reset
[   62.815675] [drm] GPU hangs can indicate a bug anywhere in the entire
gfx stack, including userspace.
[   62.815680] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[   62.815683] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[   62.815687] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[   62.815691] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   63.575242] drm/i915: Resetting chip after gpu hang
[   63.575437] [drm] RC6 on
[   63.591843] [drm] GuC firmware load skipped


As being adviced by the message, I have opened an upstream bug at [1],
got then redirected to a known bug at [2].

And indeed, rebuilding a custom ⒋.9.6 kernel and applying the patch
from [3] to intel_lrc.c resolves my problem.

Then my system resumes successfully from hibernation without these
freezes.

Cheers,
Andreas

[1] https://bugs.freedesktop.org/show_bug.cgi?id=99545
[2] https://bugs.freedesktop.org/show_bug.cgi?id=96526
[3] https://patchwork.freedesktop.org/patch/111587/


-- Package-specific info:
** Version:
Linux version 4.9.0-1-amd64 (debian-kernel@lists.debian.org) (gcc 
version 6.3.0 20170124 (Debian 6.3.0-5) ) #1 SMP Debian 4.9.6-3 (2017-01-28)


** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-1-amd64 root=/dev/mapper/carbon-root ro 
resume=UUID=b1a930e8-b6f2-481e-8478-cddd551b795f intel_iommu=igfx_off


** Not tainted

** Kernel log:
[   62.815665] [drm] GPU HANG: ecode 9:1:0xc28d04b4, in Xorg [1830], 
reason: Hang on blitter ring, action: reset
[   62.815675] [drm] GPU hangs can indicate a bug anywhere in the entire 
gfx stack, including userspace.
[   62.815680] [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
[   62.815683] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
[   62.815687] [drm] The gpu crash dump is required to analyze gpu 
hangs, so please always attach it.

[   62.815691] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   63.575242] drm/i915: Resetting chip after gpu hang
[   63.575437] [drm] RC6 on
[   63.591843] [drm] GuC firmware load skipped

** Model information
sys_vendor: LENOVO
product_name: 20FB003RGE
product_version: ThinkPad X1 Carbon 4th
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N1FET43W (1.17 )
board_vendor: LENOVO
board_name: 20FB003RGE
board_version: SDK0J40705 WIN

** Loaded modules:
fuse
rfcomm
ip6table_mangle
nf_log_ipv6
nf_conntrack_ipv6
nf_defrag_ipv6
xt_connmark
iptable_mangle
xt_helper
nf_log_ipv4
nf_log_common
xt_LOG
xt_limit
nf_conntrack_ipv4
nf_defrag_ipv4
xt_tcpudp
xt_addrtype
xt_conntrack
nf_conntrack_sip
nf_conntrack_ftp
nf_conntrack_irc
nf_conntrack_pptp
nf_conntrack_proto_gre
nf_conntrack
ctr
ccm
ebtable_filter
ebtables
ip6table_filter
ip6_tables
iptable_filter
snd_hrtimer
snd_seq
snd_seq_device
cpufreq_userspace
cpufreq_powersave
cmac
cpufreq_conservative
bnep
binfmt_misc
algif_skcipher
af_alg
dm_crypt
hid_sensor_accel_3d
hid_sensor_trigger
hid_sensor_iio_common
industrialio_triggered_buffer
kfifo_buf
arc4
industrialio
acer_wmi
sparse_keymap
ext4
jbd2
fscrypto
ecb
mbcache
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
kvm_intel
kvm
irqbypass
crct10dif_pclmul
crc32_pclmul
iwlmvm
ghash_clmulni_intel
snd_hda_codec_hdmi
intel_cstate
intel_uncore
mac80211
snd_hda_codec_conexant

Bug#855055: marked as done (linux-image-4.9.0-1-amd64: Hibernation bug fixed in linux-image-4.10.0-rc6-amd64)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#855055: fixed in linux 4.9.10-1
has caused the Debian Bug report #855055,
regarding linux-image-4.9.0-1-amd64: Hibernation bug fixed in 
linux-image-4.10.0-rc6-amd64
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.)


-- 
855055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.6-3
Severity: normal

Dear Maintainer,

This bug:
https://bugs.freedesktop.org/show_bug.cgi?id=96526,
which prevents some systems from waking up after hibernation,
has been fixed there:
https://patchwork.freedesktop.org/patch/111587/

Specifically on a Lenovo Helix with CPU Intel Core M 5Y10,
the system could never wake up from hibernation with
linux-image-4.9.0-1-amd64;
Now that I have installed linux-image-4.10.0-rc6-amd64, from experimental,
the system always wake up normally.

This is an important functionality, especially because:
- The computer is a tablet,
- echo mem > /sys/power/state doesn't work
- echo freeze > sys/power/state works only when the tablet
is connected to a keyboard.

Those later bugs are described there:
https://bugzilla.kernel.org/show_bug.cgi?id=100171

So it is the only power saving method available.

Regards,
Chris
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.10-1

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 855...@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: Fri, 17 Feb 2017 13:18:17 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 
btrfs-modules-4.9.0-2-alpha-generic-di ext4-modules-4.9.0-2-alpha-generic-di 
isofs-modules-4.9.0-2-alpha-generic-di jfs-modules-4.9.0-2-alpha-generic-di
 xfs-modules-4.9.0-2-alpha-generic-di fat-modules-4.9.0-2-alpha-generic-di 
md-modules-4.9.0-2-alpha-generic-di multipath-modules-4.9.0-2-alpha-generic-di 
usb-modules-4.9.0-2-alpha-generic-di 
usb-storage-modules-4.9.0-2-alpha-generic-di 
fb-modules-4.9.0-2-alpha-generic-di input-modules-4.9.0-2-alpha-generic-di 
event-modules-4.9.0-2-alpha-generic-di mouse-modules-4.9.0-2-alpha-generic-di 
nic-pcmcia-modules-4.9.0-2-alpha-generic-di 
pcmcia-modules-4.9.0-2-alpha-generic-di 
nic-usb-modules-4.9.0-2-alpha-generic-di sata-modules-4.9.0-2-alpha-generic-di 
crc-modules-4.9.0-2-alpha-generic-di crypto-modules-4.9.0-2-alpha-generic-di 
crypto-dm-modules-4.9.0-2-alpha-generic-di ata-modules-4.9.0-2-alpha-generic-di 
nbd-modules-4.9.0-2-alpha-generic-di squashfs-modules-4.9.0-2-alpha-generic-di 
virtio-modules-4.9.0-2-alpha-generic-di zlib-modules-4.9.0-2-alpha-generic-di 
fuse-modules-4.9.0-2-alpha-generic-di srm-modules-4.9.0-2-alpha-generic-di 
linux-image-4.9.0-2-alpha-generic
 linux-headers-4.9.0-2-alpha-generic linux-image-4.9.0-2-alpha-generic-dbgsym 
linux-image-4.9.0-2-alpha-smp linux-headers-4.9.0-2-alpha-smp 
linux-image-4.9.0-2-alpha-smp-dbgsym linux-headers-4.9.0-2-all-amd64 
linux-image-4.9.0-2-amd64-unsigned linux-headers-4.9.0-2-amd64 
linux-image-4.9.0-2-amd64-dbgsym 

Bug#854662: marked as done (linux-image-4.9.0-0.bpo.1-marvell: please enable CONFIG_SENSORS_G762)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#854662: fixed in linux 4.9.10-1
has caused the Debian Bug report #854662,
regarding linux-image-4.9.0-0.bpo.1-marvell: please enable CONFIG_SENSORS_G762
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.)


-- 
854662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.2-2~bpo8+1
Severity: wishlist

Dear Maintainer,

I am installing debian on a Netgear ReadyNAS Duo v2, and so far everything 
works except some of the sensors, because CONFIG_SENSORS_G762 is not set:

$ grep CONFIG_SENSORS_G762 /boot/config-4.9.0-0.bpo.1-marvell
# CONFIG_SENSORS_G762 is not set

Please consider enabling this feature. Thank you.

-- Package-specific info:
** Version:
Linux version 4.9.0-0.bpo.1-marvell (debian-kernel@lists.debian.org) (gcc 
version 4.9.2 (Debian 4.9.2-10) ) #1 Debian 4.9.2-2~bpo8+1 (2017-01-26)

** Command line:
root=/dev/md0 console=ttyS0,115200 earlyprintk reason=normal 
mtdparts=nand_mtd:0x18@0(u-boot),0x2@0x18(u-boot-env),0x60@0x20(uImage),0x100@0x80(minirootfs),0x680@0x180(jffs2);

** Not tainted

** Kernel log:
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.9.0-0.bpo.1-marvell 
(debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 
Debian 4.9.2-2~bpo8+1 (2017-01-26)
[0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), 
cr=0005397f
[0.00] CPU: VIVT data cache, VIVT instruction cache
[0.00] OF: fdt:Machine model: NETGEAR ReadyNAS Duo v2
[0.00] bootconsole [earlycon0] enabled
[0.00] Memory policy: Data cache writeback
[0.00] On node 0 totalpages: 65536
[0.00] free_area_init_node: node 0, pgdat c059d218, node_mem_map 
cfdf8000
[0.00]   Normal zone: 512 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 65536 pages, LIFO batch:15
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 65024
[0.00] Kernel command line: root=/dev/md0 console=ttyS0,115200 
earlyprintk reason=normal 
mtdparts=nand_mtd:0x18@0(u-boot),0x2@0x18(u-boot-env),0x60@0x20(uImage),0x100@0x80(minirootfs),0x680@0x180(jffs2);
[0.00] PID hash table entries: 1024 (order: 0, 4096 bytes)
[0.00] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.00] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[0.00] Memory: 241080K/262144K available (3796K kernel code, 397K 
rwdata, 1124K rodata, 300K init, 298K bss, 21064K reserved, 0K cma-reserved, 0K 
highmem)
[0.00] Virtual kernel memory layout:
vector  : 0x - 0x1000   (   4 kB)
fixmap  : 0xffc0 - 0xfff0   (3072 kB)
vmalloc : 0xd080 - 0xff80   ( 752 MB)
lowmem  : 0xc000 - 0xd000   ( 256 MB)
pkmap   : 0xbfe0 - 0xc000   (   2 MB)
modules : 0xbf00 - 0xbfe0   (  14 MB)
  .text : 0xc0008000 - 0xc03bd2c8   (3797 kB)
  .init : 0xc04fd000 - 0xc0548000   ( 300 kB)
  .data : 0xc0548000 - 0xc05ab7e8   ( 398 kB)
   .bss : 0xc05ab7e8 - 0xc05f6060   ( 299 kB)
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] clocksource: orion_clocksource: mask: 0x max_cycles: 
0x, max_idle_ns: 9556302233 ns
[0.06] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 
10737418237ns
[0.008266] Console: colour dummy device 80x30
[0.012817] Calibrating delay loop... 1594.36 BogoMIPS (lpj=3188736)
[0.042766] pid_max: default: 32768 minimum: 301
[0.047596] Security Framework initialized
[0.051784] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.058590] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.065292] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.073254] CPU: Testing write buffer coherency: ok
[0.078286] ftrace: allocating 16938 entries in 34 pages
[0.109047] Setting up static identity map for 0x8200 - 0x823c
[0.115169] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[0.122672] devtmpfs: initialized
[0.130442] VFP support v0.3: not present
[0.134688] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
[

Bug#853170: marked as done (fails to boot on debian's MP30-AR1 systems [regression])

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#853170: fixed in linux 4.9.10-1
has caused the Debian Bug report #853170,
regarding fails to boot on debian's MP30-AR1 systems [regression]
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.)


-- 
853170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.9.0-1-arm64
Version: 4.9.6-3
Severity: grave
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team

The 4.9.6-3 kernel package fails to boot on Debian's aagaard and acker
systems.  4.9.2-2 before that booted just fine.

This is from the serial:

[..]
] Updating memory slots
] Searching for slot 1 structure
] Loading Linux 4.9.0-1-arm64 ...
] Loading initial ramdisk ...
] Loading driver at 0x08079224000 EntryPoint=0x08079B28670
] EFI stub: Booting Linux Kernel...
] ConvertPages: Incompatible memory types
] EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
] EFI stub: Using DTB from configuration table
] EFI stub: Exiting boot services and installing virtual address map...
] OSBootEvent = Success
] L3c Cache: 8MB
] 
] 
] Synchronous Exception at 0x00807954A740
] 
]   X0 0x9FE059D0   X1 0x008079BC369D   X2 0x0010   X3 
0x6D6D2D696665752C
]   X4 0x0065   X5 0x   X6 0x8000   X7 
0x73716073722C6F60
]   X8 0x0005   X9 0x0008  X10 0xFFFD  X11 
0x
]  X12 0x0002  X13 0x9FE0  X14 0xEE030400  X15 
0xFFF1
]  X16 0x000FFFE366D0  X17 0x0004  X18 0x  X19 
0x539C
]  X20 0x9FE053D4  X21 0x9FE0  X22 0x0015  X23 
0x000FFFE364BC
]  X24 0x9FE059C3  X25 0x008079BC3698  X26 0x00807FF9  X27 
0x
]  X28 0x5350   FP 0x000FFFE36410   LR 0x008079B2F0C4  
] 
]   V0 0x931FB7DE0AF5E032 B5FDFBBDDEFBF6F6   V1 0xDFF9BFCDD5A9DC14 
FCCD1F828E36EFAB
]   V2 0x9595DCB5BF2ADA46 FFDE4B719BD36EC5   V3 0xE7FCDF7AE399BBFF 
D5FFCF7729F963DE
]   V4 0x73BE4F7E3F33F753 DF77DEF7BBE1F987   V5 0x2357FFFEA5798E68 
FDCEDECEF3C7CB91
]   V6 0xF7D6DFFA3237ABBE 9F3FDFEFEFB22FCC   V7 0xA4FD7B2FFF865F7F 
EFDF6DB9EADB7BA6
]   V8 0x    V9 0x 
0003
]  V10 0x D7EACFFFEB7D6F7F  V11 0x 
DDD9CF78D6C07BAA
]  V12 0x DBB1DEEDFBFB2B38  V13 0x 
7FF8BBFEF5F7EFFF
]  V14 0x D7BE6674E7FF  V15 0x 

]  V16 0x53FFDA68FF1BDF17 55DDDFFBFB736BE7  V17 0x912EC77BF436FB27 
BBF87C9F6F9DDF57
]  V18 0xF338DE75A9F7FB77 CD18137BFFE7FBA7  V19 0x7F35FBF2CE83FABA 
F9F8C7D5DB91DDE6
]  V20 0x080080022000 6008484020882008  V21 0x009000500800800A 
201240100402
]  V22 0x014200A02404 000A025062004100  V23 0x01004000 
50501808
]  V24 0x0500D8400201 014208042000  V25 0xC420D4208000 
402000188000
]  V26 0x00089240A0200041 12A00020  V27 0x020C48010001000A 
043800128000
]  V28 0xC000C2D4C018 00028A005180  V29 0x104022036000 
54204050082D0C08
]  V30 0x84300804 0040801080004048  V31 0x424202010206 
0504421020242840
] 
]   SP 0x000FFFE36410  ELR 0x00807954A740  SPSR 0x0309  FPSR 
0x288A
]  ESR 0x9621  FAR 0x008079BC369D
] 
]  ESR : EC 0x25  IL 0x1  ISS 0x0021
] 
] Data abort: Alignment fault
] 
] 
] Synchronous Exception at 0x00807954A740
] 
]   X0 0x9FE059D0   X1 0x008079BC369D   X2 0x0010   X3 
0x6D6D2D696665752C
]   X4 0x0065   X5 0x   X6 0x8000   X7 
0x73716073722C6F60
]   X8 0x0005   X9 0x0008  X10 0xFFFD  X11 
0x
]  X12 0x0002  X13 0x9FE0  X14 0xEE030400  X15 
0xFFF1
]  X16 0x000FFFE366D0  X17 0x0004  X18 0x  X19 
0x539C
]  X20 0x9FE053D4  X21 0x9FE0  X22 0x0015  X23 
0x000FFFE364BC
]  X24 0x9FE059C3  X25 0x008079BC3698  X26D1F828E36EFAB
]   V2 0x9595DCB5BF2ADA46 FFDE4B719BD36EC5   V3 0xE7FCDF7AE399BBFF 
D5FFCF7729F963DE
]   V4 0x73BE4F7E3F33F753 DF77DEF7BBE1F987   V5 0x2357FFFEA5798E68 
FDCEDECEF3C7CB91
]   V6 0xF7D6DFFA3237ABBE 9F3FDFEFEFB22FCC   V7 0xA4FD7B2FFF865F7F 

Bug#853067: marked as done (iio-sensor-proxy: spams syslog with an error message every second)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#853067: fixed in linux 4.9.10-1
has caused the Debian Bug report #853067,
regarding iio-sensor-proxy: spams syslog with an error message every second
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.)


-- 
853067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iio-sensor-proxy
Version: 2.0-1
Severity: important

Dear Maintainer,

my syslog is full of messages like

iio-sensor-prox[574]: Could not open input accel '/dev/input/event9':
Operation not permitted

about once a second.  I don't know why that package is installed or what
it does but filling up syslog seems like the wrong thing to do
regardless.  /dev/input/event9 is identified as "Acer BMA150
accelerometer", fwiw.

Cheers,
Julien

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
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)

Versions of packages iio-sensor-proxy depends on:
ii  libc6   2.24-8
ii  libglib2.0-02.50.2-2
ii  libgudev-1.0-0  230-3
ii  systemd 232-8

iio-sensor-proxy recommends no packages.

iio-sensor-proxy suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.10-1

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 853...@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: Fri, 17 Feb 2017 13:18:17 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 
btrfs-modules-4.9.0-2-alpha-generic-di ext4-modules-4.9.0-2-alpha-generic-di 
isofs-modules-4.9.0-2-alpha-generic-di jfs-modules-4.9.0-2-alpha-generic-di
 xfs-modules-4.9.0-2-alpha-generic-di fat-modules-4.9.0-2-alpha-generic-di 
md-modules-4.9.0-2-alpha-generic-di multipath-modules-4.9.0-2-alpha-generic-di 
usb-modules-4.9.0-2-alpha-generic-di 
usb-storage-modules-4.9.0-2-alpha-generic-di 
fb-modules-4.9.0-2-alpha-generic-di input-modules-4.9.0-2-alpha-generic-di 
event-modules-4.9.0-2-alpha-generic-di mouse-modules-4.9.0-2-alpha-generic-di 
nic-pcmcia-modules-4.9.0-2-alpha-generic-di 
pcmcia-modules-4.9.0-2-alpha-generic-di 
nic-usb-modules-4.9.0-2-alpha-generic-di sata-modules-4.9.0-2-alpha-generic-di 
crc-modules-4.9.0-2-alpha-generic-di crypto-modules-4.9.0-2-alpha-generic-di 
crypto-dm-modules-4.9.0-2-alpha-generic-di ata-modules-4.9.0-2-alpha-generic-di 
nbd-modules-4.9.0-2-alpha-generic-di squashfs-modules-4.9.0-2-alpha-generic-di 
virtio-modules-4.9.0-2-alpha-generic-di zlib-modules-4.9.0-2-alpha-generic-di 
fuse-modules-4.9.0-2-alpha-generic-di srm-modules-4.9.0-2-alpha-generic-di 
linux-image-4.9.0-2-alpha-generic
 linux-headers-4.9.0-2-alpha-generic linux-image-4.9.0-2-alpha-generic-dbgsym 
linux-image-4.9.0-2-alpha-smp linux-headers-4.9.0-2-alpha-smp 

Bug#853073: marked as done (linux-image-4.9.0-1-amd64: Wrong firmware for my card loaded by rtl8192ce driver)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#853073: fixed in linux 4.9.10-1
has caused the Debian Bug report #853073,
regarding linux-image-4.9.0-1-amd64: Wrong firmware for my card loaded by 
rtl8192ce driver
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.)


-- 
853073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.9.2-2
Severity: important
Tags: upstream

Hello,

In the last few weeks I noticed a regression in performance of the 
wifi card in my ThinkPad X220 laptop (running unstable), the 
connection has become significantly more flaky, especially further 
away from the access point. Trying to isolate the failure I booted 
from a Jessie live CD and noticed that the same wireless driver 
(rtl8192ce) is loading different firmware in Jessie 
(rtlwifi/rtl8192cfw.bin) compared to unstable 
(rtlwifi/rtl8192cfwU.bin). Looks like it is an inadvertent result of 
the following upstream commits:

https://github.com/torvalds/linux/commit/d86e64768859fca82c78e52877ceeba04e25d27a
https://github.com/torvalds/linux/commit/cf4747d7535a936105f0abe8d8109d3fe339162b

I forced the driver to load the firmware (rtl8192cfw.bin) used by 
Jessie driver and which I believe to be correct for my card 
(PCI ID 10ec:8176) by renaming the firmware files, and in this 
configuration I see much better link stability and latency, as 
measured by ping to the access point.

-- Package-specific info:
** Version:
Linux version 4.9.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2 (2017-01-12)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-1-amd64 
root=UUID=476bc45a-c62d-409b-b6e9-81acb45fab7e ro quiet

** Not tainted

** Kernel log:

** Model information
sys_vendor: LENOVO
product_name: 4286CTO
product_version: [   12.688515] ACPI: AC Adapter [AC] (off-line)
[   12.79] ACPI: Battery Slot [BAT0] (battery present)
[   12.880100] Non-volatile memory driver v1.3
[   12.952811] wmi: Mapper loaded
[   12.959853] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   12.959928] sd 6:0:0:0: Attached scsi generic sg1 type 0
[   12.982634] thinkpad_acpi: ThinkPad ACPI Extras v0.25
[   12.982635] thinkpad_acpi: http://ibm-acpi.sf.net/
[   12.982636] thinkpad_acpi: ThinkPad BIOS 8DET69WW (1.39 ), EC unknown
[   12.982637] thinkpad_acpi: Lenovo ThinkPad X220, model 4286CTO
[   12.983267] thinkpad_acpi: radio switch found; radios are enabled
[   12.983390] thinkpad_acpi: possible tablet mode switch found; ThinkPad in 
laptop mode
[   12.983505] thinkpad_acpi: This ThinkPad has standard ACPI backlight 
brightness control, supported by the ACPI video driver
[   12.983506] thinkpad_acpi: Disabling thinkpad-acpi brightness events by 
default...
[   12.985350] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
unblocked
[   12.985925] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[   13.005025] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input7
[   13.022735] input: PC Speaker as /devices/platform/pcspkr/input/input8
[   13.341597] i915: unknown parameter 'i915_enable_rc6' ignored
[   13.342150] [drm] Memory usable by graphics device = 2048M
[   13.342151] [drm] Replacing VGA console driver
[   13.342654] Console: switching to colour dummy device 80x25
[   13.348084] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   13.348087] [drm] Driver supports precise vblank timestamp query.
[   13.348310] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   13.478619] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 163840 ms 
ovfl timer
[   13.478621] RAPL PMU: hw unit of domain pp0-core 2^-16 Joules
[   13.478622] RAPL PMU: hw unit of domain package 2^-16 Joules
[   13.478623] RAPL PMU: hw unit of domain pp1-gpu 2^-16 Joules
[   13.559369] snd_hda_codec_conexant hdaudioC0D0: CX20590: BIOS auto-probing.
[   13.559841] snd_hda_codec_conexant hdaudioC0D0: autoconfig for CX20590: 
line_outs=1 (0x1f/0x0/0x0/0x0/0x0) type:speaker
[   13.559842] snd_hda_codec_conexant hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   13.559843] snd_hda_codec_conexant hdaudioC0D0:hp_outs=2 
(0x1c/0x19/0x0/0x0/0x0)
[   13.559844] snd_hda_codec_conexant hdaudioC0D0:mono: mono_out=0x0
[   13.559844] snd_hda_codec_conexant hdaudioC0D0:inputs:
[   13.559846] snd_hda_codec_conexant hdaudioC0D0: 

Bug#853110: marked as done (linux-image-4.9.0-1-amd64: dvb usb fails to load)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#853110: fixed in linux 4.9.10-1
has caused the Debian Bug report #853110,
regarding linux-image-4.9.0-1-amd64: dvb usb fails to load
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.)


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

Dear Maintainer,

DVB usb device fails to load with linux 4.9 with the following error:

Jan 29 20:58:12 gandalf kernel: [   18.972611] Bluetooth: BNEP (Ethernet 
Emulation) ver 1.3
Jan 29 20:58:12 gandalf kernel: [   18.972613] Bluetooth: BNEP filters: 
protocol multicast
Jan 29 20:58:12 gandalf kernel: [   18.972617] Bluetooth: BNEP socket layer 
initialized
Jan 29 20:58:12 gandalf NetworkManager[649]:   [1485719892.9476] bluez: 
use BlueZ version 5
Jan 29 20:59:07 gandalf kernel: [   74.398182] usb 1-4: USB disconnect, device 
number 2
Jan 29 20:59:11 gandalf kernel: [   78.294727] usb 1-4: new high-speed USB 
device number 5 using ehci-pci
Jan 29 20:59:11 gandalf kernel: [   78.498959] usb 1-4: New USB device found, 
idVendor=2040, idProduct=9300
Jan 29 20:59:11 gandalf kernel: [   78.498966] usb 1-4: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Jan 29 20:59:11 gandalf kernel: [   78.498969] usb 1-4: Product: SOHO-FX2
Jan 29 20:59:11 gandalf kernel: [   78.498973] usb 1-4: Manufacturer: Hauppau⁧攀 
Jan 29 20:59:11 gandalf kernel: [   78.498976] usb 1-4: SerialNumber: 
9301-00-F008B260
Jan 29 20:59:11 gandalf kernel: [   78.527415] dvb_usb_dibusb_mc_common: 
Unknown symbol __symbol_get (err 0)
$ lsusb
Bus 012 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 011 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 2040:9300 Hauppauge WinTV NOVA-T USB2 (cold)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 009 Device 003: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel 
Mouse
Bus 009 Device 002: ID 046d:c316 Logitech, Inc. HID-Compliant Keyboard
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 2109:0811 VIA Labs, Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Another dvb device triggers an oops:

Jan 29 21:02:55 gandalf kernel: [  302.088936] usb 1-4: USB disconnect, device 
number 5
Jan 29 21:03:12 gandalf kernel: [  318.830302] usb 1-3: new high-speed USB 
device number 6 using ehci-pci
Jan 29 21:03:12 gandalf kernel: [  318.979191] usb 1-3: New USB device found, 
idVendor=2040, idProduct=5500
Jan 29 21:03:12 gandalf kernel: [  318.979198] usb 1-3: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
Jan 29 21:03:12 gandalf kernel: [  318.979202] usb 1-3: Product: WinTV MiniStick
Jan 29 21:03:12 gandalf kernel: [  318.979205] usb 1-3: Manufacturer: Hauppauge 
Computer Works
Jan 29 21:03:12 gandalf kernel: [  318.979208] usb 1-3: SerialNumber: f067e725
Jan 29 21:03:12 gandalf kernel: [  319.017475] smsusb:smsusb_probe: board id=8, 
interface number 0
Jan 29 21:03:12 gandalf kernel: [  319.020723] usb 1-3: firmware: 
direct-loading firmware sms1xxx-hcw-55xxx-dvbt-02.fw
Jan 29 21:03:12 gandalf kernel: [  319.530390] Registered IR keymap rc-hauppauge
Jan 29 21:03:12 gandalf kernel: [  319.530718] input: SMS IR (Hauppauge WinTV 
MiniStick) as /devices/pci:00/:00:12.2/usb1/1-3/rc/rc0/input19
Jan 29 21:03:12 gandalf kernel: [  319.530893] rc rc0: SMS IR (Hauppauge WinTV 
MiniStick) as /devices/pci:00/:00:12.2/usb1/1-3/rc/rc0
Jan 29 21:03:12 gandalf kernel: [  319.531677] smsusb:smsusb_probe: Device 
initialized with return code 0
Jan 29 21:03:12 gandalf kernel: [  319.535915] lirc_dev: IR Remote Control 
driver registered, major 246
Jan 29 21:03:12 gandalf kernel: [  319.538993] DVB: registering new adapter 
(Hauppauge WinTV MiniStick)
Jan 29 21:03:12 gandalf kernel: [  319.539007] rc rc0: lirc_dev: driver 
ir-lirc-codec (smsmdtv) registered at minor = 0
Jan 

Bug#852747: marked as done (enable kexec on arm64)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#852747: fixed in linux 4.9.10-1
has caused the Debian Bug report #852747,
regarding enable kexec on arm64
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.)


-- 
852747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 4.9.2-2

Hi! Please enable CONFIG_KEXEC on arm64. The userspace side landed in
unstable yesterday, and I verified that it works (at least in QEMU) w/
a Debian kernel rebuilt w/ CONFIG_KEXEC=y.

  -dann
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.10-1

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 852...@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: Fri, 17 Feb 2017 13:18:17 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 
btrfs-modules-4.9.0-2-alpha-generic-di ext4-modules-4.9.0-2-alpha-generic-di 
isofs-modules-4.9.0-2-alpha-generic-di jfs-modules-4.9.0-2-alpha-generic-di
 xfs-modules-4.9.0-2-alpha-generic-di fat-modules-4.9.0-2-alpha-generic-di 
md-modules-4.9.0-2-alpha-generic-di multipath-modules-4.9.0-2-alpha-generic-di 
usb-modules-4.9.0-2-alpha-generic-di 
usb-storage-modules-4.9.0-2-alpha-generic-di 
fb-modules-4.9.0-2-alpha-generic-di input-modules-4.9.0-2-alpha-generic-di 
event-modules-4.9.0-2-alpha-generic-di mouse-modules-4.9.0-2-alpha-generic-di 
nic-pcmcia-modules-4.9.0-2-alpha-generic-di 
pcmcia-modules-4.9.0-2-alpha-generic-di 
nic-usb-modules-4.9.0-2-alpha-generic-di sata-modules-4.9.0-2-alpha-generic-di 
crc-modules-4.9.0-2-alpha-generic-di crypto-modules-4.9.0-2-alpha-generic-di 
crypto-dm-modules-4.9.0-2-alpha-generic-di ata-modules-4.9.0-2-alpha-generic-di 
nbd-modules-4.9.0-2-alpha-generic-di squashfs-modules-4.9.0-2-alpha-generic-di 
virtio-modules-4.9.0-2-alpha-generic-di zlib-modules-4.9.0-2-alpha-generic-di 
fuse-modules-4.9.0-2-alpha-generic-di srm-modules-4.9.0-2-alpha-generic-di 
linux-image-4.9.0-2-alpha-generic
 linux-headers-4.9.0-2-alpha-generic linux-image-4.9.0-2-alpha-generic-dbgsym 
linux-image-4.9.0-2-alpha-smp linux-headers-4.9.0-2-alpha-smp 
linux-image-4.9.0-2-alpha-smp-dbgsym linux-headers-4.9.0-2-all-amd64 
linux-image-4.9.0-2-amd64-unsigned linux-headers-4.9.0-2-amd64 
linux-image-4.9.0-2-amd64-dbgsym linux-image-4.9.0-2-rt-amd64-unsigned 
linux-headers-4.9.0-2-rt-amd64 linux-image-4.9.0-2-rt-amd64-dbgsym 
linux-headers-4.9.0-2-all-arm64 linux-image-4.9.0-2-arm64-unsigned 
linux-headers-4.9.0-2-arm64 linux-image-4.9.0-2-arm64-dbgsym 
linux-headers-4.9.0-2-all-armel kernel-image-4.9.0-2-marvell-di 
nic-modules-4.9.0-2-marvell-di nic-shared-modules-4.9.0-2-marvell-di 
usb-serial-modules-4.9.0-2-marvell-di ppp-modules-4.9.0-2-marvell-di 
cdrom-core-modules-4.9.0-2-marvell-di scsi-core-modules-4.9.0-2-marvell-di 
loop-modules-4.9.0-2-marvell-di ipv6-modules-4.9.0-2-marvell-di 
btrfs-modules-4.9.0-2-marvell-di ext4-modules-4.9.0-2-marvell-di 
isofs-modules-4.9.0-2-marvell-di
 jffs2-modules-4.9.0-2-marvell-di jfs-modules-4.9.0-2-marvell-di 

Bug#852556: marked as done (linux-image-4.9.0-1-amd64: [Regression] Trendnet's TU-ET100C Pegasus II based LAN to USB adapter stopped to work)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#852556: fixed in linux 4.9.10-1
has caused the Debian Bug report #852556,
regarding linux-image-4.9.0-1-amd64: [Regression] Trendnet's TU-ET100C Pegasus 
II based LAN to USB adapter stopped to work
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.)


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

Hi! Running this version of the kernel I get:

[   86.479474] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet 
driver
[   86.480195] [ cut here ]
[   86.480219] WARNING: CPU: 0 PID: 2043 at 
/build/linux-fgnWKv/linux-4.9.2/drivers/usb/core/hcd.c:1584 
usb_hcd_map_urb_for_dma+0x37c/0x570 [usbcore]
[   86.480221] transfer buffer not dma capable
[   86.480223] Modules linked in: pegasus(+) mii pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_multiport iptable_filter 8021q 
garp mrp stp llc uinput binfmt_misc wl(POE) iTCO_wdt iTCO_vendor_support 
dell_wmi sparse_keymap dell_rbtn pcmcia kvm_intel dell_laptop dell_smbios 
dcdbas snd_hda_codec_hdmi kvm dell_smm_hwmon snd_hda_codec_idt i915 
snd_hda_codec_generic irqbypass cfg80211 yenta_socket evdev pcmcia_rsrc 
pcmcia_core joydev pcspkr snd_hda_intel serio_raw snd_hda_codec lpc_ich 
snd_hda_core mfd_core sg snd_hwdep snd_pcm rfkill snd_timer snd soundcore 
drm_kms_helper shpchp wmi drm i2c_algo_bit acpi_cpufreq video ac battery button 
tpm_tis tpm_tis_core tpm coretemp parport_pc ppdev lp parport ip_tables 
x_tables autofs4 ext4 crc16 jbd2 fscrypto ecb lrw glue_helper ablk_helper cryptd
[   86.480294]  aes_x86_64 mbcache xts gf128mul algif_skcipher af_alg dm_crypt 
dm_mod raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear 
md_mod sr_mod cdrom sd_mod psmouse i2c_i801 i2c_smbus ahci libahci libata 
sdhci_pci sdhci scsi_mod mmc_core firewire_ohci firewire_core crc_itu_t tg3 ptp 
pps_core libphy ehci_pci uhci_hcd ehci_hcd thermal usbcore usb_common
[   86.480339] CPU: 0 PID: 2043 Comm: systemd-udevd Tainted: P   OE   
4.9.0-1-amd64 #1 Debian 4.9.2-2
[   86.480341] Hardware name: Dell Inc. Latitude E5500  
/0X796D, BIOS A08 01/05/2009
[   86.480343]   9f728b84 b14681eef840 

[   86.480347]  9f476dbe a05a571ffd80 b14681eef898 

[   86.480351]  b14681eefa4c a05a558e7000 0001 
9f476e3f
[   86.480354] Call Trace:
[   86.480361]  [] ? dump_stack+0x5c/0x78
[   86.480365]  [] ? __warn+0xbe/0xe0
[   86.480368]  [] ? warn_slowpath_fmt+0x5f/0x80
[   86.480372]  [] ? schedule+0x32/0x80
[   86.480382]  [] ? usb_hcd_map_urb_for_dma+0x37c/0x570 
[usbcore]
[   86.480392]  [] ? usb_hcd_submit_urb+0x330/0xaa0 [usbcore]
[   86.480395]  [] ? enqueue_entity+0x30e/0x920
[   86.480398]  [] ? enqueue_task_fair+0x82/0x940
[   86.480408]  [] ? usb_start_wait_urb+0x6d/0x170 [usbcore]
[   86.480419]  [] ? usb_control_msg+0xdc/0x130 [usbcore]
[   86.480425]  [] ? set_register+0x50/0xa0 [pegasus]
[   86.480429]  [] ? read_eprom_word+0x31/0x100 [pegasus]
[   86.480433]  [] ? pegasus_probe+0x20c/0x840 [pegasus]
[   86.480437]  [] ? __pm_runtime_set_status+0x1bd/0x270
[   86.480447]  [] ? usb_probe_interface+0x15d/0x2c0 [usbcore]
[   86.480451]  [] ? driver_probe_device+0x21a/0x420
[   86.480453]  [] ? __driver_attach+0xda/0xe0
[   86.480456]  [] ? driver_probe_device+0x420/0x420
[   86.480459]  [] ? bus_for_each_dev+0x67/0xb0
[   86.480461]  [] ? bus_add_driver+0x16a/0x260
[   86.480464]  [] ? driver_register+0x57/0xc0
[   86.480474]  [] ? usb_register_driver+0x7b/0x130 [usbcore]
[   86.480476]  [] ? 0xc1155000
[   86.480480]  [] ? pegasus_init+0x164/0x1000 [pegasus]
[   86.480482]  [] ? 0xc1155000
[   86.480486]  [] ? do_one_initcall+0x4b/0x180
[   86.480490]  [] ? __vunmap+0x6d/0xc0
[   86.480493]  [] ? do_init_module+0x5b/0x1ed
[   86.480496]  [] ? load_module+0x2523/0x2a00
[   86.480499]  [] ? __symbol_put+0x60/0x60
[   86.480502]  [] ? SYSC_finit_module+0xc6/0xf0
[   86.480505]  [] ? do_syscall_64+0x7c/0xf0
[   86.480508]  [] ? entry_SYSCALL64_slow_path+0x25/0x25
[   86.480510] ---[ end trace 92d967e7878ff49b ]---
[   86.480618] (unnamed net_device) (uninitialized): read_eprom_word failed
[   86.480725] pegasus 6-2:1.0: can't reset MAC
[   86.480770] 

Bug#826614: marked as done (CONFIG_MAC_SCSI and CONFIG_MAC8390 are set to 'y')

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#826614: fixed in linux 4.9.10-1
has caused the Debian Bug report #826614,
regarding CONFIG_MAC_SCSI and CONFIG_MAC8390 are set to 'y'
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.)


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

In Linux v3.19, CONFIG_MAC_SCSI became a tristate option (instead of 
bool). In Linux v4.4, CONFIG_MAC8390 became a tristate option (it too was 
previously bool).

Please set CONFIG_MAC_SCSI=m and CONFIG_MAC8390=m for m68k kernel builds 
to reduce the size of the kernel binary. The former is a SCSI host adapter 
driver and the latter is an Ethernet NIC driver. Both drivers are only 
relevant to the Mac sub-architecture and are not used on Amiga, Atari etc.

-- 
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.10-1

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 826...@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: Fri, 17 Feb 2017 13:18:17 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 
btrfs-modules-4.9.0-2-alpha-generic-di ext4-modules-4.9.0-2-alpha-generic-di 
isofs-modules-4.9.0-2-alpha-generic-di jfs-modules-4.9.0-2-alpha-generic-di
 xfs-modules-4.9.0-2-alpha-generic-di fat-modules-4.9.0-2-alpha-generic-di 
md-modules-4.9.0-2-alpha-generic-di multipath-modules-4.9.0-2-alpha-generic-di 
usb-modules-4.9.0-2-alpha-generic-di 
usb-storage-modules-4.9.0-2-alpha-generic-di 
fb-modules-4.9.0-2-alpha-generic-di input-modules-4.9.0-2-alpha-generic-di 
event-modules-4.9.0-2-alpha-generic-di mouse-modules-4.9.0-2-alpha-generic-di 
nic-pcmcia-modules-4.9.0-2-alpha-generic-di 
pcmcia-modules-4.9.0-2-alpha-generic-di 
nic-usb-modules-4.9.0-2-alpha-generic-di sata-modules-4.9.0-2-alpha-generic-di 
crc-modules-4.9.0-2-alpha-generic-di crypto-modules-4.9.0-2-alpha-generic-di 
crypto-dm-modules-4.9.0-2-alpha-generic-di ata-modules-4.9.0-2-alpha-generic-di 
nbd-modules-4.9.0-2-alpha-generic-di squashfs-modules-4.9.0-2-alpha-generic-di 
virtio-modules-4.9.0-2-alpha-generic-di zlib-modules-4.9.0-2-alpha-generic-di 
fuse-modules-4.9.0-2-alpha-generic-di srm-modules-4.9.0-2-alpha-generic-di 
linux-image-4.9.0-2-alpha-generic
 linux-headers-4.9.0-2-alpha-generic linux-image-4.9.0-2-alpha-generic-dbgsym 
linux-image-4.9.0-2-alpha-smp linux-headers-4.9.0-2-alpha-smp 
linux-image-4.9.0-2-alpha-smp-dbgsym linux-headers-4.9.0-2-all-amd64 
linux-image-4.9.0-2-amd64-unsigned linux-headers-4.9.0-2-amd64 
linux-image-4.9.0-2-amd64-dbgsym linux-image-4.9.0-2-rt-amd64-unsigned 
linux-headers-4.9.0-2-rt-amd64 linux-image-4.9.0-2-rt-amd64-dbgsym 
linux-headers-4.9.0-2-all-arm64 linux-image-4.9.0-2-arm64-unsigned 
linux-headers-4.9.0-2-arm64 linux-image-4.9.0-2-arm64-dbgsym 
linux-headers-4.9.0-2-all-armel kernel-image-4.9.0-2-marvell-di 
nic-modules-4.9.0-2-marvell-di nic-shared-modules-4.9.0-2-marvell-di 
usb-serial-modules-4.9.0-2-marvell-di ppp-modules-4.9.0-2-marvell-di 

Bug#848682: marked as done (process accounting sometimes does not work)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#848682: fixed in linux 4.9.10-1
has caused the Debian Bug report #848682,
regarding process accounting sometimes does not work
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.)


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

Dear Ben, dear maintainers,

starting from a Debian bug report of mine, Gerlof Langeveld, developer
of system and process monitor atop¹, found two issues with process
accounting². I also started an LKML thread about these³.

[1] http://atoptool.nl/
[2] #833997 atop: process accounting does not work:
https://bugs.debian.org/833997
[3] [REGRESSION] Two issues that prevent process accounting (taskstats) from
working correctly: https://lkml.org/lkml/2016/12/19/182

I am reporting the two issues separately.

I am currently not running Debian a kernel, but Gerlof verified the issue with
Debian kernel. Pprocess accounting works with 3.16, but fails with 4.8 and
4.7 at least. I think it also fails with earlier versions, but I do not
know exactly since which version.


1) Sometimes process accounting does not work at all.

Bug 190271 - process accounting sometimes does not work 
https://bugzilla.kernel.org/show_bug.cgi?id=190271

The acct() system call (to activate process accounting) return value 0, 
which means that process accounting is activated successfully.
However, no process accounting records are written whatsoever. This 
situation can be reproduced with the program 'acctdemo.c'
that you can find as attachment. When this program gives the message 
"found a process accounting record!", the situation is okay
and process accounting works fine to the file '/tmp/mypacct'. When the 
message 'No process accounting record yet' is repeatedly given,
process accounting does not work and will not work at all. It might be 
that you have to start this program several times before you get
this situation (preferably start/finish lots of processes in the mean time).
This problem is probably caused by a new mechanism introduced in the 
kernel code (/linux/kernel/acct.c) that is called 'slow accounting'
and has to be solved in the kernel code.

I experience this problem on Debian8 with a 4.8 kernel and on CentOS7 
with a 4.8 kernel.

Thanks,
Martin

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

Kernel: Linux 4.8.14-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.10-1

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: Fri, 17 Feb 2017 13:18:17 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 

Bug#718548: marked as done (Please add bcache module udeb)

[Debian Bug Tracking System]

Your message dated Fri, 17 Feb 2017 20:00:13 +
with message-id 
and subject line Bug#718548: fixed in linux 4.9.10-1
has caused the Debian Bug report #718548,
regarding Please add bcache module udeb
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.)


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

Dear Maintainer,


Last kernel versions have added bcache to the system. It allows to use an SSD
drive as a cache for a -for example- a disk drive partition.

A common installation is /dev/sda as the main disk drive and /dev/sdb as a
cache drive for it. After a configuration like this, one gets the /dev/bcache0
device to mkfs the filesystem  on it, in a similar way to LVM or RAID. Even
more, bcache can be combined with these.

It would be nice if the installer gave these options to configure, for example,
at the moment, in an expert mode install. It would require bcache-tools at boot
and bcache as a module in the kernel.

You have more info at http://bcache.evilpiepirate.org/ and in kernel source at
./Documentation/bcache.txt

Thanks,
Josep



-- System Information:
Debian Release: 7.1
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-rc3 (SMP w/4 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-- 
--
Salutacions...Josep
--
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.9.10-1

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 718...@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: Fri, 17 Feb 2017 13:18:17 +
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-2 linux-doc-4.9 linux-manual-4.9 
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9 
libusbip-dev usbip hyperv-daemons linux-headers-4.9.0-2-common 
linux-headers-4.9.0-2-common-rt linux-libc-dev linux-headers-4.9.0-2-all 
linux-headers-4.9.0-2-all-alpha kernel-image-4.9.0-2-alpha-generic-di 
nic-modules-4.9.0-2-alpha-generic-di 
nic-wireless-modules-4.9.0-2-alpha-generic-di 
nic-shared-modules-4.9.0-2-alpha-generic-di 
serial-modules-4.9.0-2-alpha-generic-di 
usb-serial-modules-4.9.0-2-alpha-generic-di 
ppp-modules-4.9.0-2-alpha-generic-di pata-modules-4.9.0-2-alpha-generic-di 
cdrom-core-modules-4.9.0-2-alpha-generic-di 
scsi-core-modules-4.9.0-2-alpha-generic-di 
scsi-modules-4.9.0-2-alpha-generic-di loop-modules-4.9.0-2-alpha-generic-di 
btrfs-modules-4.9.0-2-alpha-generic-di ext4-modules-4.9.0-2-alpha-generic-di 
isofs-modules-4.9.0-2-alpha-generic-di jfs-modules-4.9.0-2-alpha-generic-di
 xfs-modules-4.9.0-2-alpha-generic-di fat-modules-4.9.0-2-alpha-generic-di 
md-modules-4.9.0-2-alpha-generic-di multipath-modules-4.9.0-2-alpha-generic-di 
usb-modules-4.9.0-2-alpha-generic-di 
usb-storage-modules-4.9.0-2-alpha-generic-di 
fb-modules-4.9.0-2-alpha-generic-di input-modules-4.9.0-2-alpha-generic-di 
event-modules-4.9.0-2-alpha-generic-di mouse-modules-4.9.0-2-alpha-generic-di 
nic-pcmcia-modules-4.9.0-2-alpha-generic-di 
pcmcia-modules-4.9.0-2-alpha-generic-di 
nic-usb-modules-4.9.0-2-alpha-generic-di sata-modules-4.9.0-2-alpha-generic-di 
crc-modules-4.9.0-2-alpha-generic-di crypto-modules-4.9.0-2-alpha-generic-di 
crypto-dm-modules-4.9.0-2-alpha-generic-di ata-modules-4.9.0-2-alpha-generic-di 
nbd-modules-4.9.0-2-alpha-generic-di squashfs-modules-4.9.0-2-alpha-generic-di 
virtio-modules-4.9.0-2-alpha-generic-di zlib-modules-4.9.0-2-alpha-generic-di 
fuse-modules-4.9.0-2-alpha-generic-di srm-modules-4.9.0-2-alpha-generic-di 
linux-image-4.9.0-2-alpha-generic
 linux-headers-4.9.0-2-alpha-generic linux-image-4.9.0-2-alpha-generic-dbgsym 
linux-image-4.9.0-2-alpha-smp 

linux_4.9.10-1_multi.changes is NEW

[Debian FTP Masters]

binary:affs-modules-4.9.0-2-4kc-malta-di is NEW.
binary:affs-modules-4.9.0-2-5kc-malta-di is NEW.
binary:affs-modules-4.9.0-2-loongson-3-di is NEW.
binary:affs-modules-4.9.0-2-octeon-di is NEW.
binary:ata-modules-4.9.0-2-4kc-malta-di is NEW.
binary:ata-modules-4.9.0-2-5kc-malta-di is NEW.
binary:ata-modules-4.9.0-2-loongson-3-di is NEW.
binary:btrfs-modules-4.9.0-2-4kc-malta-di is NEW.
binary:btrfs-modules-4.9.0-2-5kc-malta-di is NEW.
binary:btrfs-modules-4.9.0-2-loongson-3-di is NEW.
binary:btrfs-modules-4.9.0-2-marvell-di is NEW.
binary:btrfs-modules-4.9.0-2-octeon-di is NEW.
binary:cdrom-core-modules-4.9.0-2-4kc-malta-di is NEW.
binary:cdrom-core-modules-4.9.0-2-5kc-malta-di is NEW.
binary:cdrom-core-modules-4.9.0-2-loongson-3-di is NEW.
binary:cdrom-core-modules-4.9.0-2-marvell-di is NEW.
binary:cdrom-core-modules-4.9.0-2-octeon-di is NEW.
binary:crc-modules-4.9.0-2-4kc-malta-di is NEW.
binary:crc-modules-4.9.0-2-5kc-malta-di is NEW.
binary:crc-modules-4.9.0-2-loongson-3-di is NEW.
binary:crc-modules-4.9.0-2-marvell-di is NEW.
binary:crc-modules-4.9.0-2-octeon-di is NEW.
binary:crypto-dm-modules-4.9.0-2-4kc-malta-di is NEW.
binary:crypto-dm-modules-4.9.0-2-5kc-malta-di is NEW.
binary:crypto-dm-modules-4.9.0-2-loongson-3-di is NEW.
binary:crypto-dm-modules-4.9.0-2-marvell-di is NEW.
binary:crypto-dm-modules-4.9.0-2-octeon-di is NEW.
binary:crypto-modules-4.9.0-2-4kc-malta-di is NEW.
binary:crypto-modules-4.9.0-2-5kc-malta-di is NEW.
binary:crypto-modules-4.9.0-2-loongson-3-di is NEW.
binary:crypto-modules-4.9.0-2-marvell-di is NEW.
binary:crypto-modules-4.9.0-2-octeon-di is NEW.
binary:event-modules-4.9.0-2-4kc-malta-di is NEW.
binary:event-modules-4.9.0-2-5kc-malta-di is NEW.
binary:event-modules-4.9.0-2-loongson-3-di is NEW.
binary:event-modules-4.9.0-2-marvell-di is NEW.
binary:event-modules-4.9.0-2-octeon-di is NEW.
binary:ext4-modules-4.9.0-2-4kc-malta-di is NEW.
binary:ext4-modules-4.9.0-2-5kc-malta-di is NEW.
binary:ext4-modules-4.9.0-2-loongson-3-di is NEW.
binary:ext4-modules-4.9.0-2-marvell-di is NEW.
binary:ext4-modules-4.9.0-2-octeon-di is NEW.
binary:fat-modules-4.9.0-2-4kc-malta-di is NEW.
binary:fat-modules-4.9.0-2-5kc-malta-di is NEW.
binary:fat-modules-4.9.0-2-loongson-3-di is NEW.
binary:fat-modules-4.9.0-2-marvell-di is NEW.
binary:fat-modules-4.9.0-2-octeon-di is NEW.
binary:fb-modules-4.9.0-2-loongson-3-di is NEW.
binary:fb-modules-4.9.0-2-marvell-di is NEW.
binary:firewire-core-modules-4.9.0-2-loongson-3-di is NEW.
binary:fuse-modules-4.9.0-2-4kc-malta-di is NEW.
binary:fuse-modules-4.9.0-2-5kc-malta-di is NEW.
binary:fuse-modules-4.9.0-2-loongson-3-di is NEW.
binary:fuse-modules-4.9.0-2-marvell-di is NEW.
binary:fuse-modules-4.9.0-2-octeon-di is NEW.
binary:hfs-modules-4.9.0-2-4kc-malta-di is NEW.
binary:hfs-modules-4.9.0-2-5kc-malta-di is NEW.
binary:hfs-modules-4.9.0-2-loongson-3-di is NEW.
binary:hfs-modules-4.9.0-2-octeon-di is NEW.
binary:i2c-modules-4.9.0-2-4kc-malta-di is NEW.
binary:i2c-modules-4.9.0-2-5kc-malta-di is NEW.
binary:input-modules-4.9.0-2-4kc-malta-di is NEW.
binary:input-modules-4.9.0-2-5kc-malta-di is NEW.
binary:input-modules-4.9.0-2-loongson-3-di is NEW.
binary:input-modules-4.9.0-2-marvell-di is NEW.
binary:input-modules-4.9.0-2-octeon-di is NEW.
binary:ipv6-modules-4.9.0-2-marvell-di is NEW.
binary:isofs-modules-4.9.0-2-4kc-malta-di is NEW.
binary:isofs-modules-4.9.0-2-5kc-malta-di is NEW.
binary:isofs-modules-4.9.0-2-loongson-3-di is NEW.
binary:isofs-modules-4.9.0-2-marvell-di is NEW.
binary:isofs-modules-4.9.0-2-octeon-di is NEW.
binary:jffs2-modules-4.9.0-2-marvell-di is NEW.
binary:jfs-modules-4.9.0-2-4kc-malta-di is NEW.
binary:jfs-modules-4.9.0-2-5kc-malta-di is NEW.
binary:jfs-modules-4.9.0-2-loongson-3-di is NEW.
binary:jfs-modules-4.9.0-2-marvell-di is NEW.
binary:jfs-modules-4.9.0-2-octeon-di is NEW.
binary:kernel-image-4.9.0-2-4kc-malta-di is NEW.
binary:kernel-image-4.9.0-2-5kc-malta-di is NEW.
binary:kernel-image-4.9.0-2-loongson-3-di is NEW.
binary:kernel-image-4.9.0-2-marvell-di is NEW.
binary:kernel-image-4.9.0-2-octeon-di is NEW.
binary:leds-modules-4.9.0-2-marvell-di is NEW.
binary:linux-headers-4.9.0-2-4kc-malta is NEW.
binary:linux-headers-4.9.0-2-5kc-malta is NEW.
binary:linux-headers-4.9.0-2-686 is NEW.
binary:linux-headers-4.9.0-2-686-pae is NEW.
binary:linux-headers-4.9.0-2-all is NEW.
binary:linux-headers-4.9.0-2-all-amd64 is NEW.
binary:linux-headers-4.9.0-2-all-arm64 is NEW.
binary:linux-headers-4.9.0-2-all-armel is NEW.
binary:linux-headers-4.9.0-2-all-armhf is NEW.
binary:linux-headers-4.9.0-2-all-i386 is NEW.
binary:linux-headers-4.9.0-2-all-mips is NEW.
binary:linux-headers-4.9.0-2-all-mips64el is NEW.
binary:linux-headers-4.9.0-2-all-mipsel is NEW.
binary:linux-headers-4.9.0-2-all-powerpc is NEW.
binary:linux-headers-4.9.0-2-all-ppc64el is NEW.
binary:linux-headers-4.9.0-2-all-s390x is NEW.
binary:linux-headers-4.9.0-2-amd64 is NEW.
binary:linux-headers-4.9.0-2-arm64 is NEW.
binary:linux-headers-4.9.0-2-armmp is NEW.

Processing of linux_4.9.10-1_multi.changes

[Debian FTP Masters]

linux_4.9.10-1_multi.changes uploaded successfully to localhost
along with the files:
  linux_4.9.10-1.dsc
  linux_4.9.10.orig.tar.xz
  linux_4.9.10-1.debian.tar.xz
  linux_4.9.10-1_source.buildinfo
  linux-doc-4.9_4.9.10-1_all.deb
  linux-headers-4.9.0-2-common-rt_4.9.10-1_all.deb
  linux-headers-4.9.0-2-common_4.9.10-1_all.deb
  linux-manual-4.9_4.9.10-1_all.deb
  linux-source-4.9_4.9.10-1_all.deb
  linux-support-4.9.0-2_4.9.10-1_all.deb

Greetings,

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

Re: Which version of firmware-iwlwifi support Intel Wireless 8260?

[慕冬亮]

On Feb 17, 2017 8:32 AM, "Ben Hutchings"  wrote:

On Thu, 2017-02-16 at 23:32 -0500, mudonglianga...@gmail.com wrote:
> Hello all,
>
> I have a laptop with Intel Wireless 8260. Its information is in the
> following:
>
> 01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
>   Subsystem: Intel Corporation Wireless 8260
>   Flags: bus master, fast devsel, latency 0, IRQ 134
>   Memory at e120 (64-bit, non-prefetchable) [size=8K]
>   Capabilities: 
>   Kernel driver in use: iwlwifi
>   Kernel modules: iwlwifi
>
> My Debian Stretch has perfect support for this driver, and the version
> of firmware-iwlwifi is 20161130-2.
>
> However, my friend whose system is Debian Stable found his wireless
> card is not working after he installed firmware-iwlwifi.
>
> I searched and found the version firmware-iwlwifi package is different
> between Debian Stretch and Debian Stable. Does firmware-iwlwifi package
>  of Debian Stable not support Intel wireless 8260?

It does not, and neither does the kernel (it was added in Linux 3.18
and hasn't been backported).

> If my friend does not want to upgrade to Debian Stretch, is it ok to
> add jessie-backports software source?

Yes.  He will need to install both the kernel and firmwarepackages from
there:

apt install -t jessie-backports linux-image-amd64 firmware-iwlwifi


Thank you very much. I will ask my friend to install those two packages
from jessie-backports. If he has any feedback, I will let you know.

Best regards.

Dongliang Mu


Ben.

--
Ben Hutchings
Any sufficiently advanced bug is indistinguishable from a feature.

Processed: severity of 855395 is important

[Debian Bug Tracking System]

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

> severity 855395 important
Bug #855395 [firmware-atheros] firmware-atheros have buggy firmwares for AR3011 
bluetooth (ath3k)
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Re: Which version of firmware-iwlwifi support Intel Wireless 8260?

[Ben Hutchings]

On Thu, 2017-02-16 at 23:32 -0500, mudonglianga...@gmail.com wrote:
> Hello all, 
> 
> I have a laptop with Intel Wireless 8260. Its information is in the
> following:
> 
> 01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
>   Subsystem: Intel Corporation Wireless 8260
>   Flags: bus master, fast devsel, latency 0, IRQ 134
>   Memory at e120 (64-bit, non-prefetchable) [size=8K]
>   Capabilities: 
>   Kernel driver in use: iwlwifi
>   Kernel modules: iwlwifi
> 
> My Debian Stretch has perfect support for this driver, and the version
> of firmware-iwlwifi is 20161130-2.
> 
> However, my friend whose system is Debian Stable found his wireless
> card is not working after he installed firmware-iwlwifi.
> 
> I searched and found the version firmware-iwlwifi package is different
> between Debian Stretch and Debian Stable. Does firmware-iwlwifi package
>  of Debian Stable not support Intel wireless 8260?

It does not, and neither does the kernel (it was added in Linux 3.18
and hasn't been backported).

> If my friend does not want to upgrade to Debian Stretch, is it ok to
> add jessie-backports software source?

Yes.  He will need to install both the kernel and firmwarepackages from
there:

apt install -t jessie-backports linux-image-amd64 firmware-iwlwifi

Ben.

-- 
Ben Hutchings
Any sufficiently advanced bug is indistinguishable from a feature.


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

Bug#855395: firmware-atheros have buggy firmwares for AR3011 bluetooth (ath3k)

[sniskorodov]

Package: firmware-atheros
Version: 20160110-1~bpo8+1
Severity: grave
Tags: patch
Justification: renders package unusable

Hi, I have found that with firmwares for notebook internal bluetooth adapter
AR3011 (AthrBT_0x11020100.dfu, ramps_0x11020100_40.dfu) from package, bluetooth
working incorrect with headset (frequently interrupts sound, and wrote error
messages in dmesg).
=-=-=-=
[  207.491195] Bluetooth: hci0 SCO packet for unknown connection handle 60
[  207.511120] Bluetooth: hci0 SCO packet for unknown connection handle 47615
[  207.521126] Bluetooth: hci0 SCO packet for unknown connection handle 65497
[  207.531118] Bluetooth: hci0 SCO packet for unknown connection handle 9
[  207.531125] Bluetooth: hci0 SCO packet for unknown connection handle 7168
[  207.541148] Bluetooth: hci0 SCO packet for unknown connection handle 76
[  207.551120] Bluetooth: hci0 SCO packet for unknown connection handle 57344
=-=-=-=

So, I found working firmwares in this thread
https://forums.gentoo.org/viewtopic-t-1013336-start-0.html
Can you replace it in package, please?



-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

firmware-atheros depends on no packages.

firmware-atheros recommends no packages.

Versions of packages firmware-atheros suggests:
ii  initramfs-tools  0.120+deb8u2

-- no debconf information


AthrBT_0x11020100.dfu
Description: Binary data


ramps_0x11020100_40.dfu
Description: Binary data

Bug#855183: linux-image-4.9.0-0.bpo.1-amd64: modprobe intel_rapl_perf stay in uninterruptible sleep

[Thomas Gleixner]

On Fri, 17 Feb 2017, Ben Hutchings wrote:
> On Wed, 2017-02-15 at 09:08 +0100, Miloslav Hula wrote:
> [...]
> > When I boot the system up, there is a constant load 1.0. I found one
> > process systemd-udevd in uninterruptible sleep.
> > Digging in proc/PID/fd I found, this proces usees fd 7 for
> > intel_rapl_perf.ko
> > 
> > * What exactly did you do (or not do) that was effective (or
> > ineffective)?
> > I rmmod intel_rapl_perf, the systemd-udevd process disappeared. I
> > tried to load intel_rapl_perf manually.
> > 
> > * What was the outcome of this action?
> > Now, the modprobe is in uninterruptible sleep
> [...]
> 
> Here's a traceback for that:
> 
> > [ 1090.784260]  a079b6c9d000  a089b8ffa0c0 
> > a079b688c140
> > [ 1090.784265]  a089bf2987c0 c1d3ce12bb30 929f536d 
> > a089bf3d8828
> > [ 1090.784268]  c1d3ce12bb60 924b0afe a089bf2987c0 
> > a079b688c140
> > [ 1090.784272] Call Trace:
> > [ 1090.784284]  [] ? __schedule+0x23d/0x6d0
> > [ 1090.784308]  [] ? uncore_cpu_prepare+0x100/0x100 
> > [intel_uncore]
> > [ 1090.784310]  [] ? schedule+0x32/0x80
> > [ 1090.784316]  [] ? schedule_timeout+0x21c/0x3c0
> > [ 1090.784327]  [] ? enqueue_task_fair+0x74/0x950
> > [ 1090.784329]  [] ? __schedule+0x245/0x6d0
> > [ 1090.784336]  [] ? sched_clock+0x5/0x10
> > [ 1090.784344]  [] ? uncore_cpu_prepare+0x100/0x100 
> > [intel_uncore]
> > [ 1090.784347]  [] ? wait_for_completion+0xfa/0x130
> > [ 1090.784353]  [] ? wake_up_q+0x60/0x60
> > [ 1090.784358]  [] ? cpuhp_issue_call+0x96/0xc0
> > [ 1090.784361]  [] ? __cpuhp_setup_state+0xca/0x200
> > [ 1090.784369]  [] ? intel_uncore_init+0x1f7/0xeaa 
> > [intel_uncore]

Unfortunately that tells us only that something waits forever, but we don't
see the stuff which does not invoke complete().

AFAICT thats a cpuhp thread which should run the cpu starting or online
callback.

What's really confusing is this information from the bug report:

" When I changed:

  Power technology:
  - from Energy Efficient
  - to Custom

  Energy Performance BIAS Setting:
  - from Balanced Performance
  - to Performance

  problem disappeared. systemd-udevd starts normally, module can be 
  normally rmmod/insmod'ed now, load is 0.07."

Miloslav: Is there any chance you can try a 4.10-rc8 kernel on that
machine?

Thanks,

tglx

Re: Bug#718548: bcache in D-I

[Samuel Thibault]

Ben Hutchings, on ven. 17 févr. 2017 02:30:58 +, wrote:
> On Sat, 2017-02-04 at 05:47 +0100, Cyril Brulebois wrote:
> > It would probably make sense to turn this into a wishlist bug report
> > against src:linux so that we get an extra udeb to be used in expert mode
> > indeed. I'm not sure anyone is going to do more integration work on the
> > d-i side, so we could probably just reassign this bug report to
> > src:linux?
> 
> I'll add bcache to md-modules, as it seems to belong there (source is
> even under drivers/md).

Ah, good thing indeed :)

Samuel