linux_5.3.7-1_multi.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 20 Oct 2019 00:56:32 +0200 Binary: linux-doc linux-doc-5.3 linux-headers-5.3.0-1-common linux-source linux-source-5.3 linux-support-5.3.0-1 Source: linux Architecture: all source Version: 5.3.7-1 Distribution:

Bug#935945: marked as done (linux-image-5.2.0-2-amd64: does not load signed kernel modules when UEFI Secure Boot is enabled)

Your message dated Sun, 20 Oct 2019 22:05:41 + with message-id and subject line Bug#935945: fixed in linux 5.3.7-1 has caused the Debian Bug report #935945, regarding linux-image-5.2.0-2-amd64: does not load signed kernel modules when UEFI Secure Boot is enabled to be marked as done. This

Bug#940530: marked as done (Add CONFIG_BRCMFMAC_SDIO=y to linux-image-rpi)

Your message dated Sun, 20 Oct 2019 22:05:41 + with message-id and subject line Bug#940530: fixed in linux 5.3.7-1 has caused the Debian Bug report #940530, regarding Add CONFIG_BRCMFMAC_SDIO=y to linux-image-rpi to be marked as done. This means that you claim that the problem has been dealt

Bug#940181: marked as done (linux-image-5.2.0-2-amd64: Kernel does not accept self-signed modules using UEFI db key)

Your message dated Sun, 20 Oct 2019 22:05:41 + with message-id and subject line Bug#935945: fixed in linux 5.3.7-1 has caused the Debian Bug report #935945, regarding linux-image-5.2.0-2-amd64: Kernel does not accept self-signed modules using UEFI db key to be marked as done. This means

Bug#940726: marked as done (linux-source-5.2: Enable SOF audio driver and back-port fixes required to 5.2 kernel)

Your message dated Sun, 20 Oct 2019 22:05:41 + with message-id and subject line Bug#940726: fixed in linux 5.3.7-1 has caused the Debian Bug report #940726, regarding linux-source-5.2: Enable SOF audio driver and back-port fixes required to 5.2 kernel to be marked as done. This means that

Bug#939773: marked as done (linux-image-5.2.0-2-amd64: MOK key not used for verification of modules signatures.)

Your message dated Sun, 20 Oct 2019 22:05:41 + with message-id and subject line Bug#935945: fixed in linux 5.3.7-1 has caused the Debian Bug report #935945, regarding linux-image-5.2.0-2-amd64: MOK key not used for verification of modules signatures. to be marked as done. This means that

Bug#941827: marked as done (module loading fails with error: "Lockdown: modprobe: Loading of unsigned module is restricted; see https://wiki.debian.org/SecureBoot")

Your message dated Sun, 20 Oct 2019 22:05:41 + with message-id and subject line Bug#935945: fixed in linux 5.3.7-1 has caused the Debian Bug report #935945, regarding module loading fails with error: "Lockdown: modprobe: Loading of unsigned module is restricted; see

Re: Debian Linux kernel uploads

Hi, On Sun, Oct 20, 2019 at 02:27:21PM +0100, Ben Hutchings wrote: > On Sun, 2019-10-20 at 13:58 +0200, Hector Oron wrote: > > Hello, > > > > I would like to support Debian Linux kernel team by doing kernel > > package uploads. > > > > Initially, I would like to attempt timely (weekly or

linux_5.3.7-1_multi.changes is NEW

binary:acpi-modules-5.3.0-1-686-di is NEW. binary:acpi-modules-5.3.0-1-686-pae-di is NEW. binary:acpi-modules-5.3.0-1-amd64-di is NEW. binary:affs-modules-5.3.0-1-4kc-malta-di is NEW. binary:affs-modules-5.3.0-1-5kc-malta-di is NEW. binary:affs-modules-5.3.0-1-loongson-3-di is NEW.

Processing of linux_5.3.7-1_multi.changes

linux_5.3.7-1_multi.changes uploaded successfully to localhost along with the files: linux_5.3.7-1.dsc linux_5.3.7.orig.tar.xz linux_5.3.7-1.debian.tar.xz linux_5.3.7-1_source.buildinfo linux-doc-5.3_5.3.7-1_all.deb linux-doc_5.3.7-1_all.deb

Debian kernel patch propagation

Hi, What is the current workflow of the patch propagation from linux mainline to debian stable kernel versions? are the downstream debian kernels rebased against the latest mainline kernel version or are they just rebased against the lts upstream version from which the debian kernel was initially

Bug#939170: Maybe wrong package?

Hi, is it possible this one is reported against the wrong package? It seems like there are a few lenovo laptop / thinkpad owners who experience this. Is there some (pseudo)package to report this to? Maybe it gets a bit more traction there... Cheers, Daniel

Re: Debian Linux kernel uploads

On Sun, 2019-10-20 at 13:58 +0200, Hector Oron wrote: > Hello, > > I would like to support Debian Linux kernel team by doing kernel > package uploads. > > Initially, I would like to attempt timely (weekly or bi-weekly, it > has not been discussed yet) updates for Debian Linux kernel package

Bug#927026: Please enable CONFIG_MD_CLUSTER for linux packages in Buster

Hi, Please enable for kernels in unstable so we can test cluster functionality for bullseye release. -- Valentin

Debian Linux kernel uploads

Hello, I would like to support Debian Linux kernel team by doing kernel package uploads. Initially, I would like to attempt timely (weekly or bi-weekly, it has not been discussed yet) updates for Debian Linux kernel package in SID and see how that works. In anycase, I would like to give a

Bug#942700: linux-image-5.2.0-3-amd64: Regularly, 1 CPU core is entirely hogged by kworker/0:1+kacpid

Package: src:linux Version: 5.2.17-1 Severity: important Dear Maintainer, Since the most recent kernel update, I regularly have 100% load on one CPU core, According to top, the load is caused by "kworker/0:1+kacpid". I have never seen this effect before so this is a recent regression. This