[Kernel-packages] [Bug 1978380] [NEW] External monitor not detected
You have been subscribed to a public bug: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- External monitor not detected https://bugs.launchpad.net/bugs/1978380 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978380] Re: External monitor not detected
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978380 Title: External monitor not detected Status in linux package in Ubuntu: New Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978380/+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 1978380] 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/1978380 Title: External monitor not detected Status in linux package in Ubuntu: Confirmed Bug description: Hello. I have a laptop Lenovo Legion Y540-15IRH (81SX00EVRA) with Hybrid graphics. OS: 20.04.4 LTS and Windows 10 in dual boot. BIOS is set to Switchable Graphics, meaning Hybrid. NVidia PRIME profile is set to Intel (power saving). So the problem is that on Ubuntu system doesn't detect an external monitor through HDMI port. When PRIME profile was set to NVidia best Performance - it was able to detect the external monitor. But as I am not playing games anymore - I don't want to use power-consuming and noisy discrete RTX 2060. So I switched to integrated Intel UHD Graphics 630. What should I do in order OS to detect an external monitor? Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:41:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.13.0-44-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.13.0-48-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-44-generic, x86_64: installed nvidia, 470.129.06, 5.13.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffd] NVIDIA Corporation TU106M [GeForce RTX 2060 Mobile] [10de:1f11] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU106M [GeForce RTX 2060 Mobile] [17aa:3ffd] InstallationDate: Installed on 2020-10-21 (597 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81SX ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic root=UUID=96af554d-dedb-4846-b7ca-651771269b4c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2022 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH:skuLENOVO_MT_81SX_BU_idea_FM_LegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978380/+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 1977684] Re: After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network
Thanks for your help. Obviously this seems to be the reason for the bug. I blacklisted the ucsi_acpi module and the system boots correctly. Hopefully there will be a backport for the 5.15. kernel so that I can remove the blacklist. Otherwise I have to wait for an Ubuntu distro with 5.16. kernel. Again thanks for your effort. -- 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/1977684 Title: After Upgrade to 22.04. System does not boot into graphical mode without being connected to the network Status in linux package in Ubuntu: Incomplete Bug description: After long wait time many systemd services fail with a timeout. Connecting to a network via Ethernet does not make the boot continuing. When the network cable is connected before booting the boot process works fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:32:01 2022 InstallationDate: Installed on 2022-01-25 (131 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to jammy on 2022-05-20 (15 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977684/+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 1978407] [NEW] package linux-image-5.15.0-37-generic 5.15.0-37.39 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
Public bug reported: Plusieurs erreurs dans le package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jm 1773 F pulseaudio /dev/snd/pcmC1D0p: jm 1773 F...m pulseaudio /dev/snd/controlC0: jm 1773 F pulseaudio CasperMD5CheckResult: pass Date: Sun Jun 12 12:05:27 2022 ErrorMessage: installed linux-image-5.15.0-37-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-21 (263 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9fd3ff88-9fe8-457d-8f89-5c1a3ce3a6ff ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 RfKill: SourcePackage: linux-signed Title: package linux-image-5.15.0-37-generic 5.15.0-37.39 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA GAMING-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd08/08/2018:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1978407 Title: package linux-image-5.15.0-37-generic 5.15.0-37.39 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 Status in linux-signed package in Ubuntu: New Bug description: Plusieurs erreurs dans le package ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-37-generic 5.15.0-37.39 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jm 1773 F pulseaudio /dev/snd/pcmC1D0p: jm 1773 F...m pulseaudio /dev/snd/controlC0: jm 1773 F pulseaudio CasperMD5CheckResult: pass Date: Sun Jun 12 12:05:27 2022 ErrorMessage: installed linux-image-5.15.0-37-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-09-21 (263 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9fd3ff88-9fe8-457d-8f89-5c1a3ce3a6ff ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu7 RfKill: SourcePackage: linux-signed Title: package linux-image-5.15.0-37-generic 5.15.0-37.39 failed to install/upgrade: run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.release: 5.13 dmi.bios.vendor: Am
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
Installing the 5.18.2 kernel eliminates the problem, but my laptop is overheating with no applications running. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy
In deed. It's a good question why it is taking so long between proposed and updates repositories. Anyone knows why the delay? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1969247 Title: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy Status in Native ZFS for Linux: Fix Released Status in mysql-8.0 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Jammy: Fix Committed Bug description: [Summary] When running Jammy on zfs or LXD with a zfs pool on a Jammy host, fallocate creates a zero-sized file. The issue was originally found when installing mysql on LXD, where fallocate would create a zero-sized ib_logfile1 file. The original information in this bug is based on that. [Steps to Reproduce] touch foo.img fallocate -z -l 10M foo.img ls -la foo.img On a non-zfs Jammy system this will show something like: -rw-r--r-- 1 root root 10M ... while on zfs it will show: -rw-rw-r-- 1 root root 0 ... [Original Description] I came across this error when testing various mysql setups in an LXD container and managed to reproduce it consistently. I'm unable to reproduce on Ubuntu desktop or server though since the prerequisites are probably handled properly there. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 15 21:31:09 2022 Dmesg: ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 KernLog: Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 'public_key.pem', 'ca.pem', 'server-key.pem'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash mem_sleep_default=deep vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)
Nvidia 3090 on an Alienware R10: boots normally, but the desktop appears as shades of bright green. It was corrected when I followed Andrii's solution in comment #28. Thank you Andrii, you just saved me a bunch of time. I had already tried the Live USB and installed 22.04 on my Gigabyte Aorus X5 MD Laptop (Nvidia 1080ti) and I have not encountered this issue on it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1969959 Title: [nouveau] Weird colors after startup (Ubuntu 22.04) Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: [Workaround/Fix] 1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu. 2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed. [Original Description] I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.470 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:54:05 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7C56 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1978296] Re: System hang with kernel general protection fault
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1978296 Title: System hang with kernel general protection fault Status in linux package in Ubuntu: Confirmed Bug description: My system running up-to-date Xubuntu 22.04 LTS and will frequently crash (several times a day). I found a "general protection fault" in /var/log/syslog. The system will be entirely unresponsive; I cannot escape to TTY and kill whatever offending process it is. I need to press the power button and do a hard shutoff. The system hang is more likely when I open a webpage that taxes the system, but it also sometimes just happens randomly. Hardware is a Dell XPS 15 (the label says P56F, which is a 9550, but sudo lshw says 087C, which is a 9570; not sure if this is relevant). This has an 8th generation i7 core. When googling the error message, I found a similar error message here, also a Dell, but the linked bug appears to have been patched. https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1931509 general protection fault, probably for non-canonical address 0xfffdf0d490323650: [#16] SMP PTI CPU: 4 PID: 19037 Comm: WRRende~ckend#7 Tainted: P DO 5.15.0-37-generic #39-Ubuntu Hardware name: Dell Inc. XPS 15 9570/0D0T05, BIOS 1.23.0 12/02/2021 RIP: 0010:rmqueue+0x44a/0xba0 Code: 04 49 8b 46 10 49 01 db 49 39 c3 0f 84 2f 01 00 00 48 be 00 01 00 00 00 00 ad de 49 8b 46 10 48 8b 08 48 8b 50 08 4c 8d 40 f8 <48> 89 51 08 48 89 0a 48 89 30 48 83 c6 22 48 89 70 08 41 83 fd 1f RSP: 0018:a945044d7750 EFLAGS: 00010093 RAX: f0d490323608 RBX: 90c62c536580 RCX: fffdf0d490323648 RDX: 90c62c5365a0 RSI: dead0100 RDI: 90c63c7d6b80 RBP: a945044d7820 R08: f0d490323600 R09: 0001 R10: 0293 R11: 90c62c5365a0 R12: 90c63c7d6b80 R13: R14: 90c62c536590 R15: 0002d588 FS: () GS:90c62c50() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f6d61d7d910 CR3: 0003944a4004 CR4: 003706e0 Call Trace: ? cpumask_next_and+0x24/0x30 ? cpumask_next_and+0x24/0x30 ? update_sg_lb_stats+0x78/0x570 ? update_sg_lb_stats+0x78/0x570 get_page_from_freelist+0xd1/0x520 __alloc_pages+0x17e/0x320 alloc_pages_vma+0x9d/0x380 wp_page_copy+0x7b/0x570 ? find_busiest_group+0x75/0x190 do_wp_page+0xca/0x2e0 handle_pte_fault+0x20b/0x230 __handle_mm_fault+0x3c7/0x700 handle_mm_fault+0xd8/0x2c0 do_user_addr_fault+0x1c5/0x670 exc_page_fault+0x77/0x160 asm_exc_page_fault+0x1e/0x30 RIP: 0010:__put_user_nocheck_4+0x3/0x11 Code: 00 00 48 39 d9 73 54 0f 01 cb 66 89 01 31 c9 0f 01 ca c3 0f 1f 44 00 00 48 bb fd ef ff ff ff 7f 00 00 48 39 d9 73 34 0f 01 cb <89> 01 31 c9 0f 01 ca c3 66 0f 1f 44 00 00 48 bb f9 ef ff ff ff 7f RSP: 0018:a945044d7c80 EFLAGS: 00050293 RAX: RBX: 7fffeffd RCX: 7f6d61d7d910 RDX: RSI: 90c2da579980 RDI: 7f6d61d7d910 RBP: a945044d7ca0 R08: 0009 R09: 7f6d61d7d920 R10: 0027 R11: R12: 90c3c2db9940 R13: 90c2da579980 R14: R15: 90c3c2db9940 ? mm_release+0xad/0xd0 exit_mm_release+0x23/0x30 exit_mm+0x3c/0x1d0 do_exit+0x1e0/0x3c0 do_group_exit+0x3b/0xb0 get_signal+0x150/0x900 arch_do_signal_or_restart+0xda/0x100 ? do_futex+0x13d/0x1d0 ? __x64_sys_futex+0x78/0x1e0 exit_to_user_mode_loop+0xc4/0x160 exit_to_user_mode_prepare+0x9c/0xb0 syscall_exit_to_user_mode+0x27/0x50 do_syscall_64+0x69/0xc0 ? do_syscall_64+0x69/0xc0 ? exit_to_user_mode_prepare+0x37/0xb0 ? syscall_exit_to_user_mode+0x27/0x50 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? __do_sys_sched_yield+0xe/0x20 ? do_syscall_64+0x69/0xc0 ? irqentry_exit+0x19/0x30 ? exc_page_fault+0x89/0x160 ? asm_exc_page_fault+0x8/0x30 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f6dc641ca3d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48 RSP: 002b:7f6d61d7aeb8 EFLAGS: 0246 ORIG_RAX: 00ca RAX: fe00 RBX: RCX: 7f6dc641ca3d RDX: RSI: 0080 RDI: 7f6d237e6368 RBP: 7f6d237e6368 R08: 7f6d443dd100 R09: 0060 R10: R11: 0246 R12: 7f6d237e6340 R13: 7f6dc641ca20 R14: 7f6d61d7afd0 R15: 7f6d61d7af40 Modules linked in: uhid ccm rfcomm nvidia_uvm(PO) cmac algif
[Kernel-packages] [Bug 1978413] [NEW] For nvidia-graphics-drivers-510-510.73.05-0ubuntu0 drivers from version 20.04 - no i386 packages, which prevents the use of 32-bit applications - including imposs
Public bug reported: For nvidia-graphics-drivers-510-510.73.05-0ubuntu0 drivers from version 20.04 - no i386 packages, which prevents the use of 32-bit applications - including impossible to run e.g. Steam ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1978413 Title: For nvidia-graphics-drivers-510-510.73.05-0ubuntu0 drivers from version 20.04 - no i386 packages, which prevents the use of 32-bit applications - including impossible to run e.g. Steam Status in linux-restricted-modules package in Ubuntu: New Bug description: For nvidia-graphics-drivers-510-510.73.05-0ubuntu0 drivers from version 20.04 - no i386 packages, which prevents the use of 32-bit applications - including impossible to run e.g. Steam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1978413/+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 1978416] [NEW] External USB webcam is not working
Public bug reported: Hello, I'm trying to connect Hikvision DS-U02 USB Webcam. It worked for once after trying multiple times, then it stopped working again. It worked when I connected it to a USB 2.0 port and now it's not working there as well. The device is showing up in lsbsb and dmseg, but not showing in "v4l2-ctl --list-devices". error in dmesg: [10856.771936] usb 3-4: new high-speed USB device number 13 using xhci_hcd [10856.929763] usb 3-4: New USB device found, idVendor=2bdf, idProduct=0280, bcdDevice=50.00 [10856.929772] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10856.929776] usb 3-4: Product: 1080P Web Camera [10856.929779] usb 3-4: Manufacturer: SN0002 [10856.929781] usb 3-4: SerialNumber: SN0002 [10856.930669] usb 3-4: Found UVC 1.00 device 1080P Web Camera (2bdf:0280) [10856.932435] uvcvideo 3-4:1.1: Failed to query (129) UVC probe control : -32 (exp. 26). [10856.932447] uvcvideo 3-4:1.1: Failed to initialize the device (-5). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 12 23:40:45 2022 InstallationDate: Installed on 2020-09-07 (643 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1978416 Title: External USB webcam is not working Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Hello, I'm trying to connect Hikvision DS-U02 USB Webcam. It worked for once after trying multiple times, then it stopped working again. It worked when I connected it to a USB 2.0 port and now it's not working there as well. The device is showing up in lsbsb and dmseg, but not showing in "v4l2-ctl --list-devices". error in dmesg: [10856.771936] usb 3-4: new high-speed USB device number 13 using xhci_hcd [10856.929763] usb 3-4: New USB device found, idVendor=2bdf, idProduct=0280, bcdDevice=50.00 [10856.929772] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [10856.929776] usb 3-4: Product: 1080P Web Camera [10856.929779] usb 3-4: Manufacturer: SN0002 [10856.929781] usb 3-4: SerialNumber: SN0002 [10856.930669] usb 3-4: Found UVC 1.00 device 1080P Web Camera (2bdf:0280) [10856.932435] uvcvideo 3-4:1.1: Failed to query (129) UVC probe control : -32 (exp. 26). [10856.932447] uvcvideo 3-4:1.1: Failed to initialize the device (-5). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-48-generic 5.13.0-48.54~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 12 23:40:45 2022 InstallationDate: Installed on 2020-09-07 (643 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1978416/+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 1953554] Re: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out
I am also hitting this same issue, with the same USB ethernet device that the bug opener is also using. According to additional discussion here, https://forums.raspberrypi.com/viewtopic.php?t=282750, and here, https://github.com/raspberrypi/linux/issues/3401, the bug appears to still be active. Any chance Canonical can work with the raspberrypi linux project to get this fix upstream? This happened on an adapter connected to a 10/100 ethernet switch providing connectivity for two devices. I can provide further logs upon request. my crash is here: Jun 12 11:03:34 [hostname] kernel: ---[ end trace 8279e4d131cf381c ]--- Jun 12 11:03:34 [hostname] kernel: start_kernel+0x4dc/0x510 Jun 12 11:03:34 [hostname] kernel: arch_call_rest_init+0x18/0x20 Jun 12 11:03:34 [hostname] kernel: rest_init+0xdc/0xe8 Jun 12 11:03:34 [hostname] kernel: cpu_startup_entry+0x30/0x78 Jun 12 11:03:34 [hostname] kernel: do_idle+0x214/0x2a0 Jun 12 11:03:34 [hostname] kernel: default_idle_call+0x28/0x6c Jun 12 11:03:34 [hostname] kernel: arch_cpu_idle+0x40/0x238 Jun 12 11:03:34 [hostname] kernel: el1_irq+0x108/0x200 Jun 12 11:03:34 [hostname] kernel: gic_handle_irq+0x5c/0xb0 Jun 12 11:03:34 [hostname] kernel: __handle_domain_irq+0x74/0xc8 Jun 12 11:03:34 [hostname] kernel: irq_exit+0xb4/0xe8 Jun 12 11:03:34 [hostname] kernel: __do_softirq+0x160/0x414 Jun 12 11:03:34 [hostname] kernel: run_timer_softirq+0x1d4/0x590 Jun 12 11:03:34 [hostname] kernel: call_timer_fn+0x40/0x1e8 Jun 12 11:03:34 [hostname] kernel: dev_watchdog+0x3a4/0x3b0 Jun 12 11:03:34 [hostname] kernel: Call trace: Jun 12 11:03:34 [hostname] kernel: x1 : x0 : Jun 12 11:03:34 [hostname] kernel: x3 : cfe85640cdbc x2 : 0004 Jun 12 11:03:34 [hostname] kernel: x5 : x4 : 0001 Jun 12 11:03:34 [hostname] kernel: x7 : x6 : Jun 12 11:03:34 [hostname] kernel: x9 : x8 : 0004 Jun 12 11:03:34 [hostname] kernel: x11: cfe85642e000 x10: cfe85654ba78 Jun 12 11:03:34 [hostname] kernel: x13: 00015934 x12: cfe85654b000 Jun 12 11:03:34 [hostname] kernel: x15: cfe856412db0 x14: Jun 12 11:03:34 [hostname] kernel: x17: x16: Jun 12 11:03:34 [hostname] kernel: x19: x18: Jun 12 11:03:34 [hostname] kernel: x21: 099d2c30b480 x20: cfe856407000 Jun 12 11:03:34 [hostname] kernel: x23: 099d2c30b45c x22: 099d2c30b000 Jun 12 11:03:34 [hostname] kernel: x25: cfe85610d028 x24: 099d338d7740 Jun 12 11:03:34 [hostname] kernel: x27: x26: Jun 12 11:03:34 [hostname] kernel: x29: 800010003d70 x28: 099d338d7680 Jun 12 11:03:34 [hostname] kernel: sp : 800010003d70 Jun 12 11:03:34 [hostname] kernel: lr : dev_watchdog+0x3a4/0x3b0 Jun 12 11:03:34 [hostname] kernel: pc : dev_watchdog+0x3a4/0x3b0 Jun 12 11:03:34 [hostname] kernel: pstate: 6045 (nZCv daif +PAN -UAO) Jun 12 11:03:34 [hostname] kernel: Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT) Jun 12 11:03:34 [hostname] kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C E 5.4.0-1065-raspi #75-Ubuntu Jun 12 11:03:34 [hostname] kernel: videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops ax88179_178a videobuf2_v4l2 snd_bcm2835(CE) videobuf2_common snd_pcm videodev snd_timer mc snd raspberrypi_hwmon vc_sm_cma(CE) rpivid_mem uio_pdrv_genirq ui> Jun 12 11:03:34 [hostname] kernel: Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 ip6table_filter ip6_tables xt_MASQUERADE xt_nat xt_tcpudp xt_recent xt_comment nf_tables ipt_REJECT> Jun 12 11:03:34 [hostname] kernel: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:472 dev_watchdog+0x3a4/0x3b0 Jun 12 11:03:34 [hostname] kernel: NETDEV WATCHDOG: lan1 (ax88179_178a): transmit queue 0 timed out Jun 12 11:03:34 [hostname] kernel: [ cut here ] ** Bug watch added: github.com/raspberrypi/linux/issues #3401 https://github.com/raspberrypi/linux/issues/3401 -- 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/1953554 Title: NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hi, I am facing this problem in Focal with the USB 3.0 Ethernet Gigabit adapter "ASIX Electronics Corp. AX88179 Gigabit Ethernet" (waneth is the name I assigned to this ethernet connected to the cable modem/router): [ cut here ] [94104.121581] NETDEV WATCHDOG: waneth (ax88179_178a): transmit queue 0 timed out [94104.121606] WARNING: CPU: 2 PID: 217952 at net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260 [94104.121615] Modules linked in: binfmt_misc xt_recent nfnetlink nls_iso8859_
[Kernel-packages] [Bug 1976188] Re: Touchpad NOT Working
Should be fixed by kernel v5.19-rc1. -- 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/1976188 Title: Touchpad NOT Working Status in linux package in Ubuntu: Confirmed Bug description: No touchpad in /proc/bus/input/devices (attached file). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fushen 1487 F pulseaudio CasperMD5CheckResult: pass Date: Sun May 29 23:49:30 2022 InstallationDate: Installed on 2022-04-10 (49 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 81YJ ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=d839f42c-bcdf-4d4b-9b89-b2f1e4e47592 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-05-17 (12 days ago) dmi.bios.date: 05/09/2022 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DSCN36WW(V1.22) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0L77769 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo XiaoXinAir-14IIL 2020 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrDSCN36WW(V1.22):bd05/09/2022:br1.36:efr1.36:svnLENOVO:pn81YJ:pvrLenovoXiaoXinAir-14IIL2020:rvnLENOVO:rnLNVNB161216:rvrSDK0L77769WIN:cvnLENOVO:ct10:cvrLenovoXiaoXinAir-14IIL2020:skuLENOVO_MT_81YJ_BU_idea_FM_XiaoXinAir-14IIL2020: dmi.product.family: XiaoXinAir-14IIL 2020 dmi.product.name: 81YJ dmi.product.sku: LENOVO_MT_81YJ_BU_idea_FM_XiaoXinAir-14IIL 2020 dmi.product.version: Lenovo XiaoXinAir-14IIL 2020 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976188/+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 1978423] [NEW] cifs: Double free in cifs_smb3_do_mount() when mount fails in cifs_get_root()
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/1978423
[Impact]
When attempting to mount a cifs share, and it fails while the kernel is
attempting to get the root inode, typically in cifs_get_root(), a double
free can occur leading to a general protection fault which panics the
system.
For example, if we try to mount a cifs share with an out of date
kerberos ticket:
[ 479.783182] CIFS: Attempting to mount \\cifs-host\cifs-share
[ 479.791769] CIFS: VFS: Verify user has a krb5 ticket and keyutils is
installed
[ 479.791774] CIFS: VFS: \\cifs-host Send error in SessSetup = -126
[ 479.791777] CIFS: VFS: cifs_read_super: get root inode failed
We hit a general protection fault:
[ 479.826541] general protection fault, probably for non-canonical address
0x2a8e69ddd8028c0: [#1] SMP NOPTI
[ 479.826546] CPU: 9 PID: 8826 Comm: nautilus Kdump: loaded Tainted: P
OE 5.11.0-40-generic #44~20.04.2-Ubuntu
[ 479.826549] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference
Platform, BIOS VMW71.00V.18227214.B64.2106252220 06/25/2021
[ 479.826551] RIP: 0010:kfree+0x5d/0x420
[ 479.826574] CR2: 559ba2c12000 CR3: 002160152002 CR4: 007706e0
[ 479.826597] Call Trace:
[ 479.826598]
[ 479.826603] smb3_cleanup_fs_context_contents.part.0+0x19/0xc0 [cifs]
[ 479.826660] smb3_cleanup_fs_context+0x18/0x30 [cifs]
[ 479.826694] delayed_free+0x1f/0x30 [cifs]
[ 479.826720] rcu_core+0x32a/0x500
[ 479.826725] rcu_core_si+0xe/0x10
[ 479.826727] __do_softirq+0xe0/0x29b
[ 479.826731] asm_call_irq_on_stack+0xf/0x20
[ 479.826734]
[ 479.826735] do_softirq_own_stack+0x3d/0x50
[ 479.826739] irq_exit_rcu+0xa4/0xb0
[ 479.826743] sysvec_apic_timer_interrupt+0x3d/0x90
[ 479.826748] ? asm_sysvec_apic_timer_interrupt+0xa/0x20
[ 479.826750] asm_sysvec_apic_timer_interrupt+0x12/0x20
[ 479.826753] RIP: 0033:0x7f410e544e98
[Fix]
The issue happens because we fall through a goto label, and free the
same cifs_sb->ctx pointer twice. The first happens when we fall through
out_super to out:
790 struct dentry *
791 cifs_smb3_do_mount(struct file_system_type *fs_type,
792 int flags, struct smb3_fs_context *old_ctx)
793 {
...
883 out_super:
884 deactivate_locked_super(sb);
885 out:
886 if (cifs_sb) {
887 kfree(cifs_sb->prepath);
888 smb3_cleanup_fs_context(cifs_sb->ctx);
889 kfree(cifs_sb);
890 }
891 return root;
892 }
The second happens in deactivate_locked_super() when we eventually make
way to delayed_free() after many function calls inbetween:
3779 static void delayed_free(struct rcu_head *p)
3780 {
3781 struct cifs_sb_info *cifs_sb = container_of(p, struct cifs_sb_info,
rcu);
3782
3783 unload_nls(cifs_sb->local_nls);
3784 smb3_cleanup_fs_context(cifs_sb->ctx);
3785 kfree(cifs_sb);
3786 }
smb3_cleanup_fs_context() frees cifs_sb->ctx, as well as all of its
pointers in the struct.
I came across the following mailing list discussion about a double free
occurring during cifs_smb3_do_mount() when we fail to get a reference to
a root dentry [2][3].
[2] https://www.spinics.net/lists/linux-cifs/msg24485.html
[3] https://www.spinics.net/lists/linux-cifs/msg24486.html
For the mailing list discussion, there is a patch submitted [4], and it
was merged into mainline in 5.17-rc5 in the below commit:
[4] https://www.spinics.net/lists/linux-cifs/msg24487.html
commit 3d6cc9898efdfb062efb74dc18cfc700e082f5d5
Author: Ronnie Sahlberg
Date: Fri Feb 11 02:59:15 2022 +1000
Subject: cifs: fix double free race when mount fails in cifs_get_root()
Link:
https://github.com/torvalds/linux/commit/3d6cc9898efdfb062efb74dc18cfc700e082f5d5
This was fixed-released in 5.13.0-48-generic and 5.15.0-23-generic.
[Testcase]
Attempt to mount a cifs share where it would fail during the initial
mount, e.g. attempting to mount a cifs share with kerberos
authentication, with an out of date or invalid kerberos ticket.
[Where problems could occur]
The fix adds a return to the out_super label, to prevent fallthrough to
out. All resources will still be cleaned up correctly through the call
to deactivate_locked_super(), which will eventually reach delayed_free()
and free the resources there, so there won't be any memory leaks of any
sort that arise due to the patch.
If a regression were to occur, it would affect users of cifs mounts,
that error out and fail during the initial mounting stage.
A workaround would be to correct the issue that prevents mount in the
first place, so it would avoid the teardown code on mount failure.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Fix Released
** Tags: sts
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Also affects: linux (Ubuntu Impish)
[Kernel-packages] [Bug 1977977] [NEW] Blanked screen doesn't wake up after locking, unless a USB mouse is installed
You have been subscribed to a public bug: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy wayland-session -- Blanked screen doesn't wake up after locking, unless a USB mouse is installed https://bugs.launchpad.net/bugs/1977977 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1977977] Re: Blanked screen doesn't wake up after locking
OK then it sounds like a kernel configuration problem where the system is sleeping some components too deeply to wake up. Do you have 'tlp' installed? If so then it's a tlp bug/feature. Just uninstall tlp. If you don't have 'tlp' installed then you can still tweak which system components are able to wake the machine up in /proc/acpi/wakeup but it's very cryptic to use. Can you provide output from 'lspci' and a copy of your /proc/acpi/wakeup file? ** Summary changed: - Blanked screen doesn't wake up after locking + Blanked screen doesn't wake up after locking, unless a USB mouse is installed ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Summary changed: - Blanked screen doesn't wake up after locking, unless a USB mouse is installed + [Lenovo ThinkPad E580] Blanked screen doesn't wake up after locking, unless a USB mouse is installed -- 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/1977977 Title: [Lenovo ThinkPad E580] Blanked screen doesn't wake up after locking, unless a USB mouse is installed Status in linux package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977977/+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 1845951] Re: ubuntu_lttng_smoke_test failed with B-hwe 5.0 ARM64
5.0 / 5.8 EOL. Closing this bug. ** Changed in: ubuntu-kernel-tests Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845951 Title: ubuntu_lttng_smoke_test failed with B-hwe 5.0 ARM64 Status in ubuntu-kernel-tests: Won't Fix Status in linux package in Ubuntu: Invalid Bug description: Issue found on ARM64 node ms10-34-mcdivittB0-kernel, with B-hwe 5.0 kernel: Running 'dkms status -m lttng-modules | grep installed' lttng-modules, 2.10.5, 5.0.0-30-generic, aarch64: installed Running '/home/ubuntu/autotest/client/tests/ubuntu_lttng_smoke_test/ubuntu_lttng_smoke_test.sh' == lttng smoke test of session create/destroy == Error: Session daemon terminated with an error (exit status: 1) Error: Problem occurred while launching session daemon (/usr/bin/lttng-sessiond) Spawning a session daemon FAILED (lttng create) Error: Command error Error: No session daemon is available Error: Command error FAILED (lttng destroy) == lttng smoke test trace context switches == Error: Session daemon terminated with an error (exit status: 1) Error: Problem occurred while launching session daemon (/usr/bin/lttng-sessiond) Spawning a session daemon FAILED (lttng create) Error: Command error Summary: 0 passed, 4 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845951/+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 1977977] Re: [Lenovo ThinkPad E580] System doesn't wake up after locking, unless a USB mouse is installed
** Summary changed: - [Lenovo ThinkPad E580] Blanked screen doesn't wake up after locking, unless a USB mouse is installed + [Lenovo ThinkPad E580] System doesn't wake up after locking, unless a USB mouse is installed -- 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/1977977 Title: [Lenovo ThinkPad E580] System doesn't wake up after locking, unless a USB mouse is installed Status in linux package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1977977/+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 1954353] Re: aquantia crash
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954353 Title: aquantia crash Status in linux package in Ubuntu: Expired Bug description: this ship is sinking. pro 10 02:19:15 r6 kernel: [ cut here ] pro 10 02:19:15 r6 kernel: Invalid tc 0 (#rx=0, #tx=0) pro 10 02:19:15 r6 kernel: WARNING: CPU: 7 PID: 8168 at drivers/net/ethernet/aquantia/atlantic/aq_vec.c:365 aq_vec_get_sw_stats+0x58/0xb0 [atlantic] pro 10 02:19:15 r6 kernel: Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast atlantic vhost_net vhost vhost_iotlb tap cfg80211 xt_nat veth nf_conntrack_netlink xfrm_user xfrm_algo br_netfilter xt_CHECKSUM xt_MASQUERADE nf_nat_tftp ip6t_rpfilter nft_chain_nat nf_nat nf_conntrack_tftp xt_CT bridge stp llc overlay ip_set binfmt_misc nvidia_uvm(POE) intel_rapl_msr nvidia_drm(POE) intel_rapl_common nvidia_modeset(POE) nvidia(POE) edac_mce_amd snd_hda_codec_realtek kvm_amd snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi kvm snd_usb_audio snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_usbmidi_lib rapl snd_seq_midi snd_seq_midi_event snd_hda_codec snd_rawmidi snd_hda_core mc input_leds snd_hwdep joydev zenpower(OE) eeepc_wmi mxm_wmi wmi_bmof efi_pstore k10temp ccp snd_pcm drm_kms_helper snd_seq cec rc_core snd_seq_device snd_timer fb_sys_fops syscopyarea sysfillrect snd sysimgblt soundcore mac_hid ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 pro 10 02:19:15 r6 kernel: xt_LOG nf_log_syslog nft_limit sch_fq_codel xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter nct6775 hwmon_vid nf_tables msr nfnetlink parport_pc ppdev lp parport drm sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid mfd_aaeon asus_wmi sparse_keymap video crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd ahci libahci igb nvme i2c_piix4 xhci_pci dca xhci_pci_renesas i2c_algo_bit macsec nvme_core wmi [last unloaded: atlantic] pro 10 02:19:15 r6 kernel: CPU: 7 PID: 8168 Comm: telegraf Tainted: P OE 5.13.0-21-generic #21-Ubuntu pro 10 02:19:15 r6 kernel: Hardware name: System manufacturer System Product Name/PRIME X570-PRO, BIOS 4021 08/09/2021 pro 10 02:19:15 r6 kernel: RIP: 0010:aq_vec_get_sw_stats+0x58/0xb0 [atlantic] pro 10 02:19:15 r6 kernel: Code: 5d 41 5e 5d c3 8b 4f 18 39 cb 72 2e 80 3d e9 f1 01 00 00 75 e5 89 de 48 c7 c7 c0 b6 1a c3 c6 05 d7 f1 01 00 01 e8 27 f1 63 f0 <0f> 0b 41 3b 5c 24 1c 73 c7 41 39 5c 24 18 76 c0 4c 8d 2c 9b 4c 89 pro 10 02:19:15 r6 kernel: RSP: 0018:9cde44da3bd8 EFLAGS: 00010286 pro 10 02:19:15 r6 kernel: RAX: RBX: RCX: 0027 pro 10 02:19:15 r6 kernel: RDX: 8a75febd89c8 RSI: 0001 RDI: 8a75febd89c0 pro 10 02:19:15 r6 kernel: RBP: 9cde44da3bf8 R08: R09: 9cde44da39c8 pro 10 02:19:15 r6 kernel: R10: 9cde44da39c0 R11: b4b55268 R12: 8a67a6ee2000 pro 10 02:19:15 r6 kernel: R13: 0001 R14: 9cde4027e0b0 R15: 9cde4027e000 pro 10 02:19:15 r6 kernel: FS: 7f06baffd640() GS:8a75febc() knlGS: pro 10 02:19:15 r6 kernel: CS: 0010 DS: ES: CR0: 80050033 pro 10 02:19:15 r6 kernel: CR2: 00c002abe000 CR3: 000115e44000 CR4: 00750ee0 pro 10 02:19:15 r6 kernel: PKRU: 5554 pro 10 02:19:15 r6 kernel: Call Trace: pro 10 02:19:15 r6 kernel: aq_nic_get_stats+0x1a5/0x1f0 [atlantic] pro 10 02:19:15 r6 kernel: aq_ethtool_stats+0x37/0x60 [atlantic] pro 10 02:19:15 r6 kernel: ethtool_get_stats+0xc8/0x1a0 pro 10 02:19:15 r6 kernel: dev_ethtool+0x1483/0x19c0 pro 10 02:19:15 r6 kernel: ? __mod_memcg_state.part.0+0x2a/0x30 pro 10 02:19:15 r6 kernel: ? __mod_memcg_lruvec_state+0x27/0xe0 pro 10 02:19:15 r6 kernel: ? inet_ioctl+0x99/0x1c0 pro 10 02:19:15 r6 kernel: ? __mod_lruvec_page_state+0x6e/0xb0 pro 10 02:19:15 r6 kernel: ? netdev_name_node_lookup_rcu+0x6b/0x80 pro 10 02:19:15 r6 kernel: dev_ioctl+0x19d/0x4a0 pro 10 02:19:15 r6 kernel: sock_do_ioctl+0xa6/0x140 pro 10 02:19:15 r6 kernel: sock_ioctl+0x246/0x330 pro 10 02:19:15 r6 kernel: __x64_sys_ioctl+0x91/0xc0 pro 10 02:19:15 r6 kernel: do_syscall_64+0x61/0xb0 pro 10 02:19:15 r6 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 pro 10 02:19:15 r6 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 pro 10 02:19:15 r6 kernel: ? irqentry_exit+0x19/0x30 pro 10 02:19:15 r6 kern
[Kernel-packages] [Bug 1919472] Re: 5.4.0-1040-azure taints kernel with a warning (512)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919472 Title: 5.4.0-1040-azure taints kernel with a warning (512) Status in linux package in Ubuntu: Expired Bug description: Since GitHub Actions has been updated to 5.4.0-1040-azure our CI (https://github.com/checkpoint-restore/criu/issues/1390) fails because a user space test leads to a kernel warning: [ 226.964883] writing to auto_msgmni has no effect [ 226.978221] [ cut here ] [ 226.978226] refcount_t hit zero at __nft_mt_tg_destroy+0x20/0x30 [nft_compat] in kworker/u4:4[103], uid/euid: 0/0 [ 226.978232] WARNING: CPU: 1 PID: 103 at kernel/panic.c:677 refcount_error_report+0x9b/0xab [ 226.978233] Modules linked in: nft_counter xt_mark nft_compat nf_tables raw_diag udp_diag tcp_diag inet_diag netlink_diag af_packet_diag unix_diag veth xfs dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat br_netfilter bridge stp llc xt_owner iptable_security xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter aufs overlay binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua joydev hid_generic crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper hv_netvsc serio_raw pata_acpi hv_balloon hyperv_fb hyperv_keyboard cfbfillrect hid_hyperv cfbimgblt hid cfbcopyarea hv_utils sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4 [ 226.978254] CPU: 1 PID: 103 Comm: kworker/u4:4 Not tainted 5.4.0-1040-azure #42-Ubuntu [ 226.978255] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090008 12/07/2018 [ 226.978260] Workqueue: netns cleanup_net [ 226.978262] RIP: 0010:refcount_error_report+0x9b/0xab [ 226.978264] Code: 00 45 8b 85 c0 08 00 00 48 8b 93 80 00 00 00 49 8d 8d b0 0a 00 00 41 56 41 89 c1 4c 89 e6 48 c7 c7 20 40 91 88 e8 10 00 00 00 <0f> 0b 58 48 8d 65 e0 5b 41 5c 41 5d 41 5e 5d c3 0f 1f 44 00 00 55 [ 226.978265] RSP: :a0768027baa0 EFLAGS: 00010286 [ 226.978266] RAX: RBX: a0768027bbd8 RCX: 0006 [ 226.978267] RDX: 0007 RSI: 0096 RDI: 88d5b8b16580 [ 226.978268] RBP: a0768027bac8 R08: 0406 R09: 0004 [ 226.978269] R10: R11: 0001 R12: 88910e83 [ 226.978270] R13: 88d5b701 R14: R15: 88d5b701 [ 226.978271] FS: () GS:88d5b8b0() knlGS: [ 226.978272] CS: 0010 DS: ES: CR0: 80050033 [ 226.978273] CR2: 7f5cc79e340c CR3: 0001930e8003 CR4: 003706e0 [ 226.978275] DR0: DR1: DR2: [ 226.978276] DR3: DR6: fffe0ff0 DR7: 0400 [ 226.978276] Call Trace: [ 226.978282] ex_handler_refcount+0x50/0x70 [ 226.978283] fixup_exception+0x4a/0x61 [ 226.978286] do_trap+0x4e/0xf0 [ 226.978288] do_error_trap+0x7c/0xb0 [ 226.978290] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978292] do_invalid_op+0x3c/0x50 [ 226.978293] ? nft_target_dump+0xc1/0xcc [nft_compat] [ 226.978296] invalid_op+0x28/0x30 [ 226.978298] RIP: 0010:__nft_mt_tg_destroy+0x20/0x30 [nft_compat] [ 226.978299] Code: c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 f3 f0 ff 0d bc 2e 00 00 0f 84 c0 10 00 00 0f 88 ba 10 00 00 fb f7 f4 c6 48 8b 3b e8 43 5c 0a c7 5b 5d c3 0f 1f 44 00 00 55 [ 226.978300] RSP: :a0768027bc88 EFLAGS: 00010246 [ 226.978301] RAX: RBX: 88d4e683f6d8 RCX: c07f2000 [ 226.978301] RDX: 88d4e683f6d8 RSI: 88d4e683f6d8 RDI: c07f7100 [ 226.978302] RBP: a0768027bc90 R08: ff00 R09: 88d4ec58 [ 226.978303] R10: 88d4e683f780 R11: 0001 R12: 88d4e683f6d8 [ 226.978304] R13: c07f7100 R14: dead0100 R15: 88d4e683f8a0 [ 226.978307] __nft_match_destroy.isra.0+0x5b/0x80 [nft_compat] [ 226.978309] nft_match_destroy+0x1c/0x20 [nft_compat] [ 226.978313] nf_tables_expr_destroy+0x1f/0x30 [nf_tables] [ 226.978316] nf_tables_rule_destroy+0x49/0x70 [nf_tables] [ 226.978320] nf_tables_exit_net+0x1ae/0x3e0 [nf_tables] [ 226.978323] ops_exit_list.isra.0+0x3b/0x70 [ 226.978325] cleanup_net+0x1f0/0x300 [ 226.978329] process_one_work+0x1e5/0x3a0 [ 226.978331] worker_thread+0x4d/0x3f0 [ 226.978333] kthread+0x104/0x140 [ 226.978334] ? process_one_work+0x3a0/0x3a0 [
[Kernel-packages] [Bug 1931952] Re: AtomISP OV2722 sensor not starting
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931952 Title: AtomISP OV2722 sensor not starting Status in linux package in Ubuntu: Expired Bug description: Here is a specific log Jun 13 01:10:21 netbook kernel: videodev: Linux video capture interface: v2.00 Jun 13 01:10:21 netbook kernel: atomisp_gmin_platform: module is from the staging directory, the quality is unknown, you have been warned. Jun 13 01:10:21 netbook kernel: atomisp_gmin_platform: module verification failed: signature and/or required key missing - tainting kernel Jun 13 01:10:21 netbook kernel: atomisp_ov2722: module is from the staging directory, the quality is unknown, you have been warned. Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: gmin: power management provided via Dollar Cove TI PMIC (i2c addr 0x5e) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: gmin_subdev_add: ACPI path is \_SB.I2C2.CAM1 Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: Failed to find EFI variable 808633FB:00_ClkSrc Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: ClkSrc: using default (1) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: Failed to find EFI variable 808633FB:00_CsiPort Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: CsiPort: using default (0) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: Failed to find EFI variable 808633FB:00_CsiLanes Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: CsiLanes: using default (1) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: will handle gpio0 via ACPI Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: will handle gpio1 via ACPI Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: Failed to find EFI gmin variable gmin_V1P8GPIO Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: V1P8GPIO: using default (-1) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: Failed to find EFI gmin variable gmin_V2P8GPIO Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: V2P8GPIO: using default (-1) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: Failed to find EFI variable 808633FB:00_CamClk Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: CamClk: using default (0) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: Will use CLK0 (pmc_plt_clk_0) Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: camera pdata: port: 0 lanes: 1 order: Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: read from offset 0x300a error -121 Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: sensor_id_high = 0x Jun 13 01:10:21 netbook kernel: ov2722 i2c-808633FB:00: ov2722_detect err s_config. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bret913 F pulseaudio /dev/snd/controlC0: bret913 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jun 15 05:48:57 2021 InstallationDate: Installed on 2021-06-12 (2 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210612) Lspci-vt: -[:00]-+-00.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register +-02.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display +-14.0 Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI +-1a.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine \-1f.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M MachineType: TOSHIBA SATELLITE Click Mini L9W-B ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=0ea6c6cc-54e3-4d2b-aa97-ea8d7fd64255 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.198 SourcePackage: linux StagingDrivers: atomisp_ov
[Kernel-packages] [Bug 1887490] Re: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model
Just stating (for my future self any anyone else) that for the other way around (removing features that were never enabled before) there is code that could handle that [1][2]. In a similar fashion libvirt could try to consider older sources before this change as "ok I accept to not insist on this feature and spawn a guest without", but then you'd end up on the new system with guests that appear to have the very same definition but behaving different - that would (other than not being implemented yet) still sound like asking for even more trouble. [1]: https://gitlab.com/libvirt/libvirt/-/commit/52cbfb2186364b1ab64f56e1360dcbc7d8ab85c1 [2]: https://gitlab.com/libvirt/libvirt/-/commit/7e0a3104982c5ba273316d6e39184d28c9f2fc9a -- 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/1887490 Title: [FFe/SRU] Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in qemu source package in Focal: Fix Released Bug description: [Impact] * CPU definitions are added to libvirt as these CPUs are known and added to qemu for execution. And due to that over time some are considered missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports three upstream fixes that just add definitions (no control flow changes) [Test Case] * Check if it has an EPYC-Rome entry in /usr/share/libvirt/cpu_map/index.xml and the file included there exists. * Define a guest like: EPYC-Rome You can only "really" start this on a system with the matching HW. But even on others it will change from: error: internal error: Unknown CPU model EPYC-Rome to being unable to start for some features missing. * libvirt probes a system if a named cpu can be used, after the fix this should include EPYC-Rome $ virsh domcapabilities | grep EPYC EPYC-IBPB EPYC [Regression Potential] * Usually these type additions are safe unless they add control flow changes (e.g. to handle yet unknown types of registers or such) but that isn't the case here. A regression if any is to be expected on systems that are close to the newly added type(s). Those will after the update be detected as such if e.g. host-model is used. If then running on a mixed cluster of updated/non-updated systems migrations will only work if the target is updated as well. [Other Info] * This is the first build since glibc 2.32 arrived in groovy, hence we need to be careful of the fix done for bug 1892826. It has to be checked if the linking is fine after the rebuild. The workload still works in groovy despite 2.32 being present (I'd ahve expected it doesn't), so we will keep the revert as-is for now. To be sure that adds two tests that shall be done: - check the linking to point to libtirpc instead of glibc $ eu-readelf -a /usr/lib/libvirt/libvirt_lxc | grep xdr_uint64 | grep GLOBAL Was pointing to glibc, does it still and if so does it work (see below)? - run the autopkgtest cases as the LXC tests would trigger an issue if there is one ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added)
To find a fix that can be released in updates to 22.04 we will need to start by identifying what the last kernel version with the bug was, and the first kernel version with the fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1905142] Re: [amdgpu] When entering sleep mode the monitors turn off then immediately turn back on
Lta, Please open a new bug for your system by running: ubuntu-bug linux This old bug 1905142 is likely to close in a few weeks due to EOL of 21.10: https://wiki.ubuntu.com/Releases -- 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/1905142 Title: [amdgpu] When entering sleep mode the monitors turn off then immediately turn back on Status in linux package in Ubuntu: Confirmed Bug description: every time that happens the following message is shown in syslog: /usr/libexec/gdm-x-session[3330]: (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Uname: Linux 5.8.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 21 18:38:27 2020 DistUpgraded: 2020-11-18 01:07:32,653 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2316] MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-30-generic root=UUID=556540f5-c271-4a31-8207-81a7fcaac401 ro amdgpu.dc=1 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-11-18 (3 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-03-16T23:17:19.931496 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Nov 17 23:04:32 2020 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1905142/+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 1967493] Re: pl2303 serial adapter not recognized
https://lists.ubuntu.com/archives/kernel-team/2022-June/130942.html
** Description changed:
+ [Impact]
+ After switching to a more strict chip type detection for the pl2303
+ USB to serial adaptor driver in commit 8a7bf751 ("USB: serial: pl2303:
+ amend and tighten type detection")
+
+ Device with bcdUSB other than 1.10 and 2.00 will stop working. For
+ example the Cashino PTP-lil/BT24 Slip printer with bcdUSB 1.01.
+
+ [Fix]
+ * e82e7c6dde ("USB: serial: pl2303: fix type detection for odd device")
+
+ This patch can be cherry-picked to all of the affected kernels.
+
+ [Test]
+ Test kernels can be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1967493-pl2303/
+
+ F-5.13 has been tested by the bug reporter and the result is good.
+
+ [Where problems could occur]
+ Change limited to this specific driver (and even to this specific type
+ of devices), if anything goes wrong the adaptor might be not working.
+
+
+ [Original Bug Report]
Hi
After upgrading the Linux kernel from 5.11.0-27 to 5.13.0-37 a device
that uses a pl2303 usb serial chip no longer works.
This seems very similar to bug 1959110, and according to that it should
be fixed, but somehow it's not.
# uname -a
Linux GAU23LD04 5.13.0-37-generic #42~20.04.1-Ubuntu SMP Tue Mar 15
15:44:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
# journalctl -b -k -g pl2303 -o cat
usbcore: registered new interface driver pl2303
usbserial: USB Serial support registered for pl2303
pl2303 1-12:1.0: pl2303 converter detected
pl2303 1-12:1.0: unknown device type, please report to
linux-...@vger.kernel.org
- # udevadm info /sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
+ # udevadm info /sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
P: /devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
L: 0
E: DEVPATH=/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.0
E: DEVTYPE=usb_interface
E: PRODUCT=67b/2303/300
E: TYPE=0/0/0
E: INTERFACE=255/0/0
E: MODALIAS=usb:v067Bp2303d0300dc00dsc00dp00icFFisc00ip00in00
E: SUBSYSTEM=usb
E: USEC_INITIALIZED=56177916
E: ID_VENDOR_FROM_DATABASE=Prolific Technology, Inc.
E: ID_MODEL_FROM_DATABASE=PL2303 Serial Port
E: ID_PATH=pci-:00:14.0-usb-0:12:1.0
E: ID_PATH_TAG=pci-_00_14_0-usb-0_12_1_0
E: ID_MM_TTY_MANUAL_SCAN_ONLY=1
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.17 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-oem-5.14 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Focal)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967493
Title:
pl2303 serial adapter not recognized
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux-oem-5.17 source package in Focal:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux-oem-5.17 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-oem-5.14 source package in Jammy:
[Kernel-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
This bug is fixed already in 42.1. If you still have problems then
please open a new bug by running:
ubuntu-bug gnome-shell
and we can work from there.
--
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/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Released
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1975566] [NEW] [radeon] GUI becomes slow and hangs with radeon, but not with amdgpu
You have been subscribed to a public bug: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax 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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.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. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy performance ubuntu uec-images -- [radeon] GUI becomes slow and hangs with radeon, but not with amdgpu https://bugs.launchpad.net/bugs/1975566 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1975566] Re: [radeon] GUI becomes slow and hangs with radeon, but not with amdgpu
** Summary changed: - [radeon] GUI becomes slow and hangs in 5.18.0-051800-generic with radeon, but not with amdgpu + [radeon] GUI becomes slow and hangs with radeon, but not with amdgpu ** Package changed: ubuntu => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975566 Title: [radeon] GUI becomes slow and hangs with radeon, but not with amdgpu Status in linux package in Ubuntu: New Bug description: Recently I upgraded my machine and moved my GPU over from the old (Intel something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I did a fresh Ubuntu install (server) and added packages to get my GUI rolling (lightdm + awesomewm), just like before. The graphics cards is a "Gigabyte GV-R928XOC-3GD Rev. 2.0" which has the R9 280X chip (TAHITI / Southern Islands). On my old system, I could play games with Vulkan, but with this system it doesn't work. If I run the 'default' setup, it uses the 'radeon' kernel module. The first couple of seconds I get reasonable performance (glxgears @ 60 FPS), then it suddenly drop to 4 and motion is almost not visible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg (not installed) Uname: Linux 5.18.0-051800-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 24 06:49:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Tahiti XTL [Radeon R9 280X OC] [1458:3001] InstallationDate: Installed on 2022-05-14 (9 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.18.0-051800-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P2.30 dmi.board.name: B550 Phantom Gaming-ITX/ax 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:bvnAmericanMegatrendsInternational,LLC.:bvrP2.30:bd02/25/2022:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming-ITX/ax:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.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. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975566/+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 1978349] [NEW] Monitors sometimes permanently blanked after resume
You have been subscribed to a public bug: Sometimes monitors don't wake up after resume. Happened couple times with Ubuntu 22.04 so far. Journalctl lists only one instance of this, might have failed to save the logs on other times. kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039! 1. (assumedly) occurs when resuming from ram 2. suspend chosen from ui 3. resume by clicking key on keyboard 4.-11. not tested yet with mainline builds, since uncertain about how to reproduce reliably. 12. openssh-server only installed after today's instance, so don't have much debug data beyond what was saved in logs before sysrq-sub. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 23:02:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 4966 F pulseaudio /dev/snd/controlC1: iheino 4966 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerIN
[Kernel-packages] [Bug 1978317] Re: package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
>From DpkgTerminalLog.txt: cat: write error: No space left on device And Df.txt: Filesystem 1K-blocks Used Available Use% Mounted on udev 7619548 07619548 0% /dev tmpfs 1530164 25481527616 1% /run /dev/mapper/ubuntu--vg-root 214943836 138901404 65100788 69% / tmpfs 7650812 07650812 0% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 7650812 07650812 0% /sys/fs/cgroup /dev/sda1 240972239937 0 100% /boot /dev/sdb1 1921802432 397790364 1426320012 22% /mnt/e48119f1-9368-47ef-b6c4-c75639b62498 tmpfs 1530160441530116 1% /run/user/1000 ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1978317 Title: package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: Standard update. This is another variation of numerous bug reports ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.31 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 2080 F pulseaudio /dev/snd/controlC0: chris 2080 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jun 10 14:17:18 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=3eb0cc8f-10d5-466f-ad48-7ad42d84e9b1 InstallationDate: Installed on 2015-12-07 (2377 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-117-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-06-22 (352 days ago) dmi.bios.date: 12/04/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1602:bd12/04/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88X-PRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1978317/+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 1978349] Re: Monitors sometimes permanently blanked after resume
In case there's more than just that amdgpu kernel crash happening please also run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - Monitors sometimes permanently blanked after resume + [amdgpu] Monitors sometimes permanently blanked after resume -- 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/1978349 Title: [amdgpu] Monitors sometimes permanently blanked after resume Status in linux package in Ubuntu: Incomplete Bug description: Sometimes monitors don't wake up after resume. Happened couple times with Ubuntu 22.04 so far. Journalctl lists only one instance of this, might have failed to save the logs on other times. kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039! 1. (assumedly) occurs when resuming from ram 2. suspend chosen from ui 3. resume by clicking key on keyboard 4.-11. not tested yet with mainline builds, since uncertain about how to reproduce reliably. 12. openssh-server only installed after today's instance, so don't have much debug data beyond what was saved in logs before sysrq-sub. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 23:02:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 4966 F pulseaudio /dev/snd/controlC1: iheino 4966 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports
