linux_3.16.56-1+deb8u1_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 08 May 2018 16:11:04 +0100 Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-6 linux-libc-dev linux-headers-3.16.0-6-all linux-headers-3.16.0-6-all-alpha

Bug#897588: marked as done (Automatic assignment of TUN device broken after (security) kernel upgrade)

Your message dated Thu, 10 May 2018 21:20:13 + with message-id and subject line Bug#897427: fixed in linux 3.16.56-1+deb8u1 has caused the Debian Bug report #897427, regarding Automatic assignment of TUN device broken after (security) kernel upgrade to be

Bug#898067: marked as done (Division by zero in microcode loader when booting on EC2 c3.large/r3.large)

Your message dated Thu, 10 May 2018 21:20:14 + with message-id and subject line Bug#898067: fixed in linux 3.16.56-1+deb8u1 has caused the Debian Bug report #898067, regarding Division by zero in microcode loader when booting on EC2 c3.large/r3.large to

Bug#897427: marked as done (linux-image-3.16.0-6-amd64 breaks KVM guests in libvirt)

Your message dated Thu, 10 May 2018 21:20:13 + with message-id and subject line Bug#897427: fixed in linux 3.16.56-1+deb8u1 has caused the Debian Bug report #897427, regarding linux-image-3.16.0-6-amd64 breaks KVM guests in libvirt to be marked as done.

Re: Fixing Linux getrandom() in stable

On Thu, 2018-05-10 at 10:41 -0700, Russ Allbery wrote: > It means that the configured timeout for which it's reasonable to wait for > randomness is centralized in one service that can set that based on > understanding of what's necessary in practice, and timeouts to catch other > startup problems

Re: Fixing Linux getrandom() in stable

On Thu, May 10, 2018 at 07:30:46PM +0200, Michael Biebl wrote: > > So we'd shift the waiting for randomness-to-be-available from one > service to another? I don't quite see yet, where the benefit is in that. > What's better if a wait-for-rng-ready binary blocks on getrandom() > instead of the

Re: Fixing Linux getrandom() in stable

On 5/10/18 7:30 PM, Michael Biebl wrote: > So we'd shift the waiting for randomness-to-be-available from one > service to another? I don't quite see yet, where the benefit is in that. > What's better if a wait-for-rng-ready binary blocks on getrandom() > instead of the krb5-kdc binary itself? We

Re: Fixing Linux getrandom() in stable

Michael Biebl writes: > Am 10.05.2018 um 19:22 schrieb Russ Allbery: >> I may be misunderstanding the nature of the issue, but I believe that a >> Type=oneshot service that runs a small C program that calls getrandom() >> and then exit(0) when it returns would provide a useful

Re: Fixing Linux getrandom() in stable

Hi Russ Am 10.05.2018 um 19:22 schrieb Russ Allbery: > Michael Biebl writes: >> Am 10.05.2018 um 00:46 schrieb Ben Hutchings: > >>> One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and >>> also proposed that systemd could provide a wait-for-rng-ready unit to >>>

Re: Fixing Linux getrandom() in stable

Michael Biebl writes: > Am 10.05.2018 um 00:46 schrieb Ben Hutchings: >> One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and >> also proposed that systemd could provide a wait-for-rng-ready unit to >> support this. > What exactly would such a wait-for-rng-ready

Bug#898350: linux-image-4.16.0-1-amd64: r8169 ethernet module unworking when returning from suspend to ram

Package: src:linux Version: 4.16.5-1 Severity: important Dear Maintainer, * What led up to the situation? suspend to ram with systemd * What was the outcome of this action? ethernet card gets unusable, links no longer detected * What outcome did you expect instead?

linux_3.16.56-1+deb8u1_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new

Mapping oldstable-security to oldstable-proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 08 May 2018 16:11:04 +0100 Source: linux Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16 linux-support-3.16.0-6 linux-libc-dev

Bug#898344: linux-image-4.9.0-6-amd64: NFS fails to mount with sec=krb5

Package: src:linux Version: 4.9.88-1+deb9u1 Severity: normal Dear Maintainer, After updating to 4.9.0-6-amd64 nfs mounts fail with these messages: [ 687.358529] NFS: nfs4_discover_server_trunking unhandled error -5. Exiting with error EIO [ 687.364094] gss_marshal: gss_get_mic FAILED (851968)

Re: Fixing Linux getrandom() in stable

Am 10.05.2018 um 00:46 schrieb Ben Hutchings: > 1. Add entropy to the kernel during boot; either: >a. Improve systemd-random-seed >b. Recommend use of haveged > 2. For each affected userland package, either: >a. Revert to using /dev/urandom >b. Tolerate a longer wait for

Bug#898074: Confirming that it seems to be solved

With 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07), the problem disappeared from two different laptops that where affected. Seems like it is fixed. -- Matthieu Dubuget

Bug#898074: linux-image-4.9.0-6-amd64: gdm3 fails to start

This seems to have been solved with the most recent kernel update: 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) After installing the above kernel everything again works as it should; gmd start without me having to ”wiggle the mouse” in order to get to the login screen. Thanks to

Bug#898335: linux-image-4.16.0-1-amd64: Boot hangs for quite some time. Black screen. Cursor only.

Package: src:linux Version: 4.16.5-1 Severity: important Dear Maintainer, I have the same issue on my ThinkPad X220. After grub, the linux-image-4.16.0-1-amd64 is loading and remains in a state with black screen and blinking cursor only. After about 2 minutes the boot continues with the

linux_3.16.56-1_multi.changes REJECTED

Moving back to unchecked, try 3. *sigh* === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.

linux_3.16.56-1_multi.changes is NEW

Mapping oldstable-security to oldstable-proposed-updates. linux_3.16.56-1.debian.tar.xz is only available in NEW. linux_3.16.56.orig.tar.xz is only available in NEW. linux_3.16.56-1.dsc is only available in NEW. linux_3.16.56.orig.tar.xz is only available in NEW. linux_3.16.56-1.debian.tar.xz is

Processed: forcibly merging 896649 898318

Processing commands for cont...@bugs.debian.org: > forcemerge 896649 898318 Bug #896649 [src:linux] linux: Please enable CONFIG_DM_INTEGRITY Bug #896649 [src:linux] linux: Please enable CONFIG_DM_INTEGRITY Marked as found in versions linux/4.16.5-1. Bug #898318 [src:linux] linux-image-amd64:

Processed: reassign 898318 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 898318 src:linux 4.16.5-1 Bug #898318 [linux-image-amd64] linux-image-amd64: dm-integrity Module not avivable Bug reassigned from package 'linux-image-amd64' to 'src:linux'. No longer marked as found in versions linux-latest/93.

Bug#898318: linux-image-amd64: dm-integrity Module not avivable

Package: linux-image-amd64 Version: 4.16+93 Severity: wishlist Dear Maintainer, I wanted to try dm-integrity with integritysetup (allready part of cryptsetup-bin), but the Module is not avivable in any kernel packages. Could you please add the Module to the package/build? -- System

Bug#898021: linux-image-4.16.0-1-amd64: kernel 4.16 infinite wait after dm login on ivy bridge and bay trail

My workarounds for this at the moment are to install tools that increase the kernel entropy pool. If not a virtual machine, and `grep -i -o -m 1 rdrand /proc/cpuinfo` returns 'rdrand', then I install the 'rng-tools5' package which uses the hardware rng in many cpu's to provide entropy to the