Re: Bug#872664: linux-image-4.9.0-3-686-pae: Resume from hibernate fails on Thinkpad T60

It's a bug on 4.9.0-3 Debian's kernel ! I upgrade kernel to 4.13 and hibernate work on Lenovo B 590 ! With Debian 8 also hibernate work ( kernel 3.16 ) so there is a bug on 4.9.0-3 kernel !

Bug#881830: linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel

Since I was a little puzzled as to why keyutils built previously on mips, I found this commit to 4.8 which caused the need for KEYS_COMPAT: commit 20f06ed9f61a185c6dabd662c310bed6189470df Author: David Howells Date: Wed Jul 27 11:43:37 2016 +0100 KEYS: 64-bit MIPS

Bug#881830: linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel

Source: linux Version: 4.9.51-1 Severity: wishlist Control: fixed -1 4.12.2-1~exp1 Hi, Is it possible to cherry-pick the following upstream commit into the stable kernel so it is available on the buildds? commit 47b2c3fff4932e6fc17ce13d51a43c6969714e20 Author: Bilal Amarni

Processed: linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel

Processing control commands: > fixed -1 4.12.2-1~exp1 Bug #881830 [src:linux] linux: cherry-pick "security/keys: add CONFIG_KEYS_COMPAT to Kconfig" to stretch kernel Marked as fixed in versions linux/4.12.2-1~exp1. -- 881830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881830 Debian Bug

Bug#881813: marked as done (linux-image-4.13.0-1-amd64: Linux 4.13.0 cannot run squeeze chroot environment)

Your message dated Wed, 15 Nov 2017 15:39:59 +0100 with message-id <20171115143958.wppch22or4765...@lorien.valinor.li> and subject line Re: Bug#881813: linux-image-4.13.0-1-amd64: Linux 4.13.0 cannot run squeeze chroot environment has caused the Debian Bug report #881813, regarding

Bug#881813: linux-image-4.13.0-1-amd64: Linux 4.13.0 cannot run squeeze chroot environment

Same for buster. I. e. if I replace sid virtual machine with buster virtual machine, I got the same bug. I mean that I created buster from the same alpha 1 installer, but this time I didn't upgrade it to sid. == Askar Safin http://vk.com/safinaskar

Bug#881425: Info received (Bug#881425: linux-image-4.13.0-1-amd64: "rm -rf " fails with ENOTEMPTY (Directory not empty))

Hmmm, using a VM I can't reproduce with 4.13.10-1... The "rm /*" is too fast, perhaps I need more background IO noise?

Re: Secure boot signing infrastructure - feedback request

Hi, On 10/31/2017 01:58 PM, Steve McIntyre wrote: Nearly three weeks later with no responses. Let's see if we get things moving... On Wed, Oct 11, 2017 at 09:48:46PM -0300, Helen Koike wrote: I did a summary about the current discussion here:

Bug#871608: linux-image-4.9.0-3-amd64: Linux kernel should handle decreasing cpu steal clock counter gracefully

Hi, I ran into the same issue with 4.9.51-1 in the guest. My dom0 in this case is still Jessie with its xen 4.4 version. Users (rightfully) worry about what's suddenly wrong with their virtual machine, since the steal values mess up the cpu graphs. I see that all the discussions linked above

Bug#881813: linux-image-4.13.0-1-amd64: Linux 4.13.0 cannot run squeeze chroot environment

Package: src:linux Version: 4.13.10-1 Severity: important Current (2017-11-14 - 2017-11-15) sid with up-to-date kernel (4.13.0) cannot "chroot" into squeeze chroot environment. What I did? * I started qemu-system-x86_64 (debian package qemu-system-x86 1:2.8+dfsg-6+deb9u3) from my host system