Processing of linux-signed-amd64_4.19.16+1~bpo9+1_source.changes

linux-signed-amd64_4.19.16+1~bpo9+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_4.19.16+1~bpo9+1.dsc linux-signed-amd64_4.19.16+1~bpo9+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#922204: linux-image-4.19.0-3-armmp-lpae: Kernel mode NEON support should be enabled

Package: linux-image-4.19.0-3-armmp-lpae Severity: important Dear Maintainer, Currently, the 32-bit ARM kernels are built without support for kernel mode NEON, which means that none of the modules that depend on it are built either. This mostly affects crypto drivers, as well as RAID6 and XOR. T

Processing of linux-signed-amd64_4.19.20+1_source.changes

linux-signed-amd64_4.19.20+1_source.changes uploaded successfully to localhost along with the files: linux-signed-amd64_4.19.20+1.dsc linux-signed-amd64_4.19.20+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of linux-signed-arm64_4.19.20+1_source.changes

linux-signed-arm64_4.19.20+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_4.19.20+1.dsc linux-signed-arm64_4.19.20+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of linux-signed-arm64_4.19.16+1~bpo9+1_source.changes

linux-signed-arm64_4.19.16+1~bpo9+1_source.changes uploaded successfully to localhost along with the files: linux-signed-arm64_4.19.16+1~bpo9+1.dsc linux-signed-arm64_4.19.16+1~bpo9+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of linux-signed-i386_4.19.16+1~bpo9+1_source.changes

linux-signed-i386_4.19.16+1~bpo9+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_4.19.16+1~bpo9+1.dsc linux-signed-i386_4.19.16+1~bpo9+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-amd64_4.19.20+1_source.changes is NEW

Mapping sid to unstable. binary:linux-image-4.19.0-3-amd64 is NEW. binary:linux-image-4.19.0-3-cloud-amd64 is NEW. binary:linux-image-4.19.0-3-rt-amd64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it

linux-signed-amd64_4.19.16+1~bpo9+1_source.changes is NEW

binary:linux-image-4.19.0-0.bpo.2-amd64 is NEW. binary:linux-image-4.19.0-0.bpo.2-cloud-amd64 is NEW. binary:linux-image-4.19.0-0.bpo.2-rt-amd64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a

linux-signed-arm64_4.19.16+1~bpo9+1_source.changes is NEW

binary:linux-image-4.19.0-0.bpo.2-arm64 is NEW. binary:linux-image-4.19.0-0.bpo.2-rt-arm64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so

linux-signed-i386_4.19.16+1~bpo9+1_source.changes is NEW

binary:linux-image-4.19.0-0.bpo.2-686 is NEW. binary:linux-image-4.19.0-0.bpo.2-686-pae is NEW. binary:linux-image-4.19.0-0.bpo.2-rt-686-pae is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good

linux-signed-arm64_4.19.20+1_source.changes is NEW

Mapping sid to unstable. binary:linux-image-4.19.0-3-arm64 is NEW. binary:linux-image-4.19.0-3-rt-arm64 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes ar

Processing of linux-signed-i386_4.19.20+1_source.changes

linux-signed-i386_4.19.20+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_4.19.20+1.dsc linux-signed-i386_4.19.20+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-amd64_4.19.20+1_source.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Feb 2019 16:55:59 + Source: linux-signed-amd64 Binary: kernel-image-4.19.0-3-amd64-di nic-modules-4.19.0-3-amd64-di nic-wireless-modules-4.19.0-3-amd64-di nic-shared-modules-4.19.0-3-amd64-di serial-modul

linux-signed-arm64_4.19.20+1_source.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Feb 2019 16:55:59 + Source: linux-signed-arm64 Binary: kernel-image-4.19.0-3-arm64-di nic-modules-4.19.0-3-arm64-di nic-wireless-modules-4.19.0-3-arm64-di nic-shared-modules-4.19.0-3-arm64-di usb-serial-m

Processed: reassign 922204 to src:linux

Processing commands for cont...@bugs.debian.org: > reassign 922204 src:linux 4.19.20-1 Bug #922204 [linux-image-4.19.0-3-armmp-lpae] linux-image-4.19.0-3-armmp-lpae: Kernel mode NEON support should be enabled Bug reassigned from package 'linux-image-4.19.0-3-armmp-lpae' to 'src:linux'. Ignoring r

Processed: reassign 922204 to src:linux, forcibly merging 917608 922204

Processing commands for cont...@bugs.debian.org: > reassign 922204 src:linux 4.19.20-1 Bug #922204 [src:linux] linux-image-4.19.0-3-armmp-lpae: Kernel mode NEON support should be enabled Ignoring request to reassign bug #922204 to the same package Bug #922204 [src:linux] linux-image-4.19.0-3-armm

linux-signed-i386_4.19.20+1_source.changes is NEW

Mapping sid to unstable. binary:linux-image-4.19.0-3-686 is NEW. binary:linux-image-4.19.0-3-686-pae is NEW. binary:linux-image-4.19.0-3-rt-686-pae is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had

linux-signed-i386_4.19.20+1_source.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 11 Feb 2019 16:55:59 + Source: linux-signed-i386 Binary: kernel-image-4.19.0-3-686-di nic-modules-4.19.0-3-686-di nic-wireless-modules-4.19.0-3-686-di nic-shared-modules-4.19.0-3-686-di serial-modules-4.19.0

linux-signed-i386_4.19.16+1~bpo9+1_source.changes ACCEPTED into stretch-backports, stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 07 Feb 2019 21:46:07 + Source: linux-signed-i386 Binary: kernel-image-4.19.0-0.bpo.2-686-di nic-modules-4.19.0-0.bpo.2-686-di nic-wireless-modules-4.19.0-0.bpo.2-686-di nic-shared-modules-4.19.0-0.bpo.2-686-

linux-signed-arm64_4.19.16+1~bpo9+1_source.changes ACCEPTED into stretch-backports, stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 07 Feb 2019 21:46:07 + Source: linux-signed-arm64 Binary: kernel-image-4.19.0-0.bpo.2-arm64-di nic-modules-4.19.0-0.bpo.2-arm64-di nic-wireless-modules-4.19.0-0.bpo.2-arm64-di nic-shared-modules-4.19.0-0.bp

linux-signed-amd64_4.19.16+1~bpo9+1_source.changes ACCEPTED into stretch-backports, stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 07 Feb 2019 21:46:07 + Source: linux-signed-amd64 Binary: kernel-image-4.19.0-0.bpo.2-amd64-di nic-modules-4.19.0-0.bpo.2-amd64-di nic-wireless-modules-4.19.0-0.bpo.2-amd64-di nic-shared-modules-4.19.0-0.bp

Bug#922146: Narrowed problem down. Found workaround

Dear Maintainer, After reading through other bugreports with hibernation problems, I was pointed into a possible workaround (see Bug#902416): Usually, I use "systemctl hibernate" to go into hibernation. The screen turns black and the system powers down. However, if I use $ sudo sh -c "echo 'disk

Bug#922234: Stretch stuck after loading initial ramdisk

Package: linux-image-amd64 Version: 4.9+80+deb9u6 Trying to boot will lead to a hung system after the message "loading initial ramdisk". Ctrl-Alt-Del will not work. I have to switch off the machine the hard way. Workaround I: This behavior first appeared a while ago (maybe 2-3 months) after an u

Bug#922234: - behavior cannot be reproduced

I just wanted to let you know the behavior cannot be reproduced with 100% success. After I wrote the initial bugreport I performed updates with synaptic and then a reboot. With "touch /forcefsck" first and then reboot the system came up normal.

Bug#919859: [src:linux]

Wol is still not working after the upgrade to 4.19.20 (package linux-image-4.19.0-2-amd64 from unstable as of Feb 13th 2019).

Processed: found 919859 in 4.19.20-1, found 919859 in 4.19.16-1

Processing commands for cont...@bugs.debian.org: > # according to reporter > found 919859 4.19.20-1 Bug #919859 [src:linux] linux-image-4.19.0-1-amd64: Lost wake on lan after the upgrade to 4.19 Marked as found in versions linux/4.19.20-1. > found 919859 4.19.16-1 Bug #919859 [src:linux] linux-im

Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

On Tue, 12 Feb 2019 00:04:15 +0100 Cesare Leonardi wrote: It still has no reply but I really hope someone will backport your fix soon. Jens Axboe has determined that the proper fix is quite different: http://git.kernel.dk/cgit/linux-block/commit/?h=for-linus&id=85bd6e61f34dffa8ec2dc75ff3c02ee

Bug#886049: Further splice() tests with and without libglib2.0-0

Reiny wrote... > About the above mentioned bug I did some more tests: I built a debug version > of the libglib2.0-0 to see what is happening inside where the splice > function is called. In case of a small file with 112 bytes the splice() is > called inside the function do_splice() in gfile.c for

Bug#922274: thinkpad_acpi: Error probing battery 2 (Lenovo Thinkpad Yoga 11e)

Package: src:linux Version: 4.19.20-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Since some time I get these error messages during startup (however, the system starts without any issue): [ 31.210320] ACPI: \_SB_.PCI0.LPCB.EC__.HKEY: BCTG evaluated but flagged as error [