Bug#955366: marked as done (Enable CONFIG_KSM in the cloud kernel)
Your message dated Mon, 27 Apr 2020 04:00:09 + with message-id and subject line Bug#955366: fixed in linux 4.19.118-1 has caused the Debian Bug report #955366, regarding Enable CONFIG_KSM in the cloud kernel 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.) -- 955366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.98-1 Severity: wishlist Owner: no...@debian.org Relaying a request on behalf of an Amazon EC2 customer. The generic kernel enables CONFIG_KSM, but the cloud kernel disables this. The customer makes extensive use of KSM features in EC2 and would like to request that the feature be enabled for the cloud kernel. Since the cloud kernel is intended to be optimized for boot time and size for common cloud usecases, it's worth understanding how much code is actually enabled by CONFIG_KSM, and how this affects the size and boot time (if at all). noah --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.118-1 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 955...@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: Sun, 26 Apr 2020 14:04:11 +0100 Source: linux Architecture: source Version: 4.19.118-1 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 947021 951274 953017 955366 Changes: linux (4.19.118-1) buster; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.99 - Revert "efi: Fix debugobjects warning on 'efi_rts_work'" - xfs: Sanity check flags of Q_XQUOTARM call - [x86] mfd: intel-lpss: Add default I2C device properties for Gemini Lake - SUNRPC: Fix svcauth_gss_proxy_init() - [powerpc*] pseries: Enable support for ibm,drc-info property - tipc: update mon's self addr when node addr generated - tipc: fix wrong timeout input for tipc_wait_for_cond() - mt7601u: fix bbp version check in mt7601u_wait_bbp_ready - [armhf] crypto: sun4i-ss - fix big endian issues - perf map: No need to adjust the long name of modules - ipmi: Fix memory leak in __ipmi_bmc_register (CVE-2019-19046) - ixgbe: don't clear IPsec sa counters on HW clearing - drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset() - iio: fix position relative kernel version - apparmor: Fix network performance issue in aa_label_sk_perm - ALSA: hda: fix unused variable warning - apparmor: don't try to replace stale label in ptrace access check - firmware: coreboot: Let OF core populate platform device - bridge: br_arp_nd_proxy: set icmp6_router if neigh has NTF_ROUTER - [arm64] drm/hisilicon: hibmc: Don't overwrite fb helper surface depth - IB/rxe: replace kvfree with vfree - [amd64] IB/hfi1: Add mtu check for operational data VLs - genirq/debugfs: Reinstate full OF path for domain name - [arm64] usb: dwc3: add EXTCON dependency for qcom - cfg80211: regulatory: make initialization more robust - [x86] mei: replace POLL* with EPOLL* for write queues. - [arm64] drm/msm: fix unsigned comparison with less than zero - ALSA: usb-audio: update quirk for B PX to remove microphone - iwlwifi: nvm: get num of hw addresses from firmware - netfilter: nft_osf: usage from output path is not valid - [x86] pwm: lpss: Release runtime-pm reference from the driver's remove callback - [powerpc*] pseries/memory-hotplug: Fix return value type of find_aa_index - rtlwifi: rtl8821ae: replace _rtl8821ae_mrate_idx_to_arfr_id with generic version - netfilter: nf_flow_table: do not remove offload when other netns's interface is down - tipc: eliminate message disordering during binding table update - [arm64] net: socionext: Add dummy PHY
Bug#951274: marked as done (Require build and include Hisilicon Hibmc drm driver in the buster installer)
Your message dated Mon, 27 Apr 2020 04:00:09 + with message-id and subject line Bug#951274: fixed in linux 4.19.118-1 has caused the Debian Bug report #951274, regarding Require build and include Hisilicon Hibmc drm driver in the buster installer 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.) -- 951274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-source Version: 4.19.0-6 Severity: important I'm trying to install Debian buster on to the Huawei Kunpeng arm64 server, found that the installation graphic output not show up via the server BMC virtual console. Huawei Kunpeng arm64 server using a hibmc chip on the mainboard, the lspci output of the VGA device is: ~$ lspci -nn | grep VGA 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) Currently the kernel VGA driver module (hibmc_drm.ko) was not included in the netboot initrd ( http://ftp.debian.org/debian/dists/stable/main/installer-arm64/20190702+deb10u1/images/netboot/netboot.tar.gz) . I have verified the BMC virtual console graphic output works well after adding the hibmc_drm.ko into the netboot initrd, could you please help to built and include this driver module in the installer? Thanks -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 4.19.0-6-arm64 (SMP w/96 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Kairui She --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.118-1 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 951...@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: Sun, 26 Apr 2020 14:04:11 +0100 Source: linux Architecture: source Version: 4.19.118-1 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 947021 951274 953017 955366 Changes: linux (4.19.118-1) buster; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.99 - Revert "efi: Fix debugobjects warning on 'efi_rts_work'" - xfs: Sanity check flags of Q_XQUOTARM call - [x86] mfd: intel-lpss: Add default I2C device properties for Gemini Lake - SUNRPC: Fix svcauth_gss_proxy_init() - [powerpc*] pseries: Enable support for ibm,drc-info property - tipc: update mon's self addr when node addr generated - tipc: fix wrong timeout input for tipc_wait_for_cond() - mt7601u: fix bbp version check in mt7601u_wait_bbp_ready - [armhf] crypto: sun4i-ss - fix big endian issues - perf map: No need to adjust the long name of modules - ipmi: Fix memory leak in __ipmi_bmc_register (CVE-2019-19046) - ixgbe: don't clear IPsec sa counters on HW clearing - drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset() - iio: fix position relative kernel version - apparmor: Fix network performance issue in aa_label_sk_perm - ALSA: hda: fix unused variable warning - apparmor: don't try to replace stale label in ptrace access check - firmware: coreboot: Let OF core populate platform device - bridge: br_arp_nd_proxy: set icmp6_router if neigh has NTF_ROUTER - [arm64] drm/hisilicon: hibmc: Don't overwrite fb helper surface depth - IB/rxe: replace kvfree with vfree - [amd64] IB/hfi1: Add mtu check for operational data VLs - genirq/debugfs: Reinstate full OF path for domain name - [arm64] usb: dwc3: add EXTCON dependency for qcom - cfg80211: regulatory: make initialization
Bug#947021: marked as done (linux-image-4.19.0-6-amd64: root can lift kernel lockdown)
Your message dated Mon, 27 Apr 2020 04:00:09 + with message-id and subject line Bug#947021: fixed in linux 4.19.118-1 has caused the Debian Bug report #947021, regarding linux-image-4.19.0-6-amd64: root can lift kernel lockdown 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.) -- 947021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:linux Version: 4.19.67-2+deb10u2 Severity: normal Dear Maintainer, echoing "x" into /proc/sysrq-trigger disables kernel lockdown, even though it shouldn't. Kernel lockdown is meant to create a barrier between root and the kernel that can only be broken with physical access to the system. But a bug in debian/patches/features/all/lockdown/0002-Add-a-SysRq-option-to-lift-kernel-lockdown.patch allows root to easily circumvent this security measure: vagrant@buster:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 root=UUID=b9ffc3d1-86b2-4a2c-a8be-f2b2f4aa4cb5 ro net.ifnames=0 quiet lockdown vagrant@buster:~$ sudo dmesg | grep locked [0.00] Kernel is locked down from command line; see https://wiki.debian.org/SecureBoot vagrant@buster:~$ sudo sysctl kernel.sysrq=1 kernel.sysrq = 1 vagrant@buster:~$ sudo sh -c "echo x > /proc/sysrq-trigger" vagrant@buster:~$ sudo dmesg | tail [3.050592] vboxvideo :00:02.0: fb0: vboxdrmfb frame buffer device [3.068268] [drm] Initialized vboxvideo 1.0.0 20130823 for :00:02.0 on minor 0 [3.183323] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [3.223529] Adding 1045500k swap on /dev/sda5. Priority:-2 extents:1 across:1045500k FS [5.200670] e1000: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [5.201533] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 42.660726] sysrq: SysRq : [ 42.660728] This sysrq operation is disabled from userspace. [ 42.660797] Disabling Secure Boot restrictions [ 42.660830] Lifting lockdown I already reported this bug to Ubuntu at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851380 but it also affects Debian. (There's a bit more context and a patch in that bug report.) Looking at the patch on salsa I think that this bug doesn't just exist in Buster, but that's the version I used to test it. Best regards, Niklas Sombert -- Package-specific info: ** Version: Linux version 4.19.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 root=UUID=b9ffc3d1-86b2-4a2c-a8be-f2b2f4aa4cb5 ro net.ifnames=0 quiet lockdown ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [1.080252] Loading compiled-in X.509 certificates [1.123039] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [1.123062] Loaded X.509 cert 'Debian Secure Boot Signer: 00a7468def' [1.123095] zswap: loaded using pool lzo/zbud [1.123659] AppArmor: AppArmor sha1 policy hashing enabled [1.124095] rtc_cmos rtc_cmos: setting system clock to 2019-12-19 14:23:08 UTC (1576765388) [1.124123] Lockdown: Hibernation is restricted; see https://wiki.debian.org/SecureBoot [1.125951] Freeing unused kernel image memory: 1584K [1.148274] Write protecting the kernel read-only data: 16384k [1.150291] Freeing unused kernel image memory: 2028K [1.150967] Freeing unused kernel image memory: 772K [1.165327] x86/mm: Checked W+X mappings: passed, no W+X pages found. [1.165329] x86/mm: Checking user space page tables [1.173508] x86/mm: Checked W+X mappings: passed, no W+X pages found. [1.173511] Run /init as init process [1.274579] piix4_smbus :00:07.0: SMBus Host Controller at 0x4100, revision 0 [1.280038] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI [1.280040] e1000: Copyright (c) 1999-2006 Intel Corporation. [1.288044] SCSI subsystem initialized [1.297356] FDC 0 is an 82078. [1.306225] cryptd: max_cpu_qlen set to 1000 [1.317316] libata version 3.00 loaded. [1.323785] ahci :00:0d.0: version 3.0 [1.324687] ahci :00:0d.0: SSS flag set, parallel bus scan disabled [1.324882] ahci :00:0d.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode [1.324884] ahci :00:0d.0: flags: 64bit ncq stag only ccc [1.325243] scsi host0: ahci [1.325387] ata1: SATA max UDMA/133 abar m8192@0xf0804000 port 0xf0804100 irq 21 [1.336127] AVX2 version of gcm_enc/dec
Bug#944546: marked as done (linux-source: Require build and include Hisilicon Hibmc drm driver in the installer)
Your message dated Mon, 27 Apr 2020 04:00:09 + with message-id and subject line Bug#951274: fixed in linux 4.19.118-1 has caused the Debian Bug report #951274, regarding linux-source: Require build and include Hisilicon Hibmc drm driver in the installer 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.) -- 951274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951274 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-source Version: 4.19.0-6 Severity: important I'm trying to install Debian buster on to the Huawei Kunpeng arm64 server, found that the installation graphic output not show up via the server BMC virtual console. Huawei Kunpeng arm64 server using a hibmc chip on the mainboard, the lspci output of the VGA device is: ~$ lspci -nn | grep VGA 05:00.0 VGA compatible controller [0300]: Huawei Technologies Co., Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support] [19e5:1711] (rev 01) Currently the kernel VGA driver module (hibmc_drm.ko) was not included in the netboot initrd ( http://ftp.debian.org/debian/dists/stable/main/installer-arm64/20190702+deb10u1/images/netboot/netboot.tar.gz) . I have verified the BMC virtual console graphic output works well after adding the hibmc_drm.ko into the netboot initrd, could you please help to built and include this driver module in the installer? Thanks -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 4.19.0-6-arm64 (SMP w/96 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Kairui She --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.118-1 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 951...@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: Sun, 26 Apr 2020 14:04:11 +0100 Source: linux Architecture: source Version: 4.19.118-1 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 947021 951274 953017 955366 Changes: linux (4.19.118-1) buster; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.99 - Revert "efi: Fix debugobjects warning on 'efi_rts_work'" - xfs: Sanity check flags of Q_XQUOTARM call - [x86] mfd: intel-lpss: Add default I2C device properties for Gemini Lake - SUNRPC: Fix svcauth_gss_proxy_init() - [powerpc*] pseries: Enable support for ibm,drc-info property - tipc: update mon's self addr when node addr generated - tipc: fix wrong timeout input for tipc_wait_for_cond() - mt7601u: fix bbp version check in mt7601u_wait_bbp_ready - [armhf] crypto: sun4i-ss - fix big endian issues - perf map: No need to adjust the long name of modules - ipmi: Fix memory leak in __ipmi_bmc_register (CVE-2019-19046) - ixgbe: don't clear IPsec sa counters on HW clearing - drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset() - iio: fix position relative kernel version - apparmor: Fix network performance issue in aa_label_sk_perm - ALSA: hda: fix unused variable warning - apparmor: don't try to replace stale label in ptrace access check - firmware: coreboot: Let OF core populate platform device - bridge: br_arp_nd_proxy: set icmp6_router if neigh has NTF_ROUTER - [arm64] drm/hisilicon: hibmc: Don't overwrite fb helper surface depth - IB/rxe: replace kvfree with vfree - [amd64] IB/hfi1: Add mtu check for operational data VLs - genirq/debugfs: Reinstate full OF path for domain name - [arm64] usb: dwc3: add EXTCON dependency for qcom - cfg80211: regulatory: make
Bug#953017: marked as done (linux-image-amd64: Regression from "mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()")
Your message dated Mon, 27 Apr 2020 04:00:09 + with message-id and subject line Bug#953017: fixed in linux 4.19.118-1 has caused the Debian Bug report #953017, regarding linux-image-amd64: Regression from "mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()" 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.) -- 953017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-amd64 Version: 5.4.13-1~bpo10+1 Severity: important Tags: upstream patch Dear Maintainer, A performance regression stemming from the patch "mm/vmalloc: Sync unmappings in __purge_vmap_area_lazy()" in all mainline and current stable kernels, except 3.16.y, was reported by multiple persons [1]. The regression involves any activity that exercises vmalloc a lot, such as creating threads with CONFIG_VMAP_STACK=y or tty allocation (for example by SSH servers). A fix [2] for this was posted last October and was picked up in the -mm tree last November [3]. However this fix did not make it into v5.6-rc or any other release. It is still only in the -mm tree. AFAICT this regression only impacts x86 platforms, as it is the only platform that has a custom vmalloc_sync_all() instead of the standard no-op stub. As per my report to upstream, I currently have one production server running with the offending patch reverted. I also have another with the fix applied, and that seems to work well. Please consider adding the fix to Debian kernel images until upstream kernels have it. [1] https://www.spinics.net/lists/stable/msg349763.html [2] https://patchwork.kernel.org/patch/11181159/ [3] https://www.spinics.net/lists/mm-commits/msg141749.html -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armhf, i386, arm64 Kernel: Linux 5.2.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), LANGUAGE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages linux-image-amd64 depends on: ii linux-image-5.4.0-0.bpo.3-amd64 5.4.13-1~bpo10+1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: linux Source-Version: 4.19.118-1 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 953...@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: Sun, 26 Apr 2020 14:04:11 +0100 Source: linux Architecture: source Version: 4.19.118-1 Distribution: buster Urgency: medium Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Closes: 947021 951274 953017 955366 Changes: linux (4.19.118-1) buster; urgency=medium . * New upstream stable update: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.99 - Revert "efi: Fix debugobjects warning on 'efi_rts_work'" - xfs: Sanity check flags of Q_XQUOTARM call - [x86] mfd: intel-lpss: Add default I2C device properties for Gemini Lake - SUNRPC: Fix svcauth_gss_proxy_init() - [powerpc*] pseries: Enable support for ibm,drc-info property - tipc: update mon's self addr when node addr generated - tipc: fix wrong timeout input for tipc_wait_for_cond() - mt7601u: fix bbp version check in mt7601u_wait_bbp_ready - [armhf] crypto: sun4i-ss - fix big endian issues - perf map: No need to adjust the long name of modules - ipmi: Fix memory leak in __ipmi_bmc_register (CVE-2019-19046) - ixgbe: don't clear IPsec sa counters on HW clearing - drm/virtio: fix bounds check in virtio_gpu_cmd_get_capset() - iio: fix position relative kernel version - apparmor: Fix network performance issue in aa_label_sk_perm - ALSA: hda: fix unused variable warning -
Bug#711135: Submission Reopened: CLOUD COMPUTING 2020 || October 25 - 29, 2020 - Nice, France
Greetings, Note that CLOUD COMPUTING 2020 scheduled earlier in the year has been moved to October 25 - 29, 2020 in Nice, France. As such, we have additional time to reopen submissions to the conference. In order to accommodate a large number of situations, we are offering the option for either physical presence or virtual participation. We would be delighted if all authors manage to attend, but are aware that special circumstances are best handled by having flexible options. The new submission deadline is June 1. Please consider to contribute to and/or forward to the appropriate groups the following opportunity to submit and publish original scientific results to: - CLOUD COMPUTING 2020: The Eleventh International Conference on Cloud Computing, GRIDs, and Virtualization Authors of selected papers will be invited to submit extended article versions to one of the IARIA Journals: http://www.iariajournals.org = CLOUD COMPUTING 2020: The Eleventh International Conference on Cloud Computing, GRIDs, and Virtualization Event schedule: October 25 - 29, 2020 - Nice, France Main page: https://www.iaria.org/conferences2020/CLOUDCOMPUTING20.html Submission: https://www.iaria.org/conferences2020/SubmitCLOUDCOMPUTING20.html Contributions: - regular papers [in the proceedings, digital library] - short papers (work in progress) [in the proceedings, digital library] - ideas: two pages [in the proceedings, digital library] - extended abstracts: two pages [in the proceedings, digital library] - posters: two pages [in the proceedings, digital library] - posters: slide only [slide-deck posted at www.iaria.org] - presentations: slide only [slide-deck posted at www.iaria.org] - demos: two pages [posted at www.iaria.org] Deadlines Submission: June 1, 2020 Notification: July 1, 2020 Registration: July 14, 2020 Camera-ready: July 20, 2020 Call for papers: https://www.iaria.org/conferences2020/CfPCLOUDCOMPUTING20.html Committees: https://www.iaria.org/conferences2020/ComCLOUDCOMPUTING20.html Extended versions of selected papers will be published in IARIA Journals: http://www.iariajournals.org Print proceedings will be available via Curran Associates, Inc.: http://www.proceedings.com/9769.html Articles will be archived in the free access ThinkMind Digital Library: http://www.thinkmind.org The topics suggested by the conference can be discussed in term of concepts, state of the art, research, standards, implementations, running experiments, applications, and industrial case studies. Authors are invited to submit complete unpublished papers, which are not under review in any other conference or journal in the following, but not limited to, topic areas. All tracks are open to both research and industry contributions, in terms of Regular papers, Posters, Work in progress, Technical/marketing/business presentations, Demos, Tutorials, and Panels. Before submission, please check and comply with the editorial rules: http://www.iaria.org/editorialrules.html Topics: TRENDS: New trends Fog-computing; Mobile Edge Computing; Cloudlets; Hosted Cloud services (WebRTC, Containers, Cloud micro-services); Cloud computing and SDN/NFV; Cloud computing and 5G; Cloud computing and LTE Pro 4.5; Cloud computing ad Big Data; High performance computing (HPC) in the Cloud; Superfluid Clouds; Mobile Apps to the public Clouds; Vehicular Cloud networks; Cloud orchestration features; Converged edge systems; Cloud federation; Micro-cloud provider federation; Open-implementation Cloud infrastructures; Untrusted Cloud environments; Multiple Clouds and data centers; Power Constrained VMs; Cloud Green abstraction layer CLOUD: Cloud computing Cloud economics; Core cloud services; Cloud technologies; Cloud computing; On-demand computing models; Hardware-as-a-service; Software-as-a-service [SaaS applications]; Platform-as-service; Storage as a service in cloud; Data-as-a-Service; Service-oriented architecture (SOA); Cloud computing programming and application development; Scalability, discovery of services and data in Cloud computing infrastructures; Trust and clouds; Client-cloud computing challenges; Geographical constraints for deploying clouds CLOUD: Challenging features Privacy, security, ownership and reliability issues; Performance and QoS; Dynamic resource provisioning; Power-efficiency and Cloud computing; Load balancing; Application streaming; Cloud SLAs; Business models and pricing policies; Cloud service subscription models; Cloud standardized SLA; Cloud-related privacy; Cloud-related control; Managing applications in the clouds; Mobile clouds; Roaming services in Clouds; Agent-based cloud computing; Cloud brokering; Cloud contracts (machine readable); Cloud security; Security and assurance properties in cloud environments; Big Data Analytics in clouds; Cloud computing back-end solutions; Cloud applications portability; Cloud-native application design;
Bug#958300: linux: enable infiniband kconfig in cloud images for Azure/HyperV
Hi Luca On Mon, Apr 20, 2020 at 10:19:22AM +, Luca Boccassi wrote: > Azure VMs can get accelerated networking for DPDK applications via the > NETVSC driver (https://doc.dpdk.org/guides/nics/netvsc.html), but this > requires enabling the Infiniband kernel modules. I have to say, I'm not so sure this is actually the same thing. This linked documentation shows how to use DPDK on top of the netsvc device, using uio_hv_generic. What you are talking about is using DPDK on the Mellanox card, which is documented here: https://doc.dpdk.org/guides/nics/mlx4.html https://docs.microsoft.com/en-us/azure/virtual-network/setup-dpdk This requires the following modules: - mlx4_ib - ib_uverbs Regards, Bastian -- Women are more easily and more deeply terrified ... generating more sheer horror than the male of the species. -- Spock, "Wolf in the Fold", stardate 3615.4
linux_4.19.118-1_source.changes is NEW
Mapping buster to stable. Mapping stable to proposed-updates. binary:acpi-modules-4.19.0-9-686-di is NEW. binary:acpi-modules-4.19.0-9-686-pae-di is NEW. binary:acpi-modules-4.19.0-9-amd64-di is NEW. binary:affs-modules-4.19.0-9-4kc-malta-di is NEW. binary:affs-modules-4.19.0-9-5kc-malta-di is NEW. binary:affs-modules-4.19.0-9-loongson-3-di is NEW. binary:affs-modules-4.19.0-9-octeon-di is NEW. binary:ata-modules-4.19.0-9-4kc-malta-di is NEW. binary:ata-modules-4.19.0-9-5kc-malta-di is NEW. binary:ata-modules-4.19.0-9-686-di is NEW. binary:ata-modules-4.19.0-9-686-pae-di is NEW. binary:ata-modules-4.19.0-9-amd64-di is NEW. binary:ata-modules-4.19.0-9-arm64-di is NEW. binary:ata-modules-4.19.0-9-armmp-di is NEW. binary:ata-modules-4.19.0-9-loongson-3-di is NEW. binary:ata-modules-4.19.0-9-powerpc64le-di is NEW. binary:btrfs-modules-4.19.0-9-4kc-malta-di is NEW. binary:btrfs-modules-4.19.0-9-5kc-malta-di is NEW. binary:btrfs-modules-4.19.0-9-686-di is NEW. binary:btrfs-modules-4.19.0-9-686-pae-di is NEW. binary:btrfs-modules-4.19.0-9-amd64-di is NEW. binary:btrfs-modules-4.19.0-9-arm64-di is NEW. binary:btrfs-modules-4.19.0-9-armmp-di is NEW. binary:btrfs-modules-4.19.0-9-loongson-3-di is NEW. binary:btrfs-modules-4.19.0-9-marvell-di is NEW. binary:btrfs-modules-4.19.0-9-octeon-di is NEW. binary:btrfs-modules-4.19.0-9-powerpc64le-di is NEW. binary:btrfs-modules-4.19.0-9-s390x-di is NEW. binary:cdrom-core-modules-4.19.0-9-4kc-malta-di is NEW. binary:cdrom-core-modules-4.19.0-9-5kc-malta-di is NEW. binary:cdrom-core-modules-4.19.0-9-686-di is NEW. binary:cdrom-core-modules-4.19.0-9-686-pae-di is NEW. binary:cdrom-core-modules-4.19.0-9-amd64-di is NEW. binary:cdrom-core-modules-4.19.0-9-arm64-di is NEW. binary:cdrom-core-modules-4.19.0-9-armmp-di is NEW. binary:cdrom-core-modules-4.19.0-9-loongson-3-di is NEW. binary:cdrom-core-modules-4.19.0-9-marvell-di is NEW. binary:cdrom-core-modules-4.19.0-9-octeon-di is NEW. binary:cdrom-core-modules-4.19.0-9-powerpc64le-di is NEW. binary:cdrom-core-modules-4.19.0-9-s390x-di is NEW. binary:compress-modules-4.19.0-9-4kc-malta-di is NEW. binary:compress-modules-4.19.0-9-5kc-malta-di is NEW. binary:compress-modules-4.19.0-9-686-di is NEW. binary:compress-modules-4.19.0-9-686-pae-di is NEW. binary:compress-modules-4.19.0-9-amd64-di is NEW. binary:compress-modules-4.19.0-9-arm64-di is NEW. binary:compress-modules-4.19.0-9-armmp-di is NEW. binary:compress-modules-4.19.0-9-loongson-3-di is NEW. binary:compress-modules-4.19.0-9-marvell-di is NEW. binary:compress-modules-4.19.0-9-octeon-di is NEW. binary:compress-modules-4.19.0-9-powerpc64le-di is NEW. binary:compress-modules-4.19.0-9-s390x-di is NEW. binary:crc-modules-4.19.0-9-4kc-malta-di is NEW. binary:crc-modules-4.19.0-9-5kc-malta-di is NEW. binary:crc-modules-4.19.0-9-686-di is NEW. binary:crc-modules-4.19.0-9-686-pae-di is NEW. binary:crc-modules-4.19.0-9-amd64-di is NEW. binary:crc-modules-4.19.0-9-arm64-di is NEW. binary:crc-modules-4.19.0-9-armmp-di is NEW. binary:crc-modules-4.19.0-9-loongson-3-di is NEW. binary:crc-modules-4.19.0-9-marvell-di is NEW. binary:crc-modules-4.19.0-9-octeon-di is NEW. binary:crc-modules-4.19.0-9-powerpc64le-di is NEW. binary:crc-modules-4.19.0-9-s390x-di is NEW. binary:crypto-dm-modules-4.19.0-9-4kc-malta-di is NEW. binary:crypto-dm-modules-4.19.0-9-5kc-malta-di is NEW. binary:crypto-dm-modules-4.19.0-9-686-di is NEW. binary:crypto-dm-modules-4.19.0-9-686-pae-di is NEW. binary:crypto-dm-modules-4.19.0-9-amd64-di is NEW. binary:crypto-dm-modules-4.19.0-9-arm64-di is NEW. binary:crypto-dm-modules-4.19.0-9-armmp-di is NEW. binary:crypto-dm-modules-4.19.0-9-loongson-3-di is NEW. binary:crypto-dm-modules-4.19.0-9-marvell-di is NEW. binary:crypto-dm-modules-4.19.0-9-octeon-di is NEW. binary:crypto-dm-modules-4.19.0-9-powerpc64le-di is NEW. binary:crypto-dm-modules-4.19.0-9-s390x-di is NEW. binary:crypto-modules-4.19.0-9-4kc-malta-di is NEW. binary:crypto-modules-4.19.0-9-5kc-malta-di is NEW. binary:crypto-modules-4.19.0-9-686-di is NEW. binary:crypto-modules-4.19.0-9-686-pae-di is NEW. binary:crypto-modules-4.19.0-9-amd64-di is NEW. binary:crypto-modules-4.19.0-9-arm64-di is NEW. binary:crypto-modules-4.19.0-9-armmp-di is NEW. binary:crypto-modules-4.19.0-9-loongson-3-di is NEW. binary:crypto-modules-4.19.0-9-marvell-di is NEW. binary:crypto-modules-4.19.0-9-octeon-di is NEW. binary:crypto-modules-4.19.0-9-powerpc64le-di is NEW. binary:crypto-modules-4.19.0-9-s390x-di is NEW. binary:dasd-extra-modules-4.19.0-9-s390x-di is NEW. binary:dasd-modules-4.19.0-9-s390x-di is NEW. binary:efi-modules-4.19.0-9-686-di is NEW. binary:efi-modules-4.19.0-9-686-pae-di is NEW. binary:efi-modules-4.19.0-9-amd64-di is NEW. binary:efi-modules-4.19.0-9-arm64-di is NEW. binary:efi-modules-4.19.0-9-armmp-di is NEW. binary:event-modules-4.19.0-9-4kc-malta-di is NEW. binary:event-modules-4.19.0-9-5kc-malta-di is NEW. binary:event-modules-4.19.0-9-686-di is NEW. binary:event-modules-4.19.0-9-686-pae-di is NEW.
Processing of linux_4.19.118-1_source.changes
linux_4.19.118-1_source.changes uploaded successfully to localhost along with the files: linux_4.19.118-1.dsc linux_4.19.118.orig.tar.xz linux_4.19.118-1.debian.tar.xz linux_4.19.118-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#958904: linux-image-4.19.0-8-rpi: Please set CONFIG_RTC_DRV_DS1307=m
Package: src:linux Version: 4.19.98-1 Severity: wishlist Dear Maintainer, Raspberry Pi Model 1B I'm running this installation from does not have built-in RTC clock. DS1307-based RTCs are very popular addon for Raspberry Pi, and I happen to have one. The support of this particular chip is disabled in Debian kernels, so please consider building it as a module Sincerely yours, Reco -- Package-specific info: ** Version: Linux version 4.19.0-8-rpi (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 Debian 4.19.98-1 (2020-01-26) ** Command line: bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2708.boardrev=0x10 bcm2708.serial=0x631eea77 bcm2708.uart_clock=4800 bcm2708.disk_led_gpio=47 bcm2708.disk_led_active_low=0 smsc95xx.macaddr=B8:27:EB:1E:EA:77 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 console=tty0 console=ttyAMA0,115200 root=/dev/pi/root rw elevator=deadline fsck.repair=yes net.ifnames=0 cma=64M rootwait ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Hardware: BCM2835 Revision: Device Tree model: Raspberry Pi Model B Plus Rev 1.2 ** Loaded modules: cfg80211 rfkill 8021q garp stp mrp llc ip6t_REJECT nf_reject_ipv6 xt_mac nft_counter ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_comment nft_compat nf_tables nfnetlink nls_ascii nls_cp437 vfat fat vc4 smsc95xx snd_soc_core usbnet mii snd_pcm_dmaengine snd_pcm snd_timer snd raspberrypi_hwmon soundcore cec vchiq(C) bcm2835_rng rng_core leds_gpio zram zsmalloc auth_rpcgss sunrpc ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb dm_mod ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: 10.3 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: armel (armv6l) Kernel: Linux 4.19.0-8-rpi Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-8-rpi depends on: ii initramfs-tools [linux-initramfs-tool] 0.133+deb10u1 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-8-rpi recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 Versions of packages linux-image-4.19.0-8-rpi suggests: pn debian-kernel-handbook pn linux-doc-4.19 Versions of packages linux-image-4.19.0-8-rpi is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120190114-2 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
