[Kernel-packages] [Bug 1926236] Re: Fix The sound has noise while audio volume is maximum
is in focal-proposed now, please test ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- 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/1926236 Title: Fix The sound has noise while audio volume is maximum Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] The sound has noise while turning the audio volume to maximum [Fix] For VEGA & Polaris, need two patches(landed on mainline kernel) to fix and a modprobe 1.(50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 2.(9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 3. #modprobe amdgpu ppfeaturemask=0xfff7bffb. For Navi_1x, need smc firmware to fix. 1. (4fe6e53b96 linux-firmware) amdgpu: update navi10 SMC firmware 1. (8ab7abaf63 linux-firmware) amdgpu: update navi14 SMC firmware [Test] Verified on RKL platform A. with wx3200(Polaris series) and the following configuration 1. With these two patch, 1.1. (50ceb1fe7a) drm/amd/pm: bug fix for pcie dpm, has landed on oem kernel. 1.2. (9d03730ecb) drm/amd/pm: workaround for audio noise issue, has landed on oem kernel 2. doesn't append ppfeaturemask=0xfff7bffb Can't observe issue. B. With wx5500(Navi series) and update the related firmware, Can't observe issue [Where problems could occur] Because disabling DPM, the power consumption would be slightly higher. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926236/+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 1929147] Re: fix system hang with 5.10 kernel + RX540 on RKL platform
is also in focal-proposed, please test ** Changed in: linux-firmware (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal verification-needed-hirsute -- 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/1929147 Title: fix system hang with 5.10 kernel + RX540 on RKL platform Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] On RKL platform with AMD RX540, system would hang during boot-up. [Fix] AMD introduce a brand new firmware, polaris 12 MC firmware. This fix the issue and the system wouldn't hang during boot-up with AMD RX540. [Test] Verified on RKL platform and AMD RX540 System would boot-up and login to desktop successfully. [Where problems could occur] This's a brand new firmware to support Polaris-series, it may introduce new issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929147/+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 1895276] Re: shmctl04 from ubuntu_ltp_syscalls failed with X-aws / 4.15
Didn't see this on X-aws-4.15 4.15.0-1103.110~16.04.1 Test skipped: shmctl04.c:167: TCONF: kernel doesn't support SHM_STAT_ANY -- 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/1895276 Title: shmctl04 from ubuntu_ltp_syscalls failed with X-aws / 4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue spotted with 4.15.0-1054.58~16.04.1-oracle The test case got re-wrote in the upstream https://github.com/linux-test-project/ltp/commit/234b8f200cd80556a4784a3a6b4b073061128c16#diff-c2b2d6e89ea2cd9831c395fbe1bef9f3 Test failed with: startup='Fri Sep 11 07:28:24 2020' tst_test.c:1250: INFO: Timeout per run is 0h 05m 00s shmctl04.c:115: FAIL: SHM_INFO haven't returned a valid index: SUCCESS (0) shmctl04.c:131: FAIL: Counted used = 0, used_ids = 4 shmctl04.c:72: PASS: used_ids = 4 shmctl04.c:79: PASS: shm_rss = 6 shmctl04.c:86: PASS: shm_swp = 0 shmctl04.c:93: PASS: shm_tot = 7 Summary: passed 4 failed 2 skipped 0 warnings 0 tag=shmctl04 stime=1599809304 dur=0 exit=exited stat=1 core=no cu=0 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1895276/+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 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition enP50s3832 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition enP53p0s0 is not for us (backend 1) ** (generate:59965): DEBUG
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Within the context of this bug report it is valid, as it is specifically about the mainline PPA. ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Like many of you out there I totally disagree with the decision to mark this bug as invalid. I myself am running newer hardware that requires support from kernel 12.x and can now only use compatible kernels like the ones produced by tux-invader, not the ones on the mainline ppa. -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Might as well delete a completely useless page then. -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Invalid Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1813878] Re: lxc test failed on Azure T-4.15
Found on 4.15.0-1115.128~14.04.1 - azure ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1813878 Title: lxc test failed on Azure T-4.15 Status in ubuntu-kernel-tests: Triaged Status in linux-signed-azure package in Ubuntu: New Bug description: There are multiple failures in the lxc test for Azure T-4.15 FAIL: lxc-tests: /usr/bin/lxc-test-autostart FAIL: lxc-tests: /usr/bin/lxc-test-cgpath FAIL: lxc-tests: /usr/bin/lxc-test-concurrent FAIL: lxc-tests: /usr/bin/lxc-test-createtest FAIL: lxc-tests: /usr/bin/lxc-test-destroytest FAIL: lxc-tests: /usr/bin/lxc-test-device-add-remove FAIL: lxc-tests: /usr/bin/lxc-test-ubuntu FAIL: lxc-tests: /usr/bin/lxc-test-unpriv FAIL: lxc-tests: /usr/bin/lxc-test-usernic FAIL: python3: API * lxc-test-autostart --- Setting up the GPG keyring Downloading the image index Downloading the rootfs Downloading the metadata The image cache is now ready Unpacking the rootfs --- You just created an Ubuntu trusty amd64 (20190129_07:43) container. To enable SSH, run: apt install openssh-server No default root or user password are set by LXC. Error starting container: lxc-test-auto Container didn't start FAIL * lxc-test-cgpath setting root password to "root" Password for 'root' changed cgpath.c:69 lxc_cmd_get_cgroup_path returned NULL lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container "lxctest1": Operation not permitted. * lxc-test-concurrent Iteration 1/1 maxfd:18 Executing (create) for 5 containers... Executing (start) for 5 containers... lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container "lxc-test-concurrent-3": Operation not permitted. Stopping the container (lxc-test-concurrent-3) failed... lxc_container: lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container "lxc-test-concurrent-1": Operation not permitted. Stopping the container (lxc-test-concurrent-1) failed... lxc_container: commands.c: lxc_cmd_stop: 628 Failed to stop container "lxc-test-concurrent-0": Operation not permitted. Stopping the container (lxc-test-concurrent-0) failed... thread returned error 1 * /lxc-test-destroytest 75: lxctest1 thought it was defined * lxc-test-device-add-remove lxc_container: lxccontainer.c: add_remove_device_node: 3260 set_cgroup_item failed while adding the device node Adding /dev/network_latency to the container (device_add_remove_test) failed... * lxc-test-ubuntu lxc-start: lxc_start.c: main: 341 The container failed to start. lxc-start: lxc_start.c: main: 343 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 345 Additional information can be obtained by setting the --logfile and --logpriority options. Failed starting ubuntu container * lxc-test-unpriv see bug 1803686 * lxc-test-usernic sent invalidate(passwd) request, exiting sent invalidate(group) request, exiting /usr/sbin/deluser: The user `usernic-user' does not exist. sent invalidate(passwd) request, exiting sent invalidate(group) request, exiting sent invalidate(passwd) request, exiting sent invalidate(group) request, exiting sent invalidate(passwd) request, exiting sent invalidate(group) request, exiting sent invalidate(passwd) request, exiting sent invalidate(group) request, exiting Failed to open connection to "unix:path=/sys/fs/cgroup/cgmanager/sock" message bus: Failed to connect to socket /sys/fs/cgroup/cgmanager/sock: Connection refused FAIL * python3: API Using image from local cache Unpacking the rootfs --- You just created an Ubuntu trusty amd64 (20190129_07:43) container. To enable SSH, run: apt install openssh-server No default root or user password are set by LXC. Getting instance for 'f13fde32-245e-11e9-8017-000d3a942bc7' Creating rootfs using 'download', arch=amd64 Testing the configuration Testing the networking Starting the container Traceback (most recent call last): File "/tmp/tmp.Y8MLapGtid", line 102, in assert(container.init_pid > 1) AssertionError Please see the attachment for the complete test log ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.15.0-1036-azure 4.15.0-1036.38~14.04.2 ProcVersionSignature: User Name 4.15.0-1036.38~14.04.2-username 4.15.18 Uname: Linux 4.15.0-1036-azure x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Jan 30 07:04:25 2019 SourcePackage: linux-signed-azure UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pack
[Kernel-packages] [Bug 1921643] Re: Thunderbolt docking station drops USB
There are many fixes in 5.13-rc*, it may worth a try. If the issue persists, please raise the issue to linux- u...@vger.kernel.org -- 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/1921643 Title: Thunderbolt docking station drops USB Status in linux package in Ubuntu: Incomplete Bug description: My Lenovo Thunderbolt Dock Gen2 randomly drops the USB controller, resulting in no USB at all. It sometimes happens after a few seconds of being plugged in to the notebook, but sometimes it works for hours. The display connected to the dock stays active and working. I tried to blacklist the driver (r8152) for the usb3-ethernet controller, as suggested in a few forums, but it does not solve the issue. dmesg is full of the following messages: [ 1001.028336] xhci_hcd :08:00.0: WARN Event TRB for slot 11 ep 1 with no TDs queued? [ 1001.029304] xhci_hcd :08:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 1 comp_code 1 [ 1001.029324] xhci_hcd :08:00.0: Looking for event-dma 00087785b460 trb-start 00087785b540 trb-end 00087785b540 seg-start 00087785b000 seg-end 00087785bff0 I'm running ubuntu 20.10, but it also happened under 20.04. Everything is up to date as of writing this bugreport. The dock is running the latest firmware, but the issue was present with earlier version of the firmware too. I also tried both thunderbolt ports on the notebook (MSI Prestige 15), the issue happens on both. The dock works flawlessly under windows 10. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.8.0-48-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: viktor 1021 F pulseaudio /dev/snd/controlC0: viktor 1021 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-06-05 (306 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=d852534f-8d9d-4f1f-90c8-c7dadb006539 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2021-03-11 (26 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921643/+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 1839912] Re: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED"
Found on bionic/linux-azure-fips: 4.15.0-2027.30 -- 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/1839912 Title: test_map in ubuntu_bpf failed with "Allowed update sockmap '0:3' not in ESTABLISHED" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This is at lease a test case regression with the proposed kernel: selftests: test_maps Allowed update sockmap '0:3' not in ESTABLISHED not ok 1..3 selftests: test_maps [FAIL] But with older kernel: selftests: test_maps test_maps: OK ok 1..3 selftests: test_maps [PASS] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 13 03:42 seq crw-rw 1 root audio 116, 33 Aug 13 03:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 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: Date: Tue Aug 13 03:52:52 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.family: To be filled by O.E.M. dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839912/+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 1923114] Re: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy
Found on bionic/linux-azure-fips: 4.15.0-2027.30 -- 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/1923114 Title: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Trusty: New Status in linux-azure-4.15 source package in Trusty: New Status in linux-azure source package in Xenial: New Status in linux-azure-4.15 source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-azure-4.15 source package in Bionic: New Status in linux-azure source package in Groovy: New Status in linux-azure-4.15 source package in Groovy: New Bug description: Test cpu-hotplug from ubuntu_kernel_selftests failed with bionic :linux-azure-4.15 running on a Basic A2 with 2 cores (besides other instance types): selftests: cpu-on-off-test.sh pid 28041's current affinity mask: 3 pid 28041's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy offline_cpu_expect_success 1: unexpected fail http://10.246.72.46/4.15.0-1112.124~16.04.1-azure/xenial-linux-azure- azure- amd64-4.15.0-Basic_A2-ubuntu_kernel_selftests/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests .cpu-hotplug/debug/ubuntu_kernel_selftests.cpu-hotplug.DEBUG.html The problem happens at "autotest-client-tests/ubuntu_kernel_selftests /cpu-on-off-test.sh" when executing: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923114/+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 1922111] Re: acpitz-acpi-0 wrong temperature
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1922111 Title: acpitz-acpi-0 wrong temperature Status in linux package in Ubuntu: Expired Bug description: I realized that acpitz-acpi-0 is not well calibrated and it will spike at random times to 70C+ for a second or two and it will come back down to 45C which is the same as Package id 0 from coretemp-isa-. The reason that I am reporting this is because my fan sensor is linked to acpitz-acpi-0 and the fan will just spike randomly due to this issue. Ubuntu 20.04 Kernel 5.8.0-49-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1510 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-12-09 (111 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201201) MachineType: Notebook NV4XMB,ME,MZ Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=e2e77f4c-c9cb-400a-8699-eff3d5a33e37 ro quiet splash i8042.reset i8042.nomux=1 intel_pstate=disable vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-49-generic N/A linux-backports-modules-5.8.0-49-generic N/A linux-firmware1.187.10 Tags: focal Uname: Linux 5.8.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip input lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/03/2020 dmi.bios.release: 7.6 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: NV4XMB,ME,MZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd11/03/2020:br7.6:efr7.2:svnNotebook:pnNV4XMB,ME,MZ:pvrNotApplicable:rvnNotebook:rnNV4XMB,ME,MZ:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: NV4XMB,ME,MZ dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-09T17:20:55.014004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922111/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Mainline kernel is not supported: https://wiki.ubuntu.com/Kernel/MainlineBuilds#Support_.28BEWARE:_there_is_none.29 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Invalid Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1928702] Re: 21.04 - Bay Trail - Annoying Graphic Artifacts
To find the fixing commit, we need to do a reverse bisection: First, find the first -rc kernel works and the last -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect new $(the working version you found) $ git bisect old $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it doesn’t work, $ git bisect old Otherwise, $ git bisect new Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the issue. -- 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/1928702 Title: 21.04 - Bay Trail - Annoying Graphic Artifacts Status in linux package in Ubuntu: Confirmed Bug description: I used Kubuntu 20.10, then migrated to 21.04. [This bug](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624) appeared in kernel version 5.8.0-49. When upgrading to 21.04, it remained in version 5.11.0-17-generic. Today's fix did not help. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-17-generic 5.11.0-17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: danil 772 F pulseaudio /dev/snd/pcmC0D0c: danil 772 F...m pulseaudio /dev/snd/pcmC0D0p: danil 772 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon May 17 19:14:10 2021 InstallationDate: Installed on 2021-05-09 (8 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Notebook W54_W94_W955TU,-T,-C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=e9593473-516a-4042-9484-7d37f7ba6129 ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: atomisp_gmin_platform atomisp_lm3554 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/13/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W54_W94_W955TU,-T,-C dmi.board.vendor: Notebook dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd03/13/2015:br5.6:svnNotebook:pnW54_W94_W955TU,-T,-C:pvrNotApplicable:rvnNotebook:rnW54_W94_W955TU,-T,-C:rvrV1.0:cvnNotebook:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: W54_W94_W955TU,-T,-C dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928702/+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 1929444] Re: SD card initialization on insertion fails
Thanks. I'll need to do bisect to identify which patch cause this problem and report upstream. Could you help me verify the kernel in https://people.canonical.com/~mschiu77/lp1929444/v2? You will need to disable the Secure Boot in the BIOS menu. Please let me know if there's any problem. -- 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/1929444 Title: SD card initialization on insertion fails Status in linux package in Ubuntu: New Bug description: If I boot my laptop with an SD card (actually SDXC) in the MMC slot the system sees it and I can mount and use it. If I then unmount it, remove it then re-insert it I get this in the system ,og: [ 194.673108] mmc0: card e624 removed [ 205.462065] mmc0: cannot verify signal voltage switch [ 205.567479] mmc0: error -84 whilst initialising SD card and the card cannot then be used. It was OK in groovy. It's failing in hirsute. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44104153 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 24 17:36:49 2021 HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c InstallationDate: Installed on 2020-08-13 (284 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+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 1929899] Re: libbpf.so.0 missing version information
I gather the version number came from BCC BPF which is currently 0.20.0 https://github.com/iovisor/bcc/tags It was a failure in dpkg in the sense that dpkg reports the library was installed fine. To me, that would mean it is the version currently set to be used (and if there are alternatives, these should be flagged if not configurable as alternatives). ** Changed in: libbpf (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libbpf in Ubuntu. https://bugs.launchpad.net/bugs/1929899 Title: libbpf.so.0 missing version information Status in libbpf package in Ubuntu: Invalid Bug description: ➜ ip address ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available (required by ip) ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available (required by ip) ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available (required by ip) ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available (required by ip) ip: symbol lookup error: ip: undefined symbol: bpf_object__open_file, version LIBBPF_0.0.6 ➜ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 ➜ sudo apt-cache policy libbpf0:amd64 libbpf0: Installed: 1:0.3-2ubuntu1 Candidate: 1:0.3-2ubuntu1 Version table: *** 1:0.3-2ubuntu1 500 500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libbpf/+bug/1929899/+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 1930179] [NEW] Advantech CAN driver not recognized in Ubuntu Core 20
Public bug reported: CAN module is not built into the kernel source for Ubuntu Core 20, hence, the CAN interface did not show up. Purpose to include Advantech's CAN driver for board MIO5373. Please kindly consider and refer to the attachment for the CAN driver source code and instructions. I hope the driver can be included as part of the official kernel. Thank you. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Advantech MIO5373 - CAN BUS source code" https://bugs.launchpad.net/bugs/1930179/+attachment/5501231/+files/20201224_Linux_Kernel_4.13_to_5.8.1.7z ** Package changed: linux-raspi (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1930179 Title: Advantech CAN driver not recognized in Ubuntu Core 20 Status in snapd package in Ubuntu: New Bug description: CAN module is not built into the kernel source for Ubuntu Core 20, hence, the CAN interface did not show up. Purpose to include Advantech's CAN driver for board MIO5373. Please kindly consider and refer to the attachment for the CAN driver source code and instructions. I hope the driver can be included as part of the official kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1930179/+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 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hi, I have done longer testing of kernel 140 and it has performance degradation issue as well. It took a couple of days to fully max out disk IOs on that kernel with the same load. Therefore, I came back to testing the other kernels in longer time-window. At the moment, I'm running kernel 4.15.0-137-generic. Will leave it running for the next few days to see if there is any difference. -- 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/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel 4.15.0-142-generic disk IOs (writes) are suffering from terrible delay. Time required to write 1GB of data to the dist is ~12 minutes. 1GB in 12 minutes: strace -ttvvff -o mel.strace dd bs=1024k count=1024 if=/dev/zero of=/data/disk_test/dd_test Before the upgrade, it took seconds to complete. The only change which was done on the system was security upgrade done with unattended-upgrade utility and main repositories for bionic and bionic-security. This is physical server LENOVO System x3650 M5, with Symbios Logic MegaRAID SAS-3 3108 disk controller. The only difference which I see is that there are more modules loaded by the latest kernel. I would expect that the performance would be the same. There were no changes to the physical server and the disks are reported as online and healthy. No only dd is affected but also all disk-based operation by barman (we are using postgres steaming backup along with rsync/ssh archiving). I think this could be a kernel bug. I would be happy to provide other information which would help in fixing this problem. = Details: lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 lsmod Module Size Used by ip6_tables 28672 0 iptable_filter 16384 0 ip_tables 28672 1 iptable_filter x_tables 40960 3 iptable_filter,ip6_tables,ip_tables tcp_diag 16384 0 udp_diag 16384 0 raw_diag 16384 0 inet_diag 24576 3 tcp_diag,raw_diag,udp_diag unix_diag 16384 0 binfmt_misc20480 1 ipmi_ssif 32768 0 kvm_intel 217088 0 kvm 614400 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 pcbc 16384 0 aesni_intel 188416 0 aes_x86_64 20480 1 aesni_intel crypto_simd16384 1 aesni_intel glue_helper16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel ipmi_si57344 0 ipmi_devintf 20480 0 ipmi_msghandler53248 3 ipmi_devintf,ipmi_si,ipmi_ssif acpi_pad 180224 0 bonding 163840 0 lp 20480 0 parport49152 1 lp autofs440960 2 mgag20045056 1 i2c_algo_bit 16384 1 mgag200 ttm 106496 1 mgag200 drm_kms_helper172032 1 mgag200 syscopyarea16384 1 drm_kms_helper tg3 167936 0 sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper ptp20480 1 tg3 drm 401408 4 drm_kms_helper,mgag200,ttm pps_core 20480 1 ptp megaraid_sas 143360 12 lspci -vnn -s 0b:00.0 0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02) Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454] Physical Slot: 9 Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0 I/O ports at 2e00 [size=256] Memory at 903f (64-bit, non-prefetchable) [size=64K] Memory at 9040 (64-bit, non-prefetchable) [size=1M] Expansion ROM at [disabled] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [d0] Vital Product Data Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=97 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [1e0] #19 Capabilities: [1c0] Power Budgeting Capabilities: [148] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: megaraid_sas Kernel modules: megaraid_sas S
[Kernel-packages] [Bug 1909499] Re: iwlwifi 0000:03:00.0: No beacon heard and the time event is over already...
Just logging in to say I have this too. Any current workarounds? Interestingly I noticed that this problem only exists in connecting to my wifi router. If I use a 4G wifi hotspot device, the connection is stable. -- 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/1909499 Title: iwlwifi :03:00.0: No beacon heard and the time event is over already... Status in linux-firmware package in Ubuntu: Confirmed Bug description: I see this error frequently inside logs: iwlwifi :03:00.0: No beacon heard and the time event is over already... Also, the internet doesn't seem stable, from time to time it disconnects and reconnects on its own, and other times it disconnects and wants me to enter the key again to connect. However, if i hit the X button to close the password modal and try to connect again from the networks list, it does connect without the need to enter the password. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.6 ProcVersionSignature: Ubuntu 5.4.0-58.64-lowlatency 5.4.73 Uname: Linux 5.4.0-58-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyubo 14448 F pulseaudio /dev/snd/pcmC0D0p: lyubo 14448 F...m pulseaudio CasperMD5CheckResult: skip Date: Mon Dec 28 21:50:51 2020 Dependencies: InstallationDate: Installed on 2020-12-27 (0 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A515-51G PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-lowlatency root=/dev/mapper/vgkubuntu-root ro quiet splash lockdown=confidentiality vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-58-lowlatency N/A linux-backports-modules-5.4.0-58-lowlatency N/A linux-firmware 1.187.6 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.02 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmander_KL dmi.board.vendor: KBL dmi.board.version: V2.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-51G dmi.product.sku: dmi.product.version: V2.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1909499/+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 1898395] Re: [nvidia] [amdgpu] Problem with external monitor
Could this be the problem described here: https://forums.developer.nvidia.com/t/ryzen-7-gtx-1660ti-blank-screen- on-external-outputs-in-hybrid-graphics-mode/157800 ie (and this is the case if the external display is connected to the NVIDIA card): "Using amdgpu as a display offload source is currently not supported due to an incompatibility between how the amdgpu driver creates “transparent huge pages” without the compound page flag set and how the NVIDIA driver tries to map them. You can see that this is happening in the dmesg log: [ 49.852234] Unhandled error in __nv_drm_gem_user_memory_handle_vma_fault: -22 Unfortunately, the only current workaround is to recompile the kernel without the CONFIG_TRANSPARENT_HUGEPAGE flag enabled. We’re investigating other ways to work around the problem." -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1898395 Title: [nvidia] [amdgpu] Problem with external monitor Status in nvidia-graphics-drivers-450 package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: So, I installed Ubuntu 20.04 on my laptop with Ryzen 7 4800h processor and Nvidia gtx 1650 graphic card.. But i wasn't able to make my external monitor work.. At first it wasn't even recognized, but after I updated kernel to version 5.7.1 and with(only with latest) nvidia drivers 450 it recognized external monitor and I get options when I press SUPER KEY + P that I can switch screens.. But even though I pick external monitor and I see that it switch to it, monitor is turned on, but I have only black screen and can't do anything.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.7.1-050701-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 22:59:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 5.7.1-050701-generic, x86_64: installed nvidia, 450.66, 5.7.1-050701-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a43] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3a3f] InstallationDate: Installed on 2020-09-15 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 82B5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=29bfdbd7-583f-4a6e-8e15-9bf5e33c383d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99
[Kernel-packages] [Bug 1929030] Re: cheese image flickers
Problem disappeared after pipewire updates. -- 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/1929030 Title: cheese image flickers Status in linux package in Ubuntu: Confirmed Bug description: Start cheese, the image on the screen flickers and I have a lot of messages: (cheese:5350): cheese-WARNING **: 10:03:34.226: Internal GStreamer error: code not implemented. Please file a bug at https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/new.: ../gst-libs/gst/video/gstvideofilter.c(296): gst_video_filter_transform (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/GstVideoConvert:vfbin-csp: invalid video buffer received I don't know if the problem is due to cheese, starting cheese and doing 'ubuntu-bug cheese' the bug seems opened against linux package. note: problem occurs in both sessions Xorg and Wayland starting cheese as superuser the problem does not occurs the problem is described also in https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/696 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/689 corrado@corrado-n3-ii-0501:~$ apt policy cheese cheese: Installed: 3.38.0-3 Candidate: 3.38.0-3 Version table: *** 3.38.0-3 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-n3-ii-0501:~$ ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu66 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 20 09:56:12 2021 InstallationDate: Installed on 2021-05-01 (18 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501) MachineType: Dell Inc. Inspiron 3793 RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0C1PF2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3793 dmi.product.sku: 097A dmi.sys.vendor: Dell Inc. lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu66 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corrado1517 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-05-01 (18 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 002: ID 145f:02b5 Trust Trust Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3793 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=90e968ca-6cd0-46ed-b382-cab86d63f80c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: wayland-session impish Uname: Linux 5.11.0-16-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: 12/17/2019 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0C1PF2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/17/2019:br1.5:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0C1PF2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3793 dmi.product.sku: 097A dmi.sys.vendor: Dell Inc. To manage notifications a
