[Kernel-packages] [Bug 2023952] Re: UNII-4 5.9G Band support request on 8852BE
** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium -- 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/2023952 Title: UNII-4 5.9G Band support request on 8852BE Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] The platform can't connect to AP with Wi-Fi 5.9G capability and wifi function doesn't work properly. [Fix] Realtek has verified the 5.9G function with 8852BE WLAN on WarlockMLK2 Intel platform and submitted upstream. https://lore.kernel.org/linux-wireless/20230508081211.38760-1-pks...@realtek.com/ Included in v6.5-rc e3b77c06c886 wifi: rtw89: support U-NII-4 channels on 5GHz band a002f98123dd wifi: rtw89: regd: judge UNII-4 according to BIOS and chip e897b0bef38a wifi: rtw89: introduce realtek ACPI DSM method [Test] Verified by ODM and can connect to 5.9G AP [Where problems could occur] commit 5 added new callback functions which change the device behavior during suspending/resuming, not sure if this impacts old chips. Other commits looks normal and should not lead to regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025344] [NEW] package linux-image-6.2.0-1003-lowlatency 6.2.0-1003.3 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: I digged the oracle one allready. That worked. it seems like ubuntu studio tries to upgrade with dkms. And it seems to linked to amd firmware drivers? purge does not work: sudo apt-get remove kernel 6.2.0-1003-lowlatency --purge Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar Let op, 'linux-objects-nvidia-525-open-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-470-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-510-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-headers-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-tools-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-image-unsigned-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-510-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-530-open-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-iwlwifi-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-470-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-image-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-450-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-450-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-signatures-nvidia-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-470-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-390-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-390-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-515-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-530-open-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-530-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-515-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-515-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-cloud-tools-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-515-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-buildinfo-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-530-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-525-open-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-525-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-extra-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-470-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-525-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-modules-nvidia-525-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Let op, 'linux-objects-nvidia-525-server-6.2.0-1003-lowlatency' wordt geselecteerd omwille van de regex '6.2.0-1003-lowlatency' Pakket 'linux-modules-extra-6.2.0-1003-lowlatency' is niet geïnstalleerd, en wordt dus niet verwijderd E: Kan pakket kernel niet vinden $ sudo apt-get autoremove Pakketlijsten worden ingelezen... Klaar Boom van vereisten wordt opgebouwd... Klaar De statusinformatie wordt gelezen... Klaar De volgende pakketten zullen VERWIJDERD worden: linux-headers-6.2.0-1005-lowlatency linux-image-6.2.0-1005-lowlatency linux-lowlatency-headers-6.2.0-1005 linux-modules-6.2.0-1
[Kernel-packages] [Bug 2025320] Re: External display sometimes frozen, after logout/login has only black screen.
Thanks. I can see the external display is connected by HDMI to the NVIDIA GPU. And you seem to be using Xorg exclusively so this is a bug between Xorg and the NVIDIA driver. I think it's likely the issue correlates with these error messages: [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership Because that means the NVIDIA driver has lost control of its displays (the external monitor). As a possible workaround you might like to try adding a kernel parameter: nvidia_drm.modeset=0 which should at least disable the code path causing the above error message. ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: Incomplete => New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags added: hybrid multigpu multimonitor nvidia ** Summary changed: - External display sometimes frozen, after logout/login has only black screen. + [nvidia] External display sometimes frozen, after logout/login has only black screen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-530 in Ubuntu. https://bugs.launchpad.net/bugs/2025320 Title: [nvidia] External display sometimes frozen, after logout/login has only black screen. Status in nvidia-graphics-drivers-530 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After some system updates my external screen is not working properly. After logout/log in it keeps black or with a background image and is frozen. Moreover, it happens from time to time even when you were logged in without any explanation. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nvidia-driver-530 530.41.03-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 29 09:06:10 2023 InstallationDate: Installed on 2023-02-19 (129 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-530/+bug/2025320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011421] Re: TDX azure instances crash during boot because of glibc bug
Sorry, there were some potential regressions that needed investigating, and we're still waiting on a few benchmark results for bug 1999551. Other than that the overall autopkgtest results are in good shape, so assuming the benchmarks show what we want them to, this shouldn't be long. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2011421 Title: TDX azure instances crash during boot because of glibc bug Status in glibc package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in glibc source package in Jammy: Fix Committed Status in linux-azure source package in Jammy: Invalid Status in glibc source package in Kinetic: Won't Fix Status in linux-azure source package in Kinetic: In Progress Status in glibc source package in Lunar: Fix Released Status in linux-azure source package in Lunar: New Bug description: [IMPACT] Glibc in jammy and kinetic is affected by the following bug : https://sourceware.org/bugzilla/show_bug.cgi?id=29953 When cpuid reports no information on a shared cache, the x86_non_temporal_threshold will be set to zero, causing memcpy/memset to behave wrong for mid-sized operations. sysdeps/x86/dl-cacheinfo.h indicates that the minimum value must be 0x4040, but this is not enforced for the default value. The issue was reported because jammy tdx instances are failing to boot (crashing) on azure. The bug has been resolved upstream in https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b [TEST CASE] Test case requires an azure tdx instance. Microsoft has tested a test package with the above commit and confirmed that instances boot successfully. [REGRESSION POTENTIAL] The patches have been accepted upstream. They modify code for x86 architecture, so any potential regression would affect x86. [OTHER] Bug upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29953 Duplicate bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30037 In jammy we need 2 commits : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b446822b6ae4e8149902a78cdd4a886634ad6321 https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b In kinetic we just need : https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=48b74865c63840b288bd85b4d8743533b73b339b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2011421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025266] Re: nvidia-dkms-* FTBS with linux 6.4
** Patch added: "nvidia-graphics-drivers-390_390.157-0ubuntu7.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+attachment/5682792/+files/nvidia-graphics-drivers-390_390.157-0ubuntu7.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2025266 Title: nvidia-dkms-* FTBS with linux 6.4 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Bug description: [Impact] /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function ‘nv_drm_update_drm_driver_features’: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: ‘struct drm_driver’ has no member named ‘dumb_destroy’ 769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy; | ^ make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1 [Fix] Apply the attached patch. [How to test] Build the dkms package and install it. [Regression potential] This patch doesn't come from NVIDIA itself, so there's a regression potential, though i can't state how severe that could be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Tested evdi-dkms module that already has this rule BUILD_EXCLUSIVE_KERNEL="CONFIG_I2C CONFIG_DRM" with jammy:linux-kvm(5.15.0-1033-kvm) that has these configs disabled. Scenario 1: old dkms version(2.8.7-2ubuntu2.1) without BUILD_EXCLUSIVE_KERNEL. Expectation: build is done and it fails because of missing config options. $ sudo apt install evdi-dkms Building for 5.15.0-1033-kvm Building initial module for 5.15.0-1033-kvm ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/evdi-dkms.0.crash' Error! Bad return status for module build on kernel: 5.15.0-1033-kvm (x86_64) Consult /var/lib/dkms/evdi/1.12.0+dfsg/build/make.log for more information. ... /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:1907: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2 Scenario 2: new dkms version(2.8.7-2ubuntu2.2) with BUILD_EXCLUSIVE_KERNEL. Expectation: build is skipped because of missing config options: $ uname -a Linux jammy-kvm 5.15.0-1033-kvm #38-Ubuntu SMP Fri Apr 21 17:30:00 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ sudo apt install evdi-dkms Loading new evdi-1.12.0+dfsg DKMS files... Building for 5.15.0-1033-kvm Building initial module for 5.15.0-1033-kvm Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1033-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-1033-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. This new package works as expected, all good. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2012612 Title: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Jammy: Fix Committed Status in dkms source package in Kinetic: Fix Released Bug description: [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 C
[Kernel-packages] [Bug 2025265] Re: Remove non-LPAE kernel flavor
** Description changed: - TBD + The LPA (large physical address) extension is an optional extension + currently supported by the Cortex-A7, Cortex-A12, and Cortex-A15 + processors. The main generic Ubuntu armhf kernel is not supposed to run + on older 32-bit processors or 32-bit processors that don't have this + extension. + + So let's drop the non-LPAE flavor. + + We currently provide two armhf flavors: generic (LPAE disabled) and + generic-lpae (LPAE enabled). Change the generic flavor to be LAPE- + enabled and remove the generic-lpae flavor. -- 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/2025265 Title: Remove non-LPAE kernel flavor Status in linux package in Ubuntu: New Bug description: The LPA (large physical address) extension is an optional extension currently supported by the Cortex-A7, Cortex-A12, and Cortex-A15 processors. The main generic Ubuntu armhf kernel is not supposed to run on older 32-bit processors or 32-bit processors that don't have this extension. So let's drop the non-LPAE flavor. We currently provide two armhf flavors: generic (LPAE disabled) and generic-lpae (LPAE enabled). Change the generic flavor to be LAPE- enabled and remove the generic-lpae flavor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025265/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025266] Re: nvidia-dkms-* FTBS with linux 6.4
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2025266 Title: nvidia-dkms-* FTBS with linux 6.4 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: New Bug description: [Impact] /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function ‘nv_drm_update_drm_driver_features’: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: ‘struct drm_driver’ has no member named ‘dumb_destroy’ 769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy; | ^ make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1 [Fix] Apply the attached patch. [How to test] Build the dkms package and install it. [Regression potential] This patch doesn't come from NVIDIA itself, so there's a regression potential, though i can't state how severe that could be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018275] Re: Fix the in-motion function does not work
The bug description does not match the requirements for an SRU, particularly "low" is no reasonable answer to "where problems could occur" ** 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/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Incomplete Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1784998] Re: After a while touchpad doesn't work
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784998 Title: After a while touchpad doesn't work Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: By default, touchpad doesn't work, but USB mouse works. WORKAROUND: Install the NVIDIA proprietary drivers, and use non-default kernel parameters: nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 10:23:53 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:15e0] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:15e0] InstallationDate: Installed on 2018-04-29 (94 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. GL553VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=48228a8f-bbca-4be4-a07a-96a383809e68 ro quiet splash nouveau.modeset=0 tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL553VD.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL553VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL553VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842425] Re: No GUI with Gnome Flashback or Classic after apt dist-upgrade; Ubuntu on Wayland OK
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: linux-signed-hwe (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1842425 Title: No GUI with Gnome Flashback or Classic after apt dist-upgrade; Ubuntu on Wayland OK Status in gnome-flashback package in Ubuntu: Incomplete Status in linux-signed-hwe package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Did apt dist-upgrade . I usually use Gnome Flashback. Now rebooting with 5.0.0.27 or 5.0.25 and logging in at GUI screen only works for "Ubuntu on Wayland". Other attempts: (1) Flashback: login transitions to purple background screen and no mouse. hitting alt-ctrl-F1 leads to an unlock screen with a next button. entering pw and clicking NEXT leads to animated circle wait icon. alt-ctrl-f2 leads to a TTY2 text mode console login screen. Login and sudo shutdown now -r (2) Gnome Classic: login transitions to a blank screen with the LCD displaying a "No video" message. alt-ctrl-f1 and unlocking there also transitions to a blank screen with the LCD displaying a "No video" message. alt-ctrl-f3 then Login and sudo shutdown now -r. (3) Ubuntu: same as with Gnome Classic. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-flashback 3.28.0-1ubuntu1.4 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 3 15:17:32 2019 InstallationDate: Installed on 2018-07-27 (403 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-flashback UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1842425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Sorry, missed your comment/question. I've tested Lunar (20230323.gitbcdcfbcf-0ubuntu1.2) and Jammy (20220329.git681281e4-0ubuntu3.14) and verified that I can establish a Bluetooth connection using the new firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/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 2025353] [NEW] Add support of AMD Pink Sardine and RPL DMIC
Public bug reported: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New -- 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2025353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887741] Re: [conroe] Display flicker sometimes
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887741 Title: [conroe] Display flicker sometimes Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: It more likey flicker more if I watch someting in fullscreen or a certain image shown is and it starts to flicker a lot out of one where. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Thu Jul 16 03:28:48 2020 DistUpgraded: 2020-06-09 01:37:47,812 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0439] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:0439] InstallationDate: Installed on 2019-12-28 (200 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=2c5b89f4-4126-404c-9d8f-3dea42f2847c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-06-09 (37 days ago) dmi.bios.date: 02/26/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0K83V0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd02/26/2010:svnDellInc.:pnInspiron560:pvr00:rvnDellInc.:rn0K83V0:rvrA00:cvnDellInc.:ct3:cvrNotSpecified: dmi.product.family: 0 dmi.product.name: Inspiron 560 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
** Tags added: oem-priority originate-from-2023145 sutton -- 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
SRU for Jammy. ** Also affects: alsa-ucm-conf (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: hwe-next Status: New => In Progress ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Status: New => In Progress ** Changed in: alsa-ucm-conf (Ubuntu Mantic) Status: New => In Progress ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu1.7.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2025353/+attachment/5682834/+files/alsa-ucm-conf_1.2.6.3-1ubuntu1.7.debdiff -- 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Status in alsa-ucm-conf source package in Mantic: In Progress Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
SRU for Lunar and Mantic. ** Patch added: "alsa-ucm-conf_1.2.6.3-1ubuntu10.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2025353/+attachment/5682835/+files/alsa-ucm-conf_1.2.6.3-1ubuntu10.debdiff -- 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Status in alsa-ucm-conf source package in Mantic: In Progress Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1769819] Re: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1769819 Title: [nvidia] Xorg crashes after system sleep / wakeup, in libwfb.so+25597 → nvidia_drv.so+60a46c → [heap]+d35cb0 Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: after putting the system to sleep, and waking it up, Xorg crashes, and I'm lead to a new greeter / login screen. naturally the state of my desktop is lost in this process, and I'm stuck with a new login with no apps running. the error reporter says: Error: [Errno 21] is a directory: '/proc/driver/nvidia/gpus/:01:00.0/' which is indeed true: $ ls /proc/driver/nvidia/gpus/\:01\:00.0/ information registry the same system worked fine with ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 8 07:51:42 2018 DistUpgraded: 2018-05-04 09:38:04,874 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.13.0-39-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GK104 [GeForce GTX 680] [10de:1180] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 680] [3842:3687] InstallationDate: Installed on 2016-04-03 (764 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=e56cb504-229d-4c7a-b16c-b259d05e992b ro noprompt quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-05-04 (3 days ago) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2
[Kernel-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1763975 Title: DP1.2 daisy-chain flickering Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2 disabled on the second monitor as per Dell instructions). I am getting flickering whereby randomly display1 or display2 turn black and then back on again. When I disable DP1.2 on the display1, and therefore get a duplicate display (as opposed to extended) on display2, I get no flickering at all. The same setup yields no flickering when running from a Windows 10 box, so don't think it is the monitors. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 12:52:24 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2068] InstallationDate: Installed on 2018-04-01 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401) MachineType: Intel Corporation NUC7i7BNH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-307 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2: dmi.product.family: Intel NUC dmi.product.name: NUC7i7BNH dmi.product.version: J31153-308 dmi.sys.vendor: Intel Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
The attachment "alsa-ucm-conf_1.2.6.3-1ubuntu1.7.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: In Progress Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Status in alsa-ucm-conf source package in Mantic: In Progress Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025266] Re: nvidia-dkms-* FTBS with linux 6.4
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2025266 Title: nvidia-dkms-* FTBS with linux 6.4 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: New Bug description: [Impact] /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function ‘nv_drm_update_drm_driver_features’: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: ‘struct drm_driver’ has no member named ‘dumb_destroy’ 769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy; | ^ make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1 [Fix] Apply the attached patch. [How to test] Build the dkms package and install it. [Regression potential] This patch doesn't come from NVIDIA itself, so there's a regression potential, though i can't state how severe that could be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2024549] Re: Linux Kernel Bluetooth L2CAP use-after-free
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024549 Title: Linux Kernel Bluetooth L2CAP use-after-free Status in linux package in Ubuntu: New Bug description: In reconnect slave mode, I start direct advertising. After establishing the connection with the central device, we begin ATT exchanges over the L2CAP socket, and then I receive a disconnect with L2CAP traces. This issue is observed across different kernel versions such as 5.17, 6.2, 6.3, 6.3.7, etc. Kernel log with bluetooth debugfs activated. $ dmesg [ 2415.213175] chan a604c117 [ 2415.213191] chan a604c117 orig refcnt 1 [ 2415.320464] hcon f362d481 bdaddr 48:b0:2d:02:81:0a status 0 [ 2415.320494] hcon f362d481 conn 1363748a hchan 81571a4f [ 2415.320505] chan a604c117 orig refcnt 2 [ 2415.320523] chan 128f5e36 [ 2415.320528] chan 128f5e36 orig refcnt 1 [ 2415.320536] conn 1363748a, psm 0x00, dcid 0x0004 [ 2415.320543] chan 128f5e36 orig refcnt 2 [ 2415.320548] chan 9ddada5b orig refcnt 1 [ 2415.320553] chan a604c117 orig refcnt 3 [ 2415.320558] chan d0b20736 [ 2415.320562] conn 1363748a, psm 0x00, dcid 0x0006 [ 2415.320567] chan d0b20736 orig refcnt 1 [ 2415.320573] chan 9ddada5b orig refcnt 2 [ 2415.320578] conn 1363748a [ 2415.320628] chan d0b20736 len 2 [ 2415.320639] chan d0b20736, skb 99ea3217 len 6 priority 7 [ 2415.320660] hci1 conn 1363748a [ 2415.614466] conn 1363748a status 0x00 encrypt 2 [ 2415.614480] chan d0b20736 scid 0x0006 state BT_CONNECTED [ 2415.614495] chan 128f5e36 scid 0x0004 state BT_OPEN [ 2415.710469] hcon f362d481 reason 19 [ 2415.710495] hcon f362d481 conn 1363748a, err 104 [ 2415.710505] chan d0b20736 orig refcnt 2 [ 2415.710512] chan d0b20736, conn 1363748a, err 104, state BT_CONNECTED [ 2415.710519] chan d0b20736 orig refcnt 3 [ 2415.710523] chan d0b20736 orig refcnt 2 [ 2415.710527] chan d0b20736 orig refcnt 1 [ 2415.710531] chan d0b20736 [ 2415.710536] chan 128f5e36 orig refcnt 3 [ 2415.710540] chan 128f5e36, conn 1363748a, err 104, state BT_OPEN [ 2415.710548] chan 128f5e36 orig refcnt 4 [ 2415.710558] chan 128f5e36 orig refcnt 3 [ 2415.710562] chan 128f5e36 orig refcnt 2 [ 2415.815007] chan a604c117 orig refcnt 2 [ 2415.815018] chan a604c117 state BT_LISTEN [ 2415.815022] chan 128f5e36 orig refcnt 1 [ 2415.815024] chan 128f5e36 [ 2415.815030] chan 128f5e36 orig refcnt 0 [ 2415.815031] [ cut here ] [ 2415.815033] refcount_t: addition on 0; use-after-free. [ 2415.815045] WARNING: CPU: 0 PID: 10662 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x150 [ 2415.815056] Modules linked in: algif_hash algif_skcipher af_alg cmac r8153_ecm cdc_ether usbnet r8152 uas mii usb_storage snd_usb_audio snd_usbmidi_lib mc ccm snd_seq_dummy snd_hrtimer hid_sensor_als hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common industrialio hid_sensor_custom joydev snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes btusb btrtl btbcm btintel btmtk bluetooth usbhid ecdh_generic ecc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus iwlmvm snd_soc_core binfmt_misc snd_compress x86_pkg_temp_thermal ac97_bus intel_powerclamp snd_pcm_dmaengine coretemp snd_hda_intel mac80211 snd_intel_dspcf g snd_intel_sdw_acpi snd_hda_codec [ 2415.815127] kvm_intel snd_hda_core libarc4 snd_hwdep kvm snd_pcm hid_sensor_hub hid_multitouch irqbypass crct10dif_pclmul crc32_pclmul polyval_clmulni snd_seq_midi snd_seq_midi_event polyval_generic ghash_clmulni_intel sha512_ssse3 hid_generic snd_rawmidi mei_hdcp mei_pxp iwlwifi snd_seq aesni_intel cmdlinepart crypto_simd spi_nor snd_seq_device cryptd ucsi_acpi pmt_telemetry nls_iso8859_1 mtd pmt_class snd_timer intel_rapl_msr mei_me processor_thermal_device_pci rapl snd i2c_i801 intel_lpss_pci processor_thermal_device spi_intel_pci processor_thermal_rfim xhci_pci intel_lpss wmi_bmof cfg80211 intel_cstate typec_ucsi soundcore i2c_smbus mei spi_intel thunderbolt idma64 intel_vsec processor_thermal_mbox xhci_pci_renesas processor_thermal_rapl intel_skl_int3
[Kernel-packages] [Bug 2025360] [NEW] Remove obsolete iwlwifi firmware
Public bug reported: Remove some of the old/obsolete iwlwifi binaries that are no longer useful for kernels >= 5.15 from the package to reduce its size. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: New ** Description changed: - Remove some of the old/obsolete iwlwifi binaries from the package to - reduce its size. + Remove some of the old/obsolete iwlwifi binaries that are no longer + useful for kernels >= 5.15 from the package to reduce its size. -- 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/2025360 Title: Remove obsolete iwlwifi firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Mantic: New Bug description: Remove some of the old/obsolete iwlwifi binaries that are no longer useful for kernels >= 5.15 from the package to reduce its size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025192] Re: broken installation while mirror syncing new kernel packages
I'm still having problems installing 'linux-image-5.15.0-76-generic- dbgsym': Unable to locate package linux-image-5.15.0-76-generic-dbgsym Couldn't find any package by glob 'linux-image-5.15.0-76-generic-dbgsym' -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2025192 Title: broken installation while mirror syncing new kernel packages Status in linux-meta package in Ubuntu: Confirmed Bug description: A new kernel package for jammy was released 3 hours ago. It is probably being synced to mirrors right now. It can be seen at https://launchpad.net/ubuntu/+source/linux-meta: 5.15.0.76.74 updates (main) 3 hours ago A little before that, I was deploying 10 Jammy machines in maas, without any problem. After that, I started having all 10 machines fail deployment. The reason is that curtin will fail package updates (complete log attached). This is the important part: ==8<--- Running command ['unshare', '--fork', '--pid', '--', 'chroot', '/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', '--option=Dpkg::options::=--force-unsafe-io', '--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with allowed return codes [0] (capture=False) Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is not installable linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not going to be installed Depends: linux-modules-extra-5.15.0-76-generic but it is not installable Recommends: thermald but it is not going to be installed E: Unable to correct problems, you have held broken packages. ==8<--- The repository being used is "http://archive.ubuntu.com/ubuntu jammy/main" It may be the case that there is still a partial mirror there, but it should not break and instead just use the latest available version while the new one is not completely avalable. I'm not sure this is only valid for linux kernel packages (maybe this is a general problem with any package) but I'm opening to linux-meta since it happened with linux in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025243] Re: Introduce the NVIDIA 535-server ERD driver series
** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Focal) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Kinetic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Lunar) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Kinetic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Lunar) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525-server in Ubuntu. https://bugs.launchpad.net/bugs/2025243 Title: Introduce the NVIDIA 535-server ERD driver series Status in nvidia-graphics-drivers-525-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-525-server source package in Focal: In Progress Status in nvidia-graphics-drivers-525-server source package in Jammy: In Progress Status in nvidia-graphics-drivers-525-server source package in Kinetic: In Progress Status in nvidia-graphics-drivers-525-server source package in Lunar: In Progress Bug description: Introduce the NVIDIA 535-server ERD driver series, enabling the -open kernel module. Release notes: https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-54-03/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525-server/+bug/2025243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
@mihalicyn yes, it looks like we are missing "UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay" in all the kernels >= 6.2. I'll open a separate bug for this. I'm wondering... do we really need to support overlayfs on top of shiftfs? Of course we don't want to break the old behavior, so there might be someone relying on it. But, to our knowledge, is there anyone/anything using this particular setup? lxd? -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Bug description: [Impact] Opened files reported in /proc/pid/map_files can be shows with the wrong mount point using overlayfs with filesystem namspaces. This incorrect behavior is fixed: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files However, the fix introduced a new regression, the reference to the original file stored in vma->vm_prfile is not properly released when vma->vm_prfile is replaced with a new file. This can cause a reference counter unbalance, leading errors such as "target is busy" when trying to unmount overlayfs, even if the filesystem has not active reference. [Test case] Reproducer provided by original bug reporter: https://launchpadlibrarian.net/663151659/overlayfsscript_example [Fix] Fix by properly releasing the original file stored in vm_prfile. [Regression potential] This fix seems to solve the reported bug (verified with the reproducer) and it doesn't seem to introduce other regressions or behavior change. However, we may experience regressions in overlayfs or potentially other "target is busy" errors when unmounting overlayfs filesystems with this fix applied, if there are still other corner cases not covered properly. [Original bug report] Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot the VM, and start the default distribution kernel, I am able to replicate the issue, the second filesystem bein
[Kernel-packages] [Bug 2025266] Re: nvidia-dkms-* FTBS with linux 6.4
** Patch added: "nvidia-graphics-drivers-470_470.182.03-0ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2025266/+attachment/5682856/+files/nvidia-graphics-drivers-470_470.182.03-0ubuntu3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2025266 Title: nvidia-dkms-* FTBS with linux 6.4 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: New Bug description: [Impact] /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function ‘nv_drm_update_drm_driver_features’: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: ‘struct drm_driver’ has no member named ‘dumb_destroy’ 769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy; | ^ make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1 [Fix] Apply the attached patch. [How to test] Build the dkms package and install it. [Regression potential] This patch doesn't come from NVIDIA itself, so there's a regression potential, though i can't state how severe that could be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 for Jammy (22.04)
** Changed in: thermald (Ubuntu Jammy) Status: Incomplete => New -- 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 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: New 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 these 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 ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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 1932124] Re: Add WWAN framework and drivers support
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1932124 Title: Add WWAN framework and drivers support Status in HWE Next: Fix Released Status in linux-intel package in Ubuntu: Fix Committed Bug description: [SRU Justification] [Impact] The Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem and Foxconn SDX55 T99W175 5G sub6 PCIE Modem are not supported in 5.11 kernel yet. The new WWAN framework and driver support are required to be backported to detect and control the new WWAN modules. [Fix] Backport the WWAN framework and drivers support from mainline kernel 5.13. [Test Case] Verify whether the Quectel/Foxconn WWAN module are detected or not. And use either `mmcli` commands or NetworkSettings Panel to test the connection. [Where problem could occur] Since the WWAN framework is totally new which makes use of the existing MHI bus drivers and protocols, it should be compatible with old WWAN modules. The regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1932124/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 arm64 when offset is not specified
** Description changed: [Description] kdump fails on arm64, on machines with a lot of memory when offeset 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 regions. To address this issue the following upstrem 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 5.15 hwe focal kernel will be fixed. - [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. 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. [Regression Potential] - [Other] Commits to backport JAMMY: kernel: a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified kexec: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions FOCAL: kernel (5.15 hwe kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel() 8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not allocate crash low memory if not needed 5832f1ae50600ac6b2b6d00cfef42d33a9473f06 docs: kdump: Update the crashkernel description for arm64 944a45abfabc171fd121315ff0d5e62b11cb5d6f arm64: kdump: Reimplement crashkernel=X d339f1584f0acf32b32326627fa3b48e6e65c599 arm64: mm: use IS_ENABLED(CONFIG_KEXEC_CORE) instead of #ifdef - kexec: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions 2572b8d702e452624bdb8d7b7c39f458e7dcf2ce arm64: kdump: deal with a lot of resource entries in /proc/iomem cf977b1af9ec67fabcc6a625589c49c52d07b11d kexec: add variant helper functions for handling memory regions f736104f533290b4ce6fbfbca74abde9ffd3888c arm64: kexec: allocate memory space avoiding reserved regions 64c49f27d88024eaab990d2cd6069289cf853098 arm64: Add support to read PHYS_OFFSET from 'kcore' - pt_note or pt_load (if available) f4ce0706d9574aecb7d4aa9af7208a1bc9b6afb4 util_lib: Add functionality to read elf notes -- 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 arm64 when offset is not specified Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: New Status in linux source package in Focal: Incomplete Status in kexec-tools source package in Jammy: New Status in linux source package in Jammy: Incomplete Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset 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 regions. To address this issue the following upstrem commits are n
[Kernel-packages] [Bug 2025266] Re: nvidia-dkms-* FTBS with linux 6.4
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2025266 Title: nvidia-dkms-* FTBS with linux 6.4 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Status in nvidia-graphics-drivers-390 source package in Mantic: New Status in nvidia-graphics-drivers-470 source package in Mantic: New Status in nvidia-graphics-drivers-510 source package in Mantic: New Bug description: [Impact] /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c: In function ‘nv_drm_update_drm_driver_features’: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:769:18: error: ‘struct drm_driver’ has no member named ‘dumb_destroy’ 769 | nv_drm_driver.dumb_destroy = nv_drm_dumb_destroy; | ^ make[2]: *** [scripts/Makefile.build:260: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.o] Error 1 [Fix] Apply the attached patch. [How to test] Build the dkms package and install it. [Regression potential] This patch doesn't come from NVIDIA itself, so there's a regression potential, though i can't state how severe that could be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2025266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 for Jammy (22.04)
** Changed in: thermald (Ubuntu Jammy) Status: New => In Progress -- 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 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress 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 these 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 ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+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 2018275] Re: Fix the in-motion function does not work
@Julian, add more explanation in [where problems could occur] ** Description changed: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] - low + because motion is always 0, the rules with motion=1 wouldn't be hit. ** Changed in: thermald (Ubuntu Jammy) Status: Incomplete => In Progress -- 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/2018275 Title: Fix the in-motion function does not work Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: In Progress Bug description: [Summary] in-Motion condition doesn't work with adaptive performance policy [Fix] This patch fix the issue, cc0890a59725) Always match motion = 0 [Test cases] 1. Install the Ubuntu 22.04-oem image on BMM4-DVT2-C2X 2. run the thermald applied the fix. #thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.log" and check the log 3. in-motion condition works [Where problems could occur] because motion is always 0, the rules with motion=1 wouldn't be hit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/2018275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025311] Re: packet storm as nics in STP enabled netns bridges lack BPDU maddr 01:80:c2:00:00:00
** Tags added: kernel-net -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2025311 Title: packet storm as nics in STP enabled netns bridges lack BPDU maddr 01:80:c2:00:00:00 Status in linux-signed package in Ubuntu: New Bug description: Bridges with STP enabled, only if in the non-default namespace, connecting the nic as a port to the bridge will not add the STP multicast address to the port nics, causing them to fail in all important BPDU topology updates. This leads to packet storms, effectively locking up all connected systems -- all the problems STP is designed to prevent. This bug exists in ubuntu's 5.15 generic Jammy and 6.1 22.04c kernels. 100% reproducible. Below you'll see two cases that vary only in that one takes place in a non-default network namespace. The only material difference is the nic ports in the non-default namespace lack the STP bridge multicast address. Notice in the default namespace, for example, we have: ip -d link show lan0bridge 31: lan0bridge: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 52:54:e5:79:c5:7a brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 65535 bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 3 stp_state 1 priority 28 vlan_filtering 0 vlan_protocol 802.1Q bridge_id 001c.52:54:e5:79:c5:7a designated_root 001c.52:54:e5:79:c5:7a root_port 1 root_path_cost 4 topology_change 0 topology_change_detected 0 hello_timer 0.00 tcn_timer0.00 topology_change_timer0.00 gc_timer 24.87 vlan_default_pvid 1 vlan_stats_enabled 0 vlan_stats_per_port 0 group_fwd_mask 0 group_address 01:80:c2:00:00:00 mcast_snooping 1 mcast_router 1 mcast_query_use_ifaddr 0 mcast_querier 0 mcast_hash_elasticity 16 mcast_hash_max 4096 mcast_last_member_count 2 mcast_startup_query_count 2 mcast_last_member_interval 100 mcast_membership_interval 26000 mcast_querier_interval 25500 mcast_query_interval 12500 mcast_query_response_interval 1000 mcast_startup_query_interval 3124 mcast_stats_enabled 0 mcast_igmp_version 2 mcast_mld_version 1 nf_call_iptables 0 nf_call_ip6tables 0 nf_call_arptables 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 And an example port: ip -d addr show gnv0lan1 32: gnv0lan1: mtu 1500 qdisc noqueue master lan0bridge state UNKNOWN group default qlen 1000 link/ether 52:54:86:cb:d4:05 brd ff:ff:ff:ff:ff:ff promiscuity 1 minmtu 68 maxmtu 65485 geneve id 7745 remote 192.XXX.XXX.XXx ttl auto dstport 6081 noudpcsum udp6zerocsumrx bridge_slave state forwarding priority 32 cost 100 hairpin off guard off root_block off fastleave off learning on flood on port_id 0x8002 port_no 0x2 designated_port 32770 designated_cost 4 designated_bridge 001c.52:54:e5:79:c5:7a designated_root 0014.52:54:ff:79:8b:4d hold_timer 0.68 message_age_timer0.00 forward_delay_timer0.00 topology_change_ack 0 config_pending 0 proxy_arp off proxy_arp_wifi off mcast_router 1 mcast_fast_leave off mcast_flood on mcast_to_unicast off neigh_suppress off group_fwd_mask 0 group_fwd_mask_str 0x0 vlan_tunnel off isolated off numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 And the expected # ip maddr show gnv0lan1 32: gnv0lan1 link 33:33:00:00:00:02 users 2 link 01:00:5e:00:00:01 link 33:33:00:00:00:01 link 01:80:c2:00:00:00 <-- STP multicast address. ... But in a non-default namespace we have, for example: root@rssnoc2e0:~# ip netns exec squad0ns ip -d link show sqd0lanbr 20: sqd0lanbr: mtu 1370 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 2a:19:e7:b2:98:c6 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 65535 bridge forward_delay 1500 hello_time 200 max_age 2000 ageing_time 3 stp_state 1 priority 1 vlan_filtering 0 vlan_protocol 802.1Q bridge_id 2710.2a:19:e7:b2:98:c6 designated_root 2710.2a:19:e7:b2:98:c6 root_port 0 root_path_cost 0 topology_change 0 topology_change_detected 0 hello_timer 0.05 tcn_timer0.00 topology_change_timer0.00 gc_timer0.00 vlan_default_pvid 1 vlan_stats_enabled 0 vlan_stats_per_port 0 group_fwd_mask 0 group_address 01:80:c2:00:00:00 mcast_snooping 1 mcast_router 1 mcast_query_use_ifaddr 0 mcast_querier 0 mcast_hash_elasticity 16 mcast_hash_max 4096 mcast_last_member_count 2 mcast_startup_query_count 2 mcast_last_member_interval 100 mcast_membership_interval 26000 mcast_querier_interval 25500 mcast_query_interval 12500 mcast_query_response_interval 1000 mcast_startup_query_interval 3124 mcast_stats_enabled 0 mcast_igmp_version 2 mcast_mld_version 1 nf_call_iptables 0 nf_call_ip6tables 0 nf_call_arptables 0 addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 And a
[Kernel-packages] [Bug 2025383] [NEW] package linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-46-generic package post-installation script
Public bug reported: bug when install software updates ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jun 29 11:59:17 2023 ErrorMessage: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-12-11 (199 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025383 Title: package linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-5.19 package in Ubuntu: New Bug description: bug when install software updates ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jun 29 11:59:17 2023 ErrorMessage: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-12-11 (199 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2025383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025383] Re: package linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-46-generic package post-installation script s
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025383 Title: package linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-5.19 package in Ubuntu: New Bug description: bug when install software updates ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jun 29 11:59:17 2023 ErrorMessage: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-12-11 (199 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: linux-hwe-5.19 Title: package linux-headers-5.19.0-46-generic 5.19.0-46.47~22.04.1 failed to install/upgrade: installed linux-headers-5.19.0-46-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2025383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025387] [NEW] Focal update: v5.4.243 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.243 upstream stable patchset
from git://git.kernel.org/
counter: 104-quad-8: Fix race condition between FLAG and CNTR reads
drm/fb-helper: set x/yres_virtual in drm_fb_helper_check_var
bluetooth: Perform careful capability checks in hci_sock_ioctl()
USB: serial: option: add UNISOC vendor and TOZED LT70C product
iio: adc: palmas_gpadc: fix NULL dereference on rmmod
ASoC: Intel: bytcr_rt5640: Add quirk for the Acer Iconia One 7 B1-750
asm-generic/io.h: suppress endianness warnings for readq() and writeq()
USB: dwc3: fix runtime pm imbalance on probe errors
USB: dwc3: fix runtime pm imbalance on unbind
perf sched: Cast PTHREAD_STACK_MIN to int as it may turn into
sysconf(__SC_THREAD_STACK_MIN_VALUE)
staging: iio: resolver: ads1210: fix config mode
debugfs: regset32: Add Runtime PM support
xhci: fix debugfs register accesses while suspended
MIPS: fw: Allow firmware to pass a empty env
ipmi:ssif: Add send_retries increment
ipmi: fix SSIF not responding under certain cond.
kheaders: Use array declaration instead of char
pwm: meson: Fix axg ao mux parents
pwm: meson: Fix g12a ao clk81 name
ring-buffer: Sync IRQ works before buffer destruction
reiserfs: Add security prefix to xattr name in reiserfs_security_write()
KVM: nVMX: Emulate NOPs in L2, and PAUSE if it's not intercepted
i2c: omap: Fix standard mode false ACK readings
Revert "ubifs: dirty_cow_znode: Fix memleak in error handling path"
ubifs: Fix memleak when insert_old_idx() failed
ubi: Fix return value overwrite issue in try_write_vid_and_data()
ubifs: Free memory for tmpfile name
selinux: fix Makefile dependencies of flask.h
selinux: ensure av_permissions.h is built when needed
tpm, tpm_tis: Do not skip reset of original interrupt vector
erofs: stop parsing non-compact HEAD index if clusterofs is invalid
erofs: fix potential overflow calculating xattr_isize
drm/rockchip: Drop unbalanced obj unref
drm/vgem: add missing mutex_destroy
drm/probe-helper: Cancel previous job before starting new one
arm64: dts: renesas: r8a77990: Remove bogus voltages from OPP table
arm64: dts: renesas: r8a774c0: Remove bogus voltages from OPP table
EDAC/skx: Fix overflows on the DRAM row address mapping arrays
ARM: dts: qcom: ipq4019: Fix the PCI I/O port range
ARM: dts: qcom: ipq8064: reduce pci IO size to 64K
ARM: dts: qcom: ipq8064: Fix the PCI I/O port range
media: bdisp: Add missing check for create_workqueue
media: uapi: add MEDIA_BUS_FMT_METADATA_FIXED media bus format.
media: av7110: prevent underflow in write_ts_to_decoder()
firmware: qcom_scm: Clear download bit during reboot
drm/msm: fix unbalanced pm_runtime_enable in adreno_gpu_{init, cleanup}
drm/msm/adreno: Defer enabling runpm until hw_init()
drm/msm/adreno: drop bogus pm_runtime_set_active()
mmc: sdhci-of-esdhc: fix quirk to ignore command inhibit for data
drm/lima/lima_drv: Add missing unwind goto in lima_pdev_probe()
regulator: core: Consistently set mutex_owner when using ww_mutex_lock_slow()
regulator: core: Avoid lockdep reports when resolving supplies
x86/apic: Fix atomic update of offset in reserve_eilvt_offset()
media: dm1105: Fix use after free bug in dm1105_remove due to race condition
media: saa7134: fix use after free bug in saa7134_finidev due to race condition
media: rcar_fdp1: simplify error check logic at fdp_open()
media: rcar_fdp1: fix pm_runtime_get_sync() usage count
media: rcar_fdp1: Make use of the helper function
devm_platform_ioremap_resource()
media: rcar_fdp1: Fix the correct variable assignments
media: rcar_fdp1: Fix refcount leak in probe and remove function
media: rc: gpio-ir-recv: Fix support for wake-up
regulator: stm32-pwr: fix of_iomap leak
x86/ioapic: Don't return 0 from arch_dynirq_lower_bound()
arm64: kgdb: Set PSTATE.SS to 1 to re-enable single-step
debugobject: Prevent init race with static objects
timekeeping: Split jiffies seqlock
tick/sched: Use tick_next_period for lockless quick check
tick/sched: Reduce seqcount held scope in tick_do_update_jiffies64()
tick/sched: Optimize tick_do_update_jiffies64() further
tick: Get rid of tick_period
tick/common: Align tick period with the HZ tick.
wifi: ath6kl: minor fix for allocation size
wifi: ath9k: hif_usb: fix memory leak of remain_skbs
wifi: ath5k: fix an off by one check in ath5k_eeprom_read_freq_list()
wifi: ath6kl: reduce WARN to dev_dbg() in callback
tools: bpftool: Remove invalid \' json escape
wifi: rtw88: mac: Return the original error from rtw_pwr_seq_parser()
wifi: rtw88: mac: Return the original error from rtw_mac_power_switch()
scm:
[Kernel-packages] [Bug 1975592] Re: Enable Nezha board
This bug was fixed in the package linux-riscv - 6.2.0-19.19.1+23.10.2 --- linux-riscv (6.2.0-19.19.1+23.10.2) mantic; urgency=medium * Miscellaneous Ubuntu changes - [Config] Update configs linux-riscv (6.2.0-19.19.1+23.10.1) mantic; urgency=medium * mantic/linux-riscv: 6.2.0-19.19.1+23.10.1 -proposed tracker (LP: #2023551) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync getabis - [Packaging] update helper scripts - [Packaging] update update.conf * Enable Nezha board (LP: #1975592) - clk: sunxi-ng: fix ccu_mmc_timing.c kernel-doc issues - clk: sunxi-ng: Avoid computing the rate twice - clk: sunxi-ng: Remove duplicate ARCH_SUNXI dependencies - clk: sunxi-ng: Move SoC driver conditions to dependencies - clk: sunxi-ng: d1: Allow building for R528/T113 - clk: sunxi-ng: d1: Mark cpux clock as critical - dt-bindings: clock: Add D1 CAN bus gates and resets - clk: sunxi-ng: d1: Add CAN bus gates and resets - soc: sunxi: sram: Only iterate over SRAM children - dt-bindings: power: Add Allwinner D1 PPU - soc: sunxi: Add Allwinner D1 PPU driver - soc: sunxi: select CONFIG_PM - dt-bindings: crypto: sun8i-ce: Add compatible for D1 - crypto: sun8i-ce - Add TRNG clock to the D1 variant - dmaengine: sun6i: Set the maximum segment size - dt-bindings: vendor-prefixes: Add Allwinner D1/D1s board vendors - dt-bindings: riscv: Add Allwinner D1/D1s board compatibles - riscv: dts: allwinner: Add the D1/D1s SoC devicetree - riscv: dts: allwinner: Add MangoPi MQ devicetree - riscv: dts: allwinner: Add Allwinner D1 Nezha devicetree - riscv: dts: allwinner: Add Sipeed Lichee RV devicetrees - riscv: dts: allwinner: Add MangoPi MQ Pro devicetree - riscv: dts: allwinner: Add Dongshan Nezha STU devicetree - riscv: Add the Allwinner SoC family Kconfig option - riscv: dts: allwinner: d1: Add power controller node - nvmem: sunxi_sid: Drop the workaround on A64 - dt-bindings: timer: Add bindings for the RISC-V timer device - clocksource/drivers/timer-riscv: Set CLOCK_EVT_FEAT_C3STOP based on DT - clocksource/drivers/riscv: Increase the clock source rating - clocksource/drivers/riscv: Get rid of clocksource_arch_init() callback - dt-bindings: timer: sifive,clint: add comaptibles for T-Head's C9xx - riscv: dts: allwinner: d1: Add crypto engine node - riscv: dts: nezha-d1: add gpio-line-names - SAUCE: mmc: sunxi-mmc: Correct the maximum segment size - SAUCE: riscv: dts: allwinner: d1: Add misc nodes - SAUCE: riscv: dts: allwinner: Keep aldo regulator on - SAUCE: riscv: dts: allwinner: Add button on the Nezha board - SAUCE: riscv: dts: allwinner: Add button on the Lichee RV Dock - SAUCE: dt-bindings: nvmem: Allow bit offsets greater than a byte - SAUCE: nvmem: core: Support reading cells with >= 8 bit offsets - SAUCE: regulator: dt-bindings: Add Allwinner D1 LDOs - SAUCE: regulator: sun20i: Add support for Allwinner D1 LDOs - SAUCE: dt-bindings: sram: sunxi-sram: Add optional regulators child - SAUCE: dt-bindings: thermal: sun8i: Add compatible for D1 - SAUCE: thermal: sun8i: Document the unknown field - SAUCE: thermal: sun8i: Set the event type for new samples - SAUCE: thermal: sun8i: Use optional clock/reset getters - SAUCE: thermal: sun8i: Ensure vref is powered - SAUCE: thermal: sun8i: Add support for the D1 variant - SAUCE: riscv: dts: allwinner: d1: Add thermal sensor and zone - SAUCE: pwm: sun8i-v536: document device tree bindings - SAUCE: pwm: sunxi: Add Allwinner SoC PWM controller driver - SAUCE: pwm: sun8i-v536: Add support for the Allwinner D1 - SAUCE: riscv: dts: allwinner: d1: Add PWM support - SAUCE: riscv: dts: allwinner: d1: Hook up PWM-controlled CPU voltage regulators - SAUCE: drm/sun4i: dsi: Allow panel attach before card registration - SAUCE: drm/sun4i: mixer: Remove unused CMA headers - SAUCE: drm/sun4i: decouple TCON_DCLK_DIV value from pll_mipi/dotclock ratio - SAUCE: drm/sun4i: tcon: Always protect the LCD dotclock rate - SAUCE: drm/sun4i: tcon_top: Register reset, clock gates in probe - SAUCE: riscv: dts: allwinner: lichee-rv-86-panel-480p: Add panel - SAUCE: riscv: dts: allwinner: d1: Add HDMI pipeline - SAUCE: riscv: dts: allwinner: d1: Enable HDMI on supported boards - SAUCE: dt-bindings: display: sun4i-tcon: Add external LVDS PHY - SAUCE: riscv: dts: allwinner: d1: Add LVDS0 PHY - SAUCE: dt-bindings: leds: Add Allwinner A100 LED controller - SAUCE: leds: sun50i-a100: New driver for the A100 LED controller - SAUCE: riscv: dts: allwinner: d1: Add LED controller node - SAUCE: riscv: dts: allwinner: d1: Add RGB LEDs to boards - SAUCE: ASoC: sun20i-codec: New driver for D1 internal codec - SAUCE: [WIP] ASoC: sun20i-codec: What is this ramp thing?
[Kernel-packages] [Bug 2025396] [NEW] kdump/kexec does not work when UEFI secureboot and kernel lockdown enabled
Public bug reported: * Explain the bug(s) We've found that for Jammy 5.15 and also 5.4.0-1049 kernel running on Bluefield, the kdump doesn't work when enabling secure boot[1]. * How to test Make sure kernel config: CONFIG_SECURITY_LOCKDOWN_LSM=y CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y CONFIG_LOCK_DOWN_IN_SECURE_BOOT=y The kdump kernel we use is actually signed correctly # file /boot/vmlinuz-5.15.0-1015-bluefield /boot/vmlinuz-5.15.0-1015-bluefield: gzip compressed data, was "vmlinuz-5.15.0 1015-bluefield.efi.signed", # kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xcfe0 /boot/vmlinuz-5.4.0-1049-bluefield kdump initrd: /boot/initrd.img-5.4.0-1049-bluefield current state:Not ready to kdump kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) Active: active (exited) since Thu 2023-04-13 19:21:01 UTC; 4 days ago Process: 1975 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) Main PID: 1975 (code=exited, status=0/SUCCESS) Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net systemd[1]: Starting Kernel crash dump capture serv> Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[1975]: Starting kdump-tools: Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2184]: * Creating symlink /var/lib/kdu> Apr 13 19:20:59 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2184]: * Creating symlink /var/lib/kdu> Apr 13 19:21:01 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2525]: syscall kexec_file_load not avai> Apr 13 19:21:01 br2-004-a-dpu.nd-sjc6w.nvmetal.net kdump-tools[2184]: * failed to load kdump kernel * Possible reason Currently, a problem faced by arm64 is if a kernel image is signed by a MOK key, loading it via the kexec_file_load() system call would be rejected with the error in dmesg "Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7". I backported the two below [2]: 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic However still kdump/kexec fails due to lockdown [ 353.298348] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 [ 364.833004] audit: type=1400 audit(1686619435.331:16): apparmor="STATUS" operation="profile_load" profile="unconfined" name="cri-containerd.apparmor.d" pid=15407 comm="apparmor_parser" If I disable kernel lockdown (CONFIG_SECURITY_LOCKDOWN_LSM=n), then kexec works ok. But this is not an acceptable workaround. * How to fix I got it working (secure boot + lockdown config enabled + kdump/kexec) using kernel v6.4 on bluefield, which means if we backport properly, mostly missing some arch/arm64/ patches, to BlueField 5.15 kernel, we can get it working. Reference 1. https://docs.nvidia.com/networking/display/BlueFieldDPUOSv392/UEFI%20Secure%20Boot 2. https://www.spinics.net/lists/arm-kernel/msg979554.html 3. https://mjg59.dreamwidth.org/50577.html ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New ** Summary changed: - kdump/kexec does not work when UEFI secureboot enabled + kdump/kexec does not work when UEFI secureboot and kernel lockdown enabled ** Description changed: * Explain the bug(s) We've found that for Jammy 5.15 and also 5.4.0-1049 kernel running on Bluefield, the kdump doesn't work when enabling secure boot[1]. * How to test + Make sure kernel config: + CONFIG_SECURITY_LOCKDOWN_LSM=y + CONFIG_SECURITY_LOCKDOWN_LSM_EARLY=y + CONFIG_LOCK_DOWN_IN_SECURE_BOOT=y + + The kdump kernel we use is actually signed correctly + # file /boot/vmlinuz-5.15.0-1015-bluefield + /boot/vmlinuz-5.15.0-1015-bluefield: gzip compressed data, was "vmlinuz-5.15.0 1015-bluefield.efi.signed", # kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xcfe0 -/boot/vmlinuz-5.4.0-1049-bluefield + /boot/vmlinuz-5.4.0-1049-bluefield kdump initrd: -/boot/initrd.img-5.4.0-1049-bluefield + /boot/initrd.img-5.4.0-1049-bluefield current state:Not ready to kdump kdump-tools.service - Kernel crash dump capture service - Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) - Active: active (exited) since Thu 2023-04-13 19:21:01 UTC; 4 days ago - Process: 1975 ExecStart=/etc/init.d/kdump-tools start (code=exited, status=0/SUCCESS) -Main PID: 1975 (code=exited, status=0/SUCCESS) + Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor preset: enabled) + Active: active (exited) since Thu 2023-04-13 19:21:01 UTC; 4 days ago + Process: 1975 ExecStart=/etc/init.d/kdump-tools
[Kernel-packages] [Bug 2025398] [NEW] RM linux-allwinner integrated into linux-riscv
Public bug reported: In mantic, linux-allwinner is now integrated into linux-riscv (aka generic). Please RM linux-allwinner source package ** Affects: linux-allwinner (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-meta-allwinner (Ubuntu) Importance: Undecided Status: Triaged ** Also affects: linux-meta-allwinner (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-allwinner (Ubuntu) Status: New => Fix Committed ** Changed in: linux-allwinner (Ubuntu) Status: New => Fix Committed ** Changed in: linux-meta-allwinner (Ubuntu) Status: Fix Committed => Triaged ** Changed in: linux-allwinner (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2025398 Title: RM linux-allwinner integrated into linux-riscv Status in linux-allwinner package in Ubuntu: Triaged Status in linux-meta-allwinner package in Ubuntu: Triaged Bug description: In mantic, linux-allwinner is now integrated into linux-riscv (aka generic). Please RM linux-allwinner source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner/+bug/2025398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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] Autopkgtest regression report (dkms/2.8.7-2ubuntu2.2)
All autopkgtests for the newly accepted dkms (2.8.7-2ubuntu2.2) for jammy have finished running. The following regressions have been reported in tests triggered by the package: openafs/1.8.8.1-3ubuntu2~22.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#dkms [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2012612 Title: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Jammy: Fix Committed Status in dkms source package in Kinetic: Fix Released Bug description: [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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2012612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2022098] Re: Severe NFS performance degradation after LP #2003053
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2022098 Title: Severe NFS performance degradation after LP #2003053 Status in linux package in Ubuntu: Incomplete Status in linux-gke package in Ubuntu: New Status in linux source package in Focal: Fix Committed Status in linux-gke source package in Focal: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux-gke source package in Jammy: Fix Released Bug description: The fix to LP #2003053 has caused massively increased NFS server access in some use-cases, which caused severe performance degradation to the point of being unusable in some cases. The solution to this issue, at least temporarily and at least for linux-gke, is to make the new behaviour optional using the "nfs_fasc=1" module parameter. Without this parameter specified, (or specified as =0) will keep the old behaviour. Regresion potential: - Regression potential is considered low considering the scope of the change and is limited to NFS only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
** Tags added: originate-from-2024143 -- 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: In Progress Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: In Progress Status in alsa-ucm-conf source package in Jammy: In Progress Status in alsa-ucm-conf source package in Lunar: In Progress Status in alsa-ucm-conf source package in Mantic: In Progress Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
The kernels that are currently in -proposed should have resolved this issue. Kernel versions: 5.4.0-154.171 (focal) 5.15.0-77.84 (jammy) The new NFS behaviour has been made to be opt-in only using the "nfs_fasc=1" modprobe option. So default behaviour should be back to normal unless this option is used. -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025360] Re: Remove obsolete iwlwifi firmware
** Tags added: kern-7292 -- 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/2025360 Title: Remove obsolete iwlwifi firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Mantic: New Bug description: Remove some of the old/obsolete iwlwifi binaries that are no longer useful for kernels >= 5.15 from the package to reduce its size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2025360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I'm fairly certain I've run the test for kinetic (20220923.gitf09bebf3-0ubuntu1.7) as well but can't find my notes. Let me redo it. -- 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 1968604] Re: rtl8761b usb bluetooth doesn't work following reboot until unplug/replug
OK, verified that I can establish a bluetooth connection on Kinetic with 20220923.gitf09bebf3-0ubuntu1.7. -- 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 1931325] Re: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15
** Tags added: 4.4 sru-20230612 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/1931325 Title: cfs_bandwidth01 in sched from ubuntu_ltp_stable failed on B-4.15 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: [Impact] Test case cfs_bandwidth01 in LTP sched test suite is a reproducer of a CFS unthrottle_cfs_rq() issue (fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning). This test triggers a warning on our 4.15 kernel: LTP: starting cfs_bandwidth01 (cfs_bandwidth01 -i 5) [ cut here ] rq->tmp_alone_branch != &rq->leaf_cfs_rq_list WARNING: CPU: 0 PID: 0 at /build/linux-fYK9kF/linux-4.15.0/kernel/sched/fair.c:393 unthrottle_cfs_rq+0x16f/0x200 Modules linked in: input_leds joydev serio_raw mac_hid qemu_fw_cfg kvm_intel kvm irqbypass sch_fq_codel binfmt_misc ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear cirrus ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm psmouse virtio_blk pata_acpi floppy virtio_net i2c_piix4 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.15.0-144-generic #148-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:unthrottle_cfs_rq+0x16f/0x200 RSP: 0018:989ebfc03e80 EFLAGS: 00010082 RAX: RBX: 989eb4c6ac00 RCX: RDX: 0005 RSI: acb63c4d RDI: 0046 RBP: 989ebfc03ea8 R08: 00af39e61b33 R09: acb63c20 R10: R11: 0001 R12: 989eb57fe400 R13: 989ebfc21900 R14: 0001 R15: 0001 FS: () GS:989ebfc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55593258d618 CR3: 7a044000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: distribute_cfs_runtime+0xc3/0x110 sched_cfs_period_timer+0xff/0x220 ? sched_cfs_slack_timer+0xd0/0xd0 __hrtimer_run_queues+0xdf/0x230 hrtimer_interrupt+0xa0/0x1d0 smp_apic_timer_interrupt+0x6f/0x140 apic_timer_interrupt+0x90/0xa0 RIP: 0010:native_safe_halt+0x12/0x20 RSP: 0018:ac603e28 EFLAGS: 0246 ORIG_RAX: ff11 RAX: abbc9280 RBX: RCX: RDX: RSI: RDI: RBP: ac603e28 R08: 00af39850067 R09: 989e73749d00 R10: R11: 7fff R12: R13: R14: R15: ? __sched_text_end+0x1/0x1 default_idle+0x20/0x100 arch_cpu_idle+0x15/0x20 default_idle_call+0x23/0x30 do_idle+0x172/0x1f0 cpu_startup_entry+0x73/0x80 rest_init+0xae/0xb0 start_kernel+0x4dc/0x500 x86_64_start_reservations+0x24/0x26 x86_64_start_kernel+0x74/0x77 secondary_startup_64+0xa5/0xb0 Code: 50 09 00 00 49 39 85 60 09 00 00 74 68 80 3d 3a 6e 54 01 00 75 5f 31 db 48 c7 c7 c0 3d 2d ac c6 05 28 6e 54 01 01 e8 11 36 fc ff <0f> 0b 48 85 db 74 43 49 8b 85 78 09 00 00 49 39 85 70 09 00 00 ---[ end trace b6b9a70bc2945c0c ]--- [Fix] Base on the test case description, we will need these fixes: * fe61468b2cbc2b sched/fair: Fix enqueue_task_fair warning * b34cb07dde7c23 sched/fair: Fix enqueue_task_fair() warning some more * 39f23ce07b9355 sched/fair: Fix unthrottle_cfs_rq() for leaf_cfs_rq list * 6d4d22468dae3d sched/fair: Reorder enqueue/dequeue_task_fair path * 5ab297bab98431 sched/fair: Fix reordering of enqueue/dequeue_task_fair() Backport needed for Bionic since we're missing some new variables / coding style changes introduced in the following commits (and their corresponding fixes): * 97fb7a0a8944bd sched: Clean up and harmonize the coding style of the scheduler code base * 9f68395333ad7f sched/pelt: Add a new runnable average signal * 6212437f0f6043 sched/fair: Fix runnable_avg for throttled cfs * 43e9f7f231e40e sched/fair: Start tracking SCHED_IDLE tasks count in cfs_rq I have also searched in the upstream tree to see if there is any other commit claim to be a fix of these but didn't see any. [Test] Test kernel can be found here: https://people.canonical.com/~phlin/kernel/lp-1931325-cfs_bandwidth01/ With these patches applied, the test can pass without triggering this warning. <<>
[Kernel-packages] [Bug 1926608] Re: upgrading does not defer initramfs updates
** Also affects: linux-firmware (Ubuntu Mantic) Importance: Undecided Status: Confirmed -- 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/1926608 Title: upgrading does not defer initramfs updates Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Mantic: Confirmed Bug description: Upgrading linux-firmware (1.173.20) on Ubuntu (18.04.5) will cause the initramfs files to be updated during the "setting up" phase of linux- firmware's installation. However, if there are other packages that also require initramfs to be updated, they will be updated again later during the "processing triggers" phase. The triggers mechanism of deb-installer is designed to avoid this duplication of effort and speed up the time taken to complete an upgrade. If there is no specific reason for linux-firmware to force the initramfs update during setup, I believe it makes sense to defer that action. In the excerpt below, udev and linux-firmware are both in the list of packages to be upgraded. Udev uses the trigger mechanism and linux- firmware does not. > # apt dist-upgrade > ... > Setting up libglib2.0-data (2.56.4-0ubuntu0.18.04.8) ... > Setting up udev (237-3ubuntu10.46) ... > update-initramfs: deferring update (trigger activated) > Setting up libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.10) ... > ... > Setting up python3-ptyprocess (0.5.2-1) ... > Setting up linux-firmware (1.173.20) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > update-initramfs: Generating /boot/initrd.img-5.4.0-65-generic > Setting up liblwres160:amd64 (1:9.11.3+dfsg-1ubuntu1.15) ... > ... > Processing triggers for libc-bin (2.27-3ubuntu1.4) ... > Processing triggers for initramfs-tools (0.130ubuntu3.11) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-72-generic > # Reference: https://wiki.debian.org/DpkgTriggers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1926608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007369] Re: Intel AX210 wifi card "Failed to run INIT ucode: -110" after linux-firmware upgraded to 20220329.git681281e4-0ubuntu3.10
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2007369 Title: Intel AX210 wifi card "Failed to run INIT ucode: -110" after linux- firmware upgraded to 20220329.git681281e4-0ubuntu3.10 Status in linux-firmware package in Ubuntu: Invalid Bug description: Xubuntu 22.04.1 LTS running 5.15.0-60-generic kernel. On last 'dist-upgrade' following packages get upgraded (according to /var/log/apt/history.log): gir1.2-javascriptcoregtk-4.0:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1), gir1.2-webkit2-4.0:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.9, 20220329.git681281e4-0ubuntu3.10), libwebkit2gtk-4.0-37:amd64 (2.38.3-0ubuntu0.22.04.1, 2.38.4-0ubuntu0.22.04.1) End-Date: 2023-02-14 00:02:47 One of this was linux-firmware package. I 'lost' my wifi connectivity. dmesg|grep iwlwifi shows: [ 10.678853] iwlwifi :01:00.0: enabling device ( -> 0002) [ 10.691307] iwlwifi :01:00.0: api flags index 2 larger than supported by driver [ 10.691325] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.63.2.2 [ 10.691602] iwlwifi :01:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm [ 10.840186] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [ 11.852608] iwlwifi :01:00.0: SecBoot CPU1 Status: 0x7663, CPU2 Status: 0xb03 [ 11.852635] iwlwifi :01:00.0: UMAC PC: 0x8047f600 [ 11.852656] iwlwifi :01:00.0: LMAC PC: 0x0 [ 11.852659] iwlwifi :01:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 11.852866] iwlwifi :01:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [ 11.852870] iwlwifi :01:00.0: 0x | ADVANCED_SYSASSERT [ 11.852874] iwlwifi :01:00.0: 0x | trm_hw_status0 [ 11.852876] iwlwifi :01:00.0: 0x | trm_hw_status1 [ 11.852878] iwlwifi :01:00.0: 0x | branchlink2 [ 11.852881] iwlwifi :01:00.0: 0x | interruptlink1 [ 11.852883] iwlwifi :01:00.0: 0x | interruptlink2 [ 11.852885] iwlwifi :01:00.0: 0x | data1 [ 11.852887] iwlwifi :01:00.0: 0x | data2 [ 11.852890] iwlwifi :01:00.0: 0x | data3 [ 11.852892] iwlwifi :01:00.0: 0x | beacon time [ 11.852894] iwlwifi :01:00.0: 0x | tsf low [ 11.852896] iwlwifi :01:00.0: 0x | tsf hi [ 11.852898] iwlwifi :01:00.0: 0x | time gp1 [ 11.852901] iwlwifi :01:00.0: 0x | time gp2 [ 11.852903] iwlwifi :01:00.0: 0x | uCode revision type [ 11.852906] iwlwifi :01:00.0: 0x | uCode version major [ 11.852908] iwlwifi :01:00.0: 0x | uCode version minor [ 11.852910] iwlwifi :01:00.0: 0x | hw version [ 11.852913] iwlwifi :01:00.0: 0x | board version [ 11.852915] iwlwifi :01:00.0: 0x | hcmd [ 11.852918] iwlwifi :01:00.0: 0x | isr0 [ 11.852920] iwlwifi :01:00.0: 0x | isr1 [ 11.852922] iwlwifi :01:00.0: 0x | isr2 [ 11.852924] iwlwifi :01:00.0: 0x | isr3 [ 11.852926] iwlwifi :01:00.0: 0x | isr4 [ 11.852928] iwlwifi :01:00.0: 0x | last cmd Id [ 11.852930] iwlwifi :01:00.0: 0x | wait_event [ 11.852933] iwlwifi :01:00.0: 0x | l2p_control [ 11.852935] iwlwifi :01:00.0: 0x | l2p_duration [ 11.852937] iwlwifi :01:00.0: 0x | l2p_mhvalid [ 11.852940] iwlwifi :01:00.0: 0x | l2p_addr_match [ 11.852942] iwlwifi :01:00.0: 0x | lmpm_pmg_sel [ 11.852944] iwlwifi :01:00.0: 0x | timestamp [ 11.852947] iwlwifi :01:00.0: 0x | flow_handler [ 11.852993] iwlwifi :01:00.0: Start IWL Error Log Dump: [ 11.852995] iwlwifi :01:00.0: Transport status: 0x0042, valid: 7 [ 11.852999] iwlwifi :01:00.0: 0x201013F2 | ADVANCED_SYSASSERT [ 11.853001] iwlwifi :01:00.0: 0x | umac branchlink1 [ 11.853004] iwlwifi :01:00.0: 0x8045DFC6 | umac branchlink2 [ 11.853006] iwlwifi :01:00.0: 0x | umac interruptlink1 [ 11.853009] iwlwifi :01:00.0: 0x | umac interruptlink2 [ 11.853011] iwlwifi :01:00.0: 0x000C | umac data1 [ 11.853013] iwlwifi :01:00.0: 0x0004 | umac data2 [ 11.853015] iwlwifi :01:00.0: 0xDEADBEEF | umac data3 [ 11.853018] iwlwifi :01:00.0: 0x0042 | umac major [ 11.853020] iwlwifi :01:00.0: 0xF1C864E0 | umac minor [ 11.853
[Kernel-packages] [Bug 2013027] Re: Issues over broadcom brcmfmac43455 firmware
If you want to keep your own firmware files and not have them being overwritten by firmware package upgrades, you can (I believe) use dpkg- divert. I don't know the exact command usage for this but you can instruct the system to place some files from linux-firmware somewhere else so that you can replace them with a local copy that doesn't get overwritten by package upgrades. -- 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/2013027 Title: Issues over broadcom brcmfmac43455 firmware Status in linux-firmware package in Ubuntu: New Status in linux-firmware-raspi2 package in Ubuntu: New Bug description: Hi, I have a Kodlix Z83-II minicomputer that employs a broadcom chipset for WIFI. The only way to make wifi on that PC work is to use the firmware from the windows image, even if that chipset is apparently managed in ubuntu. With the firmware files provided by ubuntu you get no 5GHz for wifi. The problem is that every time ubuntu updates the firmware package, firmware files dropped in /lib/firmware get overwritten, linking to some file in the cypress sub-directory. - Ideally, Ubuntu should provide all the firmware files that might be needed. Maybe this is not possible as there is a too large variety of different firmwares for broadcom chipsets or licesing issues preventing distribution. - As a second possibility, there should be a way to drop files in /lib/firmware 'side to side' to the distro ones, without having the risk of finding the manually added files rewritten. This implies that different pieces of hardware use firmware files with different filenames. Don't know if this is truly possible, as I do not know how the linux kernel decides the name of the firmware to load. - In cases like mine, it seems that the ubuntu firmware package puts in place symlinks to have brcmfmac43455 files point to the corresponding cypress cyfmac43455 files. Possibly, the package could avoid creating the symlinks if a brcmfmac43455 file is manually placed in lib/firmware. - As a last resort, I think that the documentation in `/usr/share/doc/linux-firmware` should be augmented to describe the most appropriate way to prevent custom firmware files from being rewritten: marking files not-writable? introducing diversions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
