[Kernel-packages] [Bug 1860416] Re: Mint 5.3.0-26 does not boot
[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/1860416 Title: Mint 5.3.0-26 does not boot Status in linux package in Ubuntu: Expired Bug description: Hello, I updated the kernel from 5.0 to 5.3 and I cannot boot anymore. Booting with 5.0 works perfectly Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860416/+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 1861237] Re: Audio not detected on X1 Yoga 4th
It's now fixed in Focal :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1861237 Title: Audio not detected on X1 Yoga 4th Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's not detecting audio from it at all. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (9 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120) Package: pulseaudio 1:13.0-3ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (9 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120) Package: pulseaudio 1:13.0-3ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861237/+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 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04
Yes, I can also confirm it's working on latest daily build of focal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1860697 Title: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Bug description: I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both output and input, does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 12:00:01 2020 InstallationDate: Installed on 2019-09-06 (139 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20QDCTO1WW ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago) dmi.bios.date: 12/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
"I was unable to use the "test" feature of gnome settings : I can open the window, but neither the front right nor front left buttons in the test play any sound" That is sth I never met before, please check if speaker-sof-skl_hda_card is selected and if profile is play HiFi Music. -- 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/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855608] Re: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake
Sorry, @tjaalton, took a while (needed to install Ubuntu again). I was able to test your custom kernel on a freshly installed Ubuntu 19.10. Results with custom kernel from https://aaltoset.kapsi.fi/lp1826125: - Screen corruption was gone - Suspend/resume worked and graphics output was usable after resume - Did not test hibernate/resume This kernel image solved the reported issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855608 Title: Dell XPS 13 7390 screen corruption in 18.04 LTS, 19.04 and 19.10 on Intel Comet Lake Status in linux package in Ubuntu: Confirmed Bug description: I just received a new Dell XPS 13 7390 laptop. With factory preinstalled Ubuntu Linux 18.04 LTS and the Dell OEM kernel, graphics was severely distorted. The display would constantly flicker with areas of the display staying black or showing patterns of square color blocks. Booting in recovery mode worked, though and I was able to install all updates for preinstalled 18.04 LTS with the OEM kernel. Problems in non-recovery mode persisted after installing all updates. I then updated to Ubuntu 19.04 and changed to "generic" linux kernel image without success: Problem persisted, only recovery mode was usable. I updated once more to 19.10 again without any success. From the perhaps related bug #1849947 I tried latest drm-tip kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/ drm-tip kernel solves the issue for first boot, but after resuming from suspend, the same issues display issues occur. Kernel images I tried: - linux-image-4.15.0-1065-oem - on Ubuntu 18.04 LTS, corrupted graphics output without "nomodeset" - linux-image-5.0.0-37-generic - on Ubuntu 19.04, corrupted graphics output without "nomodeset" - linux-image-5.3.0-24-generic - on Ubuntu 19.10, corrupted graphics output without "nomodeset" - linux-image-unsigned-5.4.0-994-generic - on Ubuntu 19.10, corrupted graphics output after resuming from suspend ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.4.0-994-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 18:51:15 2019 DistUpgraded: 2019-12-07 22:36:44,841 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-11-25 (13 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-994-generic root=UUID=45745b59-5aff-4246-94d2-34fe9ae5012f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-12-07 (0 days ago) dmi.bios.date: 11/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.1 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.1:bd11/08/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864392] Re: WiFi not working
On Ubuntu 20.04, WiFi won't authenticate after the upgrade, and I had to "forget" it, then reenter the password. Much less severe, but it would be a problem for those who don't know what to do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. enx00249b1ec202 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless
[Kernel-packages] [Bug 1864392] Re: WiFi not working
apport information ** Tags added: focal ** Description changed: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. enx00249b1ec202 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. enx00249b1ec202 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions:
[Kernel-packages] [Bug 1864392] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5339866/+files/ProcEnviron.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/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. enx00249b1ec202 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions.
[Kernel-packages] [Bug 1864392] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864392/+attachment/5339865/+files/ProcCpuinfoMinimal.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/1864392 Title: WiFi not working Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: No WiFi APs are detected. It's like the driver doesn't recognize the hardware. I tried reinstalling it, but it didn't work. Please fix this ASAP. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-40-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: backport-iwlwifi-dkms 7906-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Feb 23 18:43:16 2020 InstallationDate: Installed on 2020-01-19 (35 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: backport-iwlwifi-dkms UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (37 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. enx00249b1ec202 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yamiyuki 2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-01-19 (50 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: enp0s31f6 no wireless extensions. lono wireless
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Additionally, this one did not cleanly apply:
Additionally, this one does not cleanly apply when cherry-picked:
765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel
warning triggered by lpfc_get_sgl_per_hdwq()
bladernr@galactica:~/development/kernels-ubuntu/focal$ cherrypick
765ab6cdac3b681952da0e22184bf6cf1ae41cf8
error: could not apply 765ab6cdac3b... scsi: lpfc: Fix a kernel warning
triggered by lpfc_get_sgl_per_hdwq()
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'
bladernr@galactica:~/development/kernels-ubuntu/focal$ git diff
diff --cc drivers/scsi/lpfc/lpfc_sli.c
index e660ee98ad8b,613fbf4a7da9..
--- a/drivers/scsi/lpfc/lpfc_sli.c
+++ b/drivers/scsi/lpfc/lpfc_sli.c
@@@ -20687,7 -20668,7 +20687,11 @@@ lpfc_get_sgl_per_hdwq(struct lpfc_hba *
/* allocate more */
spin_unlock_irqrestore(>hdwq_lock, iflags);
tmp = kmalloc_node(sizeof(*tmp), GFP_ATOMIC,
++<<< HEAD
+ cpu_to_node(hdwq->io_wq->chann));
++===
+ cpu_to_node(raw_smp_processor_id()));
++>>> 765ab6cdac3b... scsi: lpfc: Fix a kernel warning triggered by
lpfc_get_sgl_per_hdwq()
if (!tmp) {
lpfc_printf_log(phba, KERN_INFO, LOG_SLI,
"8353 error kmalloc memory for HDWQ "
@@@ -20830,7 -20811,7 +20834,11 @@@ lpfc_get_cmd_rsp_buf_per_hdwq(struct lp
/* allocate more */
spin_unlock_irqrestore(>hdwq_lock, iflags);
tmp = kmalloc_node(sizeof(*tmp), GFP_ATOMIC,
++<<< HEAD
+ cpu_to_node(hdwq->io_wq->chann));
++===
+ cpu_to_node(raw_smp_processor_id()));
++>>> 765ab6cdac3b... scsi: lpfc: Fix a kernel warning triggered by
lpfc_get_sgl_per_hdwq()
if (!tmp) {
lpfc_printf_log(phba, KERN_INFO, LOG_SLI,
"8355 error kmalloc memory for HDWQ "
--
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/1855303
Title:
Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
In Progress
Bug description:
[IMPACT]
This is related to bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340
both patch sets are needed to make up
This is a massive number of updates by Broadcom to the lpfc driver that
didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware
support for 5 years, we need to ensure as much hardware support lands as
possible to support server vendors over the next couple years.
Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The
version in focal is 12.2.0.3 and missing several bug fixes and
hardware support additions.
Please update the driver in focal appropriately.
[FIXES]
eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by
last cpu id set
4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned
cpu for allocation
3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version
to 12.6.0.2
542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max
queues to be hdwq count
bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map
for not present cpus
d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of
lpfc_sli4_cleanup_poll_list()
6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity:
lpfc_cmpl_els_rsp(): Null pointer dereferences
6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity:
lpfc_get_scsi_buf_s3(): Null pointer dereferences
61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix
lpfc_cpumask_of_node_init()
eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel
warning triggered by lpfc_sli4_enable_intr()
765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel
warning triggered by lpfc_get_sgl_per_hdwq()
aff6ab9e7221c1b5d15418419b9797e5badd4aec scsi: lpfc: Update lpfc version
to 12.6.0.1
171f6c41949f6e9d5e09dcac842a10bf8dda8dcc scsi: lpfc: Add enablement of
multiple adapter dumps
dcaa213679387e95a315dca05c57dbb15273703c scsi: lpfc: Change default IRQ
model on AMD architectures
93a4d6f40198dffcca35d9a928c409f9290f1fe0 scsi: lpfc: Add registration
for CPU Offline/Online events
b9da814cd5f5bb93041a6e4dbc9c5149713186ff scsi: lpfc: Clarify FAWNN error
message
69641627c653464db46f3e3d8c438349be055670 scsi: lpfc: Sync with FC-NVMe-2
SLER change to require Conf with SLER
dda5bdf074da3782ff9e785ee50cd2a3f214d498 scsi: lpfc: Fix dynamic fw log
enablement check
[Kernel-packages] [Bug 1855303] Re: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5
Hi Vignesh, As I've been working on this and I just noticed that several of these patches do not exist in the upstream kernel: 89cc9dba63c91a6c796dc46342c1d57c82c9b0cd scsi: lpfc: Fix lpfc_io_buf resource leak in lpfc_get_scsi_buf_s4 error path 692fc8380ca0f9185e75e01a74357d2cf3083743 scsi: lpfc: Fix broken Credit Recovery after driver load 0f74f70cb674e3b8712e896863ad85db4d193d46 scsi: lpfc: Fix registration of ELS type support in fdmi 01034e708a353fed29963d084c35d58785a317a6 scsi: lpfc: Fix release of hwq to clear the eq relationship 3cd50eac891db354e945bf9898726e163a19560e scsi: lpfc: Fix compiler warning on frame size 3ad04f4f0ad75ad4e7d886133f673d9fe20aa9c4 scsi: lpfc: Fix coverity errors in fmdi attribute handling 8d9fae72109e9921f52be342007b4c78490ea4fe scsi: lpfc: Remove handler for obsolete ELS - Read Port Status (RPS) 20d674a4bf64acf54eadc7215ea32b88a3a7687e scsi: lpfc: Clean up hba max_lun_queue_depth checks 35817310d9e05e666dbd242750008dad33ed8992 scsi: lpfc: Update lpfc version to 12.6.0.4 fd6cc30f341fea14bac45bf1c5c9d10702c18a9d scsi: lpfc: Copyright updates for 12.6.0.4 patches 73ec6d2748dc35db2b32cf3c182a27c4a0837b9b scsi: fc: Update Descriptor definition and add RDF and Link Integrity FPINs df3fe76658ed47617741819a501e2bd2ae446962 scsi: lpfc: add RDF registration and Link Integrity FPIN logging So I appreciate the patch set you've provided, but due to the number of patches, what I need to do is cherry-pick them from mainline and push a branch with cherry picks rather than 70+ patches that need to be reviewed/applied by the kernel team. And because I can't find these in mainline at all (I've just checked all the proposed commit ids against the most recent updates to mainline) I can't cherry pick these. Do you know when they'll be accepted upstream? I also checked against Linus tree and cant find those commit IDs there either. -- 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/1855303 Title: Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x from 5.5 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: [IMPACT] This is related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340 both patch sets are needed to make up This is a massive number of updates by Broadcom to the lpfc driver that didn't make 5.4 in time. As 20.04 is an LTS release with expected hardware support for 5 years, we need to ensure as much hardware support lands as possible to support server vendors over the next couple years. Broadcom has updated the lpfc driver to version 12.6.0.2 in 5.5. The version in focal is 12.2.0.3 and missing several bug fixes and hardware support additions. Please update the driver in focal appropriately. [FIXES] eede4970fb6c29f2056d7d016a3764c90e9d8a65 scsi: lpfc: size cpu map by last cpu id set 4583a4f66b323c6e4d774be2649e83a4e7c7b78c scsi: lpfc: use hdwq assigned cpu for allocation 3b294c0fb910dc91250abab574e85c9c1957c795 scsi: lpfc: Update lpfc version to 12.6.0.2 542ddc9b346984cb5bbc2a923d3f3f27ae961ffa scsi: lpfc: revise nvme max queues to be hdwq count bc227dde0d8b687aa525d01b0df5556d4d37eca3 scsi: lpfc: Initialize cpu_map for not present cpus d480e57809a04a3b9e755c0bdd43e10a9f12 scsi: lpfc: fix inlining of lpfc_sli4_cleanup_poll_list() 6c6d59e0fe5b86cf273d6d744a6a9768c4ecc756 scsi: lpfc: fix: Coverity: lpfc_cmpl_els_rsp(): Null pointer dereferences 6f23f8c5c9f1be4eb17c035129c80e49000c18a7 scsi: lpfc: fix: Coverity: lpfc_get_scsi_buf_s3(): Null pointer dereferences 61951a6d3153b4482404b739be921a7459f8dc12 scsi: lpfc: Fix lpfc_cpumask_of_node_init() eea2d396aa57acb3607f79ef04c08c2c5166f3fa scsi: lpfc: Fix a kernel warning triggered by lpfc_sli4_enable_intr() 765ab6cdac3b681952da0e22184bf6cf1ae41cf8 scsi: lpfc: Fix a kernel warning triggered by lpfc_get_sgl_per_hdwq()
[Kernel-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Is this going to be fixed in 20.04? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
It is a r8168 card. The problem continues to happen with the dkms module however. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 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-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x
[Kernel-packages] [Bug 1864061] Re: PCI/internal sound card not detected
Thanks -- looks like it's working! For anyone else with this problem, I enabled proposed (as found in https://wiki.ubuntu.com/Testing/EnableProposed), then ran apt install for: linux-generic/eoan-proposed linux-headers-generic/eoan-proposed linux- image-generic/eoan-proposed linux-libc-dev/eoan-proposed linux-signed- generic/eoan-proposed linux-firmware libasound2 which ended up installing/upgrading: linux-headers-5.3.0-43 linux-headers-5.3.0-43-generic linux-image-5.3.0-43-generic linux-modules-5.3.0-43-generic linux-modules-extra-5.3.0-43-generic libasound2 libasound2-data libasound2-dev linux-firmware I did NOT blacklist snd_soc_skl and snd_hda_intel in the /etc/modprobe.d/blacklist.conf since the comment said "after linux-image-5.3.0-43-generic is ready, the blacklist is not needed anymore". I kept the "options snd-hda-intel dmic_detect=0" that I had previously added to /etc/modprobe.d/alsa-base.conf, didn't try removing it. Sound works again, pavucontrol sees the devices it saw in -40, amixer can control volume again. It still doesn't see the built-microphone, but that's a different bug that I think is targeted for 20.04. -- 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/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the
[Kernel-packages] [Bug 1866866] Re: [FFe] Please accept patches for secure guest feature
The kernel team picked up the ('secure guest' aka protvirt) kernel patches for
focal master-next and with that LP 1835531 was changed to Fix Committed.
Hence I'm updating the kernel entry here to Fix Committed, too.
(Notice that the kernel didn't reached the kernel freeze yet, so it's
technically not part of this FFe, but since all the affected components
are needed for the 'secure guest' feature it was added here for the
reason of completeness.)
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1866866
Title:
[FFe] Please accept patches for secure guest feature
Status in Ubuntu on IBM z Systems:
New
Status in linux package in Ubuntu:
Fix Committed
Status in qemu package in Ubuntu:
New
Status in s390-tools package in Ubuntu:
Fix Released
Bug description:
The secure guest feature (aka protvirt) affects multiple components (kernel,
qemu and s390-tools - see below).
While dedicated tickets for the different components exist since quite a
while, the code arrived late and/or discussion to get it upstream accepted took
longer than expected.
(Even if we as of today didn't reached the kernel freeze, I'm already adding
kernel to this FFe.)
Since this is a very important feature the current IBM Z and LinuxONE
family, it's requested to be included into focal, the next LTS
release, to become exploitable by long running systems.
The code is largely architecture specific.
No brand new packages or new upstream version are requested, only the
cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able.
kernel:
The patch set for the kernel is huge (30+ commits), but has only one common
code patch (two files).
The arch specific patches landed in between in linux-next, the arch specific
one is expected to land there very soon (hours/days from now). The common-code
patch ran through several hands and landed in between in Andrew Morton's mmots
tree.
A pre-screening of the code was done by the kernel team and it looked
acceptable.
(dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531)
qemu:
The entire code seems to be arch specific.
Again a pre-screening of the maintainer lead to the fact that it should be
acceptable, too.
(dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546)
s390-tools:
The entire tool only exists for the s390x architecture.
Hence obviously everything is arch specific on that.
(dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534)
Currently work is going on to test this function end to end based on Ubuntu
components (means based on our s390-tools, qemu and kernel [focal master-next]
trees).
On top I applied the patches to the packages as well and did manual test
buids.
With that a potential regression can be considered as low - and even
in case of a regression, it will affect s390x only.
The patches are being staged for this feature in:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+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 1835531] Re: [20.04 FEAT] Base KVM setup for secure guests - kernel part
** Changed in: ubuntu-z-systems Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835531 Title: [20.04 FEAT] Base KVM setup for secure guests - kernel part Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Enable KVM guests to start and control a guest running in secure mode. With that Customers can securely run sensitive workloads in KVM on premise and in the cloud. Feature Request for kernel contribution Target kernel will be 5.3. Currently not available. Git-commit / backport will be provided To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1835531/+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 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04
Yes, both microphone and speakers are now working for me after updating from proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1860697 Title: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Bug description: I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both output and input, does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 12:00:01 2020 InstallationDate: Installed on 2019-09-06 (139 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20QDCTO1WW ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago) dmi.bios.date: 12/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+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 1860697] Re: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04
I can confirm this problem is fixed after latest update on X1 Carbon 7th gen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1860697 Title: Sound doesn't work on Lenovo X1 Carbon 7th with 20.04 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Bug description: I recently upgraded from 18.04+HWE kernel to 20.04 and now sound, both output and input, does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jan 23 12:00:01 2020 InstallationDate: Installed on 2019-09-06 (139 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20QDCTO1WW ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-22 (1 days ago) dmi.bios.date: 12/09/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET43W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET43W(1.26):bd12/09/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697/+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 1868388] 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/1868388 Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] Status in linux package in Ubuntu: Confirmed Bug description: Got this after resuming from suspend for a few hours. Also noticed that it was not possible to re-establish wifi connectivity. Had to reboot the machine to get back to a proper working state. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1443 F pulseaudio marcus 1889 F pulseaudio Date: Sat Mar 21 11:43:52 2020 Failure: oops InstallationDate: Installed on 2020-03-18 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 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: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868388/+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 1868388] [NEW] watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0]
Public bug reported: Got this after resuming from suspend for a few hours. Also noticed that it was not possible to re-establish wifi connectivity. Had to reboot the machine to get back to a proper working state. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1443 F pulseaudio marcus 1889 F pulseaudio Date: Sat Mar 21 11:43:52 2020 Failure: oops InstallationDate: Installed on 2020-03-18 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 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: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-kerneloops focal kernel-oops -- 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/1868388 Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] Status in linux package in Ubuntu: Confirmed Bug description: Got this after resuming from suspend for a few hours. Also noticed that it was not possible to re-establish wifi connectivity. Had to reboot the machine to get back to a proper working state. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-18-generic 5.4.0-18.22 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1443 F pulseaudio marcus 1889 F pulseaudio Date: Sat Mar 21 11:43:52 2020 Failure: oops InstallationDate: Installed on 2020-03-18 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:671d Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8c0be221-e900-480f-b359-5cbd3f16ebd4 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: kerneloops-daemon N/A SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#11 stuck for 188s! [swapper/11:0] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C
Re: [Kernel-packages] [Bug 1868376] Re: after kernel update: no sound, freeze on standby
*** This bug is a duplicate of bug 1867803 *** https://bugs.launchpad.net/bugs/1867803 I can verify that Kernel version 5.3.0-43 (from proposed) works, as did 5.3.0-40. So this is probably a duplicate of 1867803. Kind regards Wolfgang Ratzka ** This bug has been marked a duplicate of bug 1867803 ALSA: No soundcards found after updating kernel to 5.3.0.42.36 -- 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/1868376 Title: after kernel update: no sound, freeze on standby Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868376/+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 1858389] Re: lxd won't restart a container
Moved the bug over to the kernel. Those log messages are caused by reference issues in a network namespace preventing it from being flushed, in turn preventing the LXC monitor from exiting, holding everything up. ** Package changed: lxd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858389 Title: lxd won't restart a container Status in linux package in Ubuntu: New Bug description: During the upgrade of a container from xenial to bionic, the container stopped working after the reboot. In an manual attempt to start the container: # lxc start juju-3fae13-25-lxd-6 error: Monitor is hung There are no failures reported in lxd/lxc related log files The dmesg does give some possibly related lines: [24085329.749762] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085339.874547] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085349.931433] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085360.136221] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085370.329020] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 I could find that eth2 got renamed quite a few time: dmesg | grep eth2 | grep renamed [ 10.974225] i40e :02:00.2 eno3: renamed from eth2 [ 38.168206] eth2: renamed from vethX6IXIX [ 39.528396] eth1: renamed from veth2L8Q43 [ 39.544217] eth2: renamed from vethCL4RR8 [ 42.132600] eth0: renamed from veth27ILVJ [ 42.184425] eth2: renamed from vethGV30Y9 [ 43.332523] eth2: renamed from veth38IOJO [ 44.553249] eth2: renamed from vethYWPS85 [ 47.696816] eth2: renamed from vethRS5NIA [12244954.658741] eth0: renamed from veth23WYKR [12244954.712483] eth2: renamed from vethXKHJAY [21391530.547187] eth2: renamed from vethON24JW [21392047.344985] eth2: renamed from vethBHEXYH [21852338.859877] eth2: renamed from veth44669K Kernel running: uname -a Linux openstack-9 4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:38 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lxd running: dpkg -l | grep lxd ii lxd 2.0.11-0ubuntu1~16.04.4 amd64Container hypervisor based on LXC - daemon ii lxd-client2.0.11-0ubuntu1~16.04.4 amd64Container hypervisor based on LXC - client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858389/+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 1858389] 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 1858389 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: xenial -- 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/1858389 Title: lxd won't restart a container Status in linux package in Ubuntu: Incomplete Bug description: During the upgrade of a container from xenial to bionic, the container stopped working after the reboot. In an manual attempt to start the container: # lxc start juju-3fae13-25-lxd-6 error: Monitor is hung There are no failures reported in lxd/lxc related log files The dmesg does give some possibly related lines: [24085329.749762] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085339.874547] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085349.931433] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085360.136221] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085370.329020] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 I could find that eth2 got renamed quite a few time: dmesg | grep eth2 | grep renamed [ 10.974225] i40e :02:00.2 eno3: renamed from eth2 [ 38.168206] eth2: renamed from vethX6IXIX [ 39.528396] eth1: renamed from veth2L8Q43 [ 39.544217] eth2: renamed from vethCL4RR8 [ 42.132600] eth0: renamed from veth27ILVJ [ 42.184425] eth2: renamed from vethGV30Y9 [ 43.332523] eth2: renamed from veth38IOJO [ 44.553249] eth2: renamed from vethYWPS85 [ 47.696816] eth2: renamed from vethRS5NIA [12244954.658741] eth0: renamed from veth23WYKR [12244954.712483] eth2: renamed from vethXKHJAY [21391530.547187] eth2: renamed from vethON24JW [21392047.344985] eth2: renamed from vethBHEXYH [21852338.859877] eth2: renamed from veth44669K Kernel running: uname -a Linux openstack-9 4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:38 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lxd running: dpkg -l | grep lxd ii lxd 2.0.11-0ubuntu1~16.04.4 amd64Container hypervisor based on LXC - daemon ii lxd-client2.0.11-0ubuntu1~16.04.4 amd64Container hypervisor based on LXC - client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858389/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
After enabling selective updates from proposed, I ran > sudo apt install linux-image-5.3.0-43-generic > linux-modules-extra-5.3.0-43-generic linux-firmware/eoan-proposed > libasound2/eoan-proposed > sudo add-apt-repository ppa:hui.wang/audio-master > sudo apt-get update > sudo apt install libasound2 I removed "options snd-hda-intel dmic_detect=0" from /etc/modprobe.d /alsa-base.conf and restarted. I can see the onboard sound card and microphone in gnome's interface. I used alsa mixer to maxout all levels. I was able to record sound and play it back using sound recorder I was able to play music from spotify and youtube I was unable to use the "test" feature of gnome settings : I can open the window, but neither the front right nor front left buttons in the test play any sound Connecting my bluetooth headset correctly switched output automatically to the headset but didn't switch input to the headset. I was however able to manually set input to the headset. disconnecting and reconnecting the headset after manually selecting it didn't fix the autoselection of the microphone but that feels like an unrelated issue. -- 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/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1868374] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339665/+files/ProcEnviron.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339661/+files/Lspci.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339669/+files/RfKill.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339670/+files/UdevDb.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339662/+files/Lsusb.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339666/+files/ProcInterrupts.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339664/+files/ProcCpuinfoMinimal.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339663/+files/ProcCpuinfo.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339668/+files/PulseList.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339659/+files/CurrentDmesg.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339658/+files/CRDA.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339660/+files/IwConfig.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339667/+files/ProcModules.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 2488 F pulseaudio /dev/snd/controlC0: jeroen 2488 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.173.16 Tags: bionic Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: docker plugdev sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 07/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX450FDX.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX450FDX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX450FDX_UX480FD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868374/+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 1868374] Re: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios
apport information ** Tags added: apport-collected ** Description changed: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus-wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.12 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: jeroen 2488 F pulseaudio + /dev/snd/controlC0: jeroen 2488 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-05-01 (324 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + MachineType: ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2dd2545f-ebe3-4b15-9fc0-581e3b760d31 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-42-generic N/A + linux-backports-modules-5.3.0-42-generic N/A + linux-firmware1.173.16 + Tags: bionic + Uname: Linux 5.3.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: docker plugdev sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 07/05/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: UX450FDX.307 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX450FDX + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX450FDX.307:bd07/05/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX450FDX_UX480FD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX450FDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: ZenBook + dmi.product.name: ZenBook UX450FDX_UX480FD + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1868374/+attachment/5339657/+files/AlsaInfo.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/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Confirmed Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1
[Kernel-packages] [Bug 1858389] [NEW] lxd won't restart a container
You have been subscribed to a public bug: During the upgrade of a container from xenial to bionic, the container stopped working after the reboot. In an manual attempt to start the container: # lxc start juju-3fae13-25-lxd-6 error: Monitor is hung There are no failures reported in lxd/lxc related log files The dmesg does give some possibly related lines: [24085329.749762] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085339.874547] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085349.931433] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085360.136221] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 [24085370.329020] unregister_netdevice: waiting for eth2 to become free. Usage count = 1 I could find that eth2 got renamed quite a few time: dmesg | grep eth2 | grep renamed [ 10.974225] i40e :02:00.2 eno3: renamed from eth2 [ 38.168206] eth2: renamed from vethX6IXIX [ 39.528396] eth1: renamed from veth2L8Q43 [ 39.544217] eth2: renamed from vethCL4RR8 [ 42.132600] eth0: renamed from veth27ILVJ [ 42.184425] eth2: renamed from vethGV30Y9 [ 43.332523] eth2: renamed from veth38IOJO [ 44.553249] eth2: renamed from vethYWPS85 [ 47.696816] eth2: renamed from vethRS5NIA [12244954.658741] eth0: renamed from veth23WYKR [12244954.712483] eth2: renamed from vethXKHJAY [21391530.547187] eth2: renamed from vethON24JW [21392047.344985] eth2: renamed from vethBHEXYH [21852338.859877] eth2: renamed from veth44669K Kernel running: uname -a Linux openstack-9 4.4.0-143-generic #169-Ubuntu SMP Thu Feb 7 07:56:38 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lxd running: dpkg -l | grep lxd ii lxd 2.0.11-0ubuntu1~16.04.4 amd64Container hypervisor based on LXC - daemon ii lxd-client2.0.11-0ubuntu1~16.04.4 amd64Container hypervisor based on LXC - client ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- lxd won't restart a container https://bugs.launchpad.net/bugs/1858389 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
5.4.0-18-generic fixed it for me too (Dell XPS 13 9370) . Thanks ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic Status in linux package in Ubuntu: Confirmed Bug description: I upgraded to Focal Fossa 3 days ago and nothing broke. At the time, it was still using linux 5.3 (linux-image-5.3.0-24-generic). Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after rebooting, the screen brightness does not work anymore - neither from keyboard keys nor from the slider in the gnome-shell panel. It works again when rebooting into the previous linux- image-5.3.0-24-generic kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 1892 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 20:23:31 2020 InstallationDate: Installed on 2018-09-13 (481 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago) dmi.bios.date: 07/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+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 1868376] Re: after kernel update: no sound, freeze on standby
Thank you for reporting this bug and make ubuntu better! can you check bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867803 to see if you have the same symptons? -- 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/1868376 Title: after kernel update: no sound, freeze on standby Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868376/+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 1868376] 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/1868376 Title: after kernel update: no sound, freeze on standby Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868376/+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 1868376] [NEW] after kernel update: no sound, freeze on standby
Public bug reported: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1868376 Title: after kernel update: no sound, freeze on standby Status in linux package in Ubuntu: New Bug description: After upgrading to linux-image-5.3.0-42-generic (5.3.0-42.34) sound stopped working, trying to send the notebook into standby freezes the machine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-42-generic 5.3.0-42.34 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 14:05:43 2020 InstallationDate: Installed on 2020-02-12 (37 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Swift SF314-56G ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=e7633265-a27c-44c9-90a8-9a7fe4b15d09 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2020-02-18 (31 days ago) dmi.bios.date: 01/04/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd01/04/2019:svnAcer:pnSwiftSF314-56G:pvrV1.08:rvnWL:rnStrongbow_WL:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56G dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868376/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1868374] 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 1868374 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: Incomplete Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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/1868374/+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 1866866] Re: [FFe] Please accept patches for secure guest feature
** Tags added: id-5e74bdb19f8d694f2b80ce41 -- 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/1866866 Title: [FFe] Please accept patches for secure guest feature Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: New Status in s390-tools package in Ubuntu: Fix Released Bug description: The secure guest feature (aka protvirt) affects multiple components (kernel, qemu and s390-tools - see below). While dedicated tickets for the different components exist since quite a while, the code arrived late and/or discussion to get it upstream accepted took longer than expected. (Even if we as of today didn't reached the kernel freeze, I'm already adding kernel to this FFe.) Since this is a very important feature the current IBM Z and LinuxONE family, it's requested to be included into focal, the next LTS release, to become exploitable by long running systems. The code is largely architecture specific. No brand new packages or new upstream version are requested, only the cherry-pick of commits (or PR) - so far everything is 'cherry-pick'-able. kernel: The patch set for the kernel is huge (30+ commits), but has only one common code patch (two files). The arch specific patches landed in between in linux-next, the arch specific one is expected to land there very soon (hours/days from now). The common-code patch ran through several hands and landed in between in Andrew Morton's mmots tree. A pre-screening of the code was done by the kernel team and it looked acceptable. (dedicated kernel ticket: https://bugs.launchpad.net/bugs/1835531) qemu: The entire code seems to be arch specific. Again a pre-screening of the maintainer lead to the fact that it should be acceptable, too. (dedicated qemu ticket: https://bugs.launchpad.net/bugs/1835546) s390-tools: The entire tool only exists for the s390x architecture. Hence obviously everything is arch specific on that. (dedicated s390-tools ticket: https://bugs.launchpad.net/bugs/1834534) Currently work is going on to test this function end to end based on Ubuntu components (means based on our s390-tools, qemu and kernel [focal master-next] trees). On top I applied the patches to the packages as well and did manual test buids. With that a potential regression can be considered as low - and even in case of a regression, it will affect s390x only. The patches are being staged for this feature in: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1866866/+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 1868374] [NEW] Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios
Public bug reported: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus-wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868374 Title: Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios Status in linux package in Ubuntu: New Bug description: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus- wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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/1868374/+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 1868374] [NEW] Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios
You have been subscribed to a public bug: When I upgrade my laptop (ASUSTeK COMPUTER INC. ZenBook UX450FDX_UX480FD/UX450FDX, BIOS UX450FDX.307 07/05/2019) to the latest BIOS (UX450FDX.313), the laptop keeps getting events to change the display mode (FN+F8), when having an external monitor connected this makes the laptop unusable, as the gnome mode selector keeps popping up. When not using an external monitor it seriously hinders/slows down keyboard input. When I revert back to the previous BIOS (UX450FDX.307) everything is fine again. What's odd is that when I use the FN+F8 button now I don't get this gnome mode selector, it just changes the mode right away. I'm guessing this is a bug in the kernel asus-wmi driver. I checked the history of the kernel for the file "drivers/platform/x86/asus-wmi.c", but I don't see anything that could have fixed this in 5.3+ kernels. I'm willing to upgrade bios/kernel and/or test experimental drivers in order to fix this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-42-generic 5.3.0-42.34~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 Date: Sat Mar 21 13:45:47 2020 InstallationDate: Installed on 2019-05-01 (324 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Asus WMI hotkey driver bug: External display mode button seems "stuck" on the latest bios https://bugs.launchpad.net/bugs/1868374 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1858844] Re: [Dell XPS 15 9575] Screen brightness stopped working with linux-image-5.4.0-9-generic
5.4.0-18-generic fixed it for me too (OP, Dell XPS 15 9575) as far as the keyboard keys are concerned. The slider in the gnome panel however is still not moved when I use the keyboard keys. -- 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/1858844 Title: [Dell XPS 15 9575] Screen brightness stopped working with linux- image-5.4.0-9-generic Status in linux package in Ubuntu: Confirmed Bug description: I upgraded to Focal Fossa 3 days ago and nothing broke. At the time, it was still using linux 5.3 (linux-image-5.3.0-24-generic). Today, it updated to linux 5.4 (linux-image-5.4.0-9-generic) and after rebooting, the screen brightness does not work anymore - neither from keyboard keys nor from the slider in the gnome-shell panel. It works again when rebooting into the previous linux- image-5.3.0-24-generic kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-9-generic 5.4.0-9.12 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mario 1892 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 20:23:31 2020 InstallationDate: Installed on 2018-09-13 (481 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-01-04 (3 days ago) dmi.bios.date: 07/07/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858844/+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 1867753] Re: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal
** Changed in: ubuntu-z-systems Status: Incomplete => 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/1867753 Title: [Ubuntu 20.04] Unset HIBERNATION and PM kernel config options for focal Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Addl change required for kernel config. from CONFIG_HIBERNATION=y CONFIG_PM=y to #CONFIG_HIBERNATION is not set #CONFIG_PM is not set hope that will be the last ticket for 20.04... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867753/+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 1867656] Re: Remove linux-firmware dependency from kernel meta packages for s390x
The submitted request to the kernel teams mailing list got APPLIED. Hence updating status to 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-meta in Ubuntu. https://bugs.launchpad.net/bugs/1867656 Title: Remove linux-firmware dependency from kernel meta packages for s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-meta package in Ubuntu: Fix Committed Bug description: As far as we understand all firmware upgrades (and the firmware itself) is coming from the HMC on case of IBM Z and LinuxONE. This not only incl. the CEC code, but also all the firmware for the different cards and adapters. If this is the case (and will be in future), it would make sense for us to get rid of the linux-firmware package for s390x - this would make things leaner, reduce size and eventually increase (installation) performance ... So please IBM can you confirm that all firmware updates (MCLs) are always done via the HMC and that is therefore the linux-firmware package is obsolete on s390x? Thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1867656/+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 1866628] Re: WiFi connection slows down significantly when Bluetooth headset connected (QCA9377 chip)
@seb128 can you please set the Importance to move forward? -- 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/1866628 Title: WiFi connection slows down significantly when Bluetooth headset connected (QCA9377 chip) Status in linux package in Ubuntu: Confirmed Bug description: STEPS TO REPRODUCE: 1. Connect laptop to internet via WiFi only. 2. Play any HD video on YouTube, etc. 3. Pair Bluetooth headset with laptop. ACTUAL RESULT: Video plays with long interruptions after Bluetooth headset was connected. EXPECTED RESULT: Video plays without interruptions when Bluetooth headset connected. NOTES: Bug reproduces on Ubuntu 18.04 and Ubuntu 19.10. Laptop: Lenovo IdeaPad 330-15IKB (81DE02VHRA). Network chip: QCA9377 https://www.qualcomm.com/products/qca9377 THERE ARE A LOT OF MENTIONS OVER INTERNET OF SAME PROBLEM OF THIS CHIP WITH UBUNTU BUT NO SUCH PROBLEM ON WINDOWS 10. One of them: https://forums.linuxmint.com/viewtopic.php?t=302482 POSSIBLE SOLUTION DESCRIBED HERE: https://askubuntu.com/questions/1097230/ubuntu-18-04-poor-wi-fi-when-connected-with-bluetooth-headphone Driver info in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866628/+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
