[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 2061324] Re: Error when re-building package from source
Hello Hector, or anyone else affected, Accepted intel-gpu-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.26-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- 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 1949314] Please test proposed package
Hello Leonardo, or anyone else affected, Accepted intel-gpu-tools into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.26-2ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: Fix Committed Status in intel-gpu-tools source package in Mantic: Fix Committed Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully NOTES: For Noble, all the 4 patches will be backported For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Hello Leonardo, or anyone else affected, Accepted intel-gpu-tools into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/intel-gpu- tools/1.27.1-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-mantic ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed-jammy -- 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/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: Fix Committed Status in intel-gpu-tools source package in Mantic: Fix Committed Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully NOTES: For Noble, all the 4 patches will be backported For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+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 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
Looking at the firmware-sof SRU, it looks like both this package and the kernel need updating to complete the hardware enablement. So have these been tested from -proposed together? It looks like verification was done separately for the kernel and for the userspace package, and that makes no sense to me. What about HWE vs. non-HWE kernels? Please confirm that you have completed SRU verification using the Test Plan and using packages only from the main archive (including packages from -proposed as appropriate) and from no other sources. Please detail the specific combinations of kernel and firmware-sof tested. Once done, please flip the tags back. ** Tags removed: verification-done-jammy verification-done-mantic ** Tags added: verification-needed-jammy verification-needed-mantic -- 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/2042090 Title: Orchid Bay MLK2/Maya Bay MLK soundwire support Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in firmware-sof source package in Noble: Fix Released Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [SRU Justifications] == kernels == [Impact] Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms. [Fix] Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part, following upstream commits are mandatory: * commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713 rt1316 config") * commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713 support") * commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct cards->components by name_prefix") * commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic config"): linux-next [Test Case] 1. enable -proposed pocket and install the latest kernel 2. browse youtube, hold backspace on virtual terminal or whatever makes some noises 3. expected sound system brought up and reacts accordingly [Where problems could occur] While this enables new devices on new platforms, we may bump into burst noises, power consumption problems at corner cases not covered by test program. [Other Info] This is to enable sof devices on Intel MTL platform, which is only supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and Jammy. == firmware-sof == [Impact] Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms. [Fix] Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware- sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2 topology files"). [Test Case] 1. enable -proposed pocket and install firmware-sof-signed 2. browse youtube, hold backspace on virtual terminal or whatever makes some noises 3. expected sound system brought up and reacts accordingly [Where problems could occur] While this enables new devices on new platforms, we may bump into burst noises, power consumption problems at corner cases not covered by test program. [Other Info] This is to enable sof devices on Intel MTL platform, which is only supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and Jammy. == original bug report == The kernel patches has been applied in the ASoC tree. Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel (spinics.net) [spinics.net] https://www.spinics.net/lists/alsa-devel/msg167273.html We need 3/23, 4/23, 6/23, and https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176 And the UCM PR is submitted ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 · alsa-project/alsa-ucm-conf (github.com) [github.com] https://github.com/alsa-project/alsa-ucm-conf/pull/363 See bug 2042902. For firmware-sof, need upstream commit 99466c05f15f ("Add Intel SOF2.7.2 topology files"). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2042090/+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 2041751] Re: RM: Remove dangerously insecure MPPE PPTP from Ubuntu
The removal of pptpd seems like something that should be release noted to me, to give enquiring users somewhere to refer to. ** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2041751 Title: RM: Remove dangerously insecure MPPE PPTP from Ubuntu Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: New Status in network-manager-pptp package in Ubuntu: New Status in pptp-linux package in Ubuntu: New Status in pptpd package in Ubuntu: Fix Released Bug description: Remove dangerously insecure MPPE PPTP from Ubuntu https://pptpclient.sourceforge.net/protocol-security.phtml It has been dead for over 20 years now. Current Windows versions natively support IPSec and L2TP as much better alternatives. https://learn.microsoft.com/en-us/windows/win32/fwp/ipsec- configuration#how-to-use-wfp-to-configure-ipsec-policies https://learn.microsoft.com/en-US/troubleshoot/windows- server/networking/configure-l2tp-ipsec-server-behind-nat-t-device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2041751/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Thank you for the clarification! I'll remove the regression-update tag then, since this is the intended behaviour of the security update, so it shouldn't count towards regression statistics. ** Tags removed: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Looks like this is a reported regression in the security pocket. ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Confirmed Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Reopening because a PIN of is not reported to work (and even if it did, that would still be a regression in a stable release). ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Changed in: bluez (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Confirmed Bug description: Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 2037224] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230919.git3672ccab-0ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2037224 Title: Multiple RTL8851BE BT stability issues Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed 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] There are multiple stability issues for RTL8851B. Issue-1: After disabling BT and leaving it idle for a period, manually turning on the RTL8851BE will fail. Issue-2: Failed to probe Bluetooth USB interface after resumed from suspend. There may be either failure to read device descriptors: usb 1-14: device descriptor read/64, error -71 or tx command timeout: Bluetooth: hci0: Opcode 0x2041 failed: -110 Bluetooth: hci0: command 0x2041 tx timeout [Fix] Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to 0x048A_D230"). [Test Case] $ checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto [Where problems could occur] This updates opaque firmware blobs, so it could bring further stability issues and/or power consumption changes. [Other Info] While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only jammy and mantic are nominated for fix. = original bug report == [issue 1] After disabling BT and leaving it idle for a period, manually turning on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.) Test step: 1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0) 2. Check BT function after boot into OS. 3. Manually turn OFF BT function. Then wait for 1 minute. 4. Manually turn ON the BT function. 5. Unable to enable BT function. (issue occurs) [issue 2] System usb got tx command timeout after suspend resume. Log: Got read usb descriptor fail after suspend resume. Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 using xhci_hcd Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 using xhci_hcd Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 using xhci_hcd And tx command timeout. Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110 Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4 using xhci_hcd Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Test step: 1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso 2. Boot into OS 3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037224/+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 2037224] Re: Multiple RTL8851BE BT stability issues
The verification-done* tags are used by the SRU process only, to track verification of a package in the official Ubuntu proposed pocket once completed according to a Test Plan agreed by the SRU team. Please do not use this tag unless this process has been followed. Since 20230919.git3672ccab-0ubuntu2.2 has never been published by Ubuntu, this is impossible, so I'm removing the tag. ** Tags removed: verification-done-mantic -- 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/2037224 Title: Multiple RTL8851BE BT stability issues Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed 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] There are multiple stability issues for RTL8851B. Issue-1: After disabling BT and leaving it idle for a period, manually turning on the RTL8851BE will fail. Issue-2: Failed to probe Bluetooth USB interface after resumed from suspend. There may be either failure to read device descriptors: usb 1-14: device descriptor read/64, error -71 or tx command timeout: Bluetooth: hci0: Opcode 0x2041 failed: -110 Bluetooth: hci0: command 0x2041 tx timeout [Fix] Upstream commit addc33924 ("rtl_bt: Update RTL8851B BT USB firmware to 0x048A_D230"). [Test Case] $ checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto [Where problems could occur] This updates opaque firmware blobs, so it could bring further stability issues and/or power consumption changes. [Other Info] While RTL8851B is only supported in oem-6.5 and linux/mantic >= 6.4, only jammy and mantic are nominated for fix. = original bug report == [issue 1] After disabling BT and leaving it idle for a period, manually turning on the RTL8851BE will fail. (Can't reproduce on Wifi functionality.) Test step: 1. Insert RTL8851BE Wifi card and install Ubuntu 22.04 OS. (Kernel : 6.5.0) 2. Check BT function after boot into OS. 3. Manually turn OFF BT function. Then wait for 1 minute. 4. Manually turn ON the BT function. 5. Unable to enable BT function. (issue occurs) [issue 2] System usb got tx command timeout after suspend resume. Log: Got read usb descriptor fail after suspend resume. Sep 11 16:37:37 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 using xhci_hcd Sep 11 16:37:37 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:38 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 using xhci_hcd Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:38 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Sep 11 16:37:39 ubuntu kernel: usb 1-14: reset full-speed USB device number 3 using xhci_hcd And tx command timeout. Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: Opcode 0x2041 failed: -110 Sep 11 16:37:41 ubuntu kernel: Bluetooth: hci0: command 0x2041 tx timeout Sep 11 16:37:41 ubuntu kernel: usb 1-14: new full-speed USB device number 4 using xhci_hcd Sep 11 16:37:41 ubuntu kernel: usb 1-14: device descriptor read/64, error -71 Test step: 1. Install dell-bto-jammy-jellyfish-abra-X96-20230822-1.iso 2. Boot into OS 3. checkbox-cli run com.canonical.plainbox::suspend/suspend_advanced_auto To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Oh, wait. You are just fixing the race condition? Please the SRU documentation then. Right now I read "We should drop it in favour of using simpledrm with fbdev emulation layer" which is very misleading as to what you're actually proposing to do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
> it will expose the race condition to GDM What race condition, please? If this is the justification for the proposed SRU, then I'd expect to see that explained, but I don't see any explanation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965303] Re: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer
Oh, this? > When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. In that case, why can you not revert the kernel config change in the HWE backport to Jammy? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1965303 Title: Migrate from fbdev drivers to simpledrm and DRM fbdev emulation layer Status in gdm: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: In Progress Status in linux source package in Jammy: Won't Fix Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in gdm3 source package in Lunar: Invalid Status in linux source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-470 source package in Lunar: Fix Released Status in gdm3 source package in Mantic: Fix Released Status in linux source package in Mantic: Confirmed Status in nvidia-graphics-drivers-470 source package in Mantic: Fix Released Status in linux package in Fedora: Fix Released Bug description: [ Impact ] The fbdev subsystem has been deprecated for a long time. We should drop it in favour of using simpledrm with fbdev emulation layer. This requires Kernel config changes: FB_EFI=n FB_VESA=n fbcon will still require FB to be available, but will use the fbdev emulation layer When this stack is enabled, it changes boot timing such that some drivers may take a longer time to boot and GDM may hang in a black screen. This issue has been readily reproduced in Ubuntu and reported to upstream mutter. https://gitlab.gnome.org/GNOME/mutter/-/issues/2909 [ Test Plan ] * Ensure that a kernel with required kernel changes can boot to GDM using DRM driver (amdgpu, i915, or nouveau) [ Where Problems could occur ] * Race conditions could be exposed to DE environments * Software that expects to find DRM device at /dev/dri/card0 may have a problem. * Some older versions of NVIDIA driver might not work properly. [ Other Info ] * Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2022385 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1965303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028366] Re: Kernel header installation fails for incompatible DKMS modules
> This is an improvement to the current situation of aborting release upgrade half way through. Is it? If the user ends up with a broken DKMS package on release upgrade, then at least they'll know about it. But if we silently ignore the failure, the release upgrade will finish pretending that it was successful when it was not, and then what if they find the system broken later? > Further UX / hooks might be needed in the release upgrade to complete the story of asking the user what they want to do with regressed dkms modules. I agree that this is appropriate to fix in SRUs, but can we fix the entire story rather than iterating in the stable release? I prefer not to move the goalposts but I think the above is a big enough concern to be worth considering first. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Jammy: Confirmed Status in dkms source package in Lunar: Fix Committed Status in dkms source package in Mantic: Fix Released Bug description: [ Impact ] If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. This is especially acute during release-upgrades, as dkms modules are upgraded out of order, and major kernel version are upgraded out of order. Majority of the time there is a new dkms available, which should attempt build & load. However, many modules are often remain broken, no longer needed, or need user to fetch updated versions themselves. [ Test Plan ] * Install jammy * Add module that support v5.15 kernel, but fails to compile with any newer kernels (one can find examples of such dkms modules in the archive, or out of the archive) * Perform release upgrade with patched dkms pre-installed * Release upgrade should succeed, despite unable to compile all dkms modules [ Where problems could occur ] * This is an improvement to the current situation of aborting release upgrade half way through. It doesn't quite resolve the UX to notify the user which dkms modules did not manage to compile, or to ask user to uninstall or to update them. Further UX / hooks might be needed in the release upgrade to complete the story of asking the user what they want to do with regressed dkms modules. [ Other Info ] * See lots and lots of upgrade bugs, failing on dkms module installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+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 2028366] Re: Kernel header installation fails for incompatible DKMS modules
@afredfactice it sounds like your issue is not related to this bug. If you think it is related, please could you explain why? Otherwise, please see https://ubuntu.com/community/support for community support options. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2028366 Title: Kernel header installation fails for incompatible DKMS modules Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Jammy: Confirmed Status in dkms source package in Lunar: Fix Committed Status in dkms source package in Mantic: Fix Released Bug description: [ Impact ] If a new kernel is installed, all installed DKMS modules are built for that new kernel. There might be incompatible modules that won't compile for the new kernel which results in a kernel header package installation failure. That's bad and not really correct, the incompatible DKMS module is the problem and not the new kernel. In this case, DKMS module build failures should be ignored so that the kernel installation completes. This is especially acute during release-upgrades, as dkms modules are upgraded out of order, and major kernel version are upgraded out of order. Majority of the time there is a new dkms available, which should attempt build & load. However, many modules are often remain broken, no longer needed, or need user to fetch updated versions themselves. [ Test Plan ] * Install jammy * Add module that support v5.15 kernel, but fails to compile with any newer kernels (one can find examples of such dkms modules in the archive, or out of the archive) * Perform release upgrade with patched dkms pre-installed * Release upgrade should succeed, despite unable to compile all dkms modules [ Where problems could occur ] * This is an improvement to the current situation of aborting release upgrade half way through. It doesn't quite resolve the UX to notify the user which dkms modules did not manage to compile, or to ask user to uninstall or to update them. Further UX / hooks might be needed in the release upgrade to complete the story of asking the user what they want to do with regressed dkms modules. [ Other Info ] * See lots and lots of upgrade bugs, failing on dkms module installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2028366/+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 2024479] Update Released
The verification of the Stable Release Update for kexec-tools 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 kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: Fix Released Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Released Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. 1) Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. 2) Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. kexec-tools - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. kexec-tools - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
I noted that Lunar wasn't updated when I accepted this, but didn't want to block progress Jammy while I enquired. However, another SRU team member has confirmed that it is a requirement for hardware enablements for the latest stable release of Ubuntu to be enabled as well - otherwise users will be regressed when they upgrade. Please could you also upload a fix for Lunar? This will block the release to Jammy. I'll add a task to track that. Thanks! ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: firmware-sof (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: firmware-sof (Ubuntu Lunar) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Lunar: Triaged Status in linux source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: New Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2020627] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2020627 Title: upgrade iwlwifi firmware of FW API 72 for WiFi 6E support in Malaysia and Morocco Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [SRU Justification] [Impact] iwlwifi takes firmware updates to support WiFi 6E in Malaysia and Morocco. The models in concern are AX210 (iwlwifi-ty-a0-gf-a0-*), AX211 (iwlwifi-so-a0-gf-a0-*) and AX411 (iwlwifi-so-a0-gf4-a0-*). [Fix] pnvm along with the ucode firmware from upstream commit 5bc279fb161d ("iwlwifi: update core69 and core72 firmwares for So device") are required. While the pnvm and ucode blobs may not be upgraded simultaneously in one single commit, those involved in the upgrade path are also pulled. [Test Case] Use `iw` to enumerate supported WiFi 6E band: $ iw reg get global country : DFS-FCC ... (5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN [Where problems could occur] Currently linux-5.15 has FW API 66, linux-hwe-5.19 or above has 72, linux-6.3 has 74, and linux-unstable (v6.4) or above has 78, so this will update iwlwifi firmware usage for kernels <= 6.2 in Jammy, e.g. linux-oem-6.1, linux-5.15. [Other Info] Blobs with FW APIs >= 72 do no harm to jammy kernels, but will be referenced in oem-6.5 if planned. These commits have been included in linux-firmware/lunar, so only Jammy is nominated for fix. == original bug report == AX210: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-ty-a0-gf-a0-72.ucode?id=4309412c0d872897dc913c7d2797bb5ce05893ad pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 AX211: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=20d9516de4cdc041e2aa83009e5b0464b1c3ed81 AX411: -72 ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0-72.ucode?id=5bc279fb161d529baaf8e837d900235fbbe9bf2f pnvm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/iwlwifi-so-a0-gf4-a0.pnvm?id=78a8782a9e51e502a6ed267d270c6925fb738805 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2020627/+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 2023193] Please test proposed package
Hello Chris, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2023193 Title: Add firmware files for HP G10 series laptops Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Won't Fix Status in linux-firmware source package in Lunar: Fix Committed Bug description: [ Impact ] HP G10 laptops need more Cirrus firmware files to enable all amplifiers to output audio with expected level. [ Test Plan ] * Power up the HP G10 series laptops and adjust the output volume to MAX * Verify speaker output volume by ears. [ Where problems could occur ] * The firmware files are released by Cirrus codec for particular HP series laptops. * The risk of regression should only impact particular models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023193/+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 2023193] Please test proposed package
Hello Chris, or anyone else affected, Accepted linux-firmware into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2023193 Title: Add firmware files for HP G10 series laptops Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Won't Fix Status in linux-firmware source package in Lunar: Fix Committed Bug description: [ Impact ] HP G10 laptops need more Cirrus firmware files to enable all amplifiers to output audio with expected level. [ Test Plan ] * Power up the HP G10 series laptops and adjust the output volume to MAX * Verify speaker output volume by ears. [ Where problems could occur ] * The firmware files are released by Cirrus codec for particular HP series laptops. * The risk of regression should only impact particular models To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023193/+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 2024427] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2024427] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2024774] Please test proposed package
Hello Mario, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2024774 Title: AMD Rembrandt / Phoenix PSR-SU related freezes Status in Linux Firmware: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Bug description: [ Impact ] When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU). After a non-deterministic amount of time the system may hang with a message like this in the logs: "[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed out]" Affects users of laptops that contain: * AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips * eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail) [ Test Plan ] * Test an affected laptop with the newer firmware and ensure that PSR-SU function can be enabled and system is stable. * Ensure other functions such as hotplugging monitors and suspending continue to work. [ Where problems could occur ] * Affected firmware only is loaded on Rembrandt and Phoenix laptops. Problems would be localized to these machines. [ Other Info ] The minimum firmware needed to help these hangs: * Rembrandt: 0x43a or later * Phoenix: 0x8001000 or later The following commit upgrades the firmware for Rembrandt (amdgpu/yellow_carp_dmcub.bin) to 0x43c: 9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics") The following commit upgrades the firmware for Phoenix (amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00: 045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs") The TCON in a given laptop can be identified from the DPCD with this script: https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2024774] Please test proposed package
Hello Mario, or anyone else affected, Accepted linux-firmware into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2024774 Title: AMD Rembrandt / Phoenix PSR-SU related freezes Status in Linux Firmware: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Bug description: [ Impact ] When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU). After a non-deterministic amount of time the system may hang with a message like this in the logs: "[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed out]" Affects users of laptops that contain: * AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips * eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail) [ Test Plan ] * Test an affected laptop with the newer firmware and ensure that PSR-SU function can be enabled and system is stable. * Ensure other functions such as hotplugging monitors and suspending continue to work. [ Where problems could occur ] * Affected firmware only is loaded on Rembrandt and Phoenix laptops. Problems would be localized to these machines. [ Other Info ] The minimum firmware needed to help these hangs: * Rembrandt: 0x43a or later * Phoenix: 0x8001000 or later The following commit upgrades the firmware for Rembrandt (amdgpu/yellow_carp_dmcub.bin) to 0x43c: 9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics") The following commit upgrades the firmware for Phoenix (amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00: 045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs") The TCON in a given laptop can be identified from the DPCD with this script: https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2026253] Please test proposed package
Hello Timo, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2026253 Title: i915: Add DMC/GuC/HuC firmware for Meteor Lake Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel. As the kernel is only for jammy, there's no need to target lunar/kinetic. [Test case] Install the update, check that i915.ko driver loads them fine on MTL hardware. [Where problems could happen] These are new files for new hardware, so they can't regress shipping hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2026253/+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 2027959] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. This is a follow-up to bug 2024427 to patch additional models. [Fix] firmware patches: * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] For the firmware parts, they have been included in linux-firmware/mantic, leaving only linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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 2027959] Please test proposed package
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2027959 Title: Follow-up: potential S3 issue for amdgpu Navi 31/Navi33 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Status in linux-firmware source package in Mantic: Fix Released Bug description: [SRU Justification] [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. This is a follow-up to bug 2024427 to patch additional models. [Fix] firmware patches: * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] For the firmware parts, they have been included in linux-firmware/mantic, leaving only linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == Per comment https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs were requested to be pulled back to linux-firmware/lunar and jammy. They are: * ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5 release (already pulled in bug 2024427) * a5d7b4df1 amdgpu: update GC 11.0.2 firmware for amd.5.5 release (already pulled in bug 2024427) * 60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release * 31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release * 1c513ec74 amdgpu: Update GC 11.0.1 and 11.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2027959/+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 2024479] Re: kdump fails on big arm64 systems when offset is not specified
Hello Ioanna, or anyone else affected, Accepted kexec-tools into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kexec- tools/1:2.0.18-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: kexec-tools (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on big arm64 systems when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.15 package in Ubuntu: Invalid Status in kexec-tools source package in Focal: Fix Committed Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.15 source package in Focal: In Progress Status in kexec-tools source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-hwe-5.15 source package in Jammy: Invalid Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in linux-hwe-5.15 source package in Kinetic: Invalid Status in kexec-tools source package in Lunar: Fix Committed Status in kexec-tools source package in Mantic: Fix Released Bug description: [Impact] kdump fails on arm64, on machines with a lot of memory when offset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel region. [Fix] To address this issue the following upstream commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the Focal 5.15 hwe kernel (from Jammy) will be fixed. [Test Plan] You need an arm64 machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump, configure the crash kernel size, and trigger a crash. - Failing scenario (crashkernel >= 4G, without offset "@"): It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. - Working scenario (crashkernel < 4G, e.g., 'crashkernel=1G') This must continue to work with the new patches (ie, no regressions), including patched kexec-tools on unpatched kernel (eg, 5.4 kernel on Focal). [Regression Potential] KERNEL 5.15 - Jammy (and Focal via the HWE kernel): To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
Hello Chris, or anyone else affected, Accepted firmware-sof into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2.0-1ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: firmware-sof (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags removed: verification-done-jammy ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Committed Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: Fix Released Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: SRU Jusitification for firmware-sof [Impact] To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6 [Fix] Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too [Test Case] Install the fixes on the target platform(RPL Dell SKU 0BDA) and verify the audio function. 1. Install the firmware-sof on platform(RPL) with Audio Smart AMP IC ALC1319D 2. Make sure the audio works 3. Also try above steps on other platforms(ADL/TGL) to make sure the audio keep working. [Where problems could occur] New firmware may affect ADL, RPL, and TGL platforms, we need to verify it on not only the target platform, but other existing platforms. [Misc] https://github.com/thesofproject/sof-bin/releases/tag/v2.2.5 https://github.com/thesofproject/sof-bin/releases/tag/v2.2.6 [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2012612] Re: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well
Hello Roxana, or anyone else affected, Accepted dkms into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.8.7-2ubuntu2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: [SRU Justification] Impact: Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG which prevent it from building if a specific configuration is enabled/disabled. This feature was released for kinetic but not for jammy. This backports the patch to jammy as well. + + [racb] This feature is required as the simplest way to deal with some of + the HWE DKMS fixes needed in Jammy such as in bug 2012412. Fix: Backported BUILD_EXCLUSIVE_CONFIG.patch from kinetic. In order to be applied, I had to slightly modify the first junk. Other than that, it was a clean backport. [Testcase] $ sudo apt install linux-image-kvm linux-headers-kvm $ sudo apt install evdi-dkms Before the fix, it will fail with this error: DKMS make.log for evdi-1.12.0+dfsg for kernel 5.15.0-1029-kvm (x86_64) Thu Mar 23 10:10:14 UTC 2023 make: Entering directory '/usr/src/linux-headers-5.15.0-1029-kvm' CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_add’: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:49:16: error: implicit declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] 49 | return i2c_add_adapter(adapter); |^~~ |i2c_verify_adapter /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_remove’: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:54:9: error: implicit declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] 54 | i2c_del_adapter(adapter); | ^~~ | i2c_verify_adapter cc1: some warnings being treated as errors make[1]: *** [scripts/Makefile.build:297: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o] Error 1 make: *** [Makefile:1906: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2 make: Leaving directory '/usr/src/linux-headers-5.15.0-1029-kvm' This fails because CONFIG_I2C=n for a KVM kernel derivative. Even though evdi has this build rule: BUILD_EXCLUSIVE_CONFIG="CONFIG_I2C CONFIG_DRM" After the fix, it will not build: Building initial module for 5.15.0-1029-kvm Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for module evdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for module evdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Skipped. [Regression potential] Very low, this is just a simple feature to prevent building a module. ** Changed in: dkms (Ubuntu Jammy) Status: In Progress =>
[Kernel-packages] [Bug 2009676] Proposed package upload rejected
An upload of thermald to focal-proposed has been rejected from the upload queue for the following reason: "Question in https://bugs.launchpad.net/oem-priority/+bug/2009676/comments/14 outstanding for over a month". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2009676 Title: Add support for Raptor Lake S CPUs Status in OEM Priority Project: Fix Released Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Incomplete Status in thermald source package in Jammy: Fix Released Bug description: [Impact] * Support thermald on Raptor Lake S CPU. [Test Plan] * Use a machine with a Raptor Lake S cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to add support for Raptor Lake S in thermald, which won't impact other hardware. [Other Info] https://github.com/intel/thermal_daemon/commit/e03493dc1e972374c1686492655250f8f48a15ba To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009676/+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 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
Which package builds of linux-firmware did you test please? All three? Just one? -- 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/1968604 Title: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Kinetic: Fix Committed Status in linux-firmware source package in Lunar: Fix Committed Bug description: [Impact] I have usb bluetooth 5.0 dongle which uses Realtek RTL8761B chip. 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio USB adapter very often stops working, can't connect or find other bluetooth devices. The adapter can't work even after reboots. The following entries appear in the log: апр 11 13:47:14 desktop kernel: Bluetooth: hci0: command 0x2005 tx timeout апр 11 13:47:16 desktop kernel: Bluetooth: hci0: command 0x2041 tx timeout апр 11 13:47:18 desktop kernel: Bluetooth: hci0: command 0x2042 tx timeout Firmware loaded correctly, but something is not working. апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1 апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin апр 11 13:46:54 desktop kernel: Bluetooth: hci0: RTL: cfg_sz 6, total sz 27814 1) I use: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) linux-firmware: 20220329.git681281e4-0ubuntu1 3) What you expected to happen? I expect a well working bluetooth adapter. 4) What happened instead? My bluetooth adapter may work, may not. The adapter may stop finding and connecting to other devices. I've found the same bug https://bugzilla.kernel.org/show_bug.cgi?id=214111#c1 I've downloaded Windows's archive http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2021/05/ca0e770c-6a5d-4de0-b37a-f4b91cccd8c3_7778831d2b9d721cf94d5a8d8c0676ff1b96c874.cab I've unpacked file rtl8761b_mp_chip_bt40_fw_asic_rom_patch_new.dll and replaced /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin and deleted rtl8761bu_config.bin After I changed firmware my usb dongle work fine. Could you change firmware rtl8761bu_fw.bin rtl8761bu_config.bin to other correct version? Could you move Realtek's rtl_bt firmware or RTL8761B's firmware into separate packages. I will remove the RTL8761B firmware package and put them manually. bluetoothctl --version bluetoothctl: 5.64 hci0: Type: Primary Bus: USB BD Address: 00:E0:4C:FC:E2:03 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:5751 acl:49 sco:0 events:489 errors:0 TX bytes:219114 acl:398 sco:0 commands:83 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: PERIPHERAL ACCEPT Name: 'desktop' Class: 0x7c0104 Service Classes: Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x97b LMP Version: 5.1 (0xa) Subversion: 0xec43 Manufacturer: Realtek Semiconductor Corporation (93) rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Realtek's worker updated these bad firmware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=45dc5f0b8e2f2d43312d22511cb26658b9ee2c80 [Test Case] Connect to and use a bluetooth device connected to a RTL8761B base USB BT controller. [Fix] Use latest rtl8761bu firmware blobs updates from linux-firmware. [Where Problems Could Occur] These firmwares are specific for the rtl8671b chips. So users of USB or UART BT controllers based on that chip could see problems when trying to connect to and use bluetooth devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1968604/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
Sorry, I'm just not clear on what has been tested. Please could you detail precisely what version of what package has been tested against what version of what kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux-oem-6.1 source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
Also is there any testing being done to ensure that other use cases of alsa-ucm-conf haven't regressed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
I see this is verified against the proposed kernel for Jammy. But Lunar and Kinetic look like they have been tested only against locally patched kernels, rather than the Ubuntu archive. I would expect SRU verifications for hardware enablements to be tested exclusively against the Ubuntu archive before releasing them into -updates. What's the plan for Lunar and Kinetic, please? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: In Progress Status in alsa-ucm-conf source package in Kinetic: Fix Committed Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+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 1964992] Re: ZFS ignores ARC sizes below allmem/32
(and please re-upload when ready - the SRU team won't notice to respond otherwise) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Triaged Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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 1964992] Re: ZFS ignores ARC sizes below allmem/32
As there's been no response, I'm cleaning this up from the queue. This can still be fixed in Focal, but see the comments above on what needs to be resolved first. ** Changed in: zfs-linux (Ubuntu Focal) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Triaged Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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 1995606] Re: Upgrade thermald to 2.5.1
Thank you for the re-upload. I think this remains blocked on answers to my questions in https://lists.ubuntu.com/archives/ubuntu- release/2022-October/005495.html ? ** Changed in: thermald (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For each supported CPU series (RPL/ADL/TGL/CML/CFL/KBL) the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1995606/+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 1981087] Re: thermald prematurely throttling GPU
This SRU remains blocked on https://lists.ubuntu.com/archives/ubuntu- release/2022-October/005495.html. For a straight backport to Jammy, if that is the conclusion, then the upload also needs an SRU meta-bug really to document the justification and regression risk mitigation for the backport. ** Changed in: thermald (Ubuntu Jammy) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Incomplete Bug description: [Impact] * thermald prematurely throttling GPU [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 1964992] Re: ZFS ignores ARC sizes below allmem/32
The correct logic shouldn't be hard to write, unless I'm missing something? So can we just do it right, and as soon as is necessary? If it's obviously correct, I don't think we need to wait for upstream acceptance, but equally it shouldn't take them long to review it either. Because the parameters are well-defined, and the correct validation is unambiguous. So diverging from upstream on the precise fix shouldn't matter as long as it is reviewed to be correct, and that shouldn't be difficult. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Incomplete Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+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 1986852] Update Released
The verification of the Stable Release Update for dmidecode 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 dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1986852 Title: Support SMBIOS 3.4 and 3.5 in Jammy for Hardware Enablement Status in dmidecode package in Ubuntu: Fix Released Status in dmidecode source package in Jammy: Fix Released Status in dmidecode source package in Kinetic: Fix Released Bug description: [Impact] * Support the SMBIOS 3.4 and 3.5 specifications in Jammy to enable new hardware in LTS release per SRU policy [1]. * Backport of 15 relatively simple patches from dmidecode 3.4 in Kinetic to dmidecode 3.3 in Jammy (vs. 49 for full version). * Patches are detailed below. [Test Plan] * Check no regressions on current systems with SMBIOS < 3.4, i.e., no output changes in text and binary form. $ sudo dmidecode > old.txt 2>&1 $ sudo dmidecode --dump-bin old.bin $ apt install dmidecode # modified package $ sudo dmidecode > new.txt 2>&1 $ sudo dmidecode --dump-bin new.bin $ cmp old.txt new.txt; echo $? 0 $ cmp old.bin new.bin; echo $? 0 * Check for expected output on new systems with SMBIOS >= 3.4. $ diff old.txt new.txt ... < # SMBIOS implementations newer than version 3.3.0 are not < # fully supported by this version of dmidecode. ... < Unknown Type < Header and Data: ... > Firmware Inventory Information > Firmware Component Name: BMC Firmware ... < Type: --- > Type: DDR5 ... < Upgrade: --- > Upgrade: Socket LGA4677 ... < Unknown Type < Header and Data: ... > Firmware Inventory Information > Firmware Component Name: BIOS Firmware [Where problems could occur] * Mostly the patches add support for new bits/codes/strings, so there's no changes expected for the old spec support, but some patches lightly change things a little bit (but only one should change a string, as far as I could tell). * So, theoretically, parsers that expect a very precise and constant format/string might have issues *in case* the changes introduced any. (But such tools maybe are already using the binary form anyway, for more detail.) [Other info] * No additional fixes upstream to the included patches. (The git repo's commits have the 'Fixes:' tag usage.) There's only 2 more commits after dmidecode-3-4 now. [Original Description] Backport the support for SMBIOS 3.4 and 3.5 specifications in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3) to enable new hardware in the LTS release per SRU policy [1]. [1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases [Patchset Details] Patches 1-8,10-11 are for SMBIOS 3.4; Patches 9,12-14 are for SMBIOS 3.5; Patch 15 updates supported version. 01: SMBIOS 3.4: add new codes/strings for memory device type 02: SMBIOS 3.4: add new codes/strings for processor socket 03: SMBIOS 3.4: add new codes/strings for slot characteristics 04: SMBIOS 3.4: add new codes/strings for memory device speed [string backward-compatible changes] 05: SMBIOS 3.4: add new codes/strings for slot types [changes append '(U.2)' to 'PCI Express {2,3} SFF-8639' per spec] 06: SMBIOS 3.4: add new codes/strings for processor characteristics 07: SMBIOS 3.4: fix for patches 5-6 08: SMBIOS 3.4: add support for ARM64 Processor ID field based on arch call [string backward-compatible changes] 09: SMBIOS 3.5: add new codes/strings for processor socket 10: SMBIOS 3.4* prep for patch 11 [string backward-compatible changes] 11: SMBIOS 3.4* add new codes/strings for slot types [string backward-compatible changes] 12: SMBIOS 3.5: add new codes/strings for manufacturing mode, pointing devices, onboard devices; introduce slot height 13: SMBIOS 3.5: introduce firmware inventory information (characteristics, state, components 14: SMBIOS 3.5: add new codes/strings for dmi types 15: SMBIOS 3.5: set suppported smbios version to 3.5 (straight from 3.3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
> For focal we can only test the current kernel (hwe-5.15 has not yet picked up the lastest jammy changes because of the upcoming point release) It seems odd to release an SRU without the ability to test what it is fixing. If it turns out not to fix it, we'd have to be doing an SRU again for no good reason. Can this wait until it can be tested properly? -- 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/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+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 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
** Bug watch added: Debian Bug tracker #996104 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996104 ** Also affects: dkms (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996104 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: In Progress Status in dkms package in Debian: Unknown Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries. Found Ubuntu 21.10 (21.10) on /dev/sda2 Found Zorin OS 16 (16) on /dev/sda5 Adding boot menu entry for UEFI Firmware Settings ... done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1963835/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1963835] Re: Message: "Error! Arguments and are not specified." when upgrading
I just hit this. The problem is in /etc/kernel/prerm.d/dkms: Lines 16 and 17: name=`echo "$line" | awk '{print $1}' | sed 's/,$//'` | cut -d'/' -f1 vers=`echo "$line" | awk '{print $1}' | sed 's/,$//'` | cut -d'/' -f2 In my case, $line is: v4l2loopback/0.12.5, 5.13.0-30-generic, x86_64: installed And so it's clear to me that those parsing lines are incorrect and the backticks should be at the end. Looking upstream, I then found: https://github.com/dell/dkms/commit/64a882a32fdf126ef20e6b6403b5cb158dad21f4 So this just needs cherry-picking. ** Changed in: dkms (Ubuntu) Status: Confirmed => In Progress ** Changed in: dkms (Ubuntu) Assignee: (unassigned) => Robie Basak (racb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1963835 Title: Message: "Error! Arguments and are not specified." when upgrading Status in dkms package in Ubuntu: In Progress Bug description: Running pre-release Xubuntu 22.04. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux After upgrading from 21.04 tot 22.04 I did: sudo apt update && sudo apt full-upgrade I saw this message in the output: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v All the output: willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade [sudo] wachtwoord voor willem: Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. 0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 0 niet opgewaardeerd. Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Opwaardering wordt doorgerekend... Klaar De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig: libboost-regex1.74.0 libcmis-0.5-5v5 libdecor-0-0 libextutils-pkgconfig-perl libfftw3-double3 libfuse2 libgtksourceview-3.0-1 libgtksourceview-3.0-common libidn11 libigdgmm11 libneon27-gnutls libperl5.32 libpython3.9 libsdl2-2.0-0 libsource-highlight-common libsource-highlight4v5 linux-headers-5.13.0-30 perl-modules-5.32 pkg-config python3-certifi python3-requests python3-simplejson Gebruik 'sudo apt autoremove' om ze te verwijderen. De volgende pakketten zullen VERWIJDERD worden: linux-headers-5.13.0-30-generic linux-image-5.13.0-30-generic linux-modules-5.13.0-30-generic linux-modules-extra-5.13.0-30-generic 0 opgewaardeerd, 0 nieuw geïnstalleerd, 4 te verwijderen en 0 niet opgewaardeerd. Na deze bewerking zal er 428 MB schijfruimte vrijkomen. Wilt u doorgaan? [J/n] (Database wordt ingelezen ... 402831 bestanden en mappen momenteel geïnstalleerd .) linux-headers-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-extra-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-modules-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ... linux-image-5.13.0-30-generic (5.13.0-30.33) wordt verwijderd ..] /etc/kernel/prerm.d/dkms: dkms: removing: (5.13.0-30-generic) (x86_64) Error! Arguments and are not specified. Usage: remove / or remove -m / or remove -m -v /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.13.0-30-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-18-generic Found initrd image: /boot/initrd.img-5.15.0-18-generic Found linux image: /boot/vmlinuz-5.13.0-32-generic Found initrd image: /boot/initrd.img-5.13.0-32-generic Memtest86+ needs a 16-bit boot, that is not available on EFI, exiting
[Kernel-packages] [Bug 1966432] Re: audio crackling on usb sound card
** Tags added: regression-update -- 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/1966432 Title: audio crackling on usb sound card Status in linux package in Ubuntu: Confirmed Bug description: After the regular updates (on 20.04 and 21.10) audio had crackling noise on the USB audio interface, while it was normal on the internal audio. Tried with different sound cards (presonus audiobox, behringer xenyx q802) and three different machines. Might be in the kernel 5.13.0-37 Reverting to that kernel removed the problem: linux-image-5.13.0-35-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: janina 1338 F pulseaudio /dev/snd/controlC2: janina 1338 F pulseaudio /dev/snd/controlC1: janina 1338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2022-03-03 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: LENOVO 10AHS0LE00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=a8081fc1-6378-4580-9a4a-416e1bead5be ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-37-generic N/A linux-backports-modules-5.13.0-37-generic N/A linux-firmware 1.187.29 RfKill: Tags: focal Uname: Linux 5.13.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/21/2018 dmi.bios.release: 1.226 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTCYAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NOK dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrFBKTCYAUS:bd03/21/2018:br1.226:efr1.13:svnLENOVO:pn10AHS0LE00:pvrThinkCentreM83:rvnLENOVO:rnSHARKBAY:rvrNOK:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuLENOVO_MT_10AH: dmi.product.family: To be filled by O.E.M. dmi.product.name: 10AHS0LE00 dmi.product.sku: LENOVO_MT_10AH dmi.product.version: ThinkCentre M83 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966432/+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 1956855] Re: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.12 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1956855 Title: [SRU] alsa-ucm-conf: Add Realtek 4050 USB Codec profile for a Dell machine Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Released Bug description: [Impact] This Dell machine has dual Realtek 4050 USB Codecs as front and rear codec, the front codec has speaker and headset, the rear codec has line-out audio jack. Without UCM, the pulseaudio can't detect this two usb audio codec and the audio can't work at all. [Fix] Backport a upstream patch, the patch adds the front and rear profiles in the ucm, then pulseaudio will enable all audio devices in this machine. [Test] booting with patched ucm, open the gnome-sound-setting, we could see usb speaker, usb headset and usb lineout, play sound to speaker, headset and lineout, all worked well, record sound via headset, it could record the sound correctly. [Where problems could occur] This SRU adds the new ucm files to a folder, in theory it will not introduce regressions, but It adds a file USB-Audio.conf, it could make other ucm conf files in the USB-Audio folder fail to parse, and make the P620 and WD15/19's audio fail to work, but this possibility is very low, we already tested it and no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956855/+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 1954938] Re: Include the QCA WCN 6856 v2.1 support
It looks like verification is still needed against linux-firmware 1.187.27 in focal-proposed? ** Tags removed: verification-done-focal ** Tags added: verification-needede-focal ** Tags removed: verification-needede-focal ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954938 Title: Include the QCA WCN 6856 v2.1 support Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-firmware source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] WCN685x hw2.1 takes additional/updated firmware for both WiFi and Bluetooth function. ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 [Fix] WCN685x hw2.1 currently shares most WiFi firmware with hw2.0 except for the directory path and a board-2.bin. For Bluetooth, updated revision of qca/nvm_usb_00130201_gf* from mainline are neccessary for Focal. Jammy has all of them already. For kernel, many of the prerequisite works have been committed for hw2.0 in bug 1945154, 1952215 and 1958850. Currently, while WiFi 6G will be turned off for the lack of userspace support, the only fix necessary is to correct read mask of version info register. ath11k 6G band lives in mainline v5.16 and was backported to oem-5.14 in bug 1939528, so only oem-5.14 has to be reverted. [Test Case] WiFi and Bluetooth devices should be up and running, pass basic operations. $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai [Where problems could occur] At the time being, WCN685x WiFi 6G support will be turnef off deliberately due to the lack of full support in the userspace management tools. [Other Info] While this is a new hardware model from OEM program, it's only nominated for Focal oem-5.14 kernel and the coming LTS Jammy. == original bug report == ath11k_pci :71:00.0: BAR 0: assigned [mem 0xa600-0xa61f 64bit] ath11k_pci :71:00.0: enabling device ( -> 0002) ath11k_pci :71:00.0: Unsupported WCN6855 SOC hardware version: 18 17 ath11k_pci: probe of :71:00.0 failed with error -95 $ lspci -nnk|grep -A3 Network :71:00.0 Network controller [0280]: Qualcomm Device [17cb:1103] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e0ce] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci $ lsusb Bus 003 Device 004: ID 0489:e0e3 Foxconn / Hon Hai To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958467] Re: focal linux-firmware package omits amdgpu/navi12 firmware
Can you confirm the package version that was used with proposed enabled please? We've had serious regressions in the past because the version released accidentally did not match the version tested, so I want to make sure that the version I release is the version you tested. Note that this is specified in the request for verification in comment 1, and I've also pointed it out in the past: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039745.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958467 Title: focal linux-firmware package omits amdgpu/navi12 firmware Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Impish: Won't Fix Status in linux-firmware source package in Jammy: Invalid Bug description: [Impact] The 20.04 LTS linux-firmware package list was cut before the amdgpu/navi12* firmware files were upstreamed to the Linux kernel repository, which is unfortunate because this hardware is older than some other included firmware (navi14*), and the firmware is required for using the AMDGPU kernel module on AWS EC2 cloud instances with AMD GPUs. The files are included in 21.04 and 21.10, but to date they have not been included in the LTS hardware-enablement releases for 20.04. It would be helpful to include the navi12 firmware files for the next LTS+HWE release, since 22.04 isn't due out for a while. Without this firmware it is difficult to get AWS EC2 G4ad instances working with Ubuntu, as customers need to manually download and install the firmware from a reputable source and put it into the appropriate directory, which is not the experience they expect on hardware that is over a year old with the most recent HWE release. [Test Case] See above. [Fix] Backport amdgpu/nav12* from linux-firmware Jammy. [Where Problems Could Occur] Graphics problems, kernel crashes on machines with AMD GPU. [Notes] This is required for the HWE kernel so not updating linux-firmware in Impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Hi Jeremy, It's not your fault. This is something your sponsor is supposed to have checked. @Alberto Please could you properly review this, make sure it meets SRU policy, try to anticipate and answer any questions the SRU team might have in advance, and then work with Jeremy to resubmit to the queue? It's not good enough just to sponsor and leave - for example in this case it'd just get lost because Jeremy isn't aware that the upload needs to be resubmitted. You need to stick with your sponsorees all the way through until SRUs land in -updates and no regressions have been found please. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Proposed package upload rejected
An upload of nvidia-settings to impish-proposed has been rejected from the upload queue for the following reason: "See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1957094/comments/12". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Proposed package upload rejected
An upload of nvidia-settings to focal-proposed has been rejected from the upload queue for the following reason: "See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1957094/comments/12". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Proposed package upload rejected
An upload of ubuntu-drivers-common to impish-proposed has been rejected from the upload queue for the following reason: "See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1957094/comments/12". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Proposed package upload rejected
An upload of ubuntu-drivers-common to focal-proposed has been rejected from the upload queue for the following reason: "See https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1957094/comments/12". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1957094] Re: on-demand mode doesn't work with nvidia-390
Missing SRU information: no regression analysis (ie. "Where things go wrong" formerly "Regression Potential"). Please follow https://wiki.ubuntu.com/StableReleaseUpdates#Procedure properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1949329] Update Released
The verification of the Stable Release Update for alsa-lib 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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1940629] Re: Support Jasper Lake
SRU +1 for the current upload in Focal unapproved also, but this is currently blocked on the 20.04.3 freeze. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: In Progress Status in thermald source package in Hirsute: Fix Committed Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+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 1940629] Re: Support Jasper Lake
Unsubscribing sponsors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: In Progress Status in thermald source package in Hirsute: Fix Committed Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+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 1940629] Re: Support Jasper Lake
Hello Andy, or anyone else affected, Accepted thermald into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/2.4.3-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: thermald (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: thermald (Ubuntu Impish) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940629 Title: Support Jasper Lake Status in OEM Priority Project: New Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: In Progress Status in thermald source package in Hirsute: Fix Committed Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on Jasper Lake CPU. * [Test Plan] * Use a machine with a Jasper Lake cpu. * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware. [Other Info] * https://github.com/intel/thermal_daemon/issues/309 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940629/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.38.1-3ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-settings-daemon (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias:
[Kernel-packages] [Bug 1926062] Please test proposed package
Hello Jatin, or anyone else affected, Accepted gnome-settings-daemon into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-settings- daemon/3.36.1-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06
[Kernel-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
Hello Andy, or anyone else affected, Accepted bluez into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.56-0ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: bluez (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-hirsute ** Changed in: bluez (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Please test proposed package
Hello Andy, or anyone else affected, Accepted bluez into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in bluez source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
> Declaring "Fix Committed" when a fix exists in an upstream tributary before anything has reached proposed is a procedure requested by seb128 and we now follow on the desktop team. I'm not sure what you mean by "upstream tributary", but if the fix exists in the main Ubuntu packaging branch used by the desktop team (ie. Vcs-Git in debian/control points to it) then that makes sense, as it was in this case. If you mean it's just fixed upstream somewhere, then that doesn't make sense - Launchpad's bug tracker expects to have a separate task to track upstream status if you want that. However, from an SRU perspective, I would expect an upload to the development release *before* an SRU is uploaded. Sometimes we make concessions (eg. during a development release freeze), but I don't think a sponsorship delay qualifies. The sponsor should be able to sponsor to the development release first, so there's no reason not to do it. I see it's there now, but please could you adjust your processes to make sure that in the normal case, this happens? This would save me reviewing the SRU twice. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Unknown Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
See bug 1926062 for previous SRU review. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
The fix for this seems missing in Impish. What does "Fix Committed" mean here? What are your plans to fix this in Impish? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Also, the current upload references bug 1933221 which is a dupe. I'm not sure how SRU tooling will handle this. Unless you can confirm that it will work, please could you reference the master bug in your upload instead? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+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 1930921] Re: Apache 2.4.41 corrupts files from samba share
Thank you for taking the time to report this bug and helping to make Ubuntu better. I'll leave any security assessment and security-based prioritisation for the security team. >From a non-security perspective, I think this is of low priority since it only affects an unusual end-user configuration that is likely to affect only a very small minority of users. Feel free to continue to use this bug to track the problem, but I do not expect anyone else to spend time looking into this soon. -- 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/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: New Status in linux package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+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 1918013] Re: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi, 3-model-b.txt lib/firmware/brcm/b
Since this bug is a packaging issue being fixed in this SRU, it needs SRU information documented please, and should be verified as part of the SRU being landed. Please also triage other similar-looking package conflicts such as bug 1691729 and bug 1927240. I assume these are covered already so am not blocking this SRU landing in -proposed but someone ought to verify that before landing all the new diversions into -updates. I'd also like you to look at bug 1927711 please, but again I don't think this should be a blocker right now. However if this situation occurs again I think it'd be appropriate to do it before landing a further SRU with further diversions. ** Description changed: + [SRU Information] + + Needs completing. See comment 5 below. + + [Original Description] + Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): - trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is + trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: dad1239 F pulseaudio - /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio - /dev/snd/controlC0: dad1239 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: dad1239 F pulseaudio + /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio + /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: - + ErrorMessage: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 ImageMediaBuild: 20210302 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 vc_sm_cma Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: ** Changed in: linux-firmware-raspi2 (Ubuntu Groovy) Status: New => Fix Committed -- 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/1918013 Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-raspi2 package in Ubuntu: Fix Released Status in linux-firmware-raspi2 source package in Focal: Fix Committed Status in linux-firmware-raspi2 source package in
[Kernel-packages] [Bug 1918013] Please test proposed package
Hello fossfreedom, or anyone else affected, Accepted linux-firmware-raspi2 into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /linux-firmware-raspi2/4-0ubuntu0~20.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware-raspi2 (Ubuntu Focal) Status: New => Fix Committed -- 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/1918013 Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-raspi2 package in Ubuntu: Fix Released Status in linux-firmware-raspi2 source package in Focal: Fix Committed Status in linux-firmware-raspi2 source package in Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware-raspi2 source package in Hirsute: Fix Released Bug description: [SRU Information] Needs completing. See comment 5 below. [Original Description] Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad1239 F pulseaudio /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: ErrorMessage: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 ImageMediaBuild: 20210302 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 vc_sm_cma Title: package linux-firmware 1.194 [modified:
[Kernel-packages] [Bug 1918013] Please test proposed package
Hello fossfreedom, or anyone else affected, Accepted linux-firmware-raspi2 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /linux-firmware-raspi2/4-0ubuntu0~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1918013 Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] failed to install/upgrade: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-raspi2 package in Ubuntu: Fix Released Status in linux-firmware-raspi2 source package in Focal: Fix Committed Status in linux-firmware-raspi2 source package in Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Invalid Status in linux-firmware-raspi2 source package in Hirsute: Fix Released Bug description: [SRU Information] Needs completing. See comment 5 below. [Original Description] Upgrade error Unpacking linux-firmware (1.195) over (1.194) ... dpkg: error processing archive /tmp/apt-dpkg-install-N6i2Cp/86-linux-firmware_1. 195_all.deb (--unpack): trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 update-initramfs: Generating /boot/initrd.img-5.8.0-1017-raspi ProblemType: Package DistroRelease: Ubuntu 21.04 Package: linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt lib/firmware/brcm/brcmfmac43455-sdio.bin lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt] ProcVersionSignature: Ubuntu 5.8.0-1017.20+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1017-raspi aarch64 ApportVersion: 2.20.11-0ubuntu59 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dad1239 F pulseaudio /dev/snd/pcmC1D0p: dad1239 F...m pulseaudio /dev/snd/controlC0: dad1239 F pulseaudio CasperMD5CheckResult: unknown Date: Sat Mar 6 14:59:23 2021 Dependencies: ErrorMessage: trying to overwrite '/lib/firmware/brcm/brcmfmac43455-sdio.clm_blob', which is also in package linux-firmware-raspi2 3-0ubuntu2 ImageMediaBuild: 20210302 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcFB: 0 vc4drmfb ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.1-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux-firmware StagingDrivers: bcm2835_v4l2 bcm2835_isp bcm2835_codec bcm2835_mmal_vchiq snd_bcm2835 vc_sm_cma Title: package linux-firmware 1.194 [modified: lib/firmware/brcm/brcmfmac43430-sdio.bin lib/firmware/brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt
[Kernel-packages] [Bug 1922242] Re: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239
Hello Kleber, or anyone else affected, Accepted openafs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openafs/1.6.15-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openafs (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1922242 Title: openafs/1.6.15-1ubuntu1 ADT test failure with linux/4.4.0-207.239 Status in linux package in Ubuntu: Invalid Status in openafs package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in openafs source package in Xenial: Fix Committed Bug description: [Impact] autopkgtest caught a build failure with openafs-modules-dkms with the xenial/linux kernel currently in -proposed (4.4.0-207.239). Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/o/openafs/20210331_082652_48bc3@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/o/openafs/20210331_001828_facc7@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/o/openafs/20210331_001310_48c45@/log.gz Build error: CC [M] /var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.o /var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c: In function ‘osi_UFSTruncate’: /var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-207-generic-SP/osi_file.c:187:12: error: implicit declaration of function ‘inode_change_ok’ [-Werror=implicit-function-declaration] code = inode_change_ok(inode, ); ^ cc1: some warnings being treated as errors This was caused by commit "fs: Give dentry to inode_change_ok() instead of inode" applied to xenial/linux as part of the fixes for CVE-2015-1350, which renamed inode_change_ok() to setattr_prepare(). [Fix] The proposed fix is to cherry-pick commit 8aeb711eeaa5ddac5a74c354091e2d4f7ac0cd63 "Linux 4.9: inode_change_ok() becomes setattr_prepare()" from openafs repository (git://git.openafs.org/openafs.git). [Test] Install openafs-modules-dkms on a xenial system running an older kernel without the interface change (<4.4.0-207) and with a newer kernel with the interface change (>=4.4.0-207). The openafs module should be built and loaded with all kernels. [Where problems could occur] The fix is based on the detection made during build time of the function available on the kernel headers. If the detection doesn't work correctly the build would fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922242/+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 1908677] Re: Dell Latitude 9510 capture volume is too low
Hello Kai-Chuan, or anyone else affected, Accepted alsa-ucm-conf into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: [Impact] * The internal mic default volume is too low A upstream commit correct the init configuration [Test Case] * Using gnome-sound-recoder to record audio without tweak capture volume The volume is very low * Try to update the init.conf mentioned by https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e $ alsactl init $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 * Using gnome-sound-recorder to record again The volume is significantly improved [Where problems could occur] * The change only apply to the hardware with rt715 codec. + * [racb] Is there any other hardware that isn't being tested that uses + this codec? + * The change adjust the volume only, but not change other control, the worst case is the change doesn't take effect. [Other Info] * The change has been verified on Latitude 9510. ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1908677 Title: Dell Latitude 9510 capture volume is too low Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Bug description: [Impact] * The internal mic default volume is too low A upstream commit correct the init configuration [Test Case] * Using gnome-sound-recoder to record audio without tweak capture volume The volume is very low * Try to update the init.conf mentioned by https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e $ alsactl init $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 * Using gnome-sound-recorder to record again The volume is significantly improved [Where problems could occur] * The change only apply to the hardware with rt715 codec. * [racb] Is there any other hardware that isn't being tested that uses this codec? * The change adjust the volume only, but not change other control, the worst case is the change doesn't take effect. [Other Info] * The change has been verified on Latitude 9510. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+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 1908677] Please test proposed package
Hello Kai-Chuan, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1908677 Title: Dell Latitude 9510 capture volume is too low Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Committed Bug description: [Impact] * The internal mic default volume is too low A upstream commit correct the init configuration [Test Case] * Using gnome-sound-recoder to record audio without tweak capture volume The volume is very low * Try to update the init.conf mentioned by https://github.com/alsa-project/alsa-ucm-conf/commit/263bd26b1216c933db3d216197a78678d0f8610e $ alsactl init $ amixer cget name='rt715 ADC 07 Capture Volume' numid=14,iface=MIXER,name='rt715 ADC 07 Capture Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0 : values=58,58 | dBscale-min=-17.25dB,step=0.75dB,mute=0 * Using gnome-sound-recorder to record again The volume is significantly improved [Where problems could occur] * The change only apply to the hardware with rt715 codec. * [racb] Is there any other hardware that isn't being tested that uses this codec? * The change adjust the volume only, but not change other control, the worst case is the change doesn't take effect. [Other Info] * The change has been verified on Latitude 9510. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1908677/+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 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing
The Hirsute fix is in hirsute-proposed. ** Changed in: dkms (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1915051 Title: dkms-autopkgtest: Also select binary packages that depends on dkms for testing Status in dkms package in Ubuntu: Fix Committed Status in dkms source package in Focal: Fix Committed Status in dkms source package in Groovy: Fix Committed Status in dkms source package in Hirsute: Fix Committed Bug description: [Impact] The current version of dkms-autopkgtest in 20.04 and later only selects binary packages with names ending with "-dkms" for its automatic DKMS test. With that packages suchs bcml-kernel-source and nvidia drivers are not being tested automatically by autopkgtest. [Test Case] Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom- 0ubuntu5) and the 5.8 kernel and even with this version of the driver failing to build with the 5.8 kernel, the test succeeds. The expected behavior, is that that dkms-autopkgtest should fail in this case. [Where problems could occur] The main issue that we can have here is selecting additional packages for the DKMS test that are not DKMS packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051/+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 1915051] Re: dkms-autopkgtest: Also select binary packages that depends on dkms for testing
Hello Marcelo, or anyone else affected, Accepted dkms into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.8.3-4ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dkms (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: dkms (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1915051 Title: dkms-autopkgtest: Also select binary packages that depends on dkms for testing Status in dkms package in Ubuntu: Fix Committed Status in dkms source package in Focal: Fix Committed Status in dkms source package in Groovy: Fix Committed Status in dkms source package in Hirsute: Fix Committed Bug description: [Impact] The current version of dkms-autopkgtest in 20.04 and later only selects binary packages with names ending with "-dkms" for its automatic DKMS test. With that packages suchs bcml-kernel-source and nvidia drivers are not being tested automatically by autopkgtest. [Test Case] Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom- 0ubuntu5) and the 5.8 kernel and even with this version of the driver failing to build with the 5.8 kernel, the test succeeds. The expected behavior, is that that dkms-autopkgtest should fail in this case. [Where problems could occur] The main issue that we can have here is selecting additional packages for the DKMS test that are not DKMS packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051/+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 1915051] Please test proposed package
Hello Marcelo, or anyone else affected, Accepted dkms into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.8.1-5ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1915051 Title: dkms-autopkgtest: Also select binary packages that depends on dkms for testing Status in dkms package in Ubuntu: Fix Committed Status in dkms source package in Focal: Fix Committed Status in dkms source package in Groovy: Fix Committed Status in dkms source package in Hirsute: Fix Committed Bug description: [Impact] The current version of dkms-autopkgtest in 20.04 and later only selects binary packages with names ending with "-dkms" for its automatic DKMS test. With that packages suchs bcml-kernel-source and nvidia drivers are not being tested automatically by autopkgtest. [Test Case] Run autopkgtest in Focal for bcmwl-kernel-source (6.30.223.271+bdcom- 0ubuntu5) and the 5.8 kernel and even with this version of the driver failing to build with the 5.8 kernel, the test succeeds. The expected behavior, is that that dkms-autopkgtest should fail in this case. [Where problems could occur] The main issue that we can have here is selecting additional packages for the DKMS test that are not DKMS packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1915051/+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 1913187] Re: iproute2 segfaults when filtering sockets
Hello Rafael, or anyone else affected, Accepted iproute2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iproute2/4.15.0-2ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iproute2 (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [Impact] * The ss tool crashes when a query returns no results (seg fault) [Test Case] * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 Segmentation fault * PPA with the fix: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187 [Where problems could occur] * The ss tool is impacted and it has its code changed for the fix. * The fix is a clean cherry-pick and straightforward (moving declaration after a NULL check). [Other Info] When in Ubuntu Bionic, if one calls: $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 tcp 00 127.0.0.1:58910 127.0.0.1:22 users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0) it works. Just like when in Groovy: $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 tcp 00 127.0.0.1:58908 127.0.0.1:22 users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0) but.. if there is nothing to show, in Bionic we get a segfault: $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] Re: iproute2 segfaults when filtering sockets
** Merge proposal linked: https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+merge/396921 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1913187 Title: iproute2 segfaults when filtering sockets Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Confirmed Bug description: [Impact] * The ss tool crashes when a query returns no results (seg fault) [Test Case] * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 Segmentation fault * PPA with the fix: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187 [Where problems could occur] * The ss tool is impacted and it has its code changed for the fix. * The fix is a clean cherry-pick and straightforward (moving declaration after a NULL check). [Other Info] When in Ubuntu Bionic, if one calls: $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 tcp 00 127.0.0.1:58910 127.0.0.1:22 users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0) it works. Just like when in Groovy: $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 tcp 00 127.0.0.1:58908 127.0.0.1:22 users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0) but.. if there is nothing to show, in Bionic we get a segfault: $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1847105] Re: very slow disk creation, snapshotting
Hello Andreas, or anyone else affected, Accepted virt-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/virt- manager/1:2.2.1-3ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: virt-manager (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in virt-manager source package in Focal: Fix Committed Status in libvirt source package in Groovy: Triaged Bug description: [Impact] * The defaults of virt-manager for disk allocation always worked fine when qcow2 had nothing but sparse support. So sparse=True vs sparse=False made no difference. So it always set sparse=False. Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it, which is not the intention. * For upgraders from pre-Focal this was a regression in two ways: a) allocation of qcow changed to non-sparse (fallocate based) potentially consuming more space b) depending on the underlying FS this made the allocation much slower * Fix by applying the upstream change that Defaults to sparse when requested format isn't raw (for raw the assumption ill stay that users do that for runtime performance, so non-sparse on those stays as-is) [Test Case] * open virt-manager and create a new guest which includes creating a new image for it * when clicking "finish" the image will be created (which e.g. on ZFS will take quite some time) * In the background grep ps output if the qemu-img call for qcow (the default) is using "preallocation=fallocate" (wrong) or "preallocation=metadata" (correct) [Regression Potential] * For upgraders from pre-focal it actually ensures behavior stays as is (no change/regression there) * For users of ZFS where the allocation was slow it fixes this slowness. * But for people using Focal all the time and on non-ZFS there will be a behavior change in no more doing falloc pre-allocating the qemu image. To be cleear there are four modes: 1. no allocation 2. metadata allocation - is initially larger but can improve performance when the image needs to grow 3. falloc - preallocates space for image by calling posix_fallocate 4. full - writes data to the underlying storage The fix changes the default from 3->2 which it always was and should be. As the patch says: "If users want to override it, they can do it via custom created storage." (To be clear, upstream changed this as we fixed it here, so on further upgrades what we apply here will be the behavior anyway, it seems wrong to keep Focal the only one in between kept different) * [racb] The code path being added special cases the 'raw' format and in handling of the default sparse setting. Areas of potential regression are therefore in the handling of the default and override of the default in the cases of both 'raw' and not 'raw'. [Other Info] * The slowness effect
[Kernel-packages] [Bug 1887490] Re: Add/Backport EPYC-v3 and EPYC-Rome CPU model
Hello Markus, or anyone else affected, Accepted qemu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: qemu (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags removed: verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Fix Committed Bug description: ## Qemu SRU ## [Impact] * CPU definitions are added to qemu as these CPUs are known. And due to that over time are missing in former releases. * To really benefit from the new features of these chips they have to be known, therefore new type additions done by upstream should be backported if they generally apply and do not depend on SRU-critical changes. * This backports two upstream fixes that just add definitions (no control flow changes) [Test Case] * Probe qemu for the known CPU types (works on all HW) $ qemu-system-x86_64 -cpu ? | grep EPYC Focal without fix: x86 EPYC (alias configured by machine type) x86 EPYC-IBPB (alias of EPYC-v2) x86 EPYC-v1 AMD EPYC Processor x86 EPYC-v2 AMD EPYC Processor (with IBPB) Focal with fix also adds: x86 EPYC-Rome (alias configured by machine type) x86 EPYC-Rome-v1 AMD EPYC-Rome Processor x86 EPYC-v3 AMD EPYC Processor * Given such HW is available start a KVM guest using those new types Since we don't have libvirt support (yet) do so directly in qemu commandline like (bootloader is enough) $ qemu-system-x86_64 -cpu EPYC-Rome -machine pc-q35-focal,accel=kvm -nographic $ qemu-system-x86_64 -cpu EPYC-v3 -machine pc-q35-focal,accel=kvm -nographic [Regression Potential] * This adds new CPU types to the list of known CPUs defining their name and features. Generally the changes are contained to those new types and only active when selected - and usually only selectable on such new machines. Therefore not a lot should change for other users. One thing thou, if a user selected an unversioned type (which in this case only can be "EPYC") by default it will pick the latest subversion that applies. In this case the behavior will change and pick EPYC-v3 after the fix. But this is the whole purpose of versioned (stay as is) and unversioned (move with updates) CPU types - so that should be ok. The EPYC-Rome type didn't exist in Focal before, so it can't "change" for users. [Other Info] * Depends on the new kernel 5.4.0-49 or later (Currently in focal-proposed) --- Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
As you explained I acknowledge that we are changing behaviour in Focal here, but I agree with you that this is the least worst option. ** Description changed: [Impact] - * The defaults of virt-manager for disk allocation always worked fine -when qcow2 had nothing but sparse support. So sparse=True vs -sparse=False made no difference. So it always set sparse=False. -Then qcow2 grows non-sparse support, and virt-manager is suddenly -defaulting to it, which is not the intention. + * The defaults of virt-manager for disk allocation always worked fine + when qcow2 had nothing but sparse support. So sparse=True vs + sparse=False made no difference. So it always set sparse=False. + Then qcow2 grows non-sparse support, and virt-manager is suddenly + defaulting to it, which is not the intention. + * For upgraders from pre-Focal this was a regression in two ways: + a) allocation of qcow changed to non-sparse (fallocate based) + potentially consuming more space + b) depending on the underlying FS this made the allocation much + slower - * For upgraders from pre-Focal this was a regression in two ways: - a) allocation of qcow changed to non-sparse (fallocate based) -potentially consuming more space - b) depending on the underlying FS this made the allocation much -slower - - * Fix by applying the upstream change that Defaults to sparse when -requested format isn't raw (for raw the assumption ill stay that -users do that for runtime performance, so non-sparse on those stays -as-is) + * Fix by applying the upstream change that Defaults to sparse when + requested format isn't raw (for raw the assumption ill stay that + users do that for runtime performance, so non-sparse on those stays + as-is) [Test Case] - * open virt-manager and create a new guest which includes creating a -new image for it -* when clicking "finish" the image will be created (which e.g. on ZFS - will take quite some time) -* In the background grep ps output if the qemu-img call for qcow (the - default) is using "preallocation=fallocate" (wrong) or - "preallocation=metadata" (correct) + * open virt-manager and create a new guest which includes creating a + new image for it + * when clicking "finish" the image will be created (which e.g. on ZFS + will take quite some time) + * In the background grep ps output if the qemu-img call for qcow (the + default) is using "preallocation=fallocate" (wrong) or + "preallocation=metadata" (correct) [Regression Potential] - * For upgraders from pre-focal it actually ensures behavior stays as is -(no change/regression there) - * For users of ZFS where the allocation was slow it fixes this -slowness. - * But for people using Focal all the time and on non-ZFS there will be -a behavior change in no more doing falloc pre-allocating the qemu -image. To be cleear there are four modes: -1. no allocation -2. metadata allocation - is initially larger but can improve - performance when the image needs to grow -3. falloc - preallocates space for image by calling posix_fallocate -4. full - writes data to the underlying storage -The fix changes the default from 3->2 which it always was and should -be. As the patch says: "If users want to override it, they can -do it via custom created storage." -(To be clear, upstream changed this as we fixed it here, so on - further upgrades what we apply here will be the behavior anyway, it - seems wrong to keep Focal the only one in between kept different) + * For upgraders from pre-focal it actually ensures behavior stays as is + (no change/regression there) + * For users of ZFS where the allocation was slow it fixes this + slowness. + * But for people using Focal all the time and on non-ZFS there will be + a behavior change in no more doing falloc pre-allocating the qemu + image. To be cleear there are four modes: + 1. no allocation + 2. metadata allocation - is initially larger but can improve + performance when the image needs to grow + 3. falloc - preallocates space for image by calling posix_fallocate + 4. full - writes data to the underlying storage + The fix changes the default from 3->2 which it always was and should + be. As the patch says: "If users want to override it, they can + do it via custom created storage." + (To be clear, upstream changed this as we fixed it here, so on + further upgrades what we apply here will be the behavior anyway, it + seems wrong to keep Focal the only one in between kept different) + * [racb] The code path being added special cases the 'raw' format and in handling of the default sparse setting. Areas of potential regression are therefore in the handling of the default and override of the default in the cases of both 'raw' and not
[Kernel-packages] [Bug 1847105] Re: very slow disk creation, snapshotting
** Tags added: focal regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847105 Title: very slow disk creation, snapshotting Status in virt-manager: Fix Released Status in Native ZFS for Linux: New Status in libvirt package in Ubuntu: Triaged Status in virt-manager package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in libvirt source package in Bionic: Invalid Status in virt-manager source package in Bionic: Invalid Status in zfs-linux source package in Bionic: Won't Fix Status in libvirt source package in Disco: Won't Fix Status in virt-manager source package in Disco: Won't Fix Status in zfs-linux source package in Disco: Won't Fix Status in libvirt source package in Focal: Triaged Status in libvirt source package in Groovy: Triaged Bug description: [Impact] * The defaults of virt-manager for disk allocation always worked fine when qcow2 had nothing but sparse support. So sparse=True vs sparse=False made no difference. So it always set sparse=False. Then qcow2 grows non-sparse support, and virt-manager is suddenly defaulting to it, which is not the intention. * For upgraders from pre-Focal this was a regression in two ways: a) allocation of qcow changed to non-sparse (fallocate based) potentially consuming more space b) depending on the underlying FS this made the allocation much slower * Fix by applying the upstream change that Defaults to sparse when requested format isn't raw (for raw the assumption ill stay that users do that for runtime performance, so non-sparse on those stays as-is) [Test Case] * open virt-manager and create a new guest which includes creating a new image for it * when clicking "finish" the image will be created (which e.g. on ZFS will take quite some time) * In the background grep ps output if the qemu-img call for qcow (the default) is using "preallocation=fallocate" (wrong) or "preallocation=metadata" (correct) [Regression Potential] * For upgraders from pre-focal it actually ensures behavior stays as is (no change/regression there) * For users of ZFS where the allocation was slow it fixes this slowness. * But for people using Focal all the time and on non-ZFS there will be a behavior change in no more doing falloc pre-allocating the qemu image. To be cleear there are four modes: 1. no allocation 2. metadata allocation - is initially larger but can improve performance when the image needs to grow 3. falloc - preallocates space for image by calling posix_fallocate 4. full - writes data to the underlying storage The fix changes the default from 3->2 which it always was and should be. As the patch says: "If users want to override it, they can do it via custom created storage." (To be clear, upstream changed this as we fixed it here, so on further upgrades what we apply here will be the behavior anyway, it seems wrong to keep Focal the only one in between kept different) [Other Info] * The slowness effect might be further mitigated by ZFS implementing more falloc options (thanks Richard for that hint) but that won't be in Focal. This is a regression in eoan for me. I use virt-manager to create vms, and I noticed that creating one now takes more than a minute. Looking at the process listing while the backing disk is being created, I see this qemu-img command line: 15658 ?Ssl0:00 /usr/sbin/libvirtd 23726 ?Sl 0:04 \_ /usr/bin/qemu-img create -f qcow2 -o preallocation=falloc,compat=1.1,lazy_refcounts /var/lib/libvirt/images/live-server.qcow2 41943040K If I run qemu-img with that preallocation parameter set, even on bionic, then it also takes a very long time. On eoan, for comparison: andreas@nsn7:~$ time qemu-img create -f qcow2 no-prealloc-image.qcow2 40G Formatting 'no-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 lazy_refcounts=off refcount_bits=16 real 0m0,016s user 0m0,010s sys 0m0,006s andreas@nsn7:~$ qemu-img info no-prealloc-image.qcow2 image: no-prealloc-image.qcow2 file format: qcow2 virtual size: 40G (42949672960 bytes) disk size: 17K cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false andreas@nsn7:~$ du -hs no-prealloc-image.qcow2 17K no-prealloc-image.qcow2 andreas@nsn7:~$ and now with preallocation=falloc: andreas@nsn7:~$ time qemu-img create -f qcow2 -o preallocation=falloc with-prealloc-image.qcow2 40G Formatting 'with-prealloc-image.qcow2', fmt=qcow2 size=42949672960 cluster_size=65536 preallocation=falloc
[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Hello You-Sheng, or anyone else affected, Accepted apport into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.17 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Committed Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: Updated Description to match SRU requirements for bionic [Impact] linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. [Test Case] 1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. [Regression Potential] Very limited, as we are just adding a symlink from linux-firmware to the linux source package hook. this change has been available in Focal and Groovy without problem Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type:
[Kernel-packages] [Bug 1888405] Re: zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols
Hello James, or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1888405 Title: zfsutils-linux: zfs-volume-wait.service fails with locked encrypted zvols Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification Focal == When an encrypted zvol is locked the zfs-volume-wait service does not start. The /sbin/zvol_wait should not wait for links when the volume has property keystatus=unavailable. == Fix == The attached patch in comment #1. == Test == lock an encrypted zvol. without the fix the volume wait will block the boot. with the fix it is not blocked. == Regression Potential == Limited to zvol wait - this change affects just the encrypted vols checking. - I was doing some experimentation with encrypted zvols and observed that the zfs-volume-wait.service systemd unit does not start if the encrypted zvol is locked. The /sbin/zvol_wait should not wait for links when the volume has property keystatus=unavailable. The attached patch seems to resolve the issue for me. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.2 Version table: 0.8.3-1ubuntu12.2 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 0.8.3-1ubuntu12.1 100 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1888405/+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 1886234] Re: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Am I right in understanding that this is a host kernel oops? My understanding of PCIe passthrough is that if you're passing through your sound card to a VM then the host kernel's sound driver should never crash, so this sounds like a kernel bug to me. My reasoning is that either the host kernel should not permit passthrough if the sound driver is using the card, or it should correctly reset the card before taking it over again afterwards. If this is wrong then presumably this is a qemu bug? For people who know more about this area, feel free to explain and reassign. But to make progress for now, I'm reassigning this bug to the kernel. ** Package changed: libvirt (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886234 Title: libvirtd Tainted: kobject_add_internal failed for emu10k1-synth-0-1 with -EEXIST, don't try to register things with the same name in the same directory. Status in linux package in Ubuntu: New Bug description: After passing through the PCIe card EMU 1212m to a VM (kvm/qemu) and turning the VM off, I see this in dmesg: [ 4675.188761] snd_emu10k1 :05:04.0: non-passthrough IOMMU detected, widening DMA allocations [ 4675.188874] snd_emu10k1 :05:04.0: emu1010: Special config. [ 4675.189019] snd_emu10k1 :05:04.0: emu1010: EMU_HANA_ID = 0x3f [ 4680.350820] snd_emu10k1 :05:04.0: emu1010: Hana Firmware loaded [ 4680.350878] snd_emu10k1 :05:04.0: emu1010: Hana version: 1.6 [ 4680.350948] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.350977] snd_emu10k1 :05:04.0: emu1010: Card options = 0x1 [ 4680.351583] snd_emu10k1 :05:04.0: emu1010: Card options3 = 0x1 [ 4680.377334] snd_emu10k1 :05:04.0: Audigy2 value: Special config. [ 4680.377972] snd_emu10k1 :05:04.0: EMU outputs on [ 4680.377972] snd_emu10k1 :05:04.0: EMU2 inputs on [ 4680.392669] sysfs: cannot create duplicate filename '/devices/pci:00/:00:01.2/:02:00.0/:03:02.0/:04:00.0/:05:04.0/sound/card0/emu10k1-synth-0-1' [ 4680.392672] CPU: 10 PID: 5204 Comm: libvirtd Tainted: G OE 5.4.0-40-generic #44-Ubuntu [ 4680.392673] Hardware name: System manufacturer System Product Name/ROG STRIX X570-E GAMING, BIOS 1409 05/12/2020 [ 4680.392674] Call Trace: [ 4680.392681] dump_stack+0x6d/0x9a [ 4680.392684] sysfs_warn_dup.cold+0x17/0x35 [ 4680.392685] sysfs_create_dir_ns+0xb8/0xd0 [ 4680.392687] kobject_add_internal+0xbd/0x2b0 [ 4680.392688] kobject_add+0x7e/0xb0 [ 4680.392692] device_add+0x132/0x6b0 [ 4680.392696] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392702] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392706] snd_device_register_all+0x33/0x50 [snd] [ 4680.392709] snd_card_register+0x62/0x1b0 [snd] [ 4680.392712] ? snd_hwdep_new+0xfe/0x146 [snd_hwdep] [ 4680.392715] snd_emux_init_hwdep+0xa0/0xd0 [snd_emux_synth] [ 4680.392717] snd_emux_register+0x11a/0x190 [snd_emux_synth] [ 4680.392719] ? 0xc1065000 [ 4680.392721] ? sf_sample_new+0x20/0x20 [snd_emux_synth] [ 4680.392723] snd_emu10k1_synth_probe+0x108/0x1a0 [snd_emu10k1_synth] [ 4680.392725] really_probe+0x2b3/0x3e0 [ 4680.392726] driver_probe_device+0xbc/0x100 [ 4680.392728] __device_attach_driver+0x71/0xd0 [ 4680.392729] ? driver_allows_async_probing+0x50/0x50 [ 4680.392731] bus_for_each_drv+0x84/0xd0 [ 4680.392732] __device_attach+0xe1/0x160 [ 4680.392734] device_initial_probe+0x13/0x20 [ 4680.392735] bus_probe_device+0x8f/0xa0 [ 4680.392737] device_add+0x3c7/0x6b0 [ 4680.392740] ? __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392742] snd_seq_device_dev_register+0x1c/0x60 [snd_seq_device] [ 4680.392745] __snd_device_register.part.0+0x1f/0x30 [snd] [ 4680.392748] snd_device_register_all+0x33/0x50 [snd] [ 4680.392751] snd_card_register+0x62/0x1b0 [snd] [ 4680.392753] ? snd_seq_device_new+0xd0/0x126 [snd_seq_device] [ 4680.392758] snd_card_emu10k1_probe+0x30f/0x400 [snd_emu10k1] [ 4680.392761] local_pci_probe+0x48/0x80 [ 4680.392763] pci_device_probe+0x10f/0x1b0 [ 4680.392765] really_probe+0x159/0x3e0 [ 4680.392766] driver_probe_device+0xbc/0x100 [ 4680.392767] __device_attach_driver+0x71/0xd0 [ 4680.392769] ? driver_allows_async_probing+0x50/0x50 [ 4680.392770] bus_for_each_drv+0x84/0xd0 [ 4680.392771] __device_attach+0xe1/0x160 [ 4680.392773] device_attach+0x10/0x20 [ 4680.392775] bus_rescan_devices_helper+0x39/0x80 [ 4680.392777] drivers_probe_store+0x36/0x60 [ 4680.392778] bus_attr_store+0x27/0x30 [ 4680.392780] sysfs_kf_write+0x3e/0x50 [ 4680.392782] kernfs_fop_write+0xda/0x1b0 [ 4680.392784] __vfs_write+0x1b/0x40 [ 4680.392785] vfs_write+0xb9/0x1a0 [
[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake
This is blocked on someone writing a test case as requested by Łukasz in comment 10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1874933 Title: Performance workaround for Dell 7390 2-in-1 Ice Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Incomplete Bug description: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == As reported here: https://www.phoronix.com/forums/forum/linux- graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice- lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream == Regression Potential == This fix involves changing the power limits logic so there is a potential that this may affect change the throttling behaviour of other systems with poorly defined PPCC power tables because it now ignores the power limits less than the power up limits. Users will see their machines run faster and hence active cooling may crank up (e.g. fans) but I think the speed improvement outweighs the noise factor. Note that these changes are already in thermald 2.1 that is now in Ubuntu Groovy 20.10. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1874933/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Here's the change that was made: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/zesty/commit/?id=a87ae50beda8c46c543b39e19070549cf355eb65 It's just the default of the consoleblank= kernel parameter. You can override it by specifying that parameter to the kernel at boot time (eg. via /etc/default/grub) If someone could test and document exact steps to do this override in this bug please, that'd be useful to users and I'd appreciate it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 1767568] Re: Console DPMS is not enabled by default in Ubuntu Server 18.04
> I understand that the original reporter said that he got it working with setterm, but as by convention these bug reports often require verification from others in order to get any attention, it seems only reasonable that after many have said that the DPMS power saving is what is not working, while simple blanking and leaving the monitor on is what is currently happening, that this bug should not have been marked invalid. I disagree. The reporter accidentally conflated DPMS with the intentional screen blanking change we made. This muddles every subsequent comment. As the reporter said that the problem was resolved, clearly it is the bug subject that was mistaken. The bug status is correct for the original problem the reporter had intended to report. If instead you think the reporter thought they were reporting was actually something else, and the bug subject was correct, then I guess that's self-consistent and you're entitled to think that, but this is only going to lead to further confusion. I suggest you file a separate bug if you think that there is a bug in DPMS. Please make sure to use an appropriate bug subject and a clear explanation in the bug description (steps to reproduce, expected behaviour, actual behaviour, etc) and then hopefully there will be clarity on exactly what you are reporting and then the community can determine the correct status of your issue as any outcome emerges. ** Summary changed: - Console DPMS is not enabled by default in Ubuntu Server 18.04 + Console blanking is not enabled by default in Ubuntu Server 18.04 -- 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/1767568 Title: Console blanking is not enabled by default in Ubuntu Server 18.04 Status in linux package in Ubuntu: Invalid Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor:
[Kernel-packages] [Bug 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor
I was still running your good test kernel: (actual kernel package appeared autoremoved) 4.15.0-66-generic #75~lp1845810 noise level low Upgrading to bionic-updates: 4.15.0-70.79 4.15.0-70-generic #79-Ubuntu noise level high (as expected, bug not yet fixed) Upgrading to bionic-proposed: 4.15.0-71.80 4.15.0-71-generic #80-Ubuntu noise level low (bug appears fixed) I also checked general audio playback on the bionic-proposed kernel (4.15.0-71.80 4.15.0-71-generic #80-Ubuntu) and that also seems fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic
[Kernel-packages] [Bug 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor
@kaihengfeng Thank you for your help in resolving this! ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64
[Kernel-packages] [Bug 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor
Your build works very well. The noise floor is even lower than before the regression, and my audio quality is now the best I've heard it. Thank you! For clarity: Medium noise: linux-image-4.15.0-58-generic 4.15.0-58.64 High noise (initial regression): linux-image-4.15.0-60-generic 4.15.0-60.67 High noise: linux-image-4.15.0-62-generic 4.15.0-62.69 High noise: linux-image-4.15.0-64-generic 4.15.0-64.73 Low noise: linux-image-4.15.0-66-generic 4.15-0-66.75~lp1845810 ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Triaged Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic
[Kernel-packages] [Bug 1845810] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292818/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic
[Kernel-packages] [Bug 1845810] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292817/+files/UdevDb.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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-28 (428 days ago)
[Kernel-packages] [Bug 1845810] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292814/+files/ProcModules.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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-28 (428 days
[Kernel-packages] [Bug 1845810] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292815/+files/PulseList.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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-28 (428 days ago)
[Kernel-packages] [Bug 1845810] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292816/+files/RfKill.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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-28 (428 days ago)
[Kernel-packages] [Bug 1845810] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292808/+files/IwConfig.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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-28 (428 days ago)
[Kernel-packages] [Bug 1845810] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292811/+files/ProcCpuinfoMinimal.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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: Upgraded to bionic on
[Kernel-packages] [Bug 1845810] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1845810/+attachment/5292810/+files/ProcCpuinfo.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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in linux package in Ubuntu: Confirmed Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2329 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc InstallationDate: Installed on 2017-05-11 (871 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-64-generic N/A linux-backports-modules-4.15.0-64-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.15.0-64-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-28 (428 days