Bug#915367: Removed package(s) from experimental

We believe that the bug you reported is now fixed; the following package(s) have been removed from experimental: linux-image-4.10.0-rc6-amd64 | 4.10~rc6-1~exp2 | amd64 --- Reason --- RoQA; NBS package left in experimental for some long ago reason --

Processed: 887045

Processing commands for cont...@bugs.debian.org: > notfixed 887045 linux/4.19.12-1 Bug #887045 {Done: Ben Hutchings } [src:linux] iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using hostapd Ignoring request to alter fixed versions of bug #887045 to the same values previously set > End

Bug#887045: 887045

Not fixed in Linux stupid 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64 GNU/Linux [297269.085315] WARNING: CPU: 1 PID: 451 at drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1431 iwl_mvm_rx_tx_cmd+0x1e6/0x650 [iwlmvm] [297269.085321] Modules linked in: ufs

Bug#916670: cryptsetup: ERROR: Couldn't resolve device rootfs

> update-initramfs: Generating /boot/initrd.img-4.18.0-3-amd64 > cryptsetup: ERROR: Couldn't resolve device rootfs > ^^^ this is due rootfs / rootfs rw 0 0 line in /etc/mtab remove it and the problem no more.

hardening-check can detect whether kernel is protected or not

When I run hardening-check on some binary I get results similar the following: # hardening-check /usr/bin/firefox /usr/bin/firefox: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate bin

Bug#917632: marked as done (bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs)

Your message dated Tue, 1 Jan 2019 15:19:00 -0800 with message-id <20190101231900.urab7yla74blu...@qor.donarmstrong.com> and subject line Re: Bug#917632: bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs has caused the Debian Bug report #9176

linux_4.9.144-1_source.changes ACCEPTED into proposed-updates->stable-new

Mapping stretch to stable. Mapping stable to proposed-updates. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 30 Dec 2018 23:27:02 + Source: linux Binary: linux-source-4.9 linux-support-4.9.0-8 linux-doc-4.9 linux-manual-4.9 linux-kbuild-4.9 linux-cpupower

Processing of linux_4.9.144-1_source.changes

linux_4.9.144-1_source.changes uploaded successfully to localhost along with the files: linux_4.9.144-1.dsc linux_4.9.144.orig.tar.xz linux_4.9.144-1.debian.tar.xz linux_4.9.144-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: reassign 917632 to initramfs-tools-core, tagging 917632

Processing commands for cont...@bugs.debian.org: > reassign 917632 initramfs-tools-core Bug #917632 [src:linux] bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs Bug reassigned from package 'src:linux' to 'initramfs-tools-core'. No longer ma

Bug#917632: bugs.debian.org: During kernel boot the nvme module is not loaded, make the kernel not finding the rootfs

Thank you. I fixed my problem with manually running sudo update-initramfs -u I don't why the initial initramfs did not contain the necessary "things" to load the nvme-module automatically. Maybe it was the constellation of update-packages. -- Patrick. On Sat, 29 Dec 2018 15:12:52 -

Bug#917939: please enable CONFIG_ARM_ARMADA_37XX_CPUFREQ for arm64

Source: linux Version: 4.19.12-1 Severity: wishlist Hi, this option is missing for cpu frequency scaling on e.g. my espressobin. According to [0], 4.19 should be ready for cpufreq on this platform. The mentioned AVS support doesn't seem to have an additional config knob, or at least I didn't