[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Invalid 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 Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.:ct3:cvrTobefilledbyO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+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 1950064] [NEW] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi
Public bug reported: [Description] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. Upgrade kernel to 5.11.0-1022 4. Reboot the system [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.11.0-1022.23-raspi ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: [Description] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. Upgrade kernel to 5.11.0-1022 4. Reboot the system [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ - Image: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz - https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-armhf+raspi.img.xz + Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz + ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.11.0-1022.23-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1950064 Title: Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi Status in linux-raspi package in Ubuntu: New Bug description: [Description] Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel 5.11.0-1022.23-raspi [Steps to reproduce] 1. Flash image (see additional information) 2. Boot into system 3. apt dist-upgrade all packages and reboot 4. Enable proposed repository 5. Upgrade kernel to 5.11.0-1022 4. Reboot the system [Actual result] Device does not boot into system [Expected result] Boot into system successfully [Additional information] Hardware: rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ Image: ubuntu-21.04-preinstalled-server-arm64+raspi.img.xz ubuntu-21.04-preinstalled-server-armhf+raspi.img.xz Kernel Version: 5.11.0-1022.23-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1950064/+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 1947614] Re: Laptop fans spin at ~50% w/o CPU load with kernel 5.13
** Tags added: kernel-bug kernel-therm ** Tags removed: kernel-bug -- 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/1947614 Title: Laptop fans spin at ~50% w/o CPU load with kernel 5.13 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 21.04 to Ubuntu 21.10 a few days ago, I noticed that the fans of my laptop (Lenovo ideapad 700-15ISK) were spinning all the time at about ~50%, no matter the CPU load. I forced all my cores to run at 100% with a simple while(1) loop to see if the fan speed would increase but nothing. Apparently, no matter the CPU load and temperature, with kernel 5.13.0-19 the fans of my laptop spin at the same RPM. From their noise, I believe that's about 50%. Therefore, I decided to boot the same Ubuntu 21.10 with the older kernel 5.11.0-37 and the problem disappeared. Looks like in the newer kernel there is a problem with the control of fans for my HW. To complete the picture, I built and booted kernel v5.15-rc5 to see if with a bleeding edge kernel the problem would disappear: it didn't. Therefore, the problem appears to be introduced somewhere between kernel 5.11 and kernel 5.13. The output of `sensors`, unfortunately doesn't show any fans and that's the same no matter the kernel version: pch_skylake-virtual-0 Adapter: Virtual device temp1:+54.5°C BAT0-acpi-0 Adapter: ACPI interface in0: 12.25 V coretemp-isa- Adapter: ISA adapter Package id 0: +39.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+37.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+38.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+39.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+38.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+39.0°C (crit = +99.0°C) temp2:+42.0°C (crit = +85.0°C) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vlad 5972 F pulseaudio /dev/snd/controlC0: vlad 5972 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 19:04:03 2021 InstallationDate: Installed on 2020-03-17 (579 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 80RU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) dmi.bios.date: 08/09/2017 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947614/+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 1947614] Re: Laptop fans spin at ~50% w/o CPU load with kernel 5.13
To check the theory about the Ubuntu-specific patches, I tried to boot another Linux distro (Fedora Live 35) in order to see if the problem would exist: it did not. The kernel used was: 5.14.10-300.fc35.x86_64. Which is more recent that the kernel 5.13.0-20, currently used by Ubuntu 21.10. Therefore, it looks that both the older Ubuntu-specific kernel and the newest Fedora kernel do _not_ have the problem, thanks to some custom patches that (apparently) do _not_ exist in 5.13.0-19 nor in the mainstream Linux kernel. It's getting even more tricky. An alternative long-shot theory is that thermal management policies changed in the newest Ubuntu, but does not activate with kernel 5.11 because of the lack of some kernel feature. That would explain why the problem exists with the mainstream kernel as well, but not on another distro. -- 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/1947614 Title: Laptop fans spin at ~50% w/o CPU load with kernel 5.13 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 21.04 to Ubuntu 21.10 a few days ago, I noticed that the fans of my laptop (Lenovo ideapad 700-15ISK) were spinning all the time at about ~50%, no matter the CPU load. I forced all my cores to run at 100% with a simple while(1) loop to see if the fan speed would increase but nothing. Apparently, no matter the CPU load and temperature, with kernel 5.13.0-19 the fans of my laptop spin at the same RPM. From their noise, I believe that's about 50%. Therefore, I decided to boot the same Ubuntu 21.10 with the older kernel 5.11.0-37 and the problem disappeared. Looks like in the newer kernel there is a problem with the control of fans for my HW. To complete the picture, I built and booted kernel v5.15-rc5 to see if with a bleeding edge kernel the problem would disappear: it didn't. Therefore, the problem appears to be introduced somewhere between kernel 5.11 and kernel 5.13. The output of `sensors`, unfortunately doesn't show any fans and that's the same no matter the kernel version: pch_skylake-virtual-0 Adapter: Virtual device temp1:+54.5°C BAT0-acpi-0 Adapter: ACPI interface in0: 12.25 V coretemp-isa- Adapter: ISA adapter Package id 0: +39.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+37.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+38.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+39.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+38.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+39.0°C (crit = +99.0°C) temp2:+42.0°C (crit = +85.0°C) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vlad 5972 F pulseaudio /dev/snd/controlC0: vlad 5972 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 19:04:03 2021 InstallationDate: Installed on 2020-03-17 (579 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 80RU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) dmi.bios.date: 08/09/2017 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1950062] 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/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in linux package in Ubuntu: Confirmed Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950062/+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 1950062] Re: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Results of i2cdetect showing i2c-0 to i2c-2 are the pixx4 interfaces from the CPU: i2cdetect -l i2c-3 i2c AMDGPU DM i2c hw bus 0 I2C adapter i2c-1 smbus SMBus PIIX4 adapter port 2 at ff00 SMBus adapter i2c-6 i2c AMDGPU DM i2c hw bus 3 I2C adapter i2c-4 i2c AMDGPU DM i2c hw bus 1 I2C adapter i2c-2 smbus SMBus PIIX4 adapter port 1 at ff20 SMBus adapter i2c-0 smbus SMBus PIIX4 adapter port 0 at ff00 SMBus adapter i2c-7 i2c AMDGPU DM aux hw bus 0 I2C adapter i2c-5 i2c AMDGPU DM i2c hw bus 2 I2C adapter -- 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/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in linux package in Ubuntu: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950062/+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 1950062] [NEW] Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's
Public bug reported: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.60:bd08/11/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1950062 Title: Unable to access CPU i2c interfaces with AMD "Cezanne" CPU's Status in linux package in Ubuntu: New Bug description: OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB controller and the DRAM RGB controllers and after updating my system to a 5700G from a 2400G I see error messages in dmesg for each read and write attempt to the interfaces. If I swap the CPU back on the same install I am able to see and control the RGB interfaces. Another user on the OpenRGB discord with a 5600G is also seeing the same issues. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1654 F pulseaudio /dev/snd/pcmC1D0p: user 1654 F...m pulseaudio /dev/snd/controlC0: user 1654 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 16:36:17 2021 InstallationDate: Installed on 2021-09-18 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=dc2e65cb-a2e0-408c-a64b-bb0ccc6fdef0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-17 (20 days ago) dmi.bios.date: 08/11/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.60 dmi.board.name: B450 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Description changed: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. + + Warning: 32bit iso on sourceforge for boot-repair-disk still contains + unpatched Kernel. This is especially dangerous if boot-repair fails to + repair the system to a bootable state, as there will be no way of + applying the Fix detailed below. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la + Fujitsu Q584 (unable to fix due to non booting OS is on the machine) --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Description changed: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. - Lenovo forums at the moment are full of topics regading this issue. + Lenovo forums at the moment are full of topics regarding this issue. Thank you!! -- You received this bug notification because you are a member of Kernel
[Kernel-packages] [Bug 1949924] Re: yelp crashes in wayland session
This seems to be NVIDIA related (I'm using nvidia-driver-470). Downgrading the libnvidia-egl-wayland1 package to the version used in impish fixes the issue; hence it's a 1.1.9 regression. Setting GDK_BACKEND=x11, as mentioned in the upstream issue, works around the problem. ** Bug watch added: github.com/NVIDIA/egl-wayland/issues #27 https://github.com/NVIDIA/egl-wayland/issues/27 ** Also affects: egl-wayland via https://github.com/NVIDIA/egl-wayland/issues/27 Importance: Unknown Status: Unknown ** Also affects: egl-wayland (Ubuntu) Importance: Undecided Status: New ** Changed in: yelp (Ubuntu) Importance: High => Undecided ** Changed in: yelp (Ubuntu) Status: New => Invalid ** Tags added: regression-release ** Summary changed: - yelp crashes in wayland session + yelp crashes in wayland session with NVIDIA 470 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to egl-wayland in Ubuntu. https://bugs.launchpad.net/bugs/1949924 Title: yelp crashes in wayland session with NVIDIA 470 Status in NVIDIA / egl-wayland: Unknown Status in egl-wayland package in Ubuntu: New Status in yelp package in Ubuntu: Invalid Bug description: $ yelp yelp: ../src/wayland-thread.c:87: wlExternalApiLock: Assertion `!"failed to lock pthread mutex"' failed. Aborted (core dumped) This does not happen in Debian testing, and it also works as expected in an Ubuntu on Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yelp 41.1-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 5 02:51:43 2021 InstallationDate: Installed on 2019-11-10 (725 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1949924/+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 1947614] Re: Laptop fans spin at ~50% w/o CPU load with kernel 5.13
Given that the problem exist with kernel 5.13.0-19 and newer but not with kernel 5.11.0-37, I tried to find which the change triggered this weird behavior using git bisect. I used bisect in the range [v5.11, v5.13] (official tags) and I've built the standard non-ubuntu kernel(s) using: make -j4 bindeb-pkg LOCALVERSION=-custom As config, I used the Ubuntu one from: /boot/config-5.11.0-37-generic and accepted all the new config options as default. But, before finishing to test all the bisect steps, I found that even with the first kernel, v5.11, commit: f40ddce88593482919761f74910f42f4b84c004b, the problem already exists. Therefore, it looks like there were some Ubuntu-specific patches in 5.11.0-37 that prevented the problem to happen. In the original v5.11 kernel, the fans spin at ~50% apparently no matter the CPU load. Apparently, those Ubuntu patches that prevented the problem from happening, got changed in 5.13.0-19. Does anybody have a clue what could that be? Thanks, Vlad -- 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/1947614 Title: Laptop fans spin at ~50% w/o CPU load with kernel 5.13 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 21.04 to Ubuntu 21.10 a few days ago, I noticed that the fans of my laptop (Lenovo ideapad 700-15ISK) were spinning all the time at about ~50%, no matter the CPU load. I forced all my cores to run at 100% with a simple while(1) loop to see if the fan speed would increase but nothing. Apparently, no matter the CPU load and temperature, with kernel 5.13.0-19 the fans of my laptop spin at the same RPM. From their noise, I believe that's about 50%. Therefore, I decided to boot the same Ubuntu 21.10 with the older kernel 5.11.0-37 and the problem disappeared. Looks like in the newer kernel there is a problem with the control of fans for my HW. To complete the picture, I built and booted kernel v5.15-rc5 to see if with a bleeding edge kernel the problem would disappear: it didn't. Therefore, the problem appears to be introduced somewhere between kernel 5.11 and kernel 5.13. The output of `sensors`, unfortunately doesn't show any fans and that's the same no matter the kernel version: pch_skylake-virtual-0 Adapter: Virtual device temp1:+54.5°C BAT0-acpi-0 Adapter: ACPI interface in0: 12.25 V coretemp-isa- Adapter: ISA adapter Package id 0: +39.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+37.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+38.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+39.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+38.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+39.0°C (crit = +99.0°C) temp2:+42.0°C (crit = +85.0°C) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vlad 5972 F pulseaudio /dev/snd/controlC0: vlad 5972 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Oct 18 19:04:03 2021 InstallationDate: Installed on 2020-03-17 (579 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 80RU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-16 (1 days ago) dmi.bios.date: 08/09/2017 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO To manage notifications
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
> I believe we can close this bug. The change to the wiki is welcome, since it now reflects the current situation. However, in my opinion, the real problem uncovered here has not been addressed: Ubuntu should provide mainline kernels built with the latest LTS toolchain alongside the current one that uses bleeding edge toolchains, so that using/testing more recent kernels becomes more accessible to a wider audience (i.e., the vast majority who does not compile their kernels from source). Historically, Ubuntu has had a major barrier to adoption: new users who buy their hardware in between LTS cycles will usually have a very sub- par experience with Ubuntu because of the outdated kernel. Their choice is to either: - use the latest intermediate release, which may still not provide a recent enough kernel and is a bad choice for a first time user anyway - use the latest LTS which may not be usable at all on their systems with the very outdated kernel (this tends to happen a lot with laptops in particular). With all due respect to the user who put up https://launchpad.net/~tuxinvader/+archive/ubuntu/kernel-build-tools and their efforts in doing so, there should be an official PPA/infrastructure in place for this. We all know users installing lots of PPAs without thinking is a huge risk and a practice that is advised against. But then you can't just leave the user with only one remaining, untenable choice, which is for their system to be unusable, in the name of security concerns that they don't quite understand. This is a common criticism of Ubuntu: it effectively _forces_ users into installing a whole bunch of random PPAs willy-nilly to get certain basic features. Until something is done about this, "LTS" releases are actually unusable (or usable with many jarring bugs) for many users. The HWE releases are better than nothing, but not nearly enough. A post above put it very nicely: > If you are telling people that you are going to support it for 5 years, then that means being able to provide security updates to them as well as allowing them to use hardware that was created during the 5 years following April 2020 within reason. To do that, people must be able to update the kernel plain and simple. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: In Progress Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950061] [NEW] Failed to start Raspberry Pi bluetooth helper
Public bug reported: OS: Ubuntu 21.10 Package: pi-bluetooth 0.1.15ubuntu2 arm64 Affected HW: Raspberry Pi 4B Here's my problem: bthelper unit fails to start # systemctl status bthelper@hci0.service × bthelper@hci0.service - Raspberry Pi bluetooth helper Loaded: loaded (/lib/systemd/system/bthelper@.service; static) Active: failed (Result: exit-code) since Sat 2021-11-06 23:44:32 EET; 1min 23s ago Process: 570 ExecStart=/usr/bin/bthelper hci0 (code=exited, status=1/FAILURE) Main PID: 570 (code=exited, status=1/FAILURE) CPU: 103ms ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: AdvertisementMonitor path registered ноя 06 23:44:32 raspberrypi bthelper[599]: AdvertisementMonitor path registered ноя 06 23:44:32 raspberrypi bthelper[609]: Invalid device: Network is down ноя 06 23:44:32 raspberrypi systemd[1]: bthelper@hci0.service: Main process exited, code=exited, status=1/FAILURE ноя 06 23:44:32 raspberrypi systemd[1]: bthelper@hci0.service: Failed with result 'exit-code'. ноя 06 23:44:32 raspberrypi systemd[1]: Failed to start Raspberry Pi bluetooth helper. But script works fine if hcitool command is placed before reinitialisation: --- /usr/bin/bthelper --- # Route SCO packets to the HCI interface (enables HFP/HSP) /usr/bin/hcitool -i $dev cmd 0x3f 0x1c 0x01 0x02 0x00 0x01 0x01 > /dev/null # Force reinitialisation to allow extra features such as Secure Simple Pairing # to be enabled /usr/bin/bluetoothctl power off /usr/bin/bluetoothctl power on --- # systemctl status bthelper@hci0.service ● bthelper@hci0.service - Raspberry Pi bluetooth helper Loaded: loaded (/lib/systemd/system/bthelper@.service; static) Active: active (exited) since Sat 2021-11-06 23:50:17 EET; 1min 17s ago Process: 1099 ExecStart=/usr/bin/bthelper hci0 (code=exited, status=0/SUCCESS) Main PID: 1099 (code=exited, status=0/SUCCESS) CPU: 98ms After this change it works as expected ** Affects: pi-bluetooth (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bthelper_modified" https://bugs.launchpad.net/bugs/1950061/+attachment/5538572/+files/bthelper_modified ** Description changed: - OS: Ubuntu 12.01 + OS: Ubuntu 21.10 Package: pi-bluetooth 0.1.15ubuntu2 arm64 Affected HW: Raspberry Pi 4B Here's my problem: bthelper unit fails to start - # systemctl status bthelper@hci0.service + # systemctl status bthelper@hci0.service × bthelper@hci0.service - Raspberry Pi bluetooth helper - Loaded: loaded (/lib/systemd/system/bthelper@.service; static) - Active: failed (Result: exit-code) since Sat 2021-11-06 23:44:32 EET; 1min 23s ago - Process: 570 ExecStart=/usr/bin/bthelper hci0 (code=exited, status=1/FAILURE) -Main PID: 570 (code=exited, status=1/FAILURE) - CPU: 103ms + Loaded: loaded (/lib/systemd/system/bthelper@.service; static) + Active: failed (Result: exit-code) since Sat 2021-11-06 23:44:32 EET; 1min 23s ago + Process: 570 ExecStart=/usr/bin/bthelper hci0 (code=exited, status=1/FAILURE) + Main PID: 570 (code=exited, status=1/FAILURE) + CPU: 103ms ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: [82B blob data] ноя 06 23:44:32 raspberrypi bthelper[578]: AdvertisementMonitor path registered ноя 06 23:44:32 raspberrypi bthelper[599]: AdvertisementMonitor path registered ноя 06 23:44:32 raspberrypi bthelper[609]: Invalid device: Network is down ноя 06 23:44:32 raspberrypi systemd[1]: bthelper@hci0.service: Main process exited, code=exited, status=1/FAILURE ноя 06 23:44:32 raspberrypi systemd[1]: bthelper@hci0.service: Failed with result 'exit-code'. ноя 06 23:44:32 raspberrypi systemd[1]: Failed to start Raspberry Pi bluetooth helper. But script works fine if this command is placed before before reinitialisation: --- /usr/bin/bthelper --- # Route SCO packets to the HCI interface (enables HFP/HSP) /usr/bin/hcitool -i $dev cmd 0x3f 0x1c 0x01 0x02 0x00 0x01 0x01 > /dev/null # Force reinitialisation to allow extra features such as Secure Simple Pairing # to be enabled /usr/bin/bluetoothctl power off /usr/bin/bluetoothctl power on --- - # systemctl status bthelper@hci0.service + # systemctl status bthelper@hci0.service ● bthelper@hci0.service - Raspberry Pi bluetooth helper - Loaded: loaded (/lib/systemd/system/bthelper@.service; static) - Active: active (exited) since Sat 2021-11-06 23:50:17 EET; 1min 17s ago - Process: 1099 ExecStart=/usr/bin/bthelper hci0 (code=exited, status=0/SUCCESS) -Main
[Kernel-packages] [Bug 1950010] Re: Upgrading to 1.187.20 results in missing firmware, Nvidia 1650 MaxQ
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1950010 Title: Upgrading to 1.187.20 results in missing firmware, Nvidia 1650 MaxQ Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a fresh install of Kubuntu 20.04, I ran sudo apt upgrade, which results in the the following warnings: Setting up linux-firmware (1.187.20) ... update-initramfs: Generating /boot/initrd.img-5.11.0-38-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 Booting to the last installed kernel, 5.11.0-27-generic will allow me to boot into the desktop - however if I were to use a Nvidia driver (460 and 470, non-server), I will have issues getting the computer to sleep, and on one boot I the shutdown greeter kept crashing The following packages were part of the upgrade: esme@Esme-Prestige-14:~$ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libatomic1:i386 libbsd0:i386 libdpkg-perl libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi7:i386 libfile-fcntllock-perl libglvnd0:i386 libllvm12:i386 libnvidia-cfg1-470 libnvidia-common-470 libnvidia-compute-470:i386 libnvidia-decode-470 libnvidia-decode-470:i386 libnvidia-encode-470 libnvidia-encode-470:i386 libnvidia-extra-470 libnvidia-fbc1-470 libnvidia-gl-470 libnvidia-gl-470:i386 libnvidia-ifr1-470 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libvulkan1:i386 libwayland-client0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-randr0:i386 libxcb-shm0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vulkan-drivers:i386 nvidia-compute-utils-470 nvidia-kernel-source-470 nvidia-prime nvidia-settings
[Kernel-packages] [Bug 1941708] Re: BlueZ 5.62 release
This bug was fixed in the package bluez - 5.62-0ubuntu1 --- bluez (5.62-0ubuntu1) jammy; urgency=medium * New upstream release 5.62 (LP: #1941708): - Fix issue with handling truncation when loading LTKs. - Fix issue with accepting Exchange MTU on EATT bearer. - Fix issue with clearing DeviceLost timers on power down. - Fix issue with AVCTP browsing channel and missing ERTM. - Fix issue with AVDTP and local SEID pool for each adapter. - Add support for BR/EDR and LE connection failure reasons. * Drop patch git_glibc234_buildfix.patch as it is included in 5.62. * New upstream release 5.61: - Fix issue with A2DP while waiting for command response. - Fix issue with A2DP when SetConfiguration fails. - Fix issue with device removal handling. - Fix issue with storing discoverable setting. - Add support for Central Address Resolution characteristic. - Add support for admin policy plugin. * Merges from Debian 5.61-1: - Change debian/watch to use HTTPS. - Add to debian/README.Debian - Replace 0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch with allow-using-obexd-without-systemd-in-the-user-sessio.patch which also fixes LP: #1945887. - Rename 0001-obex-Use-GLib-helper-function-to-manipulate-paths.patch to obex-Use-GLib-helper-function-to-manipulate-paths.patch - Rename 0001-work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch to work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch although Ubuntu still carries an additional fix that's not in the Debian branch. -- Daniel van Vugt Fri, 15 Oct 2021 15:18:43 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- 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/1941708 Title: BlueZ 5.62 release Status in bluez package in Ubuntu: Fix Released Bug description: BlueZ 5.62 release is out: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1941708/+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 1945887] Re: org.bluez.obex.service contains unresolved '@libexecdir@'
This bug was fixed in the package bluez - 5.62-0ubuntu1 --- bluez (5.62-0ubuntu1) jammy; urgency=medium * New upstream release 5.62 (LP: #1941708): - Fix issue with handling truncation when loading LTKs. - Fix issue with accepting Exchange MTU on EATT bearer. - Fix issue with clearing DeviceLost timers on power down. - Fix issue with AVCTP browsing channel and missing ERTM. - Fix issue with AVDTP and local SEID pool for each adapter. - Add support for BR/EDR and LE connection failure reasons. * Drop patch git_glibc234_buildfix.patch as it is included in 5.62. * New upstream release 5.61: - Fix issue with A2DP while waiting for command response. - Fix issue with A2DP when SetConfiguration fails. - Fix issue with device removal handling. - Fix issue with storing discoverable setting. - Add support for Central Address Resolution characteristic. - Add support for admin policy plugin. * Merges from Debian 5.61-1: - Change debian/watch to use HTTPS. - Add to debian/README.Debian - Replace 0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch with allow-using-obexd-without-systemd-in-the-user-sessio.patch which also fixes LP: #1945887. - Rename 0001-obex-Use-GLib-helper-function-to-manipulate-paths.patch to obex-Use-GLib-helper-function-to-manipulate-paths.patch - Rename 0001-work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch to work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch although Ubuntu still carries an additional fix that's not in the Debian branch. -- Daniel van Vugt Fri, 15 Oct 2021 15:18:43 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- 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/1945887 Title: org.bluez.obex.service contains unresolved '@libexecdir@' Status in bluez package in Ubuntu: Fix Released Bug description: After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday, the following error message showed up in the syslog: Oct 2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760] Activated service 'org.bluez.obex' failed: Failed to execute program org.bluez.obex: No such file or directory Upon inspection, this was due to the fact that the service definition contained the line 'Exec=@libexecdir@/obexd' which could not be resolved (this placeholder is supposedly to be replaced at build time). Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this (together with 'systemctl --user daemon-reload; systemctl --user restart obex'). Note that this problem should be part of *all* current versions of the bluez[-obexd] package, regardless of the used architecture (including Focal, Impish): % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb [...] Länge: 217906 (213K) [application/x-debian-package] Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert. [...] 2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert [217906/217906] % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb [...] Länge: 160832 (157K) [application/x-debian-package] Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert. [...] 2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert [160832/160832] % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service Exec=@libexecdir@/obexd % # lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 # apt-cache policy bluez-obexd bluez-obexd: [...] 5.53-0ubuntu3.3 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1945887/+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 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
On my affected machine I tested a live iso of EndeavourOS (latest release) with kernel 5.13+ and I observed no freezes. So the problem looks specific to Ubuntu on my laptop (Dell Latitude 7390). -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+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 1950046] 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 1950046 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/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: Incomplete Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
I have observed that if I choose to boot in recovery mode from GRUB menu and then select to resume boot, the system does not freeze. Of course, in that case the graphics drivers are not loaded properly so it's probably not a particularly viable workaround. -- 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/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+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 1950046] Re: tg3 transmit timed out, resetting
Example 2: Nov 06 15:34:38 kernel: [ cut here ] Nov 06 15:34:38 kernel: NETDEV WATCHDOG: eno1 (tg3): transmit queue 0 timed out Nov 06 15:34:38 kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 Nov 06 15:34:38 kernel: Modules linked in: rpcsec_gss_krb5 usblp binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm hpilo rapl intel_cstate acpi_ip> Nov 06 15:34:38 kernel: ghash_clmulni_intel cryptd drm psmouse libahci xhci_pci tg3 lpc_ich xhci_pci_renesas Nov 06 15:34:38 kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.11.0-38-generic #42~20.04.1-Ubuntu Nov 06 15:34:38 kernel: Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 Nov 06 15:34:38 kernel: RIP: 0010:dev_watchdog+0x24f/0x260 Nov 06 15:34:38 kernel: Code: 07 78 fd ff eb ab 4c 89 ff c6 05 33 22 ee 00 01 e8 26 3c fa ff 44 89 e9 4c 89 fe 48 c7 c7 f0 42 c9 8f 48 89 c2 e8 cf 5a 16 00 <0f> 0b eb 8c 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 Nov 06 15:34:38 kernel: RSP: 0018:ad17002c4e88 EFLAGS: 00010282 Nov 06 15:34:38 kernel: RAX: RBX: 93cd93e7bd00 RCX: Nov 06 15:34:38 kernel: RDX: 93d07aa68a20 RSI: 93d07aa58ac0 RDI: 0300 Nov 06 15:34:38 kernel: RBP: ad17002c4eb8 R08: 93d07aa58ac0 R09: ad17002c4c48 Nov 06 15:34:38 kernel: R10: 00cb9cd0 R11: 00cb9db8 R12: 0005 Nov 06 15:34:38 kernel: R13: R14: 93cd94af04c0 R15: 93cd94af Nov 06 15:34:38 kernel: FS: () GS:93d07aa4() knlGS: Nov 06 15:34:38 kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 06 15:34:38 kernel: CR2: 7f41920eed38 CR3: be610001 CR4: 001706e0 Nov 06 15:34:38 kernel: Call Trace: Nov 06 15:34:38 kernel: Nov 06 15:34:38 kernel: ? pfifo_fast_enqueue+0x150/0x150 Nov 06 15:34:38 kernel: call_timer_fn+0x2e/0x100 Nov 06 15:34:38 kernel: __run_timers.part.0+0x1e0/0x250 Nov 06 15:34:38 kernel: ? lapic_next_deadline+0x2c/0x40 Nov 06 15:34:38 kernel: ? clockevents_program_event+0x8f/0xe0 Nov 06 15:34:38 kernel: run_timer_softirq+0x2a/0x50 Nov 06 15:34:38 kernel: __do_softirq+0xe0/0x29b Nov 06 15:34:38 kernel: asm_call_irq_on_stack+0x12/0x20 Nov 06 15:34:38 kernel: Nov 06 15:34:38 kernel: do_softirq_own_stack+0x3d/0x50 Nov 06 15:34:38 kernel: irq_exit_rcu+0xa4/0xb0 Nov 06 15:34:38 kernel: sysvec_apic_timer_interrupt+0x3d/0x90 Nov 06 15:34:38 kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Nov 06 15:34:38 kernel: RIP: 0010:cpuidle_enter_state+0xdf/0x350 Nov 06 15:34:38 kernel: Code: ff e8 95 a8 77 ff 80 7d d7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 52 02 00 00 31 ff e8 c8 52 7e ff fb 66 0f 1f 44 00 00 <45> 85 ff 0f 88 e5 00 00 00 49 63 c7 4c 2b 75 c8 48 8d 14 40 48 8d Nov 06 15:34:38 kernel: RSP: 0018:ad1700097e48 EFLAGS: 0246 Nov 06 15:34:38 kernel: RAX: 93d07aa6c380 RBX: 0004 RCX: 001f Nov 06 15:34:38 kernel: RDX: RSI: 37c75227 RDI: Nov 06 15:34:38 kernel: RBP: ad1700097e80 R08: 00027d42516aa349 R09: 0e3b Nov 06 15:34:38 kernel: R10: 93d07aa6afa4 R11: 93d07aa6af84 R12: 93d07aa77600 Nov 06 15:34:38 kernel: R13: 9004d8e0 R14: 00027d42516aa349 R15: 0004 Nov 06 15:34:38 kernel: ? cpuidle_enter_state+0xbb/0x350 Nov 06 15:34:38 kernel: cpuidle_enter+0x2e/0x40 Nov 06 15:34:38 kernel: call_cpuidle+0x23/0x40 Nov 06 15:34:38 kernel: do_idle+0x1df/0x260 Nov 06 15:34:38 kernel: cpu_startup_entry+0x20/0x30 Nov 06 15:34:38 kernel: start_secondary+0x11f/0x160 Nov 06 15:34:38 kernel: secondary_startup_64_no_verify+0xc2/0xcb Nov 06 15:34:38 kernel: ---[ end trace 28a5883990ef746a ]--- Nov 06 15:34:38 kernel: tg3 :03:00.0 eno1: transmit timed out, resetting Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x: 0x165f14e4, 0x00100446, 0x0200, 0x00800010 Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0010: 0xfabf000c, 0x, 0xfabe000c, 0x Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0020: 0xfabd000c, 0x, 0x, 0x2133103c Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0030: 0x, 0x0048, 0x, 0x010a Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0040: 0x, 0x1a00, 0xc8035001, 0x64002008 Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0050: 0x5803, 0x, 0x0086a005, 0x Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0060: 0x, 0x, 0xf298, 0x00380081 Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0070: 0x000710b0, 0xf50eacfb, 0x, 0x Nov 06 15:34:39 kernel: tg3 :03:00.0 eno1: 0x0080: 0x165f14e4, 0x80f8,
[Kernel-packages] [Bug 1950046] [NEW] tg3 transmit timed out, resetting
Public bug reported: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Package changed: linux-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1950046 Title: tg3 transmit timed out, resetting Status in linux package in Ubuntu: New Bug description: Hi, since earlier this year (sorry, I don't have an exact date) I started to encounter regular network hangs on multiple HPE servers that I manage. The hangs occur on high network load and are followed by a message like "tg3 :02:00.0 eno1: transmit timed out, resetting". The problem already started on the original 20.04 kernel and still occurs on the current HWE kernel. Affected machines are HPE ProLiant ML30 Gen9, DL20 Gen9, and Microserver Gen8. The frequency of the problem seems to increase as time passes. There is a long standing upstream ticket at https://bugzilla.kernel.org/show_bug.cgi?id=12877. I'll post log messages in the comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950046/+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 1950046] Re: tg3 transmit timed out, resetting
Example 1: Nov 04 17:34:59 kernel: [ cut here ] Nov 04 17:34:59 kernel: NETDEV WATCHDOG: eno1 (tg3): transmit queue 0 timed out Nov 04 17:34:59 kernel: WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 Nov 04 17:34:59 kernel: Modules linked in: rpcsec_gss_krb5 xt_nat veth xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_use> Nov 04 17:34:59 kernel: raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel m> Nov 04 17:34:59 kernel: CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.11.0-38-generic #42~20.04.1-Ubuntu Nov 04 17:34:59 kernel: Hardware name: HP ProLiant ML30 Gen9/ProLiant ML30 Gen9, BIOS U23 04/04/2019 Nov 04 17:34:59 kernel: RIP: 0010:dev_watchdog+0x24f/0x260 Nov 04 17:34:59 kernel: Code: 07 78 fd ff eb ab 4c 89 ff c6 05 33 22 ee 00 01 e8 26 3c fa ff 44 89 e9 4c 89 fe 48 c7 c7 f0 4> Nov 04 17:34:59 kernel: RSP: 0018:a82b80174e88 EFLAGS: 00010282 Nov 04 17:34:59 kernel: RAX: RBX: 94c7927c8500 RCX: 0027 Nov 04 17:34:59 kernel: RDX: 0027 RSI: 000100012071 RDI: 94cbebd98ac8 Nov 04 17:34:59 kernel: RBP: a82b80174eb8 R08: 94cbebd98ac0 R09: a82b80174c48 Nov 04 17:34:59 kernel: R10: 0113d6b0 R11: 0113d790 R12: 0005 Nov 04 17:34:59 kernel: R13: R14: 94c7931cc4c0 R15: 94c7931cc000 Nov 04 17:34:59 kernel: FS: () GS:94cbebd8() knlGS: Nov 04 17:34:59 kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 04 17:34:59 kernel: CR2: 56452bee1a38 CR3: 00052a610003 CR4: 003706e0 Nov 04 17:34:59 kernel: DR0: DR1: DR2: Nov 04 17:34:59 kernel: DR3: DR6: fffe0ff0 DR7: 0400 Nov 04 17:34:59 kernel: Call Trace: Nov 04 17:34:59 kernel: Nov 04 17:34:59 kernel: ? pfifo_fast_enqueue+0x150/0x150 Nov 04 17:34:59 kernel: call_timer_fn+0x2e/0x100 Nov 04 17:34:59 kernel: __run_timers.part.0+0x1e0/0x250 Nov 04 17:34:59 kernel: ? lapic_next_deadline+0x2c/0x40 Nov 04 17:34:59 kernel: ? clockevents_program_event+0x8f/0xe0 Nov 04 17:34:59 kernel: run_timer_softirq+0x2a/0x50 Nov 04 17:34:59 kernel: __do_softirq+0xe0/0x29b Nov 04 17:34:59 kernel: asm_call_irq_on_stack+0x12/0x20 Nov 04 17:34:59 kernel: Nov 04 17:34:59 kernel: do_softirq_own_stack+0x3d/0x50 Nov 04 17:34:59 kernel: irq_exit_rcu+0xa4/0xb0 Nov 04 17:34:59 kernel: sysvec_apic_timer_interrupt+0x3d/0x90 Nov 04 17:34:59 kernel: asm_sysvec_apic_timer_interrupt+0x12/0x20 Nov 04 17:34:59 kernel: RIP: 0010:cpuidle_enter_state+0xdf/0x350 Nov 04 17:34:59 kernel: Code: ff e8 95 a8 77 ff 80 7d d7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 52 02 00 00 31 ff e8 c> Nov 04 17:34:59 kernel: RSP: 0018:a82b800cfe48 EFLAGS: 0246 Nov 04 17:34:59 kernel: RAX: 94cbebdac380 RBX: 0006 RCX: 001f Nov 04 17:34:59 kernel: RDX: RSI: 2aaa530e RDI: Nov 04 17:34:59 kernel: RBP: a82b800cfe80 R08: 0001e6651774fce9 R09: 104c Nov 04 17:34:59 kernel: R10: 94cbebdaafa4 R11: 94cbebdaaf84 R12: 94cbebdb7a00 Nov 04 17:34:59 kernel: R13: b804d8e0 R14: 0001e6651774fce9 R15: 0006 Nov 04 17:34:59 kernel: ? cpuidle_enter_state+0xbb/0x350 Nov 04 17:34:59 kernel: cpuidle_enter+0x2e/0x40 Nov 04 17:34:59 kernel: call_cpuidle+0x23/0x40 Nov 04 17:34:59 kernel: do_idle+0x1df/0x260 Nov 04 17:34:59 kernel: cpu_startup_entry+0x20/0x30 Nov 04 17:34:59 kernel: start_secondary+0x11f/0x160 Nov 04 17:34:59 kernel: secondary_startup_64_no_verify+0xc2/0xcb Nov 04 17:34:59 kernel: ---[ end trace 7e2e93595130f070 ]--- Nov 04 17:34:59 kernel: tg3 :02:00.0 eno1: transmit timed out, resetting Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x: 0x165f14e4, 0x00100546, 0x0200, 0x00800010 Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0010: 0x92b3000c, 0x, 0x92b4000c, 0x Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0020: 0x92b5000c, 0x, 0x, 0x22e8103c Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0030: 0x, 0x0048, 0x, 0x01ff Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0040: 0x, 0x7400, 0xc8035001, 0x64002008 Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0050: 0x5803, 0x, 0x0086a005, 0x Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0060: 0x, 0x, 0xf298, 0x00380081 Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0070: 0x000710b0, 0xf56dffdb, 0x, 0x Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0080: 0x165f14e4, 0x80f8, 0x, 0x089d Nov 04 17:35:00 kernel: tg3 :02:00.0 eno1: 0x0090: 0x, 0x, 0x,
[Kernel-packages] [Bug 1950042] 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 1950042 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Confirmed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+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 1950042] [NEW] Let NVMe with HMB use native power control again
Public bug reported: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1949545 somerville ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Tags added: oem-priority originate-from-1949545 somerville -- 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/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14
[Kernel-packages] [Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
To be clear, the last dmesg is from after I rebooted the "frozen" computer (which wouldn't respond to Control-Alt-F1/F8/etc or any other keys). Since it shows kernel version, etc. I pushed some keys, the backlight came on like it was going to boot, and then it just stopped there. But I think the power LEDs were set to suspend like proper. -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-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: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+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 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
NOPE, NEVERMIND. The issue is still happening. I thought I did a full reboot, with [deep], and came back. But I just came back after an hour or two and the BACKLIGHT turned on, but it still wouldn't come back from suspend. This seems like it attempted to come back online: $ journalctl -o short-precise -k -b -1 Nov 06 06:48:08.615902 sedna kernel: ACPI: EC: EC stopped Nov 06 06:48:08.615935 sedna kernel: PM: Saving platform NVS memory Nov 06 06:48:08.615965 sedna kernel: Disabling non-boot CPUs ... Nov 06 06:48:08.616002 sedna kernel: IRQ 41: no longer affine to CPU1 Nov 06 06:48:08.616039 sedna kernel: IRQ 42: no longer affine to CPU1 Nov 06 06:48:08.616071 sedna kernel: IRQ 43: no longer affine to CPU1 Nov 06 06:48:08.616104 sedna kernel: smpboot: CPU 1 is now offline Nov 06 06:48:08.616136 sedna kernel: ACPI: Low-level resume complete Nov 06 06:48:08.616165 sedna kernel: ACPI: EC: EC started Nov 06 06:48:08.616199 sedna kernel: PM: Restoring platform NVS memory Nov 06 06:48:08.616230 sedna kernel: Enabling non-boot CPUs ... Nov 06 06:48:08.616255 sedna kernel: x86: Booting SMP configuration: Nov 06 06:48:08.616284 sedna kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2 Nov 06 06:48:08.616313 sedna kernel: CPU1 is up Nov 06 06:48:08.616338 sedna kernel: ACPI: Waking up from system sleep state S3 Nov 06 06:48:08.616374 sedna kernel: ACPI: EC: interrupt unblocked Nov 06 06:48:08.616405 sedna kernel: ACPI: EC: event unblocked Nov 06 06:48:08.616435 sedna kernel: sd 0:0:0:0: [sda] Starting disk Nov 06 06:48:08.616612 sedna kernel: elan_i2c i2c-ELAN:00: invalid report id data (ff) Nov 06 06:48:08.616821 sedna kernel: usb 1-3: reset high-speed USB device number 2 using xhci_hcd Nov 06 06:48:08.617097 sedna kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 06 06:48:08.617134 sedna kernel: ata1.00: configured for UDMA/133 Nov 06 06:48:08.617164 sedna kernel: OOM killer enabled. Nov 06 06:48:08.617198 sedna kernel: Restarting tasks ... done. Nov 06 06:48:08.617227 sedna kernel: PM: suspend exit Nov 06 06:48:12.073184 sedna kernel: wlp1s0: authenticate with 1c:3b:f3:4c:6b:6f Nov 06 06:48:12.081030 sedna kernel: wlp1s0: send auth to 1c:3b:f3:4c:6b:6f (try 1/3) Nov 06 06:48:12.081106 sedna kernel: wlp1s0: authenticated Nov 06 06:48:12.081155 sedna kernel: wlp1s0: associate with 1c:3b:f3:4c:6b:6f (try 1/3) Nov 06 06:48:12.083802 sedna kernel: wlp1s0: RX AssocResp from 1c:3b:f3:4c:6b:6f (capab=0x1511 status=0 aid=3) Nov 06 06:48:12.089026 sedna kernel: wlp1s0: associated Nov 06 06:48:12.139628 sedna kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready [there are no more entries] [then the reboot] $ sudo dmesg Nov 06 06:49:04.835437 sedna kernel: microcode: microcode updated early to revision 0x2f, date = 2019-11-12 Nov 06 06:49:04.835488 sedna kernel: Linux version 5.13.0-20-generic (buildd@lgw01-amd64-013) (gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binut> Nov 06 06:49:04.835508 sedna kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=afb97784-f7dc-4891-8f9b-f6c22831a037 ro mitig> Nov 06 06:49:04.835521 sedna kernel: KERNEL supported cpus: Nov 06 06:49:04.835533 sedna kernel: Intel GenuineIntel Nov 06 06:49:04.835545 sedna kernel: AMD AuthenticAMD Nov 06 06:49:04.835558 sedna kernel: Hygon HygonGenuine Nov 06 06:49:04.835570 sedna kernel: Centaur CentaurHauls Nov 06 06:49:04.835584 sedna kernel: zhaoxin Shanghai Nov 06 06:49:04.835600 sedna kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Nov 06 06:49:04.835613 sedna kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Nov 06 06:49:04.835625 sedna kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format. Nov 06 06:49:04.835636 sedna kernel: BIOS-provided physical RAM map: Nov 06 06:49:04.835649 sedna kernel: BIOS-e820: [mem 0x-0x0009fbff] usable Nov 06 06:49:04.835663 sedna kernel: BIOS-e820: [mem 0x0009fc00-0x0009] reserved Nov 06 06:49:04.835678 sedna kernel: BIOS-e820: [mem 0x000f-0x000f] reserved [etc] -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64
[Kernel-packages] [Bug 1949977] Re: Laptop doesn't return from sleep
** Description changed: I have an HP Pavilion 15-eh0050wm laptop running Kubuntu 21.10 and when I wake it up from sleep, the screen flashes rainbow colours, and the laptop freezes. It doesn't matter if I suspend it with 'systemctl suspend', close the lid or through the desktop. The problem only occurs with kernel version 5.11 and 5.13. I tested it on kernel 5.8 and as far - as I can tell, it wakes up normally. I also tried booting a live 21.10 - live USB, but the problem still occurs. + as I can tell, it wakes up normally. I also tried booting a 21.10 live + USB, but the problem still occurs. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: hristos_joia 5029 F pulseaudio - /dev/snd/controlC1: hristos_joia 5029 F pulseaudio - /dev/snd/controlC0: hristos_joia 5029 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: hristos_joia 5029 F pulseaudio + /dev/snd/controlC1: hristos_joia 5029 F pulseaudio + /dev/snd/controlC0: hristos_joia 5029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Nov 5 15:54:47 2021 InstallationDate: Installed on 2021-03-11 (239 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Laptop 15-eh0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=82a2f784-953e-4903-98a7-b49423372c8b ro nouveau.modeset=0 quiet splash acpi=force vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.13.0-20-generic N/A - linux-backports-modules-5.13.0-20-generic N/A - linux-firmware 1.201.1 + linux-restricted-modules-5.13.0-20-generic N/A + linux-backports-modules-5.13.0-20-generic N/A + linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: - + dmi.bios.date: 10/16/2020 dmi.bios.release: 15.5 dmi.bios.vendor: AMI dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 87C5 dmi.board.vendor: HP dmi.board.version: 35.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 35.24 dmi.modalias: dmi:bvnAMI:bvrF.05:bd10/16/2020:br15.5:efr35.24:svnHP:pnHPPavilionLaptop15-eh0xxx:pvr:sku183G1UA#ABA:rvnHP:rn87C5:rvr35.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eh0xxx dmi.product.sku: 183G1UA#ABA dmi.sys.vendor: HP -- 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/1949977 Title: Laptop doesn't return from sleep Status in linux package in Ubuntu: Confirmed Bug description: I have an HP Pavilion 15-eh0050wm laptop running Kubuntu 21.10 and when I wake it up from sleep, the screen flashes rainbow colours, and the laptop freezes. It doesn't matter if I suspend it with 'systemctl suspend', close the lid or through the desktop. The problem only occurs with kernel version 5.11 and 5.13. I tested it on kernel 5.8 and as far as I can tell, it wakes up normally. I also tried booting a 21.10 live USB, but the problem still occurs. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: hristos_joia 5029 F pulseaudio /dev/snd/controlC1: hristos_joia 5029 F pulseaudio /dev/snd/controlC0: hristos_joia 5029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Nov 5 15:54:47 2021 InstallationDate: Installed on 2021-03-11 (239 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP HP Pavilion Laptop 15-eh0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=82a2f784-953e-4903-98a7-b49423372c8b ro nouveau.modeset=0 quiet splash acpi=force vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/16/2020 dmi.bios.release: 15.5 dmi.bios.vendor: AMI dmi.bios.version: F.05
[Kernel-packages] [Bug 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
Okay, so I added to my GRUB kernel parameters string: acpi_sleep=s3_bios,s3_mode per here: - http://powersave.sourceforge.net/powersave/Suspend2Ram.html - https://wiki.ubuntu.com/Kernel/KernelBootParameters and ran GRUB config. And set myself back to: echo deep | sudo tee /sys/power/mem_sleep And it appears to be working! I noticed SOMETHING seemed off because when my computer would "go to sleep" in the new version, the power light would stay bright blue (just like when it was on). So it seems to be crashing on suspend somewhere. Because now, when I hit suspend, it does the normal blinking yellow for the same LED. -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-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: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+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 1910927] Re: Suspend stopped working since kernel 5.4 (ubuntu 20.04)
I JUST got the "you have a new version available" and clicked update last night. From ~21.xx to 21.10 and it won't come back from deep sleep. Acer C740P laptop with Ubuntu desktop. Switching to: echo shallow | sudo tee /sys/power/mem_sleep from the previous comment allows me to come back. However, I'm almost certain this is a lesser level of suspend than WAS working on 21.xx because now it comes back on _instantly_ and it never did it that fast before. So I imagine that means my computer is barely suspended at all in this mode. The last line of dmesg was : acpi: EC: interrupt blocked using: $ journalctl -o short-precise -k -b -1 to get the previous dmesg log. But that ACPI line may be innocuous and not the key failure. I'm not aware of any other useful log locations. Also a tool called pm- suspend seem to sleep and come back just fine. -- 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/1910927 Title: Suspend stopped working since kernel 5.4 (ubuntu 20.04) Status in linux package in Ubuntu: Confirmed Bug description: Suspend was working on ubuntu 18.04 with kernel 4.15.0-128. After upgrade to ubuntu 20.04, suspend is not working. The device is on black screen, fully powered and not responding any longer. I can still boot the old kernel 4.15.0-128 from ubuntu 18.04, suspend is working with this kernel! I tested kernel 5.4.0-60 and 5.8.0-36 from hwe. With both kernels, suspend is broken on my older device with Core2Duo. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu4020 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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 nouveaudrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-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: 04/01/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 10LI.M008.20100401.KSJ dmi.board.name: R510/P510 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10LI.M008.20100401.KSJ:bd04/01/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR510/P510:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR510/P510:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R510/P510 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910927/+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 1661987] Re: Wrong colours on some monitors via USB-C to HDMI
I have the same problem on Hirsute Hippo. I am on a Lenovo Yoga 730, connecting to a Coms projector from usb-c through a lenovo usb-c to hdmi adapter that was included with the laptop. I have had no trouble before connecting from the same laptop through the included usb-c to VGA adapter. I cannot get the colours right even by having the projector connected on boot. This laptop also has intel graphics. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-edge in Ubuntu. https://bugs.launchpad.net/bugs/1661987 Title: Wrong colours on some monitors via USB-C to HDMI Status in Linux: New Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.04.1 on my Dell XPS 13 9360 and I'm experiencing some issues with external displays. I bought two adapters from Aukey: USB-C to VGA and USB-C to HDMI (USB-C is the only port that I can use for video output on my computer). USB-C to VGA work flawlessly with all display I tested. USB-C to HDMI has issues with some displays. Sound works great but with some displays (such as on 2 24" Samsung TV monitors) colors are rendered wrong, like if a 16-bit palette is used (this picture posted by another user gives an idea of the problem: https://i.stack.imgur.com/KY44f.jpg). If I connect the display BEFORE turning it on and then turn it on it works correctly (until any video setting option is changed... then I get weird colours again). When I get weird colours if I turn the monitor off and on I get correct colours (until a change in video mode options). However on some other displays it works correctly all the time, such as on a 40" Toshiba TV. Other users are reporting the same issues with other usb-c to hdmi adapters / monitors combinations. The same adapter/monitor combination works flawlessly with Windows 10, and previously I used the same monitor with Ubuntu on my old computer (that had HDMI output) with no problems. I tested some other distros with the same result, so I think it is a kernel-related bug. I tested latest 4.10 rc6 kernel but the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-34-generic 4.8.0-34.36~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 5 17:39:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-05 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1661987/+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 1950036] 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/1950036 Title: cant adjust brightness Status in linux package in Ubuntu: Confirmed Bug description: cant adjust brightness and not that stable when i try to fix it ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jjyj3531434 F pulseaudio /dev/snd/controlC0: jjyj3531434 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 15:27:10 2021 InstallationDate: Installed on 2021-11-05 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: MACHCREATOR MACHCREATOR-A ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=f86cbc27-5454-4a5b-8297-12bc8ddc8e63 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 nomodeset RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05TQLM dmi.board.asset.tag: Tag 12345 dmi.board.name: NL5xRU dmi.board.vendor: MACHCREATOR dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MACHCREATOR dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05TQLM:bd12/15/2020:br7.5:svnMACHCREATOR:pnMACHCREATOR-A:pvrNotApplicable:skuMC-A_R4U:rvnMACHCREATOR:rnNL5xRU:rvrNotApplicable:cvnMACHCREATOR:ct10:cvrN/A: dmi.product.family: MACHCREATOR-A Series dmi.product.name: MACHCREATOR-A dmi.product.sku: MC-A_R4U dmi.product.version: Not Applicable dmi.sys.vendor: MACHCREATOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950036/+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 1950036] [NEW] cant adjust brightness
Public bug reported: cant adjust brightness and not that stable when i try to fix it ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jjyj3531434 F pulseaudio /dev/snd/controlC0: jjyj3531434 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 15:27:10 2021 InstallationDate: Installed on 2021-11-05 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: MACHCREATOR MACHCREATOR-A ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=f86cbc27-5454-4a5b-8297-12bc8ddc8e63 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 nomodeset RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05TQLM dmi.board.asset.tag: Tag 12345 dmi.board.name: NL5xRU dmi.board.vendor: MACHCREATOR dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MACHCREATOR dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05TQLM:bd12/15/2020:br7.5:svnMACHCREATOR:pnMACHCREATOR-A:pvrNotApplicable:skuMC-A_R4U:rvnMACHCREATOR:rnNL5xRU:rvrNotApplicable:cvnMACHCREATOR:ct10:cvrN/A: dmi.product.family: MACHCREATOR-A Series dmi.product.name: MACHCREATOR-A dmi.product.sku: MC-A_R4U dmi.product.version: Not Applicable dmi.sys.vendor: MACHCREATOR ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish -- 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/1950036 Title: cant adjust brightness Status in linux package in Ubuntu: Confirmed Bug description: cant adjust brightness and not that stable when i try to fix it ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-20-generic 5.13.0-20.20 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jjyj3531434 F pulseaudio /dev/snd/controlC0: jjyj3531434 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 15:27:10 2021 InstallationDate: Installed on 2021-11-05 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: MACHCREATOR MACHCREATOR-A ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=f86cbc27-5454-4a5b-8297-12bc8ddc8e63 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 nomodeset RelatedPackageVersions: linux-restricted-modules-5.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 7.5 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.05TQLM dmi.board.asset.tag: Tag 12345 dmi.board.name: NL5xRU dmi.board.vendor: MACHCREATOR dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MACHCREATOR dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.05TQLM:bd12/15/2020:br7.5:svnMACHCREATOR:pnMACHCREATOR-A:pvrNotApplicable:skuMC-A_R4U:rvnMACHCREATOR:rnNL5xRU:rvrNotApplicable:cvnMACHCREATOR:ct10:cvrN/A: dmi.product.family: MACHCREATOR-A Series dmi.product.name: MACHCREATOR-A dmi.product.sku: MC-A_R4U dmi.product.version: Not Applicable dmi.sys.vendor: MACHCREATOR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950036/+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
