[Kernel-packages] [Bug 2059215] Re: HDMI Display Not detected: AMD Ryzen 5 7530U/LENOVO IdeaPad Flex 5 14ABR8
** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2059215 Title: HDMI Display Not detected: AMD Ryzen 5 7530U/LENOVO IdeaPad Flex 5 14ABR8 Status in linux-firmware package in Ubuntu: Invalid Bug description: I have been using on below system with kernel 6.5.0-15. Note: Newer than this version will not recognize the HDMI Display and will give a GPU not found error in rocminfo. System: Kernel: 6.5.0-15-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 6.0.4 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Machine: Type: Convertible System: LENOVO product: 82XX v: IdeaPad Flex 5 14ABR8 serial: Chassis: type: 31 v: IdeaPad Flex 5 14ABR8 serial: Mobo: LENOVO model: LNVNB161216 v: SDK0T76463 WIN serial: UEFI: LENOVO v: L7CN18WW date: 09/07/2023 CPU: Info: 6-core model: AMD Ryzen 5 7530U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB Speed (MHz): avg: 2660 high: 4531 min/max: 400/4546 cores: 1: 3618 2: 3632 3: 4033 4: 3622 5: 3624 6: 400 7: 4531 8: 400 9: 400 10: 3631 11: 3632 12: 400 bogomips: 47908 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Barcelo vendor: Lenovo driver: amdgpu v: 6.3.6 pcie: speed: 8 GT/s lanes: 16 ports: active: HDMI-A-1,eDP-1 empty: DP-1 bus-ID: 04:00.0 chip-ID: 1002:15e7 class-ID: 0300 Also, the GPU will not be detected in the above system if the following Update is applied. zfs-linux (2.1.5-1ubuntu6~22.04.3) jammy; urgency=medium linux-firmware (20220329.git681281e4-0ubuntu3.29) jammy; urgency=medium This will occur when one of these two is applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2059215/+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 2063143] Re: Frequent boot to black display
For the plymouth part I think the suggestion above "plymouth.use- simpledrm" makes sense. -- 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/2063143 Title: Frequent boot to black display Status in Linux: New Status in Plymouth: New Status in SDDM: New Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: Hardware: AMD Framework 13 OS: Ubuntu Noble 24.04 DE: Plasma Wayland BIOS: version 3.03 and 3.05 (latest new release) Kernel: 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux This issue started about 2-3 weeks ago I believe around the time that Ubuntu updated Noble to linux kernel 6.8 and linux firmware packages. This issue may not be a kernel regression but instead a wayland regression but I am not certain and looking for help. The issue is that on boot the (internal laptop and external displays if connected) are black but backlight is lit. I am able to boot into recovery mode without issue since the graphics drivers are not loaded in that case (only amd framebuffer driver and userspace mesa llvmpipe). Cold boot from OFF seems to be the most common case for this issue and it happens about 50-75% of the time from there. I have to force power the device off and try again in this case. I don't know how to get proper bootlogs from the previous boot when this is the case since /var/log only seems to contain logs from the current boot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 22 13:35:21 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Framework Computer Inc. Phoenix1 [f111:0006] InstallationDate: Installed on 2023-11-16 (159 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2063143/+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 2063002] Re: Add support for DCN 3.5
** Description changed: - Products with DCN 3.5 need linux-firmware to be added for noble. - Matching kernel support is already in kernel 6.8. + [Impact] + Products with DCN 3.5 need linux-firmware to be added for noble. Matching kernel support is already in kernel 6.8. + Without this firmware amdgpu won't bind. + + [Test Plan] + Boot system and ensure accelerated graphics works. + + [Where problems could occur] + This firmware is only loaded on hardware with DCN 3.5, VPE 6.1, VCN 4.0.5, SDMA 6.1.0, GC 11.5.0, or PSP 14.0.0. + + [Other info] + Here are commit IDs: 6bfdacdd amdgpu: add DMCUB 3.5 firmware cb59bf73 amdgpu: add VPE 6.1.0 firmware 3ca35ef5 amdgpu: add VCN 4.0.5 firmware 9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware 62cc1372 amdgpu: add SDMA 6.1.0 firmware b455dd24 amdgpu: add PSP 14.0.0 firmware 30c1adcb amdgpu: add GC 11.5.0 firmware -- 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/2063002 Title: Add support for DCN 3.5 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Noble: New Bug description: [Impact] Products with DCN 3.5 need linux-firmware to be added for noble. Matching kernel support is already in kernel 6.8. Without this firmware amdgpu won't bind. [Test Plan] Boot system and ensure accelerated graphics works. [Where problems could occur] This firmware is only loaded on hardware with DCN 3.5, VPE 6.1, VCN 4.0.5, SDMA 6.1.0, GC 11.5.0, or PSP 14.0.0. [Other info] Here are commit IDs: 6bfdacdd amdgpu: add DMCUB 3.5 firmware cb59bf73 amdgpu: add VPE 6.1.0 firmware 3ca35ef5 amdgpu: add VCN 4.0.5 firmware 9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware 62cc1372 amdgpu: add SDMA 6.1.0 firmware b455dd24 amdgpu: add PSP 14.0.0 firmware 30c1adcb amdgpu: add GC 11.5.0 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+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 2063002] [NEW] Add support for DCN 3.5
Public bug reported: Products with DCN 3.5 need linux-firmware to be added for noble. Matching kernel support is already in kernel 6.8. 6bfdacdd amdgpu: add DMCUB 3.5 firmware cb59bf73 amdgpu: add VPE 6.1.0 firmware 3ca35ef5 amdgpu: add VCN 4.0.5 firmware 9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware 62cc1372 amdgpu: add SDMA 6.1.0 firmware b455dd24 amdgpu: add PSP 14.0.0 firmware 30c1adcb amdgpu: add GC 11.5.0 firmware ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New ** Tags: originate-from-2063001 ** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2063002 Title: Add support for DCN 3.5 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Noble: New Bug description: Products with DCN 3.5 need linux-firmware to be added for noble. Matching kernel support is already in kernel 6.8. 6bfdacdd amdgpu: add DMCUB 3.5 firmware cb59bf73 amdgpu: add VPE 6.1.0 firmware 3ca35ef5 amdgpu: add VCN 4.0.5 firmware 9a3a6c61 amdgpu: add UMSCH 4.0.0 firmware 62cc1372 amdgpu: add SDMA 6.1.0 firmware b455dd24 amdgpu: add PSP 14.0.0 firmware 30c1adcb amdgpu: add GC 11.5.0 firmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2063002/+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 2062412] Re: No input through internal microphone (Ryzen 6000)
There is a second commit with a similar problem and really the one I
should have linked; this one is much more severe.
Here is that fix:
https://github.com/torvalds/linux/commit/37bee1855d0e3b6dbeb8de71895f6f68cad137be
It also came into 6.8.3.
3e52444ed190 ("ASoC: amd: yc: Revert "add new YC platform variant (0x63)
support"")
Maybe you can try some of the mainline PPA builds to confirm they picked up the
fix.
https://kernel.ubuntu.com/mainline/
--
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/2062412
Title:
No input through internal microphone (Ryzen 6000)
Status in linux package in Ubuntu:
New
Bug description:
The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after
updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This
is a known problem and a patch may be included in kernel 6.8.3.
Is it possible to backport this patch? Or is the plan to wait for a
kernel update? It would be good use the microphone in 24.04.
The symptoms are exactly as described in
https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297
Reportedly the patch is included in
https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2062412] Re: No input through internal microphone (Ryzen 6000)
The problem is that the "Pink Sardine" (Phoenix) laptops were being applied to the "Yellow Carp" (Rembrandt) driver. This is improper behavior and will cause other problems even if it fixed the immediate microphone issue. The Phoenix Lenovo laptops are supposed to have something in the ACPI tables that makes sure they bind properly to the Pink Sardine driver, shouldn't need quirks. You *might* be able to workaround the issue until Ubuntu issues a fix by blacklisting snd_pci_acp6x. A Phoenix laptop should be loading snd_pci_ps. -- 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/2062412 Title: No input through internal microphone (Ryzen 6000) Status in linux package in Ubuntu: New Bug description: The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This is a known problem and a patch may be included in kernel 6.8.3. Is it possible to backport this patch? Or is the plan to wait for a kernel update? It would be good use the microphone in 24.04. The symptoms are exactly as described in https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297 Reportedly the patch is included in https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2062412] Re: No input through internal microphone (Ryzen 6000)
This is the upstream solution:
https://github.com/torvalds/linux/commit/861b3415e4dee06cc00cd1754808a7827b9105bf
Here is the commit from 6.8.3:
b44a34f581b0 ("ASoC: amd: yc: Revert "Fix non-functional mic on Lenovo
21J2"")
--
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/2062412
Title:
No input through internal microphone (Ryzen 6000)
Status in linux package in Ubuntu:
New
Bug description:
The microphone in a Thinkpad P14S (AMD) Gen 4 stopped working after
updating from 23.10 to 24.04 Beta with kernel 6.8.0-22-generic. This
is a known problem and a patch may be included in kernel 6.8.3.
Is it possible to backport this patch? Or is the plan to wait for a
kernel update? It would be good use the microphone in 24.04.
The symptoms are exactly as described in
https://bbs.archlinux.org/viewtopic.php?pid=2162297#p2162297
Reportedly the patch is included in
https://github.com/zen-kernel/zen-kernel/blob/6.7/main/sound/soc/amd/yc/acp6x-mach.c#L59
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062412/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
Variable sized arrays have fallen out of fashion.
There are various patches like that which fix this issue every time it
crops up.
If you can still reproduce on the latest 6.9-rc kernels you should
report a bug upstream to get the remaining cases fixed. Or if you feel
comfortable you can write a patch for any remaining cases you hit. As
you can see it's a trivial fix.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
Confirmed
Bug description:
Error in boot:
[8.597520] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
[8.597527] index 7 is out of range for type
'ATOM_Polaris_SCLK_Dependency_Record [1]'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-generic 6.5.0.9.11
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 09:28:16 2023
InstallationDate: Installed on 2022-10-12 (373 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3
sysrq_always_enabled=1 audit=0 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
dmi.bios.date: 07/11/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: D3EMW08.110
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: D3F3-EM
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MEDION
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: D3F3-EM
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MEDION
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 2039926] Re: Error UBSAN: array-index-out-of-bounds amdgpu (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
https://patchwork.freedesktop.org/patch/588305/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2039926
Title:
Error UBSAN: array-index-out-of-bounds amdgpu
(drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c)
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux-hwe-6.5 package in Ubuntu:
Confirmed
Bug description:
Error in boot:
[8.597520] UBSAN: array-index-out-of-bounds in
/build/linux-D15vQj/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
[8.597527] index 7 is out of range for type
'ATOM_Polaris_SCLK_Dependency_Record [1]'
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-generic 6.5.0.9.11
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 09:28:16 2023
InstallationDate: Installed on 2022-10-12 (373 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=9edc5478-c6c2-4cf3-9de8-01ccb697fb9e ro quiet splash audit=0
mitigations=off amdgpu.ppfeaturemask=0x vt.global_cursor_default=0
loglevel=2 rd.systemd.show_status=false rd.udev.log-prority=3
sysrq_always_enabled=1 audit=0 vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-10-13 (6 days ago)
dmi.bios.date: 07/11/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: D3EMW08.110
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: D3F3-EM
dmi.board.vendor: MEDION
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MEDION
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrD3EMW08.110:bd07/11/2014:br4.6:svnMEDION:pnD3F3-EM:pvr1.0:rvnMEDION:rnD3F3-EM:rvr1.0:cvnMEDION:ct3:cvr:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: D3F3-EM
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: MEDION
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039926/+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 2056445] Re: external monitors flash white with every interrupt
It was confirmed by many people this is fixed in the upgraded Framework BIOS 3.05. ** Changed in: linux (Ubuntu) Status: Triaged => 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Invalid Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2056803] Re: amdgpu: hotplugging display sometimes fails
*** This bug is a duplicate of bug 2056445 *** https://bugs.launchpad.net/bugs/2056445 ** This bug has been marked a duplicate of bug 2056445 external monitors flash white with every interrupt -- 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/2056803 Title: amdgpu: hotplugging display sometimes fails Status in linux package in Ubuntu: New Bug description: Description:Ubuntu Noble Numbat (development branch) Release:24.04 Kernel info: Linux gman-Laptop-13-AMD-Ryzen-7040Series 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Hardware: AMD Framework 13 Expected: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) after boot does not fail every time What happened: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) frequently fails with either: - no outout - a white screen with only the mouse cursor visible - attempt enable and disable over and over again with dmesg log spam and KDE display configuration showing that the display arrangement changes every couple of seconds this problem is not observed on Windows 11 with the same hardware. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 11 16:59:30 2024 InstallationDate: Installed on 2023-11-16 (117 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-02-25 (16 days ago) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056803/+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 2056445] Re: external monitors flash white with every interrupt
I have a suspicion the root cause of the white screen could be fixed in BIOS 3.05. https://community.frame.work/t/framework- laptop-13-ryzen-7040-bios-3-05-release-and-driver-bundle-beta/48276 Can you still reproduce it with no workarounds, 6.8.0-20 and the BIOS upgrade? -- 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2060268] Re: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver
Probably nvidia.ko is missing a call to drm_aperture_remove_conflicting_pci_framebuffers() -- 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/2060268 Title: Phantom 46" monitor (simpledrm) shown in Settings after installing the Nvidia driver Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-545 package in Ubuntu: New Bug description: After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. --- ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060268/+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 2059807] Re: Power management settings on Ryzen 7 5800H are missing
This is because amd-pstate is in active mode but nothing is tuning EPP most likely. Try to upgrade to this version of power profiles daemon: https://launchpad.net/~superm1/+archive/ubuntu/ppd Then you can change the power setting using the Gnome or kde GUI for it or by using powerprofilesctl. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2059807 Title: Power management settings on Ryzen 7 5800H are missing Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: After the update to kernel 6.5, cpufreq no longer has options to set most governors or frequencies. The only available options are powersave and performance, but changing between them seem to have no effect. Consequently, the CPU temperature is always high: while with the 6.2 kernel it would idle at under 50°C, now with 6.5 it's idling at 65°C. Under a load that, with the 6.2 kernel, would result in around 80°C on CPU and 70°C on motherboard, now with the 6.5 it results in 100°C on both CPU and motherboard (I barely can touch the laptop because it gets so hot). To be able to use my laptop properly, I'm having to choose the 6.2 kernel on boot time. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Mar 29 15:54:34 2024 InstallationDate: Installed on 2017-06-13 (2480 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2019-12-22 (1558 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2059807/+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 2056445] Re: external monitors flash white with every interrupt
> I'll also report back once I am able to test the new kernel. I had a try and I was able to install it today on Noble by pulling the deb packages for linux-image-unsigned-6.8.0-20-generic, linux- modules-6.8.0-20-generic, linux-modules-extra-6.8.0-20-generic from Launchpad manually. -- 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2056445] Re: external monitors flash white with every interrupt
> this system has a single DIMM which was provided by framework: DDR5-5600 - 32GB (1 x 32GB) My system is 8GB, single stick, same speed 5600 MT/s, same company (A-DATA). > Restarting firefox temporarily resolves the issue. This behavior started to happen after I switched to X11. You're the first I've ever heard of this. Hopefully it's not present in Wayland. There is very little testing or development that happens in X11. > After setting UMA_Game_Optimized, I can confirm that (after 30 minutes of usage), the system appears far more stable. That's good to hear the workarounds improve things for you too. -- 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2051410] Re: AMD-GPU, decrease video resolution leads to black screen
*** This bug is a duplicate of bug 2046504 *** https://bugs.launchpad.net/bugs/2046504 ** This bug has been marked a duplicate of bug 2046504 AMD GPU display is blank when set lower resolution than native mode on eDP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051410 Title: AMD-GPU, decrease video resolution leads to black screen Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Only the highest resolution can be set (1920x1080). If the resolution will be set to e.g,: 1280x720, only a black screen will be seen. Also games, or "Wine" application does not work, former resolution settings can not be changed, start the "Wine" application leads also to a black screen (rebooting necessary). Additionalinformation Xorg.0.log, resolution modified : [ 4028.159] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4028.170] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4028.170] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4253.595] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4254.499] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4254.499] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4254.508] (II) AMDGPU(0): Allocate new frame buffer 1280x720 [ 4254.509] (II) AMDGPU(0): => pitch 5120 bytes [ 4254.859] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4254.859] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4254.859] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4255.673] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4255.674] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4255.674] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.307] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.307] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.307] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.768] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.768] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.768] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4274.945] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4274.945] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4274.969] (II) AMDGPU(0): Allocate new frame buffer 1920x1080 [ 4274.984] (II) AMDGPU(0): => pitch 7680 bytes [ 4276.213] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.213] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.213] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4276.327] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.327] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.327] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.060] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.060] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.060] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.180] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.180] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.180] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4292.371] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4293.277] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4293.277] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4293.293] (II) AMDGPU(0): Allocate new frame buffer 1680x1050 [ 4293.294] (II) AMDGPU(0): => pitch 7168 bytes [ 4293.642] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4293.642] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4293.642] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.332] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.332] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.332] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.416] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.416] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.416] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP)
[Kernel-packages] [Bug 2056445] Re: external monitors flash white with every interrupt
> Am I missing something to get the proposed kernel? I guess the same reason it's not migrating is the reason you can't install it? Maybe some kernel team members can comment. > It sounds like GTT access is what causes this issue, and that using the bios option won't guarantee that it will never happen. Is that correct? If you look at your journal from when this issue occurs you'll see an IOMMU page fault. This is the IOMMU reporting that there was an attempted access at memory that is out of the region that the GPU is allowed to access. This can happen when there is a userspace driver bug (IE mesa) or a misconfigured driver (IE amdgpu) or a faulty firmware (IE the BIOS). There have been cases of a white screen caused by an incorrect memory addressing mask on systems with 64GB, but that's been fixed a long time now. It is definitely an attempt at accessing outside of VRAM but I have a suspicion the address attempting to be addressed is ALSO outside of GTT. > Interesting. If there's any extra info (or testing) I can provide to help with debugging/fixing this issue, please let me know. If you can add your details for your "specific" FW13 AMD to the upstream bug maybe others who are affected can help with building the pattern. I mean the memory vendor, speed of memory, amount, channel configuration. What you do to trigger it, etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2056445] Re: external monitors flash white with every interrupt
> Should this fix the flickering issue? I'm happy to test it out. It will fix a colored flickering; but not the white screen (if that is what you're observing). It also fixes issues with suspend/resume that were present in earlier 6.8-rc kernels but fixed by the final version. > I'm curious about the implications of the two workarounds presented. I see that UMA_Game_Optimized will reserve some system ram for the GPU, which I don't have any issues with if there is some benefit. Will this use scatter/gather and therefore perform better as a result? If you use the BIOS option yes it will carve out more memory for VRAM use. S/G is still used, but GTT memory is less likely to be accessed when you have more VRAM. If you turn off S/G then GTT will NEVER be used. The potential negative implication for the BIOS option is more RAM being used for GPU that can't be for anything else. The potential negative implications of turning off S/G in the driver are that the driver may run out of memory in some situations that require a lot of VRAM such as multiple 4k monitor docking. FWIW - I have a FW13 AMD and I've never seen this white screen problem myself. I don't know if it is tied to RAM vendor, RAM size, or a BIOS issue. My educated guess is it's actually a BIOS issue and it might be properly fixed when FW upgrades to the next BIOS. -- 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: New Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2058830] Re: vp9 hw decode broken on modern AMD apus, needs amdgpu update
** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Assignee: Jose Ogando Justo (joseogando) Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => Jose Ogando Justo (joseogando) ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => Jose Ogando Justo (joseogando) ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #8044 https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044 ** Also affects: linux-firmware via https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044 Importance: Unknown Status: Unknown -- 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/2058830 Title: vp9 hw decode broken on modern AMD apus, needs amdgpu update Status in Linux Firmware: Unknown Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Mantic: New Status in linux-firmware source package in Noble: Fix Released Bug description: Current version of amdgpu binaries in linux-firmware shipped with ubuntu 22.04 (jammy) and ubuntu 23.10 (mantic) create various problems when decoding VP9 content with the iGPU on modern AMD mobile processor (rembrant and phoenix, i.e. 6xxxU/H, 7x40U/H and 7x35U/H processor). The issue has been reported and solved upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8044 [EDIT: fixed link] Solution dates to the end of February: https://gitlab.com/kernel- firmware/linux- firmware/-/commit/977332782302476e1c863b09b840f463d0378807 Ubuntu 24.04 already ships the updated binaries and should not be affected. Steps to reproduce: * on an affected system play a VP9 video with hardware decoding Additional links: * https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=977332782302476e1c863b09b840f463d0378807 * https://bugzilla.redhat.com/show_bug.cgi?id=2267714 * https://www.phoronix.com/news/AMDGPU-Firmware-Fixes-VP9 Workaround: * download the amdgpu folder from upstream linux-firmware repos * compress each file with zstd * copy into /lib/firmware/amdgpu * regenerate the initrd I'm currently running ubuntu 23.10 (mantic) with binaries from upstream and the issue is solved. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2058830/+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 2057424] Re: No variable refresh rate (VRR) on the Framework 16
FWIW it's in drm-fixes now. https://cgit.freedesktop.org/drm/drm/commit/?id=2f14c0c8cae8e9e3b603a3f91909baba66540027 -- 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/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+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 2054489] Re: Crash on blank screen
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
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/2054489
Title:
Crash on blank screen
Status in linux package in Ubuntu:
New
Bug description:
When my computer screen goes blank and then locks due to inactivity,
the screen goes white and requires a reboot to recover.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu7
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 20 17:29:43 2024
InstallationDate: Installed on 2024-02-02 (19 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.6.0-14-generic N/A
linux-backports-modules-6.6.0-14-generic N/A
linux-firmware20240202.git36777504-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA735010072
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054489/+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 2053040] Re: GPU Crash When Waking from Suspend
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
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/2053040
Title:
GPU Crash When Waking from Suspend
Status in linux package in Ubuntu:
New
Bug description:
Screen goes completely white, have to reboot the system to recover.
I've manually attached the kernel log from the previous boot which
contains the relevant errors.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 13 10:19:39 2024
InstallationDate: Installed on 2024-02-02 (12 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.6.0-14-generic N/A
linux-backports-modules-6.6.0-14-generic N/A
linux-firmware20240202.git36777504-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA735010072
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053040/+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 2052467] Re: Unplugging External Monitor Causes GPU Crash
*** This bug is a duplicate of bug 2056445 ***
https://bugs.launchpad.net/bugs/2056445
** This bug has been marked a duplicate of bug 2056445
external monitors flash white with every interrupt
--
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/2052467
Title:
Unplugging External Monitor Causes GPU Crash
Status in linux package in Ubuntu:
New
Bug description:
Unplugging an exteranal usb-c monitor caused the GPU to crash - the
screen went white and unresponsive, reboot was required for the
machine to become usable.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:holmanb1976 F pipewire
/dev/snd/controlC0: holmanb1989 F wireplumber
/dev/snd/controlC1: holmanb1989 F wireplumber
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 5 16:20:03 2024
InstallationDate: Installed on 2024-02-02 (4 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.0-14-generic
root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.6.0-14-generic N/A
linux-backports-modules-6.6.0-14-generic N/A
linux-firmware20240202.git36777504-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA735010072
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052467/+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 2056445] Re: external monitors flash white with every interrupt
I suggest updating to 6.8.0-20 though, this 6.8.0-11 has an old 6.8-RC snapshot and there are other bugs that got fixed later on in the 6.8-RC's. -- 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 2056445] Re: external monitors flash white with every interrupt
For some unknown reason this only seems to be reported on some people's Framework 13 AMD laptops. FYI - there are two workarounds for those currently encountering this issue. * On the kernel command line: amdgpu.sg_display=0 * Change the BIOS settings from Auto to UMA_Game_Optimized. ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3187 https://gitlab.freedesktop.org/drm/amd/-/issues/3187 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/3187 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Status: New => Triaged -- 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/2056445 Title: external monitors flash white with every interrupt Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: an interesting amdgpu issue: I currently have two external monitors, and only one will display the desktop at a time - the other is completely white. The interesting thing is that with each interrupt that the kernel receives from keyboard / mouse, the screens will flip which one is visible. With my monitors positioned above and to the left of the laptop's built-in display, the flashing monitors feel akin to attending an electronic light show, or perhaps a display of fireworks - the monitors flip visibility with each keypress. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 05:23:23 2024 InstallationDate: Installed on 2024-02-02 (34 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240123) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-11-generic root=UUID=8de457ce-abc8-47cf-a43f-c13183977aa5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP07 dmi.board.vendor: Framework dmi.board.version: A7 dmi.chassis.asset.tag: FRANDGCPA735010072 dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A7 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP07 dmi.product.version: A7 dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2056445/+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 1970069] Re: Annoying boot messages interfering with splash screen
Can you double check the framebuffer FB related conf options in your kconfig against those in Fedora? -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
The backend is a framebuffer driver. For example efifb which uses the framebuffer set up by GOP in pre-boot. If there are framebuffer drivers in tinydrm then maybe they matter for those architectures. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2057424] Re: No variable refresh rate (VRR) on the Framework 16
V2 addressed comments and was reviewed. -- 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/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+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 2056498] Re: Kernel crash in amd gpu driver
*** This bug is a duplicate of bug 2039926 *** https://bugs.launchpad.net/bugs/2039926 ** This bug has been marked a duplicate of bug 2039926 Error UBSAN: array-index-out-of-bounds amdgpu (drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2056498 Title: Kernel crash in amd gpu driver Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Mar 7 19:07:10 ripper kernel: [9.873519] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4 Mar 7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for type 'ATOM_Polaris_SCLK_Dependency_Record [1]' Mar 7 19:07:10 ripper kernel: [9.873538] CPU: 4 PID: 849 Comm: systemd-udevd Not tainted 6.5.0-17-generic #17~22.04.1-Ubuntu Mar 7 19:07:10 ripper kernel: [9.873542] Hardware name: LENOVO 30E1S3VV00/1046, BIOS S07KT45A 01/20/2022 Mar 7 19:07:10 ripper kernel: [9.873544] Call Trace: Mar 7 19:07:10 ripper kernel: [9.873545] Mar 7 19:07:10 ripper kernel: [9.873547] dump_stack_lvl+0x48/0x70 Mar 7 19:07:10 ripper kernel: [9.873551] dump_stack+0x10/0x20 Mar 7 19:07:10 ripper kernel: [9.873554] __ubsan_handle_out_of_bounds+0xc6/0x110 Mar 7 19:07:10 ripper kernel: [9.873560] smu7_get_pp_table_entry_callback_func_v1+0x9b7/0xa00 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.873897] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.873900] ? vi_pcie_rreg+0x6e/0x90 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874187] ? __pfx_smu7_get_pp_table_entry_callback_func_v1+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874515] get_powerplay_table_entry_v1_0+0xf8/0x490 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.874842] smu7_get_pp_table_entry_v1+0x41/0x4c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875169] smu7_get_pp_table_entry+0x3d/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875495] psm_init_power_state_table+0x161/0x250 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.875826] hwmgr_hw_init+0xe3/0x1e0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876150] pp_hw_init+0x16/0x50 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876484] amdgpu_device_ip_init+0x48d/0x960 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.876749] amdgpu_device_init+0x9a2/0x1150 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877014] amdgpu_driver_load_kms+0x1a/0x1c0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877278] amdgpu_pci_probe+0x182/0x450 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877541] local_pci_probe+0x47/0xb0 Mar 7 19:07:10 ripper kernel: [9.877545] pci_call_probe+0x55/0x190 Mar 7 19:07:10 ripper kernel: [9.877550] pci_device_probe+0x84/0x120 Mar 7 19:07:10 ripper kernel: [9.877553] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.877557] really_probe+0x1cc/0x430 Mar 7 19:07:10 ripper kernel: [9.877560] __driver_probe_device+0x8c/0x190 Mar 7 19:07:10 ripper kernel: [9.877563] driver_probe_device+0x24/0xd0 Mar 7 19:07:10 ripper kernel: [9.877566] __driver_attach+0x10b/0x210 Mar 7 19:07:10 ripper kernel: [9.877569] ? __pfx___driver_attach+0x10/0x10 Mar 7 19:07:10 ripper kernel: [9.877572] bus_for_each_dev+0x8d/0xf0 Mar 7 19:07:10 ripper kernel: [9.877576] driver_attach+0x1e/0x30 Mar 7 19:07:10 ripper kernel: [9.877579] bus_add_driver+0x127/0x240 Mar 7 19:07:10 ripper kernel: [9.877583] driver_register+0x5e/0x130 Mar 7 19:07:10 ripper kernel: [9.877586] ? __pfx_amdgpu_init+0x10/0x10 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.877849] __pci_register_driver+0x62/0x70 Mar 7 19:07:10 ripper kernel: [9.877852] amdgpu_init+0x69/0xff0 [amdgpu] Mar 7 19:07:10 ripper kernel: [9.878111] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878114] do_one_initcall+0x5e/0x340 Mar 7 19:07:10 ripper kernel: [9.878120] do_init_module+0x68/0x260 Mar 7 19:07:10 ripper kernel: [9.878123] load_module+0xb85/0xcd0 Mar 7 19:07:10 ripper kernel: [9.878128] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878131] ? security_kernel_post_read_file+0x75/0x90 Mar 7 19:07:10 ripper kernel: [9.878136] init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878139] ? srso_return_thunk+0x5/0x10 Mar 7 19:07:10 ripper kernel: [9.878142] ? init_module_from_file+0x96/0x100 Mar 7 19:07:10 ripper kernel: [9.878149] idempotent_init_module+0x11c/0x2b0 Mar 7 19:07:10 ripper kernel: [9.878155] __x64_sys_finit_module+0x64/0xd0 Mar 7 19:07:10 ripper kernel: [9.878159] do_syscall_64+0x5b/0x90
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding all those other drm drivers makes a lot of sense. No use doubling the initrd size for the LUKS 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/1970069 Title: Annoying boot messages interfering with splash screen Status in initramfs-tools package in Ubuntu: Opinion Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
AFAICT; these initramfs-tools package changes would cover it: * hooks/framebuffer can be totally removed. * scripts/init-top/framebuffer should probably stay * conf/initramfs.conf needs FRAMEBUFFER=y added to it -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Plymouth only gets added to the initrd when LUKS is enabled or you mark another reason for needing the framebuffer. So the suggestion I have from comment #49 is to mark needing the framebuffer by default, and then stop including any DRM modules because simpledrm is built into the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Bug description: [ Impact ] Kernel (and systemd) log messages appear during boot for many machines, when the user should be seeing only the BIOS logo and/or Plymouth splash screens. [ Workaround ] On most machines you can hide the problem by using these kernel parameters together: quiet splash loglevel=2 fastboot [ Test Plan ] 1. Boot Ubuntu on a number of laptops that have the problem and verify no console text messages appear during boot. 2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still. 3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages should appear. [ Where problems could occur ] Since the fix works by deferring fbcon's takeover of the console, the main problem encountered during its development was the inability to VT switch. [ Original Description ] Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
#33, was your issue a one boot problem? Or it happens every time? Is
it tied to specifically that kernel + firmware, or is it also with older
kernel?
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I tested with a Framework 16 with a 14c3:0616 WLAN. With
20220329.git681281e4-0ubuntu3.28 it's completely unusable with my AP
unless I turn off power save with iwconfig (Unifi).
With to 20220329.git681281e4-0ubuntu3.29 it works as expected.
** Tags removed: verification-failed-jammy
** Tags added: verification-done-jammy
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2036737] Re: Enable dynamic boost control in ccp kernel driver
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Triaged => 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/2036737 Title: Enable dynamic boost control in ccp kernel driver Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Won't Fix Bug description: [Impact] We need to backport dynamic boost control into OEM-6.5 kernel. This request is to backport the ccp changes. Here are the commits necessary to backport to OEM-6.5 kernel from kernel 6.6: b58276372182 crypto: ccp - Rename macro for security attributes 2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost control d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost control e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters Here are the commits necessary to backport to OEM-6.5 kernel from kernel 6.7: 53f7f779f45c crypto: ccp - Get a free page to use while fetching initial nonce [Test case] WIP [Regression potential] WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036737/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
Internal team at AMD has tested an OEM RMB that doesn't need the DP swap change to check for any potential regression. They tested using OEM 6.5-1014 kernel. This testing well. Anson will confirm results on the system needing DP swap after he's back from holiday. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
Internal team at AMD has tested across a number of different OEM PHX
systems using OEM 6.5-1014 kernel. This is testing well.
** Tags added: verification-done-jammy
--
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/2051636
Title:
AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker
[Fix]
Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and
other prerequisites:
* amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1
firmware")
* amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4
firmware")
* amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2
firmware")
* amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4
firmware")
* amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11
firmware")
[Test Case]
Run stress tool like 3DMark or GravityMark.
[Where problems could occur]
Binary firmware update recommended by chip vendor. No known issue so
far.
[Other Info]
Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy
is also nominated for fix.
== original bug report ==
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker. Also using mantic +
v6.7 hit the hang, so need to update new FWs to fix this issue.
PHX series
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85
[ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0
timeout, signaled seq=27035, emitted seq=27037
[ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421
[ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin!
[ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.334377] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.464226] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.464398] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.594247] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.594418] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.724265] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.724432] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.854275] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.854437] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.984284] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.984456] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.996743] amdgpu :0d:00.0:
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
The two missing commits are specified in comment #4.
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1180974eb33ac67903269b71f35a489a2b77e5e9
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/6b91b2ef6f4173099c1434e5d7c552e51814e26e
** Tags added: verification-failed-jammy
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
I examined the packages and I notice the MT7921 firmware (Which
confusingly goes by MT7961) is updated but "not" the MT7922 firmware.
Based on the above comments and below finding it seems that the MT7921
hardware is fixed with the update but not the MT7922 (which also
confusingly uses the mt7921e driver...).
I think it needs to be bumped again to pull in the MT7922 commits.
Upstream:
$ md5sum *MT79*
7cf075421ea7b6b9d0721b8744c2a576 BT_RAM_CODE_MT7922_1_1_hdr.bin
f8e386541ca02a6311d7c0d9441fbab7 BT_RAM_CODE_MT7961_1_2_hdr.bin
5b1812463de97fcb04f4eba19f37dafd WIFI_MT7922_patch_mcu_1_1_hdr.bin
0a4d833efe94a56c502de8a38405d8fe WIFI_MT7961_patch_mcu_1_2_hdr.bin
77aaec5c622d01736f7a0a5ac3d0558b WIFI_RAM_CODE_MT7922_1.bin
8d0a4f6dc2d01a8b442ae0b8d76d9122 WIFI_RAM_CODE_MT7961_1.bin
Jammy (as of 20220329.git681281e4-0ubuntu3.28)
$ md5sum *MT79*
98423461b3d66e93368a3228de2c1e4a BT_RAM_CODE_MT7922_1_1_hdr.bin
f8e386541ca02a6311d7c0d9441fbab7 BT_RAM_CODE_MT7961_1_2_hdr.bin
4180dc35aa66f62ab8a3e202b4712560 WIFI_MT7922_patch_mcu_1_1_hdr.bin
0a4d833efe94a56c502de8a38405d8fe WIFI_MT7961_patch_mcu_1_2_hdr.bin
8ff1bdc0f54f255bb2a1d6825781506b WIFI_RAM_CODE_MT7922_1.bin
8d0a4f6dc2d01a8b442ae0b8d76d9122 WIFI_RAM_CODE_MT7961_1.bin
Nobel (as of 20240202.git36777504-0ubuntu1)
$ md5sum *MT79*
7cf075421ea7b6b9d0721b8744c2a576 BT_RAM_CODE_MT7922_1_1_hdr.bin
f8e386541ca02a6311d7c0d9441fbab7 BT_RAM_CODE_MT7961_1_2_hdr.bin
5b1812463de97fcb04f4eba19f37dafd WIFI_MT7922_patch_mcu_1_1_hdr.bin
0a4d833efe94a56c502de8a38405d8fe WIFI_MT7961_patch_mcu_1_2_hdr.bin
77aaec5c622d01736f7a0a5ac3d0558b WIFI_RAM_CODE_MT7922_1.bin
8d0a4f6dc2d01a8b442ae0b8d76d9122 WIFI_RAM_CODE_MT7961_1.bin
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Did you put any other files in /lib/firmware? Maybe the output of
$tree /lib/firmware
Would explain what is going on.
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Do you perhaps have the older version in /lib/firmware/updates?
--
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/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Noble got updated: https://launchpad.net/ubuntu/+source/linux-
firmware/20240202.git36777504-0ubuntu1
Still waiting for others.
** Changed in: linux-firmware (Ubuntu Noble)
Status: Triaged => 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/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 1970069] Re: Annoying boot messages interfering with splash screen
With your change Fedora and Ubuntu are now behaving relatively similarly. * Both have a deficiency where the handoff from BGRT logo to Plymouth is doing a modeset for some reason. * Due to something in Fedora's GRUB it's a little clearer when GRUB starts. Here's various artifacts if you want to be able to compare anything since I have both on the same hardware. I ran the same kernel binary that has your patches on both (but on Fedora it behavedthe same with a stock one). Ubuntu booting (video): https://youtu.be/1J0_Vg1pScQ Kernel config: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-kernel-config-both Ubuntu /etc/default/grub: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-etc-default-grub Ubuntu journal: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-ubuntu-journal Fedora booting (video): https://youtu.be/IzesNHpM-nw Fedora journal: https://gist.github.com/superm1/77de12fccd01715697029a28de2dbce5#file-fedora-journal -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black screen. Moving that to zero certainly helps. It's a lot better; but still not perfect. Let me get things back to as close as possible to stock and capture logs and a videos to compare with Ubuntu and Fedora with this exact same kernel and I'll get back. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
I tested it on Noble with a hand built kernel and it at least does what you planned (don't see any console messages), but also I'm not seeing the OEM vendor logo stick all the way through. There's a really long time of a black screen. Not sure if this is because it was an upstream kernel and it's missing a VT switch patch or something. Does that match what you're seeing? -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
You could detect both parameters to avoid that corner case. Alternatively this is something I feel simpledrm will help you avoid hitting too. Otherwise it sounds good to me. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Yeah; so try forcing plymouth to the Ubuntu initrd like this: echo "FRAMEBUFFER=y" | sudo tee /etc/initramfs-tools/conf.d/splash Then if you rebuild the initrd you'll end up with plymouth in it. This unfortunately DOUBLES the initramfs size; but it's because it puts all the drm modules in there. Here is where simpledrm really shines. I belive /usr/share/initrams-tools/hooks/plymouth can be modified to stop including any drm modules and /usr/share/initramfs-tools/framebuffer can be totally dropped. I believe this will guarantee plymouth wins the race. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Something "big" I notice different is that by default Ubuntu doesn't put plymouth in the initramfs but Fedora does. Maybe plymouthd really isn't running at the time systemd-fsckd is running. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
> I don't really know if Fedora does that better or they just failed to notice the bug. I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in Fedora with simpledrm; never see the console. That's why I was thinking something might be missing and worth looking at. * Fedora doesn't key off "splash", they key off "rhgb" (standing for red hat graphical boot). * Ubuntu sets "vt.handoff=7", Fedora doesn't do anything. Maybe it's part of this flow difference leading to the problem? That's from ~10 years ago, does it still make sense? -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
> But the feature would still be gated on the "splash" kernel parameter which is Plymouth-specific and may cause pushback from kernel developers. If the patch is the way you go another idea for you is to use the "quiet" keyword to key off instead for this behavior which is already used by the kernel. You'd be overloading it. quiet [KNL] Disable most log messages -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
Have you already looked at everything Fedora is doing in this area? They already have simpledrm; but from what you described I would have thought they should still lose the fbcon race. Is it just that they don't have systemd-fsckd patch? I would think they still end up showing ERR/WARN kernel messages which can be noisy too. Just wondering if there is something else to look at. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
JFYI
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37 [1] is
reported to fix issues that were found in 36 in [2].
[1]
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/5217b76bed90ae86d5f3fe9a5f4e2301868cdd02
[2] https://bugzilla.kernel.org/show_bug.cgi?id=217239
** Bug watch added: Linux Kernel Bug Tracker #217239
https://bugzilla.kernel.org/show_bug.cgi?id=217239
--
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/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
Triaged
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
* 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
* 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
update board-2.bin") to forfill git history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2051410] Re: AMD-GPU, decrease video resolution leads to black screen
Probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867. Try turning on proposed and getting 6.5.0-17.17 to see if it helps. It picks up that fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051410 Title: AMD-GPU, decrease video resolution leads to black screen Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: Only the highest resolution can be set (1920x1080). If the resolution will be set to e.g,: 1280x720, only a black screen will be seen. Also games, or "Wine" application does not work, former resolution settings can not be changed, start the "Wine" application leads also to a black screen (rebooting necessary). Additionalinformation Xorg.0.log, resolution modified : [ 4028.159] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4028.170] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4028.170] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4253.595] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4254.499] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4254.499] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4254.508] (II) AMDGPU(0): Allocate new frame buffer 1280x720 [ 4254.509] (II) AMDGPU(0): => pitch 5120 bytes [ 4254.859] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4254.859] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4254.859] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4255.673] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4255.674] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4255.674] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.307] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.307] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.307] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4256.768] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4256.768] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4256.768] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4274.945] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4274.945] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4274.969] (II) AMDGPU(0): Allocate new frame buffer 1920x1080 [ 4274.984] (II) AMDGPU(0): => pitch 7680 bytes [ 4276.213] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.213] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.213] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4276.327] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4276.327] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4276.327] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.060] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.060] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.060] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4277.180] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4277.180] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4277.180] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4292.371] (EE) AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter [ 4293.277] (WW) AMDGPU(0): flip queue failed: Invalid argument [ 4293.277] (WW) AMDGPU(0): Page flip failed: Invalid argument [ 4293.293] (II) AMDGPU(0): Allocate new frame buffer 1680x1050 [ 4293.294] (II) AMDGPU(0): => pitch 7168 bytes [ 4293.642] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4293.642] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4293.642] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.332] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.332] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.332] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4294.416] (II) AMDGPU(0): EDID vendor "AUO", prod id 8685 [ 4294.416] (II) AMDGPU(0): Printing DDC gathered Modelines: [ 4294.416] (II) AMDGPU(0): Modeline "1920x1080"x0.0 141.00 1920 2028 2076 2100 1080 1090 1100 1116 -hsync -vsync (67.1 kHz eP) [ 4295.110] (II) AMDGPU(0): EDID vendor
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
> Also to prevent Grub from blanking the screen you need to uncomment: Can you open another bug against GRUB to fix this default for Noble? > Thanks for testing, so DRM_SIMPLEDRM needs to be built-in for it to work properly Yeah it should need to be built in. > But bug 1970069 still pops up after that. Too bad; but it sounds like between simpledrm, the GRUB policy change and your fbcon patch it would be a great experience! -- 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in linux source package in Mantic: Won't Fix Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux source package in Noble: Confirmed Status in nvidia-graphics-drivers-470 source package in Noble: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer [ Test Plan ] * Ensure that systems currently relying on fbdev (and therefore only allowing Xorg logins) such as some virtual machine types, boot with working Wayland support. [ Where Problems could occur ] * When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen (bug 2039757). * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+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 1970069] Re: Annoying boot messages interfering with splash screen
> This seems to be a bug in the kernel documentation. Yeah I guess so. > I'm now waiting until my conversation with Daniel Vetter is concluded before formulating a plan for how to approach dri-devel. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1970069] Re: Annoying boot messages interfering with splash screen
I'm not sure where you posted that to, I didn't see it dri-devel. But I think this is the first use of "splash" from the kernel command line within the kernel. I think it needs to be documented. -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 1990052] Re: fwupdtool reports an error (KERNEL BUG) when refreshing
AFAICT those kernel commits are now landed in Ubuntu's kernel. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990052 Title: fwupdtool reports an error (KERNEL BUG) when refreshing Status in Linux: Fix Released Status in fwupd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: when running the "refresh" command I get the following message $ sudo fwupdtool refresh Loading… [** ]07:43:19:0893 FuBiosSettings KERNEL BUG: 'type' attribute not exported: (failed to load type: Failed to open file “/sys/class/firmware-attributes/thinklmi/attributes/TotalMemoryEncryption/type”: No such file or directory) Loading… [- ] Downloading… [***] Downloading… [***] Downloading… [** ] Not sure if it's just a warning or an actual error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: fwupd 1.8.4-2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Sep 18 09:43:50 2022 InstallationDate: Installed on 2022-09-11 (6 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-09-11 (7 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) MachineType: LENOVO 21AHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-16-generic root=UUID=77d67dcd-a70a-4ee7-be9d-00c2cf6248c2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-16-generic N/A linux-backports-modules-5.19.0-16-generic N/A linux-firmware 20220831.gitd3c92280-0ubuntu1 Tags: kinetic wayland-session Uname: Linux 5.19.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2022 dmi.bios.release: 1.5 dmi.bios.vendor: LENOVO dmi.bios.version: N3MET08W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnLENOVO:bvrN3MET08W(1.05):bd09/13/2022:br1.5:efr1.3:svnLENOVO:pn21AHCTO1WW:pvrThinkPadT14Gen3:rvnLENOVO:rn21AHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21AH_BU_Think_FM_ThinkPadT14Gen3: dmi.product.family: ThinkPad T14 Gen 3 dmi.product.name: 21AHCTO1WW dmi.product.sku: LENOVO_MT_21AH_BU_Think_FM_ThinkPad T14 Gen 3 dmi.product.version: ThinkPad T14 Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1990052/+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 1970069] Re: Annoying boot messages interfering with splash screen
If it's a SAUCE only patch, I think it should be proposed here: https://lists.ubuntu.com/mailman/listinfo/kernel-team -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+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 2036737] Re: Enable dynamic boost control in ccp kernel driver
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036737 Title: Enable dynamic boost control in ccp kernel driver Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Triaged Bug description: [Impact] We need to backport dynamic boost control into OEM-6.5 kernel. This request is to backport the ccp changes. Here are the commits necessary to backport to OEM-6.5 kernel from kernel 6.6: b58276372182 crypto: ccp - Rename macro for security attributes 2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost control d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost control e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters Here are the commits necessary to backport to OEM-6.5 kernel from kernel 6.7: 53f7f779f45c crypto: ccp - Get a free page to use while fetching initial nonce [Test case] WIP [Regression potential] WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036737/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
** Description changed: - Some OEM platforms swap DP connections on the Rembrandt-R, which causes - improper eDP behavior. AMD experimented with reproducing at CRB level to - come out with a solution + [Impact] + Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle + + AMD has fixed these issues, but it requires both a kernel patch and an + updated DMCUB microcode. + + [Test Plan] + Validate brightness control works. + Validate that PSR works. + Validate that eDP works after suspend/resume. + Validate that external display works. + + Run above test plan on Rembrandt or Rembrandt-R system with swapped DP + as well as one without swapped DP. + + [Where problems can occur] + The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. + + [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 -- 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/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) 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/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: New Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: New Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. AMD experimented with reproducing at CRB level to come out with a solution - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+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 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Is this going to happen for noble? It should just be kernel config changes at this point. ** Changed in: linux (Ubuntu Mantic) 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/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in linux source package in Mantic: Won't Fix Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer [ Test Plan ] * Ensure that systems currently relying on fbdev (and therefore only allowing Xorg logins) such as some virtual machine types, boot with working Wayland support. [ Where Problems could occur ] * When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen (bug 2039757). * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Since the PPA failed would you be able to manually build 6.5.13 to see
if it's fixed there?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2042713] Re: Pale Green blank screen after login
Boot a bad kernel, reboot the system, boot a good kernel. >From the good kernel: journalctl -k -b0 > good_kernel.txt journalctl -k -b-1 > bad_kernel.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042713 Title: Pale Green blank screen after login Status in linux package in Ubuntu: Incomplete Bug description: Since linux Kernel 5.15.0-86, when I only get a pale green blank screen after login Linux Mint 21.2 Victoria / Cinnamon so I got to use 5.15.0-84. N.B. I'm using a Graphic AMD processor with unconventional screens resolutions (1280x1025 (5/4) & 1360x768 (16:9)) inxi : CPU: dual core AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G (-MT MCP-) speed/min/max: 3594/1400/3500 MHz Kernel: 5.15.0-84-generic x86_64 Up: 12h 9m Mem: 1946.1/15413.6 MiB (12.6%) Storage: 7.04 TiB (38.5% used) Procs: 256 Shell: Bash inxi: 3.3.13 inxi -S : System: Host: linuxmint Kernel: 5.15.0-84-generic x86_64 bits: 64 Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042713/+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 2048735] Re: Disable keyboard wakeup for Framework 13
It's a pretty complicated backport to 6.1. there is a directory rename, missing quirks that this builds on. Considering 6.1 OEM will transition to 6.5 OEM eventually it might be better to only target to 6.5 OEM. They patches were nominated to 6.6.y already, but 6.5.y is EOL upstream so it's up to kernel team to manually do backport instead of cherry pick from stable tree. -- 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/2048735 Title: Disable keyboard wakeup for Framework 13 Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Framework 13" AMD version has an unexpected behavior that EC triggers a keyboard wakeup event every time the system exits s0i3. This EC keyboard wakeup event is to workaround a different bug. Because of this, the following series is sent to mailing list to disable wakeup from keyboard when on latest BIOS for Framework 13 AMD. https://lore.kernel.org/platform-driver-x86/20231212045006.97581-1-mario.limoncie...@amd.com/T/#mca26ce4d4358b188fc61e8b32c27d62410780c5a 85980669a863 platform/x86/amd/pmc: Move platform defines to header 2d53c0ab61e6 platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne b614a4bd73ef platform/x86/amd/pmc: Move keyboard wakeup disablement detection to pmc-quirks a55bdad5dfd1 platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048735/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
** Also affects: linux-firmware (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Mantic: New Status in linux-firmware source package in Noble: New Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2046504] Re: Fix AMDGPU display on lower resolution modes
The patches for this issue are in the original bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042867 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046504 Title: Fix AMDGPU display on lower resolution modes Status in HWE Next: In Progress Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Bug description: [Impact] AMD GPU display is blank when set lower resolution than native mode on eDP. [Fix] On eDP the invalid modes are set, call mode set for valid modes instead. [Test] Tested on hardware, all the modes shown in gnome menu can be set OK. [Where problems could occur] It may break AMD display. This issue is not reproduced on v6.2- kernel versions, so SRU for oem-6.5 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2046504/+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 2045573] Re: AMDGPU: cp queue preemption timeout
*** This bug is a duplicate of bug 2047389 *** https://bugs.launchpad.net/bugs/2047389 ** This bug has been marked a duplicate of bug 2047389 Fix AMDGPU crash on 6.5 kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: New Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached X-HWE-Bug: Bug #2047389 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
OK thanks for clarifying. Can you please still try latest 6.5.13 and
6.6.6 and see if it happens in either of those?
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2039570] Re: [amdgpu] Fullscreen in any Wayland / Xwayland window shows a black screen (no screen detected)
Is this happening possibly when there is a resolution change for the
eDP? If so, can you please try the latest linux-6.5.y kernel:
https://kernel.ubuntu.com/mainline/v6.5.13/
--
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/2039570
Title:
[amdgpu] Fullscreen in any Wayland / Xwayland window shows a black
screen (no screen detected)
Status in Linux:
New
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
When I go into "fullscreen" watching a video while browsing in Firefox
or when playing a game through Steam (fullscreen mode), the screen
goes black.
The workaround I have discovered to get back is to enter the gdm from
"Ctrl + alt + F1" and then return to the session you were in
(normally, "Ctrl + alt + F2).
Edit: It happens when I connect a second monitor and use it as the
primary display while the laptop screen is disabled.
MSI laptop.
CPU: AMD Ryzen 7 Series 4000
GPU: AMD Radeon RX 5600m
RAM: 16GB
NVM: 1TB.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: noctis 2095 F wireplumber
/dev/snd/controlC0: noctis 2095 F wireplumber
/dev/snd/seq:noctis 2090 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 15:00:55 2023
InstallationDate: Installed on 2023-10-13 (4 days ago)
InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=es_ES.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB:
0 amdgpudrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic
root=UUID=fb325c2c-11c5-43e3-aceb-e921d5a7b323 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2020
dmi.bios.release: 1.1
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E17EKAMS.101
dmi.board.asset.tag: Default string
dmi.board.name: MS-17EK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrE17EKAMS.101:bd10/26/2020:br1.1:svnMicro-StarInternationalCo.,Ltd.:pnAlpha17A4DEK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17EK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku17EK.1:
dmi.product.family: Al
dmi.product.name: Alpha 17 A4DEK
dmi.product.sku: 17EK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039570/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f6
** Changed in: linux (Ubuntu)
Status: Won't Fix => Confirmed
** Changed in: linux (Ubuntu Jammy)
Status: Won't Fix => Confirmed
** Changed in: linux (Ubuntu Lunar)
Status: Won't Fix => 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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Confirmed
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
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.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2045573] Re: AMDGPU: cp queue preemption timeout
Here's the fix commit ID to backport to fix this issue. https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f6 -- 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/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: New Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2045573] Re: AMDGPU: cp queue preemption timeout
that patch I linked will go into the next 6.7-fixes PR. I suggest backporting it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: New Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2045573] Re: AMDGPU: cp queue preemption timeout
This will be fixed by this patch: https://lore.kernel.org/amd- gfx/20231201005751.4194154-1-jiadong@amd.com/ Until Canonical pulls it in for now you can use amdgpu.mcbp=0 on kernel command line to avoid it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045573 Title: AMDGPU: cp queue preemption timeout Status in linux package in Ubuntu: New Bug description: Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic Under load, GPU crashed resulting in a weird behavior. Screen froze, blinked a few times and the laptop suspended. After wakeup a normal login screen showed up but after logging in, it crashed to black screen with a message: " cp queue preemption timeout". Eventually I was able to log in to a clean session. Log attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573/+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 2045382] Re: AMD Lexa PRO graphic card can't work
That was already CC to stable, so I suggest checking the latest 5.15.y. If that's still not working, you probably need https://github.com/torvalds/linux/commit/2757a848cb0f184850d3e0a33b4a69e8014fdc5d backported too. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2045382 Title: AMD Lexa PRO graphic card can't work Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work normally by using the onboard graphic card. After checking, AMD graphic card is broken after upgrading to 5.15.0-89-generic, it still have same issue in "5.15.0-91-generic" kernel version, but everything is good in the "5.15.0-88-generic" kernel version. [Information] Problematic DUT CID: 202101-28622 Platform name: Caribou Launchpad Tag: fossa-cubone-rkl Project name: Optiplex 5090 Used GM image: dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 1 14:39:55 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-hwe-5.15 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.15/+bug/2045382/+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 2045382] Re: AMD Lexa PRO graphic card can't work
It's probably a duplicate of the same patches missing for bug 2036742. https://github.com/torvalds/linux/commit/64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2045382 Title: AMD Lexa PRO graphic card can't work Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work normally by using the onboard graphic card. After checking, AMD graphic card is broken after upgrading to 5.15.0-89-generic, it still have same issue in "5.15.0-91-generic" kernel version, but everything is good in the "5.15.0-88-generic" kernel version. [Information] Problematic DUT CID: 202101-28622 Platform name: Caribou Launchpad Tag: fossa-cubone-rkl Project name: Optiplex 5090 Used GM image: dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 1 14:39:55 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-hwe-5.15 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.15/+bug/2045382/+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 2045382] Re: AMD Lexa PRO graphic card can't work
try amdgpu.aspm=0. If this helps it's because of missing stable backport patches. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2045382 Title: AMD Lexa PRO graphic card can't work Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: [Summary] When I racked the one dell device, and do the trail run, I found that the checkbox process is stuck when it got the graphic information. I want to debug with the monitor, plug the DP cable to AMD card. After doing the power cycle, it entered to the BIOS, observe through the screen that the kernel has been started, but it immediately turned into a black screen. Fortunately, it can ssh-able, it can work normally by using the onboard graphic card. After checking, AMD graphic card is broken after upgrading to 5.15.0-89-generic, it still have same issue in "5.15.0-91-generic" kernel version, but everything is good in the "5.15.0-88-generic" kernel version. [Information] Problematic DUT CID: 202101-28622 Platform name: Caribou Launchpad Tag: fossa-cubone-rkl Project name: Optiplex 5090 Used GM image: dell-bto-focal-fossa-release-X120-20210625-7_fossa-cubone-rkl_A02.iso GPU: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-91-generic 5.15.0-91.101~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-91.101~20.04.1-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 1 14:39:55 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-release+X120 InstallationDate: Installed on 2023-11-30 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-hwe-5.15 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.15/+bug/2045382/+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 2043264] Re: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE)
Can you please try to reproduce using a mainline upstream build? https://kernel.ubuntu.com/mainline/v6.7-rc2/ If you can reproduce please share a new kernel log from a boot it occurs. -- 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/2043264 Title: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: --- en Always, almost every time I turn on my notebook, my LG external monitor keeps blinking and it takes a while to actually connect to the notebook and the external monitor screen to turn on. For the external monitor to work I change the video settings using Ctrl + P and turn the monitor off/on several times. In Kubuntu it is recognized but when it blinks the system thinks the monitor is off. I'm using Kubuntu 23.04, I've used other distributions on the same hardware and this problem hasn't happened. I believe it's something with KDE. --- pt-br Sempre, quase toda vez que ligo meu notebook, meu monitor externo LG fica piscando e demora para realmente conectar ao notebook e a tela do monitor externo ligar. Para o monitor externo funcionar eu mudo as configurações de vídeo usando Ctrl + P e desligo/ligo o monitor várias vezes. No Kubuntu ele é reconhecido mas quando fica piscando o sistema acha que o monitor está desligado. Estou usando o Kubuntu 23.04, já usei outras distribuições no mesmo hardware e esse problema não aconteceu. Eu acredito que seja algo com o KDE. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sat Nov 11 07:52:24 2023 DistUpgraded: 2023-11-02 07:28:00,578 DEBUG /openCache(), new cache size 78921 DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:3804] InstallationDate: Installed on 2022-10-23 (383 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 81V7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=d72b8a6b-953f-4b38-8b0a-d1e9b6899ad2 ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-11-02 (9 days ago) dmi.bios.date: 05/19/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: BUCN25WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15API dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrBUCN25WW:bd05/19/2020:br1.25:efr1.25:svnLENOVO:pn81V7:pvrLenovoIdeaPadS145-15API:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15API:skuLENOVO_MT_81V7_BU_idea_FM_IdeaPadS145-15API: dmi.product.family: IdeaPad S145-15API dmi.product.name: 81V7 dmi.product.sku: LENOVO_MT_81V7_BU_idea_FM_IdeaPad S145-15API dmi.product.version: Lenovo IdeaPad S145-15API dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3.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-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043264/+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 2043905] Re: VT6307 IEEE1394 card causes reboot loop
** Summary changed: - Mantic reboot loop before splash screen is displayed + VT6307 IEEE1394 card causes reboot loop -- 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/2043905 Title: VT6307 IEEE1394 card causes reboot loop Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+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 2043905] Re: Mantic reboot loop before splash screen is displayed
** Bug watch added: Linux Kernel Bug Tracker #217993 https://bugzilla.kernel.org/show_bug.cgi?id=217993 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=217993 Importance: Unknown Status: Unknown -- 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/2043905 Title: Mantic reboot loop before splash screen is displayed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: used the live USB for Kubuntu and UbuntuStudio 23.10 as well as upgraded to Mantic 6.5.0-10-generic from a Lunar 6.2.0-36 that works... all of the 6.5.0 64 bit kernel versions do a reboot loop prior to the splash screen display. Processor is an AMD Ryzen 5600X, MSI MPG B550 GAMING PLUS Motherboard with 64 gig 3200 ddr4 ram. AMD Radeon RX6600 graphics... latest BIOS firmware is installed, "fwupdmrg refresh --force && fwupdmrg update" in root terminal reports no available updates. in the advanced options of grub I can boot into mantic with the lunar 6.2.0-36 kernel. Cell phone video capture of the bad boot included... Further testing found that a Mantic beta July 3rd build will boot (6.3 kernel) booting to the current live Kubuntu USB with the 6.5.0-9 kernel and removing hardware 1 piece at a time then replacing if the loop occurred found that as soon as a VT6307 PCIe card is removed the 6.5.0-9 and 6.5.0-10 kernels will boot properly. as soon as the card is reinstalled the panic reboot loop starts up again... If there was a log generated from the loop I have been unable to find one in the /var/log directory... I have been unable to get kdump to work... To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2043905/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt upgrade
# sudo reboot
If they don't, you can remove the PPA using ppa-purge like this:
# sudo ppa-purge ppa:superm1/gitlab2971
# sudo reboot
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Unknown
Status in linux package in Ubuntu:
Won't Fix
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Won't Fix
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
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.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: mesa (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Lunar)
Status: New => Won't Fix
** Also affects: mesa via
https://gitlab.freedesktop.org/drm/amd/-/issues/2971
Importance: Unknown
Status: Unknown
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Unknown
Status in linux package in Ubuntu:
Won't Fix
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Won't Fix
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Won't Fix
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
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.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
I don't think we should close it, if you reproduce a hang in Ubuntu it should
be fixed in Ubuntu.
The patch should come in mesa. I already know what patch should fix it in mesa
(it's mentioned in https://gitlab.freedesktop.org/drm/amd/-/issues/2971)
If I build you a PPA to test, can you see if it helps without the
parameter?
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in linux package in Ubuntu:
New
Status in mesa package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
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.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043640/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
Try amdgpu.mcbp=0 on your kernel command line.
--
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/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in linux package in Ubuntu:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
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.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043640/+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 2036737] Re: Enable dynamic boost control in ccp kernel driver
** Description changed:
[Impact]
We need to backport dynamic boost control into OEM-6.5 kernel. This
request is to backport the ccp changes.
Here are the commits necessary to backport to OEM-6.5 kernel from kernel
6.6:
b58276372182 crypto: ccp - Rename macro for security attributes
2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost
control
d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost
control
e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters
+ Here are the commits necessary to backport to OEM-6.5 kernel from kernel
+ 6.7:
+
+ 53f7f779f45c ("crypto: ccp - Get a free page to use while fetching
+ initial nonce")
+
[Test case]
WIP
[Regression potential]
WIP
** Description changed:
[Impact]
We need to backport dynamic boost control into OEM-6.5 kernel. This
request is to backport the ccp changes.
Here are the commits necessary to backport to OEM-6.5 kernel from kernel
6.6:
b58276372182 crypto: ccp - Rename macro for security attributes
2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost
control
d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost
control
e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters
Here are the commits necessary to backport to OEM-6.5 kernel from kernel
6.7:
- 53f7f779f45c ("crypto: ccp - Get a free page to use while fetching
- initial nonce")
+ 53f7f779f45c crypto: ccp - Get a free page to use while fetching initial
+ nonce
[Test case]
WIP
[Regression potential]
WIP
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2036737
Title:
Enable dynamic boost control in ccp kernel driver
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.5 source package in Jammy:
New
Bug description:
[Impact]
We need to backport dynamic boost control into OEM-6.5 kernel. This
request is to backport the ccp changes.
Here are the commits necessary to backport to OEM-6.5 kernel from
kernel 6.6:
b58276372182 crypto: ccp - Rename macro for security attributes
2e424c33d8e7 crypto: ccp - Add support for displaying PSP firmware versions
e938b08ad8cd crypto: ccp - Add bootloader and TEE version offsets
b8440d55f7d4 crypto: ccp - move setting PSP master to earlier in the init
c04cf9e14f10 crypto: ccp - Add support for fetching a nonce for dynamic boost
control
d9408716d212 crypto: ccp - Add support for setting user ID for dynamic boost
control
e2cfe05e9277 crypto: ccp - Add support for getting and setting DBC parameters
Here are the commits necessary to backport to OEM-6.5 kernel from
kernel 6.7:
53f7f779f45c crypto: ccp - Get a free page to use while fetching
initial nonce
[Test case]
WIP
[Regression potential]
WIP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2036737/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
This should be a different issue than the mutter issue; please open it up separately for investigation. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2043515] Re: Black screen on 6.5
*** This bug is a duplicate of bug 2042867 ***
https://bugs.launchpad.net/bugs/2042867
** This bug has been marked a duplicate of bug 2042867
Changing display resolution leads into black screen
--
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/2043515
Title:
Black screen on 6.5
Status in linux package in Ubuntu:
New
Bug description:
Hello, the screen stays black under many resolutions on Ryzen on
kernel 6.5. It worked well up until the update (from 6.2). It seems to
be a known regression already fixed in upstream. Could you also apply
the patch https://www.spinics.net/lists/stable/msg679132.html? Thank
you.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Nov 14 22:48:59 2023
InstallationDate: Installed on 2023-08-07 (99 days ago)
InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (12 days ago)
dmi.bios.date: 08/08/2023
dmi.bios.release: 1.35
dmi.bios.vendor: LENOVO
dmi.bios.version: R22ET65W (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CNS17C00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 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.27
dmi.modalias:
dmi:bvnLENOVO:bvrR22ET65W(1.35):bd08/08/2023:br1.35:efr1.27:svnLENOVO:pn21CNS17C00:pvrThinkPadX13Gen3:rvnLENOVO:rn21CNS17C00:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CN_BU_Think_FM_ThinkPadX13Gen3:
dmi.product.family: ThinkPad X13 Gen 3
dmi.product.name: 21CNS17C00
dmi.product.sku: LENOVO_MT_21CN_BU_Think_FM_ThinkPad X13 Gen 3
dmi.product.version: ThinkPad X13 Gen 3
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043515/+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 2043493] Re: Logitech StreamCam driver broken with update
*** This bug is a duplicate of bug 2043197 *** https://bugs.launchpad.net/bugs/2043197 ** This bug has been marked a duplicate of bug 2043197 USB bus error after upgrading to proposed kernel on lunar and 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/2043493 Title: Logitech StreamCam driver broken with update Status in linux package in Ubuntu: New Bug description: My Logitech StreamCam works with linux-image-5.15.0-88. With linux-image-5.15.0-90 it does not work and instead I get the syslog messages when plugging in such as that below (a longer extract is attached). Nov 14 16:02:12 mylaptop kernel: [ 482.608545] pci_bus :04: Allocating resources Nov 14 16:02:12 mylaptop kernel: [ 482.608572] pcieport :04:02.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 39] add_size 20 add_align 10 Nov 14 16:02:12 mylaptop kernel: [ 482.608584] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608586] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608590] pcieport :04:02.0: BAR 15: no space for [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608591] pcieport :04:02.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.608594] pcieport :00:1c.4: PCI bridge to [bus 03-6d] Nov 14 16:02:12 mylaptop kernel: [ 482.608597] pcieport :00:1c.4: bridge window [io 0x2000-0x5fff] Nov 14 16:02:12 mylaptop kernel: [ 482.608601] pcieport :00:1c.4: bridge window [mem 0xac00-0xda0f] Nov 14 16:02:12 mylaptop kernel: [ 482.608604] pcieport :00:1c.4: bridge window [mem 0x6000-0xa9ff 64bit pref] Nov 14 16:02:12 mylaptop kernel: [ 482.948297] usb 4-2: new SuperSpeed USB device number 2 using xhci_hcd Nov 14 16:02:12 mylaptop kernel: [ 482.972432] usb 4-2: device descriptor read/8, error -71 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2917 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:57:47 2023 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (1900 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043493/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Open a new bug at kernel bugzilla and attach kernel log, acpidump and dmidecode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy
Btw - That commit is in 5.15.132. -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar and jammy Status in linux package in Ubuntu: Confirmed Bug description: [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 600 G6 dmi.product.sku: 123456#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043197/+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 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy
Should be fixed with https://github.com/torvalds/linux/commit/59cf445754566984fd55af19ba7146c76e6627bc then I would expect. -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar and jammy Status in linux package in Ubuntu: Confirmed Bug description: [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 600 G6 dmi.product.sku: 123456#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043197/+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 2042075] Re: Black screen at login after updating to this kernel
Each page you'll need the following binaries: Linux image unsigned Linux modules Linux modules extra Download those 3 and install them with dpkg. Note: none of these are signed for secure boot. If you have that enabled, disable it for this experiment. -- 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/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+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 2042075] Re: Black screen at login after updating to this kernel
OK thanks. Nothing was obvious in the log differences. We need to narrow down intermediate kernel releases to identify what's changed to cause this regression. Can you please test these binaries from those. Capture the journals for each and note if they worked or didn't. Hopefully we'll get closer. https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/26313281 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa2/+build/26398561 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/26405786 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa2/+build/26504338 https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa2/+build/26504338 -- 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/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+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 2042867] Re: Changing display resolution leads into black screen
This issue is fixed in 6.6-rc3: 2de19022c5d7 ("drm/amd/display: fix the
ability to use lower resolution modes on eDP")
It's backported to stable 6.5.6 as 79aec38ba852 ("drm/amd/display: fix
the ability to use lower resolution modes on eDP").
Canonical needs to pull the fix into their kernel.
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2693
https://gitlab.freedesktop.org/drm/amd/-/issues/2693
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2693
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (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/2042867
Title:
Changing display resolution leads into black screen
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Since updating into 23.10, when I change my build-in display from
2880x1800 (16:10) at 90Hz to any other resolution, it turns the screen
black and unable to use.
The only resolution that works is the predefined one.
This bug wasn't present on the previous release, 23.04.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-10-generic 6.5.0-10.10
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 6 19:37:48 2023
InstallationDate: Installed on 2023-05-05 (185 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-03 (3 days ago)
dmi.bios.date: 04/18/2022
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UM5401QAB_UM5401QA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UM5401QAB
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:bvnAmericanMegatrendsInternational,LLC.:bvrUM5401QAB_UM5401QA.302:bd04/18/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnZenbookUM5401QAB_UM5401QA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM5401QAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Zenbook
dmi.product.name: Zenbook UM5401QAB_UM5401QA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2042867/+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 2042713] Re: Pale Green blank screen after login
Please add kernel log from both your old kernel and new kernel. ** 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/2042713 Title: Pale Green blank screen after login Status in linux package in Ubuntu: Incomplete Bug description: Since linux Kernel 5.15.0-86, when I only get a pale green blank screen after login Linux Mint 21.2 Victoria / Cinnamon so I got to use 5.15.0-84. N.B. I'm using a Graphic AMD processor with unconventional screens resolutions (1280x1025 (5/4) & 1360x768 (16:9)) inxi : CPU: dual core AMD A6-9500 RADEON R5 8 COMPUTE CORES 2C+6G (-MT MCP-) speed/min/max: 3594/1400/3500 MHz Kernel: 5.15.0-84-generic x86_64 Up: 12h 9m Mem: 1946.1/15413.6 MiB (12.6%) Storage: 7.04 TiB (38.5% used) Procs: 256 Shell: Bash inxi: 3.3.13 inxi -S : System: Host: linuxmint Kernel: 5.15.0-84-generic x86_64 bits: 64 Desktop: Cinnamon 5.8.4 Distro: Linux Mint 21.2 Victoria To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042713/+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 2042075] Re: Black screen at login after updating to this kernel
Your "good" journal is with nomodeset. Can I see the log from a good journal without adding a module parameter? Like an older kernel that worked? -- 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/2042075 Title: Black screen at login after updating to this kernel Status in linux package in Ubuntu: Incomplete Bug description: Dell Inspiron AMD A10 Laptop Linux Mint Mate O/S After updating the kernel I restarted the laptop. After entering my password and logging in the screen goes black with occasional flashes of, I guess i'd call it static. The same thing happened with the previous kernel I installed, ending .87, when I was running Zorin OS. After un-installing the system returns to opening as usual. System: Kernel: 5.15.0-76-generic x86_64 bits (This is the kernel that is working correctly): 64 compiler: gcc v: 11.3.0 Desktop: MATE 1.26.0 wm: marco dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy Machine: Type: Portable System: Dell product: Inspiron v: A12 serial: Chassis: type: 8 v: A12 serial: Mobo: Dell model: 0CX84K v: A00 serial: UEFI: Dell v: A12 date: 08/30/2016 CPU: Info: quad core model: AMD A10-8700P Radeon R6 10 Compute Cores 4C+6G bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB Speed (MHz): avg: 2776 high: 3053 min/max: 1300/1800 boost: enabled cores: 1: 2673 2: 2680 3: 3053 4: 2700 bogomips: 14374 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Dell driver: amdgpu v: kernel ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:01.0 chip-ID: 1002:9874 Device-2: AMD Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 M430 Radeon 520 Mobile] vendor: Dell driver: radeon v: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 03:00.0 chip-ID: 1002:6660 Device-3: Microdia Integrated Webcam HD type: USB driver: uvcvideo bus-ID: 2-4:3 chip-ID: 0c45:6712 Display: x11 server: X.Org v: 1.21.1.4 compositor: marco v: 1.26.0 driver: X: loaded: ati,radeon unloaded: amdgpu,fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP res: 1366x768 dpi: 112 diag: 354mm (13.9") OpenGL: renderer: AMD Radeon R6 Graphics (carrizo LLVM 15.0.7 DRM 3.42 5.15.0-76-generic) v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 direct render: Yes I don't have a lot of experience with reporting errors so I hope this helps! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
** Changed in: linux (Ubuntu Noble) Status: New => Triaged ** Changed in: linux (Ubuntu Mantic) Status: New => Triaged ** Changed in: linux (Ubuntu Lunar) Status: New => Triaged ** Changed in: linux (Ubuntu Jammy) Status: New => Triaged ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Triaged Status in linux-oem-6.5 source package in Jammy: Triaged Status in linux source package in Lunar: Triaged Status in linux-oem-6.5 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Triaged Status in linux-oem-6.5 source package in Noble: Invalid Bug description: My screen suddenly turned completely white, then only the bottom half was white, but I can still operate the application window. When moving the application window, the bottom half of the screen turns the Ubuntu theme color. Only lock and unlock the screen or turn off the screen can fix the situation. There are some photo about the exception attached. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1006.6-oem 6.5.3 Uname: Linux 6.5.0-1006-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 31 12:26:24 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1006-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2042054/+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
