[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
Please reproduce the problem (boot to black screen). Then reboot in a way that you can use the computer and run this without rebooting again: sudo journalctl -k -b -1 > /tmp/kernel.log Then attach /tmp/kernel.log to your bug report. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064595] [NEW] S2idle regression
Public bug reported: [Impact] On some OEM platforms observed bad suspend occurs on lid close and power LED stays on without normal sleep behavior at that time. Needs to call GFXOFF to the right state during the suspend stage. https://github.com/torvalds/linux/commit/ca299b4512d4b4f516732a48ce9aa19d91f4473e Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3132 Fixes: ab4750332dbe [Test case] test that s2idle works after installing the update [Regression potential] minimal ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: Fix Committed ** Affects: linux-oem-6.8 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: Fix Committed ** Also affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oem-6.8 (Ubuntu) Status: New => Invalid ** Description changed: [Impact] On some OEM platforms observed bad suspend occurs on lid close and power LED stays on without normal sleep behavior at that time. Needs to call - GFXOFF to the right state during the suspend stage, please backport to - both oem-6.5 & oem-6.8. + GFXOFF to the right state during the suspend stage. https://github.com/torvalds/linux/commit/ca299b4512d4b4f516732a48ce9aa19d91f4473e Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3132 Fixes: ab4750332dbe [Test case] test that s2idle works after installing the update [Regression potential] minimal ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.8 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2064595 Title: S2idle regression Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux-oem-6.8 source package in Jammy: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Status in linux-oem-6.8 source package in Noble: Fix Committed Bug description: [Impact] On some OEM platforms observed bad suspend occurs on lid close and power LED stays on without normal sleep behavior at that time. Needs to call GFXOFF to the right state during the suspend stage. https://github.com/torvalds/linux/commit/ca299b4512d4b4f516732a48ce9aa19d91f4473e Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/3132 Fixes: ab4750332dbe [Test case] test that s2idle works after installing the update [Regression potential] minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056716] Re: To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Noble) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056716 Title: To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Committed Bug description: [SRU Justification] [Impact] power-profiles-daemon >= 2.0 now utilizes AMD GPU panel_power_savings sysfs entry to set desired panel power saving level. Related kernel fixes are to be released in v6.9. [Fix] Two linux-next committed fixes are required. The first one introduces panel_power_savings sysfs entry itself, and the second one extends abmlevel sysfs entry to allow an auto mode. [Test Case] 1. Check existence of panel_power_savings sysfs entry: $ cat /sys/class/drm/card0-eDP-1/amdgpu/panel_power_savings -1 2. Remove power cable and switch between power profiles from Power Management settings. The content of above panel_power_savings sysfs entry should be updated correspondingly. [Where problems could occur] While the abmlevel entry now has a different default value that allows automatic power management, the behavior may differ from users' expectation. [Other Info] power-profiles-daemon >= 0.20 is only available on Noble or later at this moment, so only Noble/Unstable will be nominated for fix. == original bug report == Required kernel fixes (in linux-next): * https://gitlab.freedesktop.org/agd5f/linux/-/commit/63d0b87213a0ba241b3fcfba3fe7b0aed0cd1cc5 * https://gitlab.freedesktop.org/agd5f/linux/-/commit/040fdcde288a2830edc31dd507963d6aadf990d2 See also power-profiles-daemon merge request https://gitlab.freedesktop.org/upower/power-profiles- daemon/-/merge_requests/137 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2063893] Re: after last OS uptate system will not boot normaly.
Is there a resolve for this issue as yet? If so please let me know, it's a pain at restarts and i'm fearful of doing more updates. On Wed, May 1, 2024 at 5:35 AM Brian Baugus wrote: > Sounds exactly the same as I am haveing. > > On Sat, Apr 27, 2024 at 11:45 AM Sni <2063...@bugs.launchpad.net> wrote: > >> Hello, I have the same or similar problem, after a dist-upgrade and >> subsequent reboot, my server ran into a kernel panic (sync init). I have >> the problem with the linux-6.5.0-34-generic kernel, the >> linux-6.5.0-28-generic and all previous ones work fine. >> >> Since the kernel does not seem to mount the root volume, there are no >> logs. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/2063893 >> >> Title: >> after last OS uptate system will not boot normaly. >> >> Status in linux package in Ubuntu: >> Confirmed >> >> Bug description: >> will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot >> into Linux 6.5.0-28 generic if forced. I have never had an issue >> before with OS updates. >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063893/+subscriptions >> >> -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2063893 Title: after last OS uptate system will not boot normaly. Status in linux package in Ubuntu: Confirmed Bug description: will not boot to, Ubuntu, with Linux 6.5.0-34 generic but will boot into Linux 6.5.0-28 generic if forced. I have never had an issue before with OS updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
This should be Fix Released for the development release, right? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: Fix Committed Bug description: [ Impact ] Impossible to build the package from source on Ubuntu 22.04, users will get this error: ``` int main(void) { void *a = (void*) _create; long long b = (long long) a; return (int) b; } Compiler stdout: Compiler stderr: Checking for function "memfd_create" : YES Configuring config.h using configuration ../lib/meson.build:155:4: ERROR: Function does not take positional arguments. dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned exit code 1 make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255 make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26' make: *** [debian/rules:39: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 ``` The problem comes from the bad call to meson function underscorify in lib/meson.build This problem has been fixed upstream: 963917a3565466832a3b2fc22e9285d34a0bf944 lib/meson.build: Fix underscorify call f.underscorify() is correct, f.underscorify(f) is an error that later meson versions don't like at all. The proposed fix for Ubuntu consists of backporting this patch. [ Test Plan ] Build the package from source on Ubuntu 22.04 The build command is : dpkg-buildpackage -us -uc -b Ubuntu release : Jammy 22.04 Meson version : 0.61.2 [ Where problems could occur ] The problem occurs only at build process [ Other Info ] This issue only happens at build and has been fixed upstream. It is safe to have it in SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
included via https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060531 ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-oem-6.8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 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: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: New 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 2055083] Re: Drop fips-checks script from trees
This bug is awaiting verification that the linux-azure/5.15.0-1064.73 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- 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/2055083 Title: Drop fips-checks script from trees Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS certs and justify why a commit was kept. For that, we have a fips-checks script that lives under debian/ in Focal, Jammy, Mantic and Noble. This script has been moved to `cranky`[1], so now there is no need to have this script in the kernel Git trees as well. [1] https://git.launchpad.net/~canonical-kernel/+git/kteam- tools/commit/?id=2ab9364d4b4c18bee7d835787d7dd11990103bca [Fix] Remove the fips-checks script and its calls. [Test Plan] Prepare a kernel and ensure that the `cranky close` step runs without any errors. [Where problems could occur] This only affects the preparation of FIPS kernels and not the kernel final binary. Moreover, I've prepared some FIPS kernels from the 2024.03.04 cycle relying on `cranky check-fips` to ensure that we have it working well on the cranky side too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055083] Re: Drop fips-checks script from trees
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2055083 Title: Drop fips-checks script from trees Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: [Impact] When producing a new version of some kernels, we need to check for changes that might affect FIPS certs and justify why a commit was kept. For that, we have a fips-checks script that lives under debian/ in Focal, Jammy, Mantic and Noble. This script has been moved to `cranky`[1], so now there is no need to have this script in the kernel Git trees as well. [1] https://git.launchpad.net/~canonical-kernel/+git/kteam- tools/commit/?id=2ab9364d4b4c18bee7d835787d7dd11990103bca [Fix] Remove the fips-checks script and its calls. [Test Plan] Prepare a kernel and ensure that the `cranky close` step runs without any errors. [Where problems could occur] This only affects the preparation of FIPS kernels and not the kernel final binary. Moreover, I've prepared some FIPS kernels from the 2024.03.04 cycle relying on `cranky check-fips` to ensure that we have it working well on the cranky side too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056227] Re: KVM: arm64: softlockups in stage2_apply_range
This bug is awaiting verification that the linux-azure/5.15.0-1064.73 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- 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/2056227 Title: KVM: arm64: softlockups in stage2_apply_range Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: [Impact] Tearing down kvm VMs on arm64 can cause softlockups to appear on console. When terminating VMs with > 100Gb of memory and 4k pages, the memory unmap times often exceed 20 seconds, which can trigger the softlockup detector. Portions of the unmap path also have interrupts disabled while tlb invalidation instructions run, which can further contribute to latency problems. My team has observed networking latency problems if the cpu where the teardown is occurring is also mapped to handle a NIC interrupt. Fortunately, a solution has been in place since Linux 6.1. A small pair of patches modify stage2_apply_range to operate on smaller memory ranges before performing a cond_resched. With these patches applied, softlockups are no longer observed when tearing down VMs with large amounts of memory. Although I also submitted the patches to 5.15 LTS (link to LTS submission in "Backport" section), I'd appreciate it if Ubuntu were willing to take this submission in parallel since the impact has left us unable to utilize arm64 for kvm until we can either migrate our hypervisors to hugepages, pick up this fix, or some combination of the two. [Backport] Backport the following fixes from linux 6.1: 3b5c082bbf KVM: arm64: Work out supported block level at compile time 5994bc9e05 KVM: arm64: Limit stage2_apply_range() batch size to largest block The fix is in 5994bc9e05 and 3b5c082bbf is a dependency that was submitted as part of the series. The original submission is here: https://lore.kernel.org/all/20221007234151.461779-1-oliver.up...@linux.dev/ I've also submitted the patches to 5.15 LTS here: https://lore.kernel.org/stable/cover.1709665227.git.k...@templeofstupid.com/ Both fixes cherry picked cleanly and there were no conflicts. [Test] Executed the test from 5994bc9e05 as well as my own run of kvm_page_table_test on a VM with 4k pages and a memory size > 100Gb. Without the patches, softlockups were observed in both tests. With the patches applied, the tests ran without incident. This was tested against both LTS 5.15.150 and linux-aws-5.15.0-1055. [Potential Regression] Regression potential is low. These patches have been present in Linux since 6.1 and appear to have needed no further maintenance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056418] Re: Fix headphone mic detection issue on ALC897
This bug is awaiting verification that the linux-azure/5.15.0-1064.73 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- 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/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux 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: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056373] Re: Problems with HVCS and hotplugging
This bug is awaiting verification that the linux-azure/5.15.0-1064.73 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- 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/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: SRU Justification: == [Impact] * HVCS (Hypervisor Virtual Console Server) is broken because the virtual terminal mkvterm fails, caused by pvmutil failing. * When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. * This leads to HVCS never having probe() called. * In addition, HVCS is missing patches/fixes, and is broken without them. [Fix] * Fix one and two is required for focal only, all other for focal and jammy: * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc "hvcs: Fix hvcs port reference counting" * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 "hvcs: Use dev_groups to manage hvcs device attributes" * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a "hvcs: Use driver groups to manage driver attributes" * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 "hvcs: Get reference to tty in remove" * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 "hvcs: Use vhangup in hotplug remove" * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f "hvcs: Synchronize hotplug remove with port free" [Test Plan] * The high level test plan is to run mkvterm with an id. * mkvterm will fail because /dev/hvcs* device nodes are missing. * Details see https://bugs.launchpad.net/bugs/2023243 for more information. Especially the script provided by IBM (see original bug description: `---Steps to Reproduce---`). * IBM will (stress) test the updated kernel(s) provided in -proposed. [Where problems could occur] * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c and are needed to fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. In case of issues here hotplugging with drmgr might break. * The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes). * The remaning 6 commits are needed for HVCS, that is essentially broken without them. Overall, issues they fix are race conditions, hotplug remove issues, as well as memory leaks. * Please notice that this is entirely ppc64el architecture-specifc. [Other Info] * All the commits listed above are included in mantic and noble. Hence these are set to Invalid. * Meanwhile these
[Kernel-packages] [Bug 2056418] Re: Fix headphone mic detection issue on ALC897
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2056418 Title: Fix headphone mic detection issue on ALC897 Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux 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: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Headphone mic is lost after resume from S3 or reboot with plugin. [Fix] Restore the headphone mic detect logic for ALC897 after lost power. [Test] Tested on hardware, the headphone mic appears as plugin after boot or resume from S3, and works fine. [Where problems could occur] It may break ALC897 sound input. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056418/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049733] Re: Dynamically determine acpi_handle_list size
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2049733 Title: Dynamically determine acpi_handle_list size Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: [Impact] ACPI handle list will be dynamic allocated without default fixed size. [Fix] Currently the ACPI_MAX_HANDLES is defined fix to 10, and it is not enough for some platforms that called ACPI _PSL method to get passive cooling device objects. then will get the error message "Invalid passive threshold", this patch change the fixed size with the dynamic handle list size which fixes the handle reference error. [Test Case] check the dmesg to see if there is the error message "Invalid passive threshold" [Where problems could occur] Only change the fixed size with the dynamic handle list size. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058808] Re: iwlwifi disconnect and crash - intel wifi7
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2058808 Title: iwlwifi disconnect and crash - intel wifi7 Status in HWE Next: In Progress Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress 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: Fix Released Status in linux source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: iwlwifi disconnecting and crashing when I using Wifi 2.4GHz. [ cut here ] Invalid rxb from HW 0 WARNING: CPU: 14 PID: 896 at drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1489 iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Modules linked in: ccm vboxdrv(OE) rfcomm cmac algif_hash algif_skcipher af_alg bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic input_leds joydev ecc intel_rapl_msr intel_rapl_common intel_uncore_frequency intel_uncore_frequency_common nft_limit x86_pkg_temp_thermal intel_powerclamp coretemp iwlmvm kvm_intel xt_tcpudp xt_LOG nf_log_syslog kvm mac80211 xt_limit xt_conntrack nf_conntrack libarc4 nf_defrag_ipv6 irqbypass nf_defrag_ipv4 crct10dif_pclmul crc32_pclmul nft_compat polyval_clmulni polyval_generic nf_tables ghash_clmulni_intel libcrc32c sha256_ssse3 iwlwifi sha1_ssse3 sunrpc rapl nvidia_uvm(PO) nfnetlink binfmt_misc n xhci_pci xhci_pci_renesas nvme_common video wmi mac_hid CPU: 14 PID: 896 Comm: irq/160-iwlwifi Tainted: PW OE 6.5.0-26-generic #26~22.04.1-Ubuntu Hardware name: ASRock Z790 Nova WiFi/Z790 Nova WiFi, BIOS 3.09 12/26/2023 RIP: 0010:iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] Code: e9 8b 43 34 83 43 30 08 83 e8 08 89 43 34 e9 70 fe ff ff 44 89 f0 89 d6 45 89 e6 41 89 c4 48 c7 c7 a8 cb 53 c4 e8 42 e4 62 e8 <0f> 0b 4c 89 ff e8 e8 3b ff ff 8b 55 d4 85 d2 0f 95 c0 41 21 c6 e9 RSP: 0018:b91d803e0e18 EFLAGS: 00010246 RAX: RBX: 956747353c30 RCX: RDX: RSI: RDI: RBP: b91d803e0e78 R08: R09: R10: R11: R12: 1007 R13: 0015 R14: R15: 956746a30028 FS: () GS:95768f38() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 02659c472000 CR3: 000112e8e000 CR4: 00752ee0 PKRU: 5554 Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? iwl_pcie_rx_handle+0x3ce/0x640 [iwlwifi] ? free_unref_page+0x30/0x180 iwl_pcie_napi_poll_msix+0x32/0x100 [iwlwifi] ? skb_free_head+0xa8/0xd0 __napi_poll+0x30/0x1f0 net_rx_action+0x181/0x2e0 ? __irq_wake_thread+0x42/0x50 __do_softirq+0xd9/0x349 ? __pfx_irq_thread_fn+0x10/0x10 do_softirq.part.0+0x41/0x80 __local_bh_enable_ip+0x72/0x80 iwl_pcie_irq_rx_msix_handler+0xd7/0x1a0 [iwlwifi] irq_thread_fn+0x21/0x70 irq_thread+0xf8/0x1c0 ? __pfx_irq_thread_dtor+0x10/0x10 ? __pfx_irq_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 ---[ end trace ]--- iwlwifi :05:00.0: Microcode SW error detected. Restarting 0x0. iwlwifi :05:00.0: Start IWL Error Log Dump: iwlwifi :05:00.0: Transport status: 0x004A, valid: 6 iwlwifi :05:00.0: Loaded firmware version: 83.ec13314b.0 gl-c0-fm-c0-83.ucode iwlwifi :05:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN iwlwifi :05:00.0: 0x0003 | trm_hw_status0 iwlwifi :05:00.0: 0x | trm_hw_status1 iwlwifi :05:00.0: 0x002C280A | branchlink2 iwlwifi :05:00.0: 0x9328 | interruptlink1 iwlwifi :05:00.0:
[Kernel-packages] [Bug 2058485] Re: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter
This bug is awaiting verification that the linux-azure/5.15.0-1064.73 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- 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/2058485 Title: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034980 Backport: ipc/msg: mitigate the lock contention with percpu counter (merged upstream in 6.1) to jammy [Impact] The msg_bytes and msg_hdrs atomic counters are frequently updated when IPC msg queue is in heavy use, causing heavy cache bounce and overhead. Change them to percpu_counter greatly improve the performance. Since there is one percpu struct per namespace, additional memory cost is minimal. Reading of the count done in msgctl call, which is infrequent. So the need to sum up the counts in each CPU is infrequent. [Fix] Backport: 72d1e611082e ipc/msg: mitigate the lock contention with percpu counter For clean backport/build, those are also required: 5d0ce3595ab75 percpu: add percpu_counter_add_local and percpu_counter_sub_local 38cd5b12b7854 ipc: Remove extra braces 0889f44e28103 ipc: Check permissions for checkpoint_restart sysctls at open time dd141a4955d5e ipc: Remove extra1 field abuse to pass ipc namespace def7343ff03bb ipc: Use the same namespace to modify and validate 1f5c135ee509e ipc: Store ipc sysctls in the ipc namespace dc55e35f9e810 ipc: Store mqueue sysctls in the ipc namespace 0e9beb8a96f21 ipc/ipc_sysctl.c: remove fallback for !CONFIG_PROC_SYSCTL 5563cabdde7ee ipc: check checkpoint_restore_ns_capable() to modify C/R proc files [Test Plan] Test as the original patch, with pts/stress-ng message passing and compare performance. [Where problems could occur] Performance regression in IPC communication/workload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] In an oem project, we found the max playback volume of the headphone is too high on 2 LG machines, it could bring harm to listeners. As requested by OEM customer, we need to decrease the max volume. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booting with the patched kernel, plug the headphone, set the playback volue to max, run: amixer -c1 contents | grep -n2 "Headphone Playback Volume" The value is 77,77 instead of 87,87 like below: numid=1,iface=MIXER,name='Headphone Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 : values=77,77 [Where problems could occur] This patch changes the amplifier's default value, probably will make the audio malfunction, but this change is specific to those 2 LG machines (by SSID), will not bring regression to other machines. For those 2 machines, we already tested patch, the audio worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
This bug is awaiting verification that the linux-azure/5.15.0-1064.73 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-azure' to 'verification-done-jammy- linux-azure'. If the problem still exists, change the tag 'verification- needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-azure-v2 verification-needed-jammy-linux-azure -- 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] In an oem project, we found the max playback volume of the headphone is too high on 2 LG machines, it could bring harm to listeners. As requested by OEM customer, we need to decrease the max volume. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booting with the patched kernel, plug the headphone, set the playback volue to max, run: amixer -c1 contents | grep -n2 "Headphone Playback Volume" The value is 77,77 instead of 87,87 like below: numid=1,iface=MIXER,name='Headphone Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 : values=77,77 [Where problems could occur] This patch changes the amplifier's default value, probably will make the audio malfunction, but this change is specific to those 2 LG machines (by SSID), will not bring regression to other machines. For those 2 machines, we already tested patch, the audio worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059143] Re: Remove getabis scripts
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2059143 Title: Remove getabis scripts Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Released Bug description: SRU Justification [Impact] With ABI checks removed from the tree (#LP2055685), there's no need to download the buildinfo from a previous version. [Fix] This is needed only in the main kernels. 1. remove the common getabis script 2. remove per kernel getabis file (this will be done with cranky fix) [Test] Build test on cbd. No issue found. Also cranked the kernels in advance to see if there were issues, but no issue was found. [Regression potential] In the current cycle, the ABI checks have been removed and this is not used anymore. No issues have been found. Now we're just removing an unused feature, therefore the regression potential is none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060446] Re: [Mantic] Compile broken on armhf (cc1 out of memory)
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2060446 Title: [Mantic] Compile broken on armhf (cc1 out of memory) Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: [SRU Justification] Impact: A set of patches from upstream stable was applied to the Mantic 6.5 kernel. The patches reworked the min()/max() macro definitions to allow more flexible input. However this caused the compile to be broken with the solo6x10 driver on armhf because its usage of nested min() and max() results in a pre-compiled file increasing from around 5MB to over 120MB (cc1: out of memory allocating 301930784 bytes after a total of 243818496 bytes). Fix: Revert the following set of patches until a final upstream solution comes up: 21e0901150a6 minmax: relax check to allow comparison between unsigned arguments and signed constants 0410eb4def1f minmax: allow comparisons of 'int' against 'unsigned char/short' 54750fcb53b3 minmax: allow min()/max()/clamp() if the arguments have the same signedness. 8d582aac6cd6 minmax: add umin(a, b) and umax(a, b) Testcase: Compiling the kernel will fail on armhf with those patches applied. So a successful build is testing this. Regression potential: This was not released. Without the new adjustments the min() and max() macros will work as before. --- Upstream discussion: https://lore.kernel.org/all/633b64e2f39e46bb8234809c5595b...@acums.aculab.com/T/#u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064560] Re: kernel panic with linux-intel-iotg 5.15.0.1056.56
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2064560 Title: kernel panic with linux-intel-iotg 5.15.0.1056.56 Status in linux package in Ubuntu: Confirmed Bug description: During the SRU testing for linux-intel-iotg 5.15.0.1056.56, Intel ADL- PS went into kernel panic. There are no journal logs existed. Please check screenshot attached. https://certification.canonical.com/hardware/202212-30962/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
This bug is awaiting verification that the linux-azure/6.5.0-1021.22 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux-azure' to 'verification-done- mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic- linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-azure-v2 verification-needed-mantic-linux-azure -- 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/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New 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: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] The first commit introduces no functional changes, it merely relocates the delay flag to dc_debug_options and makes some consequent modifications. The second commit introduce a new flag, but we don't use it. The third and forth commits add 4 panel IDs which should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064560] Re: kernel panic with linux-intel-iotg 5.15.0.1056.56
Is this 100% reproducible ? Is this hardware remotely accessible ? -- 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/2064560 Title: kernel panic with linux-intel-iotg 5.15.0.1056.56 Status in linux package in Ubuntu: New Bug description: During the SRU testing for linux-intel-iotg 5.15.0.1056.56, Intel ADL- PS went into kernel panic. There are no journal logs existed. Please check screenshot attached. https://certification.canonical.com/hardware/202212-30962/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Changed in: linux-oem-6.8 (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-meta-oem-6.8 (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Released Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem-6.8 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: Fix Committed Status in linux-meta source package in Noble: Fix Committed Status in linux-meta-oem-6.8 source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 == linux-meta, linux-meta-unstable, linux-meta-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The main fixes are in kernel & dkms packages. This adds ivsc-modules to Provides list of linux-image-generic as other built-in linux-modules-foo packages do. [Test Case] The generated meta package linux-image-generic should then provides "ivsc-modules". [Where problems could occur] Meta package changes only. No real effect but in package dependency. [Other Info] While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will only be nominated for Unstable/Noble/OEM-6.8. == ipu6-drivers, linux, linux-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
This bug was fixed in the package linux-firmware - 20230919.git3672ccab-0ubuntu2.10 --- linux-firmware (20230919.git3672ccab-0ubuntu2.10) mantic; urgency=medium * Miscellaneous Ubuntu changes - [Workflow] Swich to actions/ubuntu-check-commit * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283) - Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: #2053277) - amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32 -- Juerg Haefliger Thu, 21 Mar 2024 08:59:16 +0100 ** Changed in: linux-firmware (Ubuntu Mantic) Status: Fix Committed => 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
If you tell me how to "gather the full kernel log from when the system booted to black screen", I might try that. -- 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/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
This bug was fixed in the package linux-firmware - 20230919.git3672ccab-0ubuntu2.10 --- linux-firmware (20230919.git3672ccab-0ubuntu2.10) mantic; urgency=medium * Miscellaneous Ubuntu changes - [Workflow] Swich to actions/ubuntu-check-commit * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283) - Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: #2053277) - amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32 -- Juerg Haefliger Thu, 21 Mar 2024 08:59:16 +0100 ** Changed in: linux-firmware (Ubuntu Mantic) Status: Fix Committed => 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Great job, confirmed that fix works on a Razer Blade 16 - RZ09-0483. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I followed this advice (mentioned above): https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share_medium=web3x_name=web3xcss_term=1_content=share_button It seems that "quiet splash" is the actual problem, not "nomodeset" (solution). I edited the GRUB entry as follows (with results added): 1) With only "quiet splash" (no "nomodeset"), default installation, fresh install of Kubuntu 24.04: only black screen, nothing happens. 2) Add "nomodeset" to "quiet splash": everything works perfectly. Also works permanently with editing of /etc/default/grub. 3) Delete "quiet splash" in GRUB and do not add "nomodeset" (or delete "nomodeset", if previously added): everything works perfectly (see Reddit link above). 4) Delete "nomodeset", after having added it to /etc/default/grub and updated grub previously, but leave the 'original' "quiet splash": computer hangs, completely unresponsive, after showing the following code: Booting a command list Loading Linux 6.8.0-31-generic ... Loading initial ramdisk ... 5) Again, boot without both "quiet splash" or "nomodeset": everything works perfectly. Also works permanently with /etc/default/grub. It went quite fast, but after "Loading initial ramdisk ..." I think the next code line was "enabling secure boot". It might be a problem with "secure boot" and "quiet splash". Secure boot is enabled in both my installations, so I can't try the other option ("secure boot" disabled in the EFI BIOS before installation). Workaround (for me): - Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Delete the words "quiet splash" (leave the quotation marks ''). - Run sudo update-grub -- 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/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2064291] Re: Ubuntu 24.04 crashed multiple times
Woopsie ** Attachment added: "var crash.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+attachment/5774022/+files/var%20crash.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/2064291 Title: Ubuntu 24.04 crashed multiple times Status in linux package in Ubuntu: New Bug description: Ubuntu 24.04 crashed multiple times due to unstable kernel. Crashed 8 times attempting to file this bug report. Recently installed the new updates for 24.04. Steps to reproduce: Open "Show Apps"-Crash, Open Firefox -Crash, Open Terminal -Crash, Setting idle does not crash. Installed synaptic -Crashed 2 times. Check for broken packages - None, no missing dependencies. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:b3 1256 F pipewire /dev/snd/controlC0: b3 1260 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 09:07:32 2024 InstallationDate: Installed on 2024-04-25 (5 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 vmwgfxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=381f85c9-ec76-4686-aaa1-aa5e3673ec82 ro quiet splash RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.30 --- linux-firmware (20220329.git681281e4-0ubuntu3.30) jammy; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] rules: Check for git executable - [Workflow] Swich to actions/ubuntu-check-commit * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283) - Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: #2053277) - amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32 -- Juerg Haefliger Thu, 21 Mar 2024 09:03:22 +0100 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053277] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Committed Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.30 --- linux-firmware (20220329.git681281e4-0ubuntu3.30) jammy; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] rules: Check for git executable - [Workflow] Swich to actions/ubuntu-check-commit * Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi (LP: #2055283) - Intel Bluetooth: Update firmware file for Intel Bluetooth Magnetor AX201 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 - Intel Bluetooth: Update firmware file for Magnetor Intel Bluetooth AX203 * add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy (LP: #2053277) - amdgpu: update DMCUB to v0.0.203.0 for DCN314 and DCN32 -- Juerg Haefliger Thu, 21 Mar 2024 09:03:22 +0100 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => 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/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Committed Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055283] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
I think this bug also affects Intel GPUs. I did an installation today that resulted in a black screen without "nomodeset". See: https://bugs.launchpad.net/ubuntu/+bug/2063877 -- 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/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system
... oh yes, I had the same problem with AMD Radeon Integrated Graphics; see the same bug report: https://bugs.launchpad.net/ubuntu/+bug/2063877 -- 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/2063983 Title: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system Status in linux package in Ubuntu: Confirmed Bug description: Config: Ryzen 5 5600X with Radeon 6700 XT GPU, a Navi22 card. Using xUbuntu. I had been daily driving the 24.04 nightly iso since March. About a week ago, I took a kernel update via apt and rebooted. The result was that the system would hard freeze to a black screen after the initial kernel messages cleared from the screen. Ctrl-Alt-Del did nothing, switching terminals (ctrl-alt-f#) did nothing, had to hard power off to regain control of the system. I tried various fixes, none of which permanently stuck. This includes nomodeset in grub, rebooting into safe mode, checking for proprietary drivers. Safe mode allowed me to reboot once more into desktop, but then any subsequent reboots would result in a black screen lockup. Suspending while able to use the desktop before reboot would cause a black screen lockup did not seem to cause any issues. 3 days before 24.04 was officially released, I reflashed the most recent installer iso to my thumbdrive, copied my home folder to my RAID and did a full wipe and fresh install. First reboot after installation always went to the desktop. Subsequent reboots always resulted in a black screen lockup. Memtest cleared without errors. Again tried various fixes, nomodeset, safe mode, drivers. The only consistency was that regardless of what I could do to regain control or what I did differently when doing a wipe and reinstall, I would always reboot to a black screen. Once 24.04 was officially released, I again did a full wipe and reinstall and encountered all of the above same issues as before. After mentioning this in #ubuntu on libera, someone suggested a kernel downgrade. 24.04 as installed was using 6.8.0-31.31 Using Mainline, I downgraded to the next minor version below 6.8 that was considered stable. 6.7.10 Problem went away. No more black screen on boot, no more hard power offs required to be able to use my system again, no suspend issues. Was not necessary for me to do anything else to maintain a consistent successful reboot to desktop. Did yet another full wipe and fresh install of 24.04, only installing Mainline upon first reboot to install 6.7.10, using Grub Customizer to edit the default grub option to boot the 6.7.10 kernel instead. No issues. I apologise that I did not collect logs during this process. --- For those affected by this issue, this was my fix: Install 24.04, reboot, at the desktop, open a terminal window and add the following PPAs: sudo add-apt-repository ppa:cappelikan/ppa sudo apt update sudo apt install mainline sudo add-apt-repository ppa:danielrichter2007/grub-customizer sudo apt-get update sudo apt-get install grub-customizer Run mainline-gtk, install kernel version 6.7.10 run grub-customizer, move "Ubuntu, with Linux 6.7.10-060710-generic" to top of list, making it the default option. Save and reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064354] Re: File manager crashes on run
The crash from the previous comment is in libnvidia-vulkan-producer.so so also a nvidia driver issue, I'm reassigning > I wonder why 535 was the most recent driver offered by "Software & Updates -> > Additional Drivers". The rational is on bug #2061830 but basically the new version was available too late in the cycle to be properly tested before release but it will enabled there once we have confidence it's working correctly ** Package changed: nautilus (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2064354 Title: File manager crashes on run Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I obtained the following from the command prompt: $ nautilus ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 16:15:29 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-04-24 (6 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2064354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064275] Re: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument]
I can reproduce it by turning off my computer and then directly logging in using wayland every time. ** Attachment added: "GSLog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064275/+attachment/5773978/+files/gslog.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/2064275 Title: Blank screen after logging in Wayland using HP Thunderbolt G4 [drmModeAtomicCommit: Invalid argument] Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Using two displayport 4k LG monitors on a HP Thunderbolt G4 dock. After logging in using wayland, both monitors goes blank and then enters power saving mode. If I replug the dock then the monitors wake up but with display settings reset. When using x-server, both screen work as normal after login remembering my screen placement etc. Optimus Laptop AMD+Nvidia graphics on-demand using USB-C alt mode. Ubuntu 24.04 with latest updtes installed. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-26 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 46.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 RelatedPackageVersions: mutter-common 46.0-1ubuntu9 Tags: noble Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-04-26 (4 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 46.0-0ubuntu5 PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 RelatedPackageVersions: mutter-common 46.0-1ubuntu9 Tags: noble wayland-session Uname: Linux 6.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin ollama plugdev sudo users _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2064354] [NEW] File manager crashes on run
You have been subscribed to a public bug: Nautilus would not open a GUI window after a fresh Ubuntu 24.04 install. I obtained the following from the command prompt: $ nautilus ** Message: 16:12:45.453: Connecting to org.freedesktop.Tracker3.Miner.Files libEGL warning: egl: failed to create dri2 screen Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 16:15:29 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-04-24 (6 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- File manager crashes on run https://bugs.launchpad.net/bugs/2064354 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp