[Kernel-packages] [Bug 1918887] Re: after upgrade to ubuntu 14.04, system not restarting and touchpad not working
[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/1918887 Title: after upgrade to ubuntu 14.04, system not restarting and touchpad not working Status in linux package in Ubuntu: Expired Bug description: after upgrade to ubuntu 14.04 from ubuntu 12.04, the system is not restarting, however after quickly pressing esc i can run the system on F11 (hp recovery) mode , but in that the touchpad is not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-170-generic 3.13.0-170.220 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 12 12:58:15 2021 InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130722-08:34 LiveMediaBuild: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130722-08:34 SourcePackage: linux-signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918887/+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 1919042] Re: Touchpad not working on HP Pavilion Laptop 14-dv0xxx
[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/1919042 Title: Touchpad not working on HP Pavilion Laptop 14-dv0xxx Status in linux package in Ubuntu: Expired Bug description: HP Imagepad not detected in 'HP Pavilion 14-DV00054TU' after installing Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hp 1523 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 14 00:45:36 2021 InstallationDate: Installed on 2021-03-08 (5 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Pavilion Laptop 14-dv0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=84f5a50d-8a8e-4afc-8e8c-3245f566346a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2021 dmi.bios.vendor: Insyde dmi.bios.version: F.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87C9 dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.11:bd01/15/2021:svnHP:pnHPPavilionLaptop14-dv0xxx:pvrType1ProductConfigId:rvnHP:rn87C9:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-dv0xxx dmi.product.sku: 2N1L0PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919042/+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 1928507] Re: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11
** 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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Confirmed Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497676/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] Re: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11
apport information ** Tags added: apport-collected ** Description changed: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.17 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1327 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-05-14 (0 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + MachineType: Intel Corporation Tiger Lake Client Platform + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-53-generic N/A + linux-backports-modules-5.8.0-53-generic N/A + linux-firmware1.187.12 + Tags: focal + Uname: Linux 5.8.0-53-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: 03/17/2021 + dmi.bios.vendor: Intel Corporation + dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: TigerLake U DDR4 SODIMM RVP + dmi.board.vendor: Intel Corporation + dmi.board.version: 1 + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: Intel Corporation + dmi.chassis.version: 0.1 + dmi.ec.firmware.release: 1.35 + dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: + dmi.product.family: Tiger Lake Client System + dmi.product.name: Tiger Lake Client Platform + dmi.product.sku: 000110010001 + dmi.product.version: 0.1 + dmi.sys.vendor: Intel Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497674/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021
[Kernel-packages] [Bug 1928507] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497690/+files/WifiSyslog.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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497679/+files/Lspci-vt.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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497688/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497683/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497687/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497691/+files/acpidump.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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497689/+files/UdevDb.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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497677/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497684/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497686/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497678/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497685/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497680/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497681/+files/Lsusb-t.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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497682/+files/Lsusb-v.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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928522] 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 1928522 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/1928522 Title: seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148 Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928522/+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 1928507] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1928507/+attachment/5497675/+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/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1327 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel Corporation Tiger Lake Client Platform Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a44b834c-d346-4f9c-aa08-ed4716d2ec2c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-53-generic N/A linux-backports-modules-5.8.0-53-generic N/A linux-firmware1.187.12 Tags: focal Uname: Linux 5.8.0-53-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: 03/17/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: TGLSFWI1.R00.4092.E68.2103171123 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: TigerLake U DDR4 SODIMM RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnIntelCorporation:bvrTGLSFWI1.R00.4092.E68.2103171123:bd03/17/2021:efr1.35:svnIntelCorporation:pnTigerLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnTigerLakeUDDR4SODIMMRVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Tiger Lake Client System dmi.product.name: Tiger Lake Client Platform dmi.product.sku: 000110010001 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928522] [NEW] seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148
Public bug reported: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Summary changed: - linux ADT test failure with linux/4.15.0-144.148 + seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148 ** Description changed: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: - i386: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/i386/l/linux/20210513_154934_db7dd@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz + s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz -- 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/1928522 Title: seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148 Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928522/+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 1927518] Re: Fix kdump failures
** Changed in: linux-azure-4.15 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1927518 Title: Fix kdump failures Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Committed Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-4.15 source package in Focal: Invalid Status in linux source package in Groovy: In Progress Status in linux-azure source package in Groovy: Fix Committed Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Committed Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: SRU Justification [Impact] Microsoft relayed a customer report of failures when trying to take a kdump. These 3 patches fix the issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/video/fbdev/hyperv_fb.c?id=aa5b7d11c7cb87c266d705b237368985e7171958 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=77db0ec8b7764cb9b09b78066ebfd47b2c0c1909 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/hv/channel_mgmt.c?id=8c2d5e0640e53c14b6240e9bf1e32a2226e6e6ca Patch #1 solves a problem where the “Unable to send packet via vmbus” message is output continuously. But with that problem fixed, the second problem can occur where the kdump kernel panics due to receiving an unexpected VMbus UNLOAD complete message. Patch #2 prevents the UNLOAD complete message from ever occurring in the kdump kernel. But if the UNLOAD complete message does occur at some unexpected time, Patch #3 prevents it from causing a panic. These patches seem worthy of application to all affected master kernels. [Test Plan] Cause a guest kernel to crash and successfully acquire a kdump. [Where problems could occur] The extended Hyper-V wait while flushing could cause side effects. [Other Info] SF: #00310145 https://canonical.lightning.force.com/lightning/r/Case/5004K05pZNNQA2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927518/+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 1927808] Re: rtw88_8821ce causes freeze
I tried 5.13, installing packages linux-headers-5.13.0-051300rc1-generic_5.13.0-051300rc1.202105092230_amd64.deb linux-headers-5.13.0-051300rc1_5.13.0-051300rc1.202105092230_all.deb linux-image-unsigned-5.13.0-051300rc1-generic_5.13.0-051300rc1.202105092230_amd64.deb linux-modules-5.13.0-051300rc1-generic_5.13.0-051300rc1.202105092230_amd64.deb Booting 5.13, the graphical (GDM?) login screen did not show; there was a mouse pointer (moving correctly with the mouse) but otherwise black screen. I could log in to the TTY console with Alt-Ctrl-F2, and obtained the output of dmesg as attached; I wonder about the Initramfs unpacking failed: Decoding failed line within. Without the graphical login, I did not think I could properly test the rtw88 module, did not remove the line blacklist rtw88_8821ce from the /etc/modprobe.d/blacklist.conf file. Should I re-try 5.13, somehow differently? ** Attachment added: "dmesg output, with 5.13 kernel and blacklist" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+attachment/5497659/+files/dmesg-5.13.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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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 1923162] Re: riscv64 images fail to boot in qemu
This bug was fixed in the package u-boot - 2021.01+dfsg-3ubuntu10 --- u-boot (2021.01+dfsg-3ubuntu10) impish; urgency=medium * Revert "Skip processing fdtdir on qemu-riscv64_smode target, as it crashes the riscv qemu VM." * Apply upstreamed patch "cmd: pxe_utils: sysboot: fix crash if either board or soc are not set." This fixes a crash booting any extlinux.conf with fdtdir specified, and dtbfile not set and "soc"/"board" not set in the environment LP: #1923162 -- Dimitri John Ledkov Fri, 14 May 2021 16:54:50 +0100 ** Changed in: u-boot (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: New Status in u-boot-menu source package in Focal: Invalid Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: New Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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 1928512] [NEW] Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)
Public bug reported: My internet connection is unstable. The wireless fall down frequently and I noticed that there isn't the directory QCA9565 into the path /etc/firmware/ath*. I've run 'lspci -nnk |grep -i Wireless;lsusb' and the result was: 6:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: Dell QCA9565 / AR9565 Wireless Network Adapter [1028:020c] Bus 001 Device 006: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 012: ID 0cf3:0036 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:670b Microdia Bus 001 Device 008: ID 046d:c535 Logitech, Inc. Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1928512 Title: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01) Status in linux-firmware package in Ubuntu: New Bug description: My internet connection is unstable. The wireless fall down frequently and I noticed that there isn't the directory QCA9565 into the path /etc/firmware/ath*. I've run 'lspci -nnk |grep -i Wireless;lsusb' and the result was: 6:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: Dell QCA9565 / AR9565 Wireless Network Adapter [1028:020c] Bus 001 Device 006: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 012: ID 0cf3:0036 Qualcomm Atheros Communications Bus 001 Device 004: ID 0c45:670b Microdia Bus 001 Device 008: ID 046d:c535 Logitech, Inc. Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928512/+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
Re: [Kernel-packages] [Bug 1916945] Re: unable to Poweroff, it causes a restart instead
latest mainline kernel still has the reboot problem when wake on Lan is enabled in the BIOS On Fri, 14 May 2021 at 12:20, Kai-Heng Feng <1916...@bugs.launchpad.net> wrote: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc1/amd64/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1916945 > > Title: > unable to Poweroff, it causes a restart instead > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > ubuntu 20.04 after jan/2021 update I am unable to poweroff (or > shutdown) the laptop. > > it works fine if I poweroff in windows or when boot test 20.04 iso OS > and power off > > HP probook 650 > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-66-generic 5.4.0-66.74 > ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 > Uname: Linux 5.4.0-66-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: cvancrae 2080 F pulseaudio >/dev/snd/controlC1: cvancrae 2080 F pulseaudio >/dev/snd/pcmC1D0c: cvancrae 2080 F...m pulseaudio >/dev/snd/pcmC1D0p: cvancrae 2080 F...m pulseaudio > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Thu Feb 25 20:15:49 2021 > InstallationDate: Installed on 2018-07-30 (940 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > MachineType: Hewlett-Packard HP ProBook 650 G1 > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic > root=UUID=ef9f1472-488d-4d4d-94ae-545d7b6bf18e ro quiet splash vt.handoff=1 > RelatedPackageVersions: >linux-restricted-modules-5.4.0-66-generic N/A >linux-backports-modules-5.4.0-66-generic N/A >linux-firmware1.187.9 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/13/2017 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: L78 Ver. 01.40 > dmi.board.name: 2101 > dmi.board.vendor: Hewlett-Packard > dmi.board.version: KBC Version 16.3C > dmi.chassis.asset.tag: 5CG4380HYL > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.modalias: > dmi:bvnHewlett-Packard:bvrL78Ver.01.40:bd07/13/2017:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10203:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: > dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI > dmi.product.name: HP ProBook 650 G1 > dmi.product.sku: D9S35AV > dmi.product.version: A3009DD10203 > dmi.sys.vendor: Hewlett-Packard > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916945/+subscriptions > -- 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/1916945 Title: unable to Poweroff, it causes a restart instead Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 20.04 after jan/2021 update I am unable to poweroff (or shutdown) the laptop. it works fine if I poweroff in windows or when boot test 20.04 iso OS and power off HP probook 650 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cvancrae 2080 F pulseaudio /dev/snd/controlC1: cvancrae 2080 F pulseaudio /dev/snd/pcmC1D0c: cvancrae 2080 F...m pulseaudio /dev/snd/pcmC1D0p: cvancrae 2080 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 25 20:15:49 2021 InstallationDate: Installed on 2018-07-30 (940 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 650 G1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=ef9f1472-488d-4d4d-94ae-545d7b6bf18e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.40 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.asset.tag: 5CG4380HYL dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard
[Kernel-packages] [Bug 1770845] Re: Make vfio-pci built-in or xhci_hcd optional
** Changed in: linux-kvm (Ubuntu Focal) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1770845 Title: Make vfio-pci built-in or xhci_hcd optional Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Invalid Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Invalid Bug description: [Impact] This allows vfio-pci to be bound to certain devices during boot, preventing other drivers from binding them. In particular, USB host drivers, like xhci_hcd, are hard to unbind, as USB devices may end up being used by applications. [Test case] Boot the system with vfio-pci.ids=8086:1e31 or other device ID. [Regression potential] Check that VFIO does not bind to any other device. -- Because of nazar-pc@nazar-pc ~> cat '/boot/config-4.15.0-21-generic' | grep CONFIG_USB_XHCI_HCD CONFIG_USB_XHCI_HCD=y Following doesn't work: nazar-pc@nazar-pc ~> cat /etc/modprobe.d/gpu-passthrough.conf options vfio-pci ids=10de:1b06,10de:10ef,1b21:2142 softdep nouveau pre: vfio-pci softdep xhci_hcd pre: vfio-pci GPU is fine (first 2 IDs), but USB controller is always occupied by xhci_hcd and I can't change that while xhci_hcd is built-in. I'd like you to resolve this issue by either embedding vfio-pci module too (prefered solution) or making xhci_hcd optional. There are some discussions withot clean solution online like this: https://www.reddit.com/r/VFIO/comments/4o6wla/cant_get_vfiopci_to_bind_to_usb_30_card_at_boot/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-21-generic 4.15.0-21.22 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-21-generic. ApportVersion: 2.20.10-0ubuntu2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: S51 [SB Omni Surround 5.1], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: nazar-pc 2226 F...m pulseaudio /dev/snd/pcmC1D0p: nazar-pc 2226 F...m pulseaudio /dev/snd/controlC1: nazar-pc 2226 F pulseaudio nazar-pc 2267 F volumeicon Card1.Amixer.info: Card hw:1 'S51'/'Creative Technology Ltd SB Omni Surround 5.1 at usb-:00:14.0-9.2, full spee' Mixer name : 'USB Mixer' Components : 'USB041e:322c' Controls : 12 Simple ctrls : 5 CurrentDesktop: Custom Date: Sat May 12 16:44:11 2018 IwConfig: Error: [Errno 2] Немає такого файла або каталогу: 'iwconfig': 'iwconfig' MachineType: Micro-Star International Co., Ltd. MS-7B45 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/root/boot/vmlinuz-4.15.0-21-generic root=UUID=5170aca4-061a-4c6c-ab00-bd7fc8ae6030 ro rootflags=subvol=root nosplash intel_pstate=disable scsi_mod.use_blk_mq=1 intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.15.0-21-generic N/A linux-backports-modules-4.15.0-21-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] Немає такого файла або каталогу: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.51 dmi.board.asset.tag: Default string dmi.board.name: Z370 GAMING PRO CARBON (MS-7B45) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.51:bd03/29/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B45:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370GAMINGPROCARBON(MS-7B45):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7B45 dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770845/+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 1877088] Autopkgtest regression report (linux-base/4.5ubuntu3.3)
All autopkgtests for the newly accepted linux-base (4.5ubuntu3.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-oem-5.6/5.6.0-1057.61 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to:
Re: [Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
On Fri, May 14, 2021 at 06:01:50PM -, Thiago Jung Bauermann wrote: > Ah, ok. This morning I went ahead and overwrote the whole of /lib/firmware/ > amdgpu/ with the files from the latest commit of the upstream linux- > firmware git repo you mention below. It's been only a little over 2 hours, > but my impression is that the latest firmware does solve the problem. If no > retry page fault happens by the end of the day, then I think it's safe to > say that it fixes the issue. Sounds good. > So at the end of the day (or earlier if I get a retry page fault) I'll do > the procedure you mention to use firmware 1.197 and only overwrite the > picasso* files to confirm if those are the ones that need to be changed. > > I don't know much about GPUs, but from looking at Wikipedia¹ I think my > model is a "Vega 10". Should I overwrite the vega10* files as well? > > ¹ https://en.wikipedia.org/wiki/Radeon_RX_Vega_series#Picasso_(2019)_2 I'm basing it on the PCI id I see in dmesg, which is 1002:15d8, which the driver looks to identify as CHIP_RAVEN and flag with AMD_APU_IS_PICASSO. Based on that it will pick firmware files which begin with "picasso". It would be informative though to have the output from "lspci -vvnn" on your machine. Let's try the picasso files first. If that doesn't work you can try the vega10 files (without the new picasso files), then if that doesn't work, try both. Then we'll have an idea about what the minimal set of files is to fix the problem. -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in linux-firmware package in Ubuntu: Incomplete Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+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 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it
The problem is clearly visible on a Dell Precision 5750. On a ThinkPad P1 Gen 3 the mouse "freezing" effect is barely noticeable. -- 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/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it Status in linux package in Ubuntu: Confirmed Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+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 1877088] Autopkgtest regression report (linux-base/4.5ubuntu1.4)
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.4) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.4/5.4.0-74.83~18.04.1 (amd64) makedumpfile/1:1.6.5-1ubuntu1~18.04.6 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications
[Kernel-packages] [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64
The patch for QEMU that has been mentioned in comment #38 has been merged already, so I'm marking this as Fix-Released there. ** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1915063 Title: Windows 10 wil not install using qemu-system-x86_64 Status in QEMU: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Invalid Bug description: Steps to reproduce install virt-manager and ovmf if nopt already there copy windows and virtio iso files to /var/lib/libvirt/images Use virt-manager from local machine to create your VMs with the disk, CPUs and memory required Select customize configuration then select OVMF(UEFI) instead of seabios set first CDROM to the windows installation iso (enable in boot options) add a second CDROM and load with the virtio iso change spice display to VNC Always get a security error from windows and it fails to launch the installer (works on RHEL and Fedora) I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of no help --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-20 (19 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201030-14:39 MachineType: LENOVO 30E102Z NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1042-oem N/A linux-backports-modules-5.6.0-1042-oem N/A linux-firmware 1.187.8 RfKill: Tags: focal Uname: Linux 5.6.0-1042-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2020 dmi.bios.vendor: LENOVO dmi.bios.version: S07KT08A dmi.board.name: 1046 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: INVALID dmi.product.name: 30E102Z dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620 dmi.product.version: ThinkStation P620 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1915063/+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 1928507] 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 1928507 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1928507] [NEW] Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11
Public bug reported: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928507 Title: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11 Status in linux package in Ubuntu: Incomplete Bug description: Screen tearing for video playback is observed after screen is rotated 180 degree in Ubuntu 20.04, Gnome Vanilla, X11. We haven't seen the issue in Wayland. Here are the steps to reproduce the issue. 1) Install Ubuntu 20.04. 2) Play video on ubuntu 20.04. 3) Turn on 'auto rotation" in setting to rotate the screen; Or use 'xrandr -o 2' to rotate the screen. 4) Screen tearing is observed for 100% reproducible after rotation. 5) It is happening on all of video contents with dynamic scene changing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928507/+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 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Same issue with Ubuntu 20.04 on ThinkPad P50. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_sof_intel_hda_common nvidia_uvm(O) snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match nvidia_drm(PO) snd_soc_acpi nvidia_modeset(PO) snd_soc_core snd_compress
[Kernel-packages] [Bug 1157440] Re: 1002:9808 [Lenovo E435, M490s]: Brightness controls do not work
** Changed in: amd
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: linux (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
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/1157440
Title:
1002:9808 [Lenovo E435, M490s]: Brightness controls do not work
Status in amd:
Won't Fix
Status in linux package in Ubuntu:
Won't Fix
Status in linux source package in Precise:
Won't Fix
Bug description:
Problem:
Brightness keys or brightness settings controls do not change the
brightness or display as intended.
However, If I run the following command it works perfectly:
xrandr --output LVDS --brightness 0.5
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-23-generic 3.5.0-23.35~precise1
ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: CONEXANT Analog [CONEXANT
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 2137 F pulseaudio
/dev/snd/controlC0: ubuntu 2137 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xf0544000 irq 46'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 6
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xf054 irq 16'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa5108,0013'
Controls : 20
Simple ctrls : 10
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Tue Mar 19 17:49:29 2013
HibernationDevice: RESUME=UUID=ee9d3e8f-05df-494c-afc6-36438c39723b
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
MachineType: LENOVO 3469C01
MarkForUpload: True
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic
root=UUID=5396c06a-e550-4e31-b4f5-d953a397915f ro quiet splash initcall_debug
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.5.0-23-generic N/A
linux-backports-modules-3.5.0-23-generic N/A
linux-firmware1.79.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: HNET14WW (1.01 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3469C01
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrHNET14WW(1.01):bd05/30/2012:svnLENOVO:pn3469C01:pvrThinkPadEdgeE435:rvnLENOVO:rn3469C01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3469C01
dmi.product.version: ThinkPad Edge E435
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1157440/+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 1927738] Re: Bluetooth doesn't work in Ubuntu 21.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1927738 Title: Bluetooth doesn't work in Ubuntu 21.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth doesn't work in Ubuntu 21.04 after update ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri May 7 16:32:21 2021 InstallationDate: Installed on 2020-04-08 (394 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to hirsute on 2021-04-15 (22 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1927738/+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
Re: [Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hello Seth, Thank you for the quick and detailed response. Em sexta-feira, 14 de maio de 2021, às 13:14:22 -03, Seth Forshee escreveu: > Before we revert we should see if newer firmware fixes the issue, and > make sure we are only changing the specific firmware files for your > hardware. Ok, sounds good. > I think your hardware is the "Picasso" series. Can you try the > following? If you are unsure about any of the following steps, let me > know and I can provide you with test packages to install instead. Thanks for the offer. It's not a problem getting the files from git and overwrite them manually. > Save all files matching /lib/firmware/amdgpu/picasso* from linux- > firmware 1.190.5. Reinstall 1.197, then overwrite the picasso firmware > files with the ones you saved. Reboot, and confirm that the issues you > see with 1.197 are fixed. If they are not fixed, then there's no need to > proceed as we haven't found the correct firmware files which are causing > your issues. Ah, ok. This morning I went ahead and overwrote the whole of /lib/firmware/ amdgpu/ with the files from the latest commit of the upstream linux- firmware git repo you mention below. It's been only a little over 2 hours, but my impression is that the latest firmware does solve the problem. If no retry page fault happens by the end of the day, then I think it's safe to say that it fixes the issue. So at the end of the day (or earlier if I get a retry page fault) I'll do the procedure you mention to use firmware 1.197 and only overwrite the picasso* files to confirm if those are the ones that need to be changed. I don't know much about GPUs, but from looking at Wikipedia¹ I think my model is a "Vega 10". Should I overwrite the vega10* files as well? ¹ https://en.wikipedia.org/wiki/Radeon_RX_Vega_series#Picasso_(2019)_2 > Then please download the picasso firmware files from here: > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-> firmware.git/tree/amdgpu > > Use the "plain" link next to each file to download the file. Overwrite > the files in /lib/firmware/admgpu with these files, reboot, and see if > you continue to have problems. > > ** Changed in: linux-firmware (Ubuntu) >Importance: Undecided => High Thanks! > > ** Changed in: linux-firmware (Ubuntu) >Status: New => Incomplete > > ** Changed in: linux-firmware (Ubuntu) > Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in linux-firmware package in Ubuntu: Incomplete Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA
[Kernel-packages] [Bug 1927738] [NEW] Bluetooth doesn't work in Ubuntu 21.04
You have been subscribed to a public bug: Bluetooth doesn't work in Ubuntu 21.04 after update ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri May 7 16:32:21 2021 InstallationDate: Installed on 2020-04-08 (394 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to hirsute on 2021-04-15 (22 days ago) VarLogDistupgradeTermlog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade hirsute -- Bluetooth doesn't work in Ubuntu 21.04 https://bugs.launchpad.net/bugs/1927738 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1926999] Re: Hirsute update: v5.11.16 upstream stable release
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1926999
Title:
Hirsute update: v5.11.16 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Hirsute:
Fix Committed
Status in linux-aws source package in Hirsute:
New
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.11.16 upstream stable release
from git://git.kernel.org/
AMD_SFH: Removed unused activecontrolstatus member from the amd_mp2_dev struct
AMD_SFH: Add sensor_mask module parameter
AMD_SFH: Add DMI quirk table for BIOS-es which don't set the activestatus bits
mtd: rawnand: mtk: Fix WAITRDY break condition and timeout
Input: nspire-keypad - enable interrupts only when opened
gpio: sysfs: Obey valid_mask
dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback
dmaengine: idxd: fix delta_rec and crc size field for completion record
dmaengine: idxd: fix opcap sysfs attribute output
dmaengine: idxd: fix wq size store permission state
dmaengine: dw: Make it dependent to HAS_IOMEM
dmaengine: Fix a double free in dma_async_device_register
dmaengine: plx_dma: add a missing put_device() on error path
dmaengine: idxd: clear MSIX permission entry on shutdown
dmaengine: idxd: fix wq cleanup of WQCFG registers
ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
remoteproc: pru: Fix loading of GNU Binutils ELF
lockdep: Add a missing initialization hint to the "INFO: Trying to register
non-static key" message
arc: kernel: Return -EFAULT if copy_to_user() fails
iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
xfrm: BEET mode doesn't support fragments for inner packets
ASoC: max98373: Changed amp shutdown register as volatile
ASoC: max98373: Added 30ms turn on/off time delay
net: axienet: allow setups without MDIO
gpu/xen: Fix a use after free in xen_drm_drv_init
bpf: Take module reference for trampoline in module
neighbour: Disregard DEAD dst in neigh_update
powerpc/signal32: Fix Oops on sigreturn with unmapped VDSO
ARM: keystone: fix integer overflow warning
ARM: omap1: fix building with clang IAS
drm/msm: Fix a5xx/a6xx timestamps
ASoC: fsl_esai: Fix TDM slot setup for I2S mode
scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
iwlwifi: add support for Qu with AX201 device
net: ieee802154: stop dump llsec keys for monitors
net: ieee802154: forbid monitor for add llsec key
net: ieee802154: forbid monitor for del llsec key
net: ieee802154: stop dump llsec devs for monitors
net: ieee802154: forbid monitor for add llsec dev
net: ieee802154: forbid monitor for del llsec dev
net: ieee802154: stop dump llsec devkeys for monitors
net: ieee802154: forbid monitor for add llsec devkey
net: ieee802154: forbid monitor for del llsec devkey
net: ieee802154: stop dump llsec seclevels for monitors
net: ieee802154: forbid monitor for add llsec seclevel
pcnet32: Use pci_resource_len to validate PCI resource
drm/amd/display: Add missing mask for DCN3
mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
virt_wifi: Return micros for BSS TSF values
lib: fix kconfig dependency on ARCH_WANT_FRAME_POINTERS
net/sctp: fix race condition in sctp_destroy_sock
Input: s6sy761 - fix coordinate read bit shift
Input: i8042 - fix Pegatron C15B ID entry
HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
dm verity fec: fix misaligned RS roots IO
readdir: make sure to verify directory entry for legacy interfaces too
drm/i915: Don't zero out the Y plane's watermarks
arm64: fix inline asm in load_unaligned_zeropad()
arm64: mte: Ensure TIF_MTE_ASYNC_FAULT is set atomically
UBUNTU: [Config] updateconfigs for AS_HAS_LSE_ATOMICS
arm64: alternatives: Move length validation in alternative_{insn, endif}
vfio/pci: Add missing range check in vfio_pci_mmap
riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
scsi: libsas: Reset num_scatter if libata marks qc as NODATA
drm/vmwgfx: Make sure we unpin no longer needed buffers
ixgbe: Fix NULL pointer dereference in ethtool loopback test
ixgbe: fix unbalanced device enable/disable in
[Kernel-packages] [Bug 1928352] Re: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
EIO on get_variable() is a EFI_DEVICE_ERROR on the EFI call. EFI_DEVICE_ERROR according to the UEFI EDK2 sources is "The variable could not be retrieved due to a hardware error." -- 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/1928352 Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Status in shim-signed package in Ubuntu: Confirmed Bug description: The installer crashed at the very end with a warning that my computer might fail to boot. It booted alright but after logging in I get a pop-up to signal that shim-signed has failed to install. Something to do with my system (EFI) running in insecure mode? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: shim-signed 1.47+15.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: pass Date: Thu May 13 16:54:46 2021 EFITables: mei 13 17:05:50 Selena kernel: efi: EFI v2.10 by American Megatrends mei 13 17:05:50 Selena kernel: efi: ACPI=0xba80b000 ACPI 2.0=0xba80b000 SMBIOS=0xf04c0 MOKvar=0xae8a2000 mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-13 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SecureBoot: 6 0 0 0 0 SourcePackage: shim-signed Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928352/+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 1928352] Re: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
The log shows: Installing for x86_64-efi platform. grub-install: warning: Cannot read EFI Boot* variables. grub-install: warning: read_file: could not read from file: Input/output error. grub-install: warning: vars_get_variable: read_file(/sys/firmware/efi/vars/Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var) failed: Input/output error. grub-install: warning: efi_get_variable: ops->get_variable failed: Input/output error. grub-install: error: failed to register the EFI boot entry: Input/output error. This is not about running in insecure mode, it's about the fact that you are on an EFI system but the /sys/firmware/efi mount point that the kernel uses to expose EFI nvram variables to the system is unusable. We have had a number of reports of such problems but have yet to isolate a cause. Opening a bug task on the kernel, since this may be a kernel filesystem bug. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** 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/1928352 Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Status in shim-signed package in Ubuntu: Confirmed Bug description: The installer crashed at the very end with a warning that my computer might fail to boot. It booted alright but after logging in I get a pop-up to signal that shim-signed has failed to install. Something to do with my system (EFI) running in insecure mode? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: shim-signed 1.47+15.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi CasperMD5CheckResult: pass Date: Thu May 13 16:54:46 2021 EFITables: mei 13 17:05:50 Selena kernel: efi: EFI v2.10 by American Megatrends mei 13 17:05:50 Selena kernel: efi: ACPI=0xba80b000 ACPI 2.0=0xba80b000 SMBIOS=0xf04c0 MOKvar=0xae8a2000 mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled mei 13 17:05:50 Selena kernel: secureboot: Secure boot disabled ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-05-13 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SecureBoot: 6 0 0 0 0 SourcePackage: shim-signed Title: package shim-signed 1.47+15.4-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928352/+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 1923162] Re: riscv64 images fail to boot in qemu
** Description changed: - When booting v5.11 based riscv unmatched image in qemu with uboot, it - fails to boot. + [Impact] - When booting v5.11 based riscv unmatched kernel+initrd directly, it - boots fine. + * u-boot may crash when attempting to boot extlinux.conf which + specifies fdtdir; the given u-boot config doesn't specify a dtb filename + to load; autodetection tries to make one up using $soc & $board + variables; and if one or both of them are not set (as it is the case for + qemu) it would crash. Fix this crash by doing validation / checking when + quering for $soc & $board variables in autodetectionn. - Somehow, it seems that u-boot fails to correctly load & start v5.11 - kernel. + [Test Plan] + + * Use qemu & uboot produced by the build that fixes this bug report + properly and attempt to boot hirsute's riscv64+unmatched image. + + * It should boot correctly without a crash / qemu backtrace. + + [Where problems could occur] + + * This patch is bein upstreamed. If one is using external uboot (i.e. + provided by some other vendor) it may still crash when trying to boot + Ubuntu's riscv64 rootfs or cloud image. + + [Other Info] + + * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html ** Changed in: u-boot (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Committed Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: New Status in u-boot-menu source package in Focal: Invalid Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: New Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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 1928394] Re: CONFIG_LATENCYTOP should be disabled
** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-raspi2 (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1928394
Title:
CONFIG_LATENCYTOP should be disabled
Status in linux package in Ubuntu:
Incomplete
Status in linux-raspi2 package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in linux-raspi2 source package in Bionic:
In Progress
Bug description:
SRU Justification
[Impact]
There were some recent changes on the main kernels to fix some syntax
issues with the annotations files (Propagate "Update annotations and
fix errors" to all derivatives), after I replicated the changes from
bionic/linux to bionic/linux-raspi2 I started getting this enforcement
error:
check-config: FAIL (y != n): CONFIG_LATENCYTOP policy<{'amd64-generic': 'n',
'amd64-lowlatency': 'y', 'arm64': 'n', 'armhf': 'n', 'i386': 'n', 'ppc64el':
'n', 's390x': 'n'}> mark
note
It seems we were supposed to have the same enforcement as the main kernel (=
n) but the raspi2 config has it actually enabled.
Looking at the url and the bug reference on the enforcement notes, it
seems it doesn't make much sense to keep it enabled for non-lowlatency
kernels.
@juerghaefliger confirmed we should disable this option:
Yes, it should be disabled. I did the same for hirsute earlier this year
after Seth fixed the master config annotations:
~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/hirsute - [no description]
If I remember correctly I made some other config changes due to Seth's
changes.
[Test Plan]
Install latencytop, try to run the tool.
[Where problems could occur]
Disabling this config removes information that userspace might depend
on.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928394/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Before we revert we should see if newer firmware fixes the issue, and make sure we are only changing the specific firmware files for your hardware. I think your hardware is the "Picasso" series. Can you try the following? If you are unsure about any of the following steps, let me know and I can provide you with test packages to install instead. Save all files matching /lib/firmware/amdgpu/picasso* from linux- firmware 1.190.5. Reinstall 1.197, then overwrite the picasso firmware files with the ones you saved. Reboot, and confirm that the issues you see with 1.197 are fixed. If they are not fixed, then there's no need to proceed as we haven't found the correct firmware files which are causing your issues. Then please download the picasso firmware files from here: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/amdgpu Use the "plain" link next to each file to download the file. Overwrite the files in /lib/firmware/admgpu with these files, reboot, and see if you continue to have problems. ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in linux-firmware package in Ubuntu: Incomplete Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+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
Re: [Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
Thank you for your information/times../ EH On Fri, May 14, 2021, 8:25 AM Dimitri John Ledkov < 1914...@bugs.launchpad.net> wrote: > sru-release comments: > > virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, > arm64) -> autopkgtest failures are a false negative. It only is built > and supported on amd64 > > sysdig/riscv64 - ftbfs is not a regression, never built on riscv64 in > focal > > zfs-linux/riscv64 - ftbfs is not a regression, never built on riscv64 in > focal > > iptables-netflow - needs 3 more days to age > > Thus everything is ready to be released to -updates & -security > > ** Changed in: acpi-call (Ubuntu) >Status: New => Fix Released > > ** Changed in: backport-iwlwifi-dkms (Ubuntu) >Status: New => Fix Released > > ** Changed in: zfs-linux (Ubuntu) >Status: New => Fix Released > > ** Changed in: virtualbox-hwe (Ubuntu) >Status: New => Fix Released > > ** Changed in: virtualbox (Ubuntu) >Status: New => Fix Released > > ** Changed in: v4l2loopback (Ubuntu) >Status: New => Fix Released > > ** Changed in: sysdig (Ubuntu) >Status: New => Fix Released > > ** Changed in: rtl8812au (Ubuntu) >Status: New => Fix Released > > ** Changed in: r8168 (Ubuntu) >Status: New => Fix Released > > ** Changed in: oss4 (Ubuntu) >Status: New => Fix Released > > ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) >Status: New => Fix Released > > ** Changed in: lttng-modules (Ubuntu) >Status: New => Fix Released > > ** Changed in: lime-forensics (Ubuntu) >Status: New => Fix Released > > ** Changed in: liblzf (Ubuntu) >Status: New => Fix Released > > ** Changed in: iptables-netflow (Ubuntu) >Status: New => Fix Released > > ** Changed in: gost-crypto (Ubuntu) >Status: New => Fix Released > > ** Changed in: evdi (Ubuntu) >Status: New => Fix Released > > ** Changed in: dm-writeboost (Ubuntu) >Status: New => Fix Released > > ** Changed in: dahdi-linux (Ubuntu) >Status: New => Fix Released > > ** Changed in: bcmwl (Ubuntu) >Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to apt in > Ubuntu. > Matching subscriptions: dragonhahney > https://bugs.launchpad.net/bugs/1914279 > > Title: > linux from security may force reboots without complete dkms modules > > Status in acpi-call package in Ubuntu: > Fix Released > Status in apt package in Ubuntu: > Invalid > Status in backport-iwlwifi-dkms package in Ubuntu: > Fix Released > Status in bcmwl package in Ubuntu: > Fix Released > Status in dahdi-linux package in Ubuntu: > Fix Released > Status in dkms package in Ubuntu: > Fix Released > Status in dm-writeboost package in Ubuntu: > Fix Released > Status in evdi package in Ubuntu: > Fix Released > Status in gost-crypto package in Ubuntu: > Fix Released > Status in iptables-netflow package in Ubuntu: > Fix Released > Status in liblzf package in Ubuntu: > Fix Released > Status in lime-forensics package in Ubuntu: > Fix Released > Status in linux package in Ubuntu: > Triaged > Status in linux-meta package in Ubuntu: > Triaged > Status in lttng-modules package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Fix Released > Status in openafs package in Ubuntu: > New > Status in oss4 package in Ubuntu: > Fix Released > Status in r8168 package in Ubuntu: > Fix Released > Status in rtl8812au package in Ubuntu: > Fix Released > Status in sysdig package in Ubuntu: > Fix Released > Status in unattended-upgrades package in Ubuntu: > Invalid > Status in update-manager package in Ubuntu: > Invalid > Status in v4l2loopback package in Ubuntu: > Fix Released > Status in virtualbox package in Ubuntu: > Fix Released > Status in virtualbox-hwe package in Ubuntu: > Fix Released > Status in zfs-linux package in Ubuntu: > Fix Released > Status in acpi-call source package in Focal: > Fix Committed > Status in backport-iwlwifi-dkms source package in Focal: > Fix Committed > Status in bcmwl source package in Focal: > Fix Committed > Status in dahdi-linux source package in Focal: > Fix Committed > Status in dm-writeboost source package in Focal: > Fix Committed > Status in evdi source package in Focal: > Fix Committed > Status in gost-crypto source package in Focal: > Fix Committed > Status in iptables-netflow source package in Focal: > Fix Committed > Status in liblzf source package in Focal: > Fix Committed > Status in lime-forensics source package in Focal: > Fix Committed > Status in lttng-modules source package in Focal: > Fix Committed > Status in nvidia-graphics-drivers-340 source package in Focal: > Fix Committed > Status in oss4 source package in Focal: > Fix Committed > Status in r8168 source package in Focal: > Fix Committed > Status in rtl8812au source package in Focal: > Fix Committed > Status in
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
** Changed in: u-boot (Ubuntu) Status: Fix Released => New ** Changed in: u-boot (Ubuntu Hirsute) Status: Fix Released => Triaged ** Changed in: u-boot (Ubuntu Hirsute) Status: Triaged => New ** Changed in: u-boot (Ubuntu) Importance: Critical => Undecided ** Also affects: u-boot (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: u-boot-menu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-riscv (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-riscv (Ubuntu Focal) Status: New => Invalid ** Changed in: u-boot-menu (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: New Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: New Status in u-boot-menu source package in Focal: Invalid Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: New Status in u-boot-menu source package in Hirsute: Fix Released Bug description: When booting v5.11 based riscv unmatched image in qemu with uboot, it fails to boot. When booting v5.11 based riscv unmatched kernel+initrd directly, it boots fine. Somehow, it seems that u-boot fails to correctly load & start v5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+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 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34
I've made the same tests with mainline kernel '5.12.4-051204-generic #202105140931 SMP Fri May 14 09:35:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux' and the results are the same, i.e. sensors command stopping when reaching amd section and this error message showing in dmesg: [ 65.636330] [drm] PCIE GART of 256M enabled (table at 0x00F4). [ 67.104101] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 67.704167] [drm:dce110_edp_wait_for_hpd_ready [amdgpu]] *ERROR* dce110_edp_wait_for_hpd_ready: wait timed out! [ 67.735924] [drm] UVD and UVD ENC initialized successfully. [ 67.845908] [drm] VCE initialized successfully. [ 67.850738] amdgpu :01:00.0: [drm] Cannot find any crtc or sizes [ 68.144823] drm_dp_i2c_do_msg: 2 callbacks suppressed [ 68.241327] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 68.241388] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 68.893269] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 68.893321] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D So the problem is not Ubuntu related. -- 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/1910562 Title: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Status in lm-sensors package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel 5.8.0-34 the fan on my machine started switching on (for an instant) and off every 10 seconds even when idle with CPU at 48/50°C. Switching back to previous kernel solves temporary the problem, i.e. fans are always off with light desktop work. The new behavior is really annoying and I guess not healthy for the fans. I'm on latest Dell bios, with every other package updated. Di something in the thermal policies change between those two kernels? Is it possible to go back to previous behavior ? Thanks in advance for help Machine: Dell Precison 7540, intel i7-9750 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 17:14:54 2021 InstallationDate: Installed on 2020-05-06 (246 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 2370 F pulseaudio /dev/snd/controlC1: gabriele 2370 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (352 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Precision 7540 Package: lm-sensors 1:3.6.0-2ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=c39f518b-f5c9-47c5-8e7f-42d970d2dedb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 01/08/2021 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0XMC3F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd01/08/2021:br1.11:svnDellInc.:pnPrecision7540:pvr:rvnDellInc.:rn0XMC3F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7540 dmi.product.sku: 0926 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
sru-release comments: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, arm64) -> autopkgtest failures are a false negative. It only is built and supported on amd64 sysdig/riscv64 - ftbfs is not a regression, never built on riscv64 in focal zfs-linux/riscv64 - ftbfs is not a regression, never built on riscv64 in focal iptables-netflow - needs 3 more days to age Thus everything is ready to be released to -updates & -security ** Changed in: acpi-call (Ubuntu) Status: New => Fix Released ** Changed in: backport-iwlwifi-dkms (Ubuntu) Status: New => Fix Released ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released ** Changed in: virtualbox (Ubuntu) Status: New => Fix Released ** Changed in: v4l2loopback (Ubuntu) Status: New => Fix Released ** Changed in: sysdig (Ubuntu) Status: New => Fix Released ** Changed in: rtl8812au (Ubuntu) Status: New => Fix Released ** Changed in: r8168 (Ubuntu) Status: New => Fix Released ** Changed in: oss4 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Fix Released ** Changed in: lttng-modules (Ubuntu) Status: New => Fix Released ** Changed in: lime-forensics (Ubuntu) Status: New => Fix Released ** Changed in: liblzf (Ubuntu) Status: New => Fix Released ** Changed in: iptables-netflow (Ubuntu) Status: New => Fix Released ** Changed in: gost-crypto (Ubuntu) Status: New => Fix Released ** Changed in: evdi (Ubuntu) Status: New => Fix Released ** Changed in: dm-writeboost (Ubuntu) Status: New => Fix Released ** Changed in: dahdi-linux (Ubuntu) Status: New => Fix Released ** Changed in: bcmwl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
[Kernel-packages] [Bug 1895132] Re: s390x broken with unknown syscall number on kernels < 5.8
Using verification steps from bug 1916485
ubuntu@test-s390x:~$ uname -a
Linux test-s390x 4.15.0-143-generic #147-Ubuntu SMP Wed Apr 14 16:16:31 UTC
2021 s390x s390x s390x GNU/Linux
ubuntu@test-s390x:~$ mkdir h
ubuntu@test-s390x:~$ cd h
ubuntu@test-s390x:~/h$ sudo tar xf ../hirsute-server-cloudimg-s390x-root.tar.xz
ubuntu@test-s390x:~/h$ sudo systemd-nspawn
Spawning container h on /home/ubuntu/h.
Press ^] three times within 1s to kill container.
root@h:~# ls -l /usr/bin/gpg
-rwxr-xr-x 1 root root 1361888 Feb 22 09:33 /usr/bin/gpg
root@h:~# test -x /usr/bin/gpg || echo "fail"
fail
ubuntu@test-s390x:~$ uname -a
Linux test-s390x 4.15.0-144-generic #148-Ubuntu SMP Sat May 8 02:31:39 UTC 2021
s390x s390x s390x GNU/Linux
ubuntu@test-s390x:~$ mkdir h
ubuntu@test-s390x:~$ cd h
ubuntu@test-s390x:~/h$ sudo tar xf ../hirsute-server-cloudimg-s390x-root.tar.xz
ubuntu@test-s390x:~/h$ sudo systemd-nspawn
Spawning container h on /home/ubuntu/h.
Press ^] three times within 1s to kill container.
root@h:~# ls -l /usr/bin/gpg
-rwxr-xr-x 1 root root 1361888 Feb 22 09:33 /usr/bin/gpg
root@h:~# test -x /usr/bin/gpg || echo "fail"
root@h:~#
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1895132
Title:
s390x broken with unknown syscall number on kernels < 5.8
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Focal:
Fix Released
Bug description:
SRU Justification
Note: I marked this as affecting bionic as well, as discovered in bug
1916485.
Impact: On kernels prior to 5.8 when a task is in traced state (due to
audit, ptrace, or seccomp) s390x and a syscall is issued that the
kernel doesn't know about s390x will not return ENOSYS in r2 but
instead will return the syscall number. This breaks userspace all over
the place. The following program compiled on s390x will output 500
instead of -ENOSYS:
root@test:~# cat test.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static inline int dummy_inline_asm(void)
{
register long r1 asm("r1") = 500;
register long r2 asm("r2") = -1;
register long r3 asm("r3") = -1;
register long r4 asm("r4") = -1;
register long r5 asm("r5") = -1;
register long __res_r2 asm("r2");
asm volatile(
"svc 0\n\t"
: "=d"(__res_r2)
: "d"(r1), "0"(r2), "d"(r3), "d"(r4), "d"(r5)
: "memory");
return (int) __res_r2;
}
static inline int dummy_syscall(void)
{
return syscall(500, -1, -1, -1, -1);
}
int main(int argc, char *argv[])
{
printf("Uhm: %d\n", dummy_inline_asm());
printf("Uhm: %d\n", dummy_syscall());
exit(EXIT_SUCCESS);
}
This breaks LXD on s390x currently completely as well as strace.
Fix: Backport
commit cd29fa798001075a554b978df3a64e6656c25794
Author: Sven Schnelle
Date: Fri Mar 6 13:18:31 2020 +0100
s390/ptrace: return -ENOSYS when invalid syscall is supplied
The current code returns the syscall number which an invalid
syscall number is supplied and tracing is enabled. This makes
the strace testsuite fail.
Signed-off-by: Sven Schnelle
Signed-off-by: Vasily Gorbik
which got released with 5.8. The commit missed to Cc stable and
although I've asked Sven to include it in stable I'm not sure when or
if it will show up there.
Regression Potential: Limited to s390x.
Test Case: The reproducer given above needs to output -ENOSYS instead
of 500.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1895132/+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 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
Ok, performed a review of the NEW packages of fabric-manager-{450,460}.
I'll accept them as is as none of those issues are blocking, but please
fix those before proceeding with the SRUs. The packaging is in overall a
bit on the 'weird' side, but Nvidia pieces can get a bit hairy.
List of minor issues to fix:
- For fabric-manager-450 the Vcs-Browser field does not exist (looks like the
450 is not on available on github?). 460 seems to be there though.
- fabric-manager-450 has .install, .links and .triggers for the 460 packages.
These need to removed as they're just adding to the confusion.
- In both packages in debian/rules there's a override_dh_auto_build: that does
`rm -f lib*.so` - that seems like some leftover that needs cleanup.
- In debian/rules the BRANCH variable is set to 999 instead of 450 and 460
respectively. I think this should be kept up to date with the packages that are
being considered.
Accepting o/
** Also affects: fabric-manager-450 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fabric-manager-460 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1925522
Title:
Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
Status in fabric-manager-450 package in Ubuntu:
New
Status in fabric-manager-460 package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
In Progress
Status in fabric-manager-450 source package in Bionic:
New
Status in fabric-manager-460 source package in Bionic:
New
Status in linux-restricted-modules source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Committed
Status in nvidia-graphics-drivers-465 source package in Bionic:
Fix Committed
Status in nvidia-settings source package in Bionic:
Fix Committed
Status in fabric-manager-450 source package in Focal:
New
Status in fabric-manager-460 source package in Focal:
New
Status in linux-restricted-modules source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Committed
Status in nvidia-graphics-drivers-465 source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Committed
Status in fabric-manager-450 source package in Groovy:
New
Status in fabric-manager-460 source package in Groovy:
New
Status in linux-restricted-modules source package in Groovy:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Committed
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Committed
Status in nvidia-graphics-drivers-465 source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Committed
Status in fabric-manager-450 source package in Hirsute:
New
Status in fabric-manager-460 source package in Hirsute:
New
Status in linux-restricted-modules source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Committed
Status in nvidia-graphics-drivers-465 source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Committed
Bug description:
Introduce the new NVIDIA 465 driver series, fabric-manager and
libnvidia-nscq. Also migrate the UDA 450 series to the 460 series.
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the changelog entry below for a full list of changes and bugs.
[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/NVidiaUpdates
Certification test suite must pass on a range of hardware:
https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu
The QA team that executed the tests will be in charge of attaching the
artifacts and console output of the appropriate run to the bug. nVidia
maintainers team members will not mark ‘verification-done’ until this
has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned system level tests are attached to this bug.
[Discussion]
[Changelog]
== 450-server ==
* New upstream release (LP: #1925522).
[Kernel-packages] [Bug 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
fine on hirsute with linux-image-5.11.0-18-generic_5.11.0-18.19_amd64 ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed-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/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it
I'm seeing this annoying issue with Ubuntu 20.04 running the linux- oem-20.04b kernel (currently 5.10.0-1026-oem). The above workaround fixes it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801642 Title: Bluetooth mouse sleeps after 5 seconds of inactivity, but btusb.enable_autosuspend=0 fixes it Status in linux package in Ubuntu: Confirmed Bug description: I'm having bluetooth mouse lag issue. After leaving it stationary for 5 seconds, I have to move it for 2 seconds before the pointer starts moving. I recently upgraded to Cosmic 3 days ago (from Bionic). There was no issue in the first 3 days, including after suspend/restart/shutdown. This issue only appears starting today. I tried: 1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 'Failed to stop discovery: org.bluez.Error.Failed'. 2. modprobe -r btusb, then modprobe it again. 3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll' 4. Disabling wifi. $ apt-cache policy bluez 5.50-0ubuntu1 $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth 4.18.0-10-generic #11 02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 73) Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460] Kernel driver in use: iwlwifi 03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:05f9] Kernel driver in use: r8169 Kernel modules: r8169 Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 17e9:4301 DisplayLink Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. Bus 002 Device 006: ID 8087:07dc Intel Corp. Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL (B) [Dell Laser Mouse] Bus 002 Device 118: ID 0853:0132 Topre Corporation Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [ 287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31 bluetooth 548864 33 btrtl,btintel,btbcm,bnep,btusb,rfcomm ecdh_generic 24576 2 bluetooth ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: MATE Date: Mon Nov 5 13:40:01 2018 InstallationDate: Installed on 2018-07-08 (119 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7537 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 SourcePackage: bluez UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.product.sku: Inspiron 7537 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: FC:F8:AE:33:C7:31 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING RX bytes:2380 acl:32 sco:0 events:208 errors:0 TX bytes:28560 acl:29 sco:0 commands:170 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801642/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
fine on groovy linux-image-5.8.0-54-generic ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928198] Re: Failed to start Suspend: A start job for unit systemd-suspend.service has failed.
@kaihengfeng How do I do this? What is the command where I use this kernel parameter? And do I have to restart the distro after applying that command for the new dmesg log? A noob-friendly explanation would have been nice. -- 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/1928198 Title: Failed to start Suspend: A start job for unit systemd-suspend.service has failed. Status in linux package in Ubuntu: Confirmed Bug description: For some reason, my distro (Ubuntu 21.04) doesn't suspend properly. I want to solve this problem it is fixable because it will save a lot of battery. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 16:00:17 2021 InstallationDate: Installed on 2020-02-16 (451 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.11.0-17-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-04-24 (17 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+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 1857257] Re: linux-image-5.0.0-35-generic breaks checkpointing of container
fine on focal linux-image-5.4.0-74-generic_5.4.0-74.83_amd64 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857257 Title: linux-image-5.0.0-35-generic breaks checkpointing of container Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: Trying to checkpoint a container (docker/podman) on 18.04 fails starting with linux-image-5.0.0-35-generic. We (CRIU upstream) see this in Travis starting a few weeks ago. Manually testing it locally shows that linux-image-5.0.0-32-generic still works and linux- image-5.0.0-35-generic does not longer work. It seems to be overlayfs related, at least that is what we believe. The CRIU error message we see is: (00.170944) Error (criu/files-reg.c:1277): Can't lookup mount=410 for fd=-3 path=/bin/busybox (00.170987) Error (criu/cr-dump.c:1246): Collect mappings (pid: 1637) failed with -1 We have not seen this only in Travis, but also multiple CRIU users reported that bug already. Currently we have to tell them to downgrade the kernel. I also able to reproduce it with linux-image-5.3.0-24-generic. Staying on the 4.18.0 kernel series does not show this error. 4.18.0-25-generic works without problems. See also https://github.com/checkpoint-restore/criu/issues/860 One of the possible explanations from our side include: "Looks like we have the same as for st_dev now with mnt_id, that is bad, because we can't find on which mount to open the file if kernel hides these information from us." Running on the upstream 5.5.0-rc1 kernel does not show this error. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 7 18:52 seq crw-rw 1 root audio 116, 33 Jan 7 18:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 19.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=PARTUUID=5b57f3f9-086a-4a7d-ae78-efdee8842586 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: eoan uec-images Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.family: DigitalOcean_Droplet dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857257/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923557] Re: CirrusLogic: The default input volume is "0%"
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1923557
Title:
CirrusLogic: The default input volume is "0%"
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, DMIC volume default
value in kernel driver is 0, which follows no audio sound will be played
during installation and OOBE until being explicitly configured again via
GNOME Settings GUI or other methods.
[Fix]
Commit 0e853a9c3937 ("ALSA: hda/cirrus: Set Initial DMIC volume for
Bullseye to -26 dB") currently landed in upstream tiwai/sound.git is
required this address this issue. It's also being proposed to v5.13
merge window.
[Test Case]
Try to remove all the user space settings caches and reboot. The
detailed steps are:
$ sudo systemctl disable alsa-restore.service
$ sudo rm /var/lib/alsa/asound.state
$ sudo reboot
$ amixer sget 'Internal Mic',0
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 0 [0%] [-51.00dB] [off]
Front Right: Capture 0 [0%] [-51.00dB] [off]
Expect 40% in the front left/right capture volumes.
[Where problems could occur]
This gives the default value of Cirrus CS8409 audio codec capture volume
on Bullseye only. Cannot come out with any side effect it may produce so
far.
[Other Info]
By SRU we skipped a couple of refactoring changes in asound upstream
tree, so additional changes to the original patch are required to
backport.
== original bug description ==
The initial default input volume right after Ubuntu installation is
set to 0% while 16% is expected.
$ amixer
...
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 0 [0%] [-51.00dB] [off]
Front Right: Capture 0 [0%] [-51.00dB] [off]
Simple mixer control 'Internal Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 2
Front Left: 0 [0%] [0.00dB]
Front Right: 0 [0%] [0.00dB]
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1523 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X90
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-04-13 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd.
FingerPrint
Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 3500
Package: linux-oem-5.10
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem
root=UUID=c666f936-5b87-4cbd-bde6-21fa93b89036 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1020-oem N/A
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+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 1925415] Re: Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925415 Title: Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Mute/micmute LEDs don't work. In addition, the internal mic can only capture lots of noises. [Fix] Use Realtek specific coef to enable LEDs and limit mic boost on the platform. [Test] With the patch applied, the both LEDs start to work, and audio recording becomes crystal clear. [Where problems could occur] It's a trivial change to a brand new device, so no existing device is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925415/+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 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925685 Title: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-hwe-5.8 source package in Bionic: Confirmed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: Confirmed Status in linux-hwe-5.8 source package in Groovy: Confirmed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Confirmed Status in linux-hwe-5.8 source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-hwe-5.8 source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: Filing this with my Kubuntu Focus (kfocus.org) OEM hat on: [Impact] We are having screen flickering and glitching issues with some of our hardware upon wake from suspend. We have worked with our ODM to figure out a fix for this. They had reported there were no issues when running Windows on the same hardware. As such, we tested, and found that this issue first began as a regression in kernel 5.0 (did not exist in kernel 4.18 per our tests). We identified a patch via https://gitlab.freedesktop.org/drm/intel/-/issues/272 in which this has been solved. Per our testing by recompiling the kernel, this completely fixes our hardware issue. As of 4-21, this fix has been merged into the Linux kernel per Timo Aaltonen, and will be included in the kernel in the 5.13 release. Our hardware ships with Kubuntu 20.04 LTS, which means the 5.13 kernel will not see these machines, at least in the forseeable future. As such, we request that this patch be added to the kernel. Per our testing, this patch is straightforward to add and works flawlessly. The patch that works best was created in collaboration with Kai-Heng Feng, is attached to this bug report, and can be found here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925685/+attachment/5491421/+files /drm-intel-both.patch Until this is fixed, we have a whole batch of hardware we cannot sell, so, as an OEM, this is a high priority. [Test Plan] * Install Kubuntu on an affected Kubuntu Focus M2 computer (not in the hands of customers at this time) * Notice screen glitching/flickering after wake-from-suspend. * Install kernel compiled with the attached patch. Boot from patched kernel. * Suspend laptop, resume. No glitches. [Where problems could occur] * Although this solves the problem for us and has been confirmed to work with the Intel developers that developed this patch, it could cause another display type to have problems. This is unlikely as it has been vetted by Intel and by the mainline Linux kernel developers. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925685/+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 1927067] Re: Add s2idle support on AMD Renoir and Cezanne
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927067 Title: Add s2idle support on AMD Renoir and Cezanne Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] S2idle doesn't work on AMD Renoir and Cezanne. [Fix] Backport AMD PMC driver and pull many new patches let AMDGPU support s2idle. [Test] Suspend the laptop and the system freezes. With the patch applied, suspend works but with some caveats: 1) Keyboard sometimes can't wake up the laptop. 2) Touchpad sometimes can wake up the laptop. 3) RTC can't wake up the laptop. (Hardware Limitation) [Where problems could occur] Most changes are limited to logic of suspend/resume, and specific to Renoir GFX. However, there are some refactoring patches may cause unintended results, so AMDGPU may break for sleep/hibernation/runtime suspend on non-Renoir GFXs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927067/+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 1926579] Re: On TGL platforms screen shows garbage when browsing website by scrolling mouse
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926579 Title: On TGL platforms screen shows garbage when browsing website by scrolling mouse Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] On Dell TGL platforms screen shows garbage when browsing website by scrolling mouse [Fix] This patch fixes the issue https://patchwork.freedesktop.org/patch/430153/?series=89348=1 [Test] Verified on Dell TGL-H platforms. [Where problems could occur] It disable PSR2 on A0 and B0 TGL-H platforms, should introduce no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926579/+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 1926792] Re: Fix kernel panic at boot on dual GFX systems
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926792 Title: Fix kernel panic at boot on dual GFX systems Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On dual GFX systems, if amdgpu fails to probe a device, vgaarb for another GFX triggers a NULL pointer dereference and freeze the system. [Fix] Defer VGA client registering so resources are handled properly when amdgpu probe fails. [Test] With the patch applied, no more kernel panic when vgaarb is changing the VGA mode. [Where problems could occur] VGA clients won't take effect until a successful probe, so unless there is very subtle bug in vgaarb or vgaswitcheroo, it's very unlikely to introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926792/+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 1928028] Re: io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 (timeouted / SIGKILL)
https://lists.ubuntu.com/archives/kernel-team/2021-May/120236.html
Sent fix to mailing list.
** Description changed:
- io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 5.6.0-1056.60 on
- host spitfire
+ [Impact]
+ When using async io_uring OP_SENDMSG, a copy to kernel address 0 might be
attempted, leading to a kernel WARN/BUG and an uninterruptible process.
+
+ [Fix]
+ Partial backport of dd821e0c95a64b5923a0c57f07d3f7563553e756 ("io_uring: fix
missing msg_name assignment"). The recvmsg side does not seed to set msg_name,
as it copies from a local/stack kernel address (at sys_recvmsg) to a uaddr
parameter, which is given when doing the copy_msghdr operation.
+
+ [Test case]
+ LTP io_uring02 was run, and an equivalent recvmsg test was done too. A
successfull sendmsg test (without the chroot at io_uring02 test) was also
tested.
+
+ [Potential regressions]
+ io_uring sendmsg/recvmsg paths could fail, potentially leading to a system
crash or even a security vulnerability.
+
+
+ ---
+
+
+ io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 5.6.0-1056.60 on host
spitfire
This test isn't found to be ran on previous versions on F/oem-5.6, so
would not consider this to be a regression.
-
26934.05/07 14:42:48 DEBUG| utils:0153| [stdout] tag=io_uring01
stime=1620398217 dur=0 exit=exited stat=0 core=no cu=0 cs=0
26935.05/07 14:42:48 DEBUG| utils:0153| [stdout] startup='Fri May 7
14:36:57 2021'
26936.05/07 14:42:48 DEBUG| utils:0153| [stdout] tst_test.c:1311:
TINFO: Timeout per run is 0h 05m 00s
26937.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26938.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26939.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26940.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26941.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26942.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26943.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26944.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26945.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26946.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26947.05/07 14:42:48 DEBUG| utils:0153| [stdout] Test timeouted,
sending SIGKILL!
26948.05/07 14:42:48 DEBUG| utils:0153| [stdout] Cannot kill test
processes!
26949.05/07 14:42:48 DEBUG| utils:0153| [stdout] Congratulation,
likely test hit a kernel bug.
26950.05/07 14:42:48 DEBUG| utils:0153| [stdout] Exitting uncleanly...
26951.05/07 14:42:48 DEBUG| utils:0153| [stdout] tag=io_uring02
stime=1620398217 dur=350 exit=exited stat=1 core=no cu=0 cs=0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1928028
Title:
io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 (timeouted /
SIGKILL)
Status in ubuntu-kernel-tests:
New
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux-oem-5.6 source package in Focal:
In Progress
Bug description:
[Impact]
When using async io_uring OP_SENDMSG, a copy to kernel address 0 might be
attempted, leading to a kernel WARN/BUG and an uninterruptible process.
[Fix]
Partial backport of dd821e0c95a64b5923a0c57f07d3f7563553e756 ("io_uring: fix
missing msg_name assignment"). The recvmsg side does not seed to set msg_name,
as it copies from a local/stack kernel address (at sys_recvmsg) to a uaddr
parameter, which is given when doing the copy_msghdr operation.
[Test case]
LTP io_uring02 was run, and an equivalent recvmsg test was done too. A
successfull sendmsg test (without the chroot at io_uring02 test) was also
tested.
[Potential regressions]
io_uring sendmsg/recvmsg paths could fail, potentially leading to a system
crash or even a security vulnerability.
---
io_uring02 from ubuntu_ltp_syscalls fails on F/oem-5.6 5.6.0-1056.60 on host
spitfire
This test isn't found to be ran on previous versions on F/oem-5.6, so
would not consider this to be a regression.
26934.05/07 14:42:48 DEBUG| utils:0153| [stdout] tag=io_uring01
stime=1620398217 dur=0 exit=exited stat=0 core=no cu=0 cs=0
26935.05/07 14:42:48 DEBUG| utils:0153| [stdout] startup='Fri May 7
14:36:57 2021'
26936.05/07 14:42:48 DEBUG| utils:0153| [stdout] tst_test.c:1311:
TINFO: Timeout per run is 0h 05m 00s
26937.05/07 14:42:48 DEBUG| utils:0153| [stdout]
[Kernel-packages] [Bug 1926564] Re: An recursive locking in igb and igc drivers
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926564 Title: An recursive locking in igb and igc drivers Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in __dev_open() it calls pm_runtime_resume() to resume devices, and in some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() again. That leads to a recursive lock. This issue is introduced by below commit since v5.9-rc1 bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] This commit currently is still under discussion fixes the issue. https://lkml.org/lkml/2021/4/20/123 [Test] Verified on Dell Precision workstations. [Where problems could occur] The patch is pretty straightforward, no problems could occur by this change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926564/+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 1912057] Re: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA
@Koba, Sorry, but I do not know what "test-by signature" is. -- 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/1912057 Title: Power consumption higher after suspend - Ubuntu 20.10 on Asus UX425JA Status in linux package in Ubuntu: Incomplete Bug description: After boot the idle power consumption is around 2.3 W but after suspend it is 4.7 W. The measurement is 5-10 min after boot/resume - looking at "top" to see system was idle. This is consistent - I have tried more that 10 times. BIOS is updated to latest version. I have checked power consumption with external meter - and confirmed that it is higher. I have attached output of: sudo powertop -t 60 -r --html=before.html (and after) I have noticed that Package C-state 6 is reached before suspend but not after. I expect that idle power consumption after suspend should be the same as before. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-38-generic 5.8.0-38.43 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hjh1448 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 15:49:32 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2021-01-03 (13 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425JA_UX425JA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=6296ce1c-eec8-4302-beb1-b4a228780075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425JA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425JA 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.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425JA.304:bd10/28/2020:br5.14:efr3.4:svnASUSTeKCOMPUTERINC.:pnZenBookUX425JA_UX425JA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425JA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425JA_UX425JA 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/1912057/+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 1877088] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted linux-base into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691
[Kernel-packages] [Bug 1877088] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted linux-base into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Released Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root
[Kernel-packages] [Bug 1927759] Re: Reboot triggers bus fatal error on Dell servers with BCM57XX network card
Do you know which commit fixes the issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927759 Title: Reboot triggers bus fatal error on Dell servers with BCM57XX network card Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 Kernel: 5.4.0-72-generic Problem Description: When rebooting the system, a bus fatal error is generated by the system hardware pointing to the BCM57XX network card. Upon reboot the error is cleared. Dell notes this in their release notes for Ubuntu 20.04 LTS - https://www.dell.com/support/manuals/en-us/ubuntu- server/ubuntu_20.04_rn_pub/A-bus-fatal-error-is-detected-on-BCM57XX- card?guid=guid-5094de74-f8fc-49ee-b8c1-47a44e4855e3=en-us I manually installed the latest mainline kernel (5.4.116-0504116.202105021035) and the error does not occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927759/+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 1924207] Re: [SRU][F:OEM-5.10/G/H] add realtek 8852 bluetooth support
** Tags removed: verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done-groovy verification-done-hirsute
--
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/1924207
Title:
[SRU][F:OEM-5.10/G/H] add realtek 8852 bluetooth support
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-oem-5.10 package in Ubuntu:
New
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
SRU justification:
[Impact]
Realtek 8852A bluetooth can not work because of no support in 5.10- kernel.
[Fix]
Add realtek 8852 bluetooth ID in driver.
Chip firmware is in another SRU.
[Test]
Verified on hardware with bluetooth headset and file transfer, all good.
[Where problems could occur]
The bluetooth chip 8852A may fail to work.
It should be low risk for adding ID for specfic hardware chip.
Unstable kernel already got it, only for F/G/H.
Backport for commit 0d484db60f ("Bluetooth: btusb: btrtl: Add support for
RTL8852A")
Because commit 6f9ff24645f ("Bluetooth: btrtl: Refine the ic_id_table for
clearer and more regular") changes the macro of IC_INFO, use the old way to add
the IDs for 8852A, no function changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1924207/+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 1927768] Re: No Bluetooth device found
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Summary changed: - No Bluetooth device found + No Bluetooth device found (Ralink RT3290) -- 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/1927768 Title: No Bluetooth device found (Ralink RT3290) Status in linux package in Ubuntu: Confirmed Bug description: My laptop HP Probook 450 g0 has a bluetooth device. But my Ubuntu 20.04 can't find this device. I tried dmesg | grep -i blue -> No output I know my laptop has bluetooth device for sure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-72-generic 5.4.0-72.80 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vivek 3179 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 7 22:07:40 2021 HibernationDevice: RESUME=UUID=91721efb-c835-42a1-a739-b90f5b9e1c5d InstallationDate: Installed on 2017-05-22 (1445 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP ProBook 450 G0 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic root=UUID=c3fba244-e5d3-42d6-ab29-cbc5d705c6e9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-72-generic N/A linux-backports-modules-5.4.0-72-generic N/A linux-firmware1.187.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRF Ver. F.63 dmi.board.name: 1949 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 90.0F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRFVer.F.63:bd06/03/2016:svnHewlett-Packard:pnHPProBook450G0:pvrA2018CD200:rvnHewlett-Packard:rn1949:rvrKBCVersion90.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G0 dmi.product.sku: F9S12PA#ACJ dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927768/+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 1927827] Re: Error launching cheese: Native Windows taller than 65535 pixels are not supported
** Package changed: linux (Ubuntu) => cheese (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/1927827 Title: Error launching cheese: Native Windows taller than 65535 pixels are not supported Status in cheese package in Ubuntu: Incomplete Bug description: Attempting to run cheese on a HDPI display in Wayland results in the following errors: (cheese:9303): Gdk-CRITICAL **: 10:29:11.221: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed (cheese:9303): Gdk-WARNING **: 10:29:11.265: Native Windows taller than 65535 pixels are not supported When this error happens, the cheese window does not open. Sometimes the "Native Windows ... not supported" does not occur, the cheese window does open. However, the photo area is black. I can work around this problem by changing the "Photo resolution" in preferences to a different value, and then changing it back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: cheese 3.38.0-3 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Ubuntu-Blue:ubuntu:GNOME Date: Sat May 8 10:32:03 2021 InstallationDate: Installed on 2021-04-28 (10 days ago) InstallationMedia: Ubuntu 21.04.0 2021.04.27 amd64 "Custom Hirsute Hippo" (20210427) MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: cheese3.38.0-3 cheese-common 3.38.0-3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1927827/+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 1803692] Re: bionic 4.15 nvme regression from trusty 4.4 with two identical devices
Please file a new bug if it's a different device. -- 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/1803692 Title: bionic 4.15 nvme regression from trusty 4.4 with two identical devices Status in linux package in Ubuntu: Fix Released Bug description: I have a system containing two identical nvme devices. When booting a trusty PXE image with kernel 4.4.0-38-generic both devices are detected and available: # nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x8086 ssvid : 0x8086 sn : BTHH82250N1X1P0E mn : INTEL SSDPEKKF010T8L fr : L08P ... # nvme id-ctrl /dev/nvme1 NVME Identify Controller: vid : 0x8086 ssvid : 0x8086 sn : BTHH82250N261P0E mn : INTEL SSDPEKKF010T8L fr : L08P ... # dmesg | grep nvme [5.106516] nvme0n1: p1 p2 p3 p4 [5.106615] nvme1n1: p1 p2 After booting a bionic PXE image based on 4.15.0-38-generic only the first nvme device is enabled, the second is detected but disabled as both devices have the same nqn: nvme nvme1: ignoring ctrl due to duplicate subnqn (nqn.2017-12.org.nvmeexpress:uuid:----). nvme nvme1: Removing after probe failure status: -22 The nqn string is found in the device firmware rather than being generated by Linux but there does not seem to be an operation in nvme-cli to change this. (It is also questionable if the device firmware value is correct according to section 7.9 of https://nvmexpress.org/wp-content/uploads/NVM-Express-1_3a-20171024_ratified.pdf. My reading of the specification is that the string should start nqn.2014-08.org.nvmeexpress:uuid: with a random UUID, and I assume a random UUID per device.) The Windows 10 installation provided on the system did not have any problems operating with both devices. Looking at the kernel nvme driver history suggests that in 4.4 it didn't care or validate the nqn but now it does there is a problem. Our typical installation is a zpool mirror across two devices and this is preventing us moving from trusty to bionic. This is a report of a similar issue: https://ask.fedoraproject.org/en/question/128422/one-of-two- identical-m2-nvme-drives-disabling-due-to-same-nqn/ It may be worth noting that if the nvme device does not provide an nqn then it seems one is generated based on the device serial number so a system with two Samsung MZVLB256HAHQ devices works fine. --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 3440 F pulseaudio CasperVersion: 1.340.2 CurrentDmesg: [ 151.172010] init: plymouth-stop pre-start process (4137) terminated with status 1 DistroRelease: Ubuntu 14.04 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. LiveMediaBuild: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 89e5:1001 Bus 001 Device 002: ID 17ef:6099 Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 30C8S04Y00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: us1931.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.10.150:/srv/boot/us1931 locale=en_GB.UTF-8 keyb=gb mirror/country=GB ip=dhcp zinstall= BOOTIF=01-30-9c-23-cb-2a-46 toram ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19 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.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.127.22 RfKill: Tags: trusty Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M1VKT1BA dmi.board.name: 3138 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305152508085 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1VKT1BA:bd08/17/2018:svnLENOVO:pn30C8S04Y00:pvrThinkStationP330:rvnLENOVO:rn3138:rvrSDK0J40697WIN3305152508085:cvnLENOVO:ct3:cvrNone: dmi.product.name: 30C8S04Y00 dmi.product.version: ThinkStation P330 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse:
[Kernel-packages] [Bug 1916945] Re: unable to Poweroff, it causes a restart instead
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc1/amd64/ -- 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/1916945 Title: unable to Poweroff, it causes a restart instead Status in linux package in Ubuntu: Confirmed Bug description: ubuntu 20.04 after jan/2021 update I am unable to poweroff (or shutdown) the laptop. it works fine if I poweroff in windows or when boot test 20.04 iso OS and power off HP probook 650 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-66-generic 5.4.0-66.74 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cvancrae 2080 F pulseaudio /dev/snd/controlC1: cvancrae 2080 F pulseaudio /dev/snd/pcmC1D0c: cvancrae 2080 F...m pulseaudio /dev/snd/pcmC1D0p: cvancrae 2080 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 25 20:15:49 2021 InstallationDate: Installed on 2018-07-30 (940 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 650 G1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=ef9f1472-488d-4d4d-94ae-545d7b6bf18e ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.40 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.asset.tag: 5CG4380HYL dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.40:bd07/13/2017:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10203:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ProBook 650 G1 dmi.product.sku: D9S35AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916945/+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 1927808] Re: rtw88_8821ce causes freeze
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc1/amd64/ There are several rtw88 fixes. -- 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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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 1925768] Re: Losing Wifi connection when USB-C Hub was plugged-in
Can you please boot, reproduce the issue, and attach just dmesg here? 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/1925768 Title: Losing Wifi connection when USB-C Hub was plugged-in Status in linux package in Ubuntu: Incomplete Bug description: Hello Ubuntu community, I have a problem with my system: when i connect my new USB-C hub to my Intel Nuc, my wifi-connection get disconnected and try to reconnect to my Wifi. The System cannot connect until i disconnect my USB-C hub. I also tries do disable the cable-connection-Ports without success. I always receive the message: could not connect to wifi... My OS: Ubuntu 20.04.2 LTS always up to date. Here is my Nuc: https://www.notebooksbilliger.de/intel+nuc+kit+nuc8i3bek2+388252?gclid=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB_id=Cj0KCQjw4ImEBhDFARIsAGOTMj_in7Zc6RBlqYMqtxrxwSDscYZsqcbmHjb9JM_ipyPl3cFjDsigaDsaAqOpEALw_wcB:G:s_kwcid=AL!8069!3!504856654760!!!g!626707857982!=6004 Link to my Adapter: https://www.amazon.de/1-Adapter-USB-C-Stromversorgung-RJ45-Gigabit- Ethernet-TF-Kartenleser-5-mm- Audiobuchse/dp/B08N424Y25/ref=sr_1_4?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91=1=usb+c+hub=1619169213=8-4 Best Regards Miro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925768/+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 1928198] Re: Failed to start Suspend: A start job for unit systemd-suspend.service has failed.
Can you please add kernel parameter "usbcore.dyndbg", suspend once, then attach dmesg here? 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/1928198 Title: Failed to start Suspend: A start job for unit systemd-suspend.service has failed. Status in linux package in Ubuntu: Confirmed Bug description: For some reason, my distro (Ubuntu 21.04) doesn't suspend properly. I want to solve this problem it is fixable because it will save a lot of battery. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 16:00:17 2021 InstallationDate: Installed on 2020-02-16 (451 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.11.0-17-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-04-24 (17 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+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 1927767] Re: All apps crashed in my X11 session, then terminal console crashed, reboot failed
** Package changed: linux (Ubuntu) => xorg-server (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/1927767 Title: All apps crashed in my X11 session, then terminal console crashed, reboot failed Status in xorg-server package in Ubuntu: Confirmed Bug description: The reboot failed with many services that could not stop. I think there may have been a crash in the network stack. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim4093 F pulseaudio /dev/snd/controlC2: tim4093 F pulseaudio /dev/snd/controlC0: tim4093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 8 03:07:12 2021 InstallationDate: Installed on 2020-11-22 (166 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE WIFI ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic root=/dev/mapper/vgubuntu-root ro quiet splash acpi_enforce_resources=lax mitigations=off crashkernel=192M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux StagingDrivers: ashmem_linux UpgradeStatus: Upgraded to hirsute on 2021-04-23 (14 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F33g dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33g:bd03/25/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITEWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITEWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1927767/+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 1926945] Re: Kernel 5.8.0.50 fails to boot
Should be fixed by -51 kernel. -- 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/1926945 Title: Kernel 5.8.0.50 fails to boot Status in linux package in Ubuntu: Incomplete Bug description: I have just installed XUbubtu 20.04 LTS on a system based on a Gigabyte J3455-D3H motherboard and a 120Gb SSD. Following installation the system will not boot and fails well before I can use it to report the bug via Apport. The last meesage displayed on screen is: [ 2.271553] hid-generic 0003:413C:2105.0001: input,hidraw0: USB HID v1.10 keyboard [Dell Dell USB Keyboard] on usb-:00:15.0.8.2/input0 Following this message the system doesn't get any further and simply hangs. I've tried leaving it for over an hour and no further messages appear. n.b. I do not think that the problem relates to the USB keyboard as it works fine on my other Ubuntu and Windows machines. I've also obviously tried several different keyboards (all fully working on my other machines) and have also unplugged the usb mouse temporarily so the only USB device attached is the keyboard. I also do not believe there is a problem with the hardware as a previous test install of Windows 10 worked fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926945/+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 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Groovy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926030
Title:
IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Groovy:
In Progress
Bug description:
[Impact]
Patch:
* media: rc: fix timeout handling after switch to microsecond durations
* media: rc: ite-cir: fix min_timeout calculation
Were applied to Groovy with our stable update process (bug 1918516)
User reported that IR Remote key press will be repeated for multiple times
with these patches applied.
Commit 528222d853f92 ("media: rc: harmonize infrared durations to
microseconds") that needs to be fixed by these two does not exist in
5.8 kernel. The patch author Matthias Reichl also state these are for
5.10 and onward.
[Fix]
Revert these two patches for groovy.
[Test]
Test kernels for G-5.8 / F-5.8 can be found here:
https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/
User Ted L confirmed that F-5.8 test kernel can fix the problem.
[Where problems could occur]
The chance to cause regression can be considered as low since the original
patch that need to be fix by these two patches does not exist in 5.8 at all.
[Original Bug Report]
I use an IR remote with the ir-keytable package. Everything was working fine
until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu
20.04.2. When any key is pressed on the remote, the key is repeated about 500
times. The kernel is now 5.8.0-50, and the problem persists.
Other users on the MythTV mailing list are reporting the issue, and it
appears that the problem is related to changes in the following files:
drivers/media/rc/ir-mce_kbd-decoder.c
drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c
drivers/media/rc/serial_ir.c
It has been reported that reverting the ir-mce_kbd-decoder.c and rc-
main.c files to the older versions fixes the problem.
/proc/version_signature > version.log:
Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
lspci -vnvn:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core
Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host
Bridge/DRAM Registers [1043:8694]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: skl_uncore
ir-keytable -V:
IR keytable control version 1.18.0
lsb_release -rd:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ted1020 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-19 (217 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lono wireless extensions.
enp3s0no wireless extensions.
enp0s31f6 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic
root=UUID=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18
RelatedPackageVersions:
linux-restricted-modules-5.8.0-50-generic N/A
linux-backports-modules-5.8.0-50-generic N/A
linux-firmware1.187.11
RfKill:
Tags: focal
Uname: Linux 5.8.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/05/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3405
dmi.board.asset.tag: Default string
dmi.board.name: H110T
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
[Kernel-packages] [Bug 1928138] Re: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached]
Do you know what's the offending commit? -- 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/1928138 Title: Flickering on built-in display (Intel Haswell graphics) since kernel v4.1 [bisected and workaround attached] Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Since kernel 4.1 laptop HP Elitebook Folio 1040 G1 (with Intel i5-4210U) has a pretty serious issue with flickering Symptoms: 1) If I leave mouse cursor for a few seconds, then start moving it, there's a slight flicker (like display brightness changes a bit). There's also some flickering even without user interactions. 2) On the top left corner sometimes appears artifacts. It's relatively easy to see with black window decorations on top of the screen. This one is showed at the attached video bellow 3) With kernel boot options drm.debug=0x1e log_buf_len=4M dmesg shows constant refresh rate changes (even if it's set to 40HZ) [ 29.977378] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 30.456537] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz [ 33.973392] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 40Hz [ 35.055923] [drm:intel_dp_set_drrs_state [i915]] eDP Refresh Rate set to : 60Hz nomodeset boot option eliminates flickering Turns out Display Refresh Rate Switching (DRRS) feature doesn't work correctly here. It was implemented on kernels 4.0...4.1 but on a particular machine flickering started with 4.1. As a workaround I'm attaching a patch which disables DRRS by default and adds module parameter "enable_drrs" to activate it. It's made for kernel 5.12 and should work for older versions as well (tested with 5.11). Until this issue is resolved, please consider adding parameter to disable DRRS. Windows has such option on Intel® Graphics Command Center. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1928138/+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 1924997] Re: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80%
verified version 5.11.0-18.19 from hirsute-proposed ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1924997 Title: CirrusLogic: Cracking noises appears in built-in speaker when output volume is set >80% Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] On a few CS8409 installed platforms, there are crack sounds when playing audio with output volume set to 100%. [Fix] The hardware is not capable of generating smooth audio output at the maximum volume that codec chip can be configured. A fix proposed to lower the maximum output volume using CS8409 equalizer. [Test Case] Use GNOME Settings / Sound Settings, set volume to 100%, play test audio for both right and left channels; set volume back to 70%, and repeat the same to compare to differences. While we don't have acoustic lab to perform precise measurements, the result was confirmed by partner. [Where problems could occur] This is to add a preconfigured, equalizer driver default values. This will introduce non-uniformed frequency response in comparison to that in the hardware preset. The net effect observable to general users is a lower maximum output volume. For those Hi-Fi users, audio output always takes additional calibration via extra software like ALSAEqual and/or hardware. [Other Info] By SRU we skipped a couple of refactoring changes in asound upstream tree, so additional changes to the original patch are required to backport. == original bug description == A cracking noises is noticed when doing audio playback from the built- in speaker when the volume is set >80. Upstream bug: https://github.com/CirrusLogic/product-support/issues/11 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1444 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X90 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-13 (6 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. FingerPrint Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3500 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem root=UUID=5faadc6d-6af0-41ba-bfce-60bd8c19b7f8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1020-oem N/A linux-backports-modules-5.10.0-1020-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.10.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 02/02/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.2 dmi.board.name: 09YKK0 dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.2:bd02/02/2021:br1.2:svnDellInc.:pnVostro3500:pvr:rvnDellInc.:rn09YKK0:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 1923557] Re: CirrusLogic: The default input volume is "0%"
verified version 5.11.0-18.19 from hirsute-proposed.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
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/1923557
Title:
CirrusLogic: The default input volume is "0%"
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, DMIC volume default
value in kernel driver is 0, which follows no audio sound will be played
during installation and OOBE until being explicitly configured again via
GNOME Settings GUI or other methods.
[Fix]
Commit 0e853a9c3937 ("ALSA: hda/cirrus: Set Initial DMIC volume for
Bullseye to -26 dB") currently landed in upstream tiwai/sound.git is
required this address this issue. It's also being proposed to v5.13
merge window.
[Test Case]
Try to remove all the user space settings caches and reboot. The
detailed steps are:
$ sudo systemctl disable alsa-restore.service
$ sudo rm /var/lib/alsa/asound.state
$ sudo reboot
$ amixer sget 'Internal Mic',0
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 0 [0%] [-51.00dB] [off]
Front Right: Capture 0 [0%] [-51.00dB] [off]
Expect 40% in the front left/right capture volumes.
[Where problems could occur]
This gives the default value of Cirrus CS8409 audio codec capture volume
on Bullseye only. Cannot come out with any side effect it may produce so
far.
[Other Info]
By SRU we skipped a couple of refactoring changes in asound upstream
tree, so additional changes to the original patch are required to
backport.
== original bug description ==
The initial default input volume right after Ubuntu installation is
set to 0% while 16% is expected.
$ amixer
...
Simple mixer control 'Internal Mic',0
Capabilities: cvolume cswitch
Capture channels: Front Left - Front Right
Limits: Capture 0 - 63
Front Left: Capture 0 [0%] [-51.00dB] [off]
Front Right: Capture 0 [0%] [-51.00dB] [off]
Simple mixer control 'Internal Mic Boost',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 2
Front Left: 0 [0%] [0.00dB]
Front Right: 0 [0%] [0.00dB]
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1523 F pulseaudio
CasperMD5CheckResult: skip
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X90
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-04-13 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd.
FingerPrint
Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 3500
Package: linux-oem-5.10
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1020-oem
root=UUID=c666f936-5b87-4cbd-bde6-21fa93b89036 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.10.0-1020.21-oem 5.10.25
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.10.0-1020-oem N/A
linux-backports-modules-5.10.0-1020-oem N/A
linux-firmware 1.187.10
Tags: focal
Uname: Linux 5.10.0-1020-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 02/02/2021
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.2
dmi.board.name: 09YKK0
dmi.board.vendor: Dell Inc.
dmi.board.version: X00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1928198] Re: Failed to start Suspend: A start job for unit systemd-suspend.service has failed.
@kaihengfeng Let me know if you need more other logs. -- 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/1928198 Title: Failed to start Suspend: A start job for unit systemd-suspend.service has failed. Status in linux package in Ubuntu: Confirmed Bug description: For some reason, my distro (Ubuntu 21.04) doesn't suspend properly. I want to solve this problem it is fixable because it will save a lot of battery. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 16:00:17 2021 InstallationDate: Installed on 2020-02-16 (451 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.11.0-17-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-04-24 (17 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+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 1928198] Re: Failed to start Suspend: A start job for unit systemd-suspend.service has failed.
"sudo dmesg" output right after booting. Hope this helps. ** Attachment added: "sudo dmesg log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+attachment/5497456/+files/sudo%20dmesg%20log%20right%20after%20boot. -- 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/1928198 Title: Failed to start Suspend: A start job for unit systemd-suspend.service has failed. Status in linux package in Ubuntu: Confirmed Bug description: For some reason, my distro (Ubuntu 21.04) doesn't suspend properly. I want to solve this problem it is fixable because it will save a lot of battery. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 12 16:00:17 2021 InstallationDate: Installed on 2020-02-16 (451 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.11.0-17-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-04-24 (17 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928198/+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 1925415] Re: Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1925415 Title: Enable mute/micmute LEDs and limit mic boost on EliteBook 845 G8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Mute/micmute LEDs don't work. In addition, the internal mic can only capture lots of noises. [Fix] Use Realtek specific coef to enable LEDs and limit mic boost on the platform. [Test] With the patch applied, the both LEDs start to work, and audio recording becomes crystal clear. [Where problems could occur] It's a trivial change to a brand new device, so no existing device is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1925415/+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 1926792] Re: Fix kernel panic at boot on dual GFX systems
** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute -- 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/1926792 Title: Fix kernel panic at boot on dual GFX systems Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On dual GFX systems, if amdgpu fails to probe a device, vgaarb for another GFX triggers a NULL pointer dereference and freeze the system. [Fix] Defer VGA client registering so resources are handled properly when amdgpu probe fails. [Test] With the patch applied, no more kernel panic when vgaarb is changing the VGA mode. [Where problems could occur] VGA clients won't take effect until a successful probe, so unless there is very subtle bug in vgaarb or vgaswitcheroo, it's very unlikely to introduce any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926792/+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 1924238] Re: Fix no picture from HDMI when it's plugged after boot
** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- 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/1924238 Title: Fix no picture from HDMI when it's plugged after boot Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On Intel CML desktop, there's no HDMI output when the cable is not connected pre-boot. [Fix] Properly handle lane polarity so the driver can write different values to the register to enable the port. [Test] 1. Boot with DP display. 2. Connect HDMI under GNOME desktop. 3. No picture on HDMI monitor. With the fix applied, the issue is resolved. [Where problems could occur] If the BIOS VBT table is not correct, which did happen in the pase, this fix may break those ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1924238/+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 1927826] 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/1927826 Title: package linux-headers-4.4.0-193 4.4.0-193.224 failed to install/upgrade: package linux-headers-4.4.0-193 is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: i don't have any details ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-193 4.4.0-193.224 ProcVersionSignature: Ubuntu 4.4.0-203.235-generic 4.4.249 Uname: Linux 4.4.0-203-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bonnie 1647 F...m pulseaudio /dev/snd/controlC0: bonnie 1647 F pulseaudio Date: Sat May 8 04:20:25 2021 DuplicateSignature: package:linux-headers-4.4.0-193:4.4.0-193.224 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-headers-4.4.0-193 (--configure): package linux-headers-4.4.0-193 is not ready for configuration ErrorMessage: package linux-headers-4.4.0-193 is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=3a013136-c7ad-4f26-8a47-c9d18a0cdb51 InstallationDate: Installed on 2017-12-28 (1227 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: DELL Inc. Studio XPS 435T/9000 PackageArchitecture: all ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-203-generic root=UUID=65964947-81b7-47d0-8ea8-365be049eda4 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: grub-pc 2.02~beta2-36ubuntu3.29 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-193 4.4.0-193.224 failed to install/upgrade: package linux-headers-4.4.0-193 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2009 dmi.bios.vendor: DELL INC. dmi.bios.version: A13 dmi.board.name: 0X501H dmi.board.vendor: DELL Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: DELL Inc. dmi.modalias: dmi:bvnDELLINC.:bvrA13:bd07/28/2009:svnDELLInc.:pnStudioXPS435T/9000:pvr00:rvnDELLInc.:rn0X501H:rvrA02:cvnDELLInc.:ct3:cvr: dmi.product.name: Studio XPS 435T/9000 dmi.product.version: 00 dmi.sys.vendor: DELL Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927826/+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
