Bug#779515: Should enable the qxl kernel driver when installed

[Ben Hutchings]

On Sat, 2015-11-07 at 00:24 +0100, Laurent Bigonville wrote:
> reassign 779515 linux-image-4.2.0-1-amd64
> severity 779515 important
> thanks
> 
> On Sun, 01 Mar 2015 18:47:54 + Ben Hutchings  
> wrote:
> 
>  > I've enabled the kernel's qxl driver, but disabled by default so that
>  > it doesn't conflict with wheezy's version of xserver-xorg-video-qxl.
>  >
>  > Please install a modprobe configuration file with the line:
>  >
>  > options qxl modeset=1
>  >
>  > (When I tried this on a VM host with virt-manager and QEMU from sid,
>  > the qxl driver complained of missing features, so KMS still didn't
>  > work. However, the fall-back to UMS still worked.)
> 
> Shouldn't the qxl kernel module be enabled by default in unstable now 
> that the xserver-xorg-video-qxl package has been updated?
[...]

Only if xserver-xorg-video-qxl in jessie works properly with KMS.  Is
that the case?

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

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

Processed: Re: Should enable the qxl kernel driver when installed

[Debian Bug Tracking System]

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

> reassign 779515 linux-image-4.2.0-1-amd64
Bug #779515 [src:xserver-xorg-video-qxl] Should enable the qxl kernel driver 
when installed
Bug reassigned from package 'src:xserver-xorg-video-qxl' to 
'linux-image-4.2.0-1-amd64'.
No longer marked as found in versions xserver-xorg-video-qxl/0.1.1-2.
Ignoring request to alter fixed versions of bug #779515 to the same values 
previously set
> severity 779515 important
Bug #779515 [linux-image-4.2.0-1-amd64] Should enable the qxl kernel driver 
when installed
Ignoring request to change severity of Bug 779515 to the same value.
> thanks
Stopping processing here.

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

Bug#804295: initramfs-tools: doesn't warn/fail when dpkg triggers for update-initramfs don't actually update

[Christoph Anton Mitterer]

Package: initramfs-tools
Version: 0.120
Severity: normal


Hi.

I've just noted the following:
Processing triggers for initramfs-tools (0.120) ...
update-initramfs: /boot/initrd.img-4.2.0-1-amd64 has been altered.
update-initramfs: Cannot update. Override with -t option.

Not sure what caused it to think that I've modified it,... nevertheless.
such a status message will likely just drown in the flood of log messages
during any update.
And in such case the initramfs may stay stale, which could cause quite
some troubles,... from non booting systems up to even security issues.


I'm not sure whether it would be better to simply let the trigger use -t,
cause this may be undesired either.

Would there be a way to give a more interactive warning (e.g. debconf)?
Or does it seem reasonable in such a case to fail the trigger?

Cheers,
Chris.

Bug#803159: linux: Enable DT support for armel/orion5x arch

[Roger Shimizu]

Patch appended, to avoid any misunderstanding.
 - 0001 is both OK for sid and jessie
 - 0002 is only necessary for sid, or other 4.x kernel series (e.g.
jessie-backport)

Thank you!

Cheers,
Roger
From ecc1733be537bf5c2583b50a0664b583cf294b37 Mon Sep 17 00:00:00 2001
From: Roger Shimizu 
Date: Tue, 27 Oct 2015 22:28:43 +0900
Subject: [PATCH 1/2] [armel/orion5x] enable DT support

Signed-off-by: Roger Shimizu 
---
 debian/config/armel/config.orion5x | 10 ++
 1 file changed, 10 insertions(+)

diff --git a/debian/config/armel/config.orion5x b/debian/config/armel/config.orion5x
index a7f4888..1e4703f 100644
--- a/debian/config/armel/config.orion5x
+++ b/debian/config/armel/config.orion5x
@@ -8,6 +8,8 @@ CONFIG_PCI=y
 CONFIG_UACCESS_WITH_MEMCPY=y
 CONFIG_ZBOOT_ROM_TEXT=0x0
 CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_ARM_APPENDED_DTB=y
+CONFIG_ARM_ATAG_DTB_COMPAT=y
 CONFIG_CMDLINE=""
 # CONFIG_XIP_KERNEL is not set
 CONFIG_ATAGS_PROC=y
@@ -23,6 +25,7 @@ CONFIG_VFP=y
 ##
 CONFIG_MACH_DB88F5281=y
 CONFIG_MACH_RD88F5182=y
+CONFIG_MACH_RD88F5182_DT=y
 CONFIG_MACH_KUROBOX_PRO=y
 CONFIG_MACH_DNS323=y
 CONFIG_MACH_TS209=y
@@ -264,6 +267,7 @@ CONFIG_MTD=y
 # CONFIG_MTD_REDBOOT_PARTS is not set
 CONFIG_MTD_CMDLINE_PARTS=y
 # CONFIG_MTD_AFS_PARTS is not set
+CONFIG_MTD_OF_PARTS=y
 CONFIG_MTD_BLOCK=y
 CONFIG_FTL=m
 CONFIG_NFTL=m
@@ -318,6 +322,7 @@ CONFIG_MTD_CFI_STAA=m
 ## file: drivers/mtd/maps/Kconfig
 ##
 # CONFIG_MTD_COMPLEX_MAPPINGS is not set
+CONFIG_MTD_PHYSMAP_OF=y
 # CONFIG_MTD_IMPA7 is not set
 # CONFIG_MTD_INTEL_VR_NOR is not set
 # CONFIG_MTD_PLATRAM is not set
@@ -487,6 +492,11 @@ CONFIG_RTC_DRV_S35390A=y
 # CONFIG_SSB is not set
 
 ##
+## file: drivers/tty/serial/Kconfig
+##
+CONFIG_SERIAL_OF_PLATFORM=y
+
+##
 ## file: drivers/tty/serial/8250/Kconfig
 ##
 CONFIG_SERIAL_8250=y
-- 
2.1.4

From d2f7318266850e3dd87ea9b045031a3871b8a055 Mon Sep 17 00:00:00 2001
From: Roger Shimizu 
Date: Sat, 7 Nov 2015 11:35:57 +0900
Subject: [PATCH 2/2] [armel/orion5x] Enable DEBUG_LL_UART_8250, to replace
 DEBUG_ICEDCC, which is default since Linux 4.0 and hangs booting on
 armel/orion5x

Signed-off-by: Roger Shimizu 
---
 debian/config/armel/config.orion5x | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/config/armel/config.orion5x b/debian/config/armel/config.orion5x
index 1e4703f..00404b9 100644
--- a/debian/config/armel/config.orion5x
+++ b/debian/config/armel/config.orion5x
@@ -16,6 +16,13 @@ CONFIG_ATAGS_PROC=y
 CONFIG_VFP=y
 
 ##
+## file: arch/arm/Kconfig.debug
+##
+## choice: Kernel low-level debugging port
+CONFIG_DEBUG_LL_UART_8250=y
+## end choice
+
+##
 ## file: arch/arm/mach-imx/Kconfig
 ##
 # CONFIG_ARCH_MXC is not set
-- 
2.1.4

Processed: affects 779515

[Debian Bug Tracking System]

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

> affects 779515 xserver-xorg-video-qxl
Bug #779515 [linux-image-4.2.0-1-amd64] Should enable the qxl kernel driver 
when installed
Added indication that 779515 affects xserver-xorg-video-qxl
> thanks
Stopping processing here.

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

Bug#802432: fixed, can be closed.

[Jos van Wolput]

Dear Maintainer,

Issue fixed in version linux-image-4.3.0-trunk-amd64 (4.3-1~exp1).
Bug #802432 can be closed.

-- System Information:
Debian Release: sid + experimental
Architecture: amd64 (x86_64)
Kernel: linux-image-4.3.0-trunk-amd64
Systemd: 227-2

Kind regards,
Jos v.Wolput

Processed: Re: [Pkg-xen-devel] Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 3.16.7-ckt11-1+deb8u5
Bug #799122 [xen-hypervisor-4.4-amd64] xen-hypervisor-4.4-amd64: Networking of 
domUs stops working after a few minutes
Bug reassigned from package 'xen-hypervisor-4.4-amd64' to 'src:linux'.
No longer marked as found in versions xen/4.4.1-9+deb8u1.
Ignoring request to alter fixed versions of bug #799122 to the same values 
previously set
Bug #799122 [src:linux] xen-hypervisor-4.4-amd64: Networking of domUs stops 
working after a few minutes
The source 'linux' and version '3.16.7-ckt11-1+deb8u5' do not appear to match 
any binary packages
Marked as found in versions linux/3.16.7-ckt11-1+deb8u5.
> found -1 4.1.3-1~bpo8+1
Bug #799122 [src:linux] xen-hypervisor-4.4-amd64: Networking of domUs stops 
working after a few minutes
Marked as found in versions linux/4.1.3-1~bpo8+1.

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

Bug#803899: marked as done (linux-image-4.2.0-1-amd64: Intel NUC built-in SD card reader requires PINCTRL module support)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 11:00:40 +
with message-id 
and subject line Bug#797949: fixed in linux 4.3-1~exp1
has caused the Debian Bug report #797949,
regarding linux-image-4.2.0-1-amd64: Intel NUC built-in SD card reader requires 
PINCTRL module support
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.)


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

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

Dear Maintainer,

(Resending bug report because the Debian BTS appears to
have dropped my previous message from another account.
Sorry if this is a dupe.)

The built-in SDHC card reader on my Intel 5th Generation
Braswell NUC (NUC5PPYH) doesn't work under Debian Unstable
running Linux kernel 4.2. The card reader, however, works
fine under an Ubuntu 15.10 live USB session, which runs
a differently configured Linux 4.2 kernel.

Below is a comparison between the runtime kernel
messages and kernel configuration for both Debian Unstable
and Ubuntu 15.10 (Wily Werewolf).

The important difference between the Debian and Ubuntu
kernels with regard my problem is the enabling of several
PINCTRL options in the Ubuntu kernel config.

Comparison between the relevant parts of dmesg output for
Debian Unstable and Ubuntu Wily Werewolf (15.10):

$ dmesg | grep -i sdhci #Debian Unstable
[1.237764] sdhci: Secure Digital Host Controller Interface driver
[1.237770] sdhci: Copyright(c) Pierre Ossman
[1.263087] sdhci-pci :00:12.0: SDHCI controller found 
[8086:2296] (rev 21)

[1.263442] sdhci-pci :00:12.0: failed to setup card detect gpio
[1.264537] sdhci-pci :00:12.0: No vmmc regulator found
[1.264543] sdhci-pci :00:12.0: No vqmmc regulator found
[1.268300] mmc0: SDHCI controller on PCI [:00:12.0] using ADMA

$ dmesg | grep -i sdhci #Ubuntu 15.10
[   11.433662] sdhci: Secure Digital Host Controller Interface driver
[   11.433666] sdhci: Copyright(c) Pierre Ossman
[   11.472483] sdhci-pci :00:12.0: SDHCI controller found 
[8086:2296] (rev 21)

[   11.473841] sdhci-pci :00:12.0: No vmmc regulator found
[   11.473845] sdhci-pci :00:12.0: No vqmmc regulator found
[   11.477273] mmc0: SDHCI controller on PCI [:00:12.0] using ADMA

Proof that the pinctrl driver can be compiled as a module:

$ lsmod | grep -Ei 'sdhci|pinctrl' #Debian Unstable
sdhci_pci  24576  0
sdhci_acpi 16384  0
sdhci  40960  2 sdhci_acpi,sdhci_pci
mmc_core  126976  3 sdhci,sdhci_acpi,sdhci_pci

$ lsmod | grep -Ei 'sdhci|pinctrl' #Ubuntu 15.10
sdhci_pci  24576  0
sdhci_acpi 16384  0
sdhci  45056  2 sdhci_acpi,sdhci_pci
pinctrl_cherryview 32768  2

Comparison between relevant portions of Debian and Ubuntu
kernel configs:

$ grep -i pinctrl /boot/config-4.2.0-1-amd64 #Debian Unstable
# CONFIG_I2C_MUX_PINCTRL is not set
CONFIG_PINCTRL=y
# CONFIG_DEBUG_PINCTRL is not set
# CONFIG_PINCTRL_AMD is not set
# CONFIG_PINCTRL_BAYTRAIL is not set
# CONFIG_PINCTRL_CHERRYVIEW is not set
# CONFIG_PINCTRL_SUNRISEPOINT is not set

$ grep -i pinctrl /boot/config-4.2.0-16-generic #Ubuntu 15.10
CONFIG_I2C_MUX_PINCTRL=m
CONFIG_PINCTRL=y
# CONFIG_DEBUG_PINCTRL is not set
CONFIG_PINCTRL_AMD=y
CONFIG_PINCTRL_BAYTRAIL=y
CONFIG_PINCTRL_CHERRYVIEW=m
CONFIG_PINCTRL_INTEL=m
CONFIG_PINCTRL_SUNRISEPOINT=m

$ lspci #Debian Unstable
00:00.0 Host bridge: Intel Corporation Device 2280 (rev 21)
00:02.0 VGA compatible controller: Intel Corporation Device 22b1 (rev 
21)

00:12.0 SD Host controller: Intel Corporation Device 2296 (rev 21)
00:13.0 SATA controller: Intel Corporation Device 22a3 (rev 21)
00:14.0 USB controller: Intel Corporation Device 22b5 (rev 21)
00:18.0 DMA controller: Intel Corporation Device 22c0 (rev 21)
00:18.6 Serial bus controller [0c80]: Intel Corporation Device 22c6 (rev 
21)
00:18.7 Serial bus controller [0c80]: Intel Corporation Device 22c7 (rev 
21)

00:1a.0 Encryption controller: Intel Corporation Device 2298 (rev 21)
00:1b.0 Audio device: Intel Corporation Device 2284 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 22c8 (rev 21)
00:1c.1 PCI bridge: Intel Corporation Device 22ca (rev 21)
00:1c.2 PCI bridge: Intel Corporation Device 22cc (rev 21)
00:1f.0 ISA bridge: Intel Corporation Device 229c (rev 21)
00:1f.3 SMBus: Intel Corporation Device 2292 (rev 21)
02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
03:00.0 Ethernet controller: Realtek Semiconductor Co., 

Bug#803370: marked as done (linux: missing netfilter modules)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 11:00:40 +
with message-id 
and subject line Bug#803370: fixed in linux 4.3-1~exp1
has caused the Debian Bug report #803370,
regarding linux: missing netfilter modules
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Dear maintainers,

thanks for your work in the linux kernel :-)

current kernel configs seems to lack some netfilter modules, with these config 
symbols:
 * CONFIG_NFT_REDIR_IPV4
 * CONFIG_NFT_REDIR_IPV6
 * CONFIG_NF_DUP_IPV4
 * CONFIG_NF_DUP_IPV6
 * CONFIG_NFT_DUP_IPV4
 * CONFIG_NFT_DUP_IPV6
 * CONFIG_NETFILTER_XT_TARGET_NOTRACK

I've checked 4.3~rc7-1~exp1 in sources.d.n, and seems to lack the configs as 
well.

Could you please enable them?

Thanks.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.3-1~exp1

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 803...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Nov 2015 07:45:13 +
Source: linux
Binary: linux-source-4.3 linux-doc-4.3 linux-manual-4.3 
linux-support-4.3.0-trunk linux-libc-dev linux-headers-4.3.0-trunk-all 
linux-headers-4.3.0-trunk-all-alpha kernel-image-4.3.0-trunk-alpha-generic-di 
nic-modules-4.3.0-trunk-alpha-generic-di 
nic-wireless-modules-4.3.0-trunk-alpha-generic-di 
nic-shared-modules-4.3.0-trunk-alpha-generic-di 
serial-modules-4.3.0-trunk-alpha-generic-di 
usb-serial-modules-4.3.0-trunk-alpha-generic-di 
ppp-modules-4.3.0-trunk-alpha-generic-di 
pata-modules-4.3.0-trunk-alpha-generic-di 
cdrom-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-modules-4.3.0-trunk-alpha-generic-di 
scsi-common-modules-4.3.0-trunk-alpha-generic-di 
scsi-extra-modules-4.3.0-trunk-alpha-generic-di 
loop-modules-4.3.0-trunk-alpha-generic-di 
btrfs-modules-4.3.0-trunk-alpha-generic-di 
ext4-modules-4.3.0-trunk-alpha-generic-di 
isofs-modules-4.3.0-trunk-alpha-generic-di 
jfs-modules-4.3.0-trunk-alpha-generic-di
 xfs-modules-4.3.0-trunk-alpha-generic-di 
fat-modules-4.3.0-trunk-alpha-generic-di 
md-modules-4.3.0-trunk-alpha-generic-di 
multipath-modules-4.3.0-trunk-alpha-generic-di 
usb-modules-4.3.0-trunk-alpha-generic-di 
usb-storage-modules-4.3.0-trunk-alpha-generic-di 
fb-modules-4.3.0-trunk-alpha-generic-di 
input-modules-4.3.0-trunk-alpha-generic-di 
event-modules-4.3.0-trunk-alpha-generic-di 
mouse-modules-4.3.0-trunk-alpha-generic-di 
nic-pcmcia-modules-4.3.0-trunk-alpha-generic-di 
pcmcia-modules-4.3.0-trunk-alpha-generic-di 
nic-usb-modules-4.3.0-trunk-alpha-generic-di 
sata-modules-4.3.0-trunk-alpha-generic-di 
core-modules-4.3.0-trunk-alpha-generic-di 
crc-modules-4.3.0-trunk-alpha-generic-di 
crypto-modules-4.3.0-trunk-alpha-generic-di 
crypto-dm-modules-4.3.0-trunk-alpha-generic-di 
ata-modules-4.3.0-trunk-alpha-generic-di 
nbd-modules-4.3.0-trunk-alpha-generic-di 
squashfs-modules-4.3.0-trunk-alpha-generic-di 
virtio-modules-4.3.0-trunk-alpha-generic-di
 zlib-modules-4.3.0-trunk-alpha-generic-di 
fuse-modules-4.3.0-trunk-alpha-generic-di 
srm-modules-4.3.0-trunk-alpha-generic-di linux-headers-4.3.0-trunk-common 
linux-image-4.3.0-trunk-alpha-generic linux-headers-4.3.0-trunk-alpha-generic 
linux-image-4.3.0-trunk-alpha-smp linux-headers-4.3.0-trunk-alpha-smp 
linux-headers-4.3.0-trunk-all-amd64 kernel-image-4.3.0-trunk-amd64-di 
nic-modules-4.3.0-trunk-amd64-di nic-wireless-modules-4.3.0-trunk-amd64-di 
nic-shared-modules-4.3.0-trunk-amd64-di serial-modules-4.3.0-trunk-amd64-di 
usb-serial-modules-4.3.0-trunk-amd64-di ppp-modules-4.3.0-trunk-amd64-di 
pata-modules-4.3.0-trunk-amd64-di cdrom-core-modules-4.3.0-trunk-amd64-di 
firewire-core-modules-4.3.0-trunk-amd64-di 
scsi-core-modules-4.3.0-trunk-amd64-di 

Bug#803323: marked as done (linux: postinst: typo "dangling linkto")

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 11:00:40 +
with message-id 
and subject line Bug#803323: fixed in linux 4.3-1~exp1
has caused the Debian Bug report #803323,
regarding linux: postinst: typo "dangling linkto"
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.)


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

Source: linux
Severity: minor
Tags: patch

--
Jakub Wilk
diff --git a/debian/templates/image.plain.postinst.in b/debian/templates/image.plain.postinst.in
index 439d4b8..5551895 100755
--- a/debian/templates/image.plain.postinst.in
+++ b/debian/templates/image.plain.postinst.in
@@ -198,7 +198,7 @@ sub move_p {
 
   if (!defined($vmlinuz_target) || ! -f "$real_target") {
 # what, a dangling symlink?
-warn "The link "  . $image_dest . "$kimage is a dangling link" .
+warn "The link "  . $image_dest . "$kimage is a dangling link " .
   "to $real_target\n";
 $force_move = 1;
 return $force_move;
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.3-1~exp1

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 803...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Nov 2015 07:45:13 +
Source: linux
Binary: linux-source-4.3 linux-doc-4.3 linux-manual-4.3 
linux-support-4.3.0-trunk linux-libc-dev linux-headers-4.3.0-trunk-all 
linux-headers-4.3.0-trunk-all-alpha kernel-image-4.3.0-trunk-alpha-generic-di 
nic-modules-4.3.0-trunk-alpha-generic-di 
nic-wireless-modules-4.3.0-trunk-alpha-generic-di 
nic-shared-modules-4.3.0-trunk-alpha-generic-di 
serial-modules-4.3.0-trunk-alpha-generic-di 
usb-serial-modules-4.3.0-trunk-alpha-generic-di 
ppp-modules-4.3.0-trunk-alpha-generic-di 
pata-modules-4.3.0-trunk-alpha-generic-di 
cdrom-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-modules-4.3.0-trunk-alpha-generic-di 
scsi-common-modules-4.3.0-trunk-alpha-generic-di 
scsi-extra-modules-4.3.0-trunk-alpha-generic-di 
loop-modules-4.3.0-trunk-alpha-generic-di 
btrfs-modules-4.3.0-trunk-alpha-generic-di 
ext4-modules-4.3.0-trunk-alpha-generic-di 
isofs-modules-4.3.0-trunk-alpha-generic-di 
jfs-modules-4.3.0-trunk-alpha-generic-di
 xfs-modules-4.3.0-trunk-alpha-generic-di 
fat-modules-4.3.0-trunk-alpha-generic-di 
md-modules-4.3.0-trunk-alpha-generic-di 
multipath-modules-4.3.0-trunk-alpha-generic-di 
usb-modules-4.3.0-trunk-alpha-generic-di 
usb-storage-modules-4.3.0-trunk-alpha-generic-di 
fb-modules-4.3.0-trunk-alpha-generic-di 
input-modules-4.3.0-trunk-alpha-generic-di 
event-modules-4.3.0-trunk-alpha-generic-di 
mouse-modules-4.3.0-trunk-alpha-generic-di 
nic-pcmcia-modules-4.3.0-trunk-alpha-generic-di 
pcmcia-modules-4.3.0-trunk-alpha-generic-di 
nic-usb-modules-4.3.0-trunk-alpha-generic-di 
sata-modules-4.3.0-trunk-alpha-generic-di 
core-modules-4.3.0-trunk-alpha-generic-di 
crc-modules-4.3.0-trunk-alpha-generic-di 
crypto-modules-4.3.0-trunk-alpha-generic-di 
crypto-dm-modules-4.3.0-trunk-alpha-generic-di 
ata-modules-4.3.0-trunk-alpha-generic-di 
nbd-modules-4.3.0-trunk-alpha-generic-di 
squashfs-modules-4.3.0-trunk-alpha-generic-di 
virtio-modules-4.3.0-trunk-alpha-generic-di
 zlib-modules-4.3.0-trunk-alpha-generic-di 
fuse-modules-4.3.0-trunk-alpha-generic-di 
srm-modules-4.3.0-trunk-alpha-generic-di linux-headers-4.3.0-trunk-common 
linux-image-4.3.0-trunk-alpha-generic linux-headers-4.3.0-trunk-alpha-generic 
linux-image-4.3.0-trunk-alpha-smp linux-headers-4.3.0-trunk-alpha-smp 
linux-headers-4.3.0-trunk-all-amd64 kernel-image-4.3.0-trunk-amd64-di 
nic-modules-4.3.0-trunk-amd64-di nic-wireless-modules-4.3.0-trunk-amd64-di 
nic-shared-modules-4.3.0-trunk-amd64-di serial-modules-4.3.0-trunk-amd64-di 
usb-serial-modules-4.3.0-trunk-amd64-di ppp-modules-4.3.0-trunk-amd64-di 
pata-modules-4.3.0-trunk-amd64-di 

Bug#797949: marked as done (linux: CONFIG_PINCTRL_BAYTRAIL=y needed for microSD slot to function on Intel Compute Stick)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 11:00:40 +
with message-id 
and subject line Bug#797949: fixed in linux 4.3-1~exp1
has caused the Debian Bug report #797949,
regarding linux: CONFIG_PINCTRL_BAYTRAIL=y needed for microSD slot to function 
on Intel Compute Stick
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.)


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

Dear Maintainer,

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

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

Suggested fix:

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

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

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

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

Thanks,
Henry Hallam
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.3-1~exp1

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 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Nov 2015 07:45:13 +
Source: linux
Binary: linux-source-4.3 linux-doc-4.3 linux-manual-4.3 
linux-support-4.3.0-trunk linux-libc-dev linux-headers-4.3.0-trunk-all 
linux-headers-4.3.0-trunk-all-alpha kernel-image-4.3.0-trunk-alpha-generic-di 
nic-modules-4.3.0-trunk-alpha-generic-di 
nic-wireless-modules-4.3.0-trunk-alpha-generic-di 
nic-shared-modules-4.3.0-trunk-alpha-generic-di 
serial-modules-4.3.0-trunk-alpha-generic-di 
usb-serial-modules-4.3.0-trunk-alpha-generic-di 
ppp-modules-4.3.0-trunk-alpha-generic-di 
pata-modules-4.3.0-trunk-alpha-generic-di 
cdrom-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-modules-4.3.0-trunk-alpha-generic-di 
scsi-common-modules-4.3.0-trunk-alpha-generic-di 
scsi-extra-modules-4.3.0-trunk-alpha-generic-di 
loop-modules-4.3.0-trunk-alpha-generic-di 
btrfs-modules-4.3.0-trunk-alpha-generic-di 
ext4-modules-4.3.0-trunk-alpha-generic-di 
isofs-modules-4.3.0-trunk-alpha-generic-di 
jfs-modules-4.3.0-trunk-alpha-generic-di
 xfs-modules-4.3.0-trunk-alpha-generic-di 
fat-modules-4.3.0-trunk-alpha-generic-di 
md-modules-4.3.0-trunk-alpha-generic-di 
multipath-modules-4.3.0-trunk-alpha-generic-di 
usb-modules-4.3.0-trunk-alpha-generic-di 
usb-storage-modules-4.3.0-trunk-alpha-generic-di 
fb-modules-4.3.0-trunk-alpha-generic-di 
input-modules-4.3.0-trunk-alpha-generic-di 
event-modules-4.3.0-trunk-alpha-generic-di 
mouse-modules-4.3.0-trunk-alpha-generic-di 
nic-pcmcia-modules-4.3.0-trunk-alpha-generic-di 

Bug#804079: linux-image-3.16.0-4-amd64: Kernel panic on Xen virtualisation in Debian

[Ian Campbell]

Control: found -1 3.16.7-ckt11-1+deb8u5
Control: notfound -1 3.16.7-ckt11-1

Thanks for your report.

On Wed, 2015-11-04 at 18:53 +0100, Jan Prunk wrote:
> Package: src:linux
> Version: 3.16.7-ckt11-1

>From your text and the screenshot I think this should really be
+deb8u5. I've updated the bug metadata with the first lines.

> Severity: important
> 
> Dear Maintainer,


> The following kernel panic error appears at random in Xen
> virtualisation.

As in it has appeared randomly from time to time (i.e. more than once)
or you've had a single random instance?

> Please look at the error in screenshot attachment.
> It's a Debian 8, Kernel 3.16.7-ckt11-1+deb8u5, Xen 4.4.4-pre

The screenshot shows a fault at 0x812b6dad == memcpy+0xd,
called from ndisc_send_redirect+0x3bf.

Unfortunately disassembling memcpy from what I think is the correct dbg
package[0] results in:

Dump of assembler code for function memcpy:
   0x812b6da0 <+0>: mov%rdi,%rax
   0x812b6da3 <+3>: cmp$0x20,%rdx
   0x812b6da7 <+7>: jb 0x812b6e27

   0x812b6da9 <+9>: cmp%dil,%sil
   0x812b6dac <+12>:jl 0x812b6de3

   0x812b6dae <+14>:sub$0x20,%rdx
   0x812b6db2 <+18>:sub$0x20,%rdx

i.e. the faulting %rip (0x812b6dad) is not on an instruction
boundary (it would be in the middle of that jl instruction, which
cannot happen).

The call in ndisc_send_redirect disassembles sensibly and matches up
ok.

If I decode the faulting address as if it were on an instruction
boundary then I get:

(gdb) x/i 0x812b6dad
   0x812b6dad :  xor$0x20ea8348,%eax

which isn't accessing RAM and therefore surely cannot fault.

The version you have given is corroborated by the screenshot and I am
pretty I have got the correct dbg package to match.

I suppose you haven't rebuilt the kernel or anything like that?

I don't like to put things down to "cosmic rays", but if this was a one
off then I'm struggling to think of anything else to explain what
appears to be a single bit error in %rip.

At this point I would normally ask if you had run memtest86 etc on the
machine (i.e. if the RAM is known to be solid), but this seems to be a
register and not memory related.

> It's a production machine so not much detailed further testing can be
> provided in time.
> The information below (bugreport) is executed from a different
> machine, so the info provided below is not matching the original
> machine where the error appears !

FYI it is possible to run reportbug on a machine but get it to write
the report to a file for transfer and sending from another machine.

Ian.

[0] 
http://security.debian.org/debian-security/pool/updates/main/l/linux/linux-image-3.16.0-4-amd64-dbg_3.16.7-ckt11-1+deb8u5_amd64.deb
 => /usr/lib/debug/vmlinux-3.16.0-4-amd64

Processed: Re: Bug#804079: linux-image-3.16.0-4-amd64: Kernel panic on Xen virtualisation in Debian

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.16.7-ckt11-1+deb8u5
Bug #804079 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on Xen 
virtualisation in Debian
The source 'linux' and version '3.16.7-ckt11-1+deb8u5' do not appear to match 
any binary packages
Marked as found in versions linux/3.16.7-ckt11-1+deb8u5.
> notfound -1 3.16.7-ckt11-1
Bug #804079 [src:linux] linux-image-3.16.0-4-amd64: Kernel panic on Xen 
virtualisation in Debian
No longer marked as found in versions linux/3.16.7-ckt11-1.

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

Bug#803159: linux: Enable DT support for armel/orion5x arch

[Roger Shimizu]

I have good news.

> If you can figure out why the LS-WTGL doesn't work and that can be
> fixed (i.e. it turns out to be something other than the size) then I
> see no problem with adding support for the LS-WTGL platform.

I finished "git bisect" and good commit is 1553282b11e and bad one is
c544d987d9572 (in debian kernel repo).
So 3.19.3-1~exp2 is bootable, but 4.0-1~exp1 is non-bootable.
I compared the configs, and find former has DEBUG_ICEDCC and latter
has DEBUG_LL_UART_NONE.
I also find it's not possible to set DEBUG_LL_UART_NONE for 4.0 kernel.
After some searches, I tried to set DEBUG_LL_UART_8250 for 4.0 kernel,
then the kernel became bootable on my orion5x device!

I also find evidences this change is necessary starting for new 4.x kernel:
1. kirkwood changed from 3.16's DEBUG_LL_UART_NONE to 4.x's
DEBUG_MVEBU_UART0_ALTERNATE: commit bf56620e4 and 58669ce1 (in debian
kernel repo)
2. mainline kernel changed to DEBUG_LL_UART_8250 for orion5x arch:
commit 34c64a5d8 (in upstream repo)

So I think it's now safe to turn on DEBUG_LL_UART_8250 and merge my patch.
Thank you!

Cheers,
Roger

Bug#803159: linux: Enable DT support for armel/orion5x arch

[Ian Campbell]

On Fri, 2015-11-06 at 23:53 +0900, Roger Shimizu wrote:
> So I think it's now safe to turn on DEBUG_LL_UART_8250 and merge my
> patch.

Great, thanks for tracking that down. 

It's a bit odd that DEBUG_LL_UART_NONE fails (after all it should be
doing nothing) but given that this flavour supports a single SOC which
all have the same UART (AFAICT, it's on in upstream orion5x defconfig
at least) I think there's no reason not to do this.

When I tried this I also got CONFIG_DEBUG_ICEDCC coming on. From the
Kconfig help I don't think we want this at all ("Note that the system
will appear to hang during boot if there is nothing connected to read
from the DCC.") so I have disabled it. Please let me know if you think
we want this for some reason.

I'll kick off a local build with this in now and push once it's done.
(I'm away this w/e, so might be next week)

Ian.

Bug#803159: linux: Enable DT support for armel/orion5x arch

[Roger Shimizu]

Thanks for the feedback!

> It's a bit odd that DEBUG_LL_UART_NONE fails (after all it should be
> doing nothing) but given that this flavour supports a single SOC which
> all have the same UART (AFAICT, it's on in upstream orion5x defconfig
> at least) I think there's no reason not to do this.

DEBUG_LL_UART_NONE seems to be removed from upstream, that's why both
orion5x and kirkwood changed behavior.

> When I tried this I also got CONFIG_DEBUG_ICEDCC coming on. From the
> Kconfig help I don't think we want this at all ("Note that the system
> will appear to hang during boot if there is nothing connected to read
> from the DCC.") so I have disabled it. Please let me know if you think
> we want this for some reason.

I don't need DEBUG_ICEDCC.
DEBUG_LL seems only have one implementation. I just append
DEBUG_LL_UART_8250 to debian/config/armel/config.orion5x, then
DEBUG_ICEDCC went away by itself.

> I'll kick off a local build with this in now and push once it's done.
> (I'm away this w/e, so might be next week)

No problem for me. Thank you!

Cheers,
Roger

Bug#797779:

[Pau Garcia i Quiles]

You can get the .txt file from this EFI variable:

/sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113

as explained in the kernel documentation:

https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#firmware_installation1

Problem is brcmfmac does not do that automatically :-(

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

Bug#802598: marked as done (linux-image-4.2.0-1-powerpc64le: Please include MLX5 again)

[Debian Bug Tracking System]

Your message dated Fri, 06 Nov 2015 17:08:59 +
with message-id <1446829739.6006.3.ca...@decadent.org.uk>
and subject line Re: Bug#802598: Acknowledgement 
(linux-image-4.2.0-1-powerpc64le: Please include MLX5 again)
has caused the Debian Bug report #802598,
regarding linux-image-4.2.0-1-powerpc64le: Please include MLX5 again
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.)


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

Please re-include the MLX5 Infiniband driver; it was included in 4.0 and 4.1,
but is not any longer with 4.2 and later:

[root@power:~] # ls -al /lib/modules/
insgesamt 24
drwxr-xr-x  6 root root 4096 Okt 21 15:33 .
drwxr-xr-x 16 root root 4096 Sep 22 13:04 ..
drwxr-xr-x  3 root root 4096 Jul 15 13:22 4.0.0-2-powerpc64le
drwxr-xr-x  4 root root 4096 Okt  6 09:15 4.1.0-2-powerpc64le
drwxr-xr-x  4 root root 4096 Okt 21 15:58 4.2.0-1-powerpc64le
drwxr-xr-x  2 root root 4096 Okt 21 15:33 4.3.0-rc5-powerpc64le
[root@power:~] # find /lib/modules/ -iname "*mlx5*" -type f
/lib/modules/4.0.0-2-powerpc64le/kernel/drivers/infiniband/hw/mlx5/mlx5_ib.ko
/lib/modules/4.0.0-2-powerpc64le/kernel/drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko
/lib/modules/4.1.0-2-powerpc64le/kernel/drivers/infiniband/hw/mlx5/mlx5_ib.ko
/lib/modules/4.1.0-2-powerpc64le/kernel/drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko

--- /boot/config-4.1.0-2-powerpc64le2015-08-25 21:56:27.0 +0200
+++ /boot/config-4.2.0-1-powerpc64le2015-10-14 21:20:17.0 +0200
@@ -1,6 +1,6 @@
 #
 # Automatically generated file; DO NOT EDIT.
-# Linux/powerpc 4.1.6 Kernel Configuration
+# Linux/powerpc 4.2.3 Kernel Configuration
 #
 CONFIG_PPC64=y

...
@@ -2146,7 +2167,7 @@
 CONFIG_MLX4_EN_VXLAN=y
 CONFIG_MLX4_CORE=m
 CONFIG_MLX4_DEBUG=y
-CONFIG_MLX5_CORE=m
+# CONFIG_MLX5_CORE is not set
 CONFIG_NET_VENDOR_MICREL=y
 # CONFIG_KS8851 is not set
 # CONFIG_KS8851_MLL is not set


-- Package-specific info:
** Version:
Linux version 4.2.0-1-powerpc64le (debian-kernel@lists.debian.org) (gcc version 
4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.2.3-1 (2015-10-06)

** Command line:
root=UUID=fd411e11-7c8a-4e93-bee0-4b1d277b1778 ro quiet

0005:01:00.0 Infiniband controller [0207]: Mellanox Technologies MT27700 Family 
[ConnectX-4] [15b3:1013]
Subsystem: Mellanox Technologies Device [15b3:0014]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Device Serial Number ba-da-ce-55-de-ad-ca-fe
Capabilities: [110 v1] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta:  RxErr- BadTLP- BadDLLP+ Rollover- Timeout- NonFatalErr+
CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 04, GenCap+ CGenEn+ ChkCap+ ChkEn+
Capabilities: [170 v1] Alternative Routing-ID Interpretation (ARI)
ARICap: MFVC- ACS-, Next Function: 1
ARICtl: MFVC- ACS-, Function Group: 0
Capabilities: [1c0 v1] #19

0005:01:00.1 Infiniband controller [0207]: Mellanox Technologies MT27700 Family 
[ConnectX-4] [15b3:1013]
Subsystem: Mellanox Technologies Device [15b3:0014]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Device Serial Number ba-da-ce-55-de-ad-ca-fe
Capabilities: [110 v1] Advanced Error Reporting
UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
RxOF- 

linux_4.3-1~exp1_multi.changes ACCEPTED into experimental, experimental

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 04 Nov 2015 07:45:13 +
Source: linux
Binary: linux-source-4.3 linux-doc-4.3 linux-manual-4.3 
linux-support-4.3.0-trunk linux-libc-dev linux-headers-4.3.0-trunk-all 
linux-headers-4.3.0-trunk-all-alpha kernel-image-4.3.0-trunk-alpha-generic-di 
nic-modules-4.3.0-trunk-alpha-generic-di 
nic-wireless-modules-4.3.0-trunk-alpha-generic-di 
nic-shared-modules-4.3.0-trunk-alpha-generic-di 
serial-modules-4.3.0-trunk-alpha-generic-di 
usb-serial-modules-4.3.0-trunk-alpha-generic-di 
ppp-modules-4.3.0-trunk-alpha-generic-di 
pata-modules-4.3.0-trunk-alpha-generic-di 
cdrom-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-core-modules-4.3.0-trunk-alpha-generic-di 
scsi-modules-4.3.0-trunk-alpha-generic-di 
scsi-common-modules-4.3.0-trunk-alpha-generic-di 
scsi-extra-modules-4.3.0-trunk-alpha-generic-di 
loop-modules-4.3.0-trunk-alpha-generic-di 
btrfs-modules-4.3.0-trunk-alpha-generic-di 
ext4-modules-4.3.0-trunk-alpha-generic-di 
isofs-modules-4.3.0-trunk-alpha-generic-di 
jfs-modules-4.3.0-trunk-alpha-generic-di
 xfs-modules-4.3.0-trunk-alpha-generic-di 
fat-modules-4.3.0-trunk-alpha-generic-di 
md-modules-4.3.0-trunk-alpha-generic-di 
multipath-modules-4.3.0-trunk-alpha-generic-di 
usb-modules-4.3.0-trunk-alpha-generic-di 
usb-storage-modules-4.3.0-trunk-alpha-generic-di 
fb-modules-4.3.0-trunk-alpha-generic-di 
input-modules-4.3.0-trunk-alpha-generic-di 
event-modules-4.3.0-trunk-alpha-generic-di 
mouse-modules-4.3.0-trunk-alpha-generic-di 
nic-pcmcia-modules-4.3.0-trunk-alpha-generic-di 
pcmcia-modules-4.3.0-trunk-alpha-generic-di 
nic-usb-modules-4.3.0-trunk-alpha-generic-di 
sata-modules-4.3.0-trunk-alpha-generic-di 
core-modules-4.3.0-trunk-alpha-generic-di 
crc-modules-4.3.0-trunk-alpha-generic-di 
crypto-modules-4.3.0-trunk-alpha-generic-di 
crypto-dm-modules-4.3.0-trunk-alpha-generic-di 
ata-modules-4.3.0-trunk-alpha-generic-di 
nbd-modules-4.3.0-trunk-alpha-generic-di 
squashfs-modules-4.3.0-trunk-alpha-generic-di 
virtio-modules-4.3.0-trunk-alpha-generic-di
 zlib-modules-4.3.0-trunk-alpha-generic-di 
fuse-modules-4.3.0-trunk-alpha-generic-di 
srm-modules-4.3.0-trunk-alpha-generic-di linux-headers-4.3.0-trunk-common 
linux-image-4.3.0-trunk-alpha-generic linux-headers-4.3.0-trunk-alpha-generic 
linux-image-4.3.0-trunk-alpha-smp linux-headers-4.3.0-trunk-alpha-smp 
linux-headers-4.3.0-trunk-all-amd64 kernel-image-4.3.0-trunk-amd64-di 
nic-modules-4.3.0-trunk-amd64-di nic-wireless-modules-4.3.0-trunk-amd64-di 
nic-shared-modules-4.3.0-trunk-amd64-di serial-modules-4.3.0-trunk-amd64-di 
usb-serial-modules-4.3.0-trunk-amd64-di ppp-modules-4.3.0-trunk-amd64-di 
pata-modules-4.3.0-trunk-amd64-di cdrom-core-modules-4.3.0-trunk-amd64-di 
firewire-core-modules-4.3.0-trunk-amd64-di 
scsi-core-modules-4.3.0-trunk-amd64-di scsi-modules-4.3.0-trunk-amd64-di 
scsi-common-modules-4.3.0-trunk-amd64-di 
scsi-extra-modules-4.3.0-trunk-amd64-di loop-modules-4.3.0-trunk-amd64-di 
btrfs-modules-4.3.0-trunk-amd64-di ext4-modules-4.3.0-trunk-amd64-di
 isofs-modules-4.3.0-trunk-amd64-di jfs-modules-4.3.0-trunk-amd64-di 
ntfs-modules-4.3.0-trunk-amd64-di xfs-modules-4.3.0-trunk-amd64-di 
fat-modules-4.3.0-trunk-amd64-di md-modules-4.3.0-trunk-amd64-di 
multipath-modules-4.3.0-trunk-amd64-di usb-modules-4.3.0-trunk-amd64-di 
usb-storage-modules-4.3.0-trunk-amd64-di 
pcmcia-storage-modules-4.3.0-trunk-amd64-di fb-modules-4.3.0-trunk-amd64-di 
input-modules-4.3.0-trunk-amd64-di event-modules-4.3.0-trunk-amd64-di 
mouse-modules-4.3.0-trunk-amd64-di nic-pcmcia-modules-4.3.0-trunk-amd64-di 
pcmcia-modules-4.3.0-trunk-amd64-di nic-usb-modules-4.3.0-trunk-amd64-di 
sata-modules-4.3.0-trunk-amd64-di core-modules-4.3.0-trunk-amd64-di 
acpi-modules-4.3.0-trunk-amd64-di i2c-modules-4.3.0-trunk-amd64-di 
crc-modules-4.3.0-trunk-amd64-di crypto-modules-4.3.0-trunk-amd64-di 
crypto-dm-modules-4.3.0-trunk-amd64-di efi-modules-4.3.0-trunk-amd64-di 
ata-modules-4.3.0-trunk-amd64-di mmc-core-modules-4.3.0-trunk-amd64-di
 mmc-modules-4.3.0-trunk-amd64-di nbd-modules-4.3.0-trunk-amd64-di 
squashfs-modules-4.3.0-trunk-amd64-di speakup-modules-4.3.0-trunk-amd64-di 
virtio-modules-4.3.0-trunk-amd64-di uinput-modules-4.3.0-trunk-amd64-di 
sound-modules-4.3.0-trunk-amd64-di hyperv-modules-4.3.0-trunk-amd64-di 
udf-modules-4.3.0-trunk-amd64-di fuse-modules-4.3.0-trunk-amd64-di 
linux-image-4.3.0-trunk-amd64 linux-headers-4.3.0-trunk-amd64 
linux-image-4.3.0-trunk-amd64-dbg xen-linux-system-4.3.0-trunk-amd64 
linux-headers-4.3.0-trunk-all-arm64 kernel-image-4.3.0-trunk-arm64-di 
nic-modules-4.3.0-trunk-arm64-di nic-wireless-modules-4.3.0-trunk-arm64-di 
nic-shared-modules-4.3.0-trunk-arm64-di ppp-modules-4.3.0-trunk-arm64-di 
cdrom-core-modules-4.3.0-trunk-arm64-di scsi-core-modules-4.3.0-trunk-arm64-di 
scsi-modules-4.3.0-trunk-arm64-di loop-modules-4.3.0-trunk-arm64-di 
btrfs-modules-4.3.0-trunk-arm64-di ext4-modules-4.3.0-trunk-arm64-di 

Bug#804260: linux-image-4.2.0-1-amd64 fails to boot with IOMMU enabled in BIOS

[Sergey Pushkin]

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

Dear Maintainer,

after upgrading to linux-image-4.2.0-1-amd64 from
linux-image-4.1.0-2-amd64 system could not boot with new kernel

during boot these messages are displayed:

Loading, please wait...
[1.417184] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:11.0 domain=0x0005 
address=0x flags=0x0020]
[2.362377] sd 7:0:0:0: [sda] No Caching mode page found
[2.362488] sd 7:0:0:0: [sda] Assuming drive cache: write through
[6.899586] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:11.0 domain=0x0005 
address=0x flags=0x0020]
[   17.373134] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:11.0 domain=0x0005 
address=0x flags=0x0020]
  lvmetad is not active yet, using direct activation during sysinit
  Volume group "erida-vg" not found
  Cannot process volume group erida-vg
  ... skipped last 3 lines repeating
Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdlint)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mapper/erida--vg-root does not exist. Dropping to a shell!
modprobe: module ehci-orion not found in modules.dep

BusyBox v1.22.1 (Debian 1:1.22.0-15) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

and boot process ends up with initramfs prompt.

previous 4.1.0-2 kernel can boot as usual
disabling IOMMU in BIOS allows new kernel to boot too


-- Package-specific info:
** Version:
Linux version 4.2.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 
(Debian 4.9.3-5) ) #1 SMP Debian 4.2.5-1 (2015-10-27)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.2.0-1-amd64 root=/dev/mapper/erida--vg-root ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[2.264133] scsi 7:0:0:0: Direct-Access SPCC PHD  1.08 
PQ: 0 ANSI: 4
[2.264819] usbcore: registered new interface driver snd-usb-audio
[2.264966] uvcvideo: Found UVC 1.00 device FaceCam 312 (0458:7076)
[2.268631] radeon :00:01.0: fence driver on ring 6 use gpu addr 
0x3c18 and cpu addr 0x88008ee33c18
[2.268636] radeon :00:01.0: fence driver on ring 7 use gpu addr 
0x3c1c and cpu addr 0x88008ee33c1c
[2.268639] radeon :00:01.0: fence driver on ring 1 use gpu addr 
0x3c04 and cpu addr 0x88008ee33c04
[2.268642] radeon :00:01.0: fence driver on ring 2 use gpu addr 
0x3c08 and cpu addr 0x88008ee33c08
[2.268645] radeon :00:01.0: fence driver on ring 3 use gpu addr 
0x3c0c and cpu addr 0x88008ee33c0c
[2.268647] radeon :00:01.0: fence driver on ring 4 use gpu addr 
0x3c10 and cpu addr 0x88008ee33c10
[2.268684] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[2.268685] [drm] Driver supports precise vblank timestamp query.
[2.268689] radeon :00:01.0: radeon: MSI limited to 32-bit
[2.268730] radeon :00:01.0: radeon: using MSI.
[2.269014] [drm] radeon: irq initialized.
[2.269028] sd 7:0:0:0: Attached scsi generic sg1 type 0
[2.269226] sd 7:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 
GiB)
[2.269691] sd 7:0:0:0: [sdb] Write Protect is off
[2.269694] sd 7:0:0:0: [sdb] Mode Sense: 23 00 00 00
[2.270034] sd 7:0:0:0: [sdb] No Caching mode page found
[2.270069] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[2.271240]  sdb: sdb1
[2.272190] sd 7:0:0:0: [sdb] Attached SCSI disk
[2.275835] sha256_ssse3: Using AVX optimized SHA-256 implementation
[2.276055] Adding 1499132k swap on /dev/mapper/erida--vg-swap_1.  
Priority:-1 extents:1 across:1499132k SSFS
[2.284597] input: FaceCam 312 as 
/devices/pci:00/:00:13.0/usb8/8-4/8-4:1.0/input/input14
[2.284669] usbcore: registered new interface driver uvcvideo
[2.284671] USB Video Class driver (1.1.1)
[2.288323] [drm] ring test on 0 succeeded in 2 usecs
[2.288332] [drm] ring test on 3 succeeded in 3 usecs
[2.288338] [drm] ring test on 4 succeeded in 3 usecs
[2.334139] [drm] ring test on 5 succeeded in 1 usecs
[2.354055] [drm] UVD initialized successfully.
[2.464561] [drm] ring test on 6 succeeded in 16 usecs
[2.464574] [drm] ring test on 7 succeeded in 3 usecs
[2.464576] [drm] VCE initialized successfully.
[2.465567] [drm] ib test on ring 0 succeeded in 0 usecs
[2.466117] [drm] ib test on ring 3 succeeded in 0 usecs
[2.466648] [drm] ib test on ring 4 succeeded in 0 usecs
[2.487124] [drm] ib test on ring 5 succeeded
[2.531648] kvm: Nested Virtualization enabled
[2.531655] kvm: Nested Paging enabled
[2.557020] random: nonblocking pool is initialized
[2.585810] EXT4-fs (sdb1): mounted filesystem with 

Bug#799122: [Pkg-xen-devel] Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

[Ian Campbell]

On Thu, 2015-11-05 at 19:16 +0100, Arne Klein wrote:
> Thank you. The tested versions on dom0 and domU in which the problem 
> occurs are:
> 4.1.3-1~bpo8+1
> 3.16.7-ckt11-1+deb8u5

I've asked around upstream and it was suggested that "xen-netback:
require fewer guest Rx slots when not using GSO" which is in later
upstream might be relevant.

Please could you try 4.3~rc7-1~exp1 from experimental in dom0 and see
if that helps?

It was also suggested that the contents of /sys/kernel/debug/xen-
netback after the stall has occurred might contain useful information.

I forgot to ask earlier but are you able to trigger this on demand
and/or is there any commonality in the workloads running in the guests
which trigger this (i.e. particular network services which they run) or
their configurations (e..g manually disabling of offloads perhaps).

Ian.

Bug#799122: [Pkg-xen-devel] Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

[Ian Campbell]

On Fri, 2015-11-06 at 11:23 +, Ian Campbell wrote:

> Please could you try 4.3~rc7-1~exp1 from experimental in dom0 and see
> if that helps?

4.3-1~exp1 was just uploaded, so you may as well try that instead.

Thanks,
Ian.

Bug#782641: initramfs-tools: nfs booting requires /usr to be present on the nfs root filesystem

[Salvatore Bonaccorso]

Hi,

On Wed, Apr 15, 2015 at 03:01:44PM +0100, fc3452-00 wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: normal
> 
> Dear Maintainer,
> 
> Problem occurs when attempting to do an nfs network boot with no /usr 
> directory
> present on the nfs root partition.
> 
> At https://www.debian.org/releases/jessie/i386/apcs02.html.en it says that
> /etc, /bin, /sbin, /lib & /dev must be present on the root partition in order
> to boot.
> 
> But in the script /usr/share/initramfs-tools/scripts/nfs there is:
> 
> # loop until nfsmount succeeds
> nfs_mount_root_impl
> nfs_retry_count=0
> while [ ${nfs_retry_count} -lt ${delay} ] \
> && ! chroot "${rootmnt}" test -x "${init}" ; do
> [ "$quiet" != "y" ] && log_begin_msg "Retrying nfs mount"
> /bin/sleep 1
> nfs_mount_root_impl
> nfs_retry_count=$(( ${nfs_retry_count} + 1 ))
> [ "$quiet" != "y" ] && log_end_msg
> done
> 
> which attempts to execute /usr/bin/test immediately after mounting the root
> partition and before mounting any of the filesystems in /etc/fstab. This fails
> if your are trying to mount /usr from another filesystem by using an entry in
> /etc/fstab. The script could be modified to use the shell built-in "test"
> command by changing the line
> 
> && ! chroot "${rootmnt}" test -x "${init}" ; do
> 
> to
> 
> && ! chroot "${rootmnt}" sh -c "[ -x \"${init}\" ]" ; do
> 
> which enables the system to boot when /usr is not present.

Untested: One other option might be to move the validate_init()
wrapper from init to scripts/functions and use that from there as well
in scripts/nfs.

Regards,
Salvatore