Processed: tagging 945213

2019-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 945213 - moreinfo Bug #945213 [src:linux] linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 945213:

Bug#944350: systemd: screen remains off after waking up from suspend

2019-11-24 Thread Jiri Kanicky
Further to the issue, when I set BIOS to discrete graphics only, I am experiencing the same issue when booting the system from shutdown state. The screen stays off, but the OS is booted and working.

linux_4.9.189-3+deb9u2_multi.changes ACCEPTED into oldstable-proposed-updates->oldstable-new, oldstable-proposed-updates

2019-11-24 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 11 Nov 2019 12:18:59 + Binary: linux-doc-4.9 linux-headers-4.9.0-11-common linux-headers-4.9.0-11-common-rt linux-manual-4.9 linux-source-4.9 linux-support-4.9.0-11 Source: linux Architecture: all source

Processed: reassign 945157 to src:linux

2019-11-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 945157 src:linux 4.19.67-2+deb10u2 Bug #945157 [linux-image-4.19.0-6-armmp] Wrong system time on DHCOM i.MX6 due to missing RTC driver Bug reassigned from package 'linux-image-4.19.0-6-armmp' to 'src:linux'. No longer marked as found in

Bug#945213: Info received (Bug#945213: linux-image-5.2.0-3-amd64: OOM handling broken if hugepages are enabled)

2019-11-24 Thread Anton Ivanov
[0.00] Linux version 5.2.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-22)) #1 SMP Debian 5.2.17-1 (2019-09-26) [0.00] Command line: BOOT_IMAGE=diskless/amd64/vmlinuz-5.2.0-3-amd64 initrd=diskless/amd64/initrd.img-5.2.0-3-amd64 root=/dev/nfs ip=dhcp

Bug#944839: linux-image-5.2.0-0.bpo.3-rt-amd64-unsigned: issues for application crash with this kernel

2019-11-24 Thread westlake
that solves it, thanks fwiw, I'm reading about this kernel option from lwn, https://lwn.net/Articles/673597/ and the opinions vary whether there's security improvement having it enabled/disabled... this may not be desirable for multi-user systems, here it's just a workstation so I suppose