Processed: retitle 898060 to Stall NFS clients: RPC request reserved 84 but used 272

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

> retitle 898060 Stall NFS clients: RPC request reserved 84 but used 272
Bug #898060 [src:linux] linux-image-4.9.0-6-amd64: q
Changed Bug title to 'Stall NFS clients: RPC request reserved 84 but used 272' 
from 'linux-image-4.9.0-6-amd64: q'.
> thanks
Stopping processing here.

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

Bug#897572: urandom hang in early boot

2018-05-07 Thread Ben Caradoc-Davies 

On 08/05/18 15:55, Ben Caradoc-Davies wrote:
If something calls getrandom without GRND_NONBLOCK while crng_init==1 
(during early boot)
I now have conclusive evidence that this is the cause of the hang. If I 
add a printk:


diff --git a/drivers/char/random.c b/drivers/char/random.c
index cd888d4ee605..b7358cc32f42 100644
--- a/drivers/char/random.c
+++ b/drivers/char/random.c
@@ -2021,6 +2021,9 @@ SYSCALL_DEFINE3(getrandom, char __user *, buf, 
size_t, count,

if (!crng_ready()) {
if (flags & GRND_NONBLOCK)
return -EAGAIN;
+   printk(KERN_NOTICE "random: %s: getrandom without "
+   "GRND_NONBLOCK while crng not ready\n",
+   current->comm);
ret = wait_for_random_bytes();
if (unlikely(ret))
return ret;

I get these at the console just before the hang:

random: plymouthd: uninitialized urandom read (8 bytes read)
random: plymouthd: uninitialized urandom read (8 bytes read)
random: plymouthd: getrandom without GRND_NONBLOCK while crng not ready

Kind regards,

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

Processed: retitle 897572 to getrandom hang in early boot prevents plymouth passphrase entry

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

> retitle 897572 getrandom hang in early boot prevents plymouth passphrase entry
Bug #897572 [linux] urandom hang in early boot prevents plymouth passphrase 
entry
Bug #897958 [linux] urandom hang in early boot prevents plymouth passphrase 
entry
Bug #898097 [linux] plymouth: linux-image-4.16-1-amd64 with splash: Hangs on 
boot
Changed Bug title to 'getrandom hang in early boot prevents plymouth passphrase 
entry' from 'urandom hang in early boot prevents plymouth passphrase entry'.
Changed Bug title to 'getrandom hang in early boot prevents plymouth passphrase 
entry' from 'urandom hang in early boot prevents plymouth passphrase entry'.
Changed Bug title to 'getrandom hang in early boot prevents plymouth passphrase 
entry' from 'plymouth: linux-image-4.16-1-amd64 with splash: Hangs on boot'.
> thanks
Stopping processing here.

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

Bug#897572: urandom hang in early boot

2018-05-07 Thread Ben Caradoc-Davies 

On 08/05/18 14:00, Ben Hutchings wrote:

You keep saying this, but based on my reading of the code I don't see
how reads from /dev/urandom can end up blocking.


Ben, I think you are right. I have picked through the code in detail and 
none of the changes affect any substantive logic (except logging). I do 
not think urandom_read can ever block. The urandom warning may be from a 
previous read before the hang: related, but a red herring.


The *one* substantive change that is affected is getrandom:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/char/random.c#n2007

If something calls getrandom without GRND_NONBLOCK while crng_init==1 
(during early boot):


- Before 43838a23a05f ("random: fix crng_ready() test"), this just falls 
thorough to urandom_read and everything seems to work (but is not 
cryptographically secure).


- After 43838a23a05f ("random: fix crng_ready() test"), this will call 
wait_for_random_bytes and hang waiting on mouse wiggles 
(cryptographically secure).


But what is calling getrandom without GRND_NONBLOCK? I could find 
nothing in the plymouth or systemd/udev codebase. Or is it something 
they spawn? I even read the plymouth softwaves.script.


Kind regards,

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

Processed: unmerging 897631

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

> unmerge 897631
Bug #897631 [src:linux] Kernel update breaks GDM
Bug #897599 [src:linux] regression in userspace on linux-image-4.9.0-6-amd64
Bug #897632 [src:linux] Boot timeout after latest security update
Bug #897917 [src:linux] Stretch kernel 4.9.88-1 breaks startup of RPC, KDC 
services
Disconnected #897631 from all other report(s).
> thanks
Stopping processing here.

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

Bug#897631: [Fwd: Re: Kernel update breaks GDM]

2018-05-07 Thread Ben Hutchings 
 Forwarded Message 
From: silvio.s...@gmail.com
To: Ben Hutchings 
Subject: Re: Kernel update breaks GDM
Date: Tue, 08 May 2018 01:07:55 +0200
Message-Id: <1525734475.1800.1.camel@localhost>

> Control: tag -1 moreinfo
> 
> On Thu, 03 May 2018 18:59:36 +0200 silvio.s...@gmail.com wrote:
> [...]
> > However soon after logging in (usually by the time I had written a
> > couple of commands) GDM would start and I could then log in from
> > the
> > GUI and from then on everything would work just fine. GDM would
> > however
> > not start if I didn't log in from the command line, instead the
> > system
> > would just hang indefinetly (I actually left it on for about 30 min
> > while going on lunch).
> 
> [...]
> 
> This may sound like a silly request, but does GDM start up if you
> wiggle the mouse for a few seconds?
> 
> Ben.
> 


No it doesn't. It starts only if I log in and only if I start typing
some command in the terminal after I've logged in.

If I wiggle the mouse for a while it just continues to hang. If I just
log in and don't type any command it doesn't start either. It's really
weird!

Here's what I've tried so far:

- I've added the "Debian-gdm" user to "video" group as well, thought it
might help, but it didn't.

- I updated the NVIDIA driver to both 384.130 and the newest 396-
version but neither of those helped.

- If I edit the "/etc/gdm3/daemon.conf"-file and comment out the
"#WaylandEnable=false"-line the NVIDIA driver does load (I can hear the
fans of my graphics card go silent) but then I get a completely blank
screen.


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

linux-latest_93~bpo9+1_all.changes ACCEPTED into stretch-backports

2018-05-07 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 08 May 2018 02:40:03 +0100
Source: linux-latest
Binary: linux-source linux-doc linux-perf linux-image-alpha-generic 
linux-headers-alpha-generic linux-image-alpha-generic-dbg linux-image-alpha-smp 
linux-headers-alpha-smp linux-image-alpha-smp-dbg linux-image-amd64 
linux-headers-amd64 linux-image-amd64-dbg linux-image-cloud-amd64 
linux-headers-cloud-amd64 linux-image-cloud-amd64-dbg linux-image-arm64 
linux-headers-arm64 linux-image-arm64-dbg linux-image-marvell 
linux-headers-marvell linux-image-marvell-dbg linux-image-armmp 
linux-headers-armmp linux-image-armmp-dbg linux-image-armmp-lpae 
linux-headers-armmp-lpae linux-image-armmp-lpae-dbg linux-image-parisc 
linux-headers-parisc linux-image-parisc-dbg linux-image-parisc-smp 
linux-headers-parisc-smp linux-image-parisc-smp-dbg linux-image-parisc64-smp 
linux-headers-parisc64-smp linux-image-parisc64-smp-dbg linux-image-686 
linux-headers-686 linux-image-686-dbg linux-image-686-pae linux-headers-686-pae 
linux-image-686-pae-dbg linux-image-itanium linux-headers-itanium
 linux-image-itanium-dbg linux-image-mckinley linux-headers-mckinley 
linux-image-mckinley-dbg linux-image-m68k linux-headers-m68k 
linux-image-m68k-dbg linux-image-4kc-malta linux-headers-4kc-malta 
linux-image-4kc-malta-dbg linux-image-5kc-malta linux-headers-5kc-malta 
linux-image-5kc-malta-dbg linux-image-octeon linux-headers-octeon 
linux-image-octeon-dbg linux-image-loongson-3 linux-headers-loongson-3 
linux-image-loongson-3-dbg linux-image-mips64r6 linux-headers-mips64r6 
linux-image-mips64r6-dbg linux-image-mips64r6el linux-headers-mips64r6el 
linux-image-mips64r6el-dbg linux-image-mips32r6 linux-headers-mips32r6 
linux-image-mips32r6-dbg linux-image-mips32r6el linux-headers-mips32r6el 
linux-image-mips32r6el-dbg linux-image-powerpc linux-headers-powerpc 
linux-image-powerpc-dbg linux-image-powerpc-smp linux-headers-powerpc-smp 
linux-image-powerpc-smp-dbg linux-image-powerpc64 linux-headers-powerpc64 
linux-image-powerpc64-dbg linux-image-powerpcspe
 linux-headers-powerpcspe linux-image-powerpcspe-dbg linux-image-powerpc64le 
linux-headers-powerpc64le linux-image-powerpc64le-dbg linux-image-s390x 
linux-headers-s390x linux-image-s390x-dbg linux-image-sh7751r 
linux-headers-sh7751r linux-image-sh7751r-dbg linux-image-sh7785lcr 
linux-headers-sh7785lcr linux-image-sh7785lcr-dbg linux-image-sparc64 
linux-headers-sparc64 linux-image-sparc64-dbg linux-image-sparc64-smp 
linux-headers-sparc64-smp
 linux-image-sparc64-smp-dbg
Architecture: source all
Version: 93~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Description:
 linux-doc  - Linux kernel specific documentation (meta-package)
 linux-headers-4kc-malta - Header files for Linux 4kc-malta configuration 
(meta-package)
 linux-headers-5kc-malta - Header files for Linux 5kc-malta configuration 
(meta-package)
 linux-headers-686 - Header files for Linux 686 configuration (meta-package)
 linux-headers-686-pae - Header files for Linux 686-pae configuration 
(meta-package)
 linux-headers-alpha-generic - Header files for Linux alpha-generic 
configuration (meta-package)
 linux-headers-alpha-smp - Header files for Linux alpha-smp configuration 
(meta-package)
 linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package)
 linux-headers-arm64 - Header files for Linux arm64 configuration (meta-package)
 linux-headers-armmp - Header files for Linux armmp configuration (meta-package)
 linux-headers-armmp-lpae - Header files for Linux armmp-lpae configuration 
(meta-package)
 linux-headers-cloud-amd64 - Header files for Linux cloud-amd64 configuration 
(meta-package)
 linux-headers-itanium - Header files for Linux itanium configuration 
(meta-package)
 linux-headers-loongson-3 - Header files for Linux loongson-3 configuration 
(meta-package)
 linux-headers-m68k - Header files for Linux m68k configuration (meta-package)
 linux-headers-marvell - Header files for Linux marvell configuration 
(meta-package)
 linux-headers-mckinley - Header files for Linux mckinley configuration 
(meta-package)
 linux-headers-mips32r6 - Header files for Linux mips32r6 configuration 
(meta-package)
 linux-headers-mips32r6el - Header files for Linux mips32r6el configuration 
(meta-package)
 linux-headers-mips64r6 - Header files for Linux mips64r6 configuration 
(meta-package)
 linux-headers-mips64r6el - Header files for Linux mips64r6el configuration 
(meta-package)
 linux-headers-octeon - Header files for Linux octeon configuration 
(meta-package)
 linux-headers-parisc - Header files for Linux parisc configuration 
(meta-package)
 linux-headers-parisc-smp - Header files for Linux parisc-smp configuration 
(meta-package)
 linux-headers-parisc64-smp - Header files for Linux parisc64-smp configuration 
(meta-package)
 linux-headers-powerpc - Header files for Linux powerpc configuration 
(meta-package)

Processing of linux-latest_93~bpo9+1_all.changes

2018-05-07 Thread Debian FTP Masters 
linux-latest_93~bpo9+1_all.changes uploaded successfully to localhost
along with the files:
  linux-latest_93~bpo9+1.dsc
  linux-latest_93~bpo9+1.tar.xz
  linux-doc_4.16+93~bpo9+1_all.deb
  linux-latest_93~bpo9+1_all.buildinfo
  linux-perf_4.16+93~bpo9+1_all.deb
  linux-source_4.16+93~bpo9+1_all.deb

Greetings,

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

Bug#897572: urandom hang in early boot

2018-05-07 Thread Ben Hutchings 
On Tue, 2018-05-08 at 11:12 +1200, Ben Caradoc-Davies wrote:
> On 08/05/18 05:34, Laurent Bigonville wrote:
> > Apparently it's also happening for other applications that are starting 
> > later during the boot like GDM.
> > Somebody has reported an issue on IRC where GDM was taking upto 8 
> > minutes to start (dmesg was showing several "random: systemd: 
> > uninitialized urandom read (16 bytes read)" during boot)
> > That problem might impact lot of people I'm afraid.
> 
> systemd is the underlying cause: plymouthd uses libudev1, which expects 
> getrandom/urandom(?) to never block:
> https://github.com/systemd/systemd/blob/master/src/basic/random-util.c#L34
> 
> See discussion here about systemd usage of random numbers:
> systemd reads from urandom before initialization
> https://github.com/systemd/systemd/issues/4167
> 
> The new problem is that 43838a23a05f ("random: fix crng_ready() test") 
> turns an ugly warning and cryptographic weakness into an indefinite 
> hang. Security achieved!

You keep saying this, but based on my reading of the code I don't see
how reads from /dev/urandom can end up blocking.

(For the time being I've concentrated on fixing stretch, so I haven't
done substantial testing in unstable.)

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained
by stupidity.



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

Bug#897572: urandom hang in early boot

2018-05-07 Thread Ben Caradoc-Davies 

On 08/05/18 05:34, Laurent Bigonville wrote:
Apparently it's also happening for other applications that are starting 
later during the boot like GDM.
Somebody has reported an issue on IRC where GDM was taking upto 8 
minutes to start (dmesg was showing several "random: systemd: 
uninitialized urandom read (16 bytes read)" during boot)

That problem might impact lot of people I'm afraid.


systemd is the underlying cause: plymouthd uses libudev1, which expects 
getrandom/urandom(?) to never block:

https://github.com/systemd/systemd/blob/master/src/basic/random-util.c#L34

See discussion here about systemd usage of random numbers:
systemd reads from urandom before initialization
https://github.com/systemd/systemd/issues/4167

The new problem is that 43838a23a05f ("random: fix crng_ready() test") 
turns an ugly warning and cryptographic weakness into an indefinite 
hang. Security achieved!


Kind regards,

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

Processed: limit source to linux, tagging 897599

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

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 897599 + pending
Bug #897599 [src:linux] regression in userspace on linux-image-4.9.0-6-amd64
Bug #897631 [src:linux] Kernel update breaks GDM
Bug #897632 [src:linux] Boot timeout after latest security update
Bug #897917 [src:linux] Stretch kernel 4.9.88-1 breaks startup of RPC, KDC 
services
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: limit source to linux, tagging 897427, tagging 898100, tagging 898067

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

> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'

> tags 897427 + pending
Bug #897427 [src:linux] linux-image-3.16.0-6-amd64 breaks KVM guests in libvirt
Bug #897588 [src:linux] Automatic assignment of TUN device broken after 
(security) kernel upgrade
Bug #897685 [src:linux] linux-image-3.16.0-6-amd64: Unable to start multiple 
KVM instances with libvirt
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> tags 898100 + pending
Bug #898100 [src:linux] linux-image-3.16.0-6-amd64: SCTP IPv4/v6 mixed mode 
socket doesn't return peer adresses anymore (with sctp_getpaddrs())
Added tag(s) pending.
> tags 898067 + pending
Bug #898067 [src:linux] Division by zero in microcode loader when booting on 
EC2 c3.large/r3.large
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897427
897588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897588
897685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897685
898067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898067
898100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898100
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#898100: linux-image-3.16.0-6-amd64: SCTP IPv4/v6 mixed mode socket doesn't return peer adresses anymore (with sctp_getpaddrs())

2018-05-07 Thread Debian Bug Tracking System 
Processing control commands:

> found -1 3.2.101-1
Bug #898100 [src:linux] linux-image-3.16.0-6-amd64: SCTP IPv4/v6 mixed mode 
socket doesn't return peer adresses anymore (with sctp_getpaddrs())
The source 'linux' and version '3.2.101-1' do not appear to match any binary 
packages
Marked as found in versions linux/3.2.101-1.
> tag -1 upstream fixed-upstream patch
Bug #898100 [src:linux] linux-image-3.16.0-6-amd64: SCTP IPv4/v6 mixed mode 
socket doesn't return peer adresses anymore (with sctp_getpaddrs())
Added tag(s) fixed-upstream, patch, and upstream.

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

Bug#898100: linux-image-3.16.0-6-amd64: SCTP IPv4/v6 mixed mode socket doesn't return peer adresses anymore (with sctp_getpaddrs())

2018-05-07 Thread Ben Hutchings 
Control: found -1 3.2.101-1
Control: tag -1 upstream fixed-upstream patch

On Mon, 2018-05-07 at 09:49 +0200, Fred Boiteux wrote:
> Package: src:linux
> Version: 3.16.56-1
> Severity: normal
> 
> Dear Maintainer,
> 
> With latest Debian Jessie Linux kernel (3.16.56-1) version,
> my SCTP application, which uses an IPv6 socket to get IPv4 or IPv6 messages,
> can retrieve anymore IPv4 addresses from peers, using sctp_getpaddrs() 
> function.
> 
> I've identified the impacting patch :r
> sctp: Fixup v4mapped behaviour to comply with Sock API
> 
> I've rebuilt a kernel with this patch reverted, and my application works
> well with
> 
> I retrieve IPv4 peer addresses in a IPv6-mapped format, like :
> 0x00: 0A 00 A5 B8 C0 A8 FE B2 00 00 00 00  
> 0x0C: 00 00 00 00 00 00 FF FF C0 A8 FE B2  
> 0x18: 30 3B C0 1F  0;..
> which means : :::192.168.254.178%532691760 -> 192.168.254.178

Note that the flowinfo and scope_id were garbage here.

> But with the latest Jessie kernel, i get :
> 0x00: 0A 00 A5 B8 00 00 00 00 00 00 00 00  
> 0x0C: 00 00 00 00 00 00 FF FF 00 00 00 00  
> 0x18: 00 00 00 00  
> which translates to : :::0.0.0.0
> 
> 
> I've stated the same bug with latest Debian Wheezy kernel
> (linux-image-3.2.0-6-amd64 package, 3.2.101-1 version) :
> I don't know if i should add a separate bug report ?
[...]

No need; the bug tracking system can handle multiple versions.

It looks like this was fixed upstream by:

commit 9302d7bb0c5cd46be5706859301f18c137b2439f
Author: Jason Gunthorpe 
Date:   Tue May 26 17:30:17 2015 -0600

sctp: Fix mangled IPv4 addresses on a IPv6 listening socket

and I should apply that fix as well.

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
  - John Lennon



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

Processed: tagging 897599

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

> tags 897599 - moreinfo
Bug #897599 [src:linux] regression in userspace on linux-image-4.9.0-6-amd64
Bug #897631 [src:linux] Kernel update breaks GDM
Bug #897632 [src:linux] Boot timeout after latest security update
Bug #897917 [src:linux] Stretch kernel 4.9.88-1 breaks startup of RPC, KDC 
services
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#898137: nfsd: increase DRC cache limit

2018-05-07 Thread Sergio Gelato 
Source: linux
Version: 4.9.88-1
Severity: wishlist
Tags: patch

I've run into this capacity limitation in stretch, which is addressed
upstream in Linux 4.15 by the following commit:

commit 44d8660d3bb0a1c8363ebcb906af2343ea8e15f6
Author: J. Bruce Fields 
Date:   Tue Sep 19 20:51:31 2017 -0400

nfsd: increase DRC cache limit

which trivially applies to Linux 4.9 (I haven't checked 3.16) and provides
significant relief in my use case. It would save me (and perhaps others)
work if this change could be included in Debian's 4.9 kernel packages;
otherwise I'll have to keep maintaining my own fork. (4.15 has other
issues so I don't want to use it in production yet.)

For the benefit of others who may be running into the same problem, here
is a more detailed description.

Symptom: an NFS server accepts only a limited number of concurrent v4.1+
mounts. Once that limit is reached, new clients get NFS4ERR_DELAY (10008)
replies to CREATE_SESSION. (This can be seen in the server's dmesg after
rpcdebug -m nfsd -s proc.) Increasing the number of nfsd threads has no
impact on the number of mounts allowed. A server with 512MB of RAM
only accepts 7 or 8 concurrent NFSv4.1+ mounts. From the perspective of
an affected client, mount.nfs appears to hang (triggering a kernel backtrace
after 120 seconds); in reality, though, it just keeps reissuing CREATE_SESSION
calls until one of them succeeds.

Pre-v4.1 clients are unaffected by this since sessions are new to NFS v4.1.

The proposed patch just increases the limit by an order of magnitude, at
the cost of using more kernel memory. As noted in comments in the source
code, it would be nice to make this tuneable by the server administrator.

Bug#898128: marked as done (linux-image-4.16.0-1-amd64: rma ryzen 5 1600x, swap with 2200g, only useable firmware for Taichi X370 is p4.40, then one of 4 gpus not listed in lspci)

2018-05-07 Thread Debian Bug Tracking System 
Your message dated Mon, 07 May 2018 20:05:50 +0100
with message-id <1c88926a100feb7f218c3ff096a9d81219f47c6c.ca...@decadent.org.uk>
and subject line Re: Bug#898128: linux-image-4.16.0-1-amd64: rma ryzen 5 1600x, 
swap with 2200g, only useable firmware for Taichi X370 is p4.40, then one of 4 
gpus not listed in lspci
has caused the Debian Bug report #898128,
regarding linux-image-4.16.0-1-amd64: rma ryzen 5 1600x, swap with 2200g, only 
useable firmware for Taichi X370 is p4.40, then one of 4 gpus not listed in 
lspci
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.)


-- 
898128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.16.5-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Can't use the 4th GPU, probably getting the replacement ryzen 5 1600x will 
solve the problem, the integrated gpu might be the culprit
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.16.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-17)) #1 SMP Debian 4.16.5-1 (2018-04-29)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-1-amd64 root=/dev/mapper/re--vg-root ro 
cryptopts=target=sda5_crypt,source=/dev/disk/by-uuid/cacf3162-302c-4ef1-913c-bba1626e5d85,lvm=re--vg-root,keyscript=/lib/cryptsetup/scripts/unlock.sh

** Tainted: PWO (4609)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
[   30.140350] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:04.0/:2c:00.1/sound/card2/input17
[   30.140591] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.1/:10:00.1/sound/card0/input12
[   30.140855] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.1/:10:00.1/sound/card0/input13
[   30.141102] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:03.0/:21:00.0/:26:03.0/:28:00.1/sound/card1/input20
[   30.141366] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:03.0/:21:00.0/:26:03.0/:28:00.1/sound/card1/input21
[   30.141623] input: HD-Audio Generic HDMI/DP,pcm=7 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input6
[   30.141856] input: HD-Audio Generic HDMI/DP,pcm=8 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input7
[   30.142094] input: HD-Audio Generic HDMI/DP,pcm=9 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input8
[   30.142335] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:04.0/:2c:00.1/sound/card2/input18
[   30.142621] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.1/:10:00.1/sound/card0/input14
[   30.142891] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:03.0/:21:00.0/:26:03.0/:28:00.1/sound/card1/input22
[   30.143225] input: HD-Audio Generic HDMI/DP,pcm=10 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input9
[   30.143477] input: HD-Audio Generic HDMI/DP,pcm=11 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input10
[   30.340726] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: 
(null)
[   30.700069] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
[   30.982897] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: 
(null)
[   30.997976] systemd-journald[384]: Received request to flush runtime journal 
from PID 1
[   31.016769] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[   32.707343] audit: type=1400 audit(1525714817.405:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=633 comm="apparmor_parser"
[   32.751452] audit: type=1400 audit(1525714817.449:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=631 
comm="apparmor_parser"
[   32.751655] audit: type=1400 audit(1525714817.449:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=631 
comm="apparmor_parser"
[   32.751857] audit: type=1400 audit(1525714817.449:5): apparmor="

Bug#898128: linux-image-4.16.0-1-amd64: rma ryzen 5 1600x, swap with 2200g, only useable firmware for Taichi X370 is p4.40, then one of 4 gpus not listed in lspci

2018-05-07 Thread Brahim Sbaiti 
Package: src:linux
Version: 4.16.5-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Can't use the 4th GPU, probably getting the replacement ryzen 5 1600x will 
solve the problem, the integrated gpu might be the culprit
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.16.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-17)) #1 SMP Debian 4.16.5-1 (2018-04-29)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-1-amd64 root=/dev/mapper/re--vg-root ro 
cryptopts=target=sda5_crypt,source=/dev/disk/by-uuid/cacf3162-302c-4ef1-913c-bba1626e5d85,lvm=re--vg-root,keyscript=/lib/cryptsetup/scripts/unlock.sh

** Tainted: PWO (4609)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
[   30.140350] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:04.0/:2c:00.1/sound/card2/input17
[   30.140591] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.1/:10:00.1/sound/card0/input12
[   30.140855] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.1/:10:00.1/sound/card0/input13
[   30.141102] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:03.0/:21:00.0/:26:03.0/:28:00.1/sound/card1/input20
[   30.141366] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:03.0/:21:00.0/:26:03.0/:28:00.1/sound/card1/input21
[   30.141623] input: HD-Audio Generic HDMI/DP,pcm=7 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input6
[   30.141856] input: HD-Audio Generic HDMI/DP,pcm=8 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input7
[   30.142094] input: HD-Audio Generic HDMI/DP,pcm=9 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input8
[   30.142335] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:04.0/:2c:00.1/sound/card2/input18
[   30.142621] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.1/:10:00.1/sound/card0/input14
[   30.142891] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:01.2/:15:00.2/:1d:03.0/:21:00.0/:26:03.0/:28:00.1/sound/card1/input22
[   30.143225] input: HD-Audio Generic HDMI/DP,pcm=10 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input9
[   30.143477] input: HD-Audio Generic HDMI/DP,pcm=11 as 
/devices/pci:00/:00:08.1/:38:00.1/sound/card3/input10
[   30.340726] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: 
(null)
[   30.700069] EXT4-fs (sda1): mounting ext2 file system using the ext4 
subsystem
[   30.982897] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: 
(null)
[   30.997976] systemd-journald[384]: Received request to flush runtime journal 
from PID 1
[   31.016769] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[   32.707343] audit: type=1400 audit(1525714817.405:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-senddoc" 
pid=633 comm="apparmor_parser"
[   32.751452] audit: type=1400 audit(1525714817.449:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=631 
comm="apparmor_parser"
[   32.751655] audit: type=1400 audit(1525714817.449:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=631 
comm="apparmor_parser"
[   32.751857] audit: type=1400 audit(1525714817.449:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=631 
comm="apparmor_parser"
[   32.761520] audit: type=1400 audit(1525714817.461:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=636 comm="apparmor_parser"
[   32.834978] audit: type=1400 audit(1525714817.533:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=632 comm="apparmor_parser"
[   32.873432] audit: type=1400 audit(1525714817.573:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-soffice" 
pid=634 comm="apparmor_parser"
[   32.873641] audit: type=1400 audit(1525714817.573:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-soffice//gpg" 
pid=634 comm="apparmor_parser"
[   32.891222] audit: type=1400 audit(1525714817.589:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=638 
comm="apparmor_parser"
[   34.227011] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more tha

Bug#898074: Confirming gdm bug with kernel 4.9.0-6

2018-05-07 Thread Magnus Wallin 
Confirming this bug on two different laptops (Dell and Lenovo) ; both running 
Debian 9 with kernel 4.9.0-6.

Booting from the previous kernel (4.9.0-6) works as expected (i.e. gdm starts 
in under five minutes!).

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

Bug#897572: urandom hang in early boot

2018-05-07 Thread Laurent Bigonville 

Hello,

Apparently it's also happening for other applications that are starting 
later during the boot like GDM.


Somebody has reported an issue on IRC where GDM was taking upto 8 
minutes to start (dmesg was showing several "random: systemd: 
uninitialized urandom read (16 bytes read)" during boot)


That problem might impact lot of people I'm afraid.

Installing rng-tools5 seems to help in that case.

Processed: forcibly merging 897599 897631

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

> forcemerge 897599 897631
Bug #897599 [src:linux] regression in userspace on linux-image-4.9.0-6-amd64
Bug #897632 [src:linux] Boot timeout after latest security update
Bug #897917 [src:linux] Stretch kernel 4.9.88-1 breaks startup of RPC, KDC 
services
Bug #897599 [src:linux] regression in userspace on linux-image-4.9.0-6-amd64
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Added tag(s) moreinfo.
Bug #897631 [src:linux] Kernel update breaks GDM
Severity set to 'important' from 'normal'
Bug #897632 [src:linux] Boot timeout after latest security update
Bug #897917 [src:linux] Stretch kernel 4.9.88-1 breaks startup of RPC, KDC 
services
Merged 897599 897631 897632 897917
> thanks
Stopping processing here.

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

Re: Debian kernel packaging no longer accepts typical downstream version numbering.

2018-05-07 Thread Ian Campbell 
On Mon, 2018-05-07 at 13:36 +0100, peter green wrote:
> Common practice for downstreams (whether complete derivatives or end
> users) is to version modified packages with a version number like
> 
> 4.16.5-1+something1
> 
> Where "something" is the name of a project, the name of the person
> performing the modification etc.
> 
> Unfortunately with 4.16.5-1 of the kernel package such a version
> number is no longer accepted with the error message "Invalid debian
> linux version". It seems the cause of this was the following change.
> 
>   (?P
> -[^-]+
> +[^-+]+
>   )
> 
> Reverting this change allowed me to get a succesful control files
> generation.

This was also reported in #898087

Re: [PATCH v2] kbuild: deb-pkg improve maintainer address generation

2018-05-07 Thread Masahiro Yamada 
Hi Riku,

2018-05-07 16:11 GMT+09:00  :
> From: Riku Voipio 
>
> There is multiple issues with the genaration of maintainer string
>
> It uses DEBEMAIL and EMAIL enviroment variables, which may contain angle 
> brackets,
> creating invalid maintainer strings. The documented KBUILD_BUILD_USER and
> KBUILD_BUILD_HOST variables are not used. Undocumented and uncommon NAME
> variable is used.

Sorry, I missed to ask you about 'NAME' variable.


I checked the Debian Administrator's Handbook.

I see the following description


  TIP
  Maintainer’s name and email address

  Most of the programs involved in package maintenance will look for
your name and
  email address in the DEBFULLNAME and DEBEMAIL or EMAIL environment variables.
  Defining them once and for all will avoid you having to type them
multiple times.
  If your usual shell is bash , it is a simple matter of adding the
following two lines
  in your ~/.bashrc file (you will obviously replace the values with
more relevant
  ones!):

  export EMAIL=”hert...@debian.org”
  export DEBFULLNAME=”Raphael Hertzog”


Indeed, 'NAME' is not mentioned at all here.



On the other hand, I also checked the following link
referred by Mathieu:
https://manpages.debian.org/unstable/devscripts/dch.1.en.html

  If the environment variable DEBFULLNAME is set, this will be used for the
  maintainer full name; if not, then NAME will be checked. If the environment
  variable DEBEMAIL is set, this will be used for the email address. If this
  variable has the form "name ", then the maintainer name will also be
  taken from here if neither DEBFULLNAME nor NAME is set.


Hmm, debchange checks 'NAME' too.



I think you are more familiar with Debian.

I just took a pause to ask
which to follow.






> Refactor the Maintainer string to:
>
> - use EMAIL or DEBEMAIL directly if they are in form "name "
> - use KBUILD_BUILD_USER and KBUILD_BUILD_HOST if set before falling
>   back to autodetection
> - no longer use NAME variable or the useless Anonymous string
>
> The logic is switched from multiline if/then/fi statements to compact
> shell variable substition commands.
>
> Reported-by: Mathieu Malaterre 
> Signed-off-by: Riku Voipio 
> ---
> v2: include improvements suggested by Masahiro-san
>
>  scripts/package/mkdebian | 27 +--
>  1 file changed, 13 insertions(+), 14 deletions(-)
>
> diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
> index 6adb3a16ba3b..985d72d1ab34 100755
> --- a/scripts/package/mkdebian
> +++ b/scripts/package/mkdebian
> @@ -71,22 +71,21 @@ if [ "$ARCH" = "um" ] ; then
> packagename=user-mode-linux-$version
>  fi
>
> -# Try to determine maintainer and email values
> -if [ -n "$DEBEMAIL" ]; then
> -   email=$DEBEMAIL
> -elif [ -n "$EMAIL" ]; then
> -   email=$EMAIL
> -else
> -   email=$(id -nu)@$(hostname -f 2>/dev/null || hostname)
> -fi
> -if [ -n "$DEBFULLNAME" ]; then
> -   name=$DEBFULLNAME
> -elif [ -n "$NAME" ]; then
> -   name=$NAME
> +email=${DEBEMAIL-$EMAIL}
> +
> +# use email string directly if it contains 
> +if echo $email | grep -q '<.*>'; then
> +   maintainer=$email
>  else
> -   name="Anonymous"
> +   # or construct the maintainer string
> +   user=${KBUILD_BUILD_USER-$(id -nu)}
> +   name=${DEBFULLNAME-$user}
> +   if [ -z "$email" ]; then
> +   buildhost=${KBUILD_BUILD_HOST-$(hostname -f 2>/dev/null || 
> hostname)}
> +   email="$user@$buildhost"
> +   fi
> +   maintainer="$name <$email>"
>  fi
> -maintainer="$name <$email>"
>
>  # Try to determine distribution
>  if [ -n "$KDEB_CHANGELOG_DIST" ]; then
> --
> 2.14.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Best Regards
Masahiro Yamada

Bug#897427: More testing

2018-05-07 Thread IB Development Team 
Hi,

Same error in Debian 8 amd64 if trying to start one guest with two
virtio nics. Guest will start ok if one nic is removed. 

No such problems after booting with previous 3.16.0-5-amd64 kernel.

Regards,
Pawel

Debian kernel packaging no longer accepts typical downstream version numbering.

2018-05-07 Thread peter green 

Common practice for downstreams (whether complete derivatives or end users) is 
to version modified packages with a version number like

4.16.5-1+something1

Where "something" is the name of a project, the name of the person performing 
the modification etc.

Unfortunately with 4.16.5-1 of the kernel package such a version number is no longer 
accepted with the error message "Invalid debian linux version". It seems the 
cause of this was the following change.

 (?P
-[^-]+
+[^-+]+
 )

Reverting this change allowed me to get a succesful control files generation.

Bug#898074: Maybe some more information on this bug

2018-05-07 Thread Matthieu Dubuget 
I experience the same problem (and got around it by reverting to 
linux-image-4.9.0-5-amd64).

In my case, the problem does not prevent gdm3 to start: it just take a vry 
looong time (around 5 min).

I reproduced it on a freshly installed (with Debian 9.4) computer.

-- 
Matthieu Dubuget

linux_4.9.88-1_source.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

2018-05-07 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Apr 2018 09:19:40 +0200
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-6 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-6-common 
linux-headers-4.9.0-6-common-rt linux-libc-dev linux-headers-4.9.0-6-all 
linux-headers-4.9.0-6-all-alpha kernel-image-4.9.0-6-alpha-generic-di 
nic-modules-4.9.0-6-alpha-generic-di 
nic-wireless-modules-4.9.0-6-alpha-generic-di 
nic-shared-modules-4.9.0-6-alpha-generic-di 
serial-modules-4.9.0-6-alpha-generic-di 
usb-serial-modules-4.9.0-6-alpha-generic-di 
ppp-modules-4.9.0-6-alpha-generic-di pata-modules-4.9.0-6-alpha-generic-di 
cdrom-core-modules-4.9.0-6-alpha-generic-di 
scsi-core-modules-4.9.0-6-alpha-generic-di 
scsi-modules-4.9.0-6-alpha-generic-di loop-modules-4.9.0-6-alpha-generic-di 
btrfs-modules-4.9.0-6-alpha-generic-di ext4-modules-4.9.0-6-alpha-generic-di 
isofs-modules-4.9.0-6-alpha-generic-di jfs-modules-4.9.0-6-alpha-generic-di
 xfs-modules-4.9.0-6-alpha-generic-di fat-modules-4.9.0-6-alpha-generic-di 
md-modules-4.9.0-6-alpha-generic-di multipath-modules-4.9.0-6-alpha-generic-di 
usb-modules-4.9.0-6-alpha-generic-di 
usb-storage-modules-4.9.0-6-alpha-generic-di 
fb-modules-4.9.0-6-alpha-generic-di input-modules-4.9.0-6-alpha-generic-di 
event-modules-4.9.0-6-alpha-generic-di mouse-modules-4.9.0-6-alpha-generic-di 
nic-pcmcia-modules-4.9.0-6-alpha-generic-di 
pcmcia-modules-4.9.0-6-alpha-generic-di 
nic-usb-modules-4.9.0-6-alpha-generic-di sata-modules-4.9.0-6-alpha-generic-di 
crc-modules-4.9.0-6-alpha-generic-di crypto-modules-4.9.0-6-alpha-generic-di 
crypto-dm-modules-4.9.0-6-alpha-generic-di ata-modules-4.9.0-6-alpha-generic-di 
nbd-modules-4.9.0-6-alpha-generic-di squashfs-modules-4.9.0-6-alpha-generic-di 
virtio-modules-4.9.0-6-alpha-generic-di zlib-modules-4.9.0-6-alpha-generic-di 
fuse-modules-4.9.0-6-alpha-generic-di srm-modules-4.9.0-6-alpha-generic-di 
linux-image-4.9.0-6-alpha-generic
 linux-headers-4.9.0-6-alpha-generic linux-image-4.9.0-6-alpha-generic-dbg 
linux-image-4.9.0-6-alpha-smp linux-headers-4.9.0-6-alpha-smp 
linux-image-4.9.0-6-alpha-smp-dbg linux-headers-4.9.0-6-all-amd64 
kernel-image-4.9.0-6-amd64-di nic-modules-4.9.0-6-amd64-di 
nic-wireless-modules-4.9.0-6-amd64-di nic-shared-modules-4.9.0-6-amd64-di 
serial-modules-4.9.0-6-amd64-di usb-serial-modules-4.9.0-6-amd64-di 
ppp-modules-4.9.0-6-amd64-di pata-modules-4.9.0-6-amd64-di 
cdrom-core-modules-4.9.0-6-amd64-di firewire-core-modules-4.9.0-6-amd64-di 
scsi-core-modules-4.9.0-6-amd64-di scsi-modules-4.9.0-6-amd64-di 
loop-modules-4.9.0-6-amd64-di btrfs-modules-4.9.0-6-amd64-di 
ext4-modules-4.9.0-6-amd64-di isofs-modules-4.9.0-6-amd64-di 
jfs-modules-4.9.0-6-amd64-di ntfs-modules-4.9.0-6-amd64-di 
xfs-modules-4.9.0-6-amd64-di fat-modules-4.9.0-6-amd64-di 
md-modules-4.9.0-6-amd64-di multipath-modules-4.9.0-6-amd64-di 
usb-modules-4.9.0-6-amd64-di usb-storage-modules-4.9.0-6-amd64-di
 pcmcia-storage-modules-4.9.0-6-amd64-di fb-modules-4.9.0-6-amd64-di 
input-modules-4.9.0-6-amd64-di event-modules-4.9.0-6-amd64-di 
mouse-modules-4.9.0-6-amd64-di nic-pcmcia-modules-4.9.0-6-amd64-di 
pcmcia-modules-4.9.0-6-amd64-di nic-usb-modules-4.9.0-6-amd64-di 
sata-modules-4.9.0-6-amd64-di acpi-modules-4.9.0-6-amd64-di 
i2c-modules-4.9.0-6-amd64-di crc-modules-4.9.0-6-amd64-di 
crypto-modules-4.9.0-6-amd64-di crypto-dm-modules-4.9.0-6-amd64-di 
efi-modules-4.9.0-6-amd64-di ata-modules-4.9.0-6-amd64-di 
mmc-core-modules-4.9.0-6-amd64-di mmc-modules-4.9.0-6-amd64-di 
nbd-modules-4.9.0-6-amd64-di squashfs-modules-4.9.0-6-amd64-di 
speakup-modules-4.9.0-6-amd64-di virtio-modules-4.9.0-6-amd64-di 
uinput-modules-4.9.0-6-amd64-di sound-modules-4.9.0-6-amd64-di 
hyperv-modules-4.9.0-6-amd64-di udf-modules-4.9.0-6-amd64-di 
fuse-modules-4.9.0-6-amd64-di linux-image-4.9.0-6-amd64 
linux-headers-4.9.0-6-amd64 linux-image-4.9.0-6-amd64-dbg 
linux-image-4.9.0-6-rt-amd64
 linux-headers-4.9.0-6-rt-amd64 linux-image-4.9.0-6-rt-amd64-dbg 
linux-headers-4.9.0-6-all-arm64 kernel-image-4.9.0-6-arm64-di 
nic-modules-4.9.0-6-arm64-di nic-wireless-modules-4.9.0-6-arm64-di 
nic-shared-modules-4.9.0-6-arm64-di ppp-modules-4.9.0-6-arm64-di 
cdrom-core-modules-4.9.0-6-arm64-di scsi-core-modules-4.9.0-6-arm64-di 
scsi-modules-4.9.0-6-arm64-di loop-modules-4.9.0-6-arm64-di 
btrfs-modules-4.9.0-6-arm64-di ext4-modules-4.9.0-6-arm64-di 
isofs-modules-4.9.0-6-arm64-di jfs-modules-4.9.0-6-arm64-di 
xfs-modules-4.9.0-6-arm64-di fat-modules-4.9.0-6-arm64-di 
md-modules-4.9.0-6-arm64-di multipath-modules-4.9.0-6-arm64-di 
usb-modules-4.9.0-6-arm64-di usb-storage-modules-4.9.0-6-arm64-di 
fb-modules-4.9.0-6-arm64-di input-modules-4.9.0-6-arm64-di 
event-modules-4.9.0-6-arm64-di nic-usb-modules-4.9.0-6-arm64-di 
sata-modules-4.9.0-6-arm64-di i2c-modules-4.9.0-6-arm64-di 
crc-modules-4.9.0-6-arm64-di crypto-modules-4.9.0

Bug#898098: It may be related to bug 897572

2018-05-07 Thread julien 
Hi,
It may be related to bug 897572
Julien.

Processed: reassign 898097 to linux, merging 898097 897958, affects 897958

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

> reassign 898097 linux
Bug #898097 [plymouth] plymouth: linux-image-4.16-1-amd64 with splash: Hangs on 
boot
Bug reassigned from package 'plymouth' to 'linux'.
No longer marked as found in versions plymouth/0.9.3-2.
Ignoring request to alter fixed versions of bug #898097 to the same values 
previously set
> merge 898097 897958
Bug #898097 [linux] plymouth: linux-image-4.16-1-amd64 with splash: Hangs on 
boot
Bug #898097 [linux] plymouth: linux-image-4.16-1-amd64 with splash: Hangs on 
boot
Marked as found in versions linux/4.16.5-1.
Bug #897572 [linux] urandom hang in early boot prevents plymouth passphrase 
entry
Bug #897958 [linux] urandom hang in early boot prevents plymouth passphrase 
entry
Merged 897572 897958 898097
> affects 897958 + plymouth
Bug #897958 [linux] urandom hang in early boot prevents plymouth passphrase 
entry
Bug #897572 [linux] urandom hang in early boot prevents plymouth passphrase 
entry
Bug #898097 [linux] plymouth: linux-image-4.16-1-amd64 with splash: Hangs on 
boot
Added indication that 897958 affects plymouth
Added indication that 897572 affects plymouth
Added indication that 898097 affects plymouth
> thanks
Stopping processing here.

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

Bug#898100: linux-image-3.16.0-6-amd64: SCTP IPv4/v6 mixed mode socket doesn't return peer adresses anymore (with sctp_getpaddrs())

2018-05-07 Thread Fred Boiteux 
Package: src:linux
Version: 3.16.56-1
Severity: normal

Dear Maintainer,

With latest Debian Jessie Linux kernel (3.16.56-1) version,
my SCTP application, which uses an IPv6 socket to get IPv4 or IPv6 messages,
can retrieve anymore IPv4 addresses from peers, using sctp_getpaddrs() function.

I've identified the impacting patch :r
sctp: Fixup v4mapped behaviour to comply with Sock API

I've rebuilt a kernel with this patch reverted, and my application works
well with

I retrieve IPv4 peer addresses in a IPv6-mapped format, like :
0x00: 0A 00 A5 B8 C0 A8 FE B2 00 00 00 00  
0x0C: 00 00 00 00 00 00 FF FF C0 A8 FE B2  
0x18: 30 3B C0 1F  0;..
which means : :::192.168.254.178%532691760 -> 192.168.254.178

But with the latest Jessie kernel, i get :
0x00: 0A 00 A5 B8 00 00 00 00 00 00 00 00  
0x0C: 00 00 00 00 00 00 FF FF 00 00 00 00  
0x18: 00 00 00 00  
which translates to : :::0.0.0.0


I've stated the same bug with latest Debian Wheezy kernel
(linux-image-3.2.0-6-amd64 package, 3.2.101-1 version) :
I don't know if i should add a separate bug report ?

   With regards,
   Fred.


-- Package-specific info:
** Version:
Linux version 3.16.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10+deb8u1) ) #1 SMP Debian 3.16.56-1 (2018-04-28)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-6-amd64 root=/dev/mapper/vg01-root ro quiet 
video=800x600

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

** Kernel log:
[2.484570] systemd[1]: Listening on LVM2 metadata daemon socket.
[2.484584] systemd[1]: Starting Device-mapper event daemon FIFOs.
[2.484641] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[2.484656] systemd[1]: Starting User and Session Slice.
[2.484711] systemd[1]: Created slice User and Session Slice.
[2.484732] systemd[1]: Starting udev Control Socket.
[2.484775] systemd[1]: Listening on udev Control Socket.
[2.484795] systemd[1]: Starting udev Kernel Socket.
[2.484828] systemd[1]: Listening on udev Kernel Socket.
[2.484847] systemd[1]: Starting Journal Socket.
[2.484911] systemd[1]: Listening on Journal Socket.
[2.484944] systemd[1]: Starting System Slice.
[2.484997] systemd[1]: Created slice System Slice.
[2.485036] systemd[1]: Starting Increase datagram queue length...
[2.485589] systemd[1]: Starting system-systemd\x2dfsck.slice.
[2.485680] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[2.485709] systemd[1]: Starting Nameserver information manager...
[2.486291] systemd[1]: Mounting POSIX Message Queue File System...
[2.486949] systemd[1]: Starting Create list of required static device nodes 
for the current kernel...
[2.489510] systemd[1]: Started Set Up Additional Binary Formats.
[2.489558] systemd[1]: Mounting Huge Pages File System...
[2.490150] systemd[1]: Starting udev Coldplug all Devices...
[2.491097] systemd[1]: Mounting Debug File System...
[2.499518] systemd[1]: Starting Load Kernel Modules...
[2.499953] systemd[1]: Starting system-getty.slice.
[2.500036] systemd[1]: Created slice system-getty.slice.
[2.500076] systemd[1]: Started File System Check on Root Device.
[2.500830] systemd[1]: Starting Slices.
[2.500846] systemd[1]: Reached target Slices.
[2.502470] systemd[1]: Started Increase datagram queue length.
[2.503536] systemd[1]: Started Create list of required static device nodes 
for the current kernel.
[2.503914] systemd[1]: Starting Create Static Device Nodes in /dev...
[2.504426] systemd[1]: Starting Syslog Socket.
[2.504474] systemd[1]: Listening on Syslog Socket.
[2.504522] systemd[1]: Starting Journal Service...
[2.506465] systemd[1]: Started Journal Service.
[2.528380] kkcore: Date: 2015-05-20
[2.528383] kkcore: compile par root le Thu 03 May 2018 12h11m08s
[2.528384] kkcore: Utilise le signal no 41.
[2.534261] loop: module loaded
[2.549479] sctp: Hash tables configured (established 256 bind 256/256)
[2.608051] systemd-udevd[195]: starting version 215
[2.700260] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[2.700266] ACPI: Power Button [PWRF]
[2.719858] parport_pc 00:04: reported by Plug and Play ACPI
[2.720140] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[2.732172] [drm] Initialized drm 1.1.0 20060810
[2.783209] [drm] Found bochs VGA, ID 0xb0c0.
[2.783212] [drm] Framebuffer size 16384 kB @ 0xfd00, mmio @ 0xfebd.
[2.784510] input: PC Speaker as /devices/platform/pcspkr/input/input5
[2.794655] [TTM] Zone  kernel: Available graphics memory: 252968 kiB
[2.794658] [TTM] Initializing pool allocator
[2.794664] [TTM] Initializing DMA pool allocator
[2.795769] fbcon: bochsdrmfb (fb0) is primary device
[2.803213] Console: switching to colour frame buffer device

Processed: Re: Bug#898092: sddm: takes extremely long time to start

2018-05-07 Thread Debian Bug Tracking System 
Processing control commands:

> block -1 with 898021
Bug #898092 [sddm] sddm: takes extremely long time to start
898092 was not blocked by any bugs.
898092 was not blocking any bugs.
Added blocking bug(s) of 898092: 898021

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

[PATCH v2] kbuild: deb-pkg improve maintainer address generation

2018-05-07 Thread riku . voipio 
From: Riku Voipio 

There is multiple issues with the genaration of maintainer string

It uses DEBEMAIL and EMAIL enviroment variables, which may contain angle 
brackets,
creating invalid maintainer strings. The documented KBUILD_BUILD_USER and
KBUILD_BUILD_HOST variables are not used. Undocumented and uncommon NAME
variable is used. Refactor the Maintainer string to:

- use EMAIL or DEBEMAIL directly if they are in form "name "
- use KBUILD_BUILD_USER and KBUILD_BUILD_HOST if set before falling
  back to autodetection
- no longer use NAME variable or the useless Anonymous string

The logic is switched from multiline if/then/fi statements to compact
shell variable substition commands.

Reported-by: Mathieu Malaterre 
Signed-off-by: Riku Voipio 
---
v2: include improvements suggested by Masahiro-san

 scripts/package/mkdebian | 27 +--
 1 file changed, 13 insertions(+), 14 deletions(-)

diff --git a/scripts/package/mkdebian b/scripts/package/mkdebian
index 6adb3a16ba3b..985d72d1ab34 100755
--- a/scripts/package/mkdebian
+++ b/scripts/package/mkdebian
@@ -71,22 +71,21 @@ if [ "$ARCH" = "um" ] ; then
packagename=user-mode-linux-$version
 fi
 
-# Try to determine maintainer and email values
-if [ -n "$DEBEMAIL" ]; then
-   email=$DEBEMAIL
-elif [ -n "$EMAIL" ]; then
-   email=$EMAIL
-else
-   email=$(id -nu)@$(hostname -f 2>/dev/null || hostname)
-fi
-if [ -n "$DEBFULLNAME" ]; then
-   name=$DEBFULLNAME
-elif [ -n "$NAME" ]; then
-   name=$NAME
+email=${DEBEMAIL-$EMAIL}
+
+# use email string directly if it contains 
+if echo $email | grep -q '<.*>'; then
+   maintainer=$email
 else
-   name="Anonymous"
+   # or construct the maintainer string
+   user=${KBUILD_BUILD_USER-$(id -nu)}
+   name=${DEBFULLNAME-$user}
+   if [ -z "$email" ]; then
+   buildhost=${KBUILD_BUILD_HOST-$(hostname -f 2>/dev/null || 
hostname)}
+   email="$user@$buildhost"
+   fi
+   maintainer="$name <$email>"
 fi
-maintainer="$name <$email>"
 
 # Try to determine distribution
 if [ -n "$KDEB_CHANGELOG_DIST" ]; then
-- 
2.14.2

Bug#898098: linux-image-4.16.0-1-amd64: Boot takes very long time (> 2minutes) since 4.16

2018-05-07 Thread Julien 
Package: src:linux
Version: 4.16.5-1
Severity: important

Dear Maintainer,

Since the linux-image-4.16.0-1 update, my laptop is very slow to boot. The boot
time is now 2-3 minutes and before it was only 15 seconds.

During the boot, the screen is black (plymouth splash screen is not visible)
and if i push alt-F4 i'm able to see the splash screen.

If i boot on the last kernel (4.15.0-3) i don't have theses issues.

Please ask me if you need anything.

Thanks,
Julien



-- Package-specific info:
** Version:
Linux version 4.16.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-17)) #1 SMP Debian 4.16.5-1 (2018-04-29)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.16.0-1-amd64 
root=UUID=6b9b2737-ba04-4635-83ff-b786a7c4fd62 ro quiet splash

** Not tainted

** Kernel log:
[   25.328074] thinkpad_acpi: radio switch found; radios are enabled
[   25.333036] thinkpad_acpi: Tablet mode switch found (type: MHKG), currently 
in laptop mode
[   25.333065] thinkpad_acpi: This ThinkPad has standard ACPI backlight 
brightness control, supported by the ACPI video driver
[   25.333065] thinkpad_acpi: Disabling thinkpad-acpi brightness events by 
default...
[   25.335662] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is 
unblocked
[   25.342060] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   25.346604] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[   25.364547] intel ips :00:1f.6: CPU TDP doesn't match expected value 
(found 25, expected 29)
[   25.365007] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input12
[   25.372998] intel ips :00:1f.6: IPS driver initialized, MCP temp limit 90
[   25.373002] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   25.374508] sd 1:0:0:0: Attached scsi generic sg1 type 0
[   25.375375] ACPI Warning: SystemIO range 
0x1028-0x102F conflicts with OpRegion 
0x1000-0x107F (\_SB.PCI0.LPC.PMIO) 
(20180105/utaddress-247)
[   25.375382] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   25.375385] ACPI Warning: SystemIO range 
0x11C0-0x11CF conflicts with OpRegion 
0x1180-0x11FF (\_SB.PCI0.LPC.LPIO) 
(20180105/utaddress-247)
[   25.375390] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   25.375391] ACPI Warning: SystemIO range 
0x11B0-0x11BF conflicts with OpRegion 
0x1180-0x11FF (\_SB.PCI0.LPC.LPIO) 
(20180105/utaddress-247)
[   25.375395] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   25.375396] ACPI Warning: SystemIO range 
0x1180-0x11AF conflicts with OpRegion 
0x1180-0x11FF (\_SB.PCI0.LPC.LPIO) 
(20180105/utaddress-247)
[   25.375401] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   25.375402] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   25.415214] snd_hda_intel :00:1b.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   25.460502] snd_hda_codec_conexant hdaudioC0D0: CX20585: BIOS auto-probing.
[   25.460996] snd_hda_codec_conexant hdaudioC0D0: autoconfig for CX20585: 
line_outs=1 (0x1f/0x0/0x0/0x0/0x0) type:speaker
[   25.460999] snd_hda_codec_conexant hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   25.461001] snd_hda_codec_conexant hdaudioC0D0:hp_outs=2 
(0x1c/0x19/0x0/0x0/0x0)
[   25.461003] snd_hda_codec_conexant hdaudioC0D0:mono: mono_out=0x0
[   25.461004] snd_hda_codec_conexant hdaudioC0D0:inputs:
[   25.461007] snd_hda_codec_conexant hdaudioC0D0:  Internal Mic=0x23
[   25.461009] snd_hda_codec_conexant hdaudioC0D0:  Mic=0x1b
[   25.461011] snd_hda_codec_conexant hdaudioC0D0:  Dock Mic=0x1a
[   25.462416] input: PC Speaker as /devices/platform/pcspkr/input/input13
[   25.463808] Intel(R) Wireless WiFi driver for Linux
[   25.463809] Copyright(c) 2003- 2015 Intel Corporation
[   25.463968] snd_hda_codec_conexant hdaudioC0D0: Enable sync_write for stable 
communication
[   25.464126] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   25.471949] iwlwifi :02:00.0: firmware: direct-loading firmware 
iwlwifi-6000-4.ucode
[   25.472118] iwlwifi :02:00.0: loaded firmware version 9.221.4.1 build 
25532 op_mode iwldvm
[   25.482164] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input14
[   25.483070] input: HDA Intel MID Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input15
[   25.483147] input: HDA Intel MID Dock Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input16
[   25.483222] input: HDA Intel MID Dock Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input17
[   25.483401] input: HDA Intel MID Headphone as