[Kernel-packages] [Bug 1885862] Re: Add in-tree Realtek 8821CE wireless module support
https://lore.kernel.org/linux- wireless/20200616091625.26489-2-yhchu...@realtek.com/ already merged. We can start following process. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1885862 Title: Add in-tree Realtek 8821CE wireless module support Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-firmware source package in Focal: Triaged Status in linux-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-firmware source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: 8821ce is being upstreamed in https://lore.kernel.org/linux- wireless/20200603094218.19942-1-yhchu...@realtek.com/ . To backport it to ubuntu kernel so that we may obsolete the usage of rtl8821ce-dkms from https://bugs.launchpad.net/ubuntu/+source/rtl8821ce . To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1885862/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
proper fix hits mainline kernel $ git show 57b1aac1b426b7255afa195298ed691ffea204c6 commit 57b1aac1b426b7255afa195298ed691ffea204c6 Author: Longfang Liu Date: Mon Jun 8 22:01:11 2020 +0800 crypto: hisilicon - update SEC driver module parameter As stress-ng running SEC engine on the Ubuntu OS, we found that SEC only supports two threads each with one TFM based on the default module parameter 'ctx_q_num'. If running more threads, stress-ng will fail since it cannot get more TFMs. In order to fix this, we adjusted the default values of the module parameters to support more TFMs. Signed-off-by: Longfang Liu Signed-off-by: Zaibo Xu Signed-off-by: Herbert Xu ** Changed in: kunpeng920/upstream-kernel Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867900 Title: CPU stress test fails with focal kernel Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Bug description: [Impact] We have several crypto accelerators for Hisilicon 1620 but unfortunately one of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 makes kernel to run crypto functions without accelerator. [Fix] Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver. [Test] $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. == [Bug Description] CPU stress test fails with focal kernel [Steps to Reproduce] 1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable 2) sudo apt-add-repository -y ppa:hardware-certification/public 3) sudo apt install -y canonical-certification-server 4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux 5) Run CPU stress test with `sudo certify-advanced` [Actual Results] Failed with stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such device) [Expected Results] Passed [Reproducibility] 100% [Additional information] Same test with bionic-update kernel passed [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889080] Re: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3
Hi Alexander, in your tweet you mentioned it was "most likely a user mistake though". Can we deduce that this is a genuine issue on upgrade or was because of changes you made that caused this issue? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889080 Title: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux- image-gke 5.3 Status in Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, as summary says, today I got an upgrade to gke which broke my 18.04 oem install (dell xps 13)... After upgrade i had ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke5.3.0-1030.32~18.04 amd64 Signed kernel image GKE and had to use advanced boot options to get back to a usable setup... maybe useful: dpkg -l linux* | grep ^ii ii linux-base 4.5ubuntu1.2 all Linux image base package ii linux-firmware 1.173.19 all Firmware for Linux kernel drivers ii linux-headers-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-oem4.15.0.1093.96amd64 OEM Linux kernel headers ii linux-image-4.15.0-1030-oem 4.15.0-1030.35amd64 Signed kernel image oem ii linux-image-4.15.0-1091-oem 4.15.0-1091.101 amd64 Signed kernel image oem ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Signed kernel image GKE ii linux-image-oem 4.15.0.1093.96amd64 OEM Linux kernel image ii linux-libc-dev:amd64 4.15.0-112.113amd64 Linux Kernel Headers for development ii linux-libc-dev:i386 4.15.0-112.113i386 Linux Kernel Headers for development ii linux-modules-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-oem4.15.0.1093.96amd64 Complete OEM Linux kernel and headers ii linux-oem-headers-4.15.0-10304.15.0-1030.35all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10904.15.0-1090.100 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10914.15.0-1091.101 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10934.15.0-1093.103 all Header files related to Linux kernel version 4.15.0 ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems To manage notifications about this bug go to: https://bugs.launchpad.net/sputnik/+bug/1889080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Released Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Released Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889080] Re: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3
(see https://twitter.com/asacasa/status/1287746641815113730 ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889080 Title: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux- image-gke 5.3 Status in Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, as summary says, today I got an upgrade to gke which broke my 18.04 oem install (dell xps 13)... After upgrade i had ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke5.3.0-1030.32~18.04 amd64 Signed kernel image GKE and had to use advanced boot options to get back to a usable setup... maybe useful: dpkg -l linux* | grep ^ii ii linux-base 4.5ubuntu1.2 all Linux image base package ii linux-firmware 1.173.19 all Firmware for Linux kernel drivers ii linux-headers-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-oem4.15.0.1093.96amd64 OEM Linux kernel headers ii linux-image-4.15.0-1030-oem 4.15.0-1030.35amd64 Signed kernel image oem ii linux-image-4.15.0-1091-oem 4.15.0-1091.101 amd64 Signed kernel image oem ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Signed kernel image GKE ii linux-image-oem 4.15.0.1093.96amd64 OEM Linux kernel image ii linux-libc-dev:amd64 4.15.0-112.113amd64 Linux Kernel Headers for development ii linux-libc-dev:i386 4.15.0-112.113i386 Linux Kernel Headers for development ii linux-modules-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-oem4.15.0.1093.96amd64 Complete OEM Linux kernel and headers ii linux-oem-headers-4.15.0-10304.15.0-1030.35all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10904.15.0-1090.100 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10914.15.0-1091.101 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10934.15.0-1093.103 all Header files related to Linux kernel version 4.15.0 ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems To manage notifications about this bug go to: https://bugs.launchpad.net/sputnik/+bug/1889080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889080] Re: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux-image-gke 5.3
https://twitter.com/asacasa/status/1287692205029765121 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889080 Title: ubuntu 18.04 dell OEM install broke after it auto upgraded to linux- image-gke 5.3 Status in Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: Hi, as summary says, today I got an upgrade to gke which broke my 18.04 oem install (dell xps 13)... After upgrade i had ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke5.3.0-1030.32~18.04 amd64 Signed kernel image GKE and had to use advanced boot options to get back to a usable setup... maybe useful: dpkg -l linux* | grep ^ii ii linux-base 4.5ubuntu1.2 all Linux image base package ii linux-firmware 1.173.19 all Firmware for Linux kernel drivers ii linux-headers-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel headers for version 4.15.0 on 64 bit x86 SMP ii linux-headers-oem4.15.0.1093.96amd64 OEM Linux kernel headers ii linux-image-4.15.0-1030-oem 4.15.0-1030.35amd64 Signed kernel image oem ii linux-image-4.15.0-1091-oem 4.15.0-1091.101 amd64 Signed kernel image oem ii linux-image-4.15.0-1093-oem 4.15.0-1093.103 amd64 Signed kernel image oem ii linux-image-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Signed kernel image GKE ii linux-image-oem 4.15.0.1093.96amd64 OEM Linux kernel image ii linux-libc-dev:amd64 4.15.0-112.113amd64 Linux Kernel Headers for development ii linux-libc-dev:i386 4.15.0-112.113i386 Linux Kernel Headers for development ii linux-modules-4.15.0-1030-oem4.15.0-1030.35amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1091-oem4.15.0-1091.101 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-4.15.0-1093-oem4.15.0-1093.103 amd64 Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP ii linux-modules-5.3.0-1030-gke 5.3.0-1030.32~18.04.1 amd64 Linux kernel extra modules for version 5.3.0 on 64 bit x86 SMP ii linux-oem4.15.0.1093.96amd64 Complete OEM Linux kernel and headers ii linux-oem-headers-4.15.0-10304.15.0-1030.35all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10904.15.0-1090.100 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10914.15.0-1091.101 all Header files related to Linux kernel version 4.15.0 ii linux-oem-headers-4.15.0-10934.15.0-1093.103 all Header files related to Linux kernel version 4.15.0 ii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systems To manage notifications about this bug go to: https://bugs.launchpad.net/sputnik/+bug/1889080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815508] Re: Xorg freezes due to kernel hung task in the i915 driver
I'm assuming this is fixed in a later release like 20.04, but if not, reopen or file a new bug ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1815508 Title: Xorg freezes due to kernel hung task in the i915 driver Status in linux package in Ubuntu: Invalid Bug description: This bug is present in 18.04 and is triggered by specific actions, in particular, paging through image galleries in Eye of Gnome. When the bug is triggered, Xorg freezes completely and goes into the D (uninterruptible sleep) state. The machine continues to respond to ping and ssh. When triggering a shutdown or reboot over ssh, the shutdown process continues normally until most userspace processes (including systemd-journald) have been stopped, but then hangs. The system can still be rebooted with the magic sysrq technique. Here's some dmesg output: [0.00] Linux version 4.15.0-45-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 (Ubuntu 4.15.0-45.48-generic 4.15.18) [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/good--fortune--vg-root ro intel_iommu=igfx_off ### # This error happens regularly and may be irrelevant: ### [ 345.680936] [ cut here ] [ 345.680938] Failed to release pages: bind_count=1, pages_pin_count=1, pin_global=0 [ 345.680998] WARNING: CPU: 1 PID: 241 at /build/linux-uQJ2um/linux-4.15.0/drivers/gpu/drm/i915/i915_gem_userptr.c:89 cancel_userptr+0xe8/0xf0 [i915] [ 345.680999] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 xt_hl ip6t_rt intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass intel_cstate intel_rapl_perf eeepc_wmi asus_wmi sparse_keymap wmi_bmof nf_conntrack_ipv6 snd_hda_codec_hdmi nf_defrag_ipv6 snd_hda_codec_realtek snd_hda_codec_generic xt_limit uvcvideo xt_tcpudp xt_addrtype videobuf2_vmalloc snd_hda_intel snd_hda_codec videobuf2_memops videobuf2_v4l2 snd_hda_core snd_usb_audio videobuf2_core snd_usbmidi_lib joydev snd_hwdep videodev snd_rawmidi shpchp snd_seq_device media snd_pcm snd_timer input_leds usblp snd soundcore mei_me mei acpi_pad mac_hid sch_fq_codel nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi [ 345.681028] scsi_transport_iscsi coretemp ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack parport_pc ppdev lp parport iptable_filter ip_tables x_tables autofs4 btrfs zstd_compress algif_skcipher af_alg dm_crypt hid_microsoft raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i2c_algo_bit drm_kms_helper syscopyarea sysfillrect aesni_intel mxm_wmi sysimgblt fb_sys_fops e1000e aes_x86_64 crypto_simd ptp glue_helper nvme cryptd drm pps_core ahci nvme_core libahci wmi video [ 345.681059] CPU: 1 PID: 241 Comm: kworker/u8:5 Tainted: P O 4.15.0-45-generic #48-Ubuntu [ 345.681059] Hardware name: System manufacturer System Product Name/PRIME B250M-C, BIOS 1402 11/16/2018 [ 345.681081] Workqueue: i915-userptr-release cancel_userptr [i915] [ 345.681096] RIP: 0010:cancel_userptr+0xe8/0xf0 [i915] [ 345.681097] RSP: 0018:afc441edbe60 EFLAGS: 00010282 [ 345.681098] RAX: RBX: 8fb681b17600 RCX: 0006 [ 345.681099] RDX: 0007 RSI: 0082 RDI: 8fb6b6c96490 [ 345.681100] RBP: afc441edbe78 R08: 0001 R09: 03c4 [ 345.681101] R10: e28d5018ef80 R11: R12: 8fb681b177a8 [ 345.681101] R13: R14: 8fb698eba500 R15: [ 345.681102] FS: () GS:8fb6b6c8() knlGS: [ 345.681103] CS: 0010 DS: ES: CR0: 80050033 [ 345.681104] CR2: 7f18205d3857 CR3: 22e0a002 CR4: 003606e0 [ 345.681105] Call Trace: [ 345.681110] process_one_work+0x1de/0x410 [ 345.68] worker_thread+0x32/0x410 [ 345.681113] kthread+0x121/0x140 [ 345.681115] ? process_one_work+0x410/0x410 [ 345.681116] ? kthread_create_worker_on_cpu+0x70/0x70 [ 345.681119] ret_from_fork+0x35/0x40 [ 345.681120] Code: bf 46 ff ff eb c9 8b 93 c8 01 00 00 8b 8b a4 01 00 00 48 c7 c7 40 44 7a c0 8b b3 9c 01 00 00 c6 05 b5 56 10 00 01 e8 e8 2a fc fa <0f> 0b eb bc 0f 1f 40 00 0f 1f 44 00 00 55 ba 08 00 00 00 48 89 [ 345.681144] ---[
[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop
** Description changed: [Impact] On the LENOVO AMD renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch ucm-implement-CardNumberByName-substitution.patch ucm-fix-the-possible-buffer-overflow-substitution.patch ucm-simplify-get_by_card-in-parser.c.patch ucm-implement-AlwaysTrue-Condition.Type.patch ucm-Allow-empty-strings-in-var-.-substitutions.patch ucm-substitution-remove-duplicate-allow_empty-assign.patch ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch ucm-substitute-the-merged-tree-completely.patch add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols [Test Case] - On the AMD renoir machines: - Boot the system with these updated packages (already backported kernel - drivers to focal and oem-5.6 kernels), open the gnome-control-center, - we could see the digital mic in the input device tab, and only one - input device. we
[Kernel-packages] [Bug 1890222] Re: Enlarge hisi_sec2 capability
** Description changed: [Impact] - Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge the capability. + Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge the capability. [Fix] - https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg43093.html + commit 57b1aac1b426b7255afa195298ed691ffea204c6 + Author: Longfang Liu + Date: Mon Jun 8 22:01:11 2020 +0800 + Subject: crypto: hisilicon - update SEC driver module parameter [Test] $ lsmod | grep hisi_sec2 # make sure hisi_sec2 loaded $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890222 Title: Enlarge hisi_sec2 capability Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Bug description: [Impact] Current hisi_sec2 driver only allows 2 threads for accelerator but cpu stress test requires more then 50 threads. We have disabled hisi_sec2 temporarily for 20.04.1. Hisilicon proposes a simple patch on upstream mailing list to enlarge the capability. [Fix] commit 57b1aac1b426b7255afa195298ed691ffea204c6 Author: Longfang Liu Date: Mon Jun 8 22:01:11 2020 +0800 Subject: crypto: hisilicon - update SEC driver module parameter [Test] $ lsmod | grep hisi_sec2 # make sure hisi_sec2 loaded $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
I'm affected too. Noticed a few months back after updates resuming from suspend became obnoxiously slow, almost 2 minutes to resume the network interface. Meanwhile the system is trying to remount network drives and failing because there is no network so clearly the system isn't in sync with itself. Super obnoxious! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux-kernel-headers package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be
[Kernel-packages] [Bug 1842230] Re: [TGL] Enable SLP_S0_DEBUG debug facilities
these are already in 5.6 ** Changed in: linux-oem-5.6 (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-oem-5.6 (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1842230 Title: [TGL] Enable SLP_S0_DEBUG debug facilities Status in intel: Fix Committed Status in linux-oem-5.6 package in Ubuntu: Fix Released Bug description: Description Beginning in CNL, there are SLP_S0_DEBUG registers which expose, either on SLP_S0 exit or through manual latching, what pulled the system out of SLP_S0. Beginning with TGL (per the Cspec at time of writing, anyway) there are supposed to additional SLP_S0 debug registers for determining what cause the system to "wake" (or exit) from C10. Requirements: Expand the pmc_core driver to expose SLP_S0 debug details in debugfs Expand the pmc_core driver to expose SLP_S0_WAKE debug details in debugfs Target Release: 20.10 Target Kernel: 5.6 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1842230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
I installed the mutter libraries from focal proposed as described in #15 and the issue seems to be fixed. Also copied my ~/.config/monitors.xml to /var/lib/gdm/.config/monitors.xml and was able to get the same monitor configuration working at the login screen. So this is verified and finally works as it used to work in 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Kernel-packages] [Bug 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 That's a new bug so please log it as such. Though if you are using Pop!OS then it's not a bug at all, since System76 has now removed the feature from their package. If you are using regular Ubuntu then please open a new bug by running: ubuntu-bug mutter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1870758 Title: [nvidia] Display scaling results in a blank screen (power save state) Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Working on fully updated focal fossy Procedure to make bug happen: 1. open gnome control center and select screen (skærme in danish) 2. click the "fractional scaling" switch 3. select 150% scaling and click the green button at top right 4. Result is a blank screen and the monitor going into a power save state A reboot doesn't help. The login screen appears, when I log in the screen goes blank again and the monitor power save kicks in. If I select the "unity" environment, the display does work. If I do this on the command line "gsettings set org.gnome.mutter experimental-features ['']", I can log in as usual and fractional scaling has been turned off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 12:11:39 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
Bot accidentally set groovy for fix released but this patch only released by focal kernel. Reset status accordingly. Also set groovy status to invalid and create new bug (bug 1890222) to track for proper fix. ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Groovy) Status: Fix Released => Invalid ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Released ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: ubuntu-18.04.5-sru-1 => ubuntu-18.04.5 ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: Fix Committed => Fix Released ** Changed in: kunpeng920 Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867900 Title: CPU stress test fails with focal kernel Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Bug description: [Impact] We have several crypto accelerators for Hisilicon 1620 but unfortunately one of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 makes kernel to run crypto functions without accelerator. [Fix] Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver. [Test] $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. == [Bug Description] CPU stress test fails with focal kernel [Steps to Reproduce] 1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable 2) sudo apt-add-repository -y ppa:hardware-certification/public 3) sudo apt install -y canonical-certification-server 4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux 5) Run CPU stress test with `sudo certify-advanced` [Actual Results] Failed with stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such device) [Expected Results] Passed [Reproducibility] 100% [Additional information] Same test with bionic-update kernel passed [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: ubuntu-18.04.5 => ubuntu-18.04.4-sru-7 ** Changed in: linux (Ubuntu Groovy) Assignee: Ike Panhc (ikepanhc) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867900 Title: CPU stress test fails with focal kernel Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Bug description: [Impact] We have several crypto accelerators for Hisilicon 1620 but unfortunately one of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 makes kernel to run crypto functions without accelerator. [Fix] Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver. [Test] $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. == [Bug Description] CPU stress test fails with focal kernel [Steps to Reproduce] 1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable 2) sudo apt-add-repository -y ppa:hardware-certification/public 3) sudo apt install -y canonical-certification-server 4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux 5) Run CPU stress test with `sudo certify-advanced` [Actual Results] Failed with stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such device) [Expected Results] Passed [Reproducibility] 100% [Additional information] Same test with bionic-update kernel passed [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
This helped me: https://linuxconfig.org/how-to-install-the-nvidia- drivers-on-ubuntu-20-04-focal-fossa-linux sudo add-apt-repository ppa:graphics-drivers/ppa ubuntu-drivers devices sudo apt install nvidia-driver-450 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64
[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b "s390/cpum_cf: Add new extended counters for IBM z15" [Test Case] * Requires the fix/patch of the perf tool, as mentioned in the bug, too. * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * This requires a patch to be included into the perf itself, too - please see bug description for more details. * Since this patch is upstream in kernel 5.7 it will automatically land in groovy. __ ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867588] Re: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/upstream-kernel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867588 Title: [SFC-0316]sync mainline kernel 5.7rc1 SFC patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] SFC patchset have merged into mainline 5.7RC1rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] spi: HiSilicon v3xx: Use DMI quirk to set controller buswidth override bits spi: HiSilicon v3xx: Properly set CMD_CONFIG for Dual/Quad modes spi: Allow SPI controller override device buswidth To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Update Released
The verification of the Stable Release Update for iproute2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Released Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1
[Kernel-packages] [Bug 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 Nvidia 1080 with two 4K screens. After updating to 440 i only have lost fraction scaling, gnome settings only shows 100,200,300,400. The old experimental flag does not work (xorg). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1870758 Title: [nvidia] Display scaling results in a blank screen (power save state) Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Working on fully updated focal fossy Procedure to make bug happen: 1. open gnome control center and select screen (skærme in danish) 2. click the "fractional scaling" switch 3. select 150% scaling and click the green button at top right 4. Result is a blank screen and the monitor going into a power save state A reboot doesn't help. The login screen appears, when I log in the screen goes blank again and the monitor power save kicks in. If I select the "unity" environment, the display does work. If I do this on the command line "gsettings set org.gnome.mutter experimental-features ['']", I can log in as usual and fractional scaling has been turned off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 12:11:39 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867586] Re: [hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/upstream-kernel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867586 Title: [hns3-0316]sync mainline kernel 5.6rc4 hns3 patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] hns3 patchset have merged into mainline 5.6rc1 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] net: hns3: clear port base VLAN when unload PF net: hns3: fix RMW issue for VLAN filter switch net: hns3: fix VF VLAN table entries inconsistent issue net: hns3: fix "tc qdisc del" failed issue net: hns3: reject unsupported coalescing params net: hns3: delete unnecessary logs after kzalloc fails net: hns3: synchronize some print relating to reset issue net: hns3: print out command code when dump fails in debugfs net: hns3: print out status register when VF receives unknown source interrupt net: hns3: add a check before PF inform VF to reset net: hns3: delete some reduandant code net: hns3: remove an unnecessary resetting check in hclge_handle_hw_ras_error() net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH net: hns3: fix some mixed type assignment net: hns3: fix a not link up issue when fibre port supports autoneg net: hns3: add missing help info for QS shaper in debugfs net: hns3: add support for dump MAC ID and loopback status in debugfs net: hns3: add enabled TC numbers and DWRR weight info in debugfs net: hns3: modify an unsuitable print when setting unknown duplex to fibre [Status] (Rejected) net: hns3: reject unsupported coalescing params (Fix committed) net: hns3: delete unnecessary logs after kzalloc fails (Fix committed) net: hns3: synchronize some print relating to reset issue (Fix committed) net: hns3: print out command code when dump fails in debugfs (Fix committed) net: hns3: print out status register when VF receives unknown source interrupt (Fix committed) net: hns3: add a check before PF inform VF to reset (Fix committed) net: hns3: delete some reduandant code (Fix committed) net: hns3: remove an unnecessary resetting check in hclge_handle_hw_ras_error() (Fix committed) net: hns3: rename macro HCLGE_MAX_NCL_CONFIG_LENGTH (Fix committed) net: hns3: fix some mixed type assignment (Fix committed) net: hns3: add missing help info for QS shaper in debugfs (Fix committed) net: hns3: add support for dump MAC ID and loopback status in debugfs (Fix committed) net: hns3: add enabled TC numbers and DWRR weight info in debugfs (Fix committed) net: hns3: modify an unsuitable print when setting unknown duplex to fibre (Fix committed) net: hns3: clear port base VLAN when unload PF (Fix committed) net: hns3: fix RMW issue for VLAN filter switch (Fix committed) net: hns3: fix VF VLAN table entries inconsistent issue (Fix committed) net: hns3: fix "tc qdisc del" failed issue (Fix committed) net: hns3: fix a not link up issue when fibre port supports autoneg To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
This bug was fixed in the package iproute2 - 4.15.0-2ubuntu1.2 --- iproute2 (4.15.0-2ubuntu1.2) bionic; urgency=medium * tc filter show tcp_flags wrong mask value (LP: #1873961) - d/p/lp1873961-tc-fix-bugs-for-tcp_flags-and-ip_attr-hex-output.patch -- Stefan Bader Wed, 15 Jul 2020 17:16:31 +0200 ** Changed in: iproute2 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Released Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go
[Kernel-packages] [Bug 1864950] Re: [roce-0227]sync mainline kernel 5.6rc3 roce patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/upstream-kernel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864950 Title: [roce-0227]sync mainline kernel 5.6rc3 roce patchset into ubuntu HWE kernel branch Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: [Bug Description] roce patchset have merged into mainline 5.6rc2 kernel. [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] RDMA/hns: Optimize eqe buffer allocation flow RDMA/hns: Cleanups of magic numbers RDMA/hns: fix spelling mistake: "attatch" -> "attach" RDMA/hns: Delayed flush cqe process with workqueue RDMA/hns: Add the workqueue framework for flush cqe handler RDMA/hns: Initialize all fields of doorbells to zero RDMA/hns: Optimize qp doorbell allocation flow RDMA/hns: Optimize kernel qp wrid allocation flow RDMA/hns: Optimize qp param setup flow RDMA/hns: Optimize qp buffer allocation flow RDMA/hns: Optimize qp number assign flow RDMA/hns: Optimize qp context create and destroy flow RDMA/hns: Optimize qp destroy flow RDMA/hns: Stop doorbell update while qp state error RDMA/hns: Use flush framework for the case in aeq RDMA/hns: Treat revision HIP08_A as a special case https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=wip /jgg-for-next RDMA/hns: Treat revision HIP08_A as a special case https://www.spinics.net/lists/linux-rdma/msg89428.html RDMA/hns: Support to set mininum depth of qp to 0 https://patchwork.kernel.org/patch/11415067/ To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1864950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
*** This bug is a duplicate of bug 1826125 *** https://bugs.launchpad.net/bugs/1826125 ** This bug has been marked a duplicate of bug 1826125 Dell XPS 13 9380 flickering (Whiskey Lake) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake Status in linux package in Ubuntu: Confirmed Bug description: I just received a new Dell XPS 13 7390 laptop. With factory preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely distorted. The display would constantly flicker with areas of the display staying black or showing patterns of square color blocks. Booting in recovery mode worked, though and I was able to install all updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non-recovery mode persisted after installing all updates. I then updated to Ubuntu 19.04 and changed to "generic" linux kernel image without success: Problem persisted, only recovery mode was usable. I updated once more to 19.10 again without any success. From the perhaps related bug #1849947 I tried latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ drm-tip kernel solves the issue for first boot, but after resuming from suspend, the same issues display issues occur. Kernel images I tried: - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics output without "nomodeset" - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output without "nomodeset" - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output without "nomodeset" - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted graphics output after resuming from suspend ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.4.0-994-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 18:51:15 2019 DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-11-25 (13 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Summary changed: - Make digital mic on the AMD renoir machines work under gnome desktop + Make digital mic on the AMD Renoir machines work under gnome desktop ** Description changed: [Impact] - On the LENOVO AMD renoir machines, there is a digital mic directly + On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch ucm-implement-CardNumberByName-substitution.patch ucm-fix-the-possible-buffer-overflow-substitution.patch ucm-simplify-get_by_card-in-parser.c.patch ucm-implement-AlwaysTrue-Condition.Type.patch ucm-Allow-empty-strings-in-var-.-substitutions.patch ucm-substitution-remove-duplicate-allow_empty-assign.patch ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch ucm-substitute-the-merged-tree-completely.patch add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols [Test Case] On the AMD Renoir machines:
[Kernel-packages] [Bug 1863603] Re: [comet lake] Screen is scrambled/distored and flickers
*** This bug is a duplicate of bug 1826125 *** https://bugs.launchpad.net/bugs/1826125 ** This bug is no longer a duplicate of bug 1855608 Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake ** This bug has been marked a duplicate of bug 1826125 Dell XPS 13 9380 flickering (Whiskey Lake) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863603 Title: [comet lake] Screen is scrambled/distored and flickers Status in linux package in Ubuntu: New Bug description: The screen is distorted/scrambled every now and then. That is, it's like a few lines of pixels are repeated (so it's a normally a blur). The screen also flickers at times. This happens a few times a few. I've noticed that if I close the lid and let the screen dim/blank/suspend then normally is goes back to normal when it wakes up. To my knowledge his happens irrespective of what programs I use at the time. Dell XPS 13 (7390). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 17 12:32:42 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-29-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-12-24 (54 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 ro resume=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 resume_offset=67694592 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/03/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890194] Re: package linux-modules-5.4.0-42-generic (not installed) failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/modules/5.4.0-42-generic/kernel/cry
English: package linux-modules-5.4.0-42-generic (not installed) failed to install / upgrade: unable to copy extracted data "./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" to "/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg- new": unexpected end of file or stream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890194 Title: package linux-modules-5.4.0-42-generic (not installed) failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do "/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg- new": niespodziewany koniec pliku lub strumienia Status in linux package in Ubuntu: Confirmed Bug description: I faced this during regular update of Ubuntu. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-42-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: linux-modules-5.4.0-42-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gdm1217 F pulseaudio michal 2302 F pulseaudio /dev/snd/controlC0: gdm1217 F pulseaudio michal 2302 F pulseaudio CasperMD5CheckResult: skip Date: Mon Aug 3 22:02:38 2020 DpkgHistoryLog: Start-Date: 2020-08-03 22:02:38 Commandline: apt-get install -f Requested-By: michal (1000) Install: linux-modules-5.4.0-42-generic:amd64 (5.4.0-42.46, automatic) ErrorMessage: nie można skopiować wypakowanych danych "./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do "/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-new": niespodziewany koniec pliku lub strumienia InstallationDate: Installed on 2020-04-24 (101 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. H370HD3 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=7235dcc7-ba5b-41ad-b76a-f18c4b11b203 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-modules-5.4.0-42-generic (not installed) failed to install/upgrade: nie można skopiować wypakowanych danych "./lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko" do "/lib/modules/5.4.0-42-generic/kernel/crypto/streebog_generic.ko.dpkg-new": niespodziewany koniec pliku lub strumienia UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F14 dmi.board.asset.tag: Default string dmi.board.name: H370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF14:bd06/05/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H370HD3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888894] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/194 Title: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically Status in linux package in Ubuntu: Fix Released Bug description: Hello, For the past several months, I noticed my wifi just drops periodically. Disabling bluetooth reduces the frequency of this. Also Ive noticed speed is slower on wifi for my 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). this problem affects others too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1741 F pulseaudio /dev/snd/controlC0: steve 1741 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859756] Re: [hns3-0115] add 8 BD limit for tx flow
** Tags removed: ikeradar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859756 Title: [hns3-0115] add 8 BD limit for tx flow Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] We get reports that iscsi and spark tests fail on hns3 [Fix] Cherry-pick/backport patches from upstream. net: hns3: add 8 BD limit for tx flow net: hns3: avoid mult + div op in critical data path net: hns3: remove some ops in struct hns3_nic_ops net: hns3: fix for not calculating tx bd num correctly net: hns3: unify maybe_stop_tx for TSO and non-TSO case net: hns3: add check for max TX BD num for tso and non-tso case net: hns3: fix for TX queue not restarted problem net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() [Test] No known way to reproduce it in our lab. Regression test only. [Regression Potential] Patchset only affects hns3 driver. Minimal risk for other drivers and platform. [Bug Description] A single transmit packet can span up to 8 descriptors, TSO transmit packet can be stored up to 63 descriptors and each segment within the TSO should be spanned up to 8 descriptors. If the packet needs more than 8 BD, and the total size of every 7 continuous frags more than MSS, HW does not support it, and it need driver makes SKB Linearized. [Actual Results] iscsi and bigdata spark test OK [Expected Results] iscsi and bigdata spark test OK [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA DTS2018091810050 [Resolution] SW use skb_copy to merge frag; 51e8439f3496 net: hns3: add 8 BD limit for tx flow 5f543a54eec0 net: hns3: fix for not calculating tx bd num correctly To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867900] Re: CPU stress test fails with focal kernel
** Tags removed: ikeradar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867900 Title: CPU stress test fails with focal kernel Status in kunpeng920: Fix Released Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Bug description: [Impact] We have several crypto accelerators for Hisilicon 1620 but unfortunately one of them is not mature and causes stress-ng tests failure. Disabling hisi_sec2 makes kernel to run crypto functions without accelerator. [Fix] Disable CONFIG_CRYPTO_DEV_HISI_SEC2 temporarily until we have proper driver. [Test] $ sudo stress-ng --aggressive --verify --timeout 330 --metrics-brief --tz --times --af-alg 0 $ echo $? [Regression Potential] This driver is only loaded on Hisilicon Hi1620 machines. Low risk for other platform. == [Bug Description] CPU stress test fails with focal kernel [Steps to Reproduce] 1) sudo apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable 2) sudo apt-add-repository -y ppa:hardware-certification/public 3) sudo apt install -y canonical-certification-server 4) Install focal kernel debs from https://launchpad.net/ubuntu/+source/linux 5) Run CPU stress test with `sudo certify-advanced` [Actual Results] Failed with stress-ng: fail: [6118] stress-ng-af-alg: bind failed, errno=19 (No such device) [Expected Results] Passed [Reproducibility] 100% [Additional information] Same test with bionic-update kernel passed [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1867900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888297] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1888297 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888297 Title: usb camera only works once until reset Status in linux package in Ubuntu: Incomplete Bug description: I have a usb camera (SDI camera, attached to magewell usb capture) which only works once. It displays the image in something like OBS Studio or ffplay, and works perfectly. I can stop the capture. Then trying to open the camera a second time does not work, I get a black screen in ffplay/OBS. To fix this, I can unplug the device and plug it back in, at which point it works until stopped and restarted. So basically, I always have to unplug it and plug it back in after stopping otherwise it won't display an image a second time. Debian 10 works perfectly fine using same physical hardware and video software, but using (x)ubuntu 20.04 I get the problem as noted above. So I suspect a kernel bug/regression. I'm using an AMD 16 core system but don't know if it's related to that. It makes no difference whether I use the USB ports on the motherboard (USB 3.1), or whether I use an addon USB 3.1 PCI card. (And debian doesn't care either which usb port I use, it works correctly there across the board). I have no idea how to report more information. I've done the software updates etc., so whatever kernel is running in 20.04 as of this date, that's what I'm using now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
That's something I already tried (removing the NV driver), but that didn't help either. I belive that some part of the tools needed for kernel preparation is broken.. I will try the instalation of Ubuntu 20.4 LTS next weekend. As far as I could see now all programms I use are available for this release. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1890136] Re: Return value in rtnetlink.sh from kselftests/net will be override in the last test
Patchset submitted to upstream
https://lore.kernel.org/linux-kselftest/20200804101803.23062-1-po-hsu@canonical.com/T/#m0a921714d68df807c118cbf29ade300ccdd8b4b7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1890136
Title:
Return value in rtnetlink.sh from kselftests/net will be override in
the last test
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Incomplete
Bug description:
In this test, it uses ret to store the return value of each test.
However, this value will be reset to 0 in the beginning of each test.
In the end of this test, it will judge PASS/FAIL base on this value.
Thus this will cause false-negative in some cases.
Below is an example for the test on Bionic OEM-OSP1, test "ip6erspan",
"erspan", "ip6gretap" failed with return value 255, but the return value will
soon be overridden with 0 if following test passed without any issue (I made
the test to print === RET $ret === line for debugging purpose):
PASS: policy routing
=== RET 0 ===
PASS: route get
=== RET 0 ===
PASS: preferred_lft addresses have expired
=== RET 0 ===
PASS: tc htb hierarchy
=== RET 0 ===
PASS: gre tunnel endpoint
=== RET 0 ===
PASS: gretap
=== RET 0 ===
Usage: ... { ip6gre | ip6gretap | ip6erspan} [ remote ADDR ]
[ local ADDR ]
[ [i|o]seq ]
[ [i|o]key KEY ]
[ [i|o]csum ]
[ hoplimit TTL ]
[ encaplimit ELIM ]
[ tclass TCLASS ]
[ flowlabel FLOWLABEL ]
[ dscp inherit ]
[ fwmark MARK ]
[ dev PHYS_DEV ]
[ noencap ]
[ encap { fou | gue | none } ]
[ encap-sport PORT ]
[ encap-dport PORT ]
[ [no]encap-csum ]
[ [no]encap-csum6 ]
[ [no]encap-remcsum ]
[ erspan IDX ]
Where: ADDR := IPV6_ADDRESS
TTL := { 0..255 } (default=64)
KEY := { DOTTED_QUAD | NUMBER }
ELIM := { none | 0..255 }(default=4)
TCLASS:= { 0x0..0xff | inherit }
FLOWLABEL := { 0x0..0xf | inherit }
MARK := { 0x0..0x | inherit }
Cannot find device "ip6gretap00"
FAIL: ip6gretap
=== RET 255 ===
Usage: ... { gre | gretap | erspan } [ remote ADDR ]
[ local ADDR ]
[ [i|o]seq ]
[ [i|o]key KEY ]
[ [i|o]csum ]
[ ttl TTL ]
[ tos TOS ]
[ [no]pmtudisc ]
[ [no]ignore-df ]
[ dev PHYS_DEV ]
[ noencap ]
[ encap { fou | gue | none } ]
[ encap-sport PORT ]
[ encap-dport PORT ]
[ [no]encap-csum ]
[ [no]encap-csum6 ]
[ [no]encap-remcsum ]
[ external ]
[ fwmark MARK ]
[ erspan IDX ]
Where: ADDR := { IP_ADDRESS | any }
TOS := { NUMBER | inherit }
TTL := { 1..255 | inherit }
KEY := { DOTTED_QUAD | NUMBER }
MARK := { 0x0..0x }
Cannot find device "erspan00"
Cannot find device "erspan00"
Cannot find device "erspan00"
Usage: ... { gre | gretap | erspan } [ remote ADDR ]
[ local ADDR ]
[ [i|o]seq ]
[ [i|o]key KEY ]
[ [i|o]csum ]
[ ttl TTL ]
[ tos TOS ]
[ [no]pmtudisc ]
[ [no]ignore-df ]
[ dev PHYS_DEV ]
[ noencap ]
[ encap { fou | gue | none } ]
[ encap-sport PORT ]
[ encap-dport PORT ]
[ [no]encap-csum ]
[ [no]encap-csum6 ]
[ [no]encap-remcsum ]
[ external ]
[ fwmark MARK ]
[Kernel-packages] [Bug 1884981] Re: Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably fails from any given boot
Launchpad has imported 9 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=208171. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-06-14T22:21:02+00:00 peteole2707 wrote: On my lenovo ideapad 5 14ARE05 random decides whether the touchpad works or not, but it stays the same until a second boot. Unlike the 15 inch version it has the following touchpad: Device 'MSFT0004:00 06CB:CD98 Touchpad': When it does not work, I get the following kernel error every few seconds: i2c_designware AMDI0010:00: controller timed out It is recognized by xinput in inoperational condition as well. However, the behavior is not totally random. Chances are much better if I shut the computer down and then power it on after a few seconds compared to hitting the reboot button. I am using manjaro linux, but also tried ubuntu and fedora, it's the same on all distros as well as on the 5.6 kernel. I have been wondering if it is possible to completely restart the touchpad until it works, but I could not find out which component need to be restarted for that and how to do it. This would be a great functionality to fix all kinds of hardware bugs. Another idea would be to find out what makes the touchpad go into the working or not working state. I would be pleased for any ideas. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/comments/0 On 2020-06-27T07:47:57+00:00 louismichel wrote: I have the same touchpad issues with the same laptop IdeaPad 5 14ARE05 I added the kernel boot parameters: "dynbg=file drivers/input/* +pt" i8042.debug=1 i8042.nopnp=1 log_buf_len=32M Then I could get the following logs: On kernel 5.7.6: (no touchpad at all) i2c_hid i2c-MSFT0004:00: HID over i2c has not been provided an Int IRQ i2c_hid: probe of i2c-MSFT0004:00 failed with error -22 On kernel 5.8.2-rc2 mainline: (touchpad acting limited) i2c_hid i2c-MSFT0004:00: supply vdd not found, using dummy regulator i2c_hid i2c-MSFT0004:00: supply vddl not found, using dummy regulator i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input13 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input14 hid-generic 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. input: MSFT0004:00 06CB:CD98 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input16 input: MSFT0004:00 06CB:CD98 Touchpad as /devices/platform/AMDI0010:00/i2c-0/i2c-MSFT0004:00/0018:06CB:CD98.0001/input/input17 hid-multitouch 0018:06CB:CD98.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0004:00 06CB:CD98] on i2c-MSFT0004:00 Hope that can helps us all find a fix for that issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/comments/6 On 2020-06-27T12:08:57+00:00 peteole2707 wrote: Thanks! I also realized that chances are better for the touchpad to work if it worked on the last boot. I believe the kernel does strange things with it when it spams me with "controller timed out" messages on shutdown. I wrote a script which prevents the system from having these shutdown issues. It unloads some modules and then reloads them. Unfortunately it only helps for the next boot, the touchpad is never even recognized after running it. sudo modprobe -r i2c_hid sudo modprobe -r i2c_piix4 sudo modprobe -r hid_multitouch sudo modprobe i2c_hid sudo modprobe i2c_piix4 sudo modprobe hid_multitouch It helps to break "bad boot streaks" Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/comments/7 On 2020-06-28T06:56:38+00:00 louismichel wrote: Interesting find indeed when doing sudo modprobe -r i2c_hid sudo modprobe i2c_hid The "controller timed out" messages stops. Although that does not fix the touchpad it does suggest that this module is at cause. After further digging, I got another set of log after booting on mainline (appended below). Basically, I see that the following shows up first before the "time out spamming" starts: i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration i2c_designware AMDI0010:00: controller timed out i2c_hid i2c-MSFT0004:00: failed to retrieve report from device. Now, I found these 3 exact log messages in this commit to fix another DELL Win8 touchpad in
Re: [Kernel-packages] [Bug 1888894] Re: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically
Hello, Though this bug is fixed for me. I know that others still experience this. I am part of an ubuntu group on facebook. I constantly see posts of people losing wifi once theyre computer wakes up from standby. I post my fix to use stacer to disable bluetooth and change your power saving options. See I initially had this issue happen alot and I was told to disable bluetooth. But I also found i had to change my power saving options. It still happened every now and then after that but not as often. Basically the computer goes in airplane mode. I wondering if network manager controls bluetooth and wifi. Anyways I just thought id voice this knowledge to you. In all regards it is fixed from my end. ps i really appreciate the work you guys do to make such a robust OS. :) -hope this helps On 2020-08-04 4:08 p.m., Alex Hung wrote: > ** Changed in: linux (Ubuntu) > Status: Confirmed => Fix Released > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/194 Title: Qualcomm Atheros QCA9377 [168c:0042] Subsystem [1028:1810] Ubuntu 20.04: wifi drops and speed is degraded periodically Status in linux package in Ubuntu: Fix Released Bug description: Hello, For the past several months, I noticed my wifi just drops periodically. Disabling bluetooth reduces the frequency of this. Also Ive noticed speed is slower on wifi for my 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). this problem affects others too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: steve 1741 F pulseaudio /dev/snd/controlC0: steve 1741 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-21 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Dell Inc. Inspiron 5765 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5659d383-5314-42cf-907e-2116ea6b8145 ro ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 0DM01M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.1.1 dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd07/17/2017:svnDellInc.:pnInspiron5765:pvr1.1.1:rvnDellInc.:rn0DM01M:rvrA00:cvnDellInc.:ct10:cvr1.1.1: dmi.product.family: Inspiron dmi.product.name: Inspiron 5765 dmi.product.sku: 076A dmi.product.version: 1.1.1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890343] [NEW] Focal update: v5.4.55 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.55 upstream stable release from git://git.kernel.org/ AX.25: Fix out-of-bounds read in ax25_connect() AX.25: Prevent out-of-bounds read in ax25_sendmsg() dev: Defer free of skbs in flush_backlog drivers/net/wan/x25_asy: Fix to make it work ip6_gre: fix null-ptr-deref in ip6gre_init_net() net-sysfs: add a newline when printing 'tx_timeout' by sysfs net: udp: Fix wrong clean up for IS_UDPLITE macro qrtr: orphan socket in qrtr_release() rtnetlink: Fix memory(net_device) leak when ->newlink fails rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA tcp: allow at most one TLP probe per flight AX.25: Prevent integer overflows in connect and sendmsg sctp: shrink stream outq only when new outcnt < old outcnt sctp: shrink stream outq when fails to do addstream reconf udp: Copy has_conns in reuseport_grow(). udp: Improve load balancing for SO_REUSEPORT. regmap: debugfs: check count when read regmap file PM: wakeup: Show statistics for deleted wakeup sources again Revert "dpaa_eth: fix usage as DSA master, try 3" Linux 5.4.55 UBUNTU: upstream stable to v5.4.55 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.55 upstream stable release + from git://git.kernel.org/ -v5.4.55 upstream stable release -from git://git.kernel.org/ + AX.25: Fix out-of-bounds read in ax25_connect() + AX.25: Prevent out-of-bounds read in ax25_sendmsg() + dev: Defer free of skbs in flush_backlog + drivers/net/wan/x25_asy: Fix to make it work + ip6_gre: fix null-ptr-deref in ip6gre_init_net() + net-sysfs: add a newline when printing 'tx_timeout' by sysfs + net: udp: Fix wrong clean up for IS_UDPLITE macro + qrtr: orphan socket in qrtr_release() + rtnetlink: Fix memory(net_device) leak when ->newlink fails + rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA + tcp: allow at most one TLP probe per flight + AX.25: Prevent integer overflows in connect and sendmsg + sctp: shrink stream outq only when new outcnt < old outcnt + sctp: shrink stream outq when fails to do addstream reconf + udp: Copy has_conns in reuseport_grow(). + udp: Improve load balancing for SO_REUSEPORT. + regmap: debugfs: check count when read regmap file + PM: wakeup: Show statistics for deleted wakeup sources again + Revert "dpaa_eth: fix usage as DSA master, try 3" + Linux 5.4.55 + UBUNTU: upstream stable to v5.4.55 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890343 Title: Focal update: v5.4.55 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: Confirmed Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
Attached is a fix for s390x that is also built at my ppa:cascardo/kdump2. ** Patch added: "Fix for groovy" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877533/+attachment/5398755/+files/makedumpfile_1.6.7-3ubuntu2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Confirmed Status in linux source package in Focal: Invalid Status in makedumpfile source package in Focal: Confirmed Status in linux source package in Groovy: Invalid Status in makedumpfile source package in Groovy: Confirmed Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888297] Re: usb camera only works once until reset
Thank you for taking the time to report this bug and helping to make Ubuntu better. As per comment #1, this bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage.I have classified this bug as a bug in 'linux' as there may be an issue detecting your hardware by the kernel that you are currently using as you suspected. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs. Please provide any additional information when prompted to do so by the kernel bot. ** Package changed: ubuntu => linux (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888297 Title: usb camera only works once until reset Status in linux package in Ubuntu: New Bug description: I have a usb camera (SDI camera, attached to magewell usb capture) which only works once. It displays the image in something like OBS Studio or ffplay, and works perfectly. I can stop the capture. Then trying to open the camera a second time does not work, I get a black screen in ffplay/OBS. To fix this, I can unplug the device and plug it back in, at which point it works until stopped and restarted. So basically, I always have to unplug it and plug it back in after stopping otherwise it won't display an image a second time. Debian 10 works perfectly fine using same physical hardware and video software, but using (x)ubuntu 20.04 I get the problem as noted above. So I suspect a kernel bug/regression. I'm using an AMD 16 core system but don't know if it's related to that. It makes no difference whether I use the USB ports on the motherboard (USB 3.1), or whether I use an addon USB 3.1 PCI card. (And debian doesn't care either which usb port I use, it works correctly there across the board). I have no idea how to report more information. I've done the software updates etc., so whatever kernel is running in 20.04 as of this date, that's what I'm using now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890231] Re: alsa: should not load sof driver if the internal mic connects to the codec
** Description changed:
- This is for tracking purpose.
+ This issue was introduced by #1872916 ("Support Intel Soundwire
+ in 5.6-OEM Kernel 20.04"), so focal and groovy kernels don't need
+ this fix.
+
+ [Impact]
+ We found the sof driver instead of hda driver is enabled on a dell
+ machine without soundwire and dmic. This will make gnome show dummy
+ output and users have no audio device to use.
+
+ [Fix]
+ When we integrated fix for #1872916, we backported 2 patches, these
+ 2 patches enable the sof driver unconditionally for Dell comet lake
+ machines. There is an upstream patch to fix it, let the sof driver
+ enable conditionally on comet lake machines.
+
+ [Test Case]
+ Boot the kernel with this patch on that dell machine, check the
+ gnome-control-center, all audio devices exist, playback and recording
+ work well.
+
+ [Regression Risk]
+ On the Dell comet lake machines with dmic, the sof driver should
+ enable. Without this patch, the sof driver will enable unconditionally,
+ but with this patch, the sof driver will enable conditionally, so it
+ is possible to introduce a regression that on Dell comet machines,
+ the sof driver doesn't enable even the machine has dmic.
+
+ I have tested this patch on a Dell comet lake dmic machines, it worked
+ well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1890231
Title:
alsa: should not load sof driver if the internal mic connects to the
codec
Status in HWE Next:
New
Status in linux-oem-5.6 package in Ubuntu:
In Progress
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
This issue was introduced by #1872916 ("Support Intel Soundwire
in 5.6-OEM Kernel 20.04"), so focal and groovy kernels don't need
this fix.
[Impact]
We found the sof driver instead of hda driver is enabled on a dell
machine without soundwire and dmic. This will make gnome show dummy
output and users have no audio device to use.
[Fix]
When we integrated fix for #1872916, we backported 2 patches, these
2 patches enable the sof driver unconditionally for Dell comet lake
machines. There is an upstream patch to fix it, let the sof driver
enable conditionally on comet lake machines.
[Test Case]
Boot the kernel with this patch on that dell machine, check the
gnome-control-center, all audio devices exist, playback and recording
work well.
[Regression Risk]
On the Dell comet lake machines with dmic, the sof driver should
enable. Without this patch, the sof driver will enable unconditionally,
but with this patch, the sof driver will enable conditionally, so it
is possible to introduce a regression that on Dell comet machines,
the sof driver doesn't enable even the machine has dmic.
I have tested this patch on a Dell comet lake dmic machines, it worked
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1890231/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888507] Comment bridged from LTC Bugzilla
--- Comment From i...@de.ibm.com 2020-08-04 18:45 EDT---
Hi,
I fixed the skydive header as follows:
--- a/ebpf/defs.h
+++ b/ebpf/defs.h
@@ -56,7 +56,7 @@ static __inline int discret_memcmp(char *s1, char *s2, int n)
/* helper marcro to define a map, socket, kprobe section in the
* eBPF elf file.
*/
-#define MAP(NAME) struct bpf_map_def __section("maps/" #NAME) NAME =
+#define MAP(NAME) struct bpf_map_def __section("maps") NAME =
#define SOCKET(NAME) __section("socket_" #NAME)
#define LICENSE __section("license")
and also tried to cherry-pick some of the older kernel patches I wrote, e.g.:
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features=88aa8939c96781089e5ace3492d818074c5c6fe9
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features=05a68e892e89c97df6650cd8cc55058002657cbc
https://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git/commit/?h=features=3f161e0ae863a0456d00e5a6c9c81098c62ab7fe
- the new ones I linked here fix samples and aren't relevant for skydive
- but then I found out that quite some common code is missing as well.
For example, on 20.04 LLVM 10 is default. It contains the following
commit:
commit fbb64aa69835c8e3e9efe0afc8a73058b5a0fb3c # llvmorg-10.0.0
Author: Yonghong Song
Date: Tue Dec 17 16:24:23 2019 -0800
[BPF] extend BTF_KIND_FUNC to cover global, static and extern funcs
which makes clang produce non-backwards-compatible BTF. This leads to:
[14] FUNC bpf_flow_table type_id=12 vlen != 0
libbpf: Error loading .BTF into kernel: -22.
when loading. It's not that BPF devs did not think about this: in case
kernel cannot handle the new BTF_KIND_FUNC bits, they are supposed to be
sanitized by libbpf. However, Ubuntu 20.04 does not ship the newest
libbpf:
# /usr/sbin/bpftool --version
/usr/lib/linux-tools/5.4.0-42-generic/bpftool v5.4.44
whereas the commit that introduced sanitization is in v5.6:
commit 2d3eb67f64ec317bbfe340cfcc8325d40a6ff317 # v5.6
Author: Alexei Starovoitov
Date: Thu Jan 9 22:41:19 2020 -0800
libbpf: Sanitize global functions
Since this now turns into quite an adventure w.r.t. backporting, can't
we try an easier path first? Namely: use clang-8, which is also
available in Ubuntu 20.04, but doesn't include any fancy stuff!
skydive# CLANG=clang-8 GOPATH=$HOME/go make -C ebpf
skydive# bpftool prog load ebpf/flow.o /sys/fs/bpf/flow ; echo $?
0
# bpftool prog load ebpf/flow-gre.o /sys/fs/bpf/flow-gre ; echo $?
0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888507
Title:
[UBUNTU 18.04] BPF programs fail on Ubuntu s390x
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
New
Status in linux source package in Bionic:
In Progress
Bug description:
We need to run BPF filters to analyse and monitor network traffic. The
BPF filters are created by skydive (http://skydive.network). Currently
skydive fails to install BPF filters on s390x (using Ubuntu 18.04
currently, soon moving to Ubuntu 20.04).
Because of these failures, we decided to try the BPF samples that come
with the kernel first. These samples also fail on s390x while they
work fine on Intel.
shense@boe-build:~/bionic/samples/bpf$ uname -a
Linux boe-build 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:40:36 UTC
2020 s390x s390x s390x GNU/Linux
Example instructions:
sudo apt install -y dpkg-dev clang llvm libelf-dev
sudo apt-get source linux-image-unsigned-$(uname -r)
cd linux-4.15.0/
make headers_install
make samples/bpf/
Errors:
shense@boe-build:~/bionic/samples/bpf$ sudo ./test_map_in_map
[sudo] password for shense:
invalid relo for insn[4].code 0x85
bpf_load_program() err=22
0: (bf) r7 = r1
1: (b7) r1 = 0
2: (63) *(u32 *)(r10 -32) = r1
3: (bf) r1 = r7
4: (85) call unknown#-1
BPF_CALL uses reserved fields
0: (bf) r7 = r1
1: (b7) r1 = 0
2: (63) *(u32 *)(r10 -32) = r1
3: (bf) r1 = r7
4: (85) call unknown#-1
BPF_CALL uses reserved fields
shense@boe-build:~/bionic/samples/bpf$ sudo ./map_perf_test
invalid relo for insn[22].code 0x85
bpf_load_program() err=22
0: (bf) r7 = r1
1: (18) r1 = 0x207265743a25646e
3: (7b) *(u64 *)(r10 -16) = r1
4: (18) r1 = 0x705f616c6c6f632e
6: (7b) *(u64 *)(r10 -24) = r1
7: (18) r1 = 0x5f6c72755f686d61
9: (7b) *(u64 *)(r10 -32) = r1
10: (18) r1 = 0x7420737472657373
12: (7b) *(u64 *)(r10 -40) = r1
13: (18) r1 = 0x4661696c65642061
15: (7b) *(u64 *)(r10 -48) = r1
16: (b7) r1 = 0
17: (73) *(u8 *)(r10 -8) = r1
18: (b7) r2 = 1
19: (7b) *(u64 *)(r10 -72) = r2
20: (63) *(u32 *)(r10 -76) = r1
21: (bf) r1 = r7
22: (85) call unknown#-1
BPF_CALL uses reserved fields
0: (bf) r7 = r1
1: (18) r1 = 0x207265743a25646e
3: (7b) *(u64 *)(r10 -16) = r1
4: (18) r1 = 0x705f616c6c6f632e
6: (7b) *(u64 *)(r10 -24) = r1
7: (18) r1 = 0x5f6c72755f686d61
9:
[Kernel-packages] [Bug 1890055] Re: Brightness control does not work with 5.4.0-42.26
Hello, 3 questions here: 1. Can you adjust the screen brightness with the hotkeys? 2. Can you adjust the screen brightness with the slide bar in Settings -> Power? 3. If not, does it work for you with these 2 methods above on older kernels (and which version)? Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890055 Title: Brightness control does not work with 5.4.0-42.26 Status in linux package in Ubuntu: Incomplete Bug description: backlight (brightness does not work) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abdr 2227 F pulseaudio /dev/snd/controlC0: abdr 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:38:12 2020 InstallationDate: Installed on 2020-07-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81SX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=7dda4531-e9b1-482c-bcec-a96bcf0a3b42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN36WW:bd02/10/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
I had this problem on nuc10i7fnb it worked when I disabled jack sensing by using hdajackretask as @kaihengfeng suggested. I had to use "Install boot override" cause when I tried "Apply now" I got error : "Device or resource busy" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890055] Re: Brightness control does not work with 5.4.0-42.26
** Summary changed: - linux-image-5.4.0-42-generic 5.4.0-42.26 + Brightness control does not work with 5.4.0-42.26 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890055 Title: Brightness control does not work with 5.4.0-42.26 Status in linux package in Ubuntu: Confirmed Bug description: backlight (brightness does not work) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abdr 2227 F pulseaudio /dev/snd/controlC0: abdr 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:38:12 2020 InstallationDate: Installed on 2020-07-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81SX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=7dda4531-e9b1-482c-bcec-a96bcf0a3b42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN36WW:bd02/10/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889735] Re: tap: use after free
** Description changed: [Impact] If the socket buffer array of a tap queue is full, a received package needs to be dropped. Currently, the check for the array being full is performed lockless, which might lead to use-after-free errors if the socket buffer array has been resized. [Test Case] TBD. [Regression Potential] The check for the array being full is simply dropped. In case the array is full, subsequent frame handling will fail and the frame is eventually dropped. A regression would manifest itself if the frame is not dropped - for whatever reason and inserted into the (ring) buffer, overwriting the - oldest frame in the buffer. + for whatever reason and inserted into the full (ring) buffer, + overwriting the oldest frame in the buffer. So we'd end up with + frame/packet loss. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889735 Title: tap: use after free Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: [Impact] If the socket buffer array of a tap queue is full, a received package needs to be dropped. Currently, the check for the array being full is performed lockless, which might lead to use-after-free errors if the socket buffer array has been resized. [Test Case] TBD. [Regression Potential] The check for the array being full is simply dropped. In case the array is full, subsequent frame handling will fail and the frame is eventually dropped. A regression would manifest itself if the frame is not dropped for whatever reason and inserted into the full (ring) buffer, overwriting the oldest frame in the buffer. So we'd end up with frame/packet loss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889735/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883008] Re: Displaylink USB3 HDMI Adapter does not resume after suspending
@seb128, any advise what I could do to get this working or which other group may be in the position to give an advise? I guess we agree that this is not the intended operation... Thanks for your help @fheimes, but seems like "nobody" is not able solve this issue... Best regards, Nicolas -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883008 Title: Displaylink USB3 HDMI Adapter does not resume after suspending Status in linux package in Ubuntu: Confirmed Bug description: Hi I recently updated to Ubuntu 20.04 and my Display Link USB adapter worked finw at first. Recently it does not resume operation after suspending the system: Plugging Adapter into USB Port: [380431.001721] usb 3-10: new high-speed USB device number 35 using xhci_hcd [380431.026448] usb 3-10: New USB device found, idVendor=17e9, idProduct=4301, bcdDevice=35.81 [380431.026450] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [380431.026451] usb 3-10: Product: USB3.0 UHD HDMI Adapter [380431.026452] usb 3-10: Manufacturer: DisplayLink [380431.026453] usb 3-10: SerialNumber: 000100110005089 [380431.031513] usb 3-10: Warning! Unlikely big volume range (=511), cval->res is probably wrong. [380431.031515] usb 3-10: [13] FU [DisplayLink Audio Playback Volume] ch = 2, val = -8176/0/16 [380431.534305] evdi: [D] evdi_painter_connect:644 (dev=-1) Process is trying to connect [380431.534307] evdi: [I] Task 290879 (DesktopManagerE) of process 290871 (DisplayLinkMana) [380431.534310] evdi: [D] evdi_painter_connect:694 (dev=1) Connected with 7f108832 [380431.534313] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629174] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629177] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid [380431.629361] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629362] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid [380432.193645] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380432.193654] evdi: [D] evdi_painter_mode_changed_notify:622 (dev=1) Notifying mode changed: 2560x1440@60; bpp 32; [380432.193655] evdi: [D] evdi_log_pixel_format:586 pixel format XR24 little-endian (0x34325258) [380432.193656] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380432.745156] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380432.745159] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid <<<>>> [380482.624749] r8169 :03:00.0 eth1: Link is Down [380482.700233] r8169 :02:00.0 eth0: Link is Down [380482.898291] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 3 [380483.575664] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380486.062394] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 3 [380496.978102] PM: suspend entry (deep) [380497.022677] Filesystems sync: 0.044 seconds [380497.023039] Freezing user space processes ... (elapsed 0.004 seconds) done. [380497.027494] OOM killer disabled. [380497.027495] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [380497.029186] printk: Suspending console(s) (use no_console_suspend to debug) [380497.047859] serial 00:06: disabled [380497.048271] serial 00:05: disabled [380497.062541] sd 1:0:0:0: [sda] Synchronizing SCSI cache [380497.062709] sd 1:0:0:0: [sda] Stopping disk [380497.870726] ACPI: Preparing to enter system sleep state S3 [380497.871533] PM: Saving platform NVS memory [380497.871612] Disabling non-boot CPUs ... [380497.872595] IRQ 23: no longer affine to CPU1 [380497.872602] IRQ 26: no longer affine to CPU1 [380497.873630] smpboot: CPU 1 is now offline [380497.877693] IRQ 16: no longer affine to CPU2 [380497.877698] IRQ 18: no longer affine to CPU2 [380497.877710] IRQ 33: no longer affine to CPU2 [380497.878752] smpboot: CPU 2 is now offline [380497.883528] IRQ 28: no longer affine to CPU3 [380497.883535] IRQ 29: no longer affine to CPU3 [380497.884567] smpboot: CPU 3 is now offline [380497.889485] ACPI: Low-level resume complete [380497.889528] PM: Restoring platform NVS memory [380497.892085] Enabling non-boot CPUs ... [380497.892130] x86: Booting SMP configuration: [380497.892131] smpboot: Booting Node 0 Processor 1 APIC 0x2 [380497.894113] CPU1 is up [380497.894144] smpboot: Booting Node 0 Processor 2 APIC 0x4 [380497.896160] CPU2 is up [380497.896185] smpboot: Booting Node 0 Processor 3 APIC 0x6 [380497.898263] CPU3 is up [380497.899479] ACPI: Waking up from system sleep state S3 [380497.919826] pcieport :00:1c.0: pciehp: Slot(0): Card present [380497.920685] sd 1:0:0:0: [sda] Starting disk [380497.922039] serial
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
I tried to re-open this bug, because we still get reports on the CRIU side that this is not fixed: https://github.com/checkpoint- restore/criu/issues/860#issuecomment-668628745 We also still see this in Travis not working. ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu Eoan) Status: Fix Released => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Fix Released => Confirmed ** Bug watch added: github.com/checkpoint-restore/criu/issues #860 https://github.com/checkpoint-restore/criu/issues/860 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing
Patch to nilfs2 by Ryusuke Konishi (https://www.spinics.net/lists/linux- nilfs/msg04322.html) has found its way to Ubuntu kernel image linux- image-5.3.0-64-lowlatency (5.3.0-64.58), and the kernel oops doesn't appear any more. To me it seems this issue is finally resolved. ** Changed in: linux (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859979 Title: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing Status in linux package in Ubuntu: Fix Released Bug description: With linux-image-5.3.0-26-lowlatency, segctord kthread encounters a "BUG: kernel NULL pointer dereference, address: 00a8" some half a minute from boot. Before that, one can log in to the system (/home is on a nilfs2 filesystem), but after the kernel BUG report, any write to a nilfs2 filesystem freezes the process trying to write, or any new login attempt freezes. This bug can be reproduced with every boot. With linux-image-5.3.0-24-lowlatency and earlier, this doesn't happen. Relevant excerpt from syslog: ... Jan 16 10:56:59 lillukka kernel: [0.00] Linux version 5.3.0-26-lowlatency (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP PREEMPT Wed Dec 18 06:21:38 UTC 2019 (Ubuntu 5.3.0-26.28-lowlatency 5.3.13) ... Jan 16 10:57:13 lillukka kernel: [ 28.727753] BUG: kernel NULL pointer dereference, address: 00a8 Jan 16 10:57:13 lillukka kernel: [ 28.727852] #PF: supervisor read access in kernel mode Jan 16 10:57:13 lillukka kernel: [ 28.727914] #PF: error_code(0x) - not-present page Jan 16 10:57:13 lillukka kernel: [ 28.727974] PGD 0 P4D 0 Jan 16 10:57:13 lillukka kernel: [ 28.728012] Oops: [#1] PREEMPT SMP PTI Jan 16 10:57:13 lillukka kernel: [ 28.728067] CPU: 3 PID: 838 Comm: segctord Not tainted 5.3.0-26-lowlatency #28-Ubuntu Jan 16 10:57:13 lillukka kernel: [ 28.728156] Hardware name: Sony Corporation SVP1321C5E/VAIO, BIOS R0280V7 07/11/2013 Jan 16 10:57:13 lillukka kernel: [ 28.728257] RIP: 0010:percpu_counter_add_batch+0x13/0x80 Jan 16 10:57:13 lillukka kernel: [ 28.728334] Code: e0 41 5c 41 5d 41 5e 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 48 89 e5 41 55 41 54 49 89 fc 53 65 ff 05 b5 5c ed 72 <48> 8b 47 20 48 63 ca 65 44 8b 28 49 63 dd 48 01 f3 48 39 d9 7e 0a Jan 16 10:57:13 lillukka kernel: [ 28.728536] RSP: 0018:b582c02afcb0 EFLAGS: 00010082 Jan 16 10:57:13 lillukka kernel: [ 28.728598] RAX: 0002 RBX: RCX: 0001 Jan 16 10:57:13 lillukka kernel: [ 28.728679] RDX: 0018 RSI: 0001 RDI: 0088 Jan 16 10:57:13 lillukka kernel: [ 28.728760] RBP: b582c02afcc8 R08: 8f519357ab40 R09: 0018 Jan 16 10:57:13 lillukka kernel: [ 28.728841] R10: 00030140 R11: 8f5193609eea R12: 0088 Jan 16 10:57:13 lillukka kernel: [ 28.728920] R13: 8f518a3ee498 R14: 8f518a3ee608 R15: e52b07e5a200 Jan 16 10:57:13 lillukka kernel: [ 28.729001] FS: () GS:8f519798() knlGS: Jan 16 10:57:13 lillukka kernel: [ 28.729091] CS: 0010 DS: ES: CR0: 80050033 Jan 16 10:57:13 lillukka kernel: [ 28.729157] CR2: 00a8 CR3: 8d60a002 CR4: 001606e0 Jan 16 10:57:13 lillukka kernel: [ 28.729237] Call Trace: Jan 16 10:57:13 lillukka kernel: [ 28.729280] __test_set_page_writeback+0x2f1/0x310 Jan 16 10:57:13 lillukka kernel: [ 28.729362] nilfs_segctor_do_construct+0xd13/0x1260 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729432] ? __switch_to_asm+0x40/0x70 Jan 16 10:57:13 lillukka kernel: [ 28.729496] nilfs_segctor_construct+0x1ff/0x2f0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729572] nilfs_segctor_thread+0x136/0x3a0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729640] kthread+0x104/0x140 Jan 16 10:57:13 lillukka kernel: [ 28.729690] ? nilfs_segctor_construct+0x2f0/0x2f0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729760] ? kthread_park+0x80/0x80 Jan 16 10:57:13 lillukka kernel: [ 28.729807] ret_from_fork+0x35/0x40 Jan 16 10:57:13 lillukka kernel: [ 28.729854] Modules linked in: ccm rfcomm aufs overlay cmac bnep nilfs2 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel pn544_mei mei_phy pn544 snd_hda_codec hci snd_hda_core snd_hwdep intel_rapl_msr mei_hdcp nfc snd_pcm snd_seq_midi snd_seq_midi_event intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp iwlmvm mac80211 snd_seq btusb btrtl libarc4 btbcm uvcvideo btintel kvm videobuf2_vmalloc iwlwifi videobuf2_memops bluetooth snd_seq_device videobuf2_v4l2
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Hello Matt, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
A fresh install would certainly help. It is also possible that additional drivers can cause this; NV proprietary driver can be an example of it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890317] [NEW] Add initial audio support for Lenovo ThinkStation P620
Public bug reported: [Impact] Lenovo ThinkStation P620 is equipped with two USB audio card that don't fully work. [Fix] Give these two cards profile name, so userspace can identify them to add addition support. In addition to that, disable non-working element and relax error handling for speaker, so there's no error left. Otherwise usb-audio driver will stop working completely. [Test] After the patch is applied, `cat /proc/asound/cards` can show correct profile name for each card. No more error can be spotted from dmesg. The audio is still not fully working yet, because it requires more work in userspace ALSA and PulseAudio. [Regression Potential] Low. Adding profile name doesn't change any code flow. The only behavioral change is error handling towards "Speaker." Becuase it actually relaxes the error handling instead of tightening, so devices that don't have this issue won't be affected. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: oem-priority originate-from-1887878 sutton ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Medium ** Summary changed: - Add inital audio support for Lenovo ThinkStation P620 + Add initial audio support for Lenovo ThinkStation P620 ** Tags added: oem-priority originate-from-1887878 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890317 Title: Add initial audio support for Lenovo ThinkStation P620 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: [Impact] Lenovo ThinkStation P620 is equipped with two USB audio card that don't fully work. [Fix] Give these two cards profile name, so userspace can identify them to add addition support. In addition to that, disable non-working element and relax error handling for speaker, so there's no error left. Otherwise usb-audio driver will stop working completely. [Test] After the patch is applied, `cat /proc/asound/cards` can show correct profile name for each card. No more error can be spotted from dmesg. The audio is still not fully working yet, because it requires more work in userspace ALSA and PulseAudio. [Regression Potential] Low. Adding profile name doesn't change any code flow. The only behavioral change is error handling towards "Speaker." Becuase it actually relaxes the error handling instead of tightening, so devices that don't have this issue won't be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1890317/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
Ubuntu 20.04 with Nvidia drivers 450.xx. Doesn't work for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant:
[Kernel-packages] [Bug 1884981] Re: No touchpad support on Lenovo IdeaPad 5 14ARE05
** Bug watch added: Linux Kernel Bug Tracker #208171 https://bugzilla.kernel.org/show_bug.cgi?id=208171 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=208171 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: No touchpad support on Lenovo IdeaPad 5 14ARE05 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890327] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1890327 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890327 Title: MSFT touchpad not working [0.826524] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy regulator Status in linux package in Ubuntu: Incomplete Bug description: Hello dmesg: [0.826524] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy regulator [0.826538] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy regulator Best regards DistroRelease: Ubuntu 20.04 Kernel: 5.4.*,5.7.*,5.8.* Processor: AMD Ryzen 4600H lspci: 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f99 (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev c7) 04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01) 04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller 05:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81) 05:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81) //lspci isn't showing touchpad / xinput: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=13 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=15 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6
[Kernel-packages] [Bug 1890306] [NEW] Fix IOMMU error on AMD Radeon Pro W5700
Public bug reported: [Impact] AMD Radeon Pro W5700 doesn't work at all, driver failed to probe the device due to IOMMU error. [Fix] Disable PCI ATS for the device. [Test] After applying the patch, there's no more IOMMU error, and the driver can correctly probe the device. The grahpics also works great. [Regression Potential] Low. amdgpu is known to work well with ATS disabled. In addition to that, AMD confirmed it's the correct fix for this card, so the chance to break anything is rather low. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Critical Status: Confirmed ** Affects: linux-oem-5.6 (Ubuntu Focal) Importance: Critical Status: Confirmed ** Tags: oem-priority originate-from-1887609 sutton ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux-oem-5.6 (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Invalid ** Tags added: oem-priority originate-from-1887609 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890306 Title: Fix IOMMU error on AMD Radeon Pro W5700 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Confirmed Bug description: [Impact] AMD Radeon Pro W5700 doesn't work at all, driver failed to probe the device due to IOMMU error. [Fix] Disable PCI ATS for the device. [Test] After applying the patch, there's no more IOMMU error, and the driver can correctly probe the device. The grahpics also works great. [Regression Potential] Low. amdgpu is known to work well with ATS disabled. In addition to that, AMD confirmed it's the correct fix for this card, so the chance to break anything is rather low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1890306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890327] [NEW] MSFT touchpad not working [ 0.826524] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy regulator
Public bug reported:
Hello
dmesg:
[0.826524] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy
regulator
[0.826538] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy
regulator
Best regards
DistroRelease: Ubuntu 20.04
Kernel: 5.4.*,5.7.*,5.8.*
Processor: AMD Ryzen 4600H
lspci:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP
Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP
Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 7
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f99 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD
Controller SM981/PM981/PM983
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 15)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Renoir (rev c7)
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h
(Models 10h-1fh) Platform Security Processor
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
10h-1fh) HD Audio Controller
05:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller
[AHCI mode] (rev 81)
05:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller
[AHCI mode] (rev 81)
//lspci isn't showing touchpad
/
xinput:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=13 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=15 [slave pointer (2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpadid=16 [slave pointer (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
↳ Power Button id=6[slave keyboard (3)]
↳ Video Bus id=7[slave keyboard (3)]
↳ Video Bus id=8[slave keyboard (3)]
↳ Power Button id=9[slave keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Controlid=11 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboard id=12 [slave keyboard (3)]
↳ Ideapad extra buttons id=14 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=17 [slave keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=18 [slave
keyboard (3)]
Under OS that can use this device (e.g. MS_win10):
Device Type: Firmware
Manufacturer: Elantech Ltd.
Location: On UEFI
UEFI\RES_{234124e9-40b7-43ef-9b5e-97470808d440}_2
UEFI\RES_{234124e9-40b7-43ef-9b5e-97470808d440}
[Kernel-packages] [Bug 1884981] Re: Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably fails from any given boot
Added upstream, and these pages might be useful to keep an eye on: * https://wiki.archlinux.org/index.php/Lenovo_IdeaPad_5_14are05 * https://wiki.archlinux.org/index.php/Lenovo_IdeaPad_Flex_5_(Ryzen) ** Summary changed: - No touchpad support on Lenovo IdeaPad 5 14ARE05 + Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably fails from any given boot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: Lenovo IdeaPad Flex 5 Ryzen (14ARE05): Touchpad/trackpad unpredictably fails from any given boot Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843742] Re: RM: irda-utils and ircp-tray (was: irda-utils ftbfs in eoan)
Confirmed no external reverse-depends and removed in Debian too.
Removing as requested.
** Summary changed:
- irda-utils ftbfs in eoan
+ RM: irda-utils and ircp-tray (was: irda-utils ftbfs in eoan)
** Also affects: ircp-tray (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ircp-tray (Ubuntu)
Status: New => In Progress
** Changed in: irda-utils (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ircp-tray (Ubuntu)
Importance: Undecided => Medium
** Changed in: irda-utils (Ubuntu)
Importance: High => Medium
** Changed in: irda-utils (Ubuntu)
Assignee: Stefan Bader (smb) => Andy Whitcroft (apw)
** Changed in: ircp-tray (Ubuntu)
Assignee: (unassigned) => Andy Whitcroft (apw)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to irda-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1843742
Title:
RM: irda-utils and ircp-tray (was: irda-utils ftbfs in eoan)
Status in ircp-tray package in Ubuntu:
In Progress
Status in irda-utils package in Ubuntu:
In Progress
Bug description:
https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
.irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c
irdadump.c
irdadump.c: In function ‘print_time’:
irdadump.c:82:13: warning: g_string_append_printf
82 | g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
irdadump.c: In function ‘print_diff_time’:
irdadump.c:108:13: warning: g_string_append_printf
108 | g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
irdadump.c: In function ‘parse_irda_frame’:
irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
irdadump.c: In function ‘irdadump_loop’:
irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this
function); did you mean ‘SIOCGARP’?
286 | if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
irdadump.c:286:16: note: each undeclared identifier is reported only once for
each function it appears in
make[1]: *** [Makefile:48: irdadump.o] Error 1
make[1]: Leaving directory '/<>/irdadump'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ircp-tray/+bug/1843742/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843742] Re: RM: irda-utils and ircp-tray (was: irda-utils ftbfs in eoan)
Removing packages from groovy:
irda-utils 0.9.18-15ubuntu1 in groovy
irda-utils 0.9.18-15ubuntu1 in groovy amd64
irda-utils 0.9.18-15ubuntu1 in groovy arm64
irda-utils 0.9.18-15ubuntu1 in groovy armhf
irda-utils 0.9.18-15ubuntu1 in groovy ppc64el
irda-utils 0.9.18-15ubuntu1 in groovy s390x
ircp-tray 0.7.6-1.2ubuntu3 in groovy
ircp-tray 0.7.6-1.2ubuntu3 in groovy amd64
ircp-tray 0.7.6-1.2ubuntu3 in groovy arm64
ircp-tray 0.7.6-1.2ubuntu3 in groovy armhf
ircp-tray 0.7.6-1.2ubuntu3 in groovy ppc64el
ircp-tray 0.7.6-1.2ubuntu3 in groovy s390x
Comment: No longer supported upstream, removed in Debian, ftbfs in grooby; LP:
#1843742
2 packages successfully removed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to irda-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1843742
Title:
RM: irda-utils and ircp-tray (was: irda-utils ftbfs in eoan)
Status in ircp-tray package in Ubuntu:
In Progress
Status in irda-utils package in Ubuntu:
In Progress
Bug description:
https://launchpadlibrarian.net/441262268/buildlog_ubuntu-eoan-amd64
.irda-utils_0.9.18-15ubuntu1_BUILDING.txt.gz
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fgnu89-inline
-W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include -I../include/ -c
irdadump.c
irdadump.c: In function ‘print_time’:
irdadump.c:82:13: warning: g_string_append_printf
82 | g_string_sprintfa(str, "%02d:%02d:%02d.%06u ",
| ^~~~
irdadump.c: In function ‘print_diff_time’:
irdadump.c:108:13: warning: g_string_append_printf
108 | g_string_sprintfa(str, "(%07.2f ms) ", diff);
| ^~~~
irdadump.c: In function ‘parse_irda_frame’:
irdadump.c:178:13: warning: g_string_append_printf
178 | g_string_sprintfa(str, "(%d) ", len);
| ^~~~
irdadump.c:189:13: warning: g_string_append_printf
189 |g_string_sprintfa(str, "%02x", frame_buf->head[i]);
| ^~~~
irdadump.c:196:13: warning: g_string_append_printf
196 |g_string_sprintfa(str, " %c", c);
| ^~~~
irdadump.c:207:13: warning: g_string_append_printf
207 |g_string_sprintfa(str, "%02x ", frame_buf->head[i]);
| ^~~~
irdadump.c: In function ‘irdadump_loop’:
irdadump.c:286:16: error: ‘SIOCGSTAMP’ undeclared (first use in this
function); did you mean ‘SIOCGARP’?
286 | if (ioctl(fd, SIOCGSTAMP, curr_time) < 0) {
|^~
|SIOCGARP
irdadump.c:286:16: note: each undeclared identifier is reported only once for
each function it appears in
make[1]: *** [Makefile:48: irdadump.o] Error 1
make[1]: Leaving directory '/<>/irdadump'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ircp-tray/+bug/1843742/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867983] Re: Computer is frozen after suspend
Many thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867983 Title: Computer is frozen after suspend Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: === SRU Justification === [Impact] Some systems with ATA drives freeze during suspend [Fix] Avoid circular sync dependency by using async cookie. [Test] User reports positive feedback. [Regression Potential] Low. This patch makes synchronize more targeted, prevents many potential freeze. === Original Bug Report === I am using an old HP EliteBook 6930p with current Ubuntu. When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping. It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42. I am holding kernel purge for now, but this is annoying. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isabelle 1010 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 20:46:35 2020 HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c InstallationDate: Installed on 2015-03-15 (1830 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.12 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.27 dmi.chassis.asset.tag: CZC939161W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 6930p dmi.product.sku: J1610781 dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800509] Re: unable to handle kernel NULL pointer dereference at 0000000000000007
this bug is present in the current upstream also (v5.8). Red Hat is working on the fix (ref: 1739593, private) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1800509 Title: unable to handle kernel NULL pointer dereference at 0007 Status in linux package in Ubuntu: Expired Bug description: ```Oct 29 13:51:25 vs09 kernel: [201179.645520] BUG: unable to handle kernel NULL pointer dereference at 0007 Oct 29 13:51:25 vs09 kernel: [201179.645601] IP: split_swap_cluster+0x4f/0x70 Oct 29 13:51:25 vs09 kernel: [201179.645633] PGD 0 P4D 0 Oct 29 13:51:25 vs09 kernel: [201179.645660] Oops: 0002 [#1] SMP PTI Oct 29 13:51:25 vs09 kernel: [201179.645689] Modules linked in: vhost_net vhost tap xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp intel_cstate ipmi_ssif joydev input_leds intel_rapl_perf bridge stp llc mei_me lpc_ich mei ioatdma shpchp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter acpi_pad mac_hid kvm_intel kvm irqbypass ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov Oct 29 13:51:25 vs09 kernel: [201179.646180] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ast crct10dif_pclmul hid_generic crc32_pclmul ttm ghash_clmulni_intel pcbc drm_kms_helper usbhid syscopyarea igb sysfillrect aesni_intel sysimgblt dca aes_x86_64 crypto_simd fb_sys_fops glue_helper i2c_algo_bit ahci ptp drm mxm_wmi hid cryptd libahci pps_core wmi Oct 29 13:51:25 vs09 kernel: [201179.646418] CPU: 15 PID: 4321 Comm: qemu-system-x86 Not tainted 4.15.0-38-generic #41~16.04.1-Ubuntu Oct 29 13:51:25 vs09 kernel: [201179.646478] Hardware name: Supermicro SYS-6028R-TR/X10DRi, BIOS 2.1 09/13/2016 Oct 29 13:51:25 vs09 kernel: [201179.646531] RIP: 0010:split_swap_cluster+0x4f/0x70 Oct 29 13:51:25 vs09 kernel: [201179.646567] RSP: 0018:a9c9f77e3398 EFLAGS: 00010246 Oct 29 13:51:25 vs09 kernel: [201179.646606] RAX: RBX: 00064566 RCX: 00064566 Oct 29 13:51:25 vs09 kernel: [201179.646655] RDX: a9c9a0001000 RSI: 05cc5fff RDI: 00064566 Oct 29 13:51:25 vs09 kernel: [201179.646703] RBP: a9c9f77e33a0 R08: 0001 R09: 9140bffd4d00 Oct 29 13:51:25 vs09 kernel: [201179.646752] R10: 9140bffd4000 R11: 0001 R12: e5fdb3178000 Oct 29 13:51:25 vs09 kernel: [201179.646800] R13: e5fdb3178080 R14: e5fdb318 R15: e5fdb3178040 Oct 29 13:51:25 vs09 kernel: [201179.646850] FS: 7fb2a27fc700() GS:913fbee4() knlGS: Oct 29 13:51:25 vs09 kernel: [201179.646905] CS: 0010 DS: ES: CR0: 80050033 Oct 29 13:51:25 vs09 kernel: [201179.646946] CR2: 0007 CR3: 003f691b4006 CR4: 003626e0 Oct 29 13:51:25 vs09 kernel: [201179.646995] DR0: DR1: DR2: Oct 29 13:51:25 vs09 kernel: [201179.647043] DR3: DR6: fffe0ff0 DR7: 0400 Oct 29 13:51:25 vs09 kernel: [201179.647091] Call Trace: Oct 29 13:51:25 vs09 kernel: [201179.647119] split_huge_page_to_list+0x76e/0x7f0 Oct 29 13:51:25 vs09 kernel: [201179.647156] deferred_split_scan+0x177/0x2d0 Oct 29 13:51:25 vs09 kernel: [201179.647191] shrink_slab.part.50+0x20b/0x440 Oct 29 13:51:25 vs09 kernel: [201179.647226] shrink_node+0x2fc/0x310 Oct 29 13:51:25 vs09 kernel: [201179.647257] do_try_to_free_pages+0xee/0x360 Oct 29 13:51:25 vs09 kernel: [201179.647290] try_to_free_pages+0xf1/0x1c0 Oct 29 13:51:25 vs09 kernel: [201179.647324] __alloc_pages_slowpath+0x405/0xec0 Oct 29 13:51:25 vs09 kernel: [201179.647362] __alloc_pages_nodemask+0x265/0x280 Oct 29 13:51:25 vs09 kernel: [201179.647399] alloc_pages_vma+0x165/0x1e0 Oct 29 13:51:25 vs09 kernel: [201179.647431] do_huge_pmd_anonymous_page+0x167/0x710 Oct 29 13:51:25 vs09 kernel: [201179.647469] __handle_mm_fault+0xb1d/0x11e0 Oct 29 13:51:25 vs09 kernel: [201179.647504] handle_mm_fault+0xcc/0x1c0 Oct 29 13:51:25 vs09 kernel: [201179.647535] __get_user_pages+0x11d/0x6d0 Oct 29 13:51:25 vs09 kernel: [201179.647568] get_user_pages+0x42/0x50 Oct 29 13:51:25 vs09 kernel: [201179.647627] __gfn_to_pfn_memslot+0x18b/0x3b0 [kvm] Oct 29 13:51:25 vs09 kernel: [201179.647691] try_async_pf+0x66/0x220 [kvm] Oct 29 13:51:25 vs09 kernel: [201179.649238] tdp_page_fault+0x12d/0x290
[Kernel-packages] [Bug 1823859] Re: NULL pointer dereference in split_swap_cluster
this bug is present in the current upstream also (v5.8). Red Hat is working on the fix (ref: 1739593, private). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1823859 Title: NULL pointer dereference in split_swap_cluster Status in linux-azure package in Ubuntu: New Bug description: We have encountered the following oops on one of our VMs: Apr 7 14:02:19 rancher1 kernel: [2089793.273674] BUG: unable to handle kernel NULL pointer dereference at 0007 Apr 7 14:02:19 rancher1 kernel: [2089793.282782] IP: split_swap_cluster+0x4f/0x70 Apr 7 14:02:19 rancher1 kernel: [2089793.330631] PGD 0 P4D 0 Apr 7 14:02:19 rancher1 kernel: [2089793.338279] Oops: 0002 [#1] SMP PTI Apr 7 14:02:19 rancher1 kernel: [2089793.350774] Modules linked in: ufs msdos xfs cmac arc4 md4 nls_utf8 cifs ccm fscache xt_tcpudp xt_set ip_set_hash_net ip_set iptable_raw vxlan ip6_udp_tunnel udp_tunnel xt_nat xt_mark xfrm6_mode_tunnel xfrm4_mode_tunnel esp4 ansi_cprng veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter nf_nat br_netfilter bridge stp llc nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_security ip_tables x_tables aufs overlay mlx4_en pci_hyperv hv_balloon serio_raw joydev ib_iser iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul Apr 7 14:02:19 rancher1 kernel: [2089793.618910] crc32_pclmul ghash_clmulni_intel pcbc hid_generic aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hid_hyperv pata_acpi hyperv_fb cfbfillrect hyperv_keyboard cfbimgblt hid cfbcopyarea hv_netvsc hv_utils Apr 7 14:02:19 rancher1 kernel: [2089793.692250] CPU: 0 PID: 47 Comm: kswapd0 Not tainted 4.15.0-1040-azure #44-Ubuntu Apr 7 14:02:19 rancher1 kernel: [2089793.725316] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 Apr 7 14:02:19 rancher1 kernel: [2089793.762206] RIP: 0010:split_swap_cluster+0x4f/0x70 Apr 7 14:02:19 rancher1 kernel: [2089793.781768] RSP: 0018:aaf900fbfbe0 EFLAGS: 00010246 Apr 7 14:02:19 rancher1 kernel: [2089793.800432] RAX: RBX: 007290de RCX: 007290de Apr 7 14:02:19 rancher1 kernel: [2089793.824572] RDX: aaf905001000 RSI: 00118df9 RDI: 007290de Apr 7 14:02:19 rancher1 kernel: [2089793.854139] RBP: aaf900fbfbe8 R08: 0001 R09: 9c647ffd4d00 Apr 7 14:02:19 rancher1 kernel: [2089793.882588] R10: 9c647ffd4000 R11: 0001 R12: f61ac463 Apr 7 14:02:19 rancher1 kernel: [2089793.909530] R13: f61ac4630080 R14: f61ac4638000 R15: f61ac4630040 Apr 7 14:02:19 rancher1 kernel: [2089793.935871] FS: () GS:9c647fc0() knlGS: Apr 7 14:02:19 rancher1 kernel: [2089793.966483] CS: 0010 DS: ES: CR0: 80050033 Apr 7 14:02:19 rancher1 kernel: [2089793.987904] CR2: 0007 CR3: 3240a005 CR4: 001606f0 Apr 7 14:02:19 rancher1 kernel: [2089794.017641] Call Trace: Apr 7 14:02:19 rancher1 kernel: [2089794.028683] split_huge_page_to_list+0x76e/0x7f0 Apr 7 14:02:19 rancher1 kernel: [2089794.051250] deferred_split_scan+0x177/0x2d0 Apr 7 14:02:19 rancher1 kernel: [2089794.065213] shrink_slab.part.50+0x20b/0x440 Apr 7 14:02:19 rancher1 kernel: [2089794.083856] shrink_node+0x2fc/0x310 Apr 7 14:02:19 rancher1 kernel: [2089794.097963] kswapd+0x32a/0x770 Apr 7 14:02:19 rancher1 kernel: [2089794.110523] kthread+0x105/0x140 Apr 7 14:02:19 rancher1 kernel: [2089794.122680] ? mem_cgroup_shrink_node+0x190/0x190 Apr 7 14:02:19 rancher1 kernel: [2089794.139139] ? kthread_destroy_worker+0x50/0x50 Apr 7 14:02:19 rancher1 kernel: [2089794.155543] ret_from_fork+0x35/0x40 Apr 7 14:02:19 rancher1 kernel: [2089794.167841] Code: c1 e3 07 48 c1 eb 10 48 8d 1c d8 48 89 df e8 49 9f 79 00 80 63 07 fb 48 85 db 74 17 48 89 df c6 07 00 0f 1f 40 00 31 c0 5b 5d c3 <80> 24 25 07 00 00 00 fb 31 c0 5b 5d c3 b8 f0 ff ff ff eb e9 0f Apr 7 14:02:19 rancher1 kernel: [2089794.237196] RIP: split_swap_cluster+0x4f/0x70 RSP: aaf900fbfbe0 Apr 7 14:02:19 rancher1 kernel: [2089794.259910] CR2: 0007 Apr 7 14:02:19 rancher1 kernel: [2089794.270891] ---[ end trace 5b797d89aee7fc1b ]--- The machine become unstable after this until reboot, like reading some namespaced process' command arguments hung, so it is possible that there was some kernel data structure corruption. The machine was under large memory pressure, when this happened. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1888297] [NEW] usb camera only works once until reset
You have been subscribed to a public bug: I have a usb camera (SDI camera, attached to magewell usb capture) which only works once. It displays the image in something like OBS Studio or ffplay, and works perfectly. I can stop the capture. Then trying to open the camera a second time does not work, I get a black screen in ffplay/OBS. To fix this, I can unplug the device and plug it back in, at which point it works until stopped and restarted. So basically, I always have to unplug it and plug it back in after stopping otherwise it won't display an image a second time. Debian 10 works perfectly fine using same physical hardware and video software, but using (x)ubuntu 20.04 I get the problem as noted above. So I suspect a kernel bug/regression. I'm using an AMD 16 core system but don't know if it's related to that. It makes no difference whether I use the USB ports on the motherboard (USB 3.1), or whether I use an addon USB 3.1 PCI card. (And debian doesn't care either which usb port I use, it works correctly there across the board). I have no idea how to report more information. I've done the software updates etc., so whatever kernel is running in 20.04 as of this date, that's what I'm using now. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- usb camera only works once until reset https://bugs.launchpad.net/bugs/1888297 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] Re: System freezes on specific kernel
Hi Anand, Yes, that patch is available since 4.4.0-185.215. Please note that this version if for the linux-image-4.4.0-185-generic package. You mentioned version numbers for the linux-generic meta package (which pulls in linux-image--generic package as a dependency.) Either way, the first number (-185, -186, etc) match between both packages. If you're on -186 the fix should be available since it's present since -185. cheers, Mauricio -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Confirmed Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864392] Re: Intel WiFi [8086:02f0] subsystem [8086:0030] not working
Please attach your `journalctl > journal.log`. Need logs to see what's going on. ** No longer affects: backport-iwlwifi-dkms (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864392 Title: Intel WiFi [8086:02f0] subsystem [8086:0030] not working Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. enx00249b1ec202 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. enx00249b1ec202 no wireless
[Kernel-packages] [Bug 1871041] Re: Nvidia drivers not working with GeForce GTX 1650 Mobile / Max-Q
Thanks!! it worked -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871041 Title: Nvidia drivers not working with GeForce GTX 1650 Mobile / Max-Q Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: *** WORKAROUND AVAILABLE *** See comment 12: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1871041/comments/12 *** Original Description *** I recently installed Ubuntu 20.04 on a Dell XPS 15, which has a GeForce GTX 1650 Mobile / Max-Q. I installed version 440 because it introduced support for this card: https://www.nvidia.com/download/driverResults.aspx/146189/en-us However, I don't think it's working correctly because if I run nvidia- smi, it cannot communicate with my card. ``` $ nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. ``` nvidia-prime is on nvidia, and I rebooted since selecting it. However nvidia-config doesn't display the typical options you find when your nvidia card is active. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-440 440.64-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 6 10:58:21 2020 InstallationDate: Installed on 2020-04-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) SourcePackage: nvidia-graphics-drivers-440 UpgradeStatus: No upgrade log present (probably fresh install) *** Update and likely underlying issue *** Given that the workaround to disable Secure Boot made the driver work, I suspect that the issue is actually that when the drivers are installed and signed (with SB active), then the keys are either not imported correctly or mokmanager was not triggered to be loaded upon next reboot. This causes that even if trying to sign the dkms modules, SB finds them to be untrusted and won't allow the nvidia driver to be loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1871041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563]
lol, somehow i can see recent messages in launchpad, but not there... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
