linux-signed-amd64_5.3.9+1_source.changes is NEW

[Debian FTP Masters]

Mapping sid to unstable.
binary:linux-image-5.3.0-2-amd64 is NEW.
binary:linux-image-5.3.0-2-cloud-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 good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

Processing of linux-signed-amd64_5.3.9+1_source.changes

[Debian FTP Masters]

linux-signed-amd64_5.3.9+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-amd64_5.3.9+1.dsc
  linux-signed-amd64_5.3.9+1.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#944428: Additional information

[Marc Bonnor]

-- Package-specific info:
** Version:
Linux version 5.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc
version 9.2.1 20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-
10-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-1-amd64 root=UUID=7761194e-0340-44b9-
b0bd-2b0643ef86ca ro quiet pcie_ports=compat

** Tainted: WOE (12800)
 * Taint on warning.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[   50.347650] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   51.357254] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   52.363217] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   53.365411] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   54.399774] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   55.410404] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   56.421193] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   57.424143] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   58.455202] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   59.458419] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   60.469761] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   61.481226] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   62.512675] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   63.516129] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   64.519806] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   65.531448] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   66.571124] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   67.574851] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   68.582652] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   69.586466] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   70.626294] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   71.634024] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   72.641863] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   73.645755] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   74.693570] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   75.705582] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   76.717449] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   77.721362] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   78.753244] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   79.757073] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   80.768948] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   81.772948] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   82.804840] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   83.808782] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   84.812703] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   85.816670] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   86.848544] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20170500
[   87.852486] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270500
[   88.856417] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370500
[   89.860358] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x201f0500
[   90.892304] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370740
[   91.900240] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20370740
[   92.904107] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270d01
[   92.904122] snd_hda_codec_generic hdaudioC0D2: Unable to sync
register 0x2f0d00. -11
[   93.908125] snd_hda_intel :00:1f.3: No response from codec,

Re: Dropping haveged from the installer

[Ben Hutchings]

On Thu, 2019-11-07 at 22:36 +0100, Cyril Brulebois wrote:
> Hi Ben,
> 
> Ben Hutchings  (2019-11-07):
> > Linux 5.4 introduces an in-kernel jitter-entropy implementation for
> > systems without a usable hardware RNG, which should remove the need for
> > haveged.
> > 
> > We could possibly cherry-pick that change on to 5.3, to avoid the need
> > for further changes to haveged packaging.
> 
> Oh, great.
> 
> Feel free to either follow-up on this bug report once you have
> backported it to 5.3, or alternatively once 5.4 trunk has reached
> experimental, so that the switch away from haveged can be tested.

This is included in 5.3.9-1, which is currently building.

Ben.

-- 
Ben Hutchings
Everything should be made as simple as possible, but not simpler.
  - Albert Einstein




signature.asc
Description: This is a digitally signed message part

linux_5.3.9-1_source.changes ACCEPTED into unstable, unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop condition in io_work
 - nvme-pci: Save PCI state before putting drive into deepest state
 - nvme: fix an error code in nvme_init_subsystem()
 - nvme-rdma: Fix max_hw_sectors calculation
 - nvme: Added QUIRKs for ADATA XPG SX8200 Pro 512GB
 - nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T
 - nvme-rdma: fix possible use-after-free in connect timeout
 - blk-mq: honor IO scheduler for multiqueue devices
 - xen/efi: Set nonblocking callbacks
 - loop: change queue block size to match when using DIO
 - nl80211: fix null pointer dereference
 - mac80211: fix txq null pointer dereference
 - netfilter: nft_connlimit: disable bh on garbage collection
 - [armhf,arm64] net: stmmac: xgmac: Not all Unicast addresses may be
   available
 - [armhf,arm64] net: stmmac: dwmac4: Always update the MAC Hash Filter
 - [armhf,arm64] net: stmmac: Correctly take timestamp for PTPv2
 - [armhf,arm64] net: stmmac: Do not stop PHY if WoL is enabled
 - drm/amdgpu: fix multiple memory leaks in acp_hw_init
 - drm/amd/display: memory leak
 - [mips*el/loongson-*] Fix the link time qualifier of 'serial_exit()'
 - [arm64] net: hisilicon: Fix usage of uninitialized variable in function
   mdio_sc_cfg_reg_write()
 - [armhf,arm64] net: stmmac: Avoid deadlock on suspend/resume
 - [s390x] mm: fix -Wunused-but-set-variable warnings
 - r8152: Set macpassthru in reset_resume callback
 - net: phy: allow for reset line to be tied to a sleepy GPIO controller
 - net: phy: fix write to mii-ctrl1000 register
 - vfs: Convert filldir[64]() from __put_user() to unsafe_put_user()
 - elf: don't use MAP_FIXED_NOREPLACE for elf executable mappings
   (regression in 4.17)
 - vfs: Make filldir[64]() verify the directory entry filename is valid
 - uaccess: implement a proper unsafe_copy_to_user() and switch filldir over
   to it
 - vfs: filldir[64]: remove WARN_ON_ONCE() for bad directory entries
 - net_sched: fix backward compatibility for TCA_KIND (regression in 5.3.4)
 - net_sched: fix backward compatibility for TCA_ACT_KIND (regression in
   5.3.4)
 - libata/ahci: Fix PCS quirk application (regression in 5.3.4)
 - md/raid0: fix warning message for parameter default_layout
 - Revert "drm/radeon: Fix EEH during kexec" (regression in 5.3.5)
 - ocfs2: fix panic due to ocfs2_wq is null
 - nvme-pci: Set the prp2 correctly when using more than 4k page
 - ipv4: fix race condition between route lookup and invalidation
 - ipv4: Return -ENETUNREACH if we can't create route but saddr is valid
 - net: avoid potential infinite loop in tc_ctl_action()
 - [hppa,m68k] net: i82596: fix dma_alloc_attr for sni_82596
 - net: ipv6: fix listify ip6_rcv_finish in case of forwarding
 - [armhf,arm64] net: stmmac: disable/enable ptp_ref_clk in suspend/resume
   flow
 - rxrpc: Fix possible NULL pointer access in ICMP handling
 - sched: etf: Fix ordering of packets with same txtime
 - sctp: change sctp_prot .no_autobind with true
 - net: aquantia: temperature retrieval fix
 - net: aquantia: when cleaning hw cache it should be toggled
 - net: aquantia: do not pass lro session with invalid tcp checksum
 - net: aquantia: correctly handle macvlan and multicast coexistence
 - net: phy: micrel: Discern KSZ8051 and KSZ8795 PHYs
 - net: phy: micrel: Update KSZ87xx PHY name
 - net: avoid errors when trying to pop MLPS 

Bug#943422: marked as done (linux: 5.3.7 breaks soundcard)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942881: fixed in linux 5.3.9-1
has caused the Debian Bug report #942881,
regarding linux: 5.3.7 breaks soundcard
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.3.7-1
Severity: important


Hi.

Apparently changes from 5.2+107 -> 5.3.7-1 break sound completely.

As soon as I login to the desktop environment the following goes of:
Oct 24 18:33:10 heisenberg kernel: snd_hda_intel :00:1f.3: azx_get_response 
timeout, switching to polling mode: last cmd=0x20270503
Oct 24 18:33:11 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, disabling MSI: last cmd=0x20270503
Oct 24 18:33:12 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:13 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:14 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:16 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:17 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:18 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:20 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:21 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:22 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:24 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:25 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:26 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:28 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:29 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:30 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:32 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:33 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:34 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:36 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:37 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:38 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:40 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:41 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:42 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:44 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:45 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:46 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:48 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20270503
Oct 24 18:33:49 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x20370503
Oct 24 18:33:50 heisenberg kernel: snd_hda_intel :00:1f.3: No response from 
codec, resetting bus: last cmd=0x201f0500
Oct 24 18:33:51 heisenberg kernel: snd_hda_intel 

Bug#943953: marked as done (linux: DKMS module builds are failing on arm64 due to lack of armhf cross-compiler)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#943953: fixed in linux 5.3.9-1
has caused the Debian Bug report #943953,
regarding linux: DKMS module builds are failing on arm64 due to lack of armhf 
cross-compiler
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
943953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.3.7-1
Severity: normal
User: de...@kali.org
Usertags: origin-kali

https://salsa.debian.org/kernel-team/linux/commit/82c843e1577930c4eb168f626ab9bd483b118efc
seems to break DKMS on arm64:


root@pinebook-kali:/usr/src# dkms autoinstall

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
'make' -j4 ARCH=arm64 KVER=5.3.0-kali1-arm64 
KSRC=/lib/modules/5.3.0-kali1-arm64/build/...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.3.0-kali1-arm64 (aarch64)
Consult /var/lib/dkms/rtl8723cs/2019.07.31/build/make.log for more information.
root@pinebook-kali:/usr/src# cat 
/var/lib/dkms/rtl8723cs/2019.07.31/build/make.log 
DKMS make.log for rtl8723cs-2019.07.31 for kernel 5.3.0-kali1-arm64 (aarch64)
Fri Nov  1 03:50:50 CDT 2019
make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/5.3.0-kali1-arm64/build/ 
M=/var/lib/dkms/rtl8723cs/2019.07.31/build  modules
make[1]: Entering directory '/usr/src/linux-headers-5.3.0-kali1-arm64'
arch/arm64/Makefile:58: *** arm-linux-gnueabihf-gcc not found, check 
CROSS_COMPILE_COMPAT.  Stop.
make[1]: *** [/usr/src/linux-headers-5.3.0-kali1-common/Makefile:179: sub-make] 
Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.3.0-kali1-arm64'
make: *** [Makefile:1670: modules] Error 2


Some more information gathered on IRC:

16:51  Oh, we have the Depends right, so I think the check in 
arch/arm64/Makefile needs to be suppressed when building out-of-tree modules
16:54  bwh: what do you mean with "we have the Depends right" (i.e. with 
or without the cross-compiler)? on what package are you looking?
16:55  The Depends for the linux-headers package don't include an armhf 
compiler, which is correct
16:55  but the kernel build system still looks for it, which is not
16:55  There are some upstream changes around this that might fix it

Cheers,
 Raphaël.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.3.9-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 943...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop 

Bug#943545: marked as done (pulseaudio: audio completely broken)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942881: fixed in linux 5.3.9-1
has caused the Debian Bug report #942881,
regarding pulseaudio: audio completely broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pulseaudio
Version: 13.0-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I recently ran apt upgrade (on 2019-10-23). The last update before that was
about two weeks before. The sound was working fine before I ran the update.
After the update, sound will no longer play out of the laptop's integrated
speakers. When I plug in headphones, sound plays only on the left side, and
moving the volume slider in the mixer does not change the volume at all. I've
used pavucontrol to check that the speakers are recognized by the system and
aren't muted. I'm not sure what other information I can provide that can be
useful, but if you let me know I will be happy to provide it.

Thanks,
Mario Alegre



-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pulseaudio depends on:
ii  adduser  3.118
ii  init-system-helpers  1.57
ii  libasound2   1.1.8-2
ii  libasound2-plugins   1.1.8-1
ii  libc62.29-2
ii  libcap2  1:2.25-2
ii  libdbus-1-3  1.12.16-2
ii  libgcc1  1:9.2.1-12
ii  libice6  2:1.0.9-2
ii  libltdl7 2.4.6-11
ii  liborc-0.4-0 1:0.4.30-1
ii  libpulse013.0-3
ii  libsm6   2:1.2.3-1
ii  libsndfile1  1.0.28-6
ii  libsoxr0 0.1.3-2
ii  libspeexdsp1 1.2~rc1.2-1.1
ii  libstdc++6   9.2.1-12
ii  libsystemd0  242-7
ii  libtdb1  1.4.2-2
ii  libudev1 242-7
ii  libwebrtc-audio-processing1  0.3-1+b1
ii  libx11-6 2:1.6.8-1
ii  libx11-xcb1  2:1.6.8-1
ii  libxcb1  1.13.1-2
ii  libxtst6 2:1.2.3-1
ii  lsb-base 11.1.0
ii  pulseaudio-utils 13.0-3

Versions of packages pulseaudio recommends:
ii  dbus-user-session  1.12.16-2
ii  libpam-systemd 242-7
ii  rtkit  0.12-4

Versions of packages pulseaudio suggests:
pn  paman
pn  paprefs  
ii  pavucontrol  3.0-4
pn  pavumeter
ii  udev 242-7

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# 

Bug#943355: marked as done (audio broken)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942881: fixed in linux 5.3.9-1
has caused the Debian Bug report #942881,
regarding audio broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.3.7-1

I installed a weeks worth of updates to my Sid install yesterday and
having done so my audio output has been broken.

I'm not at all certain which package to target a bug report at, there
was nothing obvious to me in the set of updates, and it is still broken
even if rebooting into kernel v5.2 where it was fine previously, so
idk. I'm in the early stages of trying to research the dmesg entries
relating to it which seems to be suggesting some sort of config issue
created by an update... :/

dmesg:
[   18.011993] snd_hda_intel :00:1f.3: azx_get_response timeout,
switching to polling mode: last cmd=0x20270503
[   19.020034] snd_hda_intel :00:1f.3: No response from codec,
disabling MSI: last cmd=0x20270503
[   20.024002] snd_hda_intel :00:1f.3: No response from codec,
resetting bus: last cmd=0x20270503
...
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.3.9-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop condition in io_work
 - nvme-pci: Save PCI state before putting drive into deepest state
 - nvme: fix an error code in nvme_init_subsystem()
 - nvme-rdma: Fix max_hw_sectors calculation
 - nvme: Added QUIRKs for ADATA XPG SX8200 Pro 512GB
 - nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T
 - nvme-rdma: fix possible use-after-free in connect timeout
 - blk-mq: honor IO scheduler for multiqueue devices
 - xen/efi: Set nonblocking callbacks
 - loop: change queue block size to match when using DIO
 - nl80211: fix null pointer dereference
 - mac80211: fix txq null pointer dereference
 - netfilter: nft_connlimit: disable bh on garbage collection
 - [armhf,arm64] net: stmmac: xgmac: Not all Unicast addresses may be
   available
 - [armhf,arm64] net: stmmac: dwmac4: Always update the MAC Hash Filter
 - [armhf,arm64] net: stmmac: Correctly take timestamp for PTPv2
 - [armhf,arm64] net: stmmac: Do not stop PHY if WoL is enabled
 - drm/amdgpu: fix multiple memory leaks in acp_hw_init
 - drm/amd/display: memory leak
 - 

Bug#942886: marked as done (linux-image-5.3.0-1-amd64: Can not modprobe "snd_hda_codec_hdmi")

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942881: fixed in linux 5.3.9-1
has caused the Debian Bug report #942881,
regarding linux-image-5.3.0-1-amd64: Can not modprobe "snd_hda_codec_hdmi"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.3.7-1
Severity: important

Dear Maintainer,
 After upgrade kernel to linux-image-5.3.0-1-amd64, I can not
 modprobe "snd_hda_codec_hdmi" any more, it show the error message,
 modprobe: ERROR: could not insert 'snd_hda_codec_hdmi': Key was
 rejected by service
 and my monitor no sound output.
 Please help, thank you.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 5.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-1-amd64 root=/dev/mapper/nvme0n1p1_crypt ro 
rootflags=subvol=rootfs apparmor=1 security=apparmor nosmt rootfstype=btrfs 
rootflags=subvol=rootfs quiet

** Not tainted

** Kernel log:
[7.126154] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[7.127219] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: 
line_outs=0 (0x0/0x0/0x0/0x0/0x0) type:line
[7.127221] snd_hda_codec_generic hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[7.127222] snd_hda_codec_generic hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[7.127222] snd_hda_codec_generic hdaudioC0D0:mono: mono_out=0x0
[7.127223] snd_hda_codec_generic hdaudioC0D0:dig-out=0x3/0x0
[7.127223] snd_hda_codec_generic hdaudioC0D0:inputs:
[7.127667] input: HDA Intel HDMI HDMI as 
/devices/pci:00/:00:03.0/sound/card0/input17
[7.153862] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: 
(null)
[7.181175] Rounding down aligned max_sectors from 4294967295 to 4294967288
[7.181662] db_root: cannot open: /etc/target
[7.245336] Adding 1952764k swap on /dev/mapper/swap.  Priority:-2 extents:1 
across:1952764k SSFS
[7.279906] bcache: bch_journal_replay() journal replay done, 177 keys in 12 
entries, seq 6365286
[7.289114] bcache: bch_cached_dev_attach() Caching sda1 as bcache0 on set 
3ec1b954-b969-438d-b264-91a36d2a1a4c
[7.289136] bcache: register_cache() registered cache device dm-5
[7.298596] intel_rapl_common: Found RAPL domain package
[7.298598] intel_rapl_common: Found RAPL domain core
[7.298598] intel_rapl_common: Found RAPL domain uncore
[7.298599] intel_rapl_common: Found RAPL domain dram
[   11.171939] BTRFS: device fsid b6b55d64-9811-4f26-9d77-f5af7750193f devid 1 
transid 2690791 /dev/dm-8
[   11.189503] BTRFS info (device dm-8): enabling ssd optimizations
[   11.189504] BTRFS info (device dm-8): turning on discard
[   11.189507] BTRFS info (device dm-8): use lzo compression, level 0
[   11.189508] BTRFS info (device dm-8): disk space caching is enabled
[   11.189509] BTRFS info (device dm-8): has skinny extents
[   11.269858] audit: type=1400 audit(1571773003.787:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=949 
comm="apparmor_parser"
[   11.270455] audit: type=1400 audit(1571773003.787:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="transmission" pid=950 
comm="apparmor_parser"
[   11.270943] audit: type=1400 audit(1571773003.787:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/gpicview" pid=948 
comm="apparmor_parser"
[   11.272458] audit: type=1400 audit(1571773003.787:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="un-archiver" pid=951 
comm="apparmor_parser"
[   11.272475] audit: type=1400 audit(1571773003.787:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/wget" pid=952 
comm="apparmor_parser"
[   11.274990] audit: type=1400 audit(1571773003.791:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/xarchiver" 

Bug#942836: marked as done (snd_hda_intel: No response from codec, resetting bus)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942881: fixed in linux 5.3.9-1
has caused the Debian Bug report #942881,
regarding snd_hda_intel: No response from codec, resetting bus
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.3.7-1
Severity: important

Kernel log says "snd_hda_intel :00:1f.3: No response from codec, resetting
bus: last cmd=0x20270500"
Audio playback doesn't work, pavucontrol reports that headphone are plugged in
even though they aren't.

The bug didn't appear before and the audio works normal when booting with the
5.2 linux series.
I should note that I modified the audio pin layout with hda-jack-retask since
the default ones are wrong configured for my device.



-- Package-specific info:
** Version:
Linux version 5.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.3.0-1-amd64 
root=UUID=fec22bf6-9f85-428b-9b5b-42f5a32fc7a8 ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[   54.133040] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   55.135246] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x203f0900
[   56.145808] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   57.152492] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   58.186938] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   59.189824] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   60.192875] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   61.196058] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   62.231473] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   63.234740] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   64.250143] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   65.257679] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   66.293245] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   67.300879] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   68.312592] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   69.316259] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   70.348012] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   71.351717] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   72.359465] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   73.363309] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   74.395052] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   75.398807] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   76.402659] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   77.410462] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   78.450285] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   79.458079] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   80.469972] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   81.481813] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   82.517667] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   83.521569] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   84.525421] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   85.529298] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   86.561161] snd_hda_intel 

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

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#935945: fixed in linux 5.3.9-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 that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.2.9-2
Severity: important

Dear Maintainer,

I sign the kernel for UEFI secure boot with my own key and also do so for 
custom-build kernel modules such as "vboxdrv" for VirtualBox (package 
virtualbox-6.0). This worked without a flaw for linux-image-4.19.0-5-amd64, but 
this kernel version rejects the signature:

> sudo modprobe -v vboxdrv
insmod /lib/modules/5.2.0-2-amd64/misc/vboxdrv.ko
modprobe: ERROR: could not insert 'vboxdrv': Operation not permitted

In `dmesg` I see my key being loaded:

[1.609556] integrity: Loading X.509 certificate: UEFI:db
[1.609992] integrity: Loaded X.509 cert 'My kernel signing key: 
XX'

it also appears in `cat /proc/keys`, but is probably not trusted:

> sudo keyctl list "%:.builtin_trusted_keys"
2 keys in keyring:
813811236: ---lswrv 0 0 asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
915392374: ---lswrv 0 0 asymmetric: Debian Secure Boot Signer: 
00a7468def

I suspect this is due to kernel config CONFIG_SECONDARY_TRUSTED_KEYRING not 
being set:

> grep CONFIG_SECONDARY_TRUSTED_KEYRING /boot/config-5.2.0-2-amd64
# CONFIG_SECONDARY_TRUSTED_KEYRING is not set

whereas

> grep CONFIG_SECONDARY_TRUSTED_KEYRING /boot/config-4.19.0-5-amd64
CONFIG_SECONDARY_TRUSTED_KEYRING=y


Could you please also set this configuration value in this version?

Thank you very much.
Best regards,
Sven

-- Package-specific info:
** Version:
Linux version 5.2.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21)

** Command line:
resume=/dev/mapper/casaubon--vg-swap_1 root=/dev/mapper/casaubon--vg-root ro 
splash quiet loglevel=3 add_efi_memmap biosdevname=0 cgroup_enable=memory 
drm.vblankoffdelay=1 elevator=noop i915.enable_dc=2 i915.enable_fbc=1 
i915.fastboot=1 net.ifnames=0 rd.systemd.show_status=auto 
rd.udev.log_priority=3 swapaccount=1 vga=current vt.global_cursor_default=0 


** Tainted: U (64)
 * Userspace-defined naughtiness.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: Latitude 7480
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.6.5
board_vendor: Dell Inc.
board_name: 00F6D3
board_version: A00

** Loaded modules:
sha512_ssse3
sha512_generic
ipheth
xt_TPROXY
nf_tproxy_ipv6
nf_tproxy_ipv4
xt_tcpudp
xt_socket
nf_socket_ipv4
nf_socket_ipv6
nf_defrag_ipv6
nf_defrag_ipv4
xt_mark
nft_compat
nft_counter
nf_tables
nfnetlink
bnep
cdc_ether
usbnet
r8152
mii
snd_usb_audio
snd_usbmidi_lib
snd_rawmidi
snd_seq_device
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
videodev
media
zram
zsmalloc
btusb
btrtl
btbcm
btintel
bluetooth
drbg
ansi_cprng
binfmt_misc
ecdh_generic
ecc
nls_ascii
nls_cp437
vfat
fat
arc4
snd_hda_codec_hdmi
snd_soc_skl
snd_soc_skl_ipc
snd_soc_sst_ipc
snd_soc_sst_dsp
snd_hda_ext_core
intel_rapl
snd_soc_acpi_intel_match
snd_hda_codec_realtek
snd_soc_acpi
snd_hda_codec_generic
snd_soc_core
iwlmvm
x86_pkg_temp_thermal
intel_powerclamp
dell_rbtn
snd_compress
mac80211
coretemp
kvm_intel
snd_hda_intel
dell_laptop
snd_hda_codec
mei_wdt
ledtrig_audio
kvm
watchdog
irqbypass
iwlwifi
snd_hda_core
dell_smm_hwmon
snd_hwdep
intel_cstate
efi_pstore
snd_pcm
intel_uncore
dell_wmi
snd_timer
dell_smbios
dcdbas
serio_raw
intel_wmi_thunderbolt
efivars
intel_rapl_perf
cfg80211
wmi_bmof
dell_wmi_descriptor
snd
soundcore
rtsx_pci_ms
rfkill
joydev
memstick
sg
mei_me
intel_pch_thermal
mei
idma64
processor_thermal_device
intel_soc_dts_iosf
battery
pcc_cpufreq
ac
intel_hid
acpi_pad
sparse_keymap
evdev
int3403_thermal
int340x_thermal_zone
int3400_thermal
acpi_thermal_rel
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
hid_lenovo
usbhid
hid_alps
hid_generic
sd_mod
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
i2c_designware_platform
i2c_designware_core
i915
rtsx_pci_sdmmc
mmc_core
aesni_intel
i2c_algo_bit
aes_x86_64
e1000e
ahci
crypto_simd
cryptd

Bug#942881: marked as done (snd-hda-codec-hdmi signature corruption)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942881: fixed in linux 5.3.9-1
has caused the Debian Bug report #942881,
regarding snd-hda-codec-hdmi signature corruption
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.3.7-1
Severity: normal

After upgrading to linux-image-5.3.0-1-amd64, I get messages like those
seen in the log ("No response from codec, resetting bus" and "Unable to
sync register"), and eventually a WARN. The mixer doesn't show the audio
device at all.

This didn't happen with the previous kernel, namely:
Oct 21 21:04:28 s kernel: Linux version 5.2.0-3-amd64 
(debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-23)) #1 SMP 
Debian 5.2.17-1 (2019-10-06)

-- Package-specific info:
** Version:
Linux version 5.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-1-amd64 
root=UUID=121586a4-bf8c-49a4-9a72-ed70fcf72772 ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[   59.442968] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   60.448988] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   61.454722] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   62.460306] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   63.493654] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   64.498615] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   65.507773] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   66.516498] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   67.557305] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   68.569978] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   69.578573] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   70.587072] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   71.627548] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   72.635462] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   73.639361] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   74.651383] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   75.687274] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   76.691051] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   77.694902] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   78.702874] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   79.734778] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   80.738684] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   81.742564] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   82.746472] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   83.786414] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   84.798403] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   85.810293] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   86.822260] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   87.862207] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20170500
[   88.866163] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20270500
[   89.874103] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x20370500
[   90.885985] snd_hda_intel :00:1f.3: No response from codec, resetting 
bus: last cmd=0x201f0500
[   91.926013] snd_hda_intel :00:1f.3: No 

Bug#942823: marked as done (linux-image-5.3.0-1-amd64: Dell XPS 13 gets stuck on sddm login screen at boot)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942881: fixed in linux 5.3.9-1
has caused the Debian Bug report #942881,
regarding linux-image-5.3.0-1-amd64: Dell XPS 13 gets stuck on sddm login 
screen at boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.3.7-1
Severity: important

Dear Maintainer,

When booting this kernel image on my Dell XPS 13 laptop, the sddm login screen
comes up, and I can enter my password, but nothing happens when I hit return.

I switched to a virtual terminal, where I saw error messages like this:

Oct 21 21:10:26 vortex kernel: [8.810386] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270503
Oct 21 21:10:27 vortex kernel: [9.814405] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20370503
Oct 21 21:10:28 vortex kernel: [   10.818466] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x201f0500
Oct 21 21:10:29 vortex kernel: [   11.822460] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270d00
Oct 21 21:10:30 vortex kernel: [   12.830446] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270d00
Oct 21 21:10:32 vortex kernel: [   14.846233] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270503
Oct 21 21:10:33 vortex kernel: [   15.850222] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20370503
Oct 21 21:10:34 vortex kernel: [   16.862221] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x201f0500
Oct 21 21:10:36 vortex kernel: [   18.902451] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270503
Oct 21 21:10:37 vortex kernel: [   19.910446] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20370503
Oct 21 21:10:38 vortex kernel: [   20.914420] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x201f0500
Oct 21 21:10:41 vortex kernel: [   22.954258] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270503
Oct 21 21:10:42 vortex kernel: [   23.962414] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20370503
Oct 21 21:10:43 vortex kernel: [   24.970253] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x201f0500
Oct 21 21:10:45 vortex kernel: [   27.010253] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270503
Oct 21 21:10:46 vortex kernel: [   28.022444] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20370503
Oct 21 21:10:47 vortex kernel: [   29.034417] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x201f0500
Oct 21 21:10:49 vortex kernel: [   31.078240] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20270503
Oct 21 21:10:50 vortex kernel: [   32.086235] snd_hda_intel :00:1f.3: No
response from codec, resetting bus: last cmd=0x20370503


These messages continue as long as I care to wait. I had to reboot using the
previous kernel to use my computer again.



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: XPS 13 9360
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 2.3.1
board_vendor: Dell Inc.
board_name: 0PF86Y
board_version: A00

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 03)
Subsystem: Dell Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM 
Registers [1028:075b]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus Graphics 
640 [8086:5926] (rev 06) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Dell Iris Plus Graphics 640 [1028:075b]
Control: I/O+ Mem+ BusMaster+ 

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

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#935945: fixed in linux 5.3.9-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 you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.2.9-2
Severity: important

Dear Maintainer,

I've updated kernel from 4.19 to 5.2 and kernel stopped accepting modules
signed with MOK key.

I have secure boot enabled on my system and enrolled generated MOK key. I use
some out-of-tree modules that use DKMS. In the previous version of the kernel
I was signing those modules with the MOK key and they loaded just fine as MOK
key was loaded into the trusted keyring in the kernel.

After the kernel update, MOK key gets inserted into the .platform keyring
(I see CONFIG_INTEGRITY_PLATFORM_KEYRING is set to true in the kernel config)
which apparently isn't used for validation of module signatures so I'm unable
to load MOK signed modules.

I would expect this to still work as the only option I have right now for
using DKMS modules is building and using my own kernel image... This is also
the method described in https://wiki.debian.org/SecureBoot.

I've found this related bug in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1701096. There are some links to
upstream patches but I've just checked linux master and
kernel/module_signing.c is still using only secondary_trusted_keyring and
builtin_trusted_keyring to verify modules signatures.

Thank you,
Marek Rusinowski
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.3.9-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 935...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop condition in io_work
 - nvme-pci: Save PCI state before putting drive into deepest state
 - nvme: fix an error code in nvme_init_subsystem()
 - nvme-rdma: Fix max_hw_sectors calculation
 - nvme: Added QUIRKs for ADATA XPG SX8200 Pro 512GB
 - nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T
 - nvme-rdma: fix possible use-after-free in connect timeout
 - blk-mq: honor IO scheduler for multiqueue devices
 - xen/efi: Set nonblocking callbacks
 - loop: change queue block size to match when using DIO
 - nl80211: fix null pointer dereference
 - mac80211: fix txq null pointer dereference
 - 

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

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#935945: fixed in linux 5.3.9-1
has caused the Debian Bug report #935945,
regarding module loading fails with error: "Lockdown: modprobe: Loading of 
unsigned module is restricted; see https://wiki.debian.org/SecureBoot;
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.3.2-1~exp1
Severity: important

I can't figure out how to sign my kernel modules once I installed my MOK,
the doc in https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key didn't 
really help me out.

└[cochabamba] mokutil --test-key mok/MOK.cer
 22:41:13
mok/MOK.cer is already enrolled
└[cochabamba] sudo keyctl show -x %:.builtin_trusted_keys   
 22:41:37
Keyring
0x2d16579e ---lswrv  0 0  keyring: .builtin_trusted_keys
0x29b4e884 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
0x3681dcff ---lswrv  0 0   \_ asymmetric: Debian Secure Boot Signer: 
00a7468def
└[cochabamba] sudo keyctl show -x %:.platform   
 22:41:42
Keyring
0x1cbb137c ---lswrv  0 0  keyring: .platform
0x3d97fc8d ---lswrv  0 0   \_ asymmetric: Microsoft Windows Production 
PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53
0x04167078 ---lswrv  0 0   \_ asymmetric: Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1
0x3646f72f ---lswrv  0 0   \_ asymmetric: Canonical Ltd. Master 
Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63
0x02bb95ba ---lswrv  0 0   \_ asymmetric: Niv Sardi: 
8b6895ea20ac18cf58b558b8367eabd6400d021d
0x16f8c206 ---lswrv  0 0   \_ asymmetric: : 
6e4c5e40f58b7aad499ef717e69bc28d
0x1120e45f ---lswrv  0 0   \_ asymmetric: Microsoft Corporation UEFI CA 
2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4
└[cochabamba] sudo /usr/src/linux-headers-(uname -r)/scripts/sign-file sha256 
~/mok/MOK.key ~/mok/MOK.cer /lib/modules/(uname -r)/updates/dkms/wireguard.ko 
wireguard.ko
└[cochabamba] hexdump -C wireguard.ko |tail -24 
 22:44:22
00053be0  4e 69 76 20 53 61 72 64  69 02 14 4e 56 b2 8b 51  |Niv Sardi..NV..Q|
00053bf0  00 33 4c 28 86 cd 99 08  b6 c9 8a 6a bb f8 58 30  |.3L(...j..X0|
00053c00  0b 06 09 60 86 48 01 65  03 04 02 01 30 0d 06 09  |...`.H.e0...|
00053c10  2a 86 48 86 f7 0d 01 01  01 05 00 04 82 01 00 3e  |*.H>|
00053c20  5e 55 0d bc 7a 4f c5 0f  f8 05 bc f3 68 a3 88 3c  |^U..zO..h..<|
00053c30  8e 52 d7 15 b9 2e 0a 26  1d a0 0f 17 48 01 bd f5  |.R.&H...|
00053c40  f1 b8 f8 f0 01 c3 8f 07  c5 33 65 08 14 f5 a6 58  |.3eX|
00053c50  44 d5 78 c2 be bf f6 14  93 3b 13 56 76 0e 46 29  |D.x..;.Vv.F)|
00053c60  de 2c b2 21 e2 c0 8b aa  04 a0 86 42 5f fb 81 89  |.,.!...B_...|
00053c70  da ca d7 23 e4 ea 1a 7c  8f 9f b6 0b c0 58 ad 6f  |...#...|.X.o|
00053c80  4d ed f2 ed 54 5c ce f8  ff 99 f9 40 d3 6d 39 7a  |M...T\.@.m9z|
00053c90  db 73 e5 47 3f da 4c 03  d0 25 f9 03 19 ad 2e cd  |.s.G?.L..%..|
00053ca0  93 e5 c0 6b eb be 2e 38  2a 0e f4 9b 18 99 27 9d  |...k...8*.'.|
00053cb0  ca 92 d1 f9 5f b2 2d 50  19 1a 8a 4b 88 3d 39 f5  |_.-P...K.=9.|
00053cc0  b4 59 9f 3e 70 5f 43 09  01 91 20 bc 95 c9 88 fc  |.Y.>p_C... .|
00053cd0  96 32 f0 06 85 9c fb 26  3a f4 05 38 e0 b8 d0 9c  |.2.&:..8|
00053ce0  94 a9 f9 c2 40 49 a9 95  43 db e1 cc 51 36 30 92  |@I..C...Q60.|
00053cf0  1e 6e ee 31 ac f4 e1 83  4a 19 91 72 26 44 f4 30  |.n.1J..r|
00053d00  6c d5 79 c4 f8 22 70 8c  9a 56 e9 ab f8 70 a9 65  |l.y.."p..V...p.e|
00053d10  cf 2e a1 96 3a ce 3d 88  30 23 2f 9c f6 be 87 00  |:.=.0#/.|
00053d20  00 02 00 00 00 00 00 00  00 01 8f 7e 4d 6f 64 75  |...~Modu|
00053d30  6c 65 20 73 69 67 6e 61  74 75 72 65 20 61 70 70  |le signature app|
00053d40  65 6e 64 65 64 7e 0a  |ended~.|
00053d47
└[cochabamba] sudo insmod ./wireguard.ko
 22:44:25
insmod: ERROR: could not insert module ./wireguard.ko: Operation not permitted

this just get dmesg to output:
[   20.488940] Lockdown: modprobe: Loading of unsigned module is restricted; 
see https://wiki.debian.org/SecureBoot

-- Package-specific info:
** Version:
Linux version 5.3.0-trunk-amd64 (debian-kernel@lists.debian.org) 

Bug#942861: marked as done (linux-image-amd64: missing-copyright-file /usr/share/doc/linux-image-amd64/copyright)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#942861: fixed in linux 5.3.9-1
has caused the Debian Bug report #942861,
regarding linux-image-amd64: missing-copyright-file 
/usr/share/doc/linux-image-amd64/copyright
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.3.7-1
Severity: serious
Justification: Policy 12.5

adequate reports the file is missing, and is right. The directory is there,
but not a symbolic link and empty.

tglase@tglase-nb:~ $ ll -d /usr/share/doc/linux-image-amd64
drwxr-xr-x 2 root root 4096 Oct 22 15:50 /usr/share/doc/linux-image-amd64/
tglase@tglase-nb:~ $ ll  /usr/share/doc/linux-image-amd64
total 0


-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-5.3.0-1-amd64  5.3.7-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.3.9-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop condition in io_work
 - nvme-pci: Save PCI state before putting drive into deepest state
 - nvme: fix an error code in nvme_init_subsystem()
 - nvme-rdma: Fix max_hw_sectors calculation
 - nvme: Added QUIRKs for ADATA XPG SX8200 Pro 512GB
 - nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T
 - nvme-rdma: fix possible use-after-free in connect timeout
 - blk-mq: honor IO scheduler for multiqueue devices
 - xen/efi: Set nonblocking callbacks
 - loop: change queue block size to match when using DIO
 - nl80211: fix null pointer dereference
 - mac80211: fix txq null pointer dereference
 - netfilter: nft_connlimit: disable bh on garbage collection
 - [armhf,arm64] net: stmmac: xgmac: Not all Unicast addresses may be
   available
 - [armhf,arm64] net: stmmac: dwmac4: Always update the MAC Hash Filter
 - 

Bug#931341: marked as done (linux-image-4.19.0-5-cloud-amd64 does not have /dev/rtc, used by GCE images)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#931341: fixed in linux 5.3.9-1
has caused the Debian Bug report #931341,
regarding linux-image-4.19.0-5-cloud-amd64 does not have /dev/rtc, used by GCE 
images
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
931341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-4.19.0-5-cloud-amd64
Version: 4.19.37-5

Dear maintainer:

On a virtual machine running buster on Google Compute Engine, where
this kernel package is the default, I get the following messages:

google_clock_skew_daemon[1539]: hwclock: Cannot access the Hardware Clock via 
any known method.
google_clock_skew_daemon[1539]: hwclock: Use the --verbose option to see the 
details of our search for an access method.

Apparently this kernel does not have /dev/rtc and that's the reason
for the error message.

Installing linux-image-4.19.0-5-amd64 makes the error message to go away.

I infer that the -cloud images should perhaps include the /dev/rtc device(s)
for those images to really be a drop-in replacement for the "full"
images in cloud environments.

[ Not using any severity here, but I would expect this to be fixed in
  a point release of buster, please upgrade to important if required ].

Thanks.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.3.9-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 931...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop condition in io_work
 - nvme-pci: Save PCI state before putting drive into deepest state
 - nvme: fix an error code in nvme_init_subsystem()
 - nvme-rdma: Fix max_hw_sectors calculation
 - nvme: Added QUIRKs for ADATA XPG SX8200 Pro 512GB
 - nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T
 - nvme-rdma: fix possible use-after-free in connect timeout
 - blk-mq: honor IO scheduler for multiqueue devices
 - xen/efi: Set nonblocking callbacks
 - loop: change queue block size to match when using DIO
 - nl80211: fix null pointer dereference
 - mac80211: fix txq null pointer dereference
 - netfilter: nft_connlimit: disable bh on garbage collection
 - [armhf,arm64] net: stmmac: xgmac: Not all Unicast addresses may be
   available
 - [armhf,arm64] net: stmmac: dwmac4: Always update the MAC Hash Filter
 - [armhf,arm64] net: stmmac: Correctly take timestamp for PTPv2
 - [armhf,arm64] net: stmmac: Do not stop PHY 

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

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#935945: fixed in linux 5.3.9-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 means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.2.9-2
Severity: important

Dear Maintainer,

   * What led up to the situation?

I regularly update Debian Testing (bullseye) on multiple computers. Two days 
ago something broke when kernel update from 4.19 to 5.2 arrived. Could you 
please help me to troubleshoot it?

   * What exactly did you do (or not do) that was effective (or ineffective)?

On computer with UEFI but without enabled Secure Boot everything works just 
fine and I can load DKMS ZFS module with kernel 5.2.0-2-amd64. On a computer 
with secure boot enabled I can’t load ZFS kernel module that is signed using my 
own key that was enrolled into UEFI using "mokutil".

   * What was the outcome of this action?

as root:
# modprobe zfs
modprobe: ERROR: could not insert 'zfs': Operation not permitted

   * What outcome did you expect instead?

Load it as usually. I was able to reproduce the same issue on a different 
computer with Secure Boot and signed modules.

A few notes:

* It works (modules are loaded) after I boot back to linux-image-4.19.0-5-amd64 
(but this is not a solution)

* It works (modules are loaded) after I disable Secure Boot (but this is not a 
solution)

* I'm sure that the modules are signed. I tested using:

find /lib/modules -name '*.ko' -exec grep -FL '~Module signature appended~' {} 
\+

* I can check that the key was loaded from UEFI during boot

Boot log with `4.19.0-5-amd64`
---
Aug 26 20:34:54 bedik002 kernel: efi: EFI v2.50 by INSYDE Corp.
Aug 26 20:34:54 bedik002 kernel: efi:  ACPI 2.0=0x7fffd014  SMBIOS=0x7f0d9000  
SMBIOS 3.0=0x7f0d7000  ESRT=0x7f0d4158  MEMATTR=0x6f699018  
TPMEventLog=0x66e32018
Aug 26 20:34:54 bedik002 kernel: Kernel is locked down from EFI secure boot; 
see https://wiki.debian.org/SecureBoot
Aug 26 20:34:54 bedik002 kernel: ACPI: UEFI 0x7FFFC000 000236 (v01 
HPQOEM 8362 0001 HP   0004)
Aug 26 20:34:54 bedik002 kernel: ACPI: UEFI 0x7FFFB000 42 (v01 
HPQOEM 8362 0002 HP   0004)
Aug 26 20:34:54 bedik002 kernel: clocksource: refined-jiffies: mask: 0x 
max_cycles: 0x, max_idle_ns: 7645519600211568 ns
Aug 26 20:34:54 bedik002 kernel: pci :00:02.0: BAR 2: assigned to efifb
Aug 26 20:34:54 bedik002 kernel: Registered efivars operations
Aug 26 20:34:54 bedik002 kernel: Asymmetric key parser 'x509' registered
Aug 26 20:34:54 bedik002 kernel: efifb: probing for efifb
Aug 26 20:34:54 bedik002 kernel: efifb: framebuffer at 0x9000, using 8100k, 
total 8100k
Aug 26 20:34:54 bedik002 kernel: efifb: mode is 1920x1080x32, linelength=7680, 
pages=1
Aug 26 20:34:54 bedik002 kernel: efifb: scrolling: redraw
Aug 26 20:34:54 bedik002 kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Aug 26 20:34:54 bedik002 kernel: fb0: EFI VGA frame buffer device
Aug 26 20:34:54 bedik002 kernel: Loading compiled-in X.509 certificates
Aug 26 20:34:54 bedik002 kernel: Loaded X.509 cert 'Debian Secure Boot CA: 
6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1'
Aug 26 20:34:54 bedik002 kernel: Loaded X.509 cert 'Debian Secure Boot Signer: 
00a7468def'
Aug 26 20:34:54 bedik002 kernel: Loaded UEFI:db cert 'Microsoft Windows 
Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' linked to 
secondary sys keyring
Aug 26 20:34:54 bedik002 kernel: Loaded UEFI:db cert 'Microsoft Corporation 
UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' linked to secondary sys 
keyring
Aug 26 20:34:54 bedik002 kernel: Loaded UEFI:db cert 'Hewlett-Packard Company: 
HP UEFI Secure Boot 2013 DB key: 1d7cf2c2b92673f69c8ee1ec7063967ab9b62bec' 
linked to secondary sys keyring

my key:
Aug 26 20:34:54 bedik002 kernel: Loaded UEFI:MokListRT cert 'bedik002 module 
signing key: b1025ea690c4c8f9593b0a158045e72586a3c12f' linked to secondary sys 
keyring

Aug 26 20:34:54 bedik002 kernel: Loaded UEFI:MokListRT cert 'Debian Secure Boot 
CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' linked to secondary sys keyring
Aug 26 20:34:54 bedik002 kernel: fb: switching to inteldrmfb from EFI VGA
Aug 26 20:34:54 bedik002 kernel: EFI Variables Facility v0.08 2004-May-17
Aug 26 20:34:54 bedik002 

Bug#924705: marked as done (Please enable PKCS8_PRIVATE_KEY_PARSER)

[Debian Bug Tracking System]

Your message dated Sat, 09 Nov 2019 21:10:12 +
with message-id 
and subject line Bug#924705: fixed in linux 5.3.9-1
has caused the Debian Bug report #924705,
regarding Please enable PKCS8_PRIVATE_KEY_PARSER
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
924705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Severity: wishlist
thanks

It would be nice to add the PKCS8_PRIVATE_KEY_PARSER to the Debian
build. Currently, importing a private key is not possible, and
generates the error `add_key: Bad message` when a key is attempted to
be loaded.

Thanks for your hard work and maintenance of such an important package!
  Paul


-- 
:wq
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.3.9-1

We believe that the bug you reported is fixed in the latest version of
linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 924...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Nov 2019 15:42:49 +
Source: linux
Architecture: source
Version: 5.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 924705 931341 935945 942861 942881 943953
Changes:
 linux (5.3.9-1) unstable; urgency=medium
 .
   * New version hopefully closes: #942881
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
 - drm: Free the writeback_job when it with an empty fb
 - drm: Clear the fence pointer when writeback job signaled
 - [armhf] clk: ti: dra7: Fix mcasp8 clock bits
 - [armhf] dts: Fix wrong clocks for dra7 mcasp
 - nvme-pci: Fix a race in controller removal
 - scsi: ufs: skip shutdown if hba is not powered
 - scsi: megaraid: disable device when probe failed after enabled device
 - scsi: qla2xxx: Silence fwdump template message
 - scsi: qla2xxx: Fix unbound sleep in fcport delete path.
 - scsi: qla2xxx: Fix stale mem access on driver unload
 - scsi: qla2xxx: Fix N2N link reset
 - scsi: qla2xxx: Fix N2N link up fail
 - [armhf] dts: Fix gpio0 flags for am335x-icev2
 - [armhf] OMAP2+: Fix missing reset done flag for am3 and am43
 - [armhf] OMAP2+: Add missing LCDC midlemode for am335x
 - [armhf] OMAP2+: Fix warnings with broken omap2_set_init_voltage()
 - nvme-tcp: fix wrong stop condition in io_work
 - nvme-pci: Save PCI state before putting drive into deepest state
 - nvme: fix an error code in nvme_init_subsystem()
 - nvme-rdma: Fix max_hw_sectors calculation
 - nvme: Added QUIRKs for ADATA XPG SX8200 Pro 512GB
 - nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T
 - nvme-rdma: fix possible use-after-free in connect timeout
 - blk-mq: honor IO scheduler for multiqueue devices
 - xen/efi: Set nonblocking callbacks
 - loop: change queue block size to match when using DIO
 - nl80211: fix null pointer dereference
 - mac80211: fix txq null pointer dereference
 - netfilter: nft_connlimit: disable bh on garbage collection
 - [armhf,arm64] net: stmmac: xgmac: Not all Unicast addresses may be
   available
 - [armhf,arm64] net: stmmac: dwmac4: Always update the MAC Hash Filter
 - [armhf,arm64] net: stmmac: Correctly take timestamp for PTPv2
 - [armhf,arm64] net: stmmac: Do not stop PHY if WoL is enabled
 - drm/amdgpu: fix multiple memory leaks in acp_hw_init
 - drm/amd/display: memory leak
 - [mips*el/loongson-*] Fix the link time qualifier of 'serial_exit()'
 - [arm64] net: hisilicon: Fix usage of uninitialized variable in function
   mdio_sc_cfg_reg_write()
 - [armhf,arm64] net: stmmac: Avoid deadlock on suspend/resume
 - [s390x] mm: fix -Wunused-but-set-variable warnings
 - r8152: Set macpassthru in reset_resume callback
 - net: phy: allow for reset line to be tied to a sleepy GPIO controller
 - net: phy: fix write to mii-ctrl1000 register
 - vfs: 

linux_5.3.9-1_source.changes is NEW

[Debian FTP Masters]

binary:acpi-modules-5.3.0-2-686-di is NEW.
binary:acpi-modules-5.3.0-2-686-pae-di is NEW.
binary:acpi-modules-5.3.0-2-amd64-di is NEW.
binary:affs-modules-5.3.0-2-4kc-malta-di is NEW.
binary:affs-modules-5.3.0-2-5kc-malta-di is NEW.
binary:affs-modules-5.3.0-2-loongson-3-di is NEW.
binary:affs-modules-5.3.0-2-octeon-di is NEW.
binary:ata-modules-5.3.0-2-4kc-malta-di is NEW.
binary:ata-modules-5.3.0-2-5kc-malta-di is NEW.
binary:ata-modules-5.3.0-2-686-di is NEW.
binary:ata-modules-5.3.0-2-686-pae-di is NEW.
binary:ata-modules-5.3.0-2-amd64-di is NEW.
binary:ata-modules-5.3.0-2-arm64-di is NEW.
binary:ata-modules-5.3.0-2-armmp-di is NEW.
binary:ata-modules-5.3.0-2-loongson-3-di is NEW.
binary:ata-modules-5.3.0-2-powerpc64le-di is NEW.
binary:btrfs-modules-5.3.0-2-4kc-malta-di is NEW.
binary:btrfs-modules-5.3.0-2-5kc-malta-di is NEW.
binary:btrfs-modules-5.3.0-2-686-di is NEW.
binary:btrfs-modules-5.3.0-2-686-pae-di is NEW.
binary:btrfs-modules-5.3.0-2-amd64-di is NEW.
binary:btrfs-modules-5.3.0-2-arm64-di is NEW.
binary:btrfs-modules-5.3.0-2-armmp-di is NEW.
binary:btrfs-modules-5.3.0-2-loongson-3-di is NEW.
binary:btrfs-modules-5.3.0-2-marvell-di is NEW.
binary:btrfs-modules-5.3.0-2-octeon-di is NEW.
binary:btrfs-modules-5.3.0-2-powerpc64le-di is NEW.
binary:btrfs-modules-5.3.0-2-s390x-di is NEW.
binary:cdrom-core-modules-5.3.0-2-4kc-malta-di is NEW.
binary:cdrom-core-modules-5.3.0-2-5kc-malta-di is NEW.
binary:cdrom-core-modules-5.3.0-2-686-di is NEW.
binary:cdrom-core-modules-5.3.0-2-686-pae-di is NEW.
binary:cdrom-core-modules-5.3.0-2-amd64-di is NEW.
binary:cdrom-core-modules-5.3.0-2-arm64-di is NEW.
binary:cdrom-core-modules-5.3.0-2-armmp-di is NEW.
binary:cdrom-core-modules-5.3.0-2-loongson-3-di is NEW.
binary:cdrom-core-modules-5.3.0-2-marvell-di is NEW.
binary:cdrom-core-modules-5.3.0-2-octeon-di is NEW.
binary:cdrom-core-modules-5.3.0-2-powerpc64le-di is NEW.
binary:cdrom-core-modules-5.3.0-2-s390x-di is NEW.
binary:compress-modules-5.3.0-2-4kc-malta-di is NEW.
binary:compress-modules-5.3.0-2-5kc-malta-di is NEW.
binary:compress-modules-5.3.0-2-686-di is NEW.
binary:compress-modules-5.3.0-2-686-pae-di is NEW.
binary:compress-modules-5.3.0-2-amd64-di is NEW.
binary:compress-modules-5.3.0-2-arm64-di is NEW.
binary:compress-modules-5.3.0-2-armmp-di is NEW.
binary:compress-modules-5.3.0-2-loongson-3-di is NEW.
binary:compress-modules-5.3.0-2-marvell-di is NEW.
binary:compress-modules-5.3.0-2-octeon-di is NEW.
binary:compress-modules-5.3.0-2-powerpc64le-di is NEW.
binary:compress-modules-5.3.0-2-s390x-di is NEW.
binary:crc-modules-5.3.0-2-4kc-malta-di is NEW.
binary:crc-modules-5.3.0-2-5kc-malta-di is NEW.
binary:crc-modules-5.3.0-2-686-di is NEW.
binary:crc-modules-5.3.0-2-686-pae-di is NEW.
binary:crc-modules-5.3.0-2-amd64-di is NEW.
binary:crc-modules-5.3.0-2-arm64-di is NEW.
binary:crc-modules-5.3.0-2-armmp-di is NEW.
binary:crc-modules-5.3.0-2-loongson-3-di is NEW.
binary:crc-modules-5.3.0-2-marvell-di is NEW.
binary:crc-modules-5.3.0-2-octeon-di is NEW.
binary:crc-modules-5.3.0-2-powerpc64le-di is NEW.
binary:crc-modules-5.3.0-2-s390x-di is NEW.
binary:crypto-dm-modules-5.3.0-2-4kc-malta-di is NEW.
binary:crypto-dm-modules-5.3.0-2-5kc-malta-di is NEW.
binary:crypto-dm-modules-5.3.0-2-686-di is NEW.
binary:crypto-dm-modules-5.3.0-2-686-pae-di is NEW.
binary:crypto-dm-modules-5.3.0-2-amd64-di is NEW.
binary:crypto-dm-modules-5.3.0-2-arm64-di is NEW.
binary:crypto-dm-modules-5.3.0-2-armmp-di is NEW.
binary:crypto-dm-modules-5.3.0-2-loongson-3-di is NEW.
binary:crypto-dm-modules-5.3.0-2-marvell-di is NEW.
binary:crypto-dm-modules-5.3.0-2-octeon-di is NEW.
binary:crypto-dm-modules-5.3.0-2-powerpc64le-di is NEW.
binary:crypto-dm-modules-5.3.0-2-s390x-di is NEW.
binary:crypto-modules-5.3.0-2-4kc-malta-di is NEW.
binary:crypto-modules-5.3.0-2-5kc-malta-di is NEW.
binary:crypto-modules-5.3.0-2-686-di is NEW.
binary:crypto-modules-5.3.0-2-686-pae-di is NEW.
binary:crypto-modules-5.3.0-2-amd64-di is NEW.
binary:crypto-modules-5.3.0-2-arm64-di is NEW.
binary:crypto-modules-5.3.0-2-armmp-di is NEW.
binary:crypto-modules-5.3.0-2-loongson-3-di is NEW.
binary:crypto-modules-5.3.0-2-marvell-di is NEW.
binary:crypto-modules-5.3.0-2-octeon-di is NEW.
binary:crypto-modules-5.3.0-2-powerpc64le-di is NEW.
binary:crypto-modules-5.3.0-2-s390x-di is NEW.
binary:dasd-extra-modules-5.3.0-2-s390x-di is NEW.
binary:dasd-modules-5.3.0-2-s390x-di is NEW.
binary:efi-modules-5.3.0-2-686-di is NEW.
binary:efi-modules-5.3.0-2-686-pae-di is NEW.
binary:efi-modules-5.3.0-2-amd64-di is NEW.
binary:efi-modules-5.3.0-2-arm64-di is NEW.
binary:efi-modules-5.3.0-2-armmp-di is NEW.
binary:event-modules-5.3.0-2-4kc-malta-di is NEW.
binary:event-modules-5.3.0-2-5kc-malta-di is NEW.
binary:event-modules-5.3.0-2-686-di is NEW.
binary:event-modules-5.3.0-2-686-pae-di is NEW.
binary:event-modules-5.3.0-2-amd64-di is NEW.
binary:event-modules-5.3.0-2-arm64-di is NEW.
binary:event-modules-5.3.0-2-armmp-di is NEW.

Processing of linux_5.3.9-1_source.changes

[Debian FTP Masters]

linux_5.3.9-1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.3.9-1.dsc
  linux_5.3.9.orig.tar.xz
  linux_5.3.9-1.debian.tar.xz
  linux_5.3.9-1_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Bug#944420: Also tried 5.2.0

[Philipp Klaus Krause]

I also tried an older 5.2.0 kernel:

linux-image-5.2.0-3-amd64 5.2.17-1

The problem there is the same, but it seems I have a somewhat higher
chance to make it to XFCE (in which I still see graphical corruption)
than just getting a green screen (which I there see bit less than half
of the time).

Bug#944420: Wrong info

[Philipp Klaus Krause]

I see reportbug added a lot of information from the system on which I
submitted the bug report. Please disregard that; sorry for the noise.

Do you need any further information from the system on which I see the
bug that I should provide?

Bug#944420: linux-image-5.3.0-1-amd64: green screen in X

[Philipp Klaus Krause]

Package: src:linux
Version: 5.3.7-1
Severity: important

A few days ago, I installed Debian on a new Ryzen 3400G system (not the system
on which I write this report, hope reportbug doesn't add any invalid
information from the system on which I type this).

I see graphical problems in X. I am not sure if the bug is in the kernel or
elsewhere, but the kernel seemed the most likely candidate for the bug report
to me.

I have installed XFCE. After boot, I see the graphical login screen. After
login, most of the time, the screen turns a dark green (so I don't get to see
XFCE). Sometimes I do get to XFCE, but then there is graphical corruption.

Despite the screen going green (which seems permanent - switching to a console
won't help), I can still switch to a console and type blindly. That way I
obtained the dmesg output I put at http://www.colecovision.eu/stuff/dmesg-log

I have also tried with kernel options ioomu=off and iommu=pt init=nomwait, but
neither one helped. The same system seems stable on Windows 10, so I guess it
is not a hardware issue.

Some installed packages:

linux-image-amd64 5.3.7-1
firmware-amd-graphics 20190717-2
xserver-xorg-vieo-amdgpu 19.1.0-1



-- Package-specific info:
** Version:
Linux version 5.3.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191008 (Debian 9.2.1-9)) #1 SMP Debian 5.3.7-1 (2019-10-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-1-amd64 root=/dev/mapper/universum-root ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Notebook
product_name: N24_25BU
product_version: Not Applicable  
chassis_vendor: Notebook
chassis_version: N/A 
bios_vendor: American Megatrends Inc.
bios_version: 5.12
board_vendor: Notebook
board_name: N24_25BU
board_version: Not Applicable  

** Loaded modules:
loop
udf
crc_itu_t
nls_utf8
isofs
fuse
ufs
qnx4
hfsplus
hfs
minix
msdos
jfs
xfs
ti_usb_3410_5052
sr_mod
cdrom
uas
usb_storage
ctr
ccm
cmac
bnep
binfmt_misc
btusb
btrtl
btbcm
btintel
pl2303
usbserial
bluetooth
nls_ascii
nls_cp437
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
videodev
vfat
fat
mc
drbg
ansi_cprng
ext4
ecdh_generic
ecc
crc16
iwlmvm
mbcache
snd_soc_skl
intel_rapl_msr
jbd2
snd_soc_hdac_hda
intel_rapl_common
mac80211
snd_hda_ext_core
snd_soc_skl_ipc
snd_soc_sst_ipc
snd_soc_sst_dsp
snd_soc_acpi_intel_match
snd_hda_codec_realtek
x86_pkg_temp_thermal
intel_powerclamp
snd_hda_codec_generic
snd_soc_acpi
libarc4
coretemp
snd_soc_core
ledtrig_audio
snd_compress
kvm_intel
snd_hda_intel
iwlwifi
snd_hda_codec
snd_hda_core
kvm
snd_hwdep
cfg80211
irqbypass
snd_pcm
intel_cstate
efi_pstore
intel_uncore
snd_timer
joydev
iTCO_wdt
intel_rapl_perf
iTCO_vendor_support
serio_raw
pcspkr
mei_me
snd
rtsx_pci_ms
efivars
watchdog
soundcore
sg
memstick
tpm_crb
mei
rfkill
intel_pch_thermal
battery
tpm_tis
tpm_tis_core
tpm
evdev
acpi_pad
rng_core
ac
parport_pc
ppdev
lp
sunrpc
parport
efivarfs
ip_tables
x_tables
autofs4
btrfs
zstd_decompress
zstd_compress
dm_crypt
dm_mod
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
hid_generic
usbhid
hid
raid6_pq
libcrc32c
crc32c_generic
raid1
raid0
multipath
linear
md_mod
sd_mod
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
i915
nvme
rtsx_pci_sdmmc
mmc_core
ahci
i2c_algo_bit
aesni_intel
drm_kms_helper
libahci
xhci_pci
aes_x86_64
psmouse
crypto_simd
cryptd
glue_helper
nvme_core
xhci_hcd
drm
i2c_i801
rtsx_pci
libata
mfd_core
r8169
realtek
libphy
scsi_mod
usbcore
usb_common
wmi
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1558:2410]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer HD Graphics 620 [1558:2410]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: CLEVO/KAPOK Computer Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th Gen Core Processor Gaussian Mixture Model [1558:2410]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- 

Bug#880549: nfs-kernel-server: NFSv4 sec=krb5p option broken on stretch

[Dietrich Clauss]

Package: nfs-kernel-server
Followup-For: Bug #880549

This bug is still present in Buster.

It can be workarounded by using the mount option "vers=4.0".

NFS versions 4.2 (default in Buster), and 4.1 are affected by this bug.
Version 4.0 works fine.  Can anyone confirm this?


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfs-kernel-server depends on:
ii  keyutils  1.6-6
ii  libblkid1 2.33.1-0.1
ii  libc6 2.28-10
ii  libcap2   1:2.25-2
ii  libsqlite3-0  3.27.2-3
ii  libtirpc3 1.1.4-0.4
ii  libwrap0  7.6.q-28
ii  lsb-base  10.2019051400
ii  netbase   5.6
ii  nfs-common1:1.3.4-2.5
ii  ucf   3.0038+nmu1

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

Bug#884284: nfs4_reclaim_open_state: Lock reclaim failed

[Dietrich Clauss]

Package: nfs-kernel-server
Followup-For: Bug #884284

Duplicate of #880549?

-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nfs-kernel-server depends on:
ii  keyutils  1.6-6
ii  libblkid1 2.33.1-0.1
ii  libc6 2.28-10
ii  libcap2   1:2.25-2
ii  libsqlite3-0  3.27.2-3
ii  libtirpc3 1.1.4-0.4
ii  libwrap0  7.6.q-28
ii  lsb-base  10.2019051400
ii  netbase   5.6
ii  nfs-common1:1.3.4-2.5
ii  ucf   3.0038+nmu1

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

Bug#884284: nfs4_reclaim_open_state: Lock reclaim failed

[Dietrich Clauss]

Duplicate of #880549?

Bug#880549: nfs-kernel-server: NFSv4 sec=krb5p option broken on stretch

[Dietrich Clauss]

This bug is still present in Buster.

It can be workarounded by using the mount option "vers=4.0".

NFS versions 4.2 (default in Buster), and 4.1 are affected by this bug.
Version 4.0 works fine.  Can anyone confirm this?