date:20200417




Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux-signed-i386
Architecture: source
Version: 5.5.17+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Changes:
 linux-signed-i386 (5.5.17+1) unstable; urgency=medium
 .
   * Sign kernel from linux 5.5.17-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII loopback for MAC reset"
 - [arm64] net: bcmgenet: keep MAC in reset until PHY is up
 - bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
 - bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
 - bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
 - bnxt_en: Free context memory after disabling PCI in probe error path.
 - bnxt_en: Reset rings if ring reservation fails during open()
 - net: ena: fix incorrect setting of the number of msix vectors
 - net: ena: fix request of incorrect number of IRQ vectors
 - net: ena: avoid memory access violation by validating req_id properly
 - net: ena: fix continuous keep-alive resets
 - net: ip_gre: Separate ERSPAN newlink / changelink callbacks
 - net: ip_gre: Accept IFLA_INFO_DATA-less configuration
 - hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
 - hsr: add restart routine into hsr_get_node_list()
 - hsr: set .netnsok flag
 - net/mlx5: DR, Fix postsend actions write length
 - net/mlx5e: Enhance ICOSQ WQE info fields
 - net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
 - net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
 - net/mlx5e: Do not recover from a non-fatal syndrome
 - net/mlx5_core: Set IB capability mask1 to fix ib_srpt connection failure
 - net/mlx5e: kTLS, Fix TCP seq off-by-1 issue in TX resync flow
 - net/mlx5e: Fix endianness handling in pedit mask
 - cgroup-v1: cgroup_pidlist_next should update position index
 - nfs: add minor version to nfs_server_key for fscache
 - drivers/of/of_mdio.c:fix of_mdiobus_register()
 - cgroup1: don't call release_agent when it is ""
 - veth: ignore peer tx_dropped when counting local rx_dropped
 - drm/amd/display: update soc bb for nv14
 - drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
 - [armhf] drm/exynos: Fix cleanup of IOMMU related objects
 - [x86] iommu/vt-d: Silence RCU-list debugging warnings
 - scsi: ipr: Fix softlockup when rescanning devices in petitboot
 - mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
 - [x86] iommu/vt-d: Fix debugfs register reads
 - [x86] iommu/vt-d: Populate debugfs if IOMMUs are detected
 - Input: fix stale timestamp on key autorepeat events
 - [x86] Input: synaptics - enable RMI on HP Envy 13-ad105ng
 - Input: avoid BIT() macro usage in the serio.h UAPI header
 - IB/rdmavt: Free kernel

Bug#958065: linux: switch from linux-image-5.5.0-1-amd64-unsigned to linux-image-5.5.0-1-amd64 made modules being lost

Source: linux
Version: 5.5.17-1
Severity: important


Hi.

I've just switched from the linux-image-5.5.0-1-amd64-unsigned to 
linux-image-5.5.0-1-amd64
(which wasn't available as soon as the -unsigned version) in on go via apt.


The consequence was, that many modules were missing.


Looking at the apt/term.log:

Removing linux-image-5.5.0-1-amd64-unsigned
[then debconf asks whether I want to remove the running image]
Removing the running kernel
/etc/kernel/prerm.d/dkms:
dkms: removing: openafs 1.8.6pre1 (5.5.0-1-amd64) (x86_64)
[...]
depmod...

DKMS: uninstall completed.
[...]
Selecting previously unselected package linux-image-5.5.0-1-amd64.
Preparing to unpack .../linux-image-5.5.0-1-amd64_5.5.13-2_amd64.deb ...
Unpacking linux-image-5.5.0-1-amd64 (5.5.13-2) ...
Preparing to unpack .../linux-image-amd64_5.5.13-2_amd64.deb ...
Unpacking linux-image-amd64 (5.5.13-2) over (5.4.19-1) ...
[...]
Removing linux-image-5.4.0-4-amd64 (5.4.19-1) ...
/etc/kernel/prerm.d/dkms:
dkms: removing: openafs 1.8.6pre1 (5.4.0-4-amd64) (x86_64)
[...]
depmod...

DKMS: uninstall completed.
[...]
Setting up linux-image-5.5.0-1-amd64 (5.5.13-2) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.2.0-3-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.2.0-3-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-5.5.0-1-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.5.0-1-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.5.0-1-amd64:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.5.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.3.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module 
i915
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.5.0-1-amd64
Found initrd image: /boot/initrd.img-5.5.0-1-amd64
Found linux image: /boot/vmlinuz-5.2.0-3-amd64
Found initrd image: /boot/initrd.img-5.2.0-3-amd64
Configured General Secure System
Found memtest86+ image: /root/boot/memtest86+.bin
Found memtest86+ multiboot image: /root/boot/memtest86+_multiboot.bin
done
[...]
Setting up xtables-addons-dkms (3.9-1) ...
Loading new xtables-addons-3.9 DKMS files...
Building for 5.5.0-1-amd64
Building initial module for 5.5.0-1-amd64
Done.
[...]
depmod...

DKMS: install completed.
[...]


So far, so good...


Purging configuration files for linux-image-5.5.0-1-amd64-unsigned (5.5.13-2) 
...
I: /vmlinuz is now a symlink to boot/vmlinuz-5.2.0-3-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.2.0-3-amd64
rmdir: failed to remove '/lib/modules/5.5.0-1-amd64': Directory not empty
Purging configuration files for linux-image-5.4.0-4-amd64 (5.4.19-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.5.0-1-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-5.5.0-1-amd64
Processing triggers for tex-common (6.14) ...
[here apt ends after some further triggers]


Looking at the postrm:
if [ "$1" = purge ]; then
for extra_file in modules.dep modules.isapnpmap modules.pcimap \
  modules.usbmap modules.parportmap \
  modules.generic_string modules.ieee1394map \
  modules.ieee1394map modules.pnpbiosmap \
  modules.alias modules.ccwmap modules.inputmap \
  modules.symbols modules.ofmap \
  modules.seriomap modules.\*.bin \
  modules.softdep modules.devname; do
eval rm -f /lib/modules/$version/$extra_file
done
rmdir /lib/modules/$version || true
fi


It deletes all modules... which are however already belonging to the
signed version of the package.


Interestingly, and I don't quite understand this, not all modules were deleted.
Cause I spotted the failed rmdir right away and looked briefly at the dir
and modules were still there.

However, after reboot, e.g. iwlwifi was gone.

Processed: Re: Bug#822730: initramfs-tools: Should we migrate to a "interest-noawait" trigger for update-initramfs -u?

Processing control commands:

> reassign -1 debhelper
Bug #822730 {Done: Niels Thykier } [initramfs-tools] 
initramfs-tools: Should we migrate to a "interest-noawait" trigger for 
update-initramfs -u?
Bug reassigned from package 'initramfs-tools' to 'debhelper'.
No longer marked as found in versions initramfs-tools/0.125.
Ignoring request to alter fixed versions of bug #822730 to the same values 
previously set

-- 
822730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#822730: initramfs-tools: Should we migrate to a "interest-noawait" trigger for update-initramfs -u?

2020-04-17 Thread Niels Thykier

Control: reassign -1 debhelper

On Thu, 19 Jul 2018 02:03:21 +0100 Ben Hutchings 
wrote:
> On Sun, 2018-02-18 at 07:35 +, Niels Thykier wrote:
> > On Sun, 31 Dec 2017 16:29:00 + Niels Thykier  wrote:
> > > Control: block 491027 by -1
> > > 
> > > On Sun, 09 Jul 2017 12:51:00 + Niels Thykier  
> > > wrote:
> > > > On Tue, 26 Apr 2016 22:10:14 +0200 Niels Thykier  
> > > > wrote:
> > > > > Package: initramfs-tools
> > > > > Version: 0.125
> > > > > Severity: wishlist
> > > > > Usertags: declarative-packaging 
> > > > > 
> > > > > Hi,
> > > > > 
> > > > 
> > > > [...]
> > > 
> > > Ping on this?
> > > 
> > 
> > Hi,
> > 
> > I have been pinging this bug for nearly two years (admittedly with quite
> > some time between some of the pings) without any replies.
> > 
> > @Ben: Given you appear to be the one doing the actual uploads (i.e. sign
> > + upload), could I ask you to review the bug and come with your take on
> > this?
> 
> I finally had a look at this while preparing a new version.  Sorry for
> taking so long, but I hope you understand that wishlist bugs asking a
> question are not a high priority.
> 
> The dpkg documentation isn't clear (#904060), but it appears to me that
> if we use "interest-noawait" then an activating package that really
> needs to await will not be able to do so.  If we carry on using
> "interest" (or "interest-await") then the activating package can choose
> whether to await the trigger or not.
> 
> A search for explicit triggers:
> https://codesearch.debian.net/search?q=activate.*update-initramfs
> shows that there are packages that use "activate-await", and I would
> not want to override that without consultation.
> 
> Ben.
> 
> -- 
> Ben Hutchings
> We get into the habit of living before acquiring the habit of thinking.
>  - Albert Camus

Processed: Re: Bug#822730: initramfs-tools: Should we migrate to a "interest-noawait" trigger for update-initramfs -u?

Processing commands for cont...@bugs.debian.org:

> unarchive 822730
Bug #822730 {Done: Niels Thykier } [initramfs-tools] 
initramfs-tools: Should we migrate to a "interest-noawait" trigger for 
update-initramfs -u?
Unarchived Bug 822730
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
822730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#958037: linux-image-arm64: Please add CONFIG_CRYPTO_DEV_SUN8I_CE

2020-04-17 Thread Philip Rinn

Hm,

according to to this commit[1] (which is part of Linux 5.5) it should actually 
be
build as a module per default. But in my /boot/config-5.5.0-1-arm64 I have

CONFIG_CRYPTO_DEV_ALLWINNER=y
# CONFIG_CRYPTO_DEV_SUN4I_SS is not set
# CONFIG_CRYPTO_DEV_SUN8I_CE is not set
# CONFIG_CRYPTO_DEV_SUN8I_SS is not set

Best,
Philip

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2fabf6dd77014f19d45fc71c01f1b073c03df255

linux-signed-i386_5.5.17+1_source.changes is NEW

Mapping sid to unstable.
binary:linux-image-5.5.0-2-686 is NEW.
binary:linux-image-5.5.0-2-686-pae is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
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-i386_5.5.17+1_source.changes

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

Greetings,

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

linux-signed-arm64_5.5.17+1_source.changes ACCEPTED into unstable, unstable




Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux-signed-arm64
Architecture: source
Version: 5.5.17+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Changes:
 linux-signed-arm64 (5.5.17+1) unstable; urgency=medium
 .
   * Sign kernel from linux 5.5.17-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII loopback for MAC reset"
 - [arm64] net: bcmgenet: keep MAC in reset until PHY is up
 - bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
 - bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
 - bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
 - bnxt_en: Free context memory after disabling PCI in probe error path.
 - bnxt_en: Reset rings if ring reservation fails during open()
 - net: ena: fix incorrect setting of the number of msix vectors
 - net: ena: fix request of incorrect number of IRQ vectors
 - net: ena: avoid memory access violation by validating req_id properly
 - net: ena: fix continuous keep-alive resets
 - net: ip_gre: Separate ERSPAN newlink / changelink callbacks
 - net: ip_gre: Accept IFLA_INFO_DATA-less configuration
 - hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
 - hsr: add restart routine into hsr_get_node_list()
 - hsr: set .netnsok flag
 - net/mlx5: DR, Fix postsend actions write length
 - net/mlx5e: Enhance ICOSQ WQE info fields
 - net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
 - net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
 - net/mlx5e: Do not recover from a non-fatal syndrome
 - net/mlx5_core: Set IB capability mask1 to fix ib_srpt connection failure
 - net/mlx5e: kTLS, Fix TCP seq off-by-1 issue in TX resync flow
 - net/mlx5e: Fix endianness handling in pedit mask
 - cgroup-v1: cgroup_pidlist_next should update position index
 - nfs: add minor version to nfs_server_key for fscache
 - drivers/of/of_mdio.c:fix of_mdiobus_register()
 - cgroup1: don't call release_agent when it is ""
 - veth: ignore peer tx_dropped when counting local rx_dropped
 - drm/amd/display: update soc bb for nv14
 - drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
 - [armhf] drm/exynos: Fix cleanup of IOMMU related objects
 - [x86] iommu/vt-d: Silence RCU-list debugging warnings
 - scsi: ipr: Fix softlockup when rescanning devices in petitboot
 - mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
 - [x86] iommu/vt-d: Fix debugfs register reads
 - [x86] iommu/vt-d: Populate debugfs if IOMMUs are detected
 - Input: fix stale timestamp on key autorepeat events
 - [x86] Input: synaptics - enable RMI on HP Envy 13-ad105ng
 - Input: avoid BIT() macro usage in the serio.h UAPI header
 - IB/rdmavt: Free kernel

linux-signed-amd64_5.5.17+1_source.changes ACCEPTED into unstable, unstable




Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Apr 2020 03:37:48 +0100
Source: linux-signed-amd64
Architecture: source
Version: 5.5.17+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Changes:
 linux-signed-amd64 (5.5.17+1) unstable; urgency=medium
 .
   * Sign kernel from linux 5.5.17-1
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.5.14
 - mmc: core: Allow host controllers to require R1B for CMD6
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for erase/trim/discard
 - mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for eMMC sleep command
 - [armhf] mmc: sdhci-omap: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - [armhf,arm64] mmc: sdhci-tegra: Fix busy detection by enabling
   MMC_CAP_NEED_RSP_BUSY
 - cxgb4: fix throughput drop during Tx backpressure
 - cxgb4: fix Txq restart check during backpressure
 - geneve: move debug check after netdev unregister
 - hsr: fix general protection fault in hsr_addr_is_self()
 - ipv4: fix a RCU-list lock in inet_dump_fib()
 - macsec: restrict to ethernet devices
 - net/bpfilter: fix dprintf usage for /dev/kmsg
 - net: cbs: Fix software cbs to consider packet sending time
 - [armhf,arm64] net: dsa: Fix duplicate frames flooded by learning
 - net: ena: Add PCI shutdown handler to allow safe kexec
 - [armhf] net: mvneta: Fix the case where the last poll did not process all
   rx
 - net/packet: tpacket_rcv: avoid a producer race condition
 - net: phy: dp83867: w/a for fld detect threshold bootstrapping issue
 - [armhf,arm64] net: phy: mdio-bcm-unimac: Fix clock handling
 - net: qmi_wwan: add support for ASKEY WWHC050
 - net/sched: act_ct: Fix leak of ct zone template on replace
 - net_sched: cls_route: remove the right filter from hashtable
 - net_sched: hold rtnl lock in tcindex_partial_destroy_work()
 - net_sched: keep alloc_hash updated after hash allocation
 - [armhf,arm64] net: stmmac: dwmac-rk: fix error path in rk_gmac_probe
 - r8169: re-enable MSI on RTL8168c
 - slcan: not call free_netdev before rtnl_unlock in slcan_open
 - tcp: also NULL skb->dev when copy was needed
 - tcp: ensure skb->dev is NULL before leaving TCP stack
 - tcp: repair: fix TCP_QUEUE_SEQ implementation
 - vxlan: check return value of gro_cells_init()
 - [arm64] Revert "net: bcmgenet: use RGMII loopback for MAC reset"
 - [arm64] net: bcmgenet: keep MAC in reset until PHY is up
 - bnxt_en: Fix Priority Bytes and Packets counters in ethtool -S.
 - bnxt_en: fix memory leaks in bnxt_dcbnl_ieee_getets()
 - bnxt_en: Return error if bnxt_alloc_ctx_mem() fails.
 - bnxt_en: Free context memory after disabling PCI in probe error path.
 - bnxt_en: Reset rings if ring reservation fails during open()
 - net: ena: fix incorrect setting of the number of msix vectors
 - net: ena: fix request of incorrect number of IRQ vectors
 - net: ena: avoid memory access violation by validating req_id properly
 - net: ena: fix continuous keep-alive resets
 - net: ip_gre: Separate ERSPAN newlink / changelink callbacks
 - net: ip_gre: Accept IFLA_INFO_DATA-less configuration
 - hsr: use rcu_read_lock() in hsr_get_node_{list/status}()
 - hsr: add restart routine into hsr_get_node_list()
 - hsr: set .netnsok flag
 - net/mlx5: DR, Fix postsend actions write length
 - net/mlx5e: Enhance ICOSQ WQE info fields
 - net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset
 - net/mlx5e: Fix ICOSQ recovery flow with Striding RQ
 - net/mlx5e: Do not recover from a non-fatal syndrome
 - net/mlx5_core: Set IB capability mask1 to fix ib_srpt connection failure
 - net/mlx5e: kTLS, Fix TCP seq off-by-1 issue in TX resync flow
 - net/mlx5e: Fix endianness handling in pedit mask
 - cgroup-v1: cgroup_pidlist_next should update position index
 - nfs: add minor version to nfs_server_key for fscache
 - drivers/of/of_mdio.c:fix of_mdiobus_register()
 - cgroup1: don't call release_agent when it is ""
 - veth: ignore peer tx_dropped when counting local rx_dropped
 - drm/amd/display: update soc bb for nv14
 - drm/amdgpu: correct ROM_INDEX/DATA offset for VEGA20
 - [armhf] drm/exynos: Fix cleanup of IOMMU related objects
 - [x86] iommu/vt-d: Silence RCU-list debugging warnings
 - scsi: ipr: Fix softlockup when rescanning devices in petitboot
 - mac80211: Do not send mesh HWMP PREQ if HWMP is disabled
 - [x86] iommu/vt-d: Fix debugfs register reads
 - [x86] iommu/vt-d: Populate debugfs if IOMMUs are detected
 - Input: fix stale timestamp on key autorepeat events
 - [x86] Input: synaptics - enable RMI on HP Envy 13-ad105ng
 - Input: avoid BIT() macro usage in the serio.h UAPI header
 - IB/rdmavt: Free kernel

linux-signed-arm64_5.5.17+1_source.changes is NEW

Mapping sid to unstable.
binary:linux-image-5.5.0-2-arm64 is NEW.
binary:linux-image-5.5.0-2-cloud-arm64 is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so 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-arm64_5.5.17+1_source.changes

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

Greetings,

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

Bug#931930: Workaround ? [Re: firmware-misc-nonfree: Please, include i915/icl_dmc_ver1_07.bin]

2020-04-17 Thread mlnl

Hi,

> I follow testing, and I have the same problem :
> 
> charpent@zen-book-flip:~/Kernel-SOS/firmware-nonfree-20190717/i915$
> dpkg -l "*firmware*" | grep ii| sed -re "s/[ \t]+/ /g" | cut -d " " -f
> 2 | xargs sudo apt-get install --reinstall -y
> 
> [ Snip... ]
> 
> Traitement des actions différées (« triggers ») pour initramfs-tools
> (0.136) ...
> update-initramfs: Generating /boot/initrd.img-5.5.0-1-amd64
> W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin
> for module i915

> Does someone has a woraround ? The Debian source package doesn't have
> the right version of the files.

Download latest archive from

and add missing files in /lib/firmware/i915


-- 
mlnl

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

Mapping sid to unstable.
binary:linux-image-5.5.0-2-amd64 is NEW.
binary:linux-image-5.5.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.5.17+1_source.changes

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

Greetings,

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

Processed: your mail

Processing commands for cont...@bugs.debian.org:

> forwarded 945055 https://bugzilla.kernel.org/show_bug.cgi?id=207245
Bug #945055 [linux] great CPU temperature increase from 5.2 to 5.5 ... and when 
using intel_pstate
Changed Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=207245' from 
'https://gitlab.freedesktop.org/drm/intel/issues/614'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
945055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#945055: great CPU temperature increase from 5.2 to 5.5 ... and when using intel_pstate

Control: tags -1 - patch
Control: notfound -1 3.16.81-1
Control: notfound -1 4.19.87-1
Control: notfound -1 5.4-1~exp1
Control: forwarded -1
https://bugzilla.kernel.org/show_bug.cgi?id=207245

Hey Ben.

On Fri, 2020-04-17 at 18:02 +0100, Ben Hutchings wrote:
> This is now neither "fixed" nor "found" in any 5.5 version. Please
> update the versions properly.

Took a while till I got the mail that the bug was unarchived so I
didn't update everything immediately.

> This is also tagged "patch" but without a direct link to the
> patch(es)
> that are supposed to fix it. (Linking to the upstream bug report is
> not specific enough.)

Sorry for the confusion I might have caused. The patch tag and also
found-in-version was based on my guess that the problems I see since
versions > 5.2 were caused by
https://gitlab.freedesktop.org/drm/intel/issues/614

That bug was a regression introduced by a security fix that prevented
the GPU from entering RC6 sleep states.

perf showed me that I was affected by it, so I assumed the fix (which
was introduced in 5.5rc-something) would solve everything.

It didn't, as my fruther test series, which I've just sent to this
Debian as well, showed.

Even with 5.5 I see a tremendous temperature increase.

Unfortunately I'm by far not an expert enough to really tell where the
problem comes from (I'd say there may be even different problems
involved)... and I'd also need guiding what to actually test, to better
nail it down.

When I saw the problem still occurs with 5.5, I've made another test
series and reported it first at lkml:
https://lore.kernel.org/lkml/ce8097694ddfab616616f8f81521495d99c74416.ca...@scientia.net/T/#u

When I got no response I've updated my older ticket at intel-drm:
https://gitlab.freedesktop.org/drm/intel/-/issues/953

My tests would indicate that there are a number of temperature
problems, in short:

- GPU intensive stuff (like playing videos)
- GPU stuff which shouldn't be intensive at all (e.g. moving around
windows)

but also:
- supposedly non-GPU intensive stuff like Alt-Tab-ing between windows,
scrolling up/down in lists in the GUI)
- stuff which doesn't even do graphics at all (see the unhide-brute and
(SHA)-verify tests I've made.

For the GPU-intensive stuff (specifically that I hit 100°C when I play
any videos) there is:
https://gitlab.freedesktop.org/drm/intel/issues/956
(intel-drm folks had asked me to put it in a separate issue)

For the general stuff (e.g. unhide brute or SHA512 verification running
much hotter), there is:
- the post to lkml
- https://bugzilla.kernel.org/show_bug.cgi?id=207245
- and since intel_pstate being enabled there's also:
https://bugzilla.kernel.org/show_bug.cgi?id=207247

The different tickets contain also descriptions of symptoms I've see,
e.g. where temperatures go through the roof even when just moving
windows, Alt-Tab-switching between them, scrolling up/down in a window,
and so on.

See especially the plots in the git repo I've provided, which shows how
much higher the temperature is from 5.2 to 5.5 (and for each of them
for intel_pstate being on or off).

Any help on what to test would be highly appreciated.

I did some preliminary tests with perf record, while then e.g.
scrolling up/down in a GUI window (used the mail list in Evolution)
while the temperatures go up to ~80°C ...
This would have indicated that during that, the number of events as
recorded by perf record, grows by a magnitude.

I haven't had time yet to make more systematic tests.

Thanks,
Chris.

Processed (with 1 error): Re: great CPU temperature increase from 5.2 to 5.5 ... and when using intel_pstate

Processing control commands:

> tags -1 - patch
Bug #945055 [linux] great CPU temperature increase from 5.2 to 5.5 ... and when 
using intel_pstate
Removed tag(s) patch.
> notfound -1 3.16.81-1
Bug #945055 [linux] great CPU temperature increase from 5.2 to 5.5 ... and when 
using intel_pstate
There is no source info for the package 'linux' at version '3.16.81-1' with 
architecture ''
Unable to make a source version for version '3.16.81-1'
No longer marked as found in versions 3.16.81-1.
> notfound -1 4.19.87-1
Bug #945055 [linux] great CPU temperature increase from 5.2 to 5.5 ... and when 
using intel_pstate
There is no source info for the package 'linux' at version '4.19.87-1' with 
architecture ''
Unable to make a source version for version '4.19.87-1'
No longer marked as found in versions 4.19.87-1.
> notfound -1 5.4-1~exp1
Bug #945055 [linux] great CPU temperature increase from 5.2 to 5.5 ... and when 
using intel_pstate
There is no source info for the package 'linux' at version '5.4-1~exp1' with 
architecture ''
Unable to make a source version for version '5.4-1~exp1'
No longer marked as found in versions 5.4-1~exp1.
> forwarded -1
Unknown command or malformed arguments to command.


-- 
945055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#945055: great CPU temperature increase from 5.2 to 5.5 ... and when using intel_pstate

I've made some further very extensive tests in the meantime, but these
were mostly for clearly GPU related stuff, i.e. the problem that the
temperatures go through the roof when playing back any video.
These were reported here:
https://gitlab.freedesktop.org/drm/intel/-/issues/953#note_463451

But I haven't made any plots/conclusions for that new set of tests, yet
(will keep this ticket updated once I've done).



As for the general (I mean even when doing non-graphics intensive stuff
like the unhide-brute or sha512 sum verify tests that I've described
above) extreme temperature increase since >5.2 that I see, ... what I
would try next is whether
mitigations=off changes anything (it didn't for video playback).


Also I found out about the nice features of perf record respectively
perf report.
I've played a bit with that already and the first "results" showed that
when I do anyting (like just typing at the keyboard, quickly moving
up/down in e.g. Evolutions mail list, or just Alt-Tab-ing between
windows, the number of events recorded there increases by
magnitudes(!!).


I'd be thankful for any guide in what to actually test to better nail
down that problem I see.

Thanks!

Bug#945055: great CPU temperature increase from 5.2 to 5.5 ... and when using intel_pstate

Hey.


For several months now, I've been chasing a tremendous heat increase
(CPU/GPU) respectively power usage on my notebook.

It basically started after upgrading from 5.2 to 5.3, at least I
haven't explicitly noted any grave changes from before 5.2 to 5.2.
The issue (actually there might be several) persists until at least 5.4
and 5.5.

Things are so bad, that when just type this mail,... that I can hear
the fan go up considerably (and temps up to 90°C) just by typing the
mail in the mail client (while it goes back to - still insane - 65°C
idle, when not typing... ok idle here(!) is with firefox running).
Similar things when I scroll through a terminal window, Alt-Tab cycle
between windows, and so on.


Testing is a bit difficult for me, as I couldn't come up with an easy
way to reproducibly generate real world load (like this typing, or
scrolling terminal windows), yet I tried to do an extensive test
series, which I think will illustrate some things.


Not really sure what the normal average or idle temps of that CPU are,
but I guess getting at average >80°C by just typing shouldn't be the
case.




1) Previous tests
*
When first searching for the reason of the temperature increase, I've
had opened several tickets:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055
https://lore.kernel.org/lkml/d05aba2742ae42783788c954e2a380e7fcb10830.ca...@scientia.net/

Finally to find (by coincidence):
https://gitlab.freedesktop.org/drm/intel/issues/614
when reporting:
https://gitlab.freedesktop.org/drm/intel/-/issues/953
myself.

At first I thought #614 would be the bug, but the fix for that went
into 5.5-rc, and in fact, with 5.5.x I do see the GPU entering RC6
sleep states again, yet the temperature of my system is still crazy.




2) Testing Environment
**
(for these new tests here)
- Fujitsu Lifebook U757
- most recent BIOS version (1.25) in the tests below (I've had used an
  older one in previous tests from the links)
- 32GB memory, some Sandisk SSD
- Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz
- microcode: sig=0x806e9, pf=0x80, revision=0xca
- Debian sid, all packages (unless some totally unrelated stuff at
  their newest versions in unstable)
- all used kernels are stock kernels from Debian
- I do use full dm-crypt encryption of the system, but that shouldn't
  be a cause for the problems, I guess.
- in my /etc/sysfs.conf I have:
  devices/system/cpu/intel_pstate/no_turbo = 1
  basically since I have that laptop... with turbo enabled I always
got 
  these:
  Apr  5 18:27:07 heisenberg kernel: [ 9884.510420] mce: CPU3: Package
temperature above threshold, cpu clock throttled (total events = 2609)
  Apr  5 18:27:07 heisenberg kernel: [ 9884.510422] mce: CPU1: Package
temperature above threshold, cpu clock throttled (total events = 2609)
  Apr  5 18:27:07 heisenberg kernel: [ 9884.510465] mce: CPU0: Package
temperature above threshold, cpu clock throttled (total events = 2609)
  Apr  5 18:27:07 heisenberg kernel: [ 9884.510467] mce: CPU2: Package
temperature above threshold, cpu clock throttled (total events = 2609)
  Apr  5 18:27:07 heisenberg kernel: [ 9884.511427] mce: CPU3: Package
temperature/speed normal
  Apr  5 18:27:07 heisenberg kernel: [ 9884.511430] mce: CPU0: Package
temperature/speed normal
  Apr  5 18:27:07 heisenberg kernel: [ 9884.511431] mce: CPU1: Package
temperature/speed normal
  Apr  5 18:27:07 heisenberg kernel: [ 9884.511436] mce: CPU2: Package
temperature/speed normal
  => so for the tests with ipntel_pstate not being disabled, turbo mode
 was always disabled




3) How tests were made
**
I've tested with the following combinations:
- kernels 5.2.17 and 5.5.13
- with and without intel_pstate=disable
- with Cinnamon and GNOME Shell in classic mode

For all tests the notebook was placed in the same position and ran with
the same commands for tests, no other major processes (like firefox or
so) were running, just the respective bare desktop environment
(cinnamon or gnome shell classic), cron/anacron were stopped.

I always took temperature measurements with the output from sensors and
CSV output from powertop (which contains all the sleep states and high
energy users).

Temperature and powertop measurements were started at basically the
same time. powertop running for n iterations each 20s.
But since powertop takes a while to start the temperature measurements
are effectively shorter.


a) deep-idle
For these tests I've waited very long (like 5 minutes or more) for the
system to cool down.
Measurements with, e.g.:
export NAME="5.2.17/ipstate-disable/thermald-no/gnome-shell-
classic/deep-idle" ; timeout 80 sh -c "while true; do sleep 1; sensors;
done | grep °C > ${NAME}.temp"
and
export NAME="5.2.17/ipstate-disable/thermald-no/cinnamon/deep-idle" ;
powertop -i 4  --csv=${NAME}.powertop.csv


b) idle
Basically the same as (a), just not waiting so long to cool down.
Effectively I've always produced some load (with the fan and CPU

linux_5.6.4-1~exp1_source.changes ACCEPTED into experimental, experimental




Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 17 Apr 2020 01:26:42 +0100
Source: linux
Architecture: source
Version: 5.6.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 956197
Changes:
 linux (5.6.4-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_5.6
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.1
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.2
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.3
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.4
 .
   [ Ben Hutchings ]
   * Set ABI to trunk
   * [mips*] Revert "staging: octeon-usb: delete the octeon usb host controller
 driver"
   * [mips*] Revert "staging: octeon: delete driver"
   * [powerpc*] i2c: Enable I2C_PARPORT instead of I2C_PARPORT_LIGHT
   * aufs: Update support patchset to aufs5.x-rcN 20200302; no functional
 change
   * linux-signed-*: Build-Depend on kernel-wedge 2.102 for consistency
   * aufs: Update support patchset to aufs5.6 20200413; no functional change
   * [rt] Update to 5.6.4-rt3 and re-enable
 .
   [ Aurelien Jarno ]
   * Enable SENSORS_DRIVETEMP
   * [riscv64] Enable SOC_VIRT
   * [riscv64] Enable GPIOLIB, GPIO_SIFIVE, POWER_RESET, POWER_RESET_GPIO,
 POWER_RESET_GPIO_RESTART, POWER_RESET_RESTART, CONFIG_PWM,
 CONFIG_PWM_SIFIVE, CONFIG_SIFIVE_L2
 .
   [ Christian Barcenas ]
   * linux-kbuild: Stop building conmakehash
   * linux-cpupower: Add libcap to Build-Depends and turbostat linker flags
   * [x86] Drop EFI cold boot mitigation patch in favor of upstream
   * [amd64] Update "x86: Make x32 syscall support conditional ..." for 5.6
 .
   [ Romain Perier ]
   * [x86] udeb: Add crc32_pclmul to crc-modules
   * udeb: Add crc32_generic to crc-modules
 .
   [ Luca Boccassi ]
   * lockdown: set default (with Secure Boot) to LOCKDOWN_INTEGRITY_MAX
 (Closes: #956197)
Checksums-Sha1:
 10b616f453a2924d48c365eddfbdc5a75d95b74d 210002 linux_5.6.4-1~exp1.dsc
 08fa53d17013fb81f710e285c439c25359a8b55d 116064736 linux_5.6.4.orig.tar.xz
 7557a0504381a497566cc5c3f334a88bcf73a489 1287880 
linux_5.6.4-1~exp1.debian.tar.xz
 9f6893a7826ccb7a57df63553f9d3505b9b177b8 53956 
linux_5.6.4-1~exp1_source.buildinfo
Checksums-Sha256:
 285decd6b401f74ce3a8d692e04c8dc58566fd66d08581ceb02b20de94bd7882 210002 
linux_5.6.4-1~exp1.dsc
 8115ac68648eeb0abc43f64405b488a070ed8dcaa4e0973d06971b204c829b5d 116064736 
linux_5.6.4.orig.tar.xz
 1cc26859937147739c92e92edd924334af209bc5477cc477c6044407da361e05 1287880 
linux_5.6.4-1~exp1.debian.tar.xz
 4bd4f6721bea5e47a8b6dec8bfa333afd8b2680154b66c1ec0aa262f4740e3b4 53956 
linux_5.6.4-1~exp1_source.buildinfo
Files:
 5c2b784e5b125647ede0f2080b31b6ab 210002 kernel optional linux_5.6.4-1~exp1.dsc
 3a098777e7f6ebbc7c833b3d9e3e994c 116064736 kernel optional 
linux_5.6.4.orig.tar.xz
 17f681b54f3e7a7f0ee54e3e23884c6c 1287880 kernel optional 
linux_5.6.4-1~exp1.debian.tar.xz
 13ab023261e0e035c82468ec51784e41 53956 kernel optional 
linux_5.6.4-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl6ZtuMACgkQ57/I7JWG
EQlAYQ/+Nxtk18NIT/rgPH4MuzY4jw4MA5XzWtG49nKjRg7Fr+fYqkEI8m833qoQ
5PFF2qEKIy8Dx/l54FUau60vSzKt8By1BtMMe8pW0pKkB8w4ezSJPmomiDl11LVI
8bcq6nZ5bZ9mqYY/hfN4EW9zCm+5fXG2OBVSyqAvXviMFILzl1dyNuN3fdyZe6O6
uVeEt0/sUCznMjDazHtZGpMswfqWjS2iTInZh6NvTATRShssEzCqbXI5hsmSECeV
ybMiLpvGa8o/OUKilc9eXFj+30KcLpcefPo2VsMgNpxP2qb7AeAxjzjfdNRBM+5K
3wSNwwnLnZWCEfIFP8wnq8yRG7tLKnqVaRLzm4Af9eIVrqO7VqIYt0aazz1wOsMR
2t6gI2Lquxcslrfgnonc++c+CqnOQHpRWKkYS5P4sYwlrxQdNTdWlLwxWbf/jYVD
b4iGOTDdampnI/gZImDuw8z8Fvz/4P0Mf0DmmR5MYez46bmqY12jooMZVHYuu8xt
OBul/c8uzgkJAxPEoMMBdlG6qJ4knRYVjVDApPqzQ9aTpyFHj2jtSvQnItGweYy5
A8iAEAL0zAxcPKtAmQ1xO2pDllD95C2ip4OyFjHwF34Gv6Kc378hTFRtwMy0cJoY
C1+0n8VOP+Gytzyf61zSkX8o+InuxGaHBfYeoDqY2z7ZNEMHxM0=
=KLBz
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#956197: marked as done (src:linux: lockdown: set default (with Secure Boot) to LOCKDOWN_INTEGRITY_MAX)

Your message dated Fri, 17 Apr 2020 18:01:01 +
with message-id 
and subject line Bug#956197: fixed in linux 5.6.4-1~exp1
has caused the Debian Bug report #956197,
regarding src:linux: lockdown: set default (with Secure Boot) to 
LOCKDOWN_INTEGRITY_MAX
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.)


-- 
956197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.5.13-2
Severity: wishlist
Tags: patch
X-Debbugs-CC: quen...@isovalent.com

Dear Maintainer(s),

LOCKDOWN_CONFIDENTIALITY_MAX restricts a lot of useful features,
even security ones (like monitoring via BPF), while not adding
that much value for common use cases.
Recently, Ubuntu, RedHat and SUSE changed the default to
LOCKDOWN_INTEGRITY_MAX.

I believe we should do the same.

MR: https://salsa.debian.org/kernel-team/linux/-/merge_requests/230

References:

https://github.com/iovisor/bcc/issues/2565#issuecomment-606566675
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868626
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?id=ef7c6600bb3e
https://bugzilla.redhat.com/show_bug.cgi?id=1815571

Thanks!

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.6.4-1~exp1
Done: Ben Hutchings 

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 956...@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: Fri, 17 Apr 2020 01:26:42 +0100
Source: linux
Architecture: source
Version: 5.6.4-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Closes: 956197
Changes:
 linux (5.6.4-1~exp1) experimental; urgency=medium
 .
   * New upstream release: https://kernelnewbies.org/Linux_5.6
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.1
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.2
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.3
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.6.4
 .
   [ Ben Hutchings ]
   * Set ABI to trunk
   * [mips*] Revert "staging: octeon-usb: delete the octeon usb host controller
 driver"
   * [mips*] Revert "staging: octeon: delete driver"
   * [powerpc*] i2c: Enable I2C_PARPORT instead of I2C_PARPORT_LIGHT
   * aufs: Update support patchset to aufs5.x-rcN 20200302; no functional
 change
   * linux-signed-*: Build-Depend on kernel-wedge 2.102 for consistency
   * aufs: Update support patchset to aufs5.6 20200413; no functional change
   * [rt] Update to 5.6.4-rt3 and re-enable
 .
   [ Aurelien Jarno ]
   * Enable SENSORS_DRIVETEMP
   * [riscv64] Enable SOC_VIRT
   * [riscv64] Enable GPIOLIB, GPIO_SIFIVE, POWER_RESET, POWER_RESET_GPIO,
 POWER_RESET_GPIO_RESTART, POWER_RESET_RESTART, CONFIG_PWM,
 CONFIG_PWM_SIFIVE, CONFIG_SIFIVE_L2
 .
   [ Christian Barcenas ]
   * linux-kbuild: Stop building conmakehash
   * linux-cpupower: Add libcap to Build-Depends and turbostat linker flags
   * [x86] Drop EFI cold boot mitigation patch in favor of upstream
   * [amd64] Update "x86: Make x32 syscall support conditional ..." for 5.6
 .
   [ Romain Perier ]
   * [x86] udeb: Add crc32_pclmul to crc-modules
   * udeb: Add crc32_generic to crc-modules
 .
   [ Luca Boccassi ]
   * lockdown: set default (with Secure Boot) to LOCKDOWN_INTEGRITY_MAX
 (Closes: #956197)
Checksums-Sha1:
 10b616f453a2924d48c365eddfbdc5a75d95b74d 210002 linux_5.6.4-1~exp1.dsc
 08fa53d17013fb81f710e285c439c25359a8b55d 116064736 linux_5.6.4.orig.tar.xz
 7557a0504381a497566cc5c3f334a88bcf73a489 1287880 
linux_5.6.4-1~exp1.debian.tar.xz
 9f6893a7826ccb7a57df63553f9d3505b9b177b8 53956 
linux_5.6.4-1~exp1_source.buildinfo
Checksums-Sha256:
 285decd6b401f74ce3a8d692e04c8dc58566fd66d08581ceb02b20de94bd7882 210002

Bug#958041: linux-image-5.5.0-1-amd64: OLED brightness control not working on Lenovo P1G2 and X1 extreme

2020-04-17 Thread Mark Pearson

Package: src:linux
Version: 5.5.13-2
Severity: normal
Tags: upstream

Dear Maintainer,

Raising bug for tracking issue with OLED brightness control not working on some
Lenovo platforms (and I believe some Dell platforms too)
The patches are upstream here:
https://patchwork.freedesktop.org/series/69914/
https://patchwork.freedesktop.org/series/72991/

and I'm working on a merge request to bring them into Debian:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/231

I was told a bug was preferred so am raising this for tracking.

Let me know if any questions or concerns.
Mark Pearson
mpear...@lenovo.com



-- Package-specific info:
** Version:
Linux version 5.5.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-8)) #1 SMP Debian 5.5.13-2 (2020-03-30)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.5.0-1-amd64 
root=UUID=fa0b3088-7fd9-47a8-9306-8cd2d4c0d3a6 ro quiet

** Not tainted

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

** Model information
sys_vendor: LENOVO
product_name: 20QUZ4QSUS
product_version: ThinkPad P1 Gen 2
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N2OET41W (1.28 )
board_vendor: LENOVO
board_name: 20QUZ4QSUS
board_version: SDK0Q40104 WIN

** Loaded modules:
sd_mod
sg
uas
usb_storage
scsi_mod
fuse
x86_pkg_temp_thermal
intel_powerclamp
coretemp
bnep
kvm_intel
kvm
irqbypass
crct10dif_pclmul
ghash_clmulni_intel
aesni_intel
crypto_simd
cryptd
snd_hda_codec_hdmi
glue_helper
mei_wdt
intel_cstate
intel_rapl_msr
intel_uncore
intel_rapl_perf
efi_pstore
serio_raw
intel_wmi_thunderbolt
wmi_bmof
snd_sof_pci
snd_sof_intel_hda_common
snd_sof_intel_hda
efivars
pcspkr
snd_sof_intel_byt
snd_sof_intel_ipc
snd_sof
iTCO_wdt
snd_sof_xtensa_dsp
iTCO_vendor_support
watchdog
snd_soc_skl
iwlwifi
snd_hda_codec_conexant
snd_soc_hdac_hda
snd_hda_codec_generic
snd_hda_ext_core
snd_soc_sst_ipc
snd_soc_sst_dsp
snd_soc_acpi_intel_match
snd_soc_acpi
snd_soc_core
btusb
nls_ascii
btrtl
snd_compress
btbcm
nls_cp437
btintel
snd_hda_intel
vfat
snd_intel_dspcfg
bluetooth
fat
uvcvideo
cfg80211
videobuf2_vmalloc
tpm_crb
mei_me
videobuf2_memops
videobuf2_v4l2
mei
snd_hda_codec
videobuf2_common
snd_hda_core
videodev
drbg
thinkpad_acpi
snd_hwdep
snd_pcm
nvram
mc
ansi_cprng
processor_thermal_device
snd_timer
tpm_tis
ledtrig_audio
intel_rapl_common
tpm_tis_core
ucsi_acpi
snd
ecdh_generic
ecc
typec_ucsi
tpm
joydev
rfkill
soundcore
intel_soc_dts_iosf
intel_pch_thermal
typec
rng_core
ac
int3403_thermal
int340x_thermal_zone
int3400_thermal
acpi_pad
evdev
acpi_thermal_rel
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
wacom
hid_generic
usbhid
hid
i915
rtsx_pci_sdmmc
mmc_core
i2c_designware_platform
i2c_designware_core
e1000e
i2c_algo_bit
psmouse
crc32_pclmul
drm_kms_helper
crc32c_intel
xhci_pci
ptp
xhci_hcd
pps_core
drm
usbcore
nvme
thunderbolt
nvme_core
rtsx_pci
i2c_i801
intel_lpss_pci
intel_lpss
idma64
usb_common
mfd_core
wmi
battery
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host 
Bridge/DRAM Registers [8086:3ec4] (rev 0d)
Subsystem: Lenovo 8th Gen Core Processor Host Bridge/DRAM Registers 
[17aa:22a8]
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:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen 
Core Processor PCIe Controller (x16) [8086:1901] (rev 0d) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 630 
(Mobile) [8086:3e9b] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:22a8]
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:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0d)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem [17aa:22a8]
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: proc_thermal
Kernel modules: processor_thermal_device

Processed: tagging 945055

Processing commands for cont...@bugs.debian.org:

> tags 945055 + moreinfo
Bug #945055 [linux] great CPU temperature increase from 5.2 to 5.5 ... and when 
using intel_pstate
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
945055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#945055:

2020-04-17 Thread Ben Hutchings

On Fri, 17 Apr 2020 17:49:35 +0200 Christoph Anton Mitterer 
 wrote:
> unarchive 945055
> reopen 945055
> retitle 945055 great CPU temperature increase from 5.2 to 5.5 ... and when 
> using intel_pstate

This is now neither "fixed" nor "found" in any 5.5 version.  Please
update the versions properly.

This is also tagged "patch" but without a direct link to the patch(es)
that are supposed to fix it.  (Linking to the upstream bug report is
not specific enough.)

Ben.

-- 
Ben Hutchings
The program is absolutely right; therefore, the computer must be wrong.

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

Bug#958037: linux-image-arm64: Please add CONFIG_CRYPTO_DEV_SUN8I_CE

2020-04-17 Thread Philip Rinn

Source: linux
Version: 5.5.13-2
Severity: wishlist

Hi,

the Crypto engine for Allwinner sun8i was recently added to the kernel[1].
Could you please enable it?

Adding a "CRYPTO_DEV_SUN8I_CE=m" should do the trick.

Thanks & happy hacking
Philip


[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=06f751b613296cc34b86fc83fccaf30d646eb8bc



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (600, 'testing'), (550, 'unstable'), (450, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.5.0-1-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

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org:

> found 951771 linux/5.5.17-1
Bug #951771 [src:linux] linux-source-5.4: linux 5.4.0-4 does not boot on this pc
Marked as found in versions linux/5.5.17-1.
> bye
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
951771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

Processing commands for cont...@bugs.debian.org:

> unarchive 945055
Bug #945055 {Done: Christoph Anton Mitterer } [linux] 
linux: CPU runs at considerably higher temperatures
Unarchived Bug 945055
> reopen 945055
Bug #945055 {Done: Christoph Anton Mitterer } [linux] 
linux: CPU runs at considerably higher temperatures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 5.5~rc5-1~exp1.
> retitle 945055 great CPU temperature increase from 5.2 to 5.5 ... and when 
> using intel_pstate
Bug #945055 [linux] linux: CPU runs at considerably higher temperatures
Changed Bug title to 'great CPU temperature increase from 5.2 to 5.5 ... and 
when using intel_pstate' from 'linux: CPU runs at considerably higher 
temperatures'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
945055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#931930: Workaround ? [Re: firmware-misc-nonfree: Please, include i915/icl_dmc_ver1_07.bin]

2020-04-17 Thread emanuel . charpentier

I follow testing, and I have the same problem :

charpent@zen-book-flip:~/Kernel-SOS/firmware-nonfree-20190717/i915$
dpkg -l "*firmware*" | grep ii| sed -re "s/[ \t]+/ /g" | cut -d " " -f
2 | xargs sudo apt-get install --reinstall -y

[ Snip... ]

Traitement des actions différées (« triggers ») pour initramfs-tools
(0.136) ...
update-initramfs: Generating /boot/initrd.img-5.5.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.3.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for
module i915

Does someone has a woraround ? The Debian source package doesn't have
the right version of the files.

BTW, do the maintainer(s) have acknowledged the problem ?

--
Emmanuel Charpentier

linux_5.6.4-1~exp1_source.changes is NEW

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

Processing of linux_5.6.4-1~exp1_source.changes

linux_5.6.4-1~exp1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.6.4-1~exp1.dsc
  linux_5.6.4.orig.tar.xz
  linux_5.6.4-1~exp1.debian.tar.xz
  linux_5.6.4-1~exp1_source.buildinfo

Greetings,

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

Bug#948576: closed by Debian FTP Masters (reply to Ben Hutchings ) (Bug#948576: fixed in linux 5.5.17-1)

2020-04-17 Thread Josua Mayer

Thanks! \o/

Am 17.04.20 um 05:03 schrieb Debian Bug Tracking System:
> This is an automatic notification regarding your Bug report
> which was filed against the src:linux package:
> 
> #948576: linux: please enable support for the layerscape SoCs and the 
> Honeycomb workstation board
> 
> It has been closed by Debian FTP Masters  
> (reply to Ben Hutchings ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Ben Hutchings ) 
> by
> replying to this email.
> 
>

Bug#957608: nfs-utils: ftbfs with GCC-10

2020-04-17 Thread Matthias Klose

Package: src:nfs-utils
Version: 1:1.3.4-2.5
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/nfs-utils_1.3.4-2.5_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
   51 |  dtable_ent(mount_dump,1,void,mountlist), /* DUMP */
  |  ^~
../../support/include/rpcmisc.h:41:3: warning: cast between incompatible 
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR 
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
   41 |   (xdrproc_t)xdr_##res_type, sizeof(res_type), \
  |   ^
mount_dispatch.c:52:2: note: in expansion of macro ‘dtable_ent’
   52 |  dtable_ent(mount_umnt,1,dirpath,void),  /* UMNT */
  |  ^~
../../support/include/rpcmisc.h:40:3: warning: cast between incompatible 
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR 
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
   40 |   (xdrproc_t)xdr_##arg_type, sizeof(arg_type), \
  |   ^
mount_dispatch.c:53:2: note: in expansion of macro ‘dtable_ent’
   53 |  dtable_ent(mount_umntall,1,void,void),  /* UMNTALL */
  |  ^~
../../support/include/rpcmisc.h:41:3: warning: cast between incompatible 
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR 
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
   41 |   (xdrproc_t)xdr_##res_type, sizeof(res_type), \
  |   ^
mount_dispatch.c:53:2: note: in expansion of macro ‘dtable_ent’
   53 |  dtable_ent(mount_umntall,1,void,void),  /* UMNTALL */
  |  ^~
../../support/include/rpcmisc.h:40:3: warning: cast between incompatible 
function types from ‘bool_t (*)(void)’ {aka ‘int (*)(void)’} to ‘bool_t (*)(XDR 
*, ...)’ {aka ‘int (*)(struct __rpc_xdr *, ...)’} [-Wcast-function-type]
   40 |   (xdrproc_t)xdr_##arg_type, sizeof(arg_type), \
  |   ^
mount_dispatch.c:54:2: note: in expansion of macro ‘dtable_ent’
   54 |  dtable_ent(mount_export,1,void,exports), /* EXPORT */
  |  ^~
gcc -DHAVE_CONFIG_H -I. -I../../support/include  -I/usr/include/tirpc 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/include 
-I../../support/export -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wall 
-Wextra -Wstrict-prototypes  -pipe -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\" 
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -c -o mountd-cache.o `test -f 
'cache.c' || echo './'`cache.c
gcc -DHAVE_CONFIG_H -I. -I../../support/include  -I/usr/include/tirpc 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/include 
-I../../support/export -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wall 
-Wextra -Wstrict-prototypes  -pipe -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\" 
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -c -o mountd-svc_run.o `test -f 
'svc_run.c' || echo './'`svc_run.c
gcc -DHAVE_CONFIG_H -I. -I../../support/include  -I/usr/include/tirpc 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/include 
-I../../support/export -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wall 
-Wextra -Wstrict-prototypes  -pipe -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\" 
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -c -o mountd-fsloc.o `test -f 
'fsloc.c' || echo './'`fsloc.c
gcc -DHAVE_CONFIG_H -I. -I../../support/include  -I/usr/include/tirpc 
-Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I../../support/include 
-I../../support/export -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -Wall 
-Wextra -Wstrict-prototypes  -pipe -g -Wall -DPIPEFS_DIR=\"/run/rpc_pipefs\" 
-DGSSD_PIPEFS_DIR=\"/run/rpc_pipefs\" -O2 -c -o mountd-v4root.o `test -f 
'v4root.c' || echo './'`v4root.c
In file included from /usr/include/string.h:495,
 from ../../support/include/exportfs.h:13,
 from v4root.c:25:
In function ‘strncpy’,
inlined from ‘v4root_create’ at v4root.c:95:2:

Bug#957491: linux: ftbfs with GCC-10

2020-04-17 Thread Matthias Klose

Package: src:linux
Version: 5.4.19-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/linux_5.4.19-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
  gcc 
-Wp,-MD,/<>/debian/build/build-tools/tools/perf/util/.probe-finder.o.d
 
-Wp,-MT,/<>/debian/build/build-tools/tools/perf/util/probe-finder.o
 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdate-time -D_FORTIFY_SOURCE=2 -I/<>/tools/perf 
-I/<>/debian/build/build-tools/tools/perf -isystem 
/<>/debian/build/build-tools/include -Wbad-function-cast 
-Wdeclaration-after-statement -Wformat-security -Wformat-y2k -Winit-self 
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs 
-Wno-system-headers -Wold-style-definition -Wpacked -Wredundant-decls 
-Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wwrite-strings 
-Wformat -Wstrict-aliasing=3 -Wshadow -DHAVE_ARCH_X86_64_SUPPORT 
-I/<>/debian/build/build-tools/tools/perf/arch/x86/include/generated
 -DHAVE_SYSCALL_TABLE_SUPPORT -DHAVE_PERF_REGS_SUPPORT 
-DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -O6 -fno-omit-frame-pointer -ggdb3 -funwi
 nd-tables -Wall -Wextra -std=gnu99 -fstack-protector-all -D_FORTIFY_SOURCE=2 
-I/<>/tools/perf/lib/include 
-I/<>/tools/perf/util/include 
-I/<>/tools/perf/arch/x86/include 
-I/<>/tools/include/ 
-I/<>/tools/arch/x86/include/uapi 
-I/<>/tools/include/uapi 
-I/<>/tools/arch/x86/include/ -I/<>/tools/arch/x86/ 
-I/<>/debian/build/build-tools/tools/perf//util 
-I/<>/debian/build/build-tools/tools/perf/ 
-I/<>/tools/perf/util -I/<>/tools/perf 
-I/<>/tools/lib/ -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
-D_GNU_SOURCE -DHAVE_SYNC_COMPARE_AND_SWAP_SUPPORT 
-DHAVE_PTHREAD_ATTR_SETAFFINITY_NP -DHAVE_PTHREAD_BARRIER -DHAVE_EVENTFD 
-DHAVE_GET_CURRENT_DIR_NAME -DHAVE_DWARF_GETLOCATIONS_SUPPORT 
-DHAVE_GLIBC_SUPPORT -DHAVE_AIO_SUPPORT -DHAVE_SCHED_GETCPU_SUPPORT 
-DHAVE_SETNS_SUPPORT -DHAVE_CSTRACE_SUPPORT -DHAVE_LIBELF_SUPPORT -DHAVE_LIBELF_
 MMAP_SUPPORT -DHAVE_ELF_GETPHDRNUM_SUPPORT -DHAVE_GELF_GETNOTE_SUPPORT 
-DHAVE_ELF_GETSHDRSTRNDX_SUPPORT -DHAVE_DWARF_SUPPORT -DHAVE_LIBBPF_SUPPORT 
-DHAVE_BPF_PROLOGUE -DHAVE_JITDUMP -DHAVE_DWARF_UNWIND_SUPPORT 
-DNO_LIBUNWIND_DEBUG_FRAME -DHAVE_LIBUNWIND_SUPPORT -DHAVE_SLANG_SUPPORT 
-DHAVE_LIBPERL_SUPPORT -DHAVE_TIMERFD_SUPPORT -DHAVE_LIBPYTHON_SUPPORT 
-DHAVE_CPLUS_DEMANGLE_SUPPORT -DHAVE_ZLIB_SUPPORT -DHAVE_LZMA_SUPPORT 
-DHAVE_BACKTRACE_SUPPORT -DHAVE_LIBNUMA_SUPPORT -DHAVE_KVM_STAT_SUPPORT 
-DHAVE_PERF_READ_VDSO32 -DHAVE_PERF_READ_VDSOX32 -DHAVE_LIBBABELTRACE_SUPPORT 
-DHAVE_AUXTRACE_SUPPORT -I/<>/debian/build/build-tools/tools/perf/ 
-D"BUILD_STR(s)=#s" -c -o 
/<>/debian/build/build-tools/tools/perf/util/probe-finder.o 
util/probe-finder.c
  gcc 
-Wp,-MD,/<>/debian/build/build-tools/tools/perf/util/.dwarf-aux.o.d
 -Wp,-MT,/<>/debian/build/build-tools/tools/perf/util/dwarf-aux.o 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wdate-time -D_FORTIFY_SOURCE=2 -I/<>/tools/perf 
-I/<>/debian/build/build-tools/tools/perf -isystem 
/<>/debian/build/build-tools/include -Wbad-function-cast 
-Wdeclaration-after-statement -Wformat-security -Wformat-y2k -Winit-self 
-Wmissing-declarations -Wmissing-prototypes -Wnested-externs 
-Wno-system-headers -Wold-style-definition -Wpacked -Wredundant-decls 
-Wstrict-prototypes -Wswitch-default -Wswitch-enum -Wundef -Wwrite-strings 
-Wformat -Wstrict-aliasing=3 -Wshadow -DHAVE_ARCH_X86_64_SUPPORT 
-I/<>/debian/build/build-tools/tools/perf/arch/x86/include/generated
 -DHAVE_SYSCALL_TABLE_SUPPORT -DHAVE_PERF_REGS_SUPPORT 
-DHAVE_ARCH_REGS_QUERY_REGISTER_OFFSET -O6 -fno-omit-frame-pointer -ggdb3 
-funwind-tab
 les -Wall -Wextra -std=gnu99 -fstack-protector-all -D_FORTIFY_SOURCE=2 
-I/<>/tools/perf/lib/include 
-I/<>/tools/perf/util/include 
-I/<>/tools/perf/arch/x86/include 
-I/<>/tools/include/ 
-I/<>/tools/arch/x86/include/uapi

Bug#957405: klibc: ftbfs with GCC-10

2020-04-17 Thread Matthias Klose

Package: src:klibc
Version: 2.0.7-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/klibc_2.0.7-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
EDESTADDRREQ (89) => "Destination address required"
EMSGSIZE (90) => "Message too long"
EPROTOTYPE (91) => "Protocol wrong type for socket"
ENOPROTOOPT (92) => "Protocol not available"
EPROTONOSUPPORT (93) => "Protocol not supported"
ESOCKTNOSUPPORT (94) => "Socket type not supported"
EOPNOTSUPP (95) => "Operation not supported on transport endpoint"
EPFNOSUPPORT (96) => "Protocol family not supported"
EAFNOSUPPORT (97) => "Address family not supported by protocol"
EADDRINUSE (98) => "Address already in use"
EADDRNOTAVAIL (99) => "Cannot assign requested address"
ENETDOWN (100) => "Network is down"
ENETUNREACH (101) => "Network is unreachable"
ENETRESET (102) => "Network dropped connection because of reset"
ECONNABORTED (103) => "Software caused connection abort"
ECONNRESET (104) => "Connection reset by peer"
ENOBUFS (105) => "No buffer space available"
EISCONN (106) => "Transport endpoint is already connected"
ENOTCONN (107) => "Transport endpoint is not connected"
ESHUTDOWN (108) => "Cannot send after transport endpoint shutdown"
ETOOMANYREFS (109) => "Too many references: cannot splice"
ETIMEDOUT (110) => "Connection timed out"
ECONNREFUSED (111) => "Connection refused"
EHOSTDOWN (112) => "Host is down"
EHOSTUNREACH (113) => "No route to host"
EALREADY (114) => "Operation already in progress"
EINPROGRESS (115) => "Operation now in progress"
ESTALE (116) => "Stale file handle"
EUCLEAN (117) => "Structure needs cleaning"
ENOTNAM (118) => "Not a XENIX named type file"
ENAVAIL (119) => "No XENIX semaphores available"
EISNAM (120) => "Is a named type file"
EREMOTEIO (121) => "Remote I/O error"
EDQUOT (122) => "Quota exceeded"
ENOMEDIUM (123) => "No medium found"
EMEDIUMTYPE (124) => "Wrong medium type"
ECANCELED (125) => "Operation Canceled"
ENOKEY (126) => "Required key not available"
EKEYEXPIRED (127) => "Key has expired"
EKEYREVOKED (128) => "Key has been revoked"
EKEYREJECTED (129) => "Key was rejected by service"
EOWNERDEAD (130) => "Owner died"
ENOTRECOVERABLE (131) => "State not recoverable"
ERFKILL (132) => "Operation not possible due to RF-kill"
EHWPOISON (133) => "Memory page has hardware error"
closing asm-generic/errno.h
closing asm/errno.h
closing linux/errno.h
  gcc -Wp,-MD,usr/klibc/.errlist.o.d  -nostdinc -iwithprefix include 
-I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 
-I/<>/usr/include/bits64 -Iusr/include/bits64 
-I/<>/usr/klibc/../include -Iusr/klibc/../include 
-I/<>/usr/include -Iusr/include -I/<>/linux/include 
-Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 
-fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer 
-mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 
-fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare 
-Wno-unused-parameter -c -o usr/klibc/errlist.o usr/klibc/errlist.c
  echo usr/klibc/vsnprintf.o usr/klibc/snprintf.o usr/klibc/vsprintf.o 
usr/klibc/sprintf.o usr/klibc/asprintf.o usr/klibc/vasprintf.o 
usr/klibc/vsscanf.o usr/klibc/sscanf.o usr/klibc/ctypes.o 
usr/klibc/strntoumax.o usr/klibc/strntoimax.o usr/klibc/atoi.o usr/klibc/atol.o 
usr/klibc/atoll.o usr/klibc/strtol.o usr/klibc/strtoll.o usr/klibc/strtoul.o 
usr/klibc/strtoull.o usr/klibc/strtoimax.o usr/klibc/strtoumax.o 
usr/klibc/globals.o usr/klibc/exit.o usr/klibc/atexit.o usr/klibc/onexit.o 
usr/klibc/execl.o usr/klibc/execle.o usr/klibc/execv.o usr/klibc/execvpe.o 
usr/klibc/execvp.o usr/klibc/execlp.o usr/klibc/execlpe.o usr/klibc/fork.o 
usr/klibc/vfork.o usr/klibc/wait.o usr/klibc/wait3.o usr/klibc/waitpid.o 
usr/klibc/system.o usr/klibc/setpgrp.o usr/klibc/getpgrp.o usr/klibc/daemon.o 
usr/klibc/printf.o usr/klibc/vprintf.o usr/klibc/fprintf.o usr/klibc/vfprintf.o

Processed: Re: Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5