Bug#888106: initramfs-tools: mkinitramfs should fail when ldd fails in copy_exec

Package: initramfs-tools Version: 0.130 Severity: minor Dear Maintainer, We're working on a minimalist build of a Debian derivative which doesn't include bash, and we ran into an situation in which due to a human error the system didn't have a working ldd. This wasn't detected during an image

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 872560 src:flatpack Bug #872560 [src:linux] linux-image-amd64: CONFIG_CGROUP_BPF is not set Added indication that 872560 affects src:flatpack > End of message, stopping processing here. Please contact me if you need assistance. --

Processed: Fwd:

Processing commands for cont...@bugs.debian.org: > affects 872560 src:iproute2 Bug #872560 [src:linux] linux-image-amd64: CONFIG_CGROUP_BPF is not set Added indication that 872560 affects src:iproute2 > End of message, stopping processing here. Please contact me if you need assistance. --

Processed: Re: nfs-utils FTBFS with glibc 2.26

Processing control commands: > tags -1 patch fixed-upstream Bug #887695 [src:nfs-utils] nfs-utils FTBFS with glibc 2.26 Added tag(s) fixed-upstream and patch. -- 887695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887695 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#887695: nfs-utils FTBFS with glibc 2.26

Control: tags -1 patch fixed-upstream On Fri, 19 Jan 2018 07:20:01 +0200 Adrian Bunk wrote: > Source: nfs-utils > ... > rpc.c:469:13: error: 'UINT16_MAX' undeclared (first use in this function); > did you mean 'UINT_MAX'? Seems to be fixed upstream in this commit:

Bug#878221: linux-image-4.9.0-4-amd64: Screen flickers randomly with Radeon R9 270X since upgrade from 4.9.0-3 to 4.9.0-4

The recent backport kernel does *not* have this issue. All is fine with 4.14.0-0.bpo.3-amd64 #1 SMP Debian 4.14.13-1~bpo9+1 (2018-01-14) This is on a Thinkpad X250 with 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) 4.9.0-4-amd64 and 4.9.0-5-amd64 on the same

Processed: tagging 880615, forcibly merging 872560 880615

Processing commands for cont...@bugs.debian.org: > tags 880615 - moreinfo Bug #880615 [src:linux] linux-latest: systemd complains about CONFIG_BPF_SYSCALL not being set Removed tag(s) moreinfo. > forcemerge 872560 880615 Bug #872560 [src:linux] linux-image-amd64: CONFIG_CGROUP_BPF is not set Bug

Re: SLAB vs. SLUB

Hi On Tue, Jan 23, 2018 at 05:37:44PM +, Ben Hutchings wrote: > On Thu, 2018-01-18 at 18:18 +0100, Bastian Blank wrote: > > Not sure when this came up the last time. However we seem to be the > > last large distribution to use SLAB as the kernel allocator. > > Don't we want to change that

Re: SLAB vs. SLUB

On Thu, 2018-01-18 at 18:18 +0100, Bastian Blank wrote: > Moin > > Not sure when this came up the last time. However we seem to be the > last large distribution to use SLAB as the kernel allocator. > > Don't we want to change that some time? Yes, let's change to SLUB. I think SLUB_DEBUG and

Re: armel/marvell kernel size

On Mon, 2018-01-22 at 22:38 +0900, Roger Shimizu wrote: > Dear Ben, > > Thanks for keeping armel things rolling for a few releases! > > On Thu, Jan 18, 2018 at 1:22 PM, Ben Hutchings wrote: > > On Fri, 2017-10-20 at 15:07 +0100, Ben Hutchings wrote: > > > Sadly, linux has

Bug#886746: Bug exists in vanilla kernel 4.9.65

I've compiled a vanilla kernel 4.9.65 (from git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git) and the bug is present.  Vanilla kernel 4.9.30 works. I'll roll up my sleeves and start bisecting. -- John Hughes, CalvaEDI S.A.S. -- An Esker Company

Processed: forwarded 886746 https://bugzilla.kernel.org/show_bug.cgi?id=198563

Processing commands for cont...@bugs.debian.org: > forwarded 886746 https://bugzilla.kernel.org/show_bug.cgi?id=198563 Bug #886746 [src:linux] linux-image-4.9.0-5-amd64: screen connected via displayport hub flashes black Set Bug forwarded-to-address to

Bug#887389: Bug solved

On Buster (testing at the moment), with the last 4.14 linux kernel image, speedstep works again correctly :) We can say the bug is solved. Arnaud