[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
The impish kernel is already fixed and the fix is applied to the current
kernel in released. Comment #142 is referring to linux-oem-5.14 in
focal, that also has the fix, so it can be ignored.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1958151] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958151 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: New Status in linux source package in Jammy: In Progress Bug description: [Impact] No driver is loaded for MT7922, and fw is missing too. [Fix] Add basic support of MT7922, and add ID of AMD RZ616/RZ608. Enable 160Mhz channel. [Test] Verified on RZ616, it works fine, suspend OK. iperf test result looks fine. Bluetooth works fine. [Where problems could occur] It may break MT7921 wifi support which shares mt7921e driver. Almost the code is specific for MT7922, checking security fw is based on MT7922 fw. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958151/+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 1952222] Re: io_uring regression - lost write request
oem-5.13 will migrate to oem-5.14 next cycle ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: New Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+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 1952222] Re: io_uring regression - lost write request
the fix is in 5.15-rc1 and up, jammy has 5.15.x ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-hwe-5.13 (Ubuntu Impish) 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/195 Title: io_uring regression - lost write request Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: New Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: New Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: There's a regression with io_uring reported against 5.11-5.14 kernels, see: https://lore.kernel.org/io-uring/CABVffEOXe=mhyW_- ynz4z9g_uxvvams662vqjn9ubff9nhw...@mail.gmail.com/T/#m8bf4fdb4c91d8ea231517d9f936d1e4354c40a3b From reading the thread and looking at the history in linux-stable/linux-5.15.y, I assume that Linux 5.15.3 is the first fully fixed version. And 5.10 was not affected. Sadly all other versions are EOL for kernel.org. But ubuntu provides 5.11, 5.13 and 5.14 based kernels, which most likely have the bug. I'm reporting it against linux-hwe-5.13 as that's what I test on most systems, but others e.g. linux-oem-5.13 and linux-oem-5.14 have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+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 1956720] Re: Focal update: upstream stable patchset 2022-01-07
the fix was already in 5.15-rc1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956720 Title: Focal update: upstream stable patchset 2022-01-07 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-01-07 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+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 1956720] Re: Focal update: upstream stable patchset 2022-01-07
simply because it's was never sent for stable ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956720 Title: Focal update: upstream stable patchset 2022-01-07 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-01-07 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+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 1958248] Re: [amdgpu] Screen garbled on login and freezes on unsuspend
*** This bug is a duplicate of bug 1958412 *** https://bugs.launchpad.net/bugs/1958412 The 'quiet' workaround of the other bug does not help for my machine. -- 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/1958248 Title: [amdgpu] Screen garbled on login and freezes on unsuspend Status in linux package in Ubuntu: Confirmed Bug description: 1. The login manager works but as soon as I log in, the screen is filled with colored vertical stripes and is unusable. I found that if I change the screen resolution to the maximum (1920x1080), then the screen is ok. Any other resolution that I've tried (eg (1440x900 used to be my preference) causes the unreadable display and it does not revert back, requiring a reboot. 2. Coming out of suspend, the password entry screen is displayed, but there is no response to keyboard or mouse, requiring a reboot. HP Envy x360 laptop with AMD Ryzen 7 with Radeon graphics Last known kernel that worked is 5.11.0-46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958248/+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 1958620] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: Confirmed Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash 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.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1958518] Re: split some large, lesser-used firmware files into -extra package
** Tags added: kern-2009 -- 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/1958518 Title: split some large, lesser-used firmware files into -extra package Status in linux-firmware package in Ubuntu: New Bug description: The linux-image-generic package depends on linux-firmware which is over half a gigabyte in size installed. I will assume that quite many people do not have netronome hardware which weighs in at almost 150MB of that. I kindly suggest to put such large firmware for less common hardware into its own linux-firmware-extra package which would be recommended by linux-firmare. Comments? I'm willing to help with the packaging provided that the changes have a chance to land. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958518/+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 1958467] Re: focal linux-firmware package omits amdgpu/navi12 firmware
** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Tags added: kern-2008 -- 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/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Triaged Bug description: The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+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 1958620] [NEW] Flickering white/black screen once KMS comes up
Public bug reported: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash 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.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958620 Title: Flickering white/black screen once KMS comes up Status in linux package in Ubuntu: New Bug description: This looks like a regression from the 5.13.0-20-generic kernel to the 5.15.0-17-generic kernel. The display works fine under efifb, but as soon as the DRM drivers are loaded and KMS kicks in the display is replaced by black with flickering white (apparently when what would be on the output changes). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 7134 F pipewire-media- /dev/snd/seq:chris 7133 F pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 21 17:07:08 2022 InstallationDate: Installed on 2021-06-26 (208 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=UUID=ff90803a-eedd-429b-bb78-b713f7c661d6 ro quiet splash 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.13.0-20-generic N/A linux-backports-modules-5.13.0-20-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-10-28 (84 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958620/+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 1956525] Re: amdgpu crash in dp_set_panel_mode from perform_link_training_with_retries
** Package changed: linux (Ubuntu) => linux-hwe-5.11 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1956525 Title: amdgpu crash in dp_set_panel_mode from perform_link_training_with_retries Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: From time to time after waking up the screen on Ubuntu Budgie, the refresh rate goes from 120hz to 48hz followed by a flashing of the screen. With dmesg this output appear: [12947.570681] WARNING: CPU: 6 PID: 891 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:4282 dp_set_panel_mode+0xbb/0xd0 [amdgpu] [12947.571031] Modules linked in: ses enclosure scsi_transport_sas uas usb_storage btrfs blake2b_generic xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nls_iso8859_1 nvidia_uvm(POE) nvidia_drm(POE) nvidia_modeset(POE) intel_rapl_msr intel_rapl_common nvidia(POE) edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi kvm_amd amdgpu snd_seq snd_seq_device iommu_v2 gpu_sched snd_timer drm_ttm_helper ttm kvm snd drm_kms_helper crct10dif_pclmul ghash_clmulni_intel cec rc_core joydev asus_nb_wmi hid_multitouch efi_pstore i2c_algo_bit wmi_bmof aesni_intel fb_sys_fops crypto_simd syscopyarea cryptd sysfillrect glue_helper k10temp soundcore sysimgblt input_leds ccp rapl serio_raw asus_wireless [12947.571130] mac_hid sch_fq_codel msr parport_pc ppdev lp drm parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid_generic mfd_aaeon asus_wmi sparse_keymap crc32_pclmul nvme r8169 ahci i2c_hid xhci_pci xhci_pci_renesas nvme_core libahci i2c_piix4 realtek wmi video hid [12947.571172] CPU: 6 PID: 891 Comm: Xorg Tainted: P OE 5.11.0-44-generic #48~20.04.2-Ubuntu [12947.571178] Hardware name: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT/FX505DT, BIOS FX505DT.316 01/28/2021 [12947.571181] RIP: 0010:dp_set_panel_mode+0xbb/0xd0 [amdgpu] [12947.571538] Code: fe b9 01 00 00 00 48 8d 55 e7 48 89 df 44 09 e0 be 0a 01 00 00 44 89 45 dc 88 45 e7 e8 8e b8 ff ff 44 8b 45 dc 83 f8 01 74 a1 <0f> 0b eb 9d e8 7c 99 3b d5 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f [12947.571543] RSP: 0018:a3d881a17660 EFLAGS: 00010282 [12947.571548] RAX: RBX: 9841d0ab9800 RCX: 010a [12947.571551] RDX: 9841c3a0eba0 RSI: c079367b RDI: 0100 [12947.571554] RBP: a3d881a17688 R08: 0001 R09: fffb [12947.571556] R10: 0001 R11: R12: 0001 [12947.571559] R13: a3d881a176e8 R14: 0001 R15: 9841d0ab9800 [12947.571562] FS: 7f49db6fda40() GS:9844cf38() knlGS: [12947.571572] CS: 0010 DS: ES: CR0: 80050033 [12947.571575] CR2: 7f6f24003f88 CR3: 00010a03 CR4: 003506e0 [12947.571579] Call Trace: [12947.571586] perform_link_training_with_retries+0xa7/0x140 [amdgpu] [12947.571920] enable_link_dp+0xe2/0x230 [amdgpu] [12947.572255] core_link_enable_stream+0x699/0x830 [amdgpu] [12947.572588] dce110_apply_ctx_to_hw+0x5c1/0x600 [amdgpu] [12947.572923] ? dcn10_verify_allow_pstate_change_high+0x22/0x350 [amdgpu] [12947.573275] ? dcn10_wait_for_mpcc_disconnect+0x43/0x140 [amdgpu] [12947.573626] dc_commit_state_no_check+0x28f/0xa00 [amdgpu] [12947.573961] dc_commit_state+0x96/0xb0 [amdgpu] [12947.574295] amdgpu_dm_atomic_commit_tail+0x56d/0x1510 [amdgpu] [12947.574643] ? ktime_get_raw+0x34/0x90 [12947.574652] ? ttm_bo_mem_compat+0x28/0x60 [ttm] [12947.574663] ? ttm_bo_validate+0x4c/0x160 [ttm] [12947.574676] ? dm_plane_helper_prepare_fb+0x1b4/0x270 [amdgpu] [12947.575021] ? _cond_resched+0x19/0x30 [12947.575029] ? wait_for_completion_timeout+0x3a/0x100 [12947.575033] ? _cond_resched+0x19/0x30 [12947.575039] commit_tail+0x99/0x130 [drm_kms_helper] [12947.575068] drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper] [12947.575096] drm_atomic_commit+0x4a/0x50 [drm] [12947.575149] drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper] [12947.575177] drm_mode_setcrtc+0x20d/0x7e0 [drm] [12947.575223] ? drm_mode_getcrtc+0x190/0x190 [drm] [12947.575267] drm_ioctl_kernel+0xae/0xf0 [drm] [12947.575308] drm_ioctl+0x257/0x410 [drm] [12947.575349] ? drm_mode_getcrtc+0x190/0x190 [drm] [12947.575395] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] [12947.575665] __x64_sys_ioctl+0x91/0xc0 [12947.575675] do_syscall_64+0x38/0x90 [12947.575683] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[Kernel-packages] [Bug 1958236] Re: Kernel 5.13 results on dxvk games crashing/hanging (LoL/Borderlands 2)
If only the games are crashing and not the kernel then please start by removing the unsupported graphics packages from your system (kisak-mesa PPA). ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958236 Title: Kernel 5.13 results on dxvk games crashing/hanging (LoL/Borderlands 2) Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: These games on Kernel 5.11.0-46 used to work fine, didn't crashing at all, but after the system updating its kernel to 5.13, hangs/crashes constantly started occurring on those games. Description: Ubuntu 20.04.3 LTS Release: 20.04 Kernel: 5.13.0-25-generic Last Kernel:5.11.0-46-generic (Works Fine) CPU:Intel Core i3 3110m 2.40ghz dual core 4 threads RAM:4GB DDR3 1333Mhz GPU:Intel HD Graphics 4000 (Mesa 21.3.4 - kisak-mesa PPA) Games tested: League of Legends - Wine-lol-ge 6.16.4 Borderlands 2 - Proton Experimental, Proton GE 6.21-GE-2, Proton GE 7.0rc6-GE-1 Native OpenGL games, Hollow Knight (Vulkan), GZDoom (Vulkan) and Quake Enhanced works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.13.0-25-generic 5.13.0-25.26~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 18 07:31:24 2022 InstallationDate: Installed on 2021-02-23 (328 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/usr/bin/zsh SourcePackage: linux-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-hwe-5.13/+bug/1958236/+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 1950060] Re: Unable to adjust screen backlight brightness on Google Pixelbook Eve
** No longer affects: linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950060 Title: Unable to adjust screen backlight brightness on Google Pixelbook Eve Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: The machine is Pixelbook 2017 Eve. OS is 21.10 fresh install and there is no way to adjust the screen backlight brightness. It is 100% all the time. IN 21.04 the solution was to add to kernel command line the i915.enable_dpcd_backlight=1 however this does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 22:38:37 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 615 [8086:591e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Google, Inc. HD Graphics 615 [1ae0:2212] InstallationDate: Installed on 2021-11-06 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 003: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:564b Realtek Semiconductor Corp. WebCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Eve ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dpcd_backlight=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Eve dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 31 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd08/06/2021:br4.14:efr0.0:svnGoogle:pnEve:pvr1.0:sku:rvnGoogle:rnEve:rvr1.0:cvnGoogle:ct31:cvr: dmi.product.family: Google_Eve dmi.product.name: Eve dmi.product.version: 1.0 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1950060/+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 1958412] Re: [amdgpu] at startup and shutdown screen gets white noise
** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958412 Title: [amdgpu] at startup and shutdown screen gets white noise Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: After the kernel release 5.13.0-27-generic was installed today, the startup and shutdown processes finish with white noise screens. The workaround at startup is to disable "quiet" in /etc/default/grub, variable GRUB_CMDLINE_LINUX_DEFAULT. (GRUB_CMDLINE_LINUX_DEFAULT="splash" works, GRUB_CMDLINE_LINUX_DEFAULT=" quiet splash" doesn't). No workaround found for shutdown until now. Can you help me find one ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jan 19 16:17:35 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18b2] InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP420UA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP420UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+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 1958248] Re: Screen garbled on login and freezes on unsuspend
*** This bug is a duplicate of bug 1958412 *** https://bugs.launchpad.net/bugs/1958412 ** Tags added: amdgpu focal ** Summary changed: - Screen garbled on login and freezes on unsuspend + [amdgpu] Screen garbled on login and freezes on unsuspend ** This bug has been marked a duplicate of bug 1958412 [amdgpu] at startup and shutdown screen gets white noise -- 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/1958248 Title: [amdgpu] Screen garbled on login and freezes on unsuspend Status in linux package in Ubuntu: Confirmed Bug description: 1. The login manager works but as soon as I log in, the screen is filled with colored vertical stripes and is unusable. I found that if I change the screen resolution to the maximum (1920x1080), then the screen is ok. Any other resolution that I've tried (eg (1440x900 used to be my preference) causes the unreadable display and it does not revert back, requiring a reboot. 2. Coming out of suspend, the password entry screen is displayed, but there is no response to keyboard or mouse, requiring a reboot. HP Envy x360 laptop with AMD Ryzen 7 with Radeon graphics Last known kernel that worked is 5.11.0-46 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958248/+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 1958519] Re: System hangs at shutdown due to systemd stuck worker on linux-image-5.13.0-27
** Package changed: linux (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958519 Title: System hangs at shutdown due to systemd stuck worker on linux- image-5.13.0-27 Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Greetings, I am having issues with udevd when using the latest 5.13.0-27-generic kernel on Ubuntu 20.04.3 LTS. At system shutdown / restart, the system never stops, forever waiting for systemd to shutdown. I noticed the following message in sudo journalctl -u systemd-udevd.service: gen 20 08:39:02 raminotebook systemd-udevd[333]: :04:00.7: Worker [391] processing SEQNUM=3059 is taking a long time Please tell me if I can provide more information. Now I am running 5.11.0-46-generic with no issues. Thank you Marco --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marco 966 F pulseaudio /dev/snd/controlC0: marco 966 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-10-17 (94 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: HP HP ENVY x360 Convertible 13-ag0xxx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic root=UUID=dae31aa6-19ca-4690-93b6-f76cf2702f75 ro ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-27-generic N/A linux-backports-modules-5.13.0-27-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.13.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/24/2021 dmi.bios.release: 15.49 dmi.bios.vendor: AMI dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8496 dmi.board.vendor: HP dmi.board.version: 92.48 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 92.48 dmi.modalias: dmi:bvnAMI:bvrF.49:bd05/24/2021:br15.49:efr92.48:svnHP:pnHPENVYx360Convertible13-ag0xxx:pvr:rvnHP:rn8496:rvr92.48:cvnHP:ct31:cvrChassisVersion:sku3YA63EA#ABZ: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ag0xxx dmi.product.sku: 3YA63EA#ABZ dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958519/+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 1958523] Re: Static-noise-like effect
*** This bug is a duplicate of bug 1958412 *** https://bugs.launchpad.net/bugs/1958412 Sounds like bug 1958412 so we should track it there. ** Tags added: amdgpu ** Summary changed: - Static-noise-like effect + [amdgpu] Static-noise-like effect ** This bug has been marked a duplicate of bug 1958412 [amdgpu] at startup and shutdown screen gets white noise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: [amdgpu] Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+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 1958591] Re: Random noise 'static' on internal display when turned off/on
*** This bug is a duplicate of bug 1958412 *** https://bugs.launchpad.net/bugs/1958412 ** Tags added: amdgpu ** Summary changed: - Random noise 'static' on internal display when turned off/on + [amdgpu] Random noise 'static' on internal display when turned off/on ** This bug has been marked a duplicate of bug 1958412 [amdgpu] at startup and shutdown screen gets white noise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' on internal display when turned off/on Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+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 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
** Tags removed: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Status in bluez package in Debian: New Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+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 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925344 Title: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth Status in gdm3 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-460 package in Ubuntu: Won't Fix Status in nvidia-prime package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top- left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1. Running `prime-select query` shows `nvidia`. Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`. Not sure which package I should fill this under. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 15:20:15 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09e1] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1] InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. G3 3500 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06ND9G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3500 dmi.product.sku: 09E1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Kernel-packages] [Bug 1870597] Re: libinput says "your system is too slow"
** Tags removed: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Hi,
I've tested current proposed kernel 5.13.0-28-generic on Thinkpad E14 Gen2,
Kubuntu 21.10.
All working fine, problem seems to be solved.
Greetings, Jan Gerrit
--
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/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1951746] Re: Kernel can't recognize hard drive in Lenovo Ideapad - Linux Mint
[Expired for linux-hwe-5.11 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.11 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951746 Title: Kernel can't recognize hard drive in Lenovo Ideapad - Linux Mint Status in linux-hwe-5.11 package in Ubuntu: Expired Bug description: Description: Linux Mint 20.1 Release: 20.1 version_signature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 ^version signature after reverting back to previous kernel version updated to kernel linux 5.11.0-40-generic after update and restart, I received kernel-panic: VFS: cannot open root device "nvme0n1p1" or unknown block (0,0): error -6 please append a correct "root=" boot option. using the previous kernel version properly loaded all firmware again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1951746/+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 759725] Re: The kernel is no longer readable by non-root users
The "statoverride" script appears to work on the first run for each
kernel. However, any subsequent times the `dpkg-statoverride` command
exits with errorcode 2:
$ apt-get install something-triggering-dkms
Processing triggers for linux-image-5.4.0-96-generic (5.4.0-96.109) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-96-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-96-generic
/etc/kernel/postinst.d/statoverride:
dpkg-statoverride: error: an override for '/boot/vmlinuz-5.4.0-96-generic'
already exists; aborting
run-parts: /etc/kernel/postinst.d/statoverride exited with return code 2
dpkg: error processing package linux-image-5.4.0-96-generic (--configure):
installed linux-image-5.4.0-96-generic package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-5.4.0-96-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
Adding the `--force-statoverride-add` flag fixed the issue:
#!/bin/sh
# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
set -e
version="$1"
if [ -z "$version" ]; then
exit 0
fi
exec dpkg-statoverride --force-statoverride-add --update --add root root
0644 "/boot/vmlinuz-${version}"
After that change, now the kernel dkms trigger succeeds:
Setting up linux-image-5.4.0-96-generic (5.4.0-96.109) ...
Processing triggers for linux-image-5.4.0-96-generic (5.4.0-96.109) ...
/etc/kernel/postinst.d/dkms:
* dkms: running auto installation service for kernel 5.4.0-96-generic
...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-96-generic
/etc/kernel/postinst.d/statoverride:
dpkg-statoverride: warning: an override for
'/boot/vmlinuz-5.4.0-96-generic' already exists, but --force specified so will
be ignored
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-96-generic
Found initrd image: /boot/initrd.img-5.4.0-96-generic
Found linux image: /boot/vmlinuz-5.4.0-94-generic
Found initrd image: /boot/initrd.img-5.4.0-94-generic
Found linux image: /boot/vmlinuz-5.4.0-91-generic
Found initrd image: /boot/initrd.img-5.4.0-91-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Ubuntu 20.04.3 LTS (20.04) on /dev/md126p1
done
If this is to be added as a postinst.d to the libguestfs-tools package,
please don't forget the `--force-statoverride-add` flag... or else we
introduce a new dkms / kernel postinst.d trigger idempotency bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/759725
Title:
The kernel is no longer readable by non-root users
Status in linux package in Ubuntu:
Won't Fix
Bug description:
The mode of the latest kernel has changed so it is no longer readable
by non-root users:
-rw-r--r-- 1 root root 4336016 2010-10-17 01:37
/boot/vmlinuz-2.6.35-22-generic
-rw-r--r-- 1 root root 4336912 2010-11-24 12:46
/boot/vmlinuz-2.6.35-23-generic
-rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
-rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic
This prevents people from using this kernel to boot qemu
virtual machines as non-root.
Please change the mode back to make the kernel readable.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: aplay: device_list:240: no soundcards found...
Architecture: amd64
ArecordDevices: arecord: device_list:240: no soundcards found...
CRDA: Error: [Errno 2] No such file or directory
Date: Wed Apr 13 13:05:01 2011
HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Red Hat KVM
PciMultimedia:
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
RelatedPackageVersions:
[Kernel-packages] [Bug 1956443] Re: Fix spurious wakeup caused by Intel 7560 WWAN
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956443 Title: Fix spurious wakeup caused by Intel 7560 WWAN Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Spurious wakeup from s2idle caused by Intel 7560 WWAN device. [Fix] Keep the device at D0 to prevent the unwanted wakeup. Since PCIe ASPM is enabled, the power consumption impact is minimal. [Test] No more spurious wakeup on s2idle. [Where problems could occur] If the device somehow requires to be power-cycled via D3, this may break the assumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956443/+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 1955443] Re: Fix USB3 detection on HP dock
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1955443 Title: Fix USB3 detection on HP dock Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Hotplug a USB3 device to HP dock can go undetected. [Fix] Add a delay for USB3 hub resume routine so the link has enough time to transit to U0. [Test] After the patch is applied, the dock can always detect USB3 devices. [Where problems could occur] A non-noticeable delay was added, so no basically no impact. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955443/+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 1956454] Re: Enable audio mute LED and mic mute LED on a new HP laptop
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956454 Title: Enable audio mute LED and mic mute LED on a new HP laptop Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Audio mute LED and mic mute LED are not working on a new HP laptop. [Fix] Use another audio quirk to enable the feature. [Test] With the patch applied, both LEDs start working. [Where problems could occur] This fix is limit to one device, so other devices are totally unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956454/+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 1950974] Re: Improve USB Type-C support
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950974 Title: Improve USB Type-C support Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)" can be found on many systems. [Fix] The main issue is that the PD firmware is unreliable, so use more deterministic methods to make it reliable [Test] The error message is gone. Also tried to plug/unplug USB Type-C power cord, and the status are always reported correctly. [Where problems could occur] This is quite a huge refactor, so regression can be expected. Only target to unstable and latest OEM kernel to reduce risk we are taking. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950974/+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 1958538] 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/1958538 Title: [amdgpu] Extreme screen flickering when setting a non-native resolution Status in linux package in Ubuntu: Confirmed Bug description: As soon I set the screen resolution to non native (4k laptop display) the screen begins to flicker and horizontal/vertical lines appear. (See attached image) Interestingly this happens only to the internal screen, external monitors work fine. Also during boot (supposedly when the display driver is loaded) severe tearing is visible for brief moment. An issue with the screen itself can be ruled out since there are no issues when running ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Jan 20 15:14:11 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5094] InstallationDate: Installed on 2022-01-03 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XLS0CJ00 ProcEnviron: LANGUAGE=de_CH:de TERM=xterm-256color PATH=(custom, no user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic root=UUID=9b2ef1f6-51f0-4f81-a1cd-0e7a073ff58e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2021 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET41W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XLS0CJ00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR1MET41W(1.11):bd09/03/2021:br1.11:efr1.11:svnLENOVO:pn20XLS0CJ00:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0CJ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.name: 20XLS0CJ00 dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958538/+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 1958586] 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1958586 Title: [Atheros AR3012] bluetooth fails shortly after startup Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On a new install of Ubuntu 21.10 on a new Librem14 laptop, I have a MX Ergo bluetooth mouse which works fine for a couple minutes after fresh startup. Seems like Bluetooth flickers on/off a few times (stutters briefly (half a second or so) and then starts working again. After a few times of that, it fails entirely and the Bluetooth mouse stops working. The touchpad on the laptop controls the mouse just fine. The indicators on the mouse itself show that it is avialable to connect to Bluetooth (slow blinking light on the mouse), but never indicates a valid connection (solid light on the mouse) once connection is lost. I then try to turn Bluetooth on/off from the gnome applet at the top- right of the screen, but regardless of how many times I toggle it on/off, the Bluetooth always appears to stay in the off position. Seems like bluetooth has crashed. Is there a way to monitor bluetooth and confirm if it is still running properly and if not why? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 18:50:10 2022 InstallationDate: Installed on 2022-01-19 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M |__ Port 6: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 14 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=de2aa352-980b-4e66-b7e1-511ec72cd176 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: 4.14-Purism-1 dmi.board.name: Librem 14 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.14-Purism-1:bd06/18/2021:br4.14:efr0.0:svnPurism:pnLibrem14:pvr1.0:rvnPurism:rnLibrem14:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 14 dmi.product.name: Librem 14 dmi.product.version: 1.0 dmi.sys.vendor: Purism hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:D7:DC:DC ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:2164672 acl:120176 sco:0 events:117 errors:0 TX bytes:5753 acl:42 sco:0 commands:70 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1958586/+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 1958586] Re: [Atheros AR3012] bluetooth fails shortly after startup
** Summary changed: - bluetooth fails shortly after startup + [Atheros AR3012] bluetooth fails shortly after startup ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1958586 Title: [Atheros AR3012] bluetooth fails shortly after startup Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On a new install of Ubuntu 21.10 on a new Librem14 laptop, I have a MX Ergo bluetooth mouse which works fine for a couple minutes after fresh startup. Seems like Bluetooth flickers on/off a few times (stutters briefly (half a second or so) and then starts working again. After a few times of that, it fails entirely and the Bluetooth mouse stops working. The touchpad on the laptop controls the mouse just fine. The indicators on the mouse itself show that it is avialable to connect to Bluetooth (slow blinking light on the mouse), but never indicates a valid connection (solid light on the mouse) once connection is lost. I then try to turn Bluetooth on/off from the gnome applet at the top- right of the screen, but regardless of how many times I toggle it on/off, the Bluetooth always appears to stay in the off position. Seems like bluetooth has crashed. Is there a way to monitor bluetooth and confirm if it is still running properly and if not why? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 18:50:10 2022 InstallationDate: Installed on 2022-01-19 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M |__ Port 6: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 14 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=de2aa352-980b-4e66-b7e1-511ec72cd176 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: 4.14-Purism-1 dmi.board.name: Librem 14 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.14-Purism-1:bd06/18/2021:br4.14:efr0.0:svnPurism:pnLibrem14:pvr1.0:rvnPurism:rnLibrem14:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 14 dmi.product.name: Librem 14 dmi.product.version: 1.0 dmi.sys.vendor: Purism hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:D7:DC:DC ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:2164672 acl:120176 sco:0 events:117 errors:0 TX bytes:5753 acl:42 sco:0 commands:70 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1958586/+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 1958583] Re: entering gnome lockscreen causes astfb displays to hang
While waiting for a kernel fix, this workaround might avoid it: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in /etc/environment ** No longer affects: gnome-shell (Ubuntu) ** Tags added: jammy ** Tags added: regression-release -- 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/1958583 Title: entering gnome lockscreen causes astfb displays to hang Status in linux package in Ubuntu: Confirmed Bug description: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument A commonality of these systems is that they use the astfb driver. I've found that this issue follows the kernel version. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958583/+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 1958538] Re: Extreme Screen flickering when setting a non-native resolution
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Extreme Screen flickering when setting a non-native resolution + [amdgpu] Extreme screen flickering when setting a non-native resolution -- 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/1958538 Title: [amdgpu] Extreme screen flickering when setting a non-native resolution Status in linux package in Ubuntu: New Bug description: As soon I set the screen resolution to non native (4k laptop display) the screen begins to flicker and horizontal/vertical lines appear. (See attached image) Interestingly this happens only to the internal screen, external monitors work fine. Also during boot (supposedly when the display driver is loaded) severe tearing is visible for brief moment. An issue with the screen itself can be ruled out since there are no issues when running ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Jan 20 15:14:11 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5094] InstallationDate: Installed on 2022-01-03 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XLS0CJ00 ProcEnviron: LANGUAGE=de_CH:de TERM=xterm-256color PATH=(custom, no user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic root=UUID=9b2ef1f6-51f0-4f81-a1cd-0e7a073ff58e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2021 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET41W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XLS0CJ00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR1MET41W(1.11):bd09/03/2021:br1.11:efr1.11:svnLENOVO:pn20XLS0CJ00:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0CJ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.name: 20XLS0CJ00 dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958538/+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 1958572] Re: kernel bug causing screen corruption on AMD GPU
** Package changed: xorg (Ubuntu) => linux-hwe-5.4 (Ubuntu) ** Tags added: radeon ** Summary changed: - kernel bug causing screen corruption on AMD GPU + [radeon] kernel bug causing screen corruption on AMD GPU -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1958572 Title: [radeon] kernel bug causing screen corruption on AMD GPU Status in linux-hwe-5.4 package in Ubuntu: New Bug description: Hi, I'm running Ubuntu MATE 18.04.6 LTS. The bug information was sadly collected from the working configuration of the system after dropping to an earlier kernel. This bug is a display bug where 1-pixel horizontal lines of multicolored corruption or occasionally incorrect screen contents appear across the screen, particularly during scrolling or moving the mouse. They appear intermittently, being more common near the top of the screen. My GPU is the built-in one on the AMD A10-5750M APU, the Radeon HD 8650G. (Laptop: G505s) I have found that this bug occurs on vmlinuz-5.4.0-96-generic but does not appear to occur on vmlinuz-5.4.0-91-generic when booting with that option in GRUB. I have not yet been able to capture an image of the issue as it becomes difficult to use the system when the bug occurs (though it appears to be fully functional, graphics aside). If very important I can try again later. -Matt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Thu Jan 20 14:05:30 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-91-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-94-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-96-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Richland [Radeon HD 8650G] [17aa:397c] InstallationDate: Installed on 2019-12-28 (754 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20255 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=3e3ee235-a725-4a35-a01f-8c156ee072f1 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN53WW(V3.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: 3193Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN53WW(V3.00):bd01/08/2014:svnLENOVO:pn20255:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvr3193Std:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.family: IDEAPAD dmi.product.name: 20255 dmi.product.sku: LENOVO_MT_20255 dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1958572/+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 1958572] [NEW] kernel bug causing screen corruption on AMD GPU
You have been subscribed to a public bug: Hi, I'm running Ubuntu MATE 18.04.6 LTS. The bug information was sadly collected from the working configuration of the system after dropping to an earlier kernel. This bug is a display bug where 1-pixel horizontal lines of multicolored corruption or occasionally incorrect screen contents appear across the screen, particularly during scrolling or moving the mouse. They appear intermittently, being more common near the top of the screen. My GPU is the built-in one on the AMD A10-5750M APU, the Radeon HD 8650G. (Laptop: G505s) I have found that this bug occurs on vmlinuz-5.4.0-96-generic but does not appear to occur on vmlinuz-5.4.0-91-generic when booting with that option in GRUB. I have not yet been able to capture an image of the issue as it becomes difficult to use the system when the bug occurs (though it appears to be fully functional, graphics aside). If very important I can try again later. -Matt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Thu Jan 20 14:05:30 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-91-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-94-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-96-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Richland [Radeon HD 8650G] [17aa:397c] InstallationDate: Installed on 2019-12-28 (754 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20255 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=3e3ee235-a725-4a35-a01f-8c156ee072f1 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN53WW(V3.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: 3193Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN53WW(V3.00):bd01/08/2014:svnLENOVO:pn20255:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvr3193Std:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.family: IDEAPAD dmi.product.name: 20255 dmi.product.sku: LENOVO_MT_20255 dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: linux-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption kernel-bug ubuntu -- kernel bug causing screen corruption on AMD GPU https://bugs.launchpad.net/bugs/1958572 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 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 1958538] [NEW] Extreme Screen flickering when setting a non-native resolution
You have been subscribed to a public bug: As soon I set the screen resolution to non native (4k laptop display) the screen begins to flicker and horizontal/vertical lines appear. (See attached image) Interestingly this happens only to the internal screen, external monitors work fine. Also during boot (supposedly when the display driver is loaded) severe tearing is visible for brief moment. An issue with the screen itself can be ruled out since there are no issues when running ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Jan 20 15:14:11 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5094] InstallationDate: Installed on 2022-01-03 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XLS0CJ00 ProcEnviron: LANGUAGE=de_CH:de TERM=xterm-256color PATH=(custom, no user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic root=UUID=9b2ef1f6-51f0-4f81-a1cd-0e7a073ff58e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2021 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET41W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XLS0CJ00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR1MET41W(1.11):bd09/03/2021:br1.11:efr1.11:svnLENOVO:pn20XLS0CJ00:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0CJ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.name: 20XLS0CJ00 dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug corruption impish ubuntu -- Extreme Screen flickering when setting a non-native resolution https://bugs.launchpad.net/bugs/1958538 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 1958443] Re: Ubuntu randomly freezes with 5.13.0-27 [rtw_8821ce 0000:01:00.0: pci bus timeout, check dma status]
** Summary changed: - Ubuntu randomly freezes with 5.13.0-27 + Ubuntu randomly freezes with 5.13.0-27 [rtw_8821ce :01:00.0: pci bus timeout, check dma status] ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958443 Title: Ubuntu randomly freezes with 5.13.0-27 [rtw_8821ce :01:00.0: pci bus timeout, check dma status] Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Ubuntu randomly freezes, and can't access keyboard and mouse anymore. The only way to solve is pressing power button to turn off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jan 19 10:46:15 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86c8] InstallationDate: Installed on 2021-12-18 (32 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: HP HP Laptop 14-dq1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=273732e3-7cd1-4dda-8015-f36adc95fbc3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2021 dmi.bios.release: 15.21 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C8 dmi.board.vendor: HP dmi.board.version: 56.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 56.33 dmi.modalias: dmi:bvnAMI:bvrF.21:bd07/21/2021:br15.21:efr56.33:svnHP:pnHPLaptop14-dq1xxx:pvr:rvnHP:rn86C8:rvr56.33:cvnHP:ct10:cvrChassisVersion:sku8AD55UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-dq1xxx dmi.product.sku: 8AD55UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958443/+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 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
I have Lenovo Ideapad with nvidia geforce gtx 1650 Ti. After upgrade
from 20.04 -> 21.10 Opera, Chrome and Firefox become very slow. All
other soft works fine. If you have nvidia, try change driver to 470(only
one works with external monitor) and try chang nvidia x server settings
-> PRIME Profiles -> NVIDIA (Performance Mode). This resolves this
problem in my case.
--
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/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22
works
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
This does not occur with linux-image-5.13.0-22-generic, but does with
linux-image-5.13.0-23-generic.
On startup, I get about a 60 second hang, with the following in the kernel
dmesg:
Jan 4 15:26:36 inspiron-3505 kernel: [ 34.160572] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:26:56 inspiron-3505 kernel: [ 54.189055] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
Jan 4 15:27:16 inspiron-3505 kernel: [ 74.329264] amdgpu :04:00.0:
amdgp : failed to write reg 28b4 wait reg 28c6
Jan 4 15:27:36 inspiron-3505 kernel: [ 94.337904] amdgpu :04:00.0:
amdgp : failed to write reg 1a6f4 wait reg 1a706
I have the following GPU:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Picass
o (rev c2) (prog-if 00 [VGA controller])
04:00.0 0300: 1002:15d8 (rev c2)
(This is a Ryzen 5 3450U CPU with Radeon Vega Mobile.)
I get a similar hang if I start firefox (when it's probing OpenGL
contexts), and even with glxgears and glxinfo. Seems like anything
that'd kick on a OpenGL context does it. I had a freeze as well when
I tried running firefox and glxgears both. Along with odd BUG:
messages logged (I have some in the attached log.)
I was running with "iommu=pt", but did try with this removed, still
got the errors (I think amdgpu driver uses the IOMMU even when it's
set to IOMMU=pt though.). See the attached log for some very odd
"[Hardware Error]" messages that were logged on one test run. I think
this was when I tried to run firestorm (second life viewer) -- that
had a large pause then opened to a black window.
Per Google, I see there was a bug like this that turned up in kernel
5.14.15 but fixed in 5.14.17. See
https://gitlab.freedesktop.org/drm/amd/-/issues/1770
Thanks!
--Henry
Fix:
upstream commit afd18180c070 ("drm/amdkfd: fix boot failure when iommu is
disabled in Picasso.")
Patch was included in the Impish kernel in -proposed (5.13.0.24.24)
from an upstream patch set. multiple confirmations the problem is
resolved with the kernel in -proposed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Wow, decided to come back to this thread out of curiosity after 4
months, still not solved haha
I guess this is a testament to rolling release and having good active
maintainers like they have in Arch and OpenSUSE Tumbleweed, things just
get fixed and pushed. I will continue using Arch for now.
--
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/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1958571] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1958571 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958571 Title: Linux 5.13.0.25-generic Network not working Status in linux package in Ubuntu: Incomplete Bug description: This problem occurs only with this version of kernel. It works fine with 5.13.0.24 version. (on my system the "ubuntu-bag" table of options, no “network issues” is provided. The option “others” on the bottom of the table yield nothing). Appreciate if you can advise how to fix it. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-24.24-generic 5.13.19 Uname: Linux 5.13.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: X-Cinnamon Date: Thu Jan 20 10:58:34 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2022-01-20 10:41:58.568301 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958571/+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 1958571] Re: Linux 5.13.0.25-generic Network not working
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: ubuntu-release-upgrader (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/1958571 Title: Linux 5.13.0.25-generic Network not working Status in linux package in Ubuntu: Incomplete Bug description: This problem occurs only with this version of kernel. It works fine with 5.13.0.24 version. (on my system the "ubuntu-bag" table of options, no “network issues” is provided. The option “others” on the bottom of the table yield nothing). Appreciate if you can advise how to fix it. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-24.24-generic 5.13.19 Uname: Linux 5.13.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: X-Cinnamon Date: Thu Jan 20 10:58:34 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2022-01-20 10:41:58.568301 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958571/+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 1958591] Re: Random noise 'static' on internal display when turned off/on
** Package changed: ubuntu => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: Random noise 'static' on internal display when turned off/on Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+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 1958571] [NEW] Linux 5.13.0.25-generic Network not working
You have been subscribed to a public bug: This problem occurs only with this version of kernel. It works fine with 5.13.0.24 version. (on my system the "ubuntu-bag" table of options, no “network issues” is provided. The option “others” on the bottom of the table yield nothing). Appreciate if you can advise how to fix it. Thanks Levi ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-24.24-generic 5.13.19 Uname: Linux 5.13.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: X-Cinnamon Date: Thu Jan 20 10:58:34 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2022-01-20 10:41:58.568301 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish third-party-packages -- Linux 5.13.0.25-generic Network not working https://bugs.launchpad.net/bugs/1958571 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 1958591] [NEW] Random noise 'static' on internal display when turned off/on
You have been subscribed to a public bug: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm- radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal third-party-packages ubuntu -- Random noise 'static' on internal display when turned off/on https://bugs.launchpad.net/bugs/1958591 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 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 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0
According to test result at https://certification.canonical.com/hardware/202002-27718/submission/245770/test-results/pass/?term=media. This problem has been solved. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951784 Title: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0 Status in linux package in Ubuntu: Fix Released Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: [Summary] I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test always fails. I found that after CPU offline test, I can't read/write SD card. After checking dmesg, I got those error msgs. [ 232.577510] __common_interrupt: 7.34 No irq handler for vector [ 234.354327] mmc0: error -110 doing runtime resume I found the same issue on Dell Precision 3551(202002-27718) and Dell Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36 Before I didn't think it's a bug since I re-run mediacard test then it's pass. But this cycle there are more systems failed to the test, I just started digging into that. [Step to reproduce] 1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04 2. sudo apt update; sudo apt dist-upgrade -y 3. run cpu offline test via checkbox-cli or execute following command for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; done; cd $mount_point_of_sd_card sudo dd if=/dev/urandom of=test bs=1M count=10 [Expected result] Can read/write SD card. [Actual result] Can't read/write SD card. [Failure rate] 5/5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 22 01:28:59 2021 InstallationDate: Installed on 2020-08-03 (475 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951784/+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 1958583] Re: entering gnome lockscreen causes astfb displays to hang
** Attachment added: "sosreport-starbuck-2022-01-20-ziauesz.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+attachment/972/+files/sosreport-starbuck-2022-01-20-ziauesz.tar.xz -- 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/1958583 Title: entering gnome lockscreen causes astfb displays to hang Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument A commonality of these systems is that they use the astfb driver. I've found that this issue follows the kernel version. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+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 1958586] [NEW] bluetooth fails shortly after startup
Public bug reported: On a new install of Ubuntu 21.10 on a new Librem14 laptop, I have a MX Ergo bluetooth mouse which works fine for a couple minutes after fresh startup. Seems like Bluetooth flickers on/off a few times (stutters briefly (half a second or so) and then starts working again. After a few times of that, it fails entirely and the Bluetooth mouse stops working. The touchpad on the laptop controls the mouse just fine. The indicators on the mouse itself show that it is avialable to connect to Bluetooth (slow blinking light on the mouse), but never indicates a valid connection (solid light on the mouse) once connection is lost. I then try to turn Bluetooth on/off from the gnome applet at the top- right of the screen, but regardless of how many times I toggle it on/off, the Bluetooth always appears to stay in the off position. Seems like bluetooth has crashed. Is there a way to monitor bluetooth and confirm if it is still running properly and if not why? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 18:50:10 2022 InstallationDate: Installed on 2022-01-19 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M |__ Port 6: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 14 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=de2aa352-980b-4e66-b7e1-511ec72cd176 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: 4.14-Purism-1 dmi.board.name: Librem 14 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.14-Purism-1:bd06/18/2021:br4.14:efr0.0:svnPurism:pnLibrem14:pvr1.0:rvnPurism:rnLibrem14:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 14 dmi.product.name: Librem 14 dmi.product.version: 1.0 dmi.sys.vendor: Purism hciconfig: hci0: Type: Primary Bus: USB BD Address: 18:CF:5E:D7:DC:DC ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:2164672 acl:120176 sco:0 events:117 errors:0 TX bytes:5753 acl:42 sco:0 commands:70 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1958586 Title: bluetooth fails shortly after startup Status in bluez package in Ubuntu: New Bug description: On a new install of Ubuntu 21.10 on a new Librem14 laptop, I have a MX Ergo bluetooth mouse which works fine for a couple minutes after fresh startup. Seems like Bluetooth flickers on/off a few times (stutters briefly (half a second or so) and then starts working again. After a few times of that, it fails entirely and the Bluetooth mouse stops working. The touchpad on the laptop controls the mouse just fine. The indicators on the mouse itself show that it is avialable to connect to Bluetooth (slow blinking light on the mouse), but never indicates a valid connection (solid light on the mouse) once connection is lost. I then try to turn Bluetooth on/off from the gnome applet at the top- right of the screen, but regardless of how many times I toggle it on/off, the Bluetooth always appears to stay in the off position. Seems like bluetooth has crashed. Is there a way to monitor bluetooth and confirm if it is still running properly and if not why? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 18:50:10 2022
[Kernel-packages] [Bug 1958583] Re: entering gnome lockscreen causes display to hang
I found that this issue also impacts upstream kernels, so I bisected and found that the problem was introduced in this commit: commit d6ddbd5c97d1b9156646ac5c42b8851edd664ee2 Author: Thomas Zimmermann Date: Thu May 7 11:06:40 2020 +0200 drm/ast: Don't check new mode if CRTC is being disabled I verified that this issue can still be reproduced with current upstream (currently between v5.16 & v5.17-rc1), and that reverting the above patch[*] causes it to go away. [*] The patch doesn't cleanly revert because the underlying code has evolved a bit, but it's straightforward to back out: diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c index 956c8982192b..336c545c46f5 100644 --- a/drivers/gpu/drm/ast/ast_mode.c +++ b/drivers/gpu/drm/ast/ast_mode.c @@ -1012,9 +1012,6 @@ static int ast_crtc_helper_atomic_check(struct drm_crtc *crtc, const struct drm_format_info *format; bool succ; - if (!crtc_state->enable) - return 0; /* no mode checks if CRTC is being disabled */ - ast_state = to_ast_crtc_state(crtc_state); format = ast_state->format; ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - entering gnome lockscreen causes display to hang + entering gnome lockscreen causes astfb displays to hang ** Description changed: When I install ubuntu-desktop on servers with an AMI BMC, I find a - remote desktop running over BMC's virtual KVM display hangs when I + remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. A commonality of these systems is that they use the astfb driver. I've found that this symptom follows the kernel. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument ** Description changed: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. - - A commonality of these systems is that they use the astfb driver. - - I've found that this symptom follows the kernel. If I run a jammy - desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just - the kernel back to focal's 5.4, the issue vanishes. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument + + A commonality of these systems is that they use the astfb driver. + + I've found that this issue follows the kernel version. If I run a jammy + desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just + the kernel back to focal's 5.4, the issue vanishes. -- 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/1958583
[Kernel-packages] [Bug 1958583] [NEW] entering gnome lockscreen causes astfb displays to hang
Public bug reported: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument A commonality of these systems is that they use the astfb driver. I've found that this issue follows the kernel version. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1958583 Title: entering gnome lockscreen causes astfb displays to hang Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument A commonality of these systems is that they use the astfb driver. I've found that this issue follows the kernel version. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+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 1958582] [NEW] nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build
Public bug reported: I have no idea what caused this to occur, but my system brought it to my attention, so I'm submitting it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.80-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-27-generic Date: Thu Jan 20 16:57:23 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.80-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/460.80/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-04-17 (278 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.80-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1958582 Title: nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I have no idea what caused this to occur, but my system brought it to my attention, so I'm submitting it. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.80-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.13.0-27-generic Date: Thu Jan 20 16:57:23 2022 DuplicateSignature: dkms:nvidia-dkms-460:460.80-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/460.80/build/nvidia-drm/nvidia-drm-crtc.c:311:23: error: initialization of ‘int (*)(struct drm_plane *, struct drm_atomic_state *)’ from incompatible pointer type ‘int (*)(struct drm_plane *, struct drm_plane_state *)’ [-Werror=incompatible-pointer-types] InstallationDate: Installed on 2021-04-17 (278 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.80-0ubuntu0.20.04.2 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: nvidia-graphics-drivers-460 Title: nvidia-dkms-460 460.80-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1958582/+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 1908264] Re: Disable Atari partition support for cloud kernels
The Hirsute Hippo has reached End of Life, so this bug will not be fixed for that release. ** Changed in: linux-aws (Ubuntu Hirsute) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Released Status in linux-gke source package in Focal: Fix Released Status in linux-gkeop source package in Focal: Fix Released Status in linux-oracle source package in Focal: Fix Released Status in linux-aws source package in Groovy: Won't Fix Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-aws source package in Hirsute: Won't Fix Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+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 1914668] Re: Exploitable vulnerabilities in AF_VSOCK implementation
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: linux (Ubuntu Hirsute)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1914668
Title:
Exploitable vulnerabilities in AF_VSOCK implementation
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.8 package in Ubuntu:
Invalid
Status in linux-oem-5.6 package in Ubuntu:
Fix Released
Status in linux-riscv package in Ubuntu:
Fix Released
Status in linux-hwe-5.8 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Won't Fix
Bug description:
https://www.openwall.com/lists/oss-security/2021/02/04/5
The following mainline patch is required for all kernels >= v5.8:
{focal hwe-5.8, groovy, hirsute}:
[linux] c518adafa39f vsock: fix the race conditions in multi-transport
support
or [linux-5.10-y] 55d900415b81 vsock: fix the race conditions in
multi-transport support
[Impact]
* Patches an exploitable vulnerability.
[Test Case]
* See disclosure article.
[Regression Potential]
* Low: straightforward race condition fix; upstream cherry-pick.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914668/+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 1908503] Re: arm64: prevent losing page dirty state
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: linux-aws (Ubuntu Hirsute)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1908503
Title:
arm64: prevent losing page dirty state
Status in linux-aws package in Ubuntu:
New
Status in linux-aws source package in Bionic:
Fix Released
Status in linux-aws source package in Focal:
Fix Released
Status in linux-aws source package in Groovy:
Won't Fix
Status in linux-aws source package in Hirsute:
Won't Fix
Bug description:
[Impact]
With hardware dirty bit management enabled calling pte_wrprotect() on
a dirty PTE will clean the dirty state without flushing the content of
the page to the backing store.
[Test case]
Bug reported by Amazon, a specific test case is not provided. This
problem has been hit by a customer.
[Fix]
Apply commit:
ff1712f953e27f0b0718762ec17d0adb15c9fd0b ("arm64: pgtable: Ensure dirty bit
is preserved across pte_wrprotect()")
Backport activity is minimal, it only requires to adjust the context a
bit to remove the previous pte_wrprotect() implementation.
[Regression potential]
The fix is specific for arm64 pgtable, it is an upstream fix also
marked for stable. The only potential downside could be the extra
overhead introduced by the additional call to pte_mkdirty() in
pte_wrprotect(), so worst case scenario it could introduce a
performance regression. It doesn't seem to potentially introduce any
other kind of regression / breakage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908503/+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 1956393] Re: Bluetooth no longer recognized after update to 5.14.0-1013
Tested with 1020 kernel in focal-updates, still no-good. Tested with 1021 kernel in focal-proposed, seems to be OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956393 Title: Bluetooth no longer recognized after update to 5.14.0-1013 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: On many CLEVO chassis computers with the recent update to the OEM 5.14.0-1013 kernel, bluetooth is no longer recognized by KDE Plasma. We are not sure why this has happened, but this is likely an API change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1013-oem 5.14.0-1013.13 ProcVersionSignature: Ubuntu 5.14.0-1013.13-oem 5.14.20 Uname: Linux 5.14.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jan 4 13:47:39 2022 InstallationDate: Installed on 2021-08-05 (151 days ago) InstallationMedia: Kubuntu 20.04.2 "Focal Fossa" (20210805) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956393/+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 1958443] Re: Ubuntu randomly freezes with 5.13.0-27
Please look at the attached file. It looks like there is issue with rtw_8821ce. I've cut the log because launchpad fails to upload the 255MB prevboot.txt. This line Jan 20 10:24:58 hpl kernel: rtw_8821ce :01:00.0: pci bus timeout, check dma status keeps repeating until line number 3076252, which is the end of file. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958443/+attachment/947/+files/prevboot.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958443 Title: Ubuntu randomly freezes with 5.13.0-27 Status in linux-hwe-5.13 package in Ubuntu: Incomplete Bug description: Ubuntu randomly freezes, and can't access keyboard and mouse anymore. The only way to solve is pressing power button to turn off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jan 19 10:46:15 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86c8] InstallationDate: Installed on 2021-12-18 (32 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: HP HP Laptop 14-dq1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=273732e3-7cd1-4dda-8015-f36adc95fbc3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2021 dmi.bios.release: 15.21 dmi.bios.vendor: AMI dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86C8 dmi.board.vendor: HP dmi.board.version: 56.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 56.33 dmi.modalias: dmi:bvnAMI:bvrF.21:bd07/21/2021:br15.21:efr56.33:svnHP:pnHPLaptop14-dq1xxx:pvr:rvnHP:rn86C8:rvr56.33:cvnHP:ct10:cvrChassisVersion:sku8AD55UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-dq1xxx dmi.product.sku: 8AD55UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958443/+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 1956467] Re: powerlight stays on after shutdown
Same issue here: AMD® A12-9720p radeon r7 Ubuntu 20.04.3 LTS Kernels from 5.11.0-46 to 5.13.0-27 fail at shutdown, restart and suspend. Only working kernel is 5.11.0-40 -- 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/1956467 Title: powerlight stays on after shutdown Status in linux package in Ubuntu: Confirmed Bug description: After kernel upgrade from 5.11.0.40 to versions 5.11.0.41, 5.11.0.43, 5.11.0.44 power-button light fails to switch off, after shutdown. shutdown can be triggered from command line or via desktop menu, result is the same. After rebooting from 5.11.0.40 normal functionality is restored. systemd appears to complete shutdown looking at the logs (see attached) Switching to suspend mode (sleep) functions as expected (power light blinks) and stays permanently on after wake-up. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1896 F pulseaudio /dev/snd/controlC0: christian 1896 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (609 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.24 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) 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: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956467/+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 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Changed in: finalrd (Ubuntu Focal) Milestone: None => ubuntu-20.04.4 -- 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Status in casper source package in Hirsute: New Status in finalrd source package in Hirsute: New Status in linux source package in Hirsute: New Status in casper source package in Impish: New Status in finalrd source package in Impish: New Status in linux source package in Impish: New Status in casper source package in Jammy: New Status in finalrd source package in Jammy: Fix Released Status in linux source package in Jammy: Confirmed Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd ---
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-oem-5.14/5.14.0.1021.18)
All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1021.18) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oem-5.14 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1958412] Re: [amdgpu] at startup and shutdown screen gets white noise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958412 Title: [amdgpu] at startup and shutdown screen gets white noise Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: After the kernel release 5.13.0-27-generic was installed today, the startup and shutdown processes finish with white noise screens. The workaround at startup is to disable "quiet" in /etc/default/grub, variable GRUB_CMDLINE_LINUX_DEFAULT. (GRUB_CMDLINE_LINUX_DEFAULT="splash" works, GRUB_CMDLINE_LINUX_DEFAULT=" quiet splash" doesn't). No workaround found for shutdown until now. Can you help me find one ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jan 19 16:17:35 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18b2] InstallationDate: Installed on 2022-01-19 (0 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=c4ec4ae8-c14c-4c0b-9922-9142270cef97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: TP420UA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP420UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrTP420UA.302:bd09/06/2021:br5.19:efr3.2:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP420UA_TM420UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP420UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP420UA_TM420UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 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 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958412/+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 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13
assuming fixed by this patchset -https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955180 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947453 Title: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13 Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Committed Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567
[Kernel-packages] [Bug 1947453] Re: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13
seems to be resolved with 5.13.0-28-generic release -- 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/1947453 Title: [amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13 Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 15:49:45 2021 DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70] InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X505BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eugene 2026 F pulseaudio /dev/snd/controlC0: eugene 2026 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2020-11-20 (329 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. X505BA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 Tags: impish wayland-session Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/02/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X505BA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X505BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1957112] Re: webcam doesn't work
I did not find any workaround either. So far I can work with 5.4.0-91. Anyway I hope that this bug will be fixed, but I can see that it is still "Unassigned" with "Undecided" importance, which doesn't lift my hopes. -- 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/1957112 Title: webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My webcam doesn't work --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 2920 F pulseaudio /dev/snd/controlC0: piotr 2920 F pulseaudio /dev/snd/controlC1: piotr 2920 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 InstallationDate: Installed on 2020-06-07 (583 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.24 RfKill: Tags: una Uname: Linux 5.4.0-91-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+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 1937269] Re: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1937269 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: Crash dialog show up on reboot right after kernel update + reinstalling using: apt purge nvidia-driver-460 # enforce a fresh install apt install nvidia-driver-460 Besides the crash dialog, I did not notice any problems so far; e.g. no visual impact, nvidia utils launch as usual showing information, etc... - - - - - - - - - - - - - ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-59-generic Date: Wed Jul 21 08:14:54 2021 Dependencies: DuplicateSignature: dkms:nvidia-kernel-source-460:460.91.03-0ubuntu0.20.04.1:clang: error: unsupported option '-dumpspecs' InstallationDate: Installed on 2021-05-27 (55 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 460.91.03-0ubuntu0.20.04.1 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: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.91.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1937269/+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 1942662] Re: package nvidia-dkms-460 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error e
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1942662 Title: package nvidia-dkms-460 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: when i uninstall snap i got this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460 460.91.03-0ubuntu0.20.04.1 Uname: Linux 5.10.3-051003-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 4 10:43:24 2021 ErrorMessage: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2020-11-09 (299 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460 Title: package nvidia-dkms-460 460.91.03-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1942662/+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 1958565] [NEW] Can not boot after updating kernel to linux-image-5.13.0-27-generic
Public bug reported: After auto-updating kernel to linux-image-5.13.0-27-generic I can not boot into Ubuntu 20.04. But using an older kernel the boot works fine. Laptop- Razor Blade 15 Advanced Model (2021) The boot fails and drops to initramfs. Ubuntu can not find any disk mounted. The problem is similar to this : https://askubuntu.com/questions/15515/disk-by-uuid-not-detected- initramfs-boot-failure Using older kernel works fine $ uname -a Linux rraj-Blade-15-Advanced-Model-Mid-2021-RZ09-0409 5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- 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/1958565 Title: Can not boot after updating kernel to linux-image-5.13.0-27-generic Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: After auto-updating kernel to linux-image-5.13.0-27-generic I can not boot into Ubuntu 20.04. But using an older kernel the boot works fine. Laptop- Razor Blade 15 Advanced Model (2021) The boot fails and drops to initramfs. Ubuntu can not find any disk mounted. The problem is similar to this : https://askubuntu.com/questions/15515/disk-by-uuid-not-detected- initramfs-boot-failure Using older kernel works fine $ uname -a Linux rraj-Blade-15-Advanced-Model-Mid-2021-RZ09-0409 5.11.0-46-generic #51~20.04.1-Ubuntu SMP Fri Jan 7 06:51:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958565/+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 1958564] [NEW] v2.1.2 upgrade complete verification
Public bug reported: v2.1.2 upgrade complete verification DONE - regression tests amd64 - autopkgtests all arches TODO - double check focal userspace with hwe-kernel new zfs-dkms - zsys in jammy on amd64 - regression tests s390x - regression tests ppc64el - regression tests arm64 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: In Progress ** Affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: In Progress ** Tags: block-proposed-jammy ** Tags added: block-proposed-jammy ** Also affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Jammy) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: zfs-linux (Ubuntu Jammy) Status: New => In Progress -- 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/1958564 Title: v2.1.2 upgrade complete verification Status in zfs-linux package in Ubuntu: In Progress Status in zfs-linux source package in Jammy: In Progress Bug description: v2.1.2 upgrade complete verification DONE - regression tests amd64 - autopkgtests all arches TODO - double check focal userspace with hwe-kernel new zfs-dkms - zsys in jammy on amd64 - regression tests s390x - regression tests ppc64el - regression tests arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1958564/+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 1958286] Re: mt7921e 0000:02:00.0: PM: failed to resume async: error -110
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127348.html
(linux-firmware/focal)
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127349.html
(linux-firmware/impish)
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127350.html
(linux-firmware/jammy)
** Also affects: linux-firmware (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in: linux-firmware (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Impish)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Impish)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Changed in: linux-firmware (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
** Description changed:
+ [SRU Justification]
+
+
+ [Impact]
+
+ Mediatek MT7921 may fail to resume from runtime suspend can cause chip
+ reset.
+
+ mt7921e :02:00.0: PM: failed to resume async: error -110
+ mt7921e :02:00.0: chip reset
+
+ [Fix]
+
+ This is fixed with both bluetooth and WiFi firmware upgrade to
+ upstream commit 094d7adc1136 ("linux-firmware: update firmware for
+ MT7921 WiFi device") and commit 1e744b85cd4c ("linux-firmware: update
+ firmware for mediatek bluetooth chip(MT7921)").
+
+ [Test Case]
+
+ This can be triggered by checkbox warm reset stress test:
+
+ $ checkbox-cli run com.canonical.certification::stress/reboot
+
+ [Where problems could occur]
+
+ This imports fixes requiring both kernel driver and proprietary firmware
+ updates, the firmware part might cause instability or so.
+
+ [Other Info]
+
+ This affects all kernels supporting MT7921, which means F/H/I/J.
+
+ == original bug report ==
+
[Summary]
Boot into Ubuntu desktop, MT7921 shows IP is obtained, however there is no
response from gateway pings, neither is 8.8.8.8.
kernel: [ 588.893227] mt7921e :02:00.0: PM: failed to resume async: error
-110
kernel: [ 588.893236] mt7921e :02:00.0: chip reset
[Reproduce Steps]
1. Boot into Ubuntu desktop
2. Check if MT7921 obtains IP, ping gateway and ping 8.8.8.8
3. No response, need to do cold boot to recover
4. The issue is easily be seen after warm reset stress, I locally test warm
reset stress for 100 times
[Results]
Expected: Has traffic and response by ping
Actual: No response
--
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/1958286
Title:
mt7921e :02:00.0: PM: failed to resume async: error -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Focal:
In Progress
Status in linux-firmware source package in Hirsute:
Won't Fix
Status in linux-firmware source package in Impish:
In Progress
Status in linux-firmware source package in Jammy:
In Progress
Bug description:
[SRU Justification]
[Impact]
Mediatek MT7921 may fail to resume from runtime suspend can cause chip
reset.
mt7921e :02:00.0: PM: failed to resume async: error -110
mt7921e :02:00.0: chip reset
[Fix]
This is fixed with both bluetooth and WiFi firmware upgrade to
upstream commit 094d7adc1136 ("linux-firmware: update firmware for
MT7921 WiFi device") and commit 1e744b85cd4c ("linux-firmware: update
firmware for mediatek bluetooth chip(MT7921)").
[Test Case]
This can be triggered by checkbox warm reset stress test:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
[Other Info]
This affects all kernels supporting MT7921, which means F/H/I/J.
== original bug report ==
[Summary]
Boot into Ubuntu desktop, MT7921 shows IP is obtained, however there is no
response from gateway pings, neither is 8.8.8.8.
kernel: [ 588.893227] mt7921e :02:00.0: PM: failed to resume async: error
-110
kernel: [ 588.893236] mt7921e :02:00.0: chip reset
[Reproduce Steps]
1. Boot into Ubuntu desktop
2. Check if MT7921 obtains IP, ping gateway and ping 8.8.8.8
3. No response, need to do cold boot to recover
4. The issue is easily be seen after warm
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Tags removed: rls-jj-incoming -- 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Status in casper source package in Hirsute: New Status in finalrd source package in Hirsute: New Status in linux source package in Hirsute: New Status in casper source package in Impish: New Status in finalrd source package in Impish: New Status in linux source package in Impish: New Status in casper source package in Jammy: New Status in finalrd source package in Jammy: Fix Released Status in linux source package in Jammy: Confirmed Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Tags added: jammy -- 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Status in casper source package in Hirsute: New Status in finalrd source package in Hirsute: New Status in linux source package in Hirsute: New Status in casper source package in Impish: New Status in finalrd source package in Impish: New Status in linux source package in Impish: New Status in casper source package in Jammy: New Status in finalrd source package in Jammy: Fix Released Status in linux source package in Jammy: Confirmed Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr
[Kernel-packages] [Bug 1956518] Re: linux-firmware 1.187.24 may crash USB ports
We're to backport new firmware updates for MT7921 in bug 1958286. Expecting landing in 1.187.26 or later. -- 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/1956518 Title: linux-firmware 1.187.24 may crash USB ports Status in linux-firmware package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 5.4.0-92-generic linux-firmware: Instalados: 1.187.24 Candidato: 1.187.24 Tabla de versión: *** 1.187.24 500 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.187 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu focal/main i386 Packages linux-firmware 1.187.24 upgrade disabled all mainboard USB ports. USB keyboard and mouse stopped working on the next reboot after upgrade. I disconnected an USB bluetooth key from a back USB port, rebooted, and everything restored to normality. My personal conclusion: there is a bug in the bluetooth firmware update that may cause a general USB crash when an USB bluetooth key is connected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alvaro 2225 F pulseaudio /dev/snd/controlC0: alvaro 2225 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=fd59aa5f-2c5c-44c8-9fd3-36c7b5ec516a InstallationDate: Installed on 2014-10-25 (2634 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B365M H NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 1.187.24 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-92-generic root=UUID=ff070320-7281-484d-a5d3-4a42ed9ed075 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: 2: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (623 days ago) UserGroups: adm boinc cdrom dip lpadmin netdev plugdev render sambashare sudo video _MarkForUpload: True dmi.bios.date: 08/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: Default string dmi.board.name: B365M H 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.:bvrF4b:bd08/18/2020:svnGigabyteTechnologyCo.,Ltd.:pnB365MH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MH:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1956518/+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 1956720] Re: Focal update: upstream stable patchset 2022-01-07
Why is this commit not included here?
commit f95dc207b93da9c88ddbb7741ec3730c6657b88e
Author: Jens Axboe
AuthorDate: Tue Aug 31 13:57:32 2021 -0600
Commit: Jens Axboe
CommitDate: Wed Sep 1 12:35:30 2021 -0600
io-wq: split bounded and unbounded work into separate lists
We've got a few issues that all boil down to the fact that we have one
list of pending work items, yet two different types of workers to
serve them. This causes some oddities around workers switching type and
even hashed work vs regular work on the same bounded list.
Just separate them out cleanly, similarly to how we already do
accounting of what is running. That provides a clean separation and
removes some corner cases that can cause stalls when handling IO
that is punted to io-wq.
Fixes: ecc53c48c13d ("io-wq: check max_worker limits if a worker
transitions bound state")
Signed-off-by: Jens Axboe
Other io_uring related patches where backported here even without being
in linux-stable/linux-5.14.y. So why is this missing?
See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1956720
Title:
Focal update: upstream stable patchset 2022-01-07
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux-oem-5.14 source package in Focal:
Incomplete
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2022-01-07
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+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 1933627] Re: HUGETLBFS is disabled
** No longer affects: linux-raspi (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1933627 Title: HUGETLBFS is disabled Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Hirsute: Fix Released Status in linux-raspi source package in Impish: Fix Released Bug description: [Impact] Huge pages can't be managed via hugeadm which requires hugetlbfs. [Test Case] $ hugeadm --pool-list hugeadm:ERROR: kernel does not support huge pages With fix: $ hugeadm --pool-list Size Minimum Current Maximum Default 65536000 2097152000* 33554432000 1073741824000 [Fix] Enable CONFIG_HUGETLBFS [Regression Potential] This config enables code that is disabled by default. However, there is minimal stub code running at boot so problems would most likely show up as splats during boot or later on when hugetlbfs is explicitly mounted by systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933627/+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 1933532] Re: Large Page support disabled on Raspberry Pi kernels
** This bug is no longer a duplicate of bug 1933627 HUGETLBFS is disabled ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux-raspi (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Description changed: + [ Impact ] + It appears that large page support and transparent hugepages are disabled in config on the Raspberry Pi. It would be nice if they were enabled in the kernel configuration, even if they are disabled by default. Then they could be set in user-editable config via the "transparent_hugepage" boot option. With 4GB hardware in this family, there might be valid uses for large pages. - root@ubuntu:/home/ubuntu# hugeadm --explain hugeadm:ERROR: kernel does not support huge pages - root@ubuntu:/home/ubuntu# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal - root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 5.4.0-1038-raspi #41-Ubuntu SMP PREEMPT Thu Jun 17 14:14:11 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux - root@ubuntu:/home/ubuntu# grep -i huge /boot/config-5.4.0-1038-raspi CONFIG_SYS_SUPPORTS_HUGETLBFS=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_HUGETLBFS is not set + + [ Test Case ] + + See above: + + [ Fix ] + + Enable HUGETLBFS and TRANSPARENT_HUGEPAGE to match the master kernel and + hirsure and later raspi kernels. + + [ Where Problems Could Occur ] + + Thess configs enable code that is disabled by default. However, there is + minimal stub code running at boot so problems would most likely show up + as splats during boot or later on when hugetlbfs is explicitly mounted + by systemd. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1933532 Title: Large Page support disabled on Raspberry Pi kernels Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: In Progress Bug description: [ Impact ] It appears that large page support and transparent hugepages are disabled in config on the Raspberry Pi. It would be nice if they were enabled in the kernel configuration, even if they are disabled by default. Then they could be set in user-editable config via the "transparent_hugepage" boot option. With 4GB hardware in this family, there might be valid uses for large pages. root@ubuntu:/home/ubuntu# hugeadm --explain hugeadm:ERROR: kernel does not support huge pages root@ubuntu:/home/ubuntu# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 5.4.0-1038-raspi #41-Ubuntu SMP PREEMPT Thu Jun 17 14:14:11 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux root@ubuntu:/home/ubuntu# grep -i huge /boot/config-5.4.0-1038-raspi CONFIG_SYS_SUPPORTS_HUGETLBFS=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_HUGETLBFS is not set [ Test Case ] See above: [ Fix ] Enable HUGETLBFS and TRANSPARENT_HUGEPAGE to match the master kernel and hirsure and later raspi kernels. [ Where Problems Could Occur ] Thess configs enable code that is disabled by default. However, there is minimal stub code running at boot so problems would most likely show up as splats during boot or later on when hugetlbfs is explicitly mounted by systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933532/+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 1952155] Re: 5.13.0-21 startup failed , show white noise screen (lenovo r9000x 4800h nvidia 2060)
Same issue after kernel update on ASUS Zephyrus G15 with AMD Ryzen 5 4600H and GTX1650Ti. A problem is coming after the system boots up. However, graphics works fine on external monitors. Kernel: Linux 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 ** Attachment added: "photo_2022-01-20_19-32-08.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952155/+attachment/894/+files/photo_2022-01-20_19-32-08.jpg -- 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/1952155 Title: 5.13.0-21 startup failed , show white noise screen (lenovo r9000x 4800h nvidia 2060) Status in linux package in Ubuntu: Confirmed Bug description: After upgrading kernel 5.13.0-21 startup failed. screen stays at white noise. laptop is lenovo r9000x , os: Linux Mint 20.2 Cinnamon cpu : amd 4800h gpu : nvidia 2060 max [code] System:Kernel: 5.11.0-40-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.7 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal Machine: Type: Laptop System: LENOVO product: 82HN v: Lenovo Legion R9000X 2021 serial: Chassis: type: 10 v: Lenovo Legion R9000X 2021 serial: Mobo: LENOVO model: LNVNB161216 v: SDK0L77769WIN serial: UEFI: LENOVO v: G1CN17WW date: 11/18/2020 Battery: ID-1: BAT0 charge: 62.3 Wh condition: 64.0/71.0 Wh (90%) volts: 15.4/N/A model: Celxpert L19C4PC3 serial: status: Unknown CPU: Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP arch: Zen rev: 1 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 92630 Speed: 1327 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1289 2: 1231 3: 1397 4: 1397 5: 1386 6: 1397 7: 1397 8: 1338 9: 2253 10: 2611 11: 1408 12: 1633 13: 1484 14: 1397 15: 1392 16: 1397 Graphics: Device-1: NVIDIA TU106 [GeForce RTX 2060] vendor: Lenovo driver: nvidia v: 460.106.00 bus ID: 01:00.0 chip ID: 10de:1f12 Device-2: AMD Renoir vendor: Lenovo driver: amdgpu v: kernel bus ID: 06:00.0 chip ID: 1002:1636 Display: x11 server: X.Org 1.20.11 driver: amdgpu,ati,nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz, 1920x1080~144Hz OpenGL: renderer: GeForce RTX 2060 with Max-Q Design/PCIe/SSE2 v: 4.6.0 NVIDIA 460.106.00 direct render: Yes Audio: Device-1: NVIDIA TU106 High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:10f9 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Lenovo driver: N/A bus ID: 06:00.5 chip ID: 1022:15e2 Device-3: AMD Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 06:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.11.0-40-generic Network: Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: 2000 bus ID: 03:00.0 chip ID: 8086:2723 IF: wlp3s0 state: up mac: Device-2: Realtek RTL8152 Fast Ethernet Adapter type: USB driver: r8152 bus ID: 5-1.4:6 chip ID: 0bda:8152 IF: enx00e04c36059b state: up speed: 100 Mbps duplex: full mac: IF-ID-1: br-db36e140ddeb state: up speed: 1 Mbps duplex: unknown mac: IF-ID-2: docker0 state: up speed: 1 Mbps duplex: unknown mac: IF-ID-3: veth0 state: up speed: N/A duplex: N/A mac: IF-ID-4: veth071d8bc state: up speed: 1 Mbps duplex: full mac: IF-ID-5: veth260b138 state: up speed: 1 Mbps duplex: full mac: IF-ID-6: veth405e95b state: up speed: 1 Mbps duplex: full mac: IF-ID-7: veth4412542 state: up speed: 1 Mbps duplex: full mac: IF-ID-8: veth56cd37a state: up speed: 1 Mbps duplex: full mac: IF-ID-9: veth9c83b77 state: up speed: 1 Mbps duplex: full mac: IF-ID-10: veth9dea6f7 state: up speed: 1 Mbps duplex: full mac: IF-ID-11: vethae53fe1 state: up speed: 1 Mbps duplex: full mac: IF-ID-12: vethdc074a2 state: up speed: 1 Mbps duplex: full mac: IF-ID-13: vethf040e52 state: up speed: 1 Mbps duplex: full mac: Drives:Local Storage: total: 1.82 TiB used: 758.93 GiB (40.7%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB512HBJQ-000L2 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: ID-2: /dev/nvme1n1 vendor: Seagate model: FireCuda 510 SSD ZP2000GM30001 size: 1.82 TiB speed: 31.6 Gb/s
[Kernel-packages] [Bug 1955070] Re: Impish update: upstream stable patchset 2021-12-16
Why is this commit not included here?
commit f95dc207b93da9c88ddbb7741ec3730c6657b88e
Author: Jens Axboe
AuthorDate: Tue Aug 31 13:57:32 2021 -0600
Commit: Jens Axboe
CommitDate: Wed Sep 1 12:35:30 2021 -0600
io-wq: split bounded and unbounded work into separate lists
We've got a few issues that all boil down to the fact that we have one
list of pending work items, yet two different types of workers to
serve them. This causes some oddities around workers switching type and
even hashed work vs regular work on the same bounded list.
Just separate them out cleanly, similarly to how we already do
accounting of what is running. That provides a clean separation and
removes some corner cases that can cause stalls when handling IO
that is punted to io-wq.
Fixes: ecc53c48c13d ("io-wq: check max_worker limits if a worker
transitions bound state")
Signed-off-by: Jens Axboe
I guess because it was added before v5.15 final, but it's critical to have,
see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195
** Changed in: linux (Ubuntu Impish)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1955070
Title:
Impish update: upstream stable patchset 2021-12-16
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Impish:
Incomplete
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-12-16
Ported from the following upstream stable releases:
v5.10.81, v5.14.21, v5.15.4
from git://git.kernel.org/
Note: upstream stable v5.14 has now reached EOL, as of
v5.14.21.
fortify: Explicitly disable Clang support
block: Add a helper to validate the block size
loop: Use blk_validate_block_size() to validate block size
bootconfig: init: Fix memblock leak in xbc_make_cmdline()
net: stmmac: dwmac-rk: fix unbalanced pm_runtime_enable warnings
parisc/entry: fix trace test in syscall exit path
PCI/MSI: Destroy sysfs before freeing entries
PCI/MSI: Deal with devices lying about their MSI mask capability
PCI: Add MSI masking quirk for Nvidia ION AHCI
erofs: remove the occupied parameter from z_erofs_pagevec_enqueue()
erofs: fix unsafe pagevec reuse of hooked pclusters
perf/core: Avoid put_page() when GUP fails
thermal: Fix NULL pointer dereferences in of_thermal_ functions
selftests/x86/iopl: Adjust to the faked iopl CLI/STI usage
KVM: Fix steal time asm constraints
Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device.
Bluetooth: btusb: Add support for TP-Link UB500 Adapter
string: uninline memcpy_and_pad
btrfs: introduce btrfs_is_data_reloc_root
btrfs: zoned: add a dedicated data relocation block group
btrfs: zoned: only allow one process to add pages to a relocation inode
btrfs: zoned: use regular writes for relocation
btrfs: check for relocation inodes on zoned btrfs in should_nocow
btrfs: zoned: allow preallocation for relocation inodes
UBUNTU: upstream stable to v5.10.81, v5.14.21, v5.15.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955070/+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 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
I can confirm the Jammy arm64 images are rebooting fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Status in casper source package in Hirsute: New Status in finalrd source package in Hirsute: New Status in linux source package in Hirsute: New Status in casper source package in Impish: New Status in finalrd source package in Impish: New Status in linux source package in Impish: New Status in casper source package in Jammy: New Status in finalrd source package in Jammy: Fix Released Status in linux source package in Jammy: Confirmed Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd ---
[Kernel-packages] [Bug 1958557] [NEW] Focal update: v5.4.169 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.169 upstream stable release from git://git.kernel.org/ net: usb: lan78xx: add Allied Telesis AT29M2-AF serial: 8250_fintek: Fix garbled text for console HID: holtek: fix mouse probing arm64: dts: allwinner: orangepi-zero-plus: fix PHY mode spi: change clk_disable_unprepare to clk_unprepare IB/qib: Fix memory leak in qib_user_sdma_queue_pkts() netfilter: fix regression in looped (broad|multi)cast's MAC handling qlcnic: potential dereference null pointer of rx_queue->page_ring net: accept UFOv6 packages in virtio_net_hdr_to_skb net: skip virtio_net_hdr_set_proto if protocol already set ipmi: Fix UAF when uninstall ipmi_si and ipmi_msghandler module bonding: fix ad_actor_system option setting to default fjes: Check for error irq drivers: net: smc911x: Check for error irq sfc: falcon: Check null pointer of rx_queue->page_ring Input: elantech - fix stack out of bound access in elantech_change_report_id() hwmon: (lm90) Fix usage of CONFIG2 register in detect function hwmon: (lm90) Add max6654 support to lm90 driver hwmon: (lm90) Add basic support for TI TMP461 hwmon: (lm90) Introduce flag indicating extended temperature support hwmon: (lm90) Drop critical attribute support for MAX6654 ALSA: jack: Check the return value of kstrdup() ALSA: drivers: opl3: Fix incorrect use of vp->state ALSA: hda/realtek: Amp init fixup for HP ZBook 15 G6 Input: atmel_mxt_ts - fix double free in mxt_read_info_block ipmi: bail out if init_srcu_struct fails ipmi: ssif: initialize ssif_info->client early ipmi: fix initialization when workqueue allocation fails parisc: Correct completer in lws start x86/pkey: Fix undefined behaviour with PKRU_WD_BIT pinctrl: stm32: consider the GPIO offset to expose all the GPIO lines mmc: sdhci-tegra: Fix switch to HS400ES mode mmc: core: Disable card detect during shutdown ARM: 9169/1: entry: fix Thumb2 bug in iWMMXt exception handling tee: optee: Fix incorrect page free bug f2fs: fix to do sanity check on last xattr entry in __f2fs_setxattr() usb: gadget: u_ether: fix race in setting MAC address in setup phase KVM: VMX: Fix stale docs for kvm-intel.emulate_invalid_guest_state mm: mempolicy: fix THP allocations escaping mempolicy restrictions pinctrl: mediatek: fix global-out-of-bounds issue hwmom: (lm90) Fix citical alarm status for MAX6680/MAX6681 hwmon: (lm90) Do not report 'busy' status bit as alarm ax25: NPD bug when detaching AX25 device hamradio: defer ax25 kfree after unregister_netdev hamradio: improve the incomplete fix to avoid NPD phonet/pep: refuse to enable an unbound pipe Linux 5.4.169 UBUNTU: upstream stable to v5.4.169 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.169 upstream stable release + from git://git.kernel.org/ -v5.4.169 upstream stable release -from git://git.kernel.org/ + net: usb: lan78xx: add Allied Telesis AT29M2-AF + serial: 8250_fintek: Fix garbled text for console + HID: holtek: fix mouse probing + arm64: dts: allwinner: orangepi-zero-plus: fix PHY mode + spi: change clk_disable_unprepare to clk_unprepare + IB/qib: Fix memory leak in qib_user_sdma_queue_pkts() + netfilter: fix regression in looped (broad|multi)cast's MAC
[Kernel-packages] [Bug 1933627] Re: HUGETLBFS is disabled
** No longer affects: linux-raspi-unstable (Ubuntu) ** No longer affects: linux-raspi-unstable (Ubuntu Impish) ** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Fix Released ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1933627 Title: HUGETLBFS is disabled Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Hirsute: Fix Released Status in linux-raspi source package in Impish: Fix Released Bug description: [Impact] Huge pages can't be managed via hugeadm which requires hugetlbfs. [Test Case] $ hugeadm --pool-list hugeadm:ERROR: kernel does not support huge pages With fix: $ hugeadm --pool-list Size Minimum Current Maximum Default 65536000 2097152000* 33554432000 1073741824000 [Fix] Enable CONFIG_HUGETLBFS [Regression Potential] This config enables code that is disabled by default. However, there is minimal stub code running at boot so problems would most likely show up as splats during boot or later on when hugetlbfs is explicitly mounted by systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933627/+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 1958374] Re: riscv: Improve support for the SiFive Unmatched board
** Summary changed:
- riscv: Improve support for the SiFive Unmathed board
+ riscv: Improve support for the SiFive Unmatched board
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1958374
Title:
riscv: Improve support for the SiFive Unmatched board
Status in linux-riscv package in Ubuntu:
New
Bug description:
The following patches should be considered for inclusion into the
v5.15 linux-image-generic kernel for the Jammy release:
commit f6f7fbb89bf8dc9132fde55cfe67483138eea880
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:42 2021 +
riscv: dts: sifive unmatched: Link the tmp451 with its power supply
Fixes the following probe warning:
lm90 0-004c: Looking up vcc-supply from device tree
lm90 0-004c: Looking up vcc-supply property in node
/soc/i2c@1003/temperature-sensor@4c failed
lm90 0-004c: supply vcc not found, using dummy regulator
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ad931d9b3b2e21586de8e6b34346d0a30c13721d
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:41 2021 +
riscv: dts: sifive unmatched: Fix regulator for board rev3
The existing values are rejected by the da9063 regulator driver, as they
are unachievable with the declared chip setup (non-merged vcore and bmem
are unable to provide the declared curent).
Fix voltages to match rev3 schematics, which also matches their boot-up
configuration within the chip's available precision.
Declare bcore1/bcore2 and bmem/bio as merged.
Set ldo09 and ldo10 as always-on as their consumers are not declared but
exist.
Drop ldo current limits as there is no current limit feature for these
regulators in the DA9063. Fixes warnings like:
DA9063_LDO3: Operation of current configuration missing
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit cd29cc8ad2540a4f9a0a3e174394d39e648ef941
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:39 2021 +
riscv: dts: sifive unmatched: Expose the PMIC sub-functions
These sub-functions are available in the chip revision on this board, so
expose them.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 8120393b74b31bbaf293f59896de6b0d50febc48
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:38 2021 +
riscv: dts: sifive unmatched: Expose the board ID eeprom
Mark it as read-only as it is factory-programmed with identifying
information, and no executable nor configuration:
- eth MAC address
- board model (PCB version, BoM version)
- board serial number
Accidental modification would cause misidentification which could brick
the board, so marking read-only seem like both a safe and non-constraining
choice.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit ea81b91e4e256b0bb75d47ad3a5c230b2171a005
Author: Vincent Pelletier
Date: Tue Nov 16 23:57:37 2021 +
riscv: dts: sifive unmatched: Name gpio lines
Follow the pin descriptions given in the version 3 of the board
schematics.
Signed-off-by: Vincent Pelletier
Signed-off-by: Palmer Dabbelt
commit 298d03c2d7f1b5daacb6d4f4053fd3d677d67087
Author: Bin Meng
Date: Wed Jun 16 15:46:45 2021 +0800
riscv: dts: unmatched: Add gpio card detect to mmc-spi-slot
Per HiFive Unmatched schematics, the card detect signal of the
micro SD card is connected to gpio pin #15, which should be
reflected in the DT via the property, as described in
Documentation/devicetree/bindings/mmc/mmc-spi-slot.txt.
[1]
https://sifive.cdn.prismic.io/sifive/6a06d6c0-6e66-49b5-8e9e-e68ce76f4192_hifive-unmatched-schematics-v3.pdf
Signed-off-by: Bin Meng
Fixes: d573b5558abb ("riscv: dts: add initial board data for the SiFive
HiFive Unmatched")
Cc: sta...@vger.kernel.org
Signed-off-by: Palmer Dabbelt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1958374/+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 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.13 (Ubuntu) Status: New => Confirmed -- 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/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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/1958494/+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 1957753] Re: net/mlx5e: EPERM on vlan 0 programming
Hello Dmitrii, can you give these test kernel a try to see if they are working as expected? F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/ H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/ I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/ J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/ This patch can be cherry-picked into I/J, but required to be backported to F/H -- 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/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Status in linux source package in Jammy: Incomplete Bug description: There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
If you want this fixed in Ubuntu I need to know what series are affected. Hirsute goes EOL at the end of the month. Are Impish and/or Jammy working or affected as well? ** Changed in: linux-firmware (Ubuntu Hirsute) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-firmware source package in Hirsute: Incomplete Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1947188] Re: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted
Well there's your root cause. It prevents dpdk from reading firmware files. https://askubuntu.com/questions/898606/operation-not-permitted-while- installing-linux-headers-4-8-0-45 ** Changed in: linux-firmware (Ubuntu Focal) 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/1947188 Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Focal: Invalid Bug description: this is encountered when I tried apt upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.17 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumaradepu 2858 F pulseaudio CasperMD5CheckResult: skip Date: Thu Oct 14 22:53:56 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-24 (20 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5539 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5300 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=f7268264-7e38-446b-b987-ce6c36322ac6 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/python3.8, Python 3.8.10, unpackaged RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: linux-firmware Title: package linux-firmware 1.187.17 failed to install/upgrade: unable to open '/lib/firmware/r128/r128_cce.bin.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2021 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0932VT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd01/22/2021:br1.13:svnDellInc.:pnLatitude5300:pvr:sku08B7:rvnDellInc.:rn0932VT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5300 dmi.product.sku: 08B7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1947188/+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 1949065] Re: Wireless-AC 9260 iwlwifi unstable and connection drops
** Changed in: linux-firmware (Ubuntu Jammy) Status: Confirmed => Incomplete -- 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/1949065 Title: Wireless-AC 9260 iwlwifi unstable and connection drops Status in linux-firmware package in Ubuntu: Incomplete Status in linux-firmware source package in Jammy: Incomplete Bug description: Ubuntu 22.04 development branch @ 28/10/2021 with kernel 5.13.0-19-generic My wifi with chipset Wireless-AC 9260 and iwlwifi are unstable and when browsing around the web a lot, i'm getting connections drops iwlwifi :02:00.0: No beacon heard and the time event is over already... and wlp2s0: Connection to AP 38:35:fb:19:91:da lost in journal logs driver=iwlwifi driverversion=5.13.0-19-generic firmware=46.6b541b68.0 9260-th-b0-jf-b0- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 1.202 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 2310 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 11:23:52 2021 Dependencies: 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 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.202 SourcePackage: linux-firmware 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:skuNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: 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-firmware/+bug/1949065/+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 1951011] Re: linux-aws: Make a signed kernel
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1951011 Title: linux-aws: Make a signed kernel Status in linux-aws package in Ubuntu: New Status in linux-aws-5.11 package in Ubuntu: Invalid Status in linux-aws-5.13 package in Ubuntu: Invalid Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Invalid Status in linux-aws-5.11 source package in Xenial: Invalid Status in linux-aws-5.13 source package in Xenial: Invalid Status in linux-aws-hwe source package in Xenial: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws-5.11 source package in Bionic: Invalid Status in linux-aws-5.13 source package in Bionic: Invalid Status in linux-aws-hwe source package in Bionic: Invalid Status in linux-aws source package in Focal: Fix Released Status in linux-aws-5.11 source package in Focal: Fix Committed Status in linux-aws-5.13 source package in Focal: Fix Committed Status in linux-aws-hwe source package in Focal: Invalid Status in linux-aws source package in Hirsute: Fix Committed Status in linux-aws-5.11 source package in Hirsute: Invalid Status in linux-aws-5.13 source package in Hirsute: Invalid Status in linux-aws-hwe source package in Hirsute: Invalid Status in linux-aws source package in Impish: In Progress Status in linux-aws-5.11 source package in Impish: Invalid Status in linux-aws-5.13 source package in Impish: Invalid Status in linux-aws-hwe source package in Impish: Invalid Bug description: SRU Justification [Impact] Ubuntu AWS kernels on secure boot instances will not load. [Fix] Generate signed kernels and packages [Test Plan] Boot in a secure boot (UEFI) environment. [Where things could go wrong] This is a new packaging feature. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951011/+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 1956105] Re: linux-firmware requires firmware-sof as a dependency
Fixed in linux-firmware 1.204. ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Fix Released -- 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/1956105 Title: linux-firmware requires firmware-sof as a dependency Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: Package should be recommended not required, for obvious reasons. https://thesofproject.github.io/latest/platforms/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1956105/+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 1957753] Re: net/mlx5e: EPERM on vlan 0 programming
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in linux source package in Hirsute: New Status in linux source package in Impish: New Status in linux source package in Jammy: Incomplete Bug description: There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+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 1933532] Re: Large Page support disabled on Raspberry Pi kernels
*** This bug is a duplicate of bug 1933627 *** https://bugs.launchpad.net/bugs/1933627 ** This bug has been marked a duplicate of bug 1933627 HUGETLBFS is disabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1933532 Title: Large Page support disabled on Raspberry Pi kernels Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: Confirmed Bug description: It appears that large page support and transparent hugepages are disabled in config on the Raspberry Pi. It would be nice if they were enabled in the kernel configuration, even if they are disabled by default. Then they could be set in user-editable config via the "transparent_hugepage" boot option. With 4GB hardware in this family, there might be valid uses for large pages. root@ubuntu:/home/ubuntu# hugeadm --explain hugeadm:ERROR: kernel does not support huge pages root@ubuntu:/home/ubuntu# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 5.4.0-1038-raspi #41-Ubuntu SMP PREEMPT Thu Jun 17 14:14:11 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux root@ubuntu:/home/ubuntu# grep -i huge /boot/config-5.4.0-1038-raspi CONFIG_SYS_SUPPORTS_HUGETLBFS=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_HUGETLBFS is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933532/+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 1958534] Re: building of linux-signed package failing on arm64
Patches have been applied and bionic/linux-signed-aws now builds
successfully
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1958534
Title:
building of linux-signed package failing on arm64
Status in linux-signed-aws package in Ubuntu:
Fix Committed
Status in linux-signed-aws source package in Bionic:
Fix Committed
Bug description:
dpkg-buildpackage
-
dpkg-buildpackage: info: source package linux-signed-aws
dpkg-buildpackage: info: source version 4.15.0-1119.126
dpkg-buildpackage: info: source distribution bionic
dpkg-source --before-build linux-signed-aws-4.15.0
dpkg-buildpackage: info: host architecture arm64
dpkg-source: info: using options from
linux-signed-aws-4.15.0/debian/source/options: --diff-ignore --tar-ignore
fakeroot debian/rules clean
sed debian/control \
-e "s/@ABI@/4.15.0-1119/g" \
-e "s/@UNSIGNED_SRC_PACKAGE@/linux-aws/g" \
-e "s/@UNSIGNED_SRC_VERSION@/4.15.0-1119.126/g" \
-e 's/@SRCPKGNAME@/linux-signed-aws/g' \
-e 's/@HEADERS_COMMON@/linux-aws-headers-4.15.0-1119/g' \
-e 's/@HEADERS_ARCH@/linux-headers-4.15.0-1119-aws/g'
rm -rf ./4.15.0-1119.126 UNSIGNED SIGNED
rm -f debian/linux-image-*.install\
debian/linux-image-*.preinst\
debian/linux-image-*.prerm \
debian/linux-image-*.postinst \
debian/linux-image-*.postrm
rm -f debian/kernel-signed-image-*.install
dh clean
dh_clean
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
./download-signed "linux-headers-4.15.0-1119-aws" "4.15.0-1119.126"
"linux-aws"
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/SHA256SUMS
... found
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/signed.tar.gz
... found
Extracting 4.15.0-1119.126 ...
Extracting 4.15.0-1119.126/control ...
Extracting 4.15.0-1119.126/control/options ...
mkdir SIGNED
( \
cd "4.15.0-1119.126" || exit 1; \
for s in *.efi.signed; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.efi.signed//'); \
( \
vars="${base}.efi.vars";\
[ -f "$vars" ] && . "./$vars"; \
if [ "$GZIP" = "1" ]; then \
gzip -9 "$s"; \
mv "${s}.gz" "$s"; \
fi; \
); \
chmod 600 "$s"; \
ln "$s" "../SIGNED/$base"; \
done; \
for s in *.opal.sig; do \
[ ! -f "$s" ] && continue; \
chmod 600 "$s"; \
base=$(echo "$s" | sed -e 's/.opal.sig//'); \
cat "$base.opal" "$s" >"../SIGNED/$base"; \
done; \
for s in *.sipl.sig; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.sipl.sig//'); \
cat "$base.sipl" "$s" >"../SIGNED/$base"; \
chmod 600 "../SIGNED/$base";\
done\
)
make[1]: Leaving directory '/<>'
fakeroot debian/rules binary-arch
dh binary-arch
dh_testroot -a
dh_prep -a
debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
for signed in "SIGNED"/*; do \
flavour=$(echo "$signed" | sed -e "s@.*-4.15.0-1119-@@");
\
instfile=$(echo "$signed" | sed -e "s@[^/]*/@@" -e
"s@-4.15.0-1119-.*@@");
[Kernel-packages] [Bug 1958534] Re: building of linux-signed package failing on arm64
Patches sent to the ML
https://lists.ubuntu.com/archives/kernel-team/2022-January/127253.html
https://lists.ubuntu.com/archives/kernel-team/2022-January/127251.html
** Changed in: linux-signed-aws (Ubuntu)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: linux-signed-aws (Ubuntu Bionic)
Assignee: (unassigned) => Ian May (ian-may)
** Changed in: linux-signed-aws (Ubuntu)
Status: New => Fix Committed
** Changed in: linux-signed-aws (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1958534
Title:
building of linux-signed package failing on arm64
Status in linux-signed-aws package in Ubuntu:
Fix Committed
Status in linux-signed-aws source package in Bionic:
Fix Committed
Bug description:
dpkg-buildpackage
-
dpkg-buildpackage: info: source package linux-signed-aws
dpkg-buildpackage: info: source version 4.15.0-1119.126
dpkg-buildpackage: info: source distribution bionic
dpkg-source --before-build linux-signed-aws-4.15.0
dpkg-buildpackage: info: host architecture arm64
dpkg-source: info: using options from
linux-signed-aws-4.15.0/debian/source/options: --diff-ignore --tar-ignore
fakeroot debian/rules clean
sed debian/control \
-e "s/@ABI@/4.15.0-1119/g" \
-e "s/@UNSIGNED_SRC_PACKAGE@/linux-aws/g" \
-e "s/@UNSIGNED_SRC_VERSION@/4.15.0-1119.126/g" \
-e 's/@SRCPKGNAME@/linux-signed-aws/g' \
-e 's/@HEADERS_COMMON@/linux-aws-headers-4.15.0-1119/g' \
-e 's/@HEADERS_ARCH@/linux-headers-4.15.0-1119-aws/g'
rm -rf ./4.15.0-1119.126 UNSIGNED SIGNED
rm -f debian/linux-image-*.install\
debian/linux-image-*.preinst\
debian/linux-image-*.prerm \
debian/linux-image-*.postinst \
debian/linux-image-*.postrm
rm -f debian/kernel-signed-image-*.install
dh clean
dh_clean
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
./download-signed "linux-headers-4.15.0-1119-aws" "4.15.0-1119.126"
"linux-aws"
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/SHA256SUMS
... found
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/signed.tar.gz
... found
Extracting 4.15.0-1119.126 ...
Extracting 4.15.0-1119.126/control ...
Extracting 4.15.0-1119.126/control/options ...
mkdir SIGNED
( \
cd "4.15.0-1119.126" || exit 1; \
for s in *.efi.signed; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.efi.signed//'); \
( \
vars="${base}.efi.vars";\
[ -f "$vars" ] && . "./$vars"; \
if [ "$GZIP" = "1" ]; then \
gzip -9 "$s"; \
mv "${s}.gz" "$s"; \
fi; \
); \
chmod 600 "$s"; \
ln "$s" "../SIGNED/$base"; \
done; \
for s in *.opal.sig; do \
[ ! -f "$s" ] && continue; \
chmod 600 "$s"; \
base=$(echo "$s" | sed -e 's/.opal.sig//'); \
cat "$base.opal" "$s" >"../SIGNED/$base"; \
done; \
for s in *.sipl.sig; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.sipl.sig//'); \
cat "$base.sipl" "$s" >"../SIGNED/$base"; \
chmod 600 "../SIGNED/$base";\
done\
)
make[1]: Leaving
[Kernel-packages] [Bug 1958534] Re: building of linux-signed package failing on arm64
This can be resolved by applying the following patches that were added
for arm64 signed support in Disco
UBUNTU: [Packaging] remove handoff check for uefi signing
UBUNTU: [Packaging] decompress gzipped efi images in signing tarball
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1958534
Title:
building of linux-signed package failing on arm64
Status in linux-signed-aws package in Ubuntu:
Fix Committed
Status in linux-signed-aws source package in Bionic:
Fix Committed
Bug description:
dpkg-buildpackage
-
dpkg-buildpackage: info: source package linux-signed-aws
dpkg-buildpackage: info: source version 4.15.0-1119.126
dpkg-buildpackage: info: source distribution bionic
dpkg-source --before-build linux-signed-aws-4.15.0
dpkg-buildpackage: info: host architecture arm64
dpkg-source: info: using options from
linux-signed-aws-4.15.0/debian/source/options: --diff-ignore --tar-ignore
fakeroot debian/rules clean
sed debian/control \
-e "s/@ABI@/4.15.0-1119/g" \
-e "s/@UNSIGNED_SRC_PACKAGE@/linux-aws/g" \
-e "s/@UNSIGNED_SRC_VERSION@/4.15.0-1119.126/g" \
-e 's/@SRCPKGNAME@/linux-signed-aws/g' \
-e 's/@HEADERS_COMMON@/linux-aws-headers-4.15.0-1119/g' \
-e 's/@HEADERS_ARCH@/linux-headers-4.15.0-1119-aws/g'
rm -rf ./4.15.0-1119.126 UNSIGNED SIGNED
rm -f debian/linux-image-*.install\
debian/linux-image-*.preinst\
debian/linux-image-*.prerm \
debian/linux-image-*.postinst \
debian/linux-image-*.postrm
rm -f debian/kernel-signed-image-*.install
dh clean
dh_clean
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
./download-signed "linux-headers-4.15.0-1119-aws" "4.15.0-1119.126"
"linux-aws"
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/SHA256SUMS
... found
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/signed.tar.gz
... found
Extracting 4.15.0-1119.126 ...
Extracting 4.15.0-1119.126/control ...
Extracting 4.15.0-1119.126/control/options ...
mkdir SIGNED
( \
cd "4.15.0-1119.126" || exit 1; \
for s in *.efi.signed; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.efi.signed//'); \
( \
vars="${base}.efi.vars";\
[ -f "$vars" ] && . "./$vars"; \
if [ "$GZIP" = "1" ]; then \
gzip -9 "$s"; \
mv "${s}.gz" "$s"; \
fi; \
); \
chmod 600 "$s"; \
ln "$s" "../SIGNED/$base"; \
done; \
for s in *.opal.sig; do \
[ ! -f "$s" ] && continue; \
chmod 600 "$s"; \
base=$(echo "$s" | sed -e 's/.opal.sig//'); \
cat "$base.opal" "$s" >"../SIGNED/$base"; \
done; \
for s in *.sipl.sig; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.sipl.sig//'); \
cat "$base.sipl" "$s" >"../SIGNED/$base"; \
chmod 600 "../SIGNED/$base";\
done\
)
make[1]: Leaving directory '/<>'
fakeroot debian/rules binary-arch
dh binary-arch
dh_testroot -a
dh_prep -a
debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
for signed in "SIGNED"/*; do \
flavour=$(echo
[Kernel-packages] [Bug 1958534] [NEW] building of linux-signed package failing on arm64
Public bug reported:
dpkg-buildpackage
-
dpkg-buildpackage: info: source package linux-signed-aws
dpkg-buildpackage: info: source version 4.15.0-1119.126
dpkg-buildpackage: info: source distribution bionic
dpkg-source --before-build linux-signed-aws-4.15.0
dpkg-buildpackage: info: host architecture arm64
dpkg-source: info: using options from
linux-signed-aws-4.15.0/debian/source/options: --diff-ignore --tar-ignore
fakeroot debian/rules clean
sed debian/control\
-e "s/@ABI@/4.15.0-1119/g" \
-e "s/@UNSIGNED_SRC_PACKAGE@/linux-aws/g" \
-e "s/@UNSIGNED_SRC_VERSION@/4.15.0-1119.126/g" \
-e 's/@SRCPKGNAME@/linux-signed-aws/g' \
-e 's/@HEADERS_COMMON@/linux-aws-headers-4.15.0-1119/g' \
-e 's/@HEADERS_ARCH@/linux-headers-4.15.0-1119-aws/g'
rm -rf ./4.15.0-1119.126 UNSIGNED SIGNED
rm -f debian/linux-image-*.install\
debian/linux-image-*.preinst\
debian/linux-image-*.prerm \
debian/linux-image-*.postinst \
debian/linux-image-*.postrm
rm -f debian/kernel-signed-image-*.install
dh clean
dh_clean
debian/rules build-arch
dh build-arch
dh_update_autotools_config -a
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
./download-signed "linux-headers-4.15.0-1119-aws" "4.15.0-1119.126" "linux-aws"
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/SHA256SUMS
... found
Downloading
http://ppa.launchpad.net/canonical-kernel-team/ppa/ubuntu/dists/bionic/main/signed/linux-aws-arm64/4.15.0-1119.126/signed.tar.gz
... found
Extracting 4.15.0-1119.126 ...
Extracting 4.15.0-1119.126/control ...
Extracting 4.15.0-1119.126/control/options ...
mkdir SIGNED
( \
cd "4.15.0-1119.126" || exit 1; \
for s in *.efi.signed; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.efi.signed//'); \
( \
vars="${base}.efi.vars";\
[ -f "$vars" ] && . "./$vars"; \
if [ "$GZIP" = "1" ]; then \
gzip -9 "$s"; \
mv "${s}.gz" "$s"; \
fi; \
); \
chmod 600 "$s"; \
ln "$s" "../SIGNED/$base"; \
done; \
for s in *.opal.sig; do \
[ ! -f "$s" ] && continue; \
chmod 600 "$s"; \
base=$(echo "$s" | sed -e 's/.opal.sig//'); \
cat "$base.opal" "$s" >"../SIGNED/$base"; \
done; \
for s in *.sipl.sig; do \
[ ! -f "$s" ] && continue; \
base=$(echo "$s" | sed -e 's/.sipl.sig//'); \
cat "$base.sipl" "$s" >"../SIGNED/$base"; \
chmod 600 "../SIGNED/$base";\
done\
)
make[1]: Leaving directory '/<>'
fakeroot debian/rules binary-arch
dh binary-arch
dh_testroot -a
dh_prep -a
debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
for signed in "SIGNED"/*; do\
flavour=$(echo "$signed" | sed -e "s@.*-4.15.0-1119-@@");
\
instfile=$(echo "$signed" | sed -e "s@[^/]*/@@" -e
"s@-4.15.0-1119-.*@@"); \
verflav="4.15.0-1119-$flavour"; \
\
package="kernel-signed-image-$verflav-di"; \
echo "$package: adding $signed";\
echo "$signed boot" >>"debian/$package.install";\
\
package="linux-image-$verflav";
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@arighi
Please urgently answer to message #141 changing the tag AND CONFIRM IT.
See message #128: I have done it for previous proposed version, but I'm allowed
to confirm, and the patch was removed from new version.
This seems to be the only way to stop this devil cycle fix-unfix.
Thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Changed in: linux-oem-5.14 (Ubuntu) Assignee: Alex Hung (alexhung) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+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 1958523] Re: Static-noise-like effect
** Package changed: ubuntu => linux-hwe-5.13 (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958523 Title: Static-noise-like effect Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+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 1921345] Re: Support MIPI camera through Intel IPU6
Hi folks, thanks for all your great work! I'm running 21.10 on my Dell 7320 Detachable. I'm wondering if you could tell me what the easiest way is to get my IPU6 tigerlake webcam to work? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Invalid Status in linux-firmware source package in Hirsute: Won't Fix Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Won't Fix Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run
[Kernel-packages] [Bug 1958523] [NEW] Static-noise-like effect
You have been subscribed to a public bug: Hello, I have encountered a bug in Ubuntu. When I turn on my laptop and log in (I can see the login screen) I see static-noise-like effect. I was able to make a screenshot and it depicts my desktop as if the problem didn't exist. Switching to stable (non-HWE) kernel solves the issue. My desktop environment is GNOME. ** Affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- Static-noise-like effect https://bugs.launchpad.net/bugs/1958523 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 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
