[Kernel-packages] [Bug 1900792] 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 1900792 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: groovy -- 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/1900792 Title: Audio doesn't work on Ubuntu 20.10 Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description: This happens on almost of Intel client platforms(ICL, TGL, CML, CFL, JSL...). This is a regression issue happen. Ubuntu 20.04 doesn't have this problem. We ever try legacy audio, HDMI audio, DP audio, doesn't work. The only working audio is audio output from Thunderbolt docking. Target Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1900792/+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 1900792] Re: Audio doesn't work on Ubuntu 20.10
@hui, do you have any clue for that? I suspect it is related with user configuraiton. -- 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/1900792 Title: Audio doesn't work on Ubuntu 20.10 Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: This happens on almost of Intel client platforms(ICL, TGL, CML, CFL, JSL...). This is a regression issue happen. Ubuntu 20.04 doesn't have this problem. We ever try legacy audio, HDMI audio, DP audio, doesn't work. The only working audio is audio output from Thunderbolt docking. Target Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1900792/+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 1900792] [NEW] Audio doesn't work on Ubuntu 20.10
Public bug reported: Description: This happens on almost of Intel client platforms(ICL, TGL, CML, CFL, JSL...). This is a regression issue happen. Ubuntu 20.04 doesn't have this problem. We ever try legacy audio, HDMI audio, DP audio, doesn't work. The only working audio is audio output from Thunderbolt docking. Target Release: 20.10 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1900792 Title: Audio doesn't work on Ubuntu 20.10 Status in intel: New Status in linux package in Ubuntu: New Bug description: Description: This happens on almost of Intel client platforms(ICL, TGL, CML, CFL, JSL...). This is a regression issue happen. Ubuntu 20.04 doesn't have this problem. We ever try legacy audio, HDMI audio, DP audio, doesn't work. The only working audio is audio output from Thunderbolt docking. Target Release: 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1900792/+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 1892483] Re: Synaptics TouchPad not getting detected
[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/1892483 Title: Synaptics TouchPad not getting detected Status in linux package in Ubuntu: Expired Bug description: I had bought a new laptop and the touchpad is not working in ubuntu. It works well in Windows10. I had searched about this and found a few fixes but none worked. I had tried cat /proc/bus/input/devices and it didn't show any touchpad. My laptop details: IdeaPad-3-14IIL05 Lenovo IdeaPad Slim 3, Intel® Core™ i3-1005G1 CPU @ 1.20GHz × 4 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) Tags: focal Uname: Linux 5.8.2-050802-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2020-08-19 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892483/+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 1900088] Re: Improve descriptions for XFAIL cases in kselftests/net/psock_snd
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1900088 Title: Improve descriptions for XFAIL cases in kselftests/net/psock_snd Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == The test output in psock_snd.sh is confusing sometimes. Here is an output example: raw csum_off with bad offset (fails) ./psock_snd: write: Invalid argument The first line is the test case description, and the second is the test execution output. It feels like this test has failed, but it has passed instead. The "fails" here means this test is expected to fail. But you will have to check the source code to know this fact. == Fix == * 30ae801746ea selftests/net: improve descriptions for XFAIL cases in psock_snd.sh Change "fails" in the test case description to "expected to fail", so that the test output can be more understandable. This test case exists after Bionic, and it can be cherry-picked. == Regression Potential == Low, minor changes for test case description only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900088/+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 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
Patches have been submitted to the Ubuntu kernel mailing list: Patchset for Bionic: https://lists.ubuntu.com/archives/kernel-team/2020-October/114166.html https://lists.ubuntu.com/archives/kernel-team/2020-October/114167.html https://lists.ubuntu.com/archives/kernel-team/2020-October/114168.html https://lists.ubuntu.com/archives/kernel-team/2020-October/114169.html Patchset for Focal: https://lists.ubuntu.com/archives/kernel-team/2020-October/114170.html https://lists.ubuntu.com/archives/kernel-team/2020-October/114171.html https://lists.ubuntu.com/archives/kernel-team/2020-October/114172.html https://lists.ubuntu.com/archives/kernel-team/2020-October/114173.html -- 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/1898786 Title: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1898786 [Impact] Systems that utilise bcache can experience extremely high IO wait times when under constant IO pressure. The IO wait times seem to stay at a consistent 1 second, and never drop as long as the bcache shrinker is enabled. If you disable the shrinker, then IO wait drops significantly to normal levels. We did some perf analysis, and it seems we spend a huge amount of time in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". Looking at the recent commits in Bionic, we found the following commit merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through upstream stable: commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b Author: Coly Li Date: Wed Nov 13 16:03:24 2019 +0800 Subject: bcache: at least try to shrink 1 node in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b It mentions in the description that: > If sc->nr_to_scan is smaller than c->btree_pages, after the above > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring > and releasing mutex c->bucket_lock. This seems to be what is going on here, but the above commit only addresses when nr is 0. From what I can see, the problems we are experiencing are when nr is 1 or 2, and again, we just waste time in bch_mca_scan() waiting on c->bucket_lock, only to release c->bucket_lock since the shrinker loop never executes since there is no work to do. [Fix] The following commits fix the problem, and all landed in 5.6-rc1: commit 125d98edd11464c8e0ec9eaaba7d682d0f832686 Author: Coly Li Date: Fri Jan 24 01:01:40 2020 +0800 Subject: bcache: remove member accessed from struct btree Link: https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686 commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 Author: Coly Li Date: Fri Jan 24 01:01:41 2020 +0800 Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 commit e3de04469a49ee09c89e80bf821508df458ccee6 Author: Coly Li Date: Fri Jan 24 01:01:42 2020 +0800 Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6 The first commit is a dependency of the other two. The first commit removes a "recently accessed" marker, used to indicate if a particular cache has been used recently, and if it has been, not consider it for cache eviction. The commit mentions that under heavy IO, all caches will end up being recently accessed, and nothing will ever be shrunk. The second commit changes a previous design decision of skipping the first 3 caches to shrink, since it is a common case to call bch_mca_scan() with nr being 1, or 2, just like 0 was common in the very first commit I mentioned. This time, if we land on 1 or 2, the loop exits and nothing happens, and we waste time waiting on locks, just like the very first commit I mentioned. The fix is to try shrink caches from the tail of the list, and not the beginning. The third commit fixes a minor issue where we don't want to re-arrange the linked list c->btree_cache, which is what the second commit ended up doing, and instead, just shrink the cache at the end of the linked list, and not change the order. One minor backport / context adjustment was required in the first commit for Bionic, and the rest are all clean cherry picks to Bionic and Focal. [Testcase] This is kind of hard to test, since the problem shows up in
[Kernel-packages] [Bug 1481442] Re: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor turns off during boot
** Tags removed: vivid wily ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Changed in: plymouth (Ubuntu) Status: New => Triaged ** Changed in: plymouth (Ubuntu) Importance: Undecided => Medium -- 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/1481442 Title: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor turns off during boot Status in linux package in Ubuntu: Triaged Status in plymouth package in Ubuntu: Triaged Bug description: When booting HP Pavilion dv6-6145eo with Ubuntu 15.04 the laptop monitor turns off in the middle of the boot. WORKAROUND: Changing in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT from: quiet splash to: quiet WORKAROUND: If I suspend and resume the computer (close and open the lid) when I hear the login sound the monitor turns back on and the computers works just fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: markus 1653 F pulseaudio /dev/snd/controlC0: markus 1653 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 4 21:24:03 2015 HibernationDevice: RESUME=UUID=1496baa6-25ad-490c-8be1-371b62216282 InstallationDate: Installed on 2015-08-04 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=36500a23-b99a-4df0-9cd8-24126399d9d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 358D dmi.board.vendor: Hewlett-Packard dmi.board.version: 33.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124461620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481442/+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 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1898786 [Impact] Systems that utilise bcache can experience extremely high IO wait times when under constant IO pressure. The IO wait times seem to stay at a consistent 1 second, and never drop as long as the bcache shrinker is enabled. If you disable the shrinker, then IO wait drops significantly to normal levels. We did some perf analysis, and it seems we spend a huge amount of time in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". Looking at the recent commits in Bionic, we found the following commit merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through upstream stable: commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b Author: Coly Li Date: Wed Nov 13 16:03:24 2019 +0800 Subject: bcache: at least try to shrink 1 node in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b It mentions in the description that: > If sc->nr_to_scan is smaller than c->btree_pages, after the above > calculation, variable 'nr' will be 0 and nothing will be shrunk. It is > frequeently observed that only 1 or 2 is set to sc->nr_to_scan and make > nr to be zero. Then bch_mca_scan() will do nothing more then acquiring > and releasing mutex c->bucket_lock. This seems to be what is going on here, but the above commit only addresses when nr is 0. From what I can see, the problems we are experiencing are when nr is 1 or 2, and again, we just waste time in bch_mca_scan() waiting on c->bucket_lock, only to release c->bucket_lock since the shrinker loop never executes since there is no work to do. [Fix] The following commits fix the problem, and all landed in 5.6-rc1: commit 125d98edd11464c8e0ec9eaaba7d682d0f832686 Author: Coly Li Date: Fri Jan 24 01:01:40 2020 +0800 Subject: bcache: remove member accessed from struct btree Link: https://github.com/torvalds/linux/commit/125d98edd11464c8e0ec9eaaba7d682d0f832686 commit d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 Author: Coly Li Date: Fri Jan 24 01:01:41 2020 +0800 Subject: bcache: reap c->btree_cache_freeable from the tail in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/d5c9c470b01177e4d90cdbf178b8c7f37f5b8795 commit e3de04469a49ee09c89e80bf821508df458ccee6 Author: Coly Li Date: Fri Jan 24 01:01:42 2020 +0800 Subject: bcache: reap from tail of c->btree_cache in bch_mca_scan() Link: https://github.com/torvalds/linux/commit/e3de04469a49ee09c89e80bf821508df458ccee6 The first commit is a dependency of the other two. The first commit removes a "recently accessed" marker, used to indicate if a particular cache has been used recently, and if it has been, not consider it for cache eviction. The commit mentions that under heavy IO, all caches will end up being recently accessed, and nothing will ever be shrunk. The second commit changes a previous design decision of skipping the first 3 caches to shrink, since it is a common case to call bch_mca_scan() with nr being 1, or 2, just like 0 was common in the very first commit I mentioned. This time, if we land on 1 or 2, the loop exits and nothing happens, and we waste time waiting on locks, just like the very first commit I mentioned. The fix is to try shrink caches from the tail of the list, and not the beginning. The third commit fixes a minor issue where we don't want to re-arrange the linked list c->btree_cache, which is what the second commit ended up doing, and instead, just shrink the cache at the end of the linked list, and not change the order. - All commits are clean cherry picks to Bionic and Focal. + One minor backport / context adjustment was required in the first commit + for Bionic, and the rest are all clean cherry picks to Bionic and Focal. [Testcase] This is kind of hard to test, since the problem shows up in production environments that are under constant IO pressure, with many different items entering and leaving the cache. The Launchpad git server is currently suffering this issue, and has been sitting at a constant IO wait of 1 second / slightly over 1 second which was causing slow response times, which was leading to build failures when git clones ended up timing out. We installed a test kernel, which is available in the following PPA: https://launchpad.net/~mruffell/+archive/ubuntu/sf294907-test Once the test kernel had been installed, IO wait times with the shrinker enabled dropped to normal levels, and the git server became responsive again. We have been monitoring the performance of the git server and watching IO wait times in grafana over the past week, and everything is looking good, and indicate that these patches solve the issue. [Regression Potential] If a regression were to occur, it would only affect users of bcache
[Kernel-packages] [Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
Thanks Lee... I think there are two different issues that need to be resolved. First, is that we recently introduced patches to the 5.4 kernel for Intel x710 NICs because 5.4 only saw some of the NIC ports. So to solve that problem, we would need new maas images spun that include the latest 5.4 kernel SRU for the boot-kernel and boot-initrd, so that MAAS deployments will succeed on systems that use the Intel X710 LOM. Second, is this issue. The two look similar at first, BUT, as Alec reported, after Oct 5, focal deployments that DID work are now not working. And looking at the images on maas.io, the most recent focal ones were from Oct 5, which would hint to me that something broke in that image update. Lee, I wonder¸ is there a way for them to download the older images from here: http://images.maas.io/ephemeral-v3/stable/focal/amd64/20200930/ga-20.04/generic/ to see if restoring the older maas images and boot media resolves the issue? I looked on one of my MAAS servers and it has only the Oct 5 update, and on another MAAS server, it only has the Sept 30 update. So am I correct in thinking that downloading that media to a new subdirectory in /var/lib/maas/boot-resources and then pointing the "current" symlink to that older media would allow them to boot using the older Sept 30 kernel and initrd? Just curious if that would work. If for no other reason than to verify that indeed the breakage is in the Oct 5 images as a sort of bisect. -- 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/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: New Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Yes, on 20.10 beta the bug seems to have been fixed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
Last week we split the image stream hosted at images.maas.io into candidate and stable. daily now redirects to stable. There have been no changes to the images, only the label has been changed. lp:maas-images only downloads the SquashFS from http://cloud-images.ubuntu.com/ and pulls the kernel out of the Debian package. It has no control over the contents of the image or kernel. ** No longer affects: maas-images -- 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/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: New Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M.
[Kernel-packages] [Bug 1898786] Re: bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled
** Summary changed: - Issue with bcache bch_mca_scan causing huge IO wait + bcache: Issues with large IO wait in bch_mca_scan() when shrinker is enabled ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Description changed: - Hello, + BugLink: https://bugs.launchpad.net/bugs/1898786 - In short, we faced an issue with a huge IO wait on a bionic Ubuntu 4.15.0-118.119-generic kernel. - This is the full list of process and the kernel function they were stuck in [0]. + [Impact] - The main issue can probably be summarized by this perf reports - * first identify that the cpu are stuck in idle because of something[1] - * second, see what kernel function seems to stuck the process kswapd0 and kswapd1 [2]. - - We could see that this seems to be the mutex_lock in the bch_mca_scan - function [3]. - - After running the command: - - | sudo bash -c "echo 1 > /sys/fs/bcache/f1a1e8cb-3e6b-40ea-852e- - 583c48d0c2b8/internal/btree_shrinker_disabled" - - The server started to respond normally and the IO wait dropped - significantly - - Here is a trace of the bcache event related lock in the kernel obtained - with some bpfcc-tools [4]. - - klockstat-bpfcc -c bch_ -i 5 -s 3 - - The trace has been run in parallel with the following command line - - echo "Shrinker disabled: $(date)"; sleep 60; echo "Enabling shrinker: - $(date)"; echo 0 | sudo tee - /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled ; sleep - 60; echo "Disabling shrinker: $(date)"; echo 1 | sudo tee - /sys/block/bcache0/bcache/cache/internal/btree_shrinker_disabled; sleep - 60; echo "End of test: $(date)" - - Trying to dig more, we reduced by 20 GB the memory allocated to a VM on the server. - * The bcache btree size fluctuation seems "normal" [5] - * I noticed that, when the shrinker was enabled,a lot of time was spent in the locks during "bch_btree_insert_node". [6] - - I decided to check if one of the function called during - bch_btree_insert_node was taking longer than usual when the shrinker was + Systems that utilise bcache can experience extremely high IO wait times + when under constant IO pressure. The IO wait times seem to stay at a + consistent 1 second, and never drop as long as the bcache shrinker is enabled. - I finally found the "funclatency" tool and tried do have the same approach I had with the klockstat [7]. However, that was inconclusive. I could see there that the bch_btree_insert_node was barely called during the whole duration of the test. - Which made me think it's amount of time spent in lock is more due to another process acquiring the lock. + If you disable the shrinker, then IO wait drops significantly to normal + levels. - I'm going to try to have another go with some perf/klockstat/funclatency - focused on bch_mca_scan and the function called there. + We did some perf analysis, and it seems we spend a huge amount of time + in bch_mca_scan(), likely waiting for the mutex ">bucket_lock". - Also, here are some memory related metrics [8]. + Looking at the recent commits in Bionic, we found the following commit + merged in upstream 5.1-rc1 and backported to 4.15.0-87-generic through + upstream stable: - Now another perf stacktrace with the command used [9]. - Strangely this one doesn't show any bch_mca_scan at all. + commit 9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b + Author: Coly Li + Date: Wed Nov 13 16:03:24 2019 +0800 + Subject: bcache: at least try to shrink 1 node in bch_mca_scan() + Link: https://github.com/torvalds/linux/commit/9fcc34b1a6dd4b8e5337e2b6ef45e428897eca6b - I enabled the shrinker again, hoping to get more traces, but apparently the timeframe was not right. Not enough load to trigger the cliff resulting in a 1sec IOwait plateau. - Which is interesting because that means that without the maximal workload, the kernel can cope with the shrinker. + It mentions in the description that: - [0]: https://pastebin.ubuntu.com/p/QYXPdsMCWC/ - [1]: https://pastebin.ubuntu.com/p/BFsvF7H54r/ - [2]: https://pastebin.ubuntu.com/p/35qdsHYHf5/ - [3]: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/drivers/md/bcache/btree.c?h=Ubuntu-4.15.0-118.119#n674 - [4]: https://pastebin.ubuntu.com/p/qhyqP35fCw/ - [5]: https://pastebin.ubuntu.com/p/McjxxqTVjn/ - [6]: https://pastebin.ubuntu.com/p/KmrnW4Ng8F/ - [7]: https://pastebin.ubuntu.com/p/fSX4c7tTFV/ - [8]:
[Kernel-packages] [Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
Hi Jeffrey, Here's the output of the commands you requested: 1. certuser@maas216-cert:~$ ls -l /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily total 460480 -rw-r--r-- 3 maas maas 86260608 Oct 6 00:25 boot-initrd -rw-r--r-- 3 maas maas 11678464 Sep 29 01:57 boot-kernel -rw-r--r-- 4 maas maas 373587968 Oct 6 00:25 squashfs 2. certuser@maas216-cert:~$ sha256sum /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/* 273212b1858bc4441b392900123f1433733023986d542e8d2caf458fbb48edb2 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/boot-initrd 1a8aec22331f411cdbc61c367b7397cf0d6cda7a85afc94c7ebb64ec478c32b8 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/boot-kernel 0caa3059361ab22a75f9797834ff7bcce372621919122a7d8289b66a1a9c8084 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/squashfs Thanks Alec -- 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/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: New Status in maas-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature:
[Kernel-packages] [Bug 1746837] Re: Add support for Realtek card reader RTL8411B [10EC:5287]
I'm still experiencing this issue on kernel 5.4.0-51-generic. The driver is missing, and the reader fails to recognize some types of SD cards. I tried installing linux-oem-osp1, nothing has improved. -- 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/1746837 Title: Add support for Realtek card reader RTL8411B [10EC:5287] Status in linux package in Ubuntu: Confirmed Bug description: The latest kernel upgrade seems to break the driver. Ubuntu 4.4.0-112.135-generic 4.4.98 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5287] (rev 01) Description: Ubuntu 16.04.3 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746837/+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 1899336] Re: Thinkpad T14s (AMD) external monitors on docking station no longer detected
I finally managed to boot kernel 5.9 after several dozen tries. "dmesg" output is attached, in case it is of interest. ** Attachment added: "dmesg-2020-10-20.txt" https://bugs.launchpad.net/ubuntubudgie/+bug/1899336/+attachment/5424789/+files/dmesg-2020-10-20.txt -- 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/1899336 Title: Thinkpad T14s (AMD) external monitors on docking station no longer detected Status in Ubuntu Budgie: New Status in linux package in Ubuntu: Confirmed Bug description: I run Ubuntu Budgie 20.04 on my Lenovo ThinkPad T14s with Ryzen 4750U processor together with the "Lenovo ThinkPad USB-C Dock (Gen 2)" (40AS0090EU). The docking station is connected via USB-C to the system, supplies it with power via USB Power Delivery and provides USB 3.1 Gen 2 (10 Gbit/s) connectivity (including an Ethernet controller and audio codec running over the USB data path), as well as support for two monitors via "DisplayPort alternate mode" of USB-C, so technically it will configure the four high-speed lanes of USB-C as one lane for SuperSpeed+ RX, one lane for SuperSpeed+ TX, and two lanes for DisplayPort 1.4, the latter of which the docking station will then demultiplex onto two full-size DisplayPort connectors like an MST hub. So far, external monitors have worked fine most of the time. However, for a couple of days now, I cannot get the system to detect the external monitors connected to my docking station anymore. The "BIOS" (EFI) boot screen (with the Lenovo logo) still shows up on the external monitors. However, both the LUKS/dm-crypt pre-boot- authentication screen (since I use full-disk-encryption) and also the desktop after login show up on the internal display, even with the laptop connected to the docking station, so it appears like the kernel no longer detects the monitors connecting via "DisplayPort alternate mode". Yesterday, I could get the monitors to show up by disconnecting the laptop from the docking station and reconnecting it again. Today, not even this appears to work. Sometimes the external monitors are detected (and shown as "enabled") in the display settings of Budgie, sometimes they do not even show up. Even when they show up and are enabled, nothing is displayed on them. The monitors say they do not receive a signal and I should check the connection. Unplugging and replugging the cables from the docking station to the monitors does not change anything. Audio, Ethernet and USB runs fine over the docking station, just DisplayPort does not. This is obviously very bad, since I now have to work on the internal display even with the laptop docked. I have the "amdgpu.exp_hw_support=1" in my kernel arguments (*) and the Ryzen 4000 GPU appears to be recognized. $ lspci -k 06:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev d1) Subsystem: Lenovo Renoir Kernel driver in use: amdgpu Kernel modules: amdgpu $ (*) When I installed Ubuntu Budgie 20.04, I needed to add this in order to extend my desktop over the two external monitors. Without this argument, the system only showed a single display in the settings, the same content was displayed on all connected monitors (mirrored) and there was no way to change that. I have attached parts of "dmesg" output which I deem relevant. $ uname -a Linux thinkpad-t14s 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-27 (75 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20UH001AGE Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=UUID=5b605ccb-8a29-46ee-b571-e0d61a323457 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 RelatedPackageVersions: linux-restricted-modules-5.4.0-48-generic N/A linux-backports-modules-5.4.0-48-generic N/A linux-firmware1.187.3 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/11/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET36W(1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001AGE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Kernel-packages] [Bug 1900757] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1900757 Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. Status in linux package in Ubuntu: Confirmed Bug description: Idk I was playing minecraft ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: linux-modules-5.4.0-52-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 20 18:59:14 2020 Dependencies: DpkgTerminalLog: [1mdpkg:[0m erreur de traitement du paquet linux-modules-5.4.0-52-generic (--remove) : Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. ErrorMessage: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. InstallationDate: Installed on 2020-09-06 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=4656160f-d86a-466f-8301-257cbc4833cf ro quiet splash amd_iommu=on kvm.ignore_msrs=1 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2008 dmi.board.asset.tag: Default string dmi.board.name: TUF B450-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2008:bd12/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900757/+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 1900468] Re: Snap store will not display packages other than editors picks.
I have Restarted virtual box several times and just checked the Snap Store. On Explore tab i have editors picks and all of the Categories below, Art and Design all the way to Utilities. I checked for system software updates installed them, one of the updates was 'snap update'. I would like to Close this Bug report, Thank You. I thank everyone for all of the hard work and dedication for Ubuntu that is accomplished every day. -- 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/1900468 Title: Snap store will not display packages other than editors picks. Status in linux package in Ubuntu: Confirmed Bug description: In Virtual Box I upgraded Ubuntu 18.04 to 20.04 the snap store only displays editor's pick of packages. Installed package list works, package search works. No list of available packages in groups. Seems to be stuck on the editors pick page in the Explore tab. Updates tab- system up to date. Right click for screen shot not working on snap store page. lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 version of package snap store latest/stable/ubuntu-20.04 3.36.0-82-g80486d0 10/12/2020 snapd version 2.47 10/14/2020 I expected to see the usual listings of other packages available. This is very similar to Bug 1900321 and Bug 1899860 https://packages.ubuntu.com/focal/snapd ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: b3 1005 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 12:05:54 2020 InstallationDate: Installed on 2020-10-10 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=33383ad6-5ca8-47c1-948f-f278bfb74a18 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900468/+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 1900468] Re: Snap store will not display packages other than editors picks.
I have Restarted virtual box several times and just checked the Snap Store. On Explore tab i have editors picks and all of the Categories below, Art and Design all the way to Utilities. I would like to Close this Bug report, Thank You. -- 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/1900468 Title: Snap store will not display packages other than editors picks. Status in linux package in Ubuntu: Confirmed Bug description: In Virtual Box I upgraded Ubuntu 18.04 to 20.04 the snap store only displays editor's pick of packages. Installed package list works, package search works. No list of available packages in groups. Seems to be stuck on the editors pick page in the Explore tab. Updates tab- system up to date. Right click for screen shot not working on snap store page. lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 version of package snap store latest/stable/ubuntu-20.04 3.36.0-82-g80486d0 10/12/2020 snapd version 2.47 10/14/2020 I expected to see the usual listings of other packages available. This is very similar to Bug 1900321 and Bug 1899860 https://packages.ubuntu.com/focal/snapd ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: b3 1005 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 19 12:05:54 2020 InstallationDate: Installed on 2020-10-10 (8 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=33383ad6-5ca8-47c1-948f-f278bfb74a18 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900468/+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 1900757] [NEW] package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer
Public bug reported: Idk I was playing minecraft ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: linux-modules-5.4.0-52-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 20 18:59:14 2020 Dependencies: DpkgTerminalLog: [1mdpkg:[0m erreur de traitement du paquet linux-modules-5.4.0-52-generic (--remove) : Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. ErrorMessage: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. InstallationDate: Installed on 2020-09-06 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=4656160f-d86a-466f-8301-257cbc4833cf ro quiet splash amd_iommu=on kvm.ignore_msrs=1 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2008 dmi.board.asset.tag: Default string dmi.board.name: TUF B450-PLUS GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2008:bd12/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1900757 Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. Status in linux package in Ubuntu: New Bug description: Idk I was playing minecraft ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: linux-modules-5.4.0-52-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 20 18:59:14 2020 Dependencies: DpkgTerminalLog: [1mdpkg:[0m erreur de traitement du paquet linux-modules-5.4.0-52-generic (--remove) : Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. ErrorMessage: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. InstallationDate: Installed on 2020-09-06 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=4656160f-d86a-466f-8301-257cbc4833cf ro quiet splash amd_iommu=on kvm.ignore_msrs=1 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.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 RfKill: SourcePackage: linux Title: package linux-modules-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2008
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Invalid Status in linux-aws source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Released Status in linux-aws source package in Eoan: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Javier That is weird that laptop does not have a intel bluetooth/wifi chip? I own one too as a private laptop and it has a qualcomm that should not be affected by this bug. Can you please post which chipset is has? Maybe Dell released one with an intel chipset too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
@rbalint, we have not seen the same issue with the 4.15 linux-aws-hwe kernels used in xenial. At this time, the backport to xenial is not necessary. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Incomplete Status in linux-aws source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Released Status in linux-aws source package in Eoan: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
Hi Dimitri, the last time I tested secure boot installation was at 20.04 on this particular laptop. All was ok at that time. enc are the installer tarball and the mok results. TIA ** Attachment added: "installation.tar" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5424744/+files/installation.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
** Attachment added: "mok.txt" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+attachment/5424745/+files/mok.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+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 1900741] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1900741
Title:
Missing battery status information on HP Pavilion Notebook 15 bc5xxx
Status in linux package in Ubuntu:
Confirmed
Bug description:
Running groovy daily in the said laptop, but battery information
aren't properly provided (it's always marked as full):
gdbus introspect --system --dest org.freedesktop.UPower --object-path
/org/freedesktop/UPower/devices/battery_BAT0
node /org/freedesktop/UPower/devices/battery_BAT0 {
interface org.freedesktop.DBus.Properties {
methods:
Get(in s interface_name,
in s property_name,
out v value);
GetAll(in s interface_name,
out a{sv} properties);
Set(in s interface_name,
in s property_name,
in v value);
signals:
PropertiesChanged(s interface_name,
a{sv} changed_properties,
as invalidated_properties);
properties:
};
interface org.freedesktop.DBus.Introspectable {
methods:
Introspect(out s xml_data);
signals:
properties:
};
interface org.freedesktop.DBus.Peer {
methods:
Ping();
GetMachineId(out s machine_uuid);
signals:
properties:
};
interface org.freedesktop.UPower.Device {
methods:
@org.freedesktop.DBus.GLib.Async("")
Refresh();
@org.freedesktop.DBus.GLib.Async("")
GetHistory(in s type,
in u timespan,
in u resolution,
out a(udu) data);
@org.freedesktop.DBus.GLib.Async("")
GetStatistics(in s type,
out a(dd) data);
signals:
properties:
readonly s NativePath = 'BAT0';
readonly s Vendor = 'HP';
readonly s Model = 'Primary';
readonly s Serial = '';
readonly t UpdateTime = 1603213894;
readonly u Type = 2;
readonly b PowerSupply = true;
readonly b HasHistory = true;
readonly b HasStatistics = true;
readonly b Online = false;
readonly d Energy = 61.601;
readonly d EnergyEmpty = 0.0;
readonly d EnergyFull = 61.601;
readonly d EnergyFullDesign = 61.601;
readonly d EnergyRate = 0.0;
readonly d Voltage = 17.3850002;
readonly d Luminosity = 0.0;
readonly x TimeToEmpty = 0;
readonly x TimeToFull = 0;
readonly d Percentage = 100.0;
readonly d Temperature = 0.0;
readonly b IsPresent = true;
readonly u State = 2;
readonly b IsRechargeable = true;
readonly d Capacity = 100.0;
readonly u Technology = 1;
readonly u WarningLevel = 1;
readonly u BatteryLevel = 1;
readonly s IconName = 'battery-full-symbolic';
};
};
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-25-generic 5.8.0-25.26
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: marco 1341 F pulseaudio
/dev/snd/controlC1: marco 1341 F pulseaudio
CasperMD5CheckResult: skip
Date: Tue Oct 20 19:13:14 2020
InstallationDate: Installed on 2020-10-20 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201020)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. Realtek
Bluetooth 4.2 Adapter
Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision
HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook 15-bc5xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic
root=/dev/mapper/vgubuntu-eoan--root 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.
RelatedPackageVersions:
linux-restricted-modules-5.8.0-25-generic N/A
linux-backports-modules-5.8.0-25-generic N/A
linux-firmware1.190
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2019
dmi.bios.release: 15.6
dmi.bios.vendor: AMI
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8640
dmi.board.vendor: HP
dmi.board.version: 52.06
dmi.chassis.type: 10
dmi.chassis.vendor
[Kernel-packages] [Bug 1481442] Re: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor turns off during boot
** Description changed: When booting HP Pavilion dv6-6145eo with Ubuntu 15.04 the laptop monitor turns off in the middle of the boot. - If I suspend and resume the computer (close and open the lid) when I - hear the login sound the monitor turns back on and the computers works - just fine. + + WORKAROUND: Changing in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT from: + quiet splash + + to: + quiet + + WORKAROUND: If I suspend and resume the computer (close and open the + lid) when I hear the login sound the monitor turns back on and the + computers works just fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: markus 1653 F pulseaudio - /dev/snd/controlC0: markus 1653 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: markus 1653 F pulseaudio + /dev/snd/controlC0: markus 1653 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 4 21:24:03 2015 HibernationDevice: RESUME=UUID=1496baa6-25ad-490c-8be1-371b62216282 InstallationDate: Installed on 2015-08-04 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: - 0 radeondrmfb - 1 radeondrmfb + 0 radeondrmfb + 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=36500a23-b99a-4df0-9cd8-24126399d9d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.19.0-25-generic N/A - linux-backports-modules-3.19.0-25-generic N/A - linux-firmware 1.143.2 + linux-restricted-modules-3.19.0-25-generic N/A + linux-backports-modules-3.19.0-25-generic N/A + linux-firmware 1.143.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 358D dmi.board.vendor: Hewlett-Packard dmi.board.version: 33.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124461620100 dmi.sys.vendor: Hewlett-Packard ** Tags added: focal ** Changed in: linux (Ubuntu) Importance: High => Low ** Changed in: linux (Ubuntu) Status: Won't Fix => Triaged -- 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/1481442 Title: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor turns off during boot Status in linux package in Ubuntu: Triaged Bug description: When booting HP Pavilion dv6-6145eo with Ubuntu 15.04 the laptop monitor turns off in the middle of the boot. WORKAROUND: Changing in /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT from: quiet splash to: quiet WORKAROUND: If I suspend and resume the computer (close and open the lid) when I hear the login sound the monitor turns back on and the computers works just fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: markus 1653 F pulseaudio /dev/snd/controlC0: markus 1653 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 4 21:24:03 2015 HibernationDevice: RESUME=UUID=1496baa6-25ad-490c-8be1-371b62216282 InstallationDate: Installed on 2015-08-04 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=36500a23-b99a-4df0-9cd8-24126399d9d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
[Kernel-packages] [Bug 1900741] [NEW] Missing battery status information on HP Pavilion Notebook 15 bc5xxx
Public bug reported:
Running groovy daily in the said laptop, but battery information aren't
properly provided (it's always marked as full):
gdbus introspect --system --dest org.freedesktop.UPower --object-path
/org/freedesktop/UPower/devices/battery_BAT0
node /org/freedesktop/UPower/devices/battery_BAT0 {
interface org.freedesktop.DBus.Properties {
methods:
Get(in s interface_name,
in s property_name,
out v value);
GetAll(in s interface_name,
out a{sv} properties);
Set(in s interface_name,
in s property_name,
in v value);
signals:
PropertiesChanged(s interface_name,
a{sv} changed_properties,
as invalidated_properties);
properties:
};
interface org.freedesktop.DBus.Introspectable {
methods:
Introspect(out s xml_data);
signals:
properties:
};
interface org.freedesktop.DBus.Peer {
methods:
Ping();
GetMachineId(out s machine_uuid);
signals:
properties:
};
interface org.freedesktop.UPower.Device {
methods:
@org.freedesktop.DBus.GLib.Async("")
Refresh();
@org.freedesktop.DBus.GLib.Async("")
GetHistory(in s type,
in u timespan,
in u resolution,
out a(udu) data);
@org.freedesktop.DBus.GLib.Async("")
GetStatistics(in s type,
out a(dd) data);
signals:
properties:
readonly s NativePath = 'BAT0';
readonly s Vendor = 'HP';
readonly s Model = 'Primary';
readonly s Serial = '';
readonly t UpdateTime = 1603213894;
readonly u Type = 2;
readonly b PowerSupply = true;
readonly b HasHistory = true;
readonly b HasStatistics = true;
readonly b Online = false;
readonly d Energy = 61.601;
readonly d EnergyEmpty = 0.0;
readonly d EnergyFull = 61.601;
readonly d EnergyFullDesign = 61.601;
readonly d EnergyRate = 0.0;
readonly d Voltage = 17.3850002;
readonly d Luminosity = 0.0;
readonly x TimeToEmpty = 0;
readonly x TimeToFull = 0;
readonly d Percentage = 100.0;
readonly d Temperature = 0.0;
readonly b IsPresent = true;
readonly u State = 2;
readonly b IsRechargeable = true;
readonly d Capacity = 100.0;
readonly u Technology = 1;
readonly u WarningLevel = 1;
readonly u BatteryLevel = 1;
readonly s IconName = 'battery-full-symbolic';
};
};
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-25-generic 5.8.0-25.26
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: marco 1341 F pulseaudio
/dev/snd/controlC1: marco 1341 F pulseaudio
CasperMD5CheckResult: skip
Date: Tue Oct 20 19:13:14 2020
InstallationDate: Installed on 2020-10-20 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201020)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:b00b Realtek Semiconductor Corp. Realtek Bluetooth
4.2 Adapter
Bus 001 Device 002: ID 04f2:b56d Chicony Electronics Co., Ltd HP Wide Vision HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook 15-bc5xxx
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic
root=/dev/mapper/vgubuntu-eoan--root 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.
RelatedPackageVersions:
linux-restricted-modules-5.8.0-25-generic N/A
linux-backports-modules-5.8.0-25-generic N/A
linux-firmware1.190
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2019
dmi.bios.release: 15.6
dmi.bios.vendor: AMI
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8640
dmi.board.vendor: HP
dmi.board.version: 52.06
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 52.6
dmi.modalias:
dmi:bvnAMI:bvrF.06:bd09/03/2019:br15.6:efr52.6:svnHP:pnHPPavilionNotebook15-bc5xxx:pvr:rvnHP:rn8640:rvr52.06:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Notebook 15-bc5xxx
dmi.product.sku: 7VL88EA#ABE
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Medium
Status: Confirmed
** Tags: amd64 apport-bug groovy
--
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/
[Kernel-packages] [Bug 1899678] Re: No wifi after installation - does not work with secure boot enabled
btw, what is the state of MOK? i.e. $ sudo mokutil --list-enrolled $ ls /var/lib/shim-signed $ ls /var/lib/shim-signed/mok/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+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 1899678] Re: No wifi after installation - does not work with secure boot enabled
Can you open bug report against ubiquity with like $ ubuntu-bug ubiquity ? that would collect all the installer logs, which will help to investigate this. Or can you please attach /var/log/installer as a tarball? do check for any sensitive info there, or feel free to mark this bug report private. I don't believe we sign broadcom drivers; thus one should require to enroll into MOK.. i wonder if MOK enrollment is working or not. ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Status in dkms package in Ubuntu: New Status in shim-signed package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+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 1900728] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1900728 Title: Ubuntu boot failure after upgrade to kernel 5.4.0-52 Status in linux package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 LTS. After upgrading from linux 5.4.0-51 to 5.4.0-52 today, the computer boots into initramfs (Busybox) every time I reboot. No disk errors found there. If I use the grub menu to switch back to 5.4.0-51, the system boots and runs normally. This is on a Lenovo P53s laptop running Ubuntu only (no dual boot). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-51-generic 5.4.0-51.56 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1624 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 09:03:33 2020 InstallationDate: Installed on 2020-06-26 (115 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20N6S00B00 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=/vmlinuz-5.4.0-51-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N6S00B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N6S00B00:pvrThinkPadP53s:rvnLENOVO:rn20N6S00B00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53s dmi.product.name: 20N6S00B00 dmi.product.sku: LENOVO_MT_20N6_BU_Think_FM_ThinkPad P53s dmi.product.version: ThinkPad P53s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900728/+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 1899678] Re: No wifi after installation: could not insert 'wl': operation not permitted
Disabling secure boot allows network-manager to display the wifi connections. Installing WITHOUT secure boot also allows network-manager to display the wifi connections. So currently bcmwl-kernel-source will only work with non-secure boot ** Summary changed: - No wifi after installation: could not insert 'wl': operation not permitted + No wifi after installation - does not work with secure boot enabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1899678 Title: No wifi after installation - does not work with secure boot enabled Status in bcmwl package in Ubuntu: New Bug description: After installation I noted that my broadcom wifi was not available. This is a regression from 20.04 where installation automatically installed the broadcom driver. So I tried to force the installation again - see trace below. The dialog message to enter the secure password appeared - however on reboot a confirmation to change the MOK state was not seen - the distro booted straight in. sudo apt install --reinstall bcmwl-kernel-source [sudo] password for dad: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu groovy/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 0s (5,232 kB/s) (Reading database ... 202371 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.8.0-22-generic Building for architecture x86_64 Building initial module for 5.8.0-22-generic Done. wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-22-generic/updates/dkms/ depmod DKMS: install completed. modprobe: ERROR: could not insert 'wl': Operation not permitted update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.137ubuntu12) ... update-initramfs: Generating /boot/initrd.img-5.8.0-22-generic ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 5.8.0-22.23-generic 5.8.14 Uname: Linux 5.8.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Oct 13 18:32:47 2020 InstallationDate: Installed on 2020-10-13 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20201013) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1899678/+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 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
@fginther Xenial does not need the backport, right? ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Xenial: Incomplete Status in linux-aws source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Released Status in linux-aws source package in Eoan: Won't Fix Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1900728] [NEW] Ubuntu boot failure after upgrade to kernel 5.4.0-52
Public bug reported: I'm on Ubuntu 20.04 LTS. After upgrading from linux 5.4.0-51 to 5.4.0-52 today, the computer boots into initramfs (Busybox) every time I reboot. No disk errors found there. If I use the grub menu to switch back to 5.4.0-51, the system boots and runs normally. This is on a Lenovo P53s laptop running Ubuntu only (no dual boot). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-51-generic 5.4.0-51.56 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1624 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 09:03:33 2020 InstallationDate: Installed on 2020-06-26 (115 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20N6S00B00 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=/vmlinuz-5.4.0-51-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N6S00B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N6S00B00:pvrThinkPadP53s:rvnLENOVO:rn20N6S00B00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53s dmi.product.name: 20N6S00B00 dmi.product.sku: LENOVO_MT_20N6_BU_Think_FM_ThinkPad P53s dmi.product.version: ThinkPad P53s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1900728 Title: Ubuntu boot failure after upgrade to kernel 5.4.0-52 Status in linux package in Ubuntu: New Bug description: I'm on Ubuntu 20.04 LTS. After upgrading from linux 5.4.0-51 to 5.4.0-52 today, the computer boots into initramfs (Busybox) every time I reboot. No disk errors found there. If I use the grub menu to switch back to 5.4.0-51, the system boots and runs normally. This is on a Lenovo P53s laptop running Ubuntu only (no dual boot). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-51-generic 5.4.0-51.56 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1624 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 09:03:33 2020 InstallationDate: Installed on 2020-06-26 (115 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20N6S00B00 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=/vmlinuz-5.4.0-51-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-51-generic N/A linux-backports-modules-5.4.0-51-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET91W (1.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N6S00B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET91W(1.69):bd08/12/2020:svnLENOVO:pn20N6S00B00:pvrThinkPadP53s:rvnLENOVO:rn20N6S00B00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53s dmi.product.name: 20N6S00B00 dmi.product.sku: LENOVO_MT_20N6_BU_Think_FM_ThinkPad P53s dmi.product.version: ThinkPad P53s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1900141] Re: overlay: permission regression in 5.4.0-51.56 due to patches related to CVE-2020-16120
I think I see what the problem is, one of the patches adds a check that
is probably unnecessary and too restrictive. This is an upstream issue
though, so I'm going to follow up with the upstream developers to ensure
there isn't a good reason for the check that isn't apparent to me.
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
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/1900141
Title:
overlay: permission regression in 5.4.0-51.56 due to patches related
to CVE-2020-16120
Status in linux package in Ubuntu:
In Progress
Bug description:
We use unprivileged user namespaces with overlay mounts for
containers. After recently upgrading our Focal kernels to 5.4.0-51.56
this breaks, one cannot access files through the overlay mount in the
container anymore. This is very likely caused by some of the patches
that were added in relation to CVE-2020-16120.
The following commands allow to reproduce the problem when executed as
an arbitrary non-root user:
mkdir /tmp/test /tmp/test/upper /tmp/test/work /tmp/test/usr
unshare -m -U -r /bin/sh -c "mount -t overlay none /tmp/test/usr -o
lowerdir=/usr,upperdir=/tmp/test/upper,workdir=/tmp/test/work; ls -l
/tmp/test/usr/bin/id; file /tmp/test/usr/bin/id; /tmp/test/usr/bin/id"
The output when broken is this:
-rwxr-xr-x 1 nobody nogroup 47480 Sep 5 2019 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: executable, regular file, no read permission
/bin/sh: 1: /tmp/test/usr/bin/id: Operation not permitted
The expected output is this:
-rwxr-xr-x 1 nobody nogroup 43224 Jan 18 2018 /tmp/test/usr/bin/id
/tmp/test/usr/bin/id: ELF 64-bit LSB shared object, ...
uid=0(root) gid=0(root) groups=0(root),65534(nogroup)
These commands create a user namespace and within it mount an overlay
of /usr to /tmp/test/usr and then try to access something in it.
This works on Ubuntu Bionic with kernel 4.15.0-121.123 (note that this
already includes a fix for CVE-2020-16120) and on kernel 5.4.0-48.52
but is broken on kernel 5.4.0-51.56, no matter whether on Bionic or
Focal.
So I strongly suspect that not the actual security fixes for
CVE-2020-16120 are the cause, but one of the following two patches
that according to the changelogs were applied in the same revision but
only to 5.4, not to 4.15:
ovl: call secutiry hook in ovl_real_ioctl()
ovl: check permission to open real file
The mail with the announcement (https://www.openwall.com/lists/oss-
security/2020/10/13/6) lists these two commits as separate from the
actual security fixes ("may be desired or necessary").
Is it possible to revert these two changes or fix them such that our
unprivileged containers work again on Ubuntu kernel 5.4? Or is there a
workaround that I can add to my container solution such that this use
case works again?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-51-generic 5.4.0-51.56
ProcVersionSignature: User Name 5.4.0-51.56-generic 5.4.65
Uname: Linux 5.4.0-51-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 14 04:48 seq
crw-rw 1 root audio 116, 33 Oct 14 04:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
CasperMD5CheckResult: skip
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read
kernel buffer failed: Operation not permitted
Date: Fri Oct 16 13:02:32 2020
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-51-generic
root=PARTUUID=59ea2f51-599c-49f2-b9b3-77197e333865 ro console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.4.0-51-generic N/A
linux-backports-modules-5.4.0-51-generic N/A
linux-firmware1.187.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version:
[Kernel-packages] [Bug 1900349] Re: [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but does in 5.4.0-48
After updating again, the bug is gone. I will be closing the bug report ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => 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/1900349 Title: [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but does in 5.4.0-48 Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Bug description: While pusleaudio works properly on gdm before logging in, once I login, it fails. I was able to successfully restart pulseaudio with pulseaudio -k on my first attempt, and one other time, but I have been unable to reproduce this. It (pulseaudio -k )usually does nothing. As such, adding "pulseaudio -k" to run on on login as a workaround does not work. This started happening after updating from kernel 5.4.0-48 to 5.4.0-52. Rolling back to 48 makes the issue go away. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 14:11:31 2020 InstallationDate: Installed on 2020-07-03 (107 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1900349/+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 1900349] Re: [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but does in 5.4.0-48
I am not certain the kernel is the cause, I just noticed the bug manifested when I updated. I will upload apport logs. I don't actually believe it is a kernel bug, because PA works properly on the login screen and only fails after login. -- 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/1900349 Title: [Lenovo IdeaPad 5 15IIL05] Audio does not work in kernel 5.4.0-52, but does in 5.4.0-48 Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: While pusleaudio works properly on gdm before logging in, once I login, it fails. I was able to successfully restart pulseaudio with pulseaudio -k on my first attempt, and one other time, but I have been unable to reproduce this. It (pulseaudio -k )usually does nothing. As such, adding "pulseaudio -k" to run on on login as a workaround does not work. This started happening after updating from kernel 5.4.0-48 to 5.4.0-52. Rolling back to 48 makes the issue go away. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 18 14:11:31 2020 InstallationDate: Installed on 2020-07-03 (107 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1900349/+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 1481442] Re: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor turns off during boot
Tested Ubuntu 20.04 (kernel 5.4.0-52-generic) with the old HP Pavilion dv6 laptop and the bug seems to still exist. Disabling the Plymouth boot screen fixes this bug (changing GRUB_CMDLINE_LINUX_DEFAULT from "quiet splash" to "quiet" in /etc/default/grub). Also closing and opening the laptop lid after boot turns the display back on. -- 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/1481442 Title: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop monitor turns off during boot Status in linux package in Ubuntu: Won't Fix Bug description: When booting HP Pavilion dv6-6145eo with Ubuntu 15.04 the laptop monitor turns off in the middle of the boot. If I suspend and resume the computer (close and open the lid) when I hear the login sound the monitor turns back on and the computers works just fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: markus 1653 F pulseaudio /dev/snd/controlC0: markus 1653 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 4 21:24:03 2015 HibernationDevice: RESUME=UUID=1496baa6-25ad-490c-8be1-371b62216282 InstallationDate: Installed on 2015-08-04 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=36500a23-b99a-4df0-9cd8-24126399d9d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-25-generic N/A linux-backports-modules-3.19.0-25-generic N/A linux-firmware 1.143.2 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 358D dmi.board.vendor: Hewlett-Packard dmi.board.version: 33.18 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124461620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481442/+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 1872510] Re: Slow / Broken Boot on Battery Power
I've worked around whatever bug by forcing iommu to soft ~$ grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet splash iommu=soft" -- 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/1872510 Title: Slow / Broken Boot on Battery Power Status in linux package in Ubuntu: Confirmed Bug description: The behavior is the same booting from USB to install the OS, and booting from NVMe on an installed OS. I'm using disk encryption, but I don't believe it plays a factor. When I boot plugged in to power, the system behaves normally, even once battery is disconnected. I can put the system to sleep on battery, wake on battery, and everything is fine. The initial boot on battery just does not seem happy either way. I've tried both with and without TLP installed. This behavior was present on 18.04, but I assumed it was an "old kernel" issue as this is fairly new hardware. I was previously on Manjaro w/ kernel 5.4, and the system was fine, but using Focal Fossa on kernel 5.4 presents the boot issue. It appears to get through most of the boot process but I don't ever see the login screen, it sits hung at a black screen and a mouse. Overall the boot process itself feels very sluggish. Please let me know if there's more information I can provide - thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lyndon 1871 F pulseaudio /dev/snd/controlC0: lyndon 1871 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 11:18:18 2020 InstallationDate: Installed on 2020-04-03 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5585 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.4 dmi.board.name: 0N999T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 2.4.4 dmi.modalias: dmi:bvnDellInc.:bvr2.4.4:bd11/12/2019:svnDellInc.:pnInspiron5585:pvr2.4.4:rvnDellInc.:rn0N999T:rvrA00:cvnDellInc.:ct10:cvr2.4.4: dmi.product.family: Inspiron dmi.product.name: Inspiron 5585 dmi.product.sku: 092B dmi.product.version: 2.4.4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872510/+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 1845178] Re: watchdog bug: soft lockup
** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1845178 Title: watchdog bug: soft lockup Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: Hello I have a Ubuntu Core 16 device (RPi CM3) which sometimes (at random) loses ethernet connection. Core snap is 16-2.40 Kernel snap is pi2-kernel 4.4.0-1120.129 Now I’ve managed to capture serial data from it and it seems it crashes completely, however it never restores (or full resets). [18037.433255] INFO: rcu_sched self-detected stall on CPU [18037.441257] INFO: rcu_sched detected stalls on CPUs/tasks: [18037.441264] e[12;17H1-...: (3708966 ticks this GP) idle=78d/141/0 softirq=7574/7589 fqs=1588 [18037.441270] e[13;17H(detected by 3, t=4495427 jiffies, g=2096, c=2095, q=35614) [18037.441272] Task dump for CPU 1: [18037.441278] manager-control R running 0 2310 2308 0x0082 [18037.441285] rcu_sched kthread starved for 4493705 jiffies! g2096 c2095 f0x2 s3 ->state=0x0 [18037.720278] e[17;17H1-...: (3708966 ticks this GP) idle=78d/141/0 softirq=7574/7589 fqs=1588 [18037.782050] e[18;17H (t=4495512 jiffies g=2096 c=2095 q=35615) [18037.813311] rcu_sched kthread starved for 4493798 jiffies! g2096 c2095 f0x2 s3 ->state=0x0 [18037.873341] Task dump for CPU 1: [18037.901730] manager-control R running 0 2310 2308 0x0082 [18037.933017] [<80112554>] (unwind_backtrace) from [<8010d7dc>] (show_stack+0x20/0x24) [18037.990378] [<8010d7dc>] (show_stack) from [<801571bc>] (sched_show_task+0xb8/0x110) [18038.048268] [<801571bc>] (sched_show_task) from [<80159a00>] (dump_cpu_task+0x48/0x4c) [18038.107812] [<80159a00>] (dump_cpu_task) from [<801919b8>] (rcu_dump_cpu_stacks+0x9c/0xd4) [18038.168554] [<801919b8>] (rcu_dump_cpu_stacks) from [<80195fec>] (rcu_check_callbacks+0x5c0/0x8bc) [18038.230663] [<80195fec>] (rcu_check_callbacks) from [<8019c3cc>] (update_process_times+0x4c/0x74) [18038.294469] [<8019c3cc>] (update_process_times) from [<801b04dc>] (tick_sched_handle+0x64/0x70) [18038.358337] [<801b04dc>] (tick_sched_handle) from [<801b0550>] (tick_sched_timer+0x68/0xbc) [18038.423493] [<801b0550>] (tick_sched_timer) from [<8019d1b0>] (__hrtimer_run_queues+0x188/0x364) [18038.490259] [<8019d1b0>] (__hrtimer_run_queues) from [<8019db4c>] (hrtimer_interrupt+0xd8/0x244) [18038.557715] [<8019db4c>] (hrtimer_interrupt) from [<80743e5c>] (arch_timer_handler_phys+0x40/0x48) [18038.626525] [<80743e5c>] (arch_timer_handler_phys) from [<8018bd2c>] (handle_percpu_devid_irq+0x80/0x194) [18038.696876] [<8018bd2c>] (handle_percpu_devid_irq) from [<80186f64>] (generic_handle_irq+0x34/0x44) [18038.768565] [<80186f64>] (generic_handle_irq) from [<80187270>] (__handle_domain_irq+0x6c/0xc4) [18038.840084] [<80187270>] (__handle_domain_irq) from [<801096f4>] (handle_IRQ+0x28/0x2c) [18038.910902] [<801096f4>] (handle_IRQ) from [<801015e4>] (bcm2836_arm_irqchip_handle_irq+0xb8/0xbc) [18038.982964] [<801015e4>] (bcm2836_arm_irqchip_handle_irq) from [<808a3678>] (__irq_svc+0x58/0x78) [18039.055005] Exception stack(0xaea2b9d0 to 0xaea2ba18) [18039.091313] b9c0: b9e3e01c 0025 0024 [18039.161335] b9e0: ae800040 aea2bae4 00011000 aea2bae4 80e0355c 000b aea2ba2c [18039.230628] ba00: aea2ba30 aea2ba20 8027a628 808a2c30 200f0013 [18039.267788] [<808a3678>] (__irq_svc) from [<808a2c30>] (_raw_spin_lock+0x40/0x54) [18039.335854] [<808a2c30>] (_raw_spin_lock) from [<8027a628>] (unmap_single_vma+0x1e8/0x64c) [18039.404789] [<8027a628>] (unmap_single_vma) from [<8027bab4>] (unmap_vmas+0x64/0x78) [18039.473309] [<8027bab4>] (unmap_vmas) from [<80282e38>] (exit_mmap+0x110/0x214) [18039.511274] [<80282e38>] (exit_mmap) from [<80122264>] (mmput+0x6c/0x138) [18039.548375] [<80122264>] (mmput) from [<80128a74>] (do_exit+0x32c/0xb38) [18039.585148] [<80128a74>] (do_exit) from [<8010db5c>] (die+0x37c/0x38c) [18039.621494] [<8010db5c>] (die) from [<8011bee0>] (__do_kernel_fault.part.0+0x74/0x1f4) [18039.688470] [<8011bee0>] (__do_kernel_fault.part.0) from [<808a40d8>] (do_page_fault+0x244/0x3c4) [18039.756059] [<808a40d8>] (do_page_fault) from [<80101284>] (do_DataAbort+0x58/0xe8) [18039.822179] [<80101284>] (do_DataAbort) from [<808a35e4>] (__dabt_svc+0x44/0x80) [18039.887651] Exception stack(0xaea2bd00 to 0xaea2bd48) [18039.921312] bd00: b9f55fc0 0037 0038 b9036000 ad5f32a0 b9f55fc0 00017000 [18039.987397] bd20: ae80005c b8af3eec 80e0354c aea2bd6c aea2bd70 aea2bd50 802855e8 802a4a5c
[Kernel-packages] [Bug 1899042] Re: System slow when using updated kernel
Good kernel: 5.4.0-45-generic pci=noaer fixes bug #1521173 I will try to update things from the bad kernel, it will take a full day to do it, but I will try It. Also, before knowing what was the problem, I tried to disable all updates from Software Updater. I will enable It and install all updates one of these days. -- 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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Incomplete Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 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 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1891454] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-20 08:52 EDT---
IBM Bugzilla status->closed, Fix Released with all requested distros
--
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/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf: changeDFLT_CCERROR counter
name
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Change the counter name DLFT_CCERROR to DLFT_CCFINISH on IBM z15 to
avoid confusion.
* This counter counts completed DEFLATE instructions with exit code 0,
1 or 2.
* And since exit code 0 means success and exit code 1 or 2 indicate
errors the name can be ambiguous.
[Fix]
* Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH.
* Backport Focal: https://launchpadlibrarian.net/493272507/0001-s390
-cpum_cf-perf-change-DFLT_CCERROR-counter-name.patch
* Backport Bionic:
https://launchpadlibrarian.net/493439681/u18-0001-s390-cpum_cf-Add-
new-extended-counters-for-IBM-z15.patch
[Test Case]
* Enable hardware counters in the activation profile of a z15 LPAR.
* Just check the countername in sysfs with: ls
/sys/devices/cpum_cf/events/{DFLT_CCERROR,DFLT_CCFINISH}
[Regression Potential]
* The regression potential can be considered as low, since:
* Counters like these are usually not activated by default and need to
be explicitly enabled.
* No code functionality is changed with that patch, only a renaming is
done at 3 places in one code file
arch/s390/kernel/perf_cpum_cf_events.c as well as in /tools/perf/pmu-
events/arch/s390/cf_z15/extended.json.
* The fix got already upstream accepted in 5.8-rc7, hence it got
upstream reviewed,
* and the modifications are limited to s390x, are only relevant for
the z15 / LinuxONE III hw generation that are relatively new.
* Issue with the renaming I can think of are that people don't know
about the new name and may look for the old one and don't find it
anymore,
* and with that also if the old counter name is used in scripts or
applications, these may fails due to an unknown counter name.
[Other Info]
* The backports are based on commit
3d3af181d370069861a3be94608464e2ff3682e2 ("s390/cpum_cf,perf: change
DFLT_CCERROR counter name") that is upstream accepted since v5.8-rc7.
* Hence this SRU is not requested for groovy, since it's already in groovys
kernel 5.8 in proposed, but only requested for focal and bionic.
__
Description: kernel: s390/cpum_cf,perf: change DFLT_CCERROR counter name
Symptom: Counter name CCERROR is misleading.
Problem: Change the counter name DLFT_CCERROR to DLFT_CCFINISH on
IBM z15. This counter counts completed DEFLATE instructions
with exit code 0, 1 or 2. Since exit code 0 means success
and exit code 1 or 2 indicate errors, change the counter
name to avoid confusion. This counter is incremented each
time the DEFLATE instruction completed regardless if an
error was detected or not.
Solution: Rename s390 z15 counter named DFLT_CCERROR to DFLT_CCFINISH
Reproduction: Command # ls /sys/devices/cpum_cf/events/DFLT_CCERROR
currently succeeds. After this patch has been applied the
command does not work anymore. The file does not exist
anymore. Use command
# ls /sys/devices/cpum_cf/events/DFLT_CCFINISH
instead.
Upstream-ID: 5ce1a24dd98c00a57a8fa13660648abf7e08e3ef
Component: kernel 5.8
Will be integrated into 20.10 by kernel 5.8 integration.
Backport available for 20.04.
To be checked for 18.04 and 16.04, update will be provided
Here is the backported patch.
The upstream commit id is 3d3af181d370069861a3be94608464e2ff3682e2
("s390/cpum_cf,perf: change DFLT_CCERROR counter name")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1891454/+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 1893778] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2020-10-20 08:40 EDT--- IBM Bugzilla status-> closed, Fix Released with all requested Distros -- 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/1893778 Title: [UBUNTU 20.04] zPCI device hot-plug during boot may result in unusable device Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: SRU Justification: == [Impact] * If a PCI device (incl. virtio-pci) is hot-plugged during boot-up on s390x, it can be detected as an entry in CLP List PCI functions and via the hot-plug event. * (This is basically equivalent to boot time probing on other architectures.) * In such a case the hot-plug event will be stale, but Linux still tries to add and enable the device which leads to: * a) a duplicate entry in zPCI internal device list * b) an attempt to enable the device with a stale function handle * In case b) the device will be placed in error state which makes it unusable. [Fix] * b76fee1bc56c31a9d2a49592810eba30cc06d61a b76fee1bc56c "s390/pci: ignore stale configuration request event" [Test Case] * Setup an Ubuntu Server 20.04 (focal) Linux operating system on an IBM Z or LinuxONE III LPAR. * It's now easiest to test on KVM using virtio-pci (on s390x). * Start a test virtual machine: sudo virsh start * Attach and hotplug a virtio-pci device: sudo virsh attach-device hotplug_pci_block.xml * Where hotplug_pci_block.xml looks like: [Regression Potential] * The regression risk is moderate, since the modification is very limited and therefore manageable (additional if statement - two lines of code) and easily testable on KVM using virtio-pci. * The changes are in the zPCI event code, so in worst-case it can happen that the event handling get harmed which may break zPCI entirely, affecting all PCI devices incl. virtio-pci (on s390x). * A bug in PCI 'availability' handling also just lead to wrong states of PCI devices which make them unavailable, hence unusable. * Notice that zPCI is the s390x-specific PCI implementation, modifications here do not affect any other architecture. * And zPCI devices are less wide-spread compared to ccw devices on s390x. * On top a test kernel was build and made available for further testing atesting can be easily done with virtio-pci on KVM. [Other] * The fix/patch got upstream accepted with kernel v5.9-rc2. * But it landed already in groovy's proposed kernel 5.8 (Ubuntu-5.8.0-18.19), due to 'Groovy update: v5.8.4 upstream stable release' that is handled in LP 1893048. * Hence this fix/patch need to be applied to focal only. __ When a PCI device (including virtio-pci for which this is easiest to test) is hot-plugged while Linux is still booting, it can be detected as an entry in CLP List PCI Functions (basically equivalent to boot time probing on other architectures) and with the hot-plug event. In this case the hot-plug event will be stale but Linux still tried to add and enable the device leading a) to a duplicate entry in zPCI internal device list b) an attempt to enable the device witha stale function handle Part b) would lead to the device being place in the error state and make it unusable. This can most easily be reproduced using KVM and doing # sudo virsh start myguest && sudo virsh attach-device myguest hotplug_pci_block.xml Where hotplug_pci_block.xml looks like the following: The problem is fixed with the 3-line upstream commit b76fee1bc56c31a9d2a49592810eba30cc06d61a s390/pci: ignore stale configuration request event I also confirmed that as of the focal tag Ubuntu-5.4.0-46.50 this cherry-picks cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1893778/+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 1900135] Re: Bluetooth headsets (mostly Sony) are not working HSP/HFP mode
Sony WH-1000XM2 Switch from HSP/HSF -> A2DP: Oct 20 12:25:08 gandalf-the-white gnome-shell[2705]: Window manager warning: WM_TRANSIENT_FOR window 0x3200199 for override-redirect window 0x3200db9 is an override-redirect window and this is not correct according to the standard, so we'll fallback to the root window. Oct 20 12:25:09 gandalf-the-white rtkit-daemon[2068]: Supervising 7 threads of 2 processes of 2 users. Oct 20 12:25:09 gandalf-the-white rtkit-daemon[2068]: Successfully made thread 129874 of process 2457 owned by '1000' RT at priority 5. Oct 20 12:25:09 gandalf-the-white rtkit-daemon[2068]: Supervising 8 threads of 2 processes of 2 users. Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_sink.70_26_05_29_7A_44.headset_head_unit" Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_sink.70_26_05_29_7A_44.headset_head_unit" Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_source.70_26_05_29_7A_44.headset_head_unit" Oct 20 12:25:09 gandalf-the-white gsd-media-keys[2843]: Unable to get default sink Oct 20 12:25:09 gandalf-the-white gsd-media-keys[2843]: Unable to get default source Oct 20 12:25:09 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_sink.70_26_05_29_7A_44.a2dp_sink" Switch from A2DP to HSP/HSF: Oct 20 12:25:50 gandalf-the-white gnome-shell[2705]: Window manager warning: WM_TRANSIENT_FOR window 0x3200199 for override-redirect window 0x32010c6 is an override-redirect window and this is not correct according to the standard, so we'll fallback to the root window. Oct 20 12:25:52 gandalf-the-white rtkit-daemon[2068]: Supervising 7 threads of 2 processes of 2 users. Oct 20 12:25:52 gandalf-the-white rtkit-daemon[2068]: Successfully made thread 129888 of process 2457 owned by '1000' RT at priority 5. Oct 20 12:25:52 gandalf-the-white rtkit-daemon[2068]: Supervising 8 threads of 2 processes of 2 users. Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_sink.70_26_05_29_7A_44.a2dp_sink" Oct 20 12:25:52 gandalf-the-white gsd-media-keys[2843]: Unable to get default sink Oct 20 12:25:52 gandalf-the-white gsd-media-keys[2843]: Unable to get default source Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_sink.70_26_05_29_7A_44.headset_head_unit" Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_source.70_26_05_29_7A_44.headset_head_unit" Oct 20 12:25:52 gandalf-the-white org.kde.kdeconnect.daemon.desktop[3009]: org.kde.pulseaudio: No object for name "bluez_source.70_26_05_29_7A_44.headset_head_unit" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1900135 Title: Bluetooth headsets (mostly Sony) are not working HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sony WH-1000XM2 and Taotronics SoundLiberty 53 are both not working in headset mode, but do in A2DP mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marc 2635 F pulseaudio /dev/snd/controlC0: marc 2635 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 13:06:42 2020 InstallationDate: Installed on 2020-06-13 (124 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/usr/bin/zsh SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.07.23 dmi.board.asset.tag: Tag 12345 dmi.board.name: P7xxTM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.07.23:bd04/09/2019:svnNotebook:pnP7xxTM1:pvrNotApplicable:rvnNotebook:rnP7xxTM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P7xxTM1 dmi.product.sku: Not Applicable dmi.product.version: Not
[Kernel-packages] [Bug 1896091] Re: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915]
Oh, drmtip exists too, I thought you said drmnext which was stuck on 09-18 (and I tested 09-15 which was more stable but not perfect). I'm currently just running the 5.9.1 mainline kernel for testing purposes, which so far (2 days in seems stable), but might just break later today, who knows. -- 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/1896091 Title: [i915] graphic corruption following orkqueue: PF_MEMALLOC task 131(kswapd0) is flushing !WQ_MEM_RECLAIM events_unbound:active_work [i915] Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Incomplete Bug description: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1899042] Re: System slow when using updated kernel
** 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/1899042 Title: System slow when using updated kernel Status in linux package in Ubuntu: Incomplete Bug description: System is slow when using kernel version 5.8.0-20-generic. (Low fps in desktop, boot takes more time, opening any application takes seconds) A temporal fix is use old kernel. Since Apport did not have a system related category, I have to report it here. I dont know how to gather more information about my system. //Output of 'lsb_release -rd' Description: Ubuntu Groovy Gorilla (development branch) Release: 20.10 //Output of 'lshw' Processor: Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz Also, resources are not at 100%, I have a SSD, 8GB RAM, is overkill for just using the system. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eladmin F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-16 (52 days ago) InstallationMedia: Ubuntu 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 1bcf:2c9b Sunplus Innovation Technology Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs0xx Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-20-generic root=UUID=7bc88721-682a-4c22-9e16-72a40d554f8b ro quiet splash pci=noaer vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 RelatedPackageVersions: linux-restricted-modules-5.8.0-20-generic N/A linux-backports-modules-5.8.0-20-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-20-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-09-30 (8 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2017 dmi.bios.release: 15.2 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8328 dmi.board.vendor: HP dmi.board.version: 23.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 23.21 dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/07/2017:br15.2:efr23.21:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8328:rvr23.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.sku: 1VH28EA#ABE dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899042/+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 1900683] [NEW] Installing wireguard-tools pulls in the generic kernel
Public bug reported: Installing wireguard-tools on Groovy raspi pulls in the generic kernel: ubuntu@rpi-4b-rev1d2-2c1a:~$ uname -a Linux rpi-4b-rev1d2-2c1a 5.8.0-1004-raspi #7-Ubuntu SMP PREEMPT Fri Oct 9 14:52:59 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@rpi-4b-rev1d2-2c1a:~$ sudo apt install wireguard-tools Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-image-5.7.0-15-generic linux-image-virtual-wip linux-modules-5.7.0-15-generic Suggested packages: fdutils linux-doc | linux-5.7-source-5.7.0 linux-5.7-tools linux-headers-5.7.0-15-generic openresolv | resolvconf The following NEW packages will be installed: linux-image-5.7.0-15-generic linux-image-virtual-wip linux-modules-5.7.0-15-generic wireguard-tools 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 27.9 MB of archives. After this operation, 105 MB of additional disk space will be used. Do you want to continue? [Y/n] ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu) ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Summary changed: - Missing wireguard provides + Installing wireguard-tools pulls in the generic kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1900683 Title: Installing wireguard-tools pulls in the generic kernel Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Groovy: New Bug description: Installing wireguard-tools on Groovy raspi pulls in the generic kernel: ubuntu@rpi-4b-rev1d2-2c1a:~$ uname -a Linux rpi-4b-rev1d2-2c1a 5.8.0-1004-raspi #7-Ubuntu SMP PREEMPT Fri Oct 9 14:52:59 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@rpi-4b-rev1d2-2c1a:~$ sudo apt install wireguard-tools Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-image-5.7.0-15-generic linux-image-virtual-wip linux-modules-5.7.0-15-generic Suggested packages: fdutils linux-doc | linux-5.7-source-5.7.0 linux-5.7-tools linux-headers-5.7.0-15-generic openresolv | resolvconf The following NEW packages will be installed: linux-image-5.7.0-15-generic linux-image-virtual-wip linux-modules-5.7.0-15-generic wireguard-tools 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 27.9 MB of archives. After this operation, 105 MB of additional disk space will be used. Do you want to continue? [Y/n] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900683/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hey there guy, can anyone tell me what im doing wrong with the patch
provided in #217. The tutorial in #211 doesnt work for me.
p_$$/tmp.o; mkdir -p
/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone/.tmp_$$; trap
"rm -rf
/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone/.tmp_$$"
EXIT; if ( echo "int main() {}" | gcc -xc -o /dev/null -lelf -) >/dev/null
2>&1; then echo "1"; else echo "0"; fi'
/bin/sh: -c: line 0: syntax error near unexpected token `('
/bin/sh: -c: line 0: `make -f ./scripts/Makefile.build
obj=/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone \'
make: *** [Makefile:1752:
/home/benjamin/Downloads/i2c-hid_standalone(1)/i2c-hid_standalone] Error 1
make: Leaving directory '/usr/lib/modules/5.8.16-2-MANJARO/build'
help much appreciated
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-40-generic N/A
linux-backports-modules-5.4.0-40-generic N/A
linux-firmware1.187.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
Confirmed to be fixed on 20.04 ubuntu - awesome - thank you very much everyone involved! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1882669] Re: Focal Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test
Found on G-5.8 Azure ** Summary changed: - Focal Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test + Focal / Groovy Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test ** Tags added: 5.8 groovy ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-azure-5.4 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-azure-5.4 (Ubuntu Focal) Importance: Undecided Status: New -- 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/1882669 Title: Focal / Groovy Azure instances crash with ftracetest in ubuntu_kernel_selftests and ubuntu_ftrace_smoke_test Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: New Status in linux-azure source package in Focal: New Status in linux-azure-5.4 source package in Focal: New Status in linux-azure source package in Groovy: New Status in linux-azure-5.4 source package in Groovy: New Bug description: Issue found on 5.4.0-1013.13 The ftrace in ubuntu_kernel_selftests failed on the second test: # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers (System hang here) Syslog: kernel: [ 2234.408225] in mmio_trace_init kernel: [ 2234.988256] mmiotrace: Disabling non-boot CPUs... kernel: [ 2235.028451] mmiotrace: Error taking CPU1 down: -16 kernel: [ 2235.052564] mmiotrace: Error taking CPU2 down: -16 kernel: [ 2235.076593] mmiotrace: Error taking CPU3 down: -16 kernel: [ 2235.096576] mmiotrace: Error taking CPU4 down: -16 kernel: [ 2235.116487] mmiotrace: Error taking CPU5 down: -16 kernel: [ 2235.132446] mmiotrace: Error taking CPU6 down: -16 kernel: [ 2235.152488] mmiotrace: Error taking CPU7 down: -16 kernel: [ 2235.172526] mmiotrace: Error taking CPU8 down: -16 kernel: [ 2235.192486] mmiotrace: Error taking CPU9 down: -16 kernel: [ 2235.212455] mmiotrace: Error taking CPU10 down: -16 kernel: [ 2235.233020] mmiotrace: Error taking CPU11 down: -16 kernel: [ 2235.256355] mmiotrace: Error taking CPU12 down: -16 kernel: [ 2235.272473] mmiotrace: Error taking CPU13 down: -16 kernel: [ 2235.292393] mmiotrace: Error taking CPU14 down: -16 kernel: [ 2235.312426] mmiotrace: Error taking CPU15 down: -16 kernel: [ 2235.344407] mmiotrace: Error taking CPU16 down: -16 kernel: [ 2235.380494] mmiotrace: Error taking CPU17 down: -16 kernel: [ 2235.400319] mmiotrace: Error taking CPU18 down: -16 kernel: [ 2235.432631] mmiotrace: Error taking CPU19 down: -16 kernel: [ 2235.456453] mmiotrace: Error taking CPU20 down: -16 kernel: [ 2235.480432] mmiotrace: Error taking CPU21 down: -16 kernel: [ 2235.496501] mmiotrace: Error taking CPU22 down: -16 kernel: [ 2235.516442] mmiotrace: Error taking CPU23 down: -16 kernel: [ 2235.536394] mmiotrace: Error taking CPU24 down: -16 kernel: [ 2235.556489] mmiotrace: Error taking CPU25 down: -16 kernel: [ 2235.573759] smpboot: CPU 26 is now offline kernel: [ 2235.575071] mmiotrace: CPU26 is down. kernel: [ 2235.585643] smpboot: CPU 27 is now offline kernel: [ 2235.586699] mmiotrace: CPU27 is down. kernel: [ 2235.609679] smpboot: CPU 28 is now offline kernel: [ 2235.610788] mmiotrace: CPU28 is down. kernel: [ 2235.633530] smpboot: CPU 29 is now offline kernel: [ 2235.634511] mmiotrace: CPU29 is down. kernel: [ 2235.653652] smpboot: CPU 30 is now offline kernel: [ 2235.655415] mmiotrace: CPU30 is down. kernel: [ 2235.678126] smpboot: CPU 31 is now offline kernel: [ 2235.679061] mmiotrace: CPU31 is down. kernel: [ 2235.679062] mmiotrace: multiple CPUs still online, may miss events. kernel: [ 2235.679063] mmiotrace: enabled. kernel: [ 2235.679128] in mmio_trace_reset kernel: [ 2235.696163] mmiotrace: Re-enabling CPUs... kernel: [ 2235.732157] mmiotrace: enabled CPU1. kernel: [ 2235.772207] mmiotrace: enabled CPU2. kernel: [ 2235.812216] mmiotrace: enabled CPU3. kernel: [ 2235.844220] mmiotrace: enabled CPU4. kernel: [ 2235.876211] mmiotrace: enabled CPU5. kernel: [ 2235.916159] mmiotrace: enabled CPU6. kernel: [ 2235.956214] mmiotrace: enabled CPU7. kernel: [ 2235.988145] mmiotrace: enabled CPU8. kernel: [ 2236.020214] mmiotrace: enabled CPU9. kernel: [ 2236.060207] mmiotrace: enabled CPU10. kernel: [ 2236.096208] mmiotrace: enabled CPU11. kernel: [ 2236.128205] mmiotrace: enabled CPU12. /usr/sbin/irqbalance: WARNING, didn't collect load info for all cpus, balancing is broken kernel: [ 2236.168204] mmiotrace: enabled CPU13. kernel: [ 2236.200206]
[Kernel-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset
THose having the issue still, it would be better to report directly
upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues since
Ubuntu doesn't currently have a dedicated pulseaudio maintainer
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
Status in alsa-lib package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via
pavucontrol.
When hot-plugging the USB headset, either the speaker is recognized,
or the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker
and the "multichannel" microphone are recognized, only one can be used
- either speaker or microphone. When selecting the speaker, the
microphone is switched back to any other device available, them same
goes for the microphone and the speaker - any other speaker is
selected.
A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a
second headset).
Running "lsb_release -a" gives
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic
Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).
I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
and it sounds somewhat very familiar, but instead of "env={}" in
/usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
Removing "env=env" doesn't resolve the problem.
Do you require additional information?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1865499/+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 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
** Changed in: maas-images Assignee: (unassigned) => Lee Trager (ltrager) ** Changed in: maas-images Importance: Undecided => Critical -- 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/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: New Status in maas-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789
[Kernel-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I'm on 20.10 Groovy Beta and, after today's kernel + linux-firmware update, HFP/HSP is working on my dell xps 13 9380. It stopped working since 20.04, it wasn't working with all previous kernel/linux-firmware versions in 20.10. Today it's finally back. $ uname -a Linux mydellxps 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ apt-cache policy linux-firmware linux-firmware: Installed: 1.190 Candidate: 1.190 Version table: *** 1.190 500 500 http://it.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1900438] Re: Bcache bypasse writeback on caching device with fragmentation
I tried to run the apport-collect on one of the server we can see the
issue on :
Waiting to hear from Launchpad about your decision...
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
..dpkg-query: no packages found matching linux
..
Traceback (most recent call last):
File "/usr/bin/apport-cli", line 370, in
if not app.run_argv():
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 666, in run_argv
return self.run_update_report()
File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 564, in
run_update_report
self.report.add_proc_environ()
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 577, in
add_proc_environ
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
AttributeError: 'module' object has no attribute 'O_PATH'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 507, in
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
AttributeError: 'module' object has no attribute 'O_PATH'
But since the bug has already been marked as "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/1900438
Title:
Bcache bypasse writeback on caching device with fragmentation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello,
An upstream bug has been opened on the matter for quite some time now [0].
I can reproduce easily on our production compute node instance, which are
trusty host with xenial hwe kernels (4.15.0-101-generic).
However due to heavy backport and such, doing real tracing is a bit hard
there.
I was able to reproduce the behavior on a hwe-bionic kernel as well.
Since most of our critical deployments use bcache, I think this is a kinda
nasty bug to have.
Reproducing the issue is relatively easy with the script provided in the bug
[1].
The script used to capture the stats is this one [2].
[0]: https://bugzilla.kernel.org/show_bug.cgi?id=206767
[1]: https://pastebin.ubuntu.com/p/YnnvvSRhXK/
[2]: https://pastebin.ubuntu.com/p/XfVpzg32sN/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900438/+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 1900665] [NEW] Switch to the upstream dwc driver on arm64
Public bug reported: We currently use the dwc_otg driver from raspberrypi on 5.4 and 5.8 armhf and arm64 kernels. That driver supports FIQ interrupt handling (presumable for better performance) but lacks the maintenance and bug fixing of the vanilla upstream dwc driver. Turns out that FIQ handling is disabled in the dwc_otg driver on arm64 so it makes little sense to use that driver on arm64. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- 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/1900665 Title: Switch to the upstream dwc driver on arm64 Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Groovy: New Bug description: We currently use the dwc_otg driver from raspberrypi on 5.4 and 5.8 armhf and arm64 kernels. That driver supports FIQ interrupt handling (presumable for better performance) but lacks the maintenance and bug fixing of the vanilla upstream dwc driver. Turns out that FIQ handling is disabled in the dwc_otg driver on arm64 so it makes little sense to use that driver on arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900665/+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 1900663] [NEW] Re-enable memory cgroups
Public bug reported: Currently, the 5.4 and 5.8 raspi kernels disable the memory cgroup by default to conserve memory [1]. This is a legacy custom modification, that is no longer needed, since the memory cgroup code has been rewritten to no longer requires large amounts of memory [2]. So the custom patch can be dropped. The patch is also the reason why the LXC ADT test fails. [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/focal/commit/?id=64e543b88ea2a013e1d8e014e7c92c53df1322ed [2] https://github.com/torvalds/linux/commit/1306a85aed3ec3db98945aafb7dfbe5648a1203c ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Package changed: livecd-rootfs (Ubuntu) => linux-raspi (Ubuntu) ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- 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/1900663 Title: Re-enable memory cgroups Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Groovy: New Bug description: Currently, the 5.4 and 5.8 raspi kernels disable the memory cgroup by default to conserve memory [1]. This is a legacy custom modification, that is no longer needed, since the memory cgroup code has been rewritten to no longer requires large amounts of memory [2]. So the custom patch can be dropped. The patch is also the reason why the LXC ADT test fails. [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/focal/commit/?id=64e543b88ea2a013e1d8e014e7c92c53df1322ed [2] https://github.com/torvalds/linux/commit/1306a85aed3ec3db98945aafb7dfbe5648a1203c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900663/+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 1900663] [NEW] Re-enable memory cgroups
You have been subscribed to a public bug: Currently, the 5.4 and 5.8 raspi kernels disable the memory cgroup by default to conserve memory [1]. This is a legacy custom modification, that is no longer needed, since the memory cgroup code has been rewritten to no longer requires large amounts of memory [2]. So the custom patch can be dropped. The patch is also the reason why the LXC ADT test fails. [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/focal/commit/?id=64e543b88ea2a013e1d8e014e7c92c53df1322ed [2] https://github.com/torvalds/linux/commit/1306a85aed3ec3db98945aafb7dfbe5648a1203c ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- Re-enable memory cgroups https://bugs.launchpad.net/bugs/1900663 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1876992] Re: X11 session crash on using Gimp or LibreOffice
This bug is closed. Please open new bugs for all new issues. -- 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/1876992 Title: X11 session crash on using Gimp or LibreOffice Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Several applications are crashing X11. Gimp after creating a new image Gimp after opening an image Libre office writer on attempting to crop and image All the currently running applications then log the following into syslog May 5 21:25:22 david-XPS-15-7590 org.freedesktop.FileManager1[8960]: gimp-2.10: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gjs[7382]: GSConnect: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 pulseaudio[7047]: X connection to :1 broken (explicit kill or server shutdown). May 5 21:25:22 david-XPS-15-7590 FirefoxDeveloperEdition.desktop[8766]: Gdk-Message: 21:25:22.150: /home/david/bin/firefox-dev.d/firefox-bin: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 evolution-alarm[7340]: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 at-spi-bus-launcher[7133]: X connection to :1 broken (explicit kill or server shutdown). May 5 21:25:22 david-XPS-15-7590 guake[7359]: guake: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 firefox-bin[8656]: firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 update-notifier[8422]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-power[7296]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-wacom[7323]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-xsettings[7328]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-keyboard[7294]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 nautilus[7262]: org.gnome.Nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-media-keys[7295]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 nextcloud[7375]: nextcloud: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-color[7289]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. On a Ubuntu session this then ends the session and it drops back to the login screen. I tried on a classic Gnome desktop and it froze the desktop resulting in requiring a forced reboot using the power key. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-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: ubuntu:GNOME Date: Tue May 5 22:04:32 2020 DistUpgraded: 2020-04-24 15:49:16,469 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905] InstallationDate: Installed on 2019-12-05 (152 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc.
[Kernel-packages] [Bug 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
Hi Jeff, I don't have daily but only stable however the checksum seems to match with Billy's: ~$ ls -l /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/stable/ total 460484 -rw-r--r-- 3 maas maas 86260608 Oct 15 19:58 boot-initrd -rw-r--r-- 3 maas maas 11678464 Oct 15 19:58 boot-kernel -rw-r--r-- 4 maas maas 373587968 Oct 15 19:58 squashfs ~$ sha256sum /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/stable/* 273212b1858bc4441b392900123f1433733023986d542e8d2caf458fbb48edb2 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/stable/boot-initrd 1a8aec22331f411cdbc61c367b7397cf0d6cda7a85afc94c7ebb64ec478c32b8 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/stable/boot-kernel 0caa3059361ab22a75f9797834ff7bcce372621919122a7d8289b66a1a9c8084 /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/stable/squashfs -- 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/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: New Status in maas-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as
[Kernel-packages] [Bug 1855815] Re: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP
Note that this has passed with G-5.8-GCP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855815 Title: flag from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestConstantMaps (0.07s) ciphersuites_flag_test.go:106: discovered version tls.VersionTLS13 not in version map FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apiserver/pkg/util/flag 0.072s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855815/+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 1855816] Re: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP
Note that this has passed with G-5.8-GCP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855816 Title: naming from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP --- FAIL: TestGetNameFromCallsite (0.00s) --- FAIL: TestGetNameFromCallsite/ignore-package (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" --- FAIL: TestGetNameFromCallsite/ignore-file (0.00s) from_stack_test.go:52: expected "testing/testing.go:777", got "testing/testing.go:865" FAIL FAIL k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/naming0.002s This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855816/+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 1876992] Re: X11 session crash on using Gimp or LibreOffice
Ubuntu 20.04 - Applications Scite, VLC, .. with fatal errors Oct 19 21:50:56 djien--SR5622NL vlc[3612]: vlc: Fatal IO error 17 (File exists) on X server :1. Oct 19 21:50:56 djien--SR5622NL vlc[3612]: vlc: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL SciTE[3503]: SciTE: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL update-notifier[3243]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL kdeconnectd[2869]: kdeconnectd: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL gsd-xsettings[2873]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL gnome-terminal-[3145]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL gsd-media-keys[2824]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL gsd-wacom[2864]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL gsd-power[2828]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 21:50:56 djien--SR5622NL [2926]: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. ct 19 21:50:56 djien--SR5622NL org.gnome.Nautilus[3301]: [3301:3301:1019/215056.368733:ERROR:x11_error_handler.cc(63)] X IO error received (X server probably went away) Oct 19 21:50:56 djien--SR5622NL at-spi-bus-launcher[2730]: X connection to :1 broken (explicit kill or server shutdown). Oct 19 21:50:56 djien--SR5622NL gsd-color[2812]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. -- 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/1876992 Title: X11 session crash on using Gimp or LibreOffice Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Several applications are crashing X11. Gimp after creating a new image Gimp after opening an image Libre office writer on attempting to crop and image All the currently running applications then log the following into syslog May 5 21:25:22 david-XPS-15-7590 org.freedesktop.FileManager1[8960]: gimp-2.10: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gjs[7382]: GSConnect: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 pulseaudio[7047]: X connection to :1 broken (explicit kill or server shutdown). May 5 21:25:22 david-XPS-15-7590 FirefoxDeveloperEdition.desktop[8766]: Gdk-Message: 21:25:22.150: /home/david/bin/firefox-dev.d/firefox-bin: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 evolution-alarm[7340]: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 at-spi-bus-launcher[7133]: X connection to :1 broken (explicit kill or server shutdown). May 5 21:25:22 david-XPS-15-7590 guake[7359]: guake: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 firefox-bin[8656]: firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 update-notifier[8422]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-power[7296]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-wacom[7323]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-xsettings[7328]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-keyboard[7294]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 nautilus[7262]: org.gnome.Nautilus: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-media-keys[7295]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 nextcloud[7375]: nextcloud: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. May 5 21:25:22 david-XPS-15-7590 gsd-color[7289]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. On a Ubuntu session this then ends the session and
[Kernel-packages] [Bug 1855809] Re: vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP / F-5.4-GCP
Note that this has passed with G-5.8-GCP
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1855809
Title:
vclib from ubuntu_k8s_unit_tests fail on Eoan 5.3 GCP / F-5.4-GCP
Status in ubuntu-kernel-tests:
New
Status in linux-gcp package in Ubuntu:
New
Bug description:
Issue found on 5.3.0-1010 Eoan GCP
E1207 09:14:34.779687 29118 datacenter.go:45] Failed to find the datacenter:
enoent. err: datacenter 'enoent' not found
E1207 09:14:34.783331 29118 datacenter.go:78] Unable to find VM by UUID. VM
UUID: enoent
E1207 09:14:34.785587 29118 datacenter.go:106] Failed to find VM by Path. VM
Path: enoent, err: vm 'enoent' not found
E1207 09:14:34.787217 29118 datacenter.go:153] Failed to parse vmDiskPath:
enoent
E1207 09:14:34.788754 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.792557 29118 datacenter.go:165] Failed while searching for
datastore: enoent. err: datastore 'enoent' not found
E1207 09:14:34.801865 29118 datacenter.go:191] Failed to get the folder
reference for enoent. err: folder 'enoent' not found
E1207 09:14:34.804569 29118 datacenter.go:203] VirtualMachine Object list is
empty
E1207 09:14:34.805548 29118 datacenter.go:213] Failed to get VM managed
objects from VM objects. vmObjList: [VirtualMachine:vm-54 @
/DC0/vm/DC0_H0_VM1], properties: [enoent], err: InvalidProperty
E1207 09:14:34.806781 29118 datacenter.go:241] Datastore Object list is empty
E1207 09:14:34.807159 29118 datacenter.go:251] Failed to get Datastore
managed objects from datastore objects. dsObjList:
[Datastore:/tmp/govcsim-DC0-LocalDS_0-314024335@folder-5 @
/DC0/datastore/LocalDS_0], properties: [enoent], err: InvalidProperty
E1207 09:14:34.968117 29118 connection.go:180] Failed to create new client.
err: EOF
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:58028: remote
error: tls: bad certificate
E1207 09:14:35.039988 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:35147/sdk: Host "127.0.0.1:35147" thumbprint does
not match "obviously wrong"
E1207 09:14:35.052610 29118 connection.go:180] Failed to create new client.
err: Post https://127.0.0.1:40591/sdk: x509: certificate signed by unknown
authority
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:37506: remote
error: tls: bad certificate
2019/12/07 09:14:35 http: TLS handshake error from 127.0.0.1:33050: remote
error: tls: bad certificate
E1207 09:14:35.081393 29118 connection.go:180] Failed to create new client.
err: EOF
E1207 09:14:35.081489 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestWithInvalidCaCertPath (0.00s)
connection_test.go:168: Expected an os.PathError, got: 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host' ({Op:"parse",
URL:"https://should-not-matter:should-not-matter;,
Err:(*errors.errorString)(0xc0004fcd70)})
E1207 09:14:35.081626 29118 connection.go:163] Failed to parse URL: . err:
parse https://should-not-matter:should-not-matter: invalid port
":should-not-matter" after host
--- FAIL: TestInvalidCaCert (0.00s)
connection_test.go:182: Expected invalid certificate error, got 'parse
https://should-not-matter:should-not-matter: invalid port ":should-not-matter"
after host'
FAIL
FAIL k8s.io/kubernetes/pkg/cloudprovider/providers/vsphere/vclib 0.319s
This is not a regression as this failure can be found in
5.3.0-1009.10-gcp as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855809/+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 1855811] Re: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP
Note that this has passed with G-5.8-GCP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855811 Title: container from ubuntu_k8s_unit_tests failed with Eoan-5.3 GCP / F-5.4-GCP Status in ubuntu-kernel-tests: New Status in linux-gcp package in Ubuntu: New Bug description: Issue found on 5.3.0-1010 Eoan GCP # k8s.io/kubernetes/pkg/kubelet/container pkg/kubelet/container/sync_result_test.go:48:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:56:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult pkg/kubelet/container/sync_result_test.go:66:3: Errorf format %q has arg result of wrong type k8s.io/kubernetes/pkg/kubelet/container.PodSyncResult []*k8s.io/kubernetes/pkg/kubelet/container.Pod FAIL k8s.io/kubernetes/pkg/kubelet/container [build failed] This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855811/+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 1867118] Re: dasd_fba io error and kernel panic
The focal part of this ticket is addressed by:
"Focal update: v5.4.69 upstream stable release"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900624
And LP 1900624 is Fix Committed and the patches are already applied to focal
master-next.
Hence aligning the status of this ticket to LP 1900624 and updating it to Fix
Committed.
** Changed in: linux (Ubuntu Focal)
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/1867118
Title:
dasd_fba io error and kernel panic
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Bug description:
Generated I/O errors every hour in syslog and caused kernel panic with
workloads running
---uname output---
Linux ubuntutest01 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:02 UTC
2020 s390x s390x s390x GNU/Linux
---Patches Installed---
distro provided. up-to-date from Ubuntu18.04.
Machine Type = z15
---System Hang---
The hourly generated I/O errors didn't impact the system up and running.
When there are workloads on it, it will cause kernel panic and rebooted the
server.
---Debugger---
A debugger is not configured
---Steps to Reproduce---
After migrated from 16.04 to 18.04, will see the i/o errors.
Stack trace output:
no
Oops output:
no
System Dump Info:
The system is not configured to capture a system dump.
Device driver error code:
[52297.898232] dasd.5c0c98: 0.0.0100: default ERP has run out of retries and
failed
[52297.898244] dasd(fba): I/O status report for device 0.0.0100:
dasd(fba): in req: 2e142bcd CS: 0x20 DS: 0x0C
dasd(fba): device 0.0.0100: Failing CCW: a84f6c9f
dasd(fba): SORRY - NO VALID SENSE AVAILABLE
[52297.898255] dasd(fba): Related CP in req: 2e142bcd
dasd(fba): CCW d15f44d3: 63400010 7FE2BBA0 DAT:
0200 008150F2 0017
dasd(fba): CCW b09ad76e: 4348 7FE2BBB0 DAT:
0506
dasd(fba): CCW c44dfb20: 41600C00 F360 DAT:
dasd(fba): CCW a84f6c9f: 4348 7FE2BBB8 DAT:
0510 0006
dasd(fba): CCW 22dac88c: 4160 DAT:
dasd(fba): CCW 69686544: 4348 7FE2BBC0 DAT:
0502 0016
dasd(fba): CCW 7bb6a17c: 41200400 F360 DAT:
[52297.898278] print_req_error: I/O error, dev dasda, sector 8474866
*Additional Instructions for y...@cn.ibm.com:
-Attach sysctl -a output output to the bug.
[reply] [?]
Internal Only
Comment 1 QI YE 2020-03-12 02:29:20 CDT
The z/VM version 6.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867118/+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 1850439] Re: No sound on ASUS UX534FT
** 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/1850439 Title: No sound on ASUS UX534FT Status in linux package in Ubuntu: Fix Released Bug description: Hi, after instal Ubuntu in dual boot alongside Windows 10, I've realised there is no sound coming out of mine new ASUS Zenbook 15 UX534FT- AA024R in Ubuntu. In Windows there is no problem. Found this topic https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810214 which had the same problem with driver for Realtek ALC294 which is also mine sound card. But even with this fix it is not working on UX534FT. Can you please add fix also for this newer model? Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-32-generic 5.0.0-32.34~18.04.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 29 15:11:25 2019 InstallationDate: Installed on 2019-10-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+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 1896726] Re: [UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic page table folding issue
The focal part of this ticket is addressed by:
"Focal update: v5.4.69 upstream stable release"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900624
And LP 1900624 is Fix Committed and the patches are already applied to focal
master-next.
Hence aligning the status of this ticket to LP 1900624 and updating it to Fix
Committed.
** Changed in: linux (Ubuntu Focal)
Status: Triaged => 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/1896726
Title:
[UBUNTU 20.04.1] qemu (secure guest) crash due to gup_fast / dynamic
page table folding issue
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
Fix Released
Bug description:
Justification:
==
Secure KVM guest (using secure execution on Ubuntu Server 20.04 for s390x)
crashes happen from time to time during boot.
Such crashed guests ("reason=crashed" in the libvirt log) end up in hutoff
state instead of crashed state ( preserve is set).
The crash points to a kernel memory management problem, addressed by the
following patch/fix.
The modifications touch common memory management code,
but it will have no effect to architectures other than s390x.
This is ensured by the fact that only s390 provides / implements the new
helper functions.
And for s390x, this is actually a critical (and carefully tested) fix for a
(previous) regression, so it can hardly get any more regressive.
The patch landed upstream in linux-next, is in depth discussed
at LKML https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
and here
https://lore.kernel.org/linux-arch/patch.git-943f1e5dcff2.your-ad-here.call-01599856292-ext-8676@work.hours/
and will soon land via the regular upstream stable release update for kernel
5.4 in focal, too.
The process already started:
https://lore.kernel.org/stable/patch-1.thread-41918b.git-41918be365c0.your-ad-here.call-01600439945-ext-8991@work.hours/
Hence this cherry-pick from the upstream patch should be added to groovy
to avoid any potential regression in case the patch landed in focal via the
upstream release update process,
but is not in groovy and someones upgrades from focal to groovy.
__
Secure Execution with Ubuntu 20.04, secure guest crash during boot
from time to time, crashed guest went into Shufoff state instead of
Crashed state (preserve is set), so I can't get a dump.
libvirt log file:
2020-04-21T16:35:39.382999Z qemu-system-s390x: Guest says index 19608 is
available
2020-04-21 16:35:44.831+: shutting down, reason=crashed
---uname output---
Linux ubu204uclg1002 5.4.0-25-generic #29-Ubuntu SMP Fri Apr 17 15:05:32 UTC
2020 s390x s390x s390x GNU/Linux
Machine Type = z15 8561
---Debugger---
A debugger is not configured
---Steps to Reproduce---
I have a setup with 72 KVM guests which I can start in secure or non-secure
mode. Starting all of them in secure mode back to back results in a number of
guests (4..8) in Shutoff state and reason=crashed in the libvirt log. I can
manually start the guest again no problem. Different guests are failing.
Host and guests are on latest Ubuntu 20.04.
The supposed fix (kernel memory management) has landed in Andrew Mortons mm
tree
https://lore.kernel.org/mm-commits/20200916003608.ib4ln%25a...@linux-foundation.org/T/#u
Please note: while this was found with secure execution, the bug is
actually present for non-KVM workloads as well.
The complete patch is this:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=a338e69ba37286c0fc300ab7e6fa0227e6ca68b1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1896726/+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
