Uploading linux (5.4.8-1)

2020-01-05 Thread Salvatore Bonaccorso
Hi

I'm intenting to upload linux version 5.4.8-1 to unstable today
(Sunday) unless some surprises arise. As perfering to move to the new
stable version 5.4.8 while there were ABI changes, prefered to do an
ABI bump.

The upload cosinst of imports of the new 5.4.7 and 5.4.8 stable
versions and additionally the following packaging changes were done:

   * Enable EROFS filesystem support as module.
 Enable EROFS_FS as module, enable EROFS_FS_XATTR, EROFS_FS_POSIX_ACL,
 EROFS_FS_SECURITY, EROFS_FS_ZIP and EROFS_FS_CLUSTER_PAGE_LIMIT.
 Thanks to Gao Xiang  (Closes: #946569)
   * Enable additional netfilter modules.
 Enable NFT_BRIDGE_META, NF_CONNTRACK_BRIDGE, IP6_NF_MATCH_SRH, NFT_XFRM
 and NFT_SYNPROXY as modules.
 Thanks to Arturo Borrero Gonzalez (Closes: #948031)

and fixes for FBTFS on mips* (Thanks to YunQiang Su)

   [ YunQiang Su ]
   * [mips*/octeon] Fix ftbfs on mips* due to octeon image-file:
 move "image-file: linux" to octeon_build from octeon_image.

Regards,
Salvatore


signature.asc
Description: PGP signature


Bug#931984: linux-image-4.19.0 : Radeon : The kernel cannot reserves memory video. Fixed in 5.

2020-01-05 Thread alain Rpnpif
This bug was fixed. It does not exist in linux-image-5.4.0-1-amd64 (from 
sid) that works fine.


It still exist in linux-image-5.0 from Ubuntu.

So please, fix it in linux-image-4.19.

Regards

Alain Rpnpif



Processed: closing 931984

2020-01-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 931984 5.4.6-1
Bug #931984 [src:linux] linux-image-4.19.0-0.bpo.5-amd64: Radeon : The kernel 
cannot reserves memory video so none video output cannot works.
Marked as fixed in versions linux/5.4.6-1.
Bug #931984 [src:linux] linux-image-4.19.0-0.bpo.5-amd64: Radeon : The kernel 
cannot reserves memory video so none video output cannot works.
Marked Bug as done
> thanks
Stopping processing here.

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



Processing of linux_5.4.8-1_source.changes

2020-01-05 Thread Debian FTP Masters
linux_5.4.8-1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.4.8-1.dsc
  linux_5.4.8.orig.tar.xz
  linux_5.4.8-1.debian.tar.xz
  linux_5.4.8-1_source.buildinfo

Greetings,

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



linux_5.4.8-1_source.changes is NEW

2020-01-05 Thread Debian FTP Masters
binary:acpi-modules-5.4.0-2-686-di is NEW.
binary:acpi-modules-5.4.0-2-686-pae-di is NEW.
binary:acpi-modules-5.4.0-2-amd64-di is NEW.
binary:affs-modules-5.4.0-2-4kc-malta-di is NEW.
binary:affs-modules-5.4.0-2-5kc-malta-di is NEW.
binary:affs-modules-5.4.0-2-loongson-3-di is NEW.
binary:affs-modules-5.4.0-2-octeon-di is NEW.
binary:ata-modules-5.4.0-2-4kc-malta-di is NEW.
binary:ata-modules-5.4.0-2-5kc-malta-di is NEW.
binary:ata-modules-5.4.0-2-686-di is NEW.
binary:ata-modules-5.4.0-2-686-pae-di is NEW.
binary:ata-modules-5.4.0-2-amd64-di is NEW.
binary:ata-modules-5.4.0-2-arm64-di is NEW.
binary:ata-modules-5.4.0-2-armmp-di is NEW.
binary:ata-modules-5.4.0-2-loongson-3-di is NEW.
binary:ata-modules-5.4.0-2-powerpc64le-di is NEW.
binary:btrfs-modules-5.4.0-2-4kc-malta-di is NEW.
binary:btrfs-modules-5.4.0-2-5kc-malta-di is NEW.
binary:btrfs-modules-5.4.0-2-686-di is NEW.
binary:btrfs-modules-5.4.0-2-686-pae-di is NEW.
binary:btrfs-modules-5.4.0-2-amd64-di is NEW.
binary:btrfs-modules-5.4.0-2-arm64-di is NEW.
binary:btrfs-modules-5.4.0-2-armmp-di is NEW.
binary:btrfs-modules-5.4.0-2-loongson-3-di is NEW.
binary:btrfs-modules-5.4.0-2-marvell-di is NEW.
binary:btrfs-modules-5.4.0-2-octeon-di is NEW.
binary:btrfs-modules-5.4.0-2-powerpc64le-di is NEW.
binary:btrfs-modules-5.4.0-2-s390x-di is NEW.
binary:cdrom-core-modules-5.4.0-2-4kc-malta-di is NEW.
binary:cdrom-core-modules-5.4.0-2-5kc-malta-di is NEW.
binary:cdrom-core-modules-5.4.0-2-686-di is NEW.
binary:cdrom-core-modules-5.4.0-2-686-pae-di is NEW.
binary:cdrom-core-modules-5.4.0-2-amd64-di is NEW.
binary:cdrom-core-modules-5.4.0-2-arm64-di is NEW.
binary:cdrom-core-modules-5.4.0-2-armmp-di is NEW.
binary:cdrom-core-modules-5.4.0-2-loongson-3-di is NEW.
binary:cdrom-core-modules-5.4.0-2-marvell-di is NEW.
binary:cdrom-core-modules-5.4.0-2-octeon-di is NEW.
binary:cdrom-core-modules-5.4.0-2-powerpc64le-di is NEW.
binary:cdrom-core-modules-5.4.0-2-s390x-di is NEW.
binary:compress-modules-5.4.0-2-4kc-malta-di is NEW.
binary:compress-modules-5.4.0-2-5kc-malta-di is NEW.
binary:compress-modules-5.4.0-2-686-di is NEW.
binary:compress-modules-5.4.0-2-686-pae-di is NEW.
binary:compress-modules-5.4.0-2-amd64-di is NEW.
binary:compress-modules-5.4.0-2-arm64-di is NEW.
binary:compress-modules-5.4.0-2-armmp-di is NEW.
binary:compress-modules-5.4.0-2-loongson-3-di is NEW.
binary:compress-modules-5.4.0-2-marvell-di is NEW.
binary:compress-modules-5.4.0-2-octeon-di is NEW.
binary:compress-modules-5.4.0-2-powerpc64le-di is NEW.
binary:compress-modules-5.4.0-2-s390x-di is NEW.
binary:crc-modules-5.4.0-2-4kc-malta-di is NEW.
binary:crc-modules-5.4.0-2-5kc-malta-di is NEW.
binary:crc-modules-5.4.0-2-686-di is NEW.
binary:crc-modules-5.4.0-2-686-pae-di is NEW.
binary:crc-modules-5.4.0-2-amd64-di is NEW.
binary:crc-modules-5.4.0-2-arm64-di is NEW.
binary:crc-modules-5.4.0-2-armmp-di is NEW.
binary:crc-modules-5.4.0-2-loongson-3-di is NEW.
binary:crc-modules-5.4.0-2-marvell-di is NEW.
binary:crc-modules-5.4.0-2-octeon-di is NEW.
binary:crc-modules-5.4.0-2-powerpc64le-di is NEW.
binary:crc-modules-5.4.0-2-s390x-di is NEW.
binary:crypto-dm-modules-5.4.0-2-4kc-malta-di is NEW.
binary:crypto-dm-modules-5.4.0-2-5kc-malta-di is NEW.
binary:crypto-dm-modules-5.4.0-2-686-di is NEW.
binary:crypto-dm-modules-5.4.0-2-686-pae-di is NEW.
binary:crypto-dm-modules-5.4.0-2-amd64-di is NEW.
binary:crypto-dm-modules-5.4.0-2-arm64-di is NEW.
binary:crypto-dm-modules-5.4.0-2-armmp-di is NEW.
binary:crypto-dm-modules-5.4.0-2-loongson-3-di is NEW.
binary:crypto-dm-modules-5.4.0-2-marvell-di is NEW.
binary:crypto-dm-modules-5.4.0-2-octeon-di is NEW.
binary:crypto-dm-modules-5.4.0-2-powerpc64le-di is NEW.
binary:crypto-dm-modules-5.4.0-2-s390x-di is NEW.
binary:crypto-modules-5.4.0-2-4kc-malta-di is NEW.
binary:crypto-modules-5.4.0-2-5kc-malta-di is NEW.
binary:crypto-modules-5.4.0-2-686-di is NEW.
binary:crypto-modules-5.4.0-2-686-pae-di is NEW.
binary:crypto-modules-5.4.0-2-amd64-di is NEW.
binary:crypto-modules-5.4.0-2-arm64-di is NEW.
binary:crypto-modules-5.4.0-2-armmp-di is NEW.
binary:crypto-modules-5.4.0-2-loongson-3-di is NEW.
binary:crypto-modules-5.4.0-2-marvell-di is NEW.
binary:crypto-modules-5.4.0-2-octeon-di is NEW.
binary:crypto-modules-5.4.0-2-powerpc64le-di is NEW.
binary:crypto-modules-5.4.0-2-s390x-di is NEW.
binary:dasd-extra-modules-5.4.0-2-s390x-di is NEW.
binary:dasd-modules-5.4.0-2-s390x-di is NEW.
binary:efi-modules-5.4.0-2-686-di is NEW.
binary:efi-modules-5.4.0-2-686-pae-di is NEW.
binary:efi-modules-5.4.0-2-amd64-di is NEW.
binary:efi-modules-5.4.0-2-arm64-di is NEW.
binary:efi-modules-5.4.0-2-armmp-di is NEW.
binary:event-modules-5.4.0-2-4kc-malta-di is NEW.
binary:event-modules-5.4.0-2-5kc-malta-di is NEW.
binary:event-modules-5.4.0-2-686-di is NEW.
binary:event-modules-5.4.0-2-686-pae-di is NEW.
binary:event-modules-5.4.0-2-amd64-di is NEW.
binary:event-modules-5.4.0-2-arm64-di is NEW.
binary:event-modules-5.4.0-2-armmp-di is NEW.
binary:event-modules-5.4.0-2-loon

Bug#931930: firmware-misc-nonfree: Please, include i915/icl_dmc_ver1_07.bin

2020-01-05 Thread Валерий Заподовников
Hi,

I'm getting these messages too... I use latest Kali linux 2020. After
I install nvidia-driver today, it happened. I suppose it is because I
have Intel Haswell, and before I was using SSD in vmware and so there
were no problems as there were no device that needed it in vmware.

root@kali# update-initramfs -u

W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_07.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin
for module i915

I fixed it by just downloading debian source code packet (sic!)
https://deb.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-nonfree_20190717.orig.tar.xz
and pasting those two files!

Why it is like that?? Please fix it!

Also see 
https://askubuntu.com/questions/832524/possible-missing-frmware-lib-firmware-i915


Recurrent alerts "Package temperature above threshold, cpu clock throttled"

2020-01-05 Thread l0f4r0
Hi team,

Multiple times per hour (despite no notable CPU-consuming activity), I get 
something like the following journalctl crit/2 entry:

kernel: CPUX: Package temperature above threshold, cpu clock throttled (total 
events = Y)
where X=[0-7] (I have a quad-core i7 with hyperthreading activated) and Y is 
generally a 4-digit number.

There are different threads about it on the Internet. Some seem to indicate a 
kernel issue, others says it's sensors or CPU paste fault and others don't 
explain anything and recommend to change the threshold or deactivate the alerts 
themselves (!).

Are you aware of anything Debian-kernel-related please (I didn't see any such 
bug at 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=linux-image-4.19.0-6-amd64 
though) that could help me regarding that matter, considering the fact I'm on 
Debian 10 (kernel 4.19.67-2+deb10u2) with an amd64 Lenovo ThinkPad X390?
NB: My laptop is brand new, so I'm not really convinced of an hardware issue at 
this stage (it cannot be totally excluded though).

Thank you in advance and Happy GNU Year! :)
Best regards,
l0f4r0



Bug#948031: marked as done (please enable some additional Netfilter modules)

2020-01-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 Jan 2020 19:00:11 +
with message-id 
and subject line Bug#948031: fixed in linux 5.4.8-1
has caused the Debian Bug report #948031,
regarding please enable some additional Netfilter modules
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.)


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

Dear kernel maintainers,

thanks for your hard work with this package, it is really appreciated.

I discovered this in my machine:

arturo@endurance:~$ grep NF_ /boot/config-5.3.0-3-amd64 | grep ^#
# CONFIG_IP6_NF_MATCH_SRH is not set
# CONFIG_NF_CONNTRACK_BRIDGE is not set
arturo@endurance:~$ grep NFT /boot/config-5.3.0-3-amd64 | grep ^#
# CONFIG_NFT_XFRM is not set
# CONFIG_NFT_SYNPROXY is not set
# CONFIG_NFT_BRIDGE_META is not set

Would you please enable them?

thanks!

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.4.8-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 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (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: Sun, 05 Jan 2020 15:40:37 +0100
Source: linux
Architecture: source
Version: 5.4.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 946569 948031
Changes:
 linux (5.4.8-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.7
 - af_packet: set defaule value for tmo
 - [amd64] fjes: fix missed check in fjes_acpi_add
 - mod_devicetable: fix PHY module format
 - net: dst: Force 4-byte alignment of dst_metrics
 - [arm64] net: hisilicon: Fix a BUG trigered by wrong bytes_compl
 - net: phy: ensure that phy IDs are correctly typed
 - net: qlogic: Fix error paths in ql_alloc_large_buffers()
 - net-sysfs: Call dev_hold always in rx_queue_add_kobject
 - net: usb: lan78xx: Fix suspend/resume PHY register access error
 - [arm64,armhf] nfp: flower: fix stats id allocation
 - qede: Disable hardware gro when xdp prog is installed
 - qede: Fix multicast mac configuration
 - sctp: fix memleak on err handling of stream initialization
 - sctp: fully initialize v4 addr in some functions
 - neighbour: remove neigh_cleanup() method
 - bonding: fix bond_neigh_init()
 - net: ena: fix default tx interrupt moderation interval
 - net: ena: fix issues in setting interrupt moderation params in ethtool
 - [armhf] net: ethernet: ti: davinci_cpdma: fix warning "device driver
   frees DMA memory with different size"
 - [arm64,armhf] net: stmmac: platform: Fix MDIO init for platforms without
   PHY
 - [armhf] net: dsa: b53: Fix egress flooding settings
 - btrfs: don't double lock the subvol_sem for rename exchange
 - btrfs: do not call synchronize_srcu() in inode_tree_del
 - Btrfs: make tree checker detect checksum items with overlapping ranges
 - btrfs: return error pointer from alloc_test_extent_buffer
 - Btrfs: fix missing data checksums after replaying a log tree
 - btrfs: send: remove WARN_ON for readonly mount
 - btrfs: abort transaction after failed inode updates in create_subvol
 - btrfs: skip log replay on orphaned roots
 - btrfs: do not leak reloc root if we fail to read the fs root
 - btrfs: handle ENOENT in btrfs_uuid_tree_iterate
 - Btrfs: fix removal logic of t

Bug#946569: marked as done (Request for CONFIG_EROFS_FS=m on 5.4+)

2020-01-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 Jan 2020 19:00:11 +
with message-id 
and subject line Bug#946569: fixed in linux 5.4.8-1
has caused the Debian Bug report #946569,
regarding Request for CONFIG_EROFS_FS=m on 5.4+
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.)


-- 
946569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: linux
Version: 5.4.2-1~exp1
Severity: normal

Hi Debian kernel maintainers,

Could you consider enabling EROFS filesystem support as a module
from 5.4 for end users now? It has been out of staging.

It has much better dynamic performance than squashfs for such
like LIVECD use. I'd suggest the following configuration:

CONFIG_EROFS_FS=m
# CONFIG_EROFS_FS_DEBUG is not set
CONFIG_EROFS_FS_XATTR=y
CONFIG_EROFS_FS_POSIX_ACL=y
CONFIG_EROFS_FS_SECURITY=y
CONFIG_EROFS_FS_ZIP=y
CONFIG_EROFS_FS_CLUSTER_PAGE_LIMIT=1

erofs-utils package has been available in testing branch as well,
https://packages.debian.org/source/bullseye/erofs-utils

Thanks,
Gao Xiang
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.4.8-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 946...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (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: Sun, 05 Jan 2020 15:40:37 +0100
Source: linux
Architecture: source
Version: 5.4.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 946569 948031
Changes:
 linux (5.4.8-1) unstable; urgency=medium
 .
   * New upstream stable update:
 https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.7
 - af_packet: set defaule value for tmo
 - [amd64] fjes: fix missed check in fjes_acpi_add
 - mod_devicetable: fix PHY module format
 - net: dst: Force 4-byte alignment of dst_metrics
 - [arm64] net: hisilicon: Fix a BUG trigered by wrong bytes_compl
 - net: phy: ensure that phy IDs are correctly typed
 - net: qlogic: Fix error paths in ql_alloc_large_buffers()
 - net-sysfs: Call dev_hold always in rx_queue_add_kobject
 - net: usb: lan78xx: Fix suspend/resume PHY register access error
 - [arm64,armhf] nfp: flower: fix stats id allocation
 - qede: Disable hardware gro when xdp prog is installed
 - qede: Fix multicast mac configuration
 - sctp: fix memleak on err handling of stream initialization
 - sctp: fully initialize v4 addr in some functions
 - neighbour: remove neigh_cleanup() method
 - bonding: fix bond_neigh_init()
 - net: ena: fix default tx interrupt moderation interval
 - net: ena: fix issues in setting interrupt moderation params in ethtool
 - [armhf] net: ethernet: ti: davinci_cpdma: fix warning "device driver
   frees DMA memory with different size"
 - [arm64,armhf] net: stmmac: platform: Fix MDIO init for platforms without
   PHY
 - [armhf] net: dsa: b53: Fix egress flooding settings
 - btrfs: don't double lock the subvol_sem for rename exchange
 - btrfs: do not call synchronize_srcu() in inode_tree_del
 - Btrfs: make tree checker detect checksum items with overlapping ranges
 - btrfs: return error pointer from alloc_test_extent_buffer
 - Btrfs: fix missing data checksums after replaying a log tree
 - btrfs: send: remove WARN_ON for readonly mount
 - btrfs: abort transaction after failed inode updates in create_subvol
 - btrfs: skip log replay on orphaned roots
 - btrfs: do not leak reloc root if we fail to read the fs root
 - btrfs: handle ENOENT in btrfs_uuid_tree_iterate
 - Btrfs: fix removal logic of the tree mod log that leads to
   use-after-free issues
 - ALSA: pcm: Avoid possible info leaks from PCM stream buffers
 - ALSA: hda/ca0132 - Keep power on during processing DSP response
 - ALSA: hda/ca0132 - Avoid endless loop
 - ALSA: hda/ca0132 - Fix work handling in delayed HP detection
 - [arm*] 

Re: Uploading linux (5.4.8-1)

2020-01-05 Thread Mike Hommey
Hi,

Are you planning an update in buster-backports, too?

Cheers,

Mike

On Sun, Jan 05, 2020 at 01:45:49PM +0100, Salvatore Bonaccorso wrote:
> Hi
> 
> I'm intenting to upload linux version 5.4.8-1 to unstable today
> (Sunday) unless some surprises arise. As perfering to move to the new
> stable version 5.4.8 while there were ABI changes, prefered to do an
> ABI bump.
> 
> The upload cosinst of imports of the new 5.4.7 and 5.4.8 stable
> versions and additionally the following packaging changes were done:
> 
>* Enable EROFS filesystem support as module.
>  Enable EROFS_FS as module, enable EROFS_FS_XATTR, EROFS_FS_POSIX_ACL,
>  EROFS_FS_SECURITY, EROFS_FS_ZIP and EROFS_FS_CLUSTER_PAGE_LIMIT.
>  Thanks to Gao Xiang  (Closes: #946569)
>* Enable additional netfilter modules.
>  Enable NFT_BRIDGE_META, NF_CONNTRACK_BRIDGE, IP6_NF_MATCH_SRH, NFT_XFRM
>  and NFT_SYNPROXY as modules.
>  Thanks to Arturo Borrero Gonzalez (Closes: #948031)
> 
> and fixes for FBTFS on mips* (Thanks to YunQiang Su)
> 
>[ YunQiang Su ]
>* [mips*/octeon] Fix ftbfs on mips* due to octeon image-file:
>  move "image-file: linux" to octeon_build from octeon_image.
> 
> Regards,
> Salvatore




Bug#948243: linux-image-5.4.0-1-amd64: Fails to boot into graphical mode on Radeon RX 5700 XT, amdgpu: [powerplay] failed send message

2020-01-05 Thread Artur Matuszewski
Package: src:linux
Version: 5.4.6-1
Severity: important

Dear Maintainer,

Switching from kernel package 5.3.0-3-amd64 to package 5.4.0-1-amd64 makes my
PC no longer boot in graphical mode, with amdgpu errors reported in kernel log.
Selecting the older kernel (5.3) from GRUB still boots the system correctly
with no issues.
I am using latest firmware binaries from linux-firmware repository because
older versions did not detect the graphics card correctly (I am using Radeon RX
5700 XT).

The following amdgpu-related lines are present in kernel logs:

[drm] amdgpu kernel modesetting enabled.
amdgpu :0a:00.0: remove_conflicting_pci_framebuffers: bar 0: 0xe000 ->
0xefff
amdgpu :0a:00.0: remove_conflicting_pci_framebuffers: bar 2: 0xf000 ->
0xf01f
amdgpu :0a:00.0: remove_conflicting_pci_framebuffers: bar 5: 0xfcb0 ->
0xfcb7
fb0: switching to amdgpudrmfb from EFI VGA
amdgpu :0a:00.0: vgaarb: deactivate vga console
amdgpu :0a:00.0: firmware: direct-loading firmware
amdgpu/navi10_gpu_info.bin
amdgpu :0a:00.0: No more image in the PCI ROM
amdgpu :0a:00.0: VRAM: 8176M 0x0080 - 0x0081FEFF (8176M
used)
amdgpu :0a:00.0: GART: 512M 0x - 0x1FFF
[drm] amdgpu: 8176M of VRAM memory ready
[drm] amdgpu: 8176M of GTT memory ready.
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_sos.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_asd.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_smc.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_pfp.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_me.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_ce.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_rlc.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_mec.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_mec2.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_sdma.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_sdma1.bin
amdgpu :0a:00.0: firmware: direct-loading firmware amdgpu/navi10_vcn.bin
amdgpu: [powerplay] SMU is initialized successfully!
fbcon: amdgpudrmfb (fb0) is primary device
amdgpu :0a:00.0: fb0: amdgpudrmfb frame buffer device
amdgpu :0a:00.0: ring 0(gfx_0.0.0) uses VM inv eng 4 on hub 0
amdgpu :0a:00.0: ring 1(gfx_0.1.0) uses VM inv eng 5 on hub 0
amdgpu :0a:00.0: ring 2(comp_1.0.0) uses VM inv eng 6 on hub 0
amdgpu :0a:00.0: ring 3(comp_1.1.0) uses VM inv eng 7 on hub 0
amdgpu :0a:00.0: ring 4(comp_1.2.0) uses VM inv eng 8 on hub 0
amdgpu :0a:00.0: ring 5(comp_1.3.0) uses VM inv eng 9 on hub 0
amdgpu :0a:00.0: ring 6(comp_1.0.1) uses VM inv eng 10 on hub 0
amdgpu :0a:00.0: ring 7(comp_1.1.1) uses VM inv eng 11 on hub 0
amdgpu :0a:00.0: ring 8(comp_1.2.1) uses VM inv eng 12 on hub 0
amdgpu :0a:00.0: ring 9(comp_1.3.1) uses VM inv eng 13 on hub 0
amdgpu :0a:00.0: ring 10(kiq_2.1.0) uses VM inv eng 14 on hub 0
amdgpu :0a:00.0: ring 11(sdma0) uses VM inv eng 15 on hub 0
amdgpu :0a:00.0: ring 12(sdma1) uses VM inv eng 16 on hub 0
amdgpu :0a:00.0: ring 13(vcn_dec) uses VM inv eng 4 on hub 1
amdgpu :0a:00.0: ring 14(vcn_enc0) uses VM inv eng 5 on hub 1
amdgpu :0a:00.0: ring 15(vcn_enc1) uses VM inv eng 6 on hub 1
amdgpu :0a:00.0: ring 16(vcn_jpeg) uses VM inv eng 7 on hub 1
[drm] Initialized amdgpu 3.35.0 20150101 for :0a:00.0 on minor 0
snd_hda_intel :0a:00.1: bound :0a:00.0 (ops
amdgpu_dm_audio_component_bind_ops [amdgpu])
amdgpu: [powerplay] failed send message: TransferTableSmu2Dram (18)
param: 0x0006 response 0xffc2
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] failed send message: PowerUpVcn (43) param:
0x0001 response 0xffc2
amdgpu :0a:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed
on vcn_enc0 (-110).
amdgpu :0a:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed
on vcn_enc1 (-110).
amdgpu: [powerplay] failed send message: TransferTableSmu2Dram (18)
param: 0x0006 response 0xffc2
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14)
param: 0x0080 response 0xffc2
amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14)
param: 0x0080 response 0xffc2
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14)
param: 0x0080 response 0xffc2
amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14)
param: 0x0080 response 0xffc2
amdgpu: [powerplay] Failed to export SMU metrics table!
amdgpu: [powerplay] failed send message: SetDriverDramAddrHigh (14)
param: 0x0080 response 0xffc2
amdgpu: [powerplay] 

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

2020-01-05 Thread Debian FTP Masters
linux-signed-amd64_5.4.8+1_source.changes uploaded successfully to localhost
along with the files:
  linux-signed-amd64_5.4.8+1.dsc
  linux-signed-amd64_5.4.8+1.tar.xz

Greetings,

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



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

2020-01-05 Thread Debian FTP Masters
Mapping sid to unstable.
binary:linux-image-5.4.0-2-amd64 is NEW.
binary:linux-image-5.4.0-2-cloud-amd64 is NEW.
binary:linux-image-5.4.0-2-rt-amd64 is NEW.

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



Re: Recurrent alerts "Package temperature above threshold, cpu clock throttled"

2020-01-05 Thread Nicholas D Steeves
Hi l0f4r0,

Reply follows inline.

 writes:

> Hi team,
>
> Multiple times per hour (despite no notable CPU-consuming activity), I
> get something like the following journalctl crit/2 entry:
>
> kernel: CPUX: Package temperature above threshold, cpu clock throttled
> (total events = Y) where X=[0-7] (I have a quad-core i7 with
> hyperthreading activated) and Y is generally a 4-digit number.
>

While I'm very much a junior member of the team, I have noted similar
behaviour on a laptop as old as an X220 and wonder if it might be due to
Spectre mitigations.  I have not noticed such log entries after
disabling hyperthreading.  FYI, as someone who works with realtime audio
I've found that hyperthreading is detrimental to worst-case latency.
eg: after many hours trying to workaround troublesome unpredictable
latency spikes the solution to disable hyperthreading emerged as the
simplest solution.

> There are different threads about it on the Internet. Some seem to
> indicate a kernel issue, others says it's sensors or CPU paste fault
> and others don't explain anything and recommend to change the
> threshold or deactivate the alerts themselves (!).
>

Yeah, you're right, that seems ill-advised, even if one can depend on
the EC to shut down the laptop in case of thermal overload.  Have you
tried disabling CPU freq boost?  When the ambient temperature is above
27°C my X220 and X230 need to have boost disabled to avoid
overheating/throttling.

> Are you aware of anything Debian-kernel-related please (I didn't see
> any such bug at
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=linux-image-4.19.0-6-amd64
> though) that could help me regarding that matter, considering the fact
> I'm on Debian 10 (kernel 4.19.67-2+deb10u2) with an amd64 Lenovo
> ThinkPad X390?  NB: My laptop is brand new, so I'm not really
> convinced of an hardware issue at this stage (it cannot be totally
> excluded though).
>

Sorry, I'm not aware of any, but someone else might be!

> Thank you in advance and Happy GNU Year! :)
> Best regards,
> l0f4r0

Thanks, you too! :-)


Best,
Nicholas


signature.asc
Description: PGP signature


Processing of linux_5.5~rc5-1~exp1_source.changes

2020-01-05 Thread Debian FTP Masters
linux_5.5~rc5-1~exp1_source.changes uploaded successfully to localhost
along with the files:
  linux_5.5~rc5-1~exp1.dsc
  linux_5.5~rc5.orig.tar.xz
  linux_5.5~rc5-1~exp1.debian.tar.xz
  linux_5.5~rc5-1~exp1_source.buildinfo

Greetings,

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



linux_5.5~rc5-1~exp1_source.changes is NEW

2020-01-05 Thread Debian FTP Masters
binary:acpi-modules-5.5.0-rc5-686-di is NEW.
binary:acpi-modules-5.5.0-rc5-686-pae-di is NEW.
binary:acpi-modules-5.5.0-rc5-amd64-di is NEW.
binary:affs-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:affs-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:affs-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:affs-modules-5.5.0-rc5-octeon-di is NEW.
binary:ata-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:ata-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:ata-modules-5.5.0-rc5-686-di is NEW.
binary:ata-modules-5.5.0-rc5-686-pae-di is NEW.
binary:ata-modules-5.5.0-rc5-amd64-di is NEW.
binary:ata-modules-5.5.0-rc5-arm64-di is NEW.
binary:ata-modules-5.5.0-rc5-armmp-di is NEW.
binary:ata-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:ata-modules-5.5.0-rc5-powerpc64le-di is NEW.
binary:btrfs-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:btrfs-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:btrfs-modules-5.5.0-rc5-686-di is NEW.
binary:btrfs-modules-5.5.0-rc5-686-pae-di is NEW.
binary:btrfs-modules-5.5.0-rc5-amd64-di is NEW.
binary:btrfs-modules-5.5.0-rc5-arm64-di is NEW.
binary:btrfs-modules-5.5.0-rc5-armmp-di is NEW.
binary:btrfs-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:btrfs-modules-5.5.0-rc5-marvell-di is NEW.
binary:btrfs-modules-5.5.0-rc5-octeon-di is NEW.
binary:btrfs-modules-5.5.0-rc5-powerpc64le-di is NEW.
binary:btrfs-modules-5.5.0-rc5-s390x-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-686-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-686-pae-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-amd64-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-arm64-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-armmp-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-marvell-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-octeon-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-powerpc64le-di is NEW.
binary:cdrom-core-modules-5.5.0-rc5-s390x-di is NEW.
binary:compress-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:compress-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:compress-modules-5.5.0-rc5-686-di is NEW.
binary:compress-modules-5.5.0-rc5-686-pae-di is NEW.
binary:compress-modules-5.5.0-rc5-amd64-di is NEW.
binary:compress-modules-5.5.0-rc5-arm64-di is NEW.
binary:compress-modules-5.5.0-rc5-armmp-di is NEW.
binary:compress-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:compress-modules-5.5.0-rc5-marvell-di is NEW.
binary:compress-modules-5.5.0-rc5-octeon-di is NEW.
binary:compress-modules-5.5.0-rc5-powerpc64le-di is NEW.
binary:compress-modules-5.5.0-rc5-s390x-di is NEW.
binary:crc-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:crc-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:crc-modules-5.5.0-rc5-686-di is NEW.
binary:crc-modules-5.5.0-rc5-686-pae-di is NEW.
binary:crc-modules-5.5.0-rc5-amd64-di is NEW.
binary:crc-modules-5.5.0-rc5-arm64-di is NEW.
binary:crc-modules-5.5.0-rc5-armmp-di is NEW.
binary:crc-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:crc-modules-5.5.0-rc5-marvell-di is NEW.
binary:crc-modules-5.5.0-rc5-octeon-di is NEW.
binary:crc-modules-5.5.0-rc5-powerpc64le-di is NEW.
binary:crc-modules-5.5.0-rc5-s390x-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-686-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-686-pae-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-amd64-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-arm64-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-armmp-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-marvell-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-octeon-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-powerpc64le-di is NEW.
binary:crypto-dm-modules-5.5.0-rc5-s390x-di is NEW.
binary:crypto-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:crypto-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:crypto-modules-5.5.0-rc5-686-di is NEW.
binary:crypto-modules-5.5.0-rc5-686-pae-di is NEW.
binary:crypto-modules-5.5.0-rc5-amd64-di is NEW.
binary:crypto-modules-5.5.0-rc5-arm64-di is NEW.
binary:crypto-modules-5.5.0-rc5-armmp-di is NEW.
binary:crypto-modules-5.5.0-rc5-loongson-3-di is NEW.
binary:crypto-modules-5.5.0-rc5-marvell-di is NEW.
binary:crypto-modules-5.5.0-rc5-octeon-di is NEW.
binary:crypto-modules-5.5.0-rc5-powerpc64le-di is NEW.
binary:crypto-modules-5.5.0-rc5-s390x-di is NEW.
binary:dasd-extra-modules-5.5.0-rc5-s390x-di is NEW.
binary:dasd-modules-5.5.0-rc5-s390x-di is NEW.
binary:efi-modules-5.5.0-rc5-686-di is NEW.
binary:efi-modules-5.5.0-rc5-686-pae-di is NEW.
binary:efi-modules-5.5.0-rc5-amd64-di is NEW.
binary:efi-modules-5.5.0-rc5-arm64-di is NEW.
binary:efi-modules-5.5.0-rc5-armmp-di is NEW.
binary:event-modules-5.5.0-rc5-4kc-malta-di is NEW.
binary:event-modules-5.5.0-rc5-5kc-malta-di is NEW.
binary:event-modules-5.5.0-rc5-686-di is NEW.
binary:event-modules-5.