[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051896 Title: Fix spurious wakeup caused by Cirque touchpad Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Spurious wakeup event caused by Cirque touchpad, prevent the system from sleep properly. [Fix] Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad. [Test] Suspend the system 100 times and make sure non of the wakeup event is caused by the touchpad and its IRQ line. [Where problems could occur] Logically the power consumption can increase slightly, but in reality there isn't any noticeable change. Since the quirk only applies to one device, there isn't much regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
** Tags removed: verification-needed-mantic-linux ** Tags added: verification-done-mantic-linux -- 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/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054598] Re: AWS kernels lacking sound support (even snd-aloop missing)
** Description changed: I need the snd-aloop module (and its dependencies: snd, snd-timer, snd- pcm) on an AWS server. - The linux-modules-extra-aws package (or the one this drags in) used to provide that module (as a fix for https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586) but then stopped providing it (probably when upgrading from Kernel 5.15 to 6.2?). + The linux-modules-extra-aws package (or the one this drags in) used to provide that module (as a fix for https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586) but then stopped providing it (probably when upgrading from Kernel 5.15 to 5.19?). That means that this bug is a regression (I didn't find a way to reopen the aforementioned bugreport, so I'm creating a new one). Please bring back snd-aloop (and possibly other modules that make sense on a server that doesn't actually have a soundcard). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2054598 Title: AWS kernels lacking sound support (even snd-aloop missing) Status in linux-aws package in Ubuntu: New Bug description: I need the snd-aloop module (and its dependencies: snd, snd-timer, snd-pcm) on an AWS server. The linux-modules-extra-aws package (or the one this drags in) used to provide that module (as a fix for https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586) but then stopped providing it (probably when upgrading from Kernel 5.15 to 5.19?). That means that this bug is a regression (I didn't find a way to reopen the aforementioned bugreport, so I'm creating a new one). Please bring back snd-aloop (and possibly other modules that make sense on a server that doesn't actually have a soundcard). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2054598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054598] Re: AWS kernels lacking sound support (even snd-aloop missing)
This problem persists in Kernel 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2054598 Title: AWS kernels lacking sound support (even snd-aloop missing) Status in linux-aws package in Ubuntu: New Bug description: I need the snd-aloop module (and its dependencies: snd, snd-timer, snd-pcm) on an AWS server. The linux-modules-extra-aws package (or the one this drags in) used to provide that module (as a fix for https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1970586) but then stopped providing it (probably when upgrading from Kernel 5.15 to 5.19?). That means that this bug is a regression (I didn't find a way to reopen the aforementioned bugreport, so I'm creating a new one). Please bring back snd-aloop (and possibly other modules that make sense on a server that doesn't actually have a soundcard). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2054598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Description changed: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP - To avoid conflicts, pull in another panel quirk + To avoid conflicts, pull in 3 other small patches + c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs + 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in 3 other small patches c4e532f75336 drm/amd/display: Re-add aux intercept disable delay generically for 2+ LTTPRs 923bbfe6c888 drm/amd/display: Clear dpcd_sink_ext_caps if not set 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057430] Re: The screen brightness is unable to adjust on BOE panel DPN#R6FD8
** Description changed: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP + + To avoid conflicts, pull in another panel quirk + 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Tags added: oem-priority originate-from-2054427 somerville -- 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/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in another panel quirk 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057430] [NEW] The screen brightness is unable to adjust on BOE panel DPN#R6FD8
Public bug reported: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in another panel quirk 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057430 Title: The screen brightness is unable to adjust on BOE panel DPN#R6FD8 Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] The screen brightness is unable to adjust on BOE panel DPN#R6FD8 [Fix] AMD provides a patch which is included in v6.8-rc7 to fix this issue b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP To avoid conflicts, pull in another panel quirk 3d71a8726e05 drm/amd/display: Add monitor patch for specific eDP [Test Case] 1. Boot to OS 2. Adjust the screen brightness via the hotkeys on the keyboard or brightness bar in the setting. 3. The screen brightness should change [Where problems could occur] It's just add 2 panel IDs to the quirk, should be pretty safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057424] Re: No variable refresh rate (VRR) on the Framework 16
The proposed v1 patch still has review comments to be addressed. Stay tuned. ** Changed in: linux (Ubuntu Noble) 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/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057424] [NEW] No variable refresh rate (VRR) on the Framework 16
Public bug reported: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Incomplete ** Tags: amd oem-priority originate-from-2056602 ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Tags added: amd oem-priority originate-from-2056602 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055037] Re: [amdgpu] My screen randomly starts flickering
It seems there was an update to 'linux-hwe-6.5' a couple of days ago so we were likely already tracking the correct component. ** Changed in: linux-hwe-6.5 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: [amdgpu] My screen randomly starts flickering Status in linux-hwe-6.5 package in Ubuntu: Fix Released Bug description: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of error, a black screen with a few lines at the top. Selecting "Start linux mint in compatability mode" does boot to mint but then the trackpad does not work. I have included this reference to Linux Mint as I believe mint is based on Ubuntu. Many thanks, Nick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:33:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39ec] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [17aa:39ec] InstallationDate: Installed on 2024-02-24 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 81MT ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=e078d5fc-6eaf-4e92-9388-969fa8b6f6db ro 1915.enable_psr=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2021 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN27WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.27 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN27WW(V2.06):bd01/12/2021:br2.27:efr2.27:svnLENOVO:pn81MT:pvrLenovoV145-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2055037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056743] Re: Keyboard stops working after suspend on Dell XPS 13
I think the fix was included in 5.15.149 upstream; https://lwn.net/Articles/963359/ Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID The kernel team have just pulled in 5.15.148, and haven't started on 149. They will likely get to it in the next week or so. Thanks, Matthew -- 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/2056743 Title: Keyboard stops working after suspend on Dell XPS 13 Status in linux package in Ubuntu: New Bug description: The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100. The issue seems to be identical to the problem reported for 6.7.0 here: https://bbs.archlinux.org/viewtopic.php?id=292203 On the page linked above is says a patch was submitted 2024-01-26 and the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17. I'm concerned that this still needs fixing in the 5.xxx kernel branch. Touchpad does not freeze and mouse-control of windows still works, so it's different from a bug reported elsewhere. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-102-generic 5.15.0-102.112 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2494 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 09:54:23 2024 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (2018 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/6.5.0.27.27)
All autopkgtests for the newly accepted linux-meta (6.5.0.27.27) for mantic have finished running. The following regressions have been reported in tests triggered by the package: apparmor/4.0.0~alpha2-0ubuntu5 (arm64, armhf, ppc64el, s390x) casper/1.486 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/mantic/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056800] Re: Bluetooth adapter not working ATS2851
Here is another post, it's a unresolved issue https://bbs.archlinux.org/viewtopic.php?id=280693=2 -- 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/2056800 Title: Bluetooth adapter not working ATS2851 Status in linux-firmware package in Ubuntu: New Bug description: Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni- Bluetooth-Computer-Receiver-Keyboard/dp/B0BQ3964FP It doesn't currently work on Linux due to a firmware bug. The fixes are documented on the web: https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-released/ "Bluetooth: Fix issue with Actions Semi ATS2851 based devices" https://github.com/xanmod/linux/commit/00f4b7c036814009e54ae2841c188fe064717ddf This is what it shows up as: Bus 001 Device 012: ID 10d7:b012 Actions general adapter My kernel version is 6.5.0-25-generic Anyone know how this is fixed? Im running Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2056800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057155] Re: amdgpu driver crashes running electron application after some time
** Attachment added: "look_at_this_journalctl_from_previous_boot.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+attachment/5754997/+files/look_at_this_journalctl_from_previous_boot.log -- 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/2057155 Title: amdgpu driver crashes running electron application after some time Status in linux package in Ubuntu: New Bug description: Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057 Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process armcord pid 14844 thread armcord:cs0 pid 14883 Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: GPU reset begin! Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110) Mar 11 18:30:07 garrett-desktop kernel: [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed Mar 11 18:30:07 garrett-desktop kernel: amdgpu: cp is busy, skip halt cp Mar 11 18:30:07 garrett-desktop kernel: amdgpu: rlc is busy, skip halt rlc Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: BACO reset In KDE Wayland session, the screen freezes for a few seconds and then graphical corruption appears on screen. This issue did not happen in previous versions of ubuntu (mantic/jammy) that I have run previously. This appears to be a regresssion in the amdgpu kernel driver or mesa. I have attached a journalctl from the previous boot (any other logs that were auto-uploaded as part of this report are likely not relevant). It is named: look_at_this_journalctl_from_previous_boot.log ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Mar 11 18:35:54 2024 InstallationDate: Installed on 2022-03-16 (727 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c53f Logitech, Inc. USB Receiver Bus 001 Device 003: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI) Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Micro-Star International Co., Ltd. MS-7B48 ProcFB: 0 amdgpudrmfb 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=1bad4da7-3fac-4981-9976-490388955115 ro quiet splash amdgpu.ppfeaturemask=0x vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-01-22 (50 days ago) dmi.bios.date: 11/18/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.D3 dmi.board.asset.tag: Default string dmi.board.name: Z370-A PRO (MS-7B48) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.D3:bd11/18/2021:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B48:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370-APRO(MS-7B48):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B48 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057155] [NEW] amdgpu driver crashes running electron application after some time
Public bug reported: Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057 Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process armcord pid 14844 thread armcord:cs0 pid 14883 Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: GPU reset begin! Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110) Mar 11 18:30:07 garrett-desktop kernel: [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed Mar 11 18:30:07 garrett-desktop kernel: amdgpu: cp is busy, skip halt cp Mar 11 18:30:07 garrett-desktop kernel: amdgpu: rlc is busy, skip halt rlc Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: BACO reset In KDE Wayland session, the screen freezes for a few seconds and then graphical corruption appears on screen. This issue did not happen in previous versions of ubuntu (mantic/jammy) that I have run previously. This appears to be a regresssion in the amdgpu kernel driver or mesa. I have attached a journalctl from the previous boot (any other logs that were auto-uploaded as part of this report are likely not relevant). It is named: look_at_this_journalctl_from_previous_boot.log ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Mon Mar 11 18:35:54 2024 InstallationDate: Installed on 2022-03-16 (727 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c53f Logitech, Inc. USB Receiver Bus 001 Device 003: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI) Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Micro-Star International Co., Ltd. MS-7B48 ProcFB: 0 amdgpudrmfb 1 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=1bad4da7-3fac-4981-9976-490388955115 ro quiet splash amdgpu.ppfeaturemask=0x vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-01-22 (50 days ago) dmi.bios.date: 11/18/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.D3 dmi.board.asset.tag: Default string dmi.board.name: Z370-A PRO (MS-7B48) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.D3:bd11/18/2021:br5.12:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B48:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ370-APRO(MS-7B48):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B48 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057155 Title: amdgpu driver crashes running electron application after some time Status in linux package in Ubuntu: New Bug description: Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057 Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process armcord pid 14844 thread armcord:cs0 pid 14883 Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: GPU reset begin! Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110) Mar 11 18:30:07 garrett-desktop kernel: [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed Mar 11 18:30:07 garrett-desktop kernel: amdgpu: cp is busy, skip halt cp Mar 11 18:30:07 garrett-desktop kernel: amdgpu: rlc is busy, skip halt rlc Mar 11 18:30:07 garrett-desktop kernel: amdgpu :01:00.0: amdgpu: BACO reset In KDE Wayland session, the screen
[Kernel-packages] [Bug 2054483] Re: Add headers package for IGX out-of-tree modules
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2054483 Title: Add headers package for IGX out-of-tree modules Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Bug description: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2054483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052479] Re: apply nvidia-tegra patches 2024 Jan 16-Feb 5
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1009.9 --- linux-nvidia-tegra-igx (5.15.0-1009.9) jammy; urgency=medium * jammy/linux-nvidia-tegra-igx: 5.15.0-1009.9 -proposed tracker (LP: #2054476) [ Ubuntu: 5.15.0-1022.22 ] * jammy/linux-nvidia-tegra: 5.15.0-1022.22 -proposed tracker (LP: #2053284) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/s2024.01.08) * apply nvidia-tegra patches 2024 Jan 16-Feb 5 (LP: #2052479) - NVIDIA: SAUCE: arm64: configs: enable CONFIG_IP_NF_TARGET_REDIRECT - NVIDIA: SAUCE: arm64: configs: Enable userspace I/O driver - NVIDIA: SAUCE: usb: gadget: tegra-xudc: Fix USB3 PHY retrieval logic - NVIDIA: SAUCE: arm64: configs: additional kubernetes related configs * jammy/linux-realtime: 5.15.0-1055.62 -proposed tracker (LP: #2052611) * jammy/linux: 5.15.0-97.107 -proposed tracker (LP: #2052600) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts * partproke is broken on empty loopback device (LP: #2049689) - block: Move checking GENHD_FL_NO_PART to bdev_add_partition() * CVE-2023-51781 - appletalk: Fix Use-After-Free in atalk_ioctl * CVE-2023-51780 - atm: Fix Use-After-Free in do_vcc_ioctl * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * CVE-2024-0565 - smb: client: fix OOB in receive_encrypted_standard() * CVE-2024-0646 - net: tls, update curr on splice as well * jammy/linux-realtime: 5.15.0-1054.60 -proposed tracker (LP: #2048310) * Jammy real-time patch set update: v5.15.145-rt73 (LP: #2049522) - rcu/tree: Protect rcu_rdp_is_offloaded() invocations on RT - sched: Introduce migratable() - arm64: mm: Make arch_faults_on_old_pte() check for migratability - printk: rename printk cpulock API and always disable interrupts - console: add write_atomic interface - kdb: only use atomic consoles for output mirroring - serial: 8250: implement write_atomic - printk: relocate printk_delay() - printk: call boot_delay_msec() in printk_delay() - printk: use seqcount_latch for console_seq - printk: introduce kernel sync mode - printk: move console printing to kthreads - printk: add console handover - printk: add pr_flush() - printk: Enhance the condition check of msleep in pr_flush() - sched: Switch wait_task_inactive to HRTIMER_MODE_REL_HARD - kthread: Move prio/affinite change into the newly created thread - genirq: Move prio assignment into the newly created thread - genirq: Disable irqfixup/poll on PREEMPT_RT. - efi: Allow efi=runtime - mm: Disable zsmalloc on PREEMPT_RT - net/core: disable NET_RX_BUSY_POLL on PREEMPT_RT - samples/kfifo: Rename read_lock/write_lock - crypto: testmgr - Only disable migration in crypto_disable_simd_for_test() - mm: Allow only SLUB on PREEMPT_RT - mm: page_alloc: Use migrate_disable() in drain_local_pages_wq() - mm/scatterlist: Replace the !preemptible warning in sg_miter_stop() - mm: Disable NUMA_BALANCING_DEFAULT_ENABLED and TRANSPARENT_HUGEPAGE on PREEMPT_RT - x86/softirq: Disable softirq stacks on PREEMPT_RT - Documentation/kcov: Include types.h in the example. - Documentation/kcov: Define `ip' in the example. - kcov: Allocate per-CPU memory on the relevant node. - kcov: Avoid enable+disable interrupts if !in_task(). - kcov: Replace local_irq_save() with a local_lock_t. - net/sched: sch_ets: properly init all active DRR list handles - gen_stats: Add instead Set the value in __gnet_stats_copy_basic(). - gen_stats: Add gnet_stats_add_queue(). - mq, mqprio: Use gnet_stats_add_queue(). - gen_stats: Move remaining users to gnet_stats_add_queue(). - u64_stats: Introduce u64_stats_set() - net: sched: Protect Qdisc::bstats with u64_stats - net: sched: Use _bstats_update/set() instead of raw writes - net: sched: Merge Qdisc::bstats and Qdisc::cpu_bstats data types - net: sched: Remove Qdisc::running sequence counter - net: sched: Allow statistics reads from softirq. - net: sched: fix logic error in qdisc_run_begin() - net: sched: remove one pair of atomic operations - net: stats: Read the statistics in ___gnet_stats_copy_basic() instead of adding. - net: sched: gred: dynamically allocate tc_gred_qopt_offload - sched/rt: Annotate the RT balancing logic irqwork as IRQ_WORK_HARD_IRQ - irq_work: Allow irq_work_sync() to sleep if irq_work() no IRQ support. - irq_work: Handle some irq_work in a per-CPU thread on PREEMPT_RT - irq_work: Also rcuwait for !IRQ_WORK_HARD_IRQ on PREEMPT_RT - irq_poll: Use raise_softirq_irqoff() in cpu_dead notifier - smp: Wake ksoftirqd on PREEMPT_RT instead do_softirq(). - fs/namespace: Boost the mount_lock.lock owner instead of spinning on PREEMPT_RT. - fscache: Use only one
[Kernel-packages] [Bug 2052479] Re: apply nvidia-tegra patches 2024 Jan 16-Feb 5
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1022.22 --- linux-nvidia-tegra (5.15.0-1022.22) jammy; urgency=medium * jammy/linux-nvidia-tegra: 5.15.0-1022.22 -proposed tracker (LP: #2053284) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/s2024.01.08) * apply nvidia-tegra patches 2024 Jan 16-Feb 5 (LP: #2052479) - NVIDIA: SAUCE: arm64: configs: enable CONFIG_IP_NF_TARGET_REDIRECT - NVIDIA: SAUCE: arm64: configs: Enable userspace I/O driver - NVIDIA: SAUCE: usb: gadget: tegra-xudc: Fix USB3 PHY retrieval logic - NVIDIA: SAUCE: arm64: configs: additional kubernetes related configs [ Ubuntu: 5.15.0-1055.62 ] * jammy/linux-realtime: 5.15.0-1055.62 -proposed tracker (LP: #2052611) * jammy/linux: 5.15.0-97.107 -proposed tracker (LP: #2052600) * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts * partproke is broken on empty loopback device (LP: #2049689) - block: Move checking GENHD_FL_NO_PART to bdev_add_partition() * CVE-2023-51781 - appletalk: Fix Use-After-Free in atalk_ioctl * CVE-2023-51780 - atm: Fix Use-After-Free in do_vcc_ioctl * CVE-2023-6915 - ida: Fix crash in ida_free when the bitmap is empty * CVE-2024-0565 - smb: client: fix OOB in receive_encrypted_standard() * CVE-2024-0646 - net: tls, update curr on splice as well [ Ubuntu: 5.15.0-1054.60 ] * jammy/linux-realtime: 5.15.0-1054.60 -proposed tracker (LP: #2048310) * Jammy real-time patch set update: v5.15.145-rt73 (LP: #2049522) - rcu/tree: Protect rcu_rdp_is_offloaded() invocations on RT - sched: Introduce migratable() - arm64: mm: Make arch_faults_on_old_pte() check for migratability - printk: rename printk cpulock API and always disable interrupts - console: add write_atomic interface - kdb: only use atomic consoles for output mirroring - serial: 8250: implement write_atomic - printk: relocate printk_delay() - printk: call boot_delay_msec() in printk_delay() - printk: use seqcount_latch for console_seq - printk: introduce kernel sync mode - printk: move console printing to kthreads - printk: add console handover - printk: add pr_flush() - printk: Enhance the condition check of msleep in pr_flush() - sched: Switch wait_task_inactive to HRTIMER_MODE_REL_HARD - kthread: Move prio/affinite change into the newly created thread - genirq: Move prio assignment into the newly created thread - genirq: Disable irqfixup/poll on PREEMPT_RT. - efi: Allow efi=runtime - mm: Disable zsmalloc on PREEMPT_RT - net/core: disable NET_RX_BUSY_POLL on PREEMPT_RT - samples/kfifo: Rename read_lock/write_lock - crypto: testmgr - Only disable migration in crypto_disable_simd_for_test() - mm: Allow only SLUB on PREEMPT_RT - mm: page_alloc: Use migrate_disable() in drain_local_pages_wq() - mm/scatterlist: Replace the !preemptible warning in sg_miter_stop() - mm: Disable NUMA_BALANCING_DEFAULT_ENABLED and TRANSPARENT_HUGEPAGE on PREEMPT_RT - x86/softirq: Disable softirq stacks on PREEMPT_RT - Documentation/kcov: Include types.h in the example. - Documentation/kcov: Define `ip' in the example. - kcov: Allocate per-CPU memory on the relevant node. - kcov: Avoid enable+disable interrupts if !in_task(). - kcov: Replace local_irq_save() with a local_lock_t. - net/sched: sch_ets: properly init all active DRR list handles - gen_stats: Add instead Set the value in __gnet_stats_copy_basic(). - gen_stats: Add gnet_stats_add_queue(). - mq, mqprio: Use gnet_stats_add_queue(). - gen_stats: Move remaining users to gnet_stats_add_queue(). - u64_stats: Introduce u64_stats_set() - net: sched: Protect Qdisc::bstats with u64_stats - net: sched: Use _bstats_update/set() instead of raw writes - net: sched: Merge Qdisc::bstats and Qdisc::cpu_bstats data types - net: sched: Remove Qdisc::running sequence counter - net: sched: Allow statistics reads from softirq. - net: sched: fix logic error in qdisc_run_begin() - net: sched: remove one pair of atomic operations - net: stats: Read the statistics in ___gnet_stats_copy_basic() instead of adding. - net: sched: gred: dynamically allocate tc_gred_qopt_offload - sched/rt: Annotate the RT balancing logic irqwork as IRQ_WORK_HARD_IRQ - irq_work: Allow irq_work_sync() to sleep if irq_work() no IRQ support. - irq_work: Handle some irq_work in a per-CPU thread on PREEMPT_RT - irq_work: Also rcuwait for !IRQ_WORK_HARD_IRQ on PREEMPT_RT - irq_poll: Use raise_softirq_irqoff() in cpu_dead notifier - smp: Wake ksoftirqd on PREEMPT_RT instead do_softirq(). - fs/namespace: Boost the mount_lock.lock owner instead of spinning on PREEMPT_RT. - fscache: Use only one fscache_object_cong_wait. - sched: Clean up the might_sleep() underscore
[Kernel-packages] [Bug 2054483] Re: Add headers package for IGX out-of-tree modules
This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed - 5.15.0-1009.9 --- linux-nvidia-tegra-igx-modules-signed (5.15.0-1009.9) jammy; urgency=medium * Master version: 5.15.0-1009.9 * Add headers package for IGX out-of-tree modules (LP: #2054483) - [Packaging] Recommend header packages -- Jacob Martin Tue, 20 Feb 2024 17:22:20 -0600 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2054483 Title: Add headers package for IGX out-of-tree modules Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Bug description: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2054483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054483] Re: Add headers package for IGX out-of-tree modules
This bug was fixed in the package linux-nvidia-tegra-igx-modules - 5.15.0-1009.9 --- linux-nvidia-tegra-igx-modules (5.15.0-1009.9) jammy; urgency=medium * Master version: 5.15.0-1009.9 * Add headers package for IGX out-of-tree modules (LP: #2054483) - [Packaging] Add out-of-tree headers package * apply nvidia-tegra patches 2024 Jan 16-Feb 5 (LP: #2052479) - [Packaging] Update tegra-oot-igx to version 1.3.3-3 -- Jacob Martin Tue, 20 Feb 2024 17:11:45 -0600 ** Changed in: linux-nvidia-tegra-igx-modules (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2054483 Title: Add headers package for IGX out-of-tree modules Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Bug description: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2054483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754949/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754950/+files/acpidump.txt ** Description changed: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. - I am attaching screenshots, kernel version is at the end of the filename. - --- + I am attaching screenshots, kernel version is at the end of the + filename. + + The GPU is an AMD RX580. + + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: shock 4322 F pulseaudio - /dev/snd/controlC0: shock 4322 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: shock 4322 F pulseaudio + /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: - 0 astdrmfb - 1 amdgpudrmfb + 0 astdrmfb + 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: - linux-restricted-modules-5.15.0-100-generic N/A - linux-backports-modules-5.15.0-100-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.29 + linux-restricted-modules-5.15.0-100-generic N/A + linux-backports-modules-5.15.0-100-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined -- 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/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A
[Kernel-packages] [Bug 2056804] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754946/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754945/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754948/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754947/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754944/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754943/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754942/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754939/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754941/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754940/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754938/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754937/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754936/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Re: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21
apport information ** Tags added: apport-collected jammy ** Description changed: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. - I am attaching screenshots, kernel version is at the end of the - filename. + I am attaching screenshots, kernel version is at the end of the filename. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: shock 4322 F pulseaudio + /dev/snd/controlC0: shock 4322 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-03-28 (1079 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Undefined Undefined + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: + 0 astdrmfb + 1 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-100-generic N/A + linux-backports-modules-5.15.0-100-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.29 + RfKill: + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: jammy + Uname: Linux 5.15.0-100-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) + UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/26/2018 + dmi.bios.release: 4.6 + dmi.bios.vendor: GIGABYTE + dmi.bios.version: R23 + dmi.board.asset.tag: 01234567890123456789AN + dmi.board.name: Undefined + dmi.board.vendor: Undefined + dmi.board.version: 0001 + dmi.chassis.asset.tag: 01234567890123456789AN + dmi.chassis.type: 17 + dmi.chassis.vendor: Undefined + dmi.chassis.version: 0001 + dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: + dmi.product.name: Undefined + dmi.product.sku: GIGABYTE Server + dmi.product.version: 0002 + dmi.sys.vendor: Undefined ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754933/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 2056804] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754935/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2056804/+attachment/5754934/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. The GPU is an AMD RX580. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Re: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21
** Attachment added: "Screenshot from 2024-03-11 21-24-02 6.5.0-21.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754917/+files/Screenshot%20from%202024-03-11%2021-24-02%206.5.0-21.png -- 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/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Re: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21
** Attachment added: "Screenshot from 2024-03-11 21-41-30 5.15.0-100.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754918/+files/Screenshot%20from%202024-03-11%2021-41-30%205.15.0-100.png -- 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/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Re: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21
** Attachment added: "Right-click 6.5.0-25.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754919/+files/Right-click%206.5.0-25.png -- 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/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] Re: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21
** Attachment added: "Screenshot from 2024-03-11 21-29-22 6.5.0-25.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754916/+files/Screenshot%20from%202024-03-11%2021-29-22%206.5.0-25.png -- 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/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056804] [NEW] Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21
Public bug reported: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: GIGABYTE dmi.bios.version: R23 dmi.board.asset.tag: 01234567890123456789AN dmi.board.name: Undefined dmi.board.vendor: Undefined dmi.board.version: 0001 dmi.chassis.asset.tag: 01234567890123456789AN dmi.chassis.type: 17 dmi.chassis.vendor: Undefined dmi.chassis.version: 0001 dmi.modalias: dmi:bvnGIGABYTE:bvrR23:bd06/26/2018:br4.6:svnUndefined:pnUndefined:pvr0002:rvnUndefined:rnUndefined:rvr0001:cvnUndefined:ct17:cvr0001:skuGIGABYTEServer: dmi.product.name: Undefined dmi.product.sku: GIGABYTE Server dmi.product.version: 0002 dmi.sys.vendor: Undefined ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy ** Attachment added: "Screenshot from 2024-03-11 21-31-48 6.5.0-25.png" https://bugs.launchpad.net/bugs/2056804/+attachment/5754914/+files/Screenshot%20from%202024-03-11%2021-31-48%206.5.0-25.png ** Package changed: mesa (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056804 Title: Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 Status in linux package in Ubuntu: New Bug description: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shock 4322 F pulseaudio /dev/snd/controlC0: shock 4322 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-03-28 (1079 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Undefined Undefined NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 astdrmfb 1 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-100-generic root=/dev/mapper/ubuntu_vg-ubuntu_root ro vfio-pci.ids=10de:17c8,10de:0fb0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-100-generic x86_64 UpgradeStatus: Upgraded to jammy on 2024-02-20 (20 days ago) UserGroups: adm cdrom dip input libvirt lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True dmi.bios.date: 06/26/2018 dmi.bios.release: 4.6
[Kernel-packages] [Bug 2056803] [NEW] amdgpu: hotplugging display sometimes fails
Public bug reported: Description:Ubuntu Noble Numbat (development branch) Release:24.04 Kernel info: Linux gman-Laptop-13-AMD-Ryzen-7040Series 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Hardware: AMD Framework 13 Expected: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) after boot does not fail every time What happened: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) frequently fails with either: - no outout - a white screen with only the mouse cursor visible - attempt enable and disable over and over again with dmesg log spam and KDE display configuration showing that the display arrangement changes every couple of seconds this problem is not observed on Windows 11 with the same hardware. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 11 16:59:30 2024 InstallationDate: Installed on 2023-11-16 (117 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-02-25 (16 days ago) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: A5 dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA5:rvnFramework:rnFRANMDCP05:rvrA5:cvnFramework:ct10:cvrA5:skuFRANDGCP05: dmi.product.family: Laptop dmi.product.name: Laptop 13 (AMD Ryzen 7040Series) dmi.product.sku: FRANDGCP05 dmi.product.version: A5 dmi.sys.vendor: Framework ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056803 Title: amdgpu: hotplugging display sometimes fails Status in linux package in Ubuntu: New Bug description: Description:Ubuntu Noble Numbat (development branch) Release:24.04 Kernel info: Linux gman-Laptop-13-AMD-Ryzen-7040Series 6.8.0-11-generic #11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Hardware: AMD Framework 13 Expected: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) after boot does not fail every time What happened: Hotplugging HDMI display (via usb-c displayport alt mode with DP-HDMI adapter) frequently fails with either: - no outout - a white screen with only the mouse cursor visible - attempt enable and disable over and over again with dmesg log spam and KDE display configuration showing that the display arrangement changes every couple of seconds this problem is not observed on Windows 11 with the same hardware. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-generic 6.8.0-11.11+1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Mar 11 16:59:30 2024 InstallationDate: Installed on 2023-11-16 (117 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) MachineType: Framework Laptop 13 (AMD Ryzen 7040Series) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8484eee5-4c87-4cb9-9f40-5f1c9a24db18 ro rtc_cmos.use_acpi_alarm=1 quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-02-25 (16 days ago) dmi.bios.date: 10/17/2023 dmi.bios.release: 3.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.03 dmi.board.asset.tag: * dmi.board.name: FRANMDCP05 dmi.board.vendor: Framework dmi.board.version: A5 dmi.chassis.asset.tag: FRANDGCPA5342400SJ
[Kernel-packages] [Bug 2056804] [NEW] Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21
You have been subscribed to a public bug: After updating to 6.5.0-25, I am experiencing a very peculiar form of screen corruption. It has been persistent and consistent across reboots. It does not manifest on 6.5.0-21, neither on 5.15.0-100. Another peculiarity is that right clicking on the right side and lower side of the screen makes the right-click menu appear in the upper-left area of the screen. I am attaching screenshots, kernel version is at the end of the filename. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Screen corruption on kernel 6.5.0-25, but not on 6.5.0-21 https://bugs.launchpad.net/bugs/2056804 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056800] [NEW] Bluetooth adapter not working ATS2851
Public bug reported: Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni-Bluetooth- Computer-Receiver-Keyboard/dp/B0BQ3964FP It doesn't currently work on Linux due to a firmware bug. The fixes are documented on the web: https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-released/ "Bluetooth: Fix issue with Actions Semi ATS2851 based devices" https://github.com/xanmod/linux/commit/00f4b7c036814009e54ae2841c188fe064717ddf This is what it shows up as: Bus 001 Device 012: ID 10d7:b012 Actions general adapter My kernel version is 6.5.0-25-generic Anyone know how this is fixed? Im running Ubuntu 23.10 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth -- 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/2056800 Title: Bluetooth adapter not working ATS2851 Status in linux-firmware package in Ubuntu: New Bug description: Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni- Bluetooth-Computer-Receiver-Keyboard/dp/B0BQ3964FP It doesn't currently work on Linux due to a firmware bug. The fixes are documented on the web: https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-released/ "Bluetooth: Fix issue with Actions Semi ATS2851 based devices" https://github.com/xanmod/linux/commit/00f4b7c036814009e54ae2841c188fe064717ddf This is what it shows up as: Bus 001 Device 012: ID 10d7:b012 Actions general adapter My kernel version is 6.5.0-25-generic Anyone know how this is fixed? Im running Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2056800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056784] Re: I am facing this problem since last update
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056784 Title: I am facing this problem since last update Status in linux package in Ubuntu: New Bug description: After the latest update my Wifi is facing problems in turning on and off. If i try to turn in off from setting Linux hangs and doesnt respond so i have to force shutdown. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 [origin: unknown] ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:34937418:2024-03-07 00:08:13.097607256 +0500:2024-03-07 00:08:08.389607314 +0500:/var/crash/_opt_kingsoft_wps-office_office6_wps.1000.crash 640:1000:124:22382432:2024-03-09 16:26:07.512111973 +0500:2024-03-09 16:26:03.740094005 +0500:/var/crash/_usr_bin_nautilus.1000.crash 640:1000:124:16745892:2024-03-10 15:07:04.239937641 +0500:2024-03-10 15:07:02.491937663 +0500:/var/crash/_opt_kingsoft_wps-office_office6_wpsoffice.1000.crash 640:1000:124:14354661:2024-03-06 19:21:34.735971256 +0500:2024-03-06 19:21:32.571971283 +0500:/var/crash/_opt_kingsoft_wps-office_office6_wpscloudsvr.1000.crash 640:1000:124:19132571:2024-02-27 11:56:01.657193535 +0500:2024-02-27 11:55:58.205193577 +0500:/var/crash/_usr_bin_gnome-software.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 23:01:49 2024 InstallationDate: Installed on 2024-02-02 (38 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056784] [NEW] I am facing this problem since last update
You have been subscribed to a public bug: After the latest update my Wifi is facing problems in turning on and off. If i try to turn in off from setting Linux hangs and doesnt respond so i have to force shutdown. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 [origin: unknown] ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CrashReports: 640:1000:124:34937418:2024-03-07 00:08:13.097607256 +0500:2024-03-07 00:08:08.389607314 +0500:/var/crash/_opt_kingsoft_wps-office_office6_wps.1000.crash 640:1000:124:22382432:2024-03-09 16:26:07.512111973 +0500:2024-03-09 16:26:03.740094005 +0500:/var/crash/_usr_bin_nautilus.1000.crash 640:1000:124:16745892:2024-03-10 15:07:04.239937641 +0500:2024-03-10 15:07:02.491937663 +0500:/var/crash/_opt_kingsoft_wps-office_office6_wpsoffice.1000.crash 640:1000:124:14354661:2024-03-06 19:21:34.735971256 +0500:2024-03-06 19:21:32.571971283 +0500:/var/crash/_opt_kingsoft_wps-office_office6_wpscloudsvr.1000.crash 640:1000:124:19132571:2024-02-27 11:56:01.657193535 +0500:2024-02-27 11:55:58.205193577 +0500:/var/crash/_usr_bin_gnome-software.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 23:01:49 2024 InstallationDate: Installed on 2024-02-02 (38 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages wayland-session -- I am facing this problem since last update https://bugs.launchpad.net/bugs/2056784 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
@rafael.lopez, Sorry, hopefully last thing: can you actually back port this to 6.5? I should be able to test that on another system -- 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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 ... kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 ... kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 ... kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
@rafael.lopez, Turns out I cannot test this. They system I have is Debian 11.9 and dpkg doesn't support zstd :( -- 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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 ... kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 ... kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 ... kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016040] Re: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error
@Rafael.lopez, Many apologies, I did not see this reply. I will test immediately and let you know. Thanks for doing this! ~Noah -- 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/2016040 Title: Creating bcache backing device using a Dell Ent NVMe CM6 MU 6.4TB storage fails with "cannot allocate memory" error Status in linux package in Ubuntu: Confirmed Bug description: # make-bcache -B /dev/nvme4n1 UUID: 569e90b3-cc2a-4a0e-a201-476c426a2141 Set UUID: d8d8458a-01df-481e-a7dc-e75843a9608f version:1 block_size: 1 data_offset:16 kern.log: Apr 12 18:21:56 ... kernel: [ 723.854659] bcache: register_bdev() error nvme4n1: cannot allocate memory Apr 12 18:21:56 ... kernel: [ 723.854662] bcache: register_bdev_worker() error /dev/nvme4n1: fail to register backing device Same error message is mentioned in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909518, but the suggested configuration change does not fix the issue: # nvme id-ns /dev/nvme4n1 -n 1 -H |grep "LBA Format" [3:0] : 0x3 Current LBA Format Selected LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes - Relative Performance: 0 Best LBA Format 2 : Metadata Size: 0 bytes - Data Size: 1 bytes - Relative Performance: 0 Best LBA Format 3 : Metadata Size: 0 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best (in use) LBA Format 4 : Metadata Size: 8 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best LBA Format 5 : Metadata Size: 64 bytes - Data Size: 4096 bytes - Relative Performance: 0 Best Using a Dell Ent NVMe P5800x WI U.2 400GB storage works as expected: # make-bcache -B /dev/nvme2n1 UUID: b1405a6d-8732-4175-8aba-d67be23b3ff0 Set UUID: af6b190f-a57e-4f2b-926e-904a95268390 version:1 block_size: 8 data_offset:16 # lsblk NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS ... nvme2n1 259:10 372.6G 0 disk └─bcache0 252:00 372.6G 0 disk ... kern.log: Apr 12 18:47:33 ... kernel: [ 2261.135332] bcache: register_bdev() registered backing device nvme2n1 Kernel versions tested: 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 5.15.0-69-generic #76-Ubuntu SMP --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 18:10 seq crw-rw 1 root audio 116, 33 Apr 12 18:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Dell Inc. PowerEdge R7525 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-38-generic root=UUID=3c0a9c0d-3f5d-4d4d-a571-37298c70a1a3 ro ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-38-generic N/A linux-backports-modules-5.19.0-38-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/25/2022 dmi.bios.release: 2.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.2 dmi.board.name: 03WYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.2:bd10/25/2022:br2.10:svnDellInc.:pnPowerEdgeR7525:pvr:rvnDellInc.:rn03WYW4:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=08FF;ModelName=PowerEdgeR7525: dmi.product.family: PowerEdge dmi.product.name: PowerEdge R7525 dmi.product.sku: SKU=08FF;ModelName=PowerEdge R7525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912880] Re: Touchpad (MSFT) not detected on Lenovo Ideapad Flex 5 AMD
You might want to try passing the various i8042 controller module linux parameters (i8042.nomux=1, i8042.kbdreset=1, i8042.reset=1) and also i8042.nopnp as told by your dmesg: [ 0.602905] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp note that the AUX port is the mouse. You can set then via grub by setting GRUB_CMDLINE_LINUX="" in /etc/default/grub and running update-grub as root. Or plain edit enter then in the grub editor at boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1912880 Title: Touchpad (MSFT) not detected on Lenovo Ideapad Flex 5 AMD Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: The Laptop is an Ideapad Flex 5 14ARE05 Model 81X2 My touchpad is not recognized at all in xinput or libinput list-devices. There are however some lines mentioned in dmesg about MSFT, Mouse and PS/2 which I think is the touchpad. [0.004374] ACPI: SSDT 0xC968F000 007216 (v02 LENOVO AmdTable 0002 MSFT 0400) [1.009575] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy regulator [1.009599] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy regulator [1.010058] i2c_hid i2c-MSFT0001:00: hid_descr_cmd failed [0.910718] hid-generic 0018:056A:5214.0001: input,hidraw0: I2C HID v1.00 Mouse [WACF2200:00 056A:5214] on i2c-WACF2200:00 [0.602905] i8042: PNP: PS/2 Controller [PNP0303:KBD0] at 0x60,0x64 irq 1 [0.602905] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp [0.604083] mousedev: PS/2 mouse device common for all mice The touchpad is an MSFT0001:00: The spec sheet for the laptop mentiones: "Buttonless Mylar® surface multi-touch touchpad" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 23 09:19:23 2021 InstallationDate: Installed on 2021-01-06 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1912880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056373] Comment bridged from LTC Bugzilla
--- Comment From jldo...@us.ibm.com 2024-03-11 14:00 EDT--- Thank you Frank for providing a test kernel! I have installed the test kernel and everything appears to be working smoothly. --- root@neop91:/home/neo# mkvterm --id 2 vterm for partition 2 is active. Press Control+] to exit. IBM Virtual I/O Server login: Cleaning up... vterm closed --- syslog: --- Mar 11 17:52:13 neop91 kernel: [ 50.767514] HVCS: Driver registered. Mar 11 17:52:13 neop91 drmgr: drmgr: -c slot -s U9080.M9S.13073A8-V1-C6 -a -w 3 Mar 11 17:52:13 neop91 kernel: [ 50.853870] rpaphp: RPA HOT Plug PCI Controller Driver version: 0.1 Mar 11 17:52:13 neop91 kernel: [ 51.030821] HVCS: vty-server@3006 added to the vio bus. Mar 11 17:52:13 neop91 kernel: [ 51.030860] rpadlpar_io: slot U9080.M9S.13073A8-V1-C6 added Mar 11 17:52:16 neop91 kernel: [ 53.899124] HVCS: vty-server@3006 connection opened. Mar 11 17:52:23 neop91 kernel: [ 61.344106] HVCS: Closed vty-server@3006 and partner vty@3000:2 connection. Mar 11 17:52:24 neop91 drmgr: drmgr: -c slot -s U9080.M9S.13073A8-V1-C6 -r -w 3 Mar 11 17:52:24 neop91 kernel: [ 61.468923] HVCS: Destroyed hvcs_struct for vty-server@3006. Mar 11 17:52:24 neop91 kernel: [ 61.468925] HVCS: vty-server@3006 removed from the vio bus. Mar 11 17:52:24 neop91 kernel: [ 61.468971] rpadlpar_io: slot U9080.M9S.13073A8-V1-C6 removed --- HVCS is being probed and rpadlpar_io is adding the slot information correctly. When mkvterm closes the connection with Ctrl+], HVCS is closing the connection properly and behaving as expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056373 Title: Problems with HVCS and hotplugging Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: Invalid Status in linux source package in Noble: Invalid Bug description: SRU Justification: == [Impact] * HVCS (Hypervisor Virtual Console Server) is broken because the virtual terminal mkvterm fails, caused by pvmutil failing. * When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. * This leads to HVCS never having probe() called. * In addition, HVCS is missing patches/fixes, and is broken without them. [Fix] * Fix one and two is required for focal only, all other for focal and jammy: * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58 "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry" * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record" * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc "hvcs: Fix hvcs port reference counting" * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556 "hvcs: Use dev_groups to manage hvcs device attributes" * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a "hvcs: Use driver groups to manage driver attributes" * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5 "hvcs: Get reference to tty in remove" * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6 "hvcs: Use vhangup in hotplug remove" * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f "hvcs: Synchronize hotplug remove with port free" [Test Plan] * The high level test plan is to run mkvterm with an id. * mkvterm will fail because /dev/hvcs* device nodes are missing. * Details see https://bugs.launchpad.net/bugs/2023243 for more information. Especially the script provided by IBM (see original bug description: `---Steps to Reproduce---`). * IBM will (stress) test the updated kernel(s) provided in -proposed. [Where problems could occur] * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c and are needed to fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. In case of issues here hotplugging with drmgr might break. * The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created. * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded
[Kernel-packages] [Bug 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if dmi-sysfs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name dmi-sysfs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2049634 Title: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data Status in linux package in Ubuntu: In Progress Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/2049634 [Impact] Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize set will see data destruction when copying files from their systems onto a cifs smb mount. wsize defaults to 65535 bytes, but when set to smaller values, like 16850, users will see blocks of 16850 bytes copied over, followed by 3900 binary zeros, followed by the next block of data followed by more binary zeros. This destroys what you are copying, and the data corruption is completely silent. A workaround is to set wsize to a multiple of PAGE_SIZE. [Fix] This was fixed upstream in 6.8-rc5 by the following: commit 4860abb91f3d7fbaf8147d54782149bb1fc45892 Author: Steve French Date: Tue Feb 6 16:34:22 2024 -0600 Subject: smb: Fix regression in writes when non-standard maximum write size negotiated Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4860abb91f3d7fbaf8147d54782149bb1fc45892 This patch has been selected for upstream stable. The patch looks at wsize negotiation from the server, and also what is set on the mount command line, and if not a multiple of PAGE_SIZE, rounds it down, taking care to not be 0. The real corruption bug still exists in netfs/folios subsystems and we are looking for it still, but this solves the immediate data corruption issues on smb. [Testcase] Start two VMs, one for the server, and the other, the client. Server -- $ sudo apt update $ sudo apt upgrade $ sudo apt install samba $ sudo vim /etc/samba/smb.conf server min protocol = NT1 [sambashare] comment = Samba on Ubuntu path = /home/ubuntu/sambashare read only = no browsable = yes $ mkdir ~/sambashare $ sudo smbpasswd -a ubuntu Client -- $ sudo apt update $ sudo apt install cifs-utils $ mkdir ~/share $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share $ ( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" ) $ sha256sum testdata.txt 9ec09af020dce3270ea76531141940106f173c7243b7193a553480fb8500b3f2 testdata.txt Now copy the file to the share. Client -- $ cp testdata.txt share/ Server -- $ sha256sum sambashare/testdata.txt 9e573a0aa795f9cd4de4ac684a1c056dbc7d2ba5494d02e71b6225ff5f0fd866 sambashare/testdata.txt The SHA256 hash is different. If you view the file with less, you will find a block of wsize=16850 bytes, then 3900 bytes of binary zeros, followed by another wsize=16850 bytes, then 3900 bytes of binary zeros, etc. An example of a broken file is: https://launchpadlibrarian.net/712573213/testdata-back-from-server.txt [Where problems could occur] We are changing the wsize that the SMB server negotiates or the user explicitly sets on the mount command line to a safe value, if the asked for value was not a multiple of PAGE_SIZE. It is unlikely that any users will notice any difference. If the wsize happens to be rounded down to a significantly smaller number, there may be a small performance impact, e.g. you set wsize=8094 for some reason, it would round down to wsize=4096, and lead to double the writes. At least you have data integrity though. Most users default to wsize=65535, and will have no impact at all. Only those with very old smb 1.0 servers that negotiate down to 16850 will see any difference. If a regression were to occur, it could result in user's wsize being incorrectly set, leading to the underlying netfs/folios data corruption being triggered and causing data corruption. [Other info] The issue
[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2053251 Title: performance: Scheduler: ratelimit updating of load_avg Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2040026 [Description] Improve cache bouncing on tg->load_avg [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Sapphire Rapids Date HW is expected at Canonical: Component(s): Perf-Scalability Scheduler [Software Information] Target Version: 24.04 Target Kernel: TBD Commit IDs: 1528c661c24b sched/fair: Ratelimit update to tg->load_avg External Links: [Business Justification] [Testing guidance] [External ID] LFE-7154 Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0 https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053251/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051896] Re: Fix spurious wakeup caused by Cirque touchpad
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051896 Title: Fix spurious wakeup caused by Cirque touchpad Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Spurious wakeup event caused by Cirque touchpad, prevent the system from sleep properly. [Fix] Skip SET_POWER SLEEP so there won't be any IRQ raised by the touchpad. [Test] Suspend the system 100 times and make sure non of the wakeup event is caused by the touchpad and its IRQ line. [Where problems could occur] Logically the power consumption can increase slightly, but in reality there isn't any noticeable change. Since the quirk only applies to one device, there isn't much regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051896/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054809] Re: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2054809 Title: linux: please move erofs.ko (CONFIG_EROFS for EROFS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: SRU Justification [Impact] The erofs.ko module (CONFIG_EROFS) is currently shipped in linux- modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from using the erofs filesystem. Erofs is a modern alternative to squashfs that supports more features such as ACLs. The following LPC presentation has more details on erofs and its advantages over squashfs: https://youtu.be/jt-hp_LtSBc. A user launching a VM using the linux-virtual kernel image is not able to mount erofs filesystems due to the lack of this kconfig. We make extensive use of erofs in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a (core) module that is built by default. To verify this works, it is sufficient to create an erofs filesystem with mkfs.erofs and verify that it can be mounted: $ mkdir sources $ echo abcde > sources/file $ mkfs.erofs erofs sources $ mount erofs mnt --mkdir $ ls mnt file Without this module installed and loaded, the mount will fail. Once enabled, it will succeed. [Test] 1. pull built linux-modules packages for architectures with do_extras_package set to true; 2. extract the deb and check if erofs kernel module file exists: $ dpkg-deb -R linux-modules-*.deb . $ find . -name erofs.ko\* [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054809/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052005] Re: Validate connection interval to pass Bluetooth Test Suite
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2052005 Title: Validate connection interval to pass Bluetooth Test Suite Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] Ubuntu doesn't pass Bluetooth Test Suite to get Bluetooth certified. [Fix] Validate max connection interval to pass test case "GAP/CONN/CPUP/BV-05-C 'Connection Parameter Update Procedure Invalid Parameters Central Responder'" [Test] Run the test suite. With the patch applied the case is passed. [Where problems could occur] If any device requires setting a wrong interval to function properly, this might affect those devices in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054218] Re: kvm: Running perf against qemu processes results in page fault inside guest
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2054218 Title: kvm: Running perf against qemu processes results in page fault inside guest Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2054218 [Impact] Running perf against a QEMU/kvm process results in the guest suffering a page fault in trying to store Precise Event Based Sampling (PEBS) records for the host. This affects both using perf against a single process, in which it crashes the targeted guest, or using perf system wide, in which it crashes all running guests on the system. The issue was introduced in 6.0 by: commit c59a1f106f5cd4843c097069ff1bb2ad72103a67 Author: Like Xu Date: Mon Apr 11 18:19:36 2022 +0800 Subject: KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c59a1f106f5cd4843c097069ff1bb2ad72103a67 This affects all 6.2 and 6.5 kernels. There is no known workaround, apart from not using perf on affected systems. [Fix] The issue was fixed in 6.7 by: commit 971079464001c6856186ca137778e534d983174a Author: Paolo Bonzini Date: Thu Jan 4 16:15:17 2024 +0100 Subject: KVM: x86/pmu: fix masking logic for MSR_CORE_PERF_GLOBAL_CTRL Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=971079464001c6856186ca137778e534d983174a This reinstates the logic for setting MSR_CORE_PERF_GLOBAL_CTRL to what it was before "KVM: x86/pmu: Add IA32_PEBS_ENABLE MSR emulation for extended PEBS". - .guest = intel_ctrl & (~cpuc->intel_ctrl_host_mask | ~pebs_mask), + .guest = intel_ctrl & ~cpuc->intel_ctrl_host_mask & ~pebs_mask, The faulty logic includes any bit that isn't both marked as exclude_guest and using PEBS, while it should really be excluding PEBS from the host. [Testcase] Start a bare metal server. Enable KVM, start a few VMs. The VMs can be idle, they don't require any workload. $ sudo apt-get install qemu-kvm libvirt-daemon-system libvirt-clients bridge-utils uvtool $ sudo reboot $ ssh-keygen $ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-b release=jammy arch=amd64 $ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-c release=jammy arch=amd64 $ virsh list Id Name State - 2jammy-a running 3jammy-b running 4jammy-c running $ uvt-kvm ssh jammy-a Check it works. $ ps aux | grep qemu Find the pid of jammy-a $ perf top -p $PID $ virsh console jammy-a Escape character is ^] (Ctrl + ]) [ 357.793039] BUG: unable to handle page fault for address: fe49178c6028 $ uvt-kvm ssh jammy-a (no response) Test packages are available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf379502-test If you install it, then running perf against the PID of qemu processes will no longer crash the guest, and they will be accessible by SSH afterward. [Where problems could occur] We are rearranging the logic of setting the PEBS MSRs, which affects processor sampling of events. This will affect any profiling tools running against KVM based virtual machines, namely perf against QEMU. If a regression were to occur, running perf against a VM could cause it to page fault and subsequently crash, resulting in downtime. The only workaround will be to disable all profiling tools until a fix is available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) [Test Case] $ sudo apt install linux-tools-common $ man usbip No manual entry for usbip [Where Problems Could Occur] Manpage packaging change, no runtime impact expected. [Additional Description] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-94.104 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 3196 F pulseaudio /dev/snd/pcmC0D0p: dmitry 3196 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 12:37:42 2024 InstallationDate: Installed on 2022-04-19 (668 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-17-generic N/A linux-backports-modules-6.5.0-17-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.26 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago) dmi.bios.date: 08/15/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052662] Re: move_mount mediation does not detect if source is detached
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2052662 Title: move_mount mediation does not detect if source is detached Status in linux package in Ubuntu: Invalid Status in linux source package in Mantic: Fix Committed Bug description: Impact: In AppArmor mediation, detached mounts are appearing as / when applying mount mediation, which is incorrect and leads to bad AppArmor policy being generated. In addition, the move_mount mediation is not being advertised to userspace, which denies the applications the possibility to respond accordingly. Fix: Fixed upstream by commit 8026e40608b4d552216d2a818ca7080a4264bb44 by preventing move_mont from applying the attach_disconnected flag. Testcase: Check if move_mount file is available in securityfs: $ cat /sys/kernel/security/apparmor/features/mount/move_mount detached Run upstream AppArmor mount tests, which include move_mount mediation. https://gitlab.com/apparmor/apparmor/-/blob/master/tests/regression/apparmor/mount.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051947] Re: Sound: Add rtl quirk of M70-Gen5
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051947 Title: Sound: Add rtl quirk of M70-Gen5 Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When plugin the headset jack, only speaker is identified. [Fix] Add ALC283_FIXUP_HEADSET_MIC quirk to make its headset mic work. [Test] Vendor tested on hardware, headset mic works fine. [Where problems could occur] It may break audio. This commit is merged by stable updates in noble kernel, 5.15 doesn't support this platform, SRU for mantic and oem-6.5. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051947/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055082] Re: IB peer memory feature regressed in 6.5
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2055082 Title: IB peer memory feature regressed in 6.5 Status in linux package in Ubuntu: Won't Fix Status in linux source package in Mantic: Fix Committed Bug description: [Impact] The GPU Direct over Infiniband feature of NVIDIA GPUs no longer works on jammy/hwe kernels that have migrated to 6.5 *except* for the -nvidia kernel, which pulled in support via bug 2049537. We have carried this patch since 5.4 (see bug 1923104). We do not plan to carry this patch into 6.8 or later - we are working on a deprecation post for that to give users some time to migrate. [Test Case] https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/tree/ubuntu_performance_gpudirect_rdma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054699] Re: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2054699 Title: x86: performance: tsc: Extend watchdog check exemption to 4-Sockets platform Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: This is a public version of https://bugs.launchpad.net/bugs/2044822 SRU Justification: [Impact] Fix tsc clocksource on 4 sockets x86 servers was wrongly judged as 'unstable' by 'jiffies' and other watchdogs, and disabled [Fix] cherry-pick 233756a640be x86/tsc: Extend watchdog check exemption to 4-Sockets platform from upstream fixes this [Test Plan] This has been tested by intel, and has been upstreamed for a while. [Where problems could occur] This is a fairly narrow change, and extends a behaviour correction to cover up to 4-socket machines, rather than just 2 socket machines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054773] Re: Fix AMD brightness issue on AUO panel
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2054773 Title: Fix AMD brightness issue on AUO panel Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.5 source package in Jammy: In Progress Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Bug description: [Impact] When change brightness quickly on gnome menu, AUO panel will be stuck in previous brightness. [Fix] The TCON is random hung by PSR-SU. Force enable ffu mode on PSR-SU panel. [Test] Tested on hardware, the brightness is changed as expected. [Where problems could occur] It may break AMD display. The commit is already in v6.8-rc5, the platform is not fully supported in Jammy 5.15, So SRU oem-6.5 and mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2054773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout
This bug is awaiting verification that the linux/6.5.0-27.28 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic- linux' to 'verification-failed-mantic-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-mantic-linux-v2 verification-needed-mantic-linux -- 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/2055685 Title: Cranky update-dkms-versions rollout Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Having a common file for dkms-versions between main kernels and derivatives causes a lot of conflicts during rebase. Solution is to have a dkms-versions per kernels, under debian./dkms-version. While at it, instead of running ./update-dkms-version script, cranky update-dkms-versions was introduced. [Fix] This is needed only in the main kernels. 1. remove update-dkms-version script 2. rename debian/dkms-version with debian.master/dkms-versions 3. Replace debian/dkms-versions references in debian scripts and rules with $(DEBIAN)/dkms-versions Note for derivatives: These changes will be inherited from the parent during cranky rebase. The only change to the cranky process is: instead of using ./update-dkms-versions script, cranky-update-dkms-versions should be used [Test] Build test on cbd. No issue found. [Regression pottential] Owners have tried this last cycle in derivatives and no issues were found. We may see build failures due to wrong dkms versions, but it will be fixed along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054094] Re: linux-tools-common: man page of usbip[d] is misplaced
This bug is awaiting verification that the linux/5.4.0-175.195 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal- linux' to 'verification-failed-focal-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux -- 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/2054094 Title: linux-tools-common: man page of usbip[d] is misplaced Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Released Bug description: [Impact] Just try man uspip, it doesn't work, because the man page file is at /usr/share/man/man1/usbipd.8.gz ^ ^^^ Looks wrong :) [Test Case] $ sudo apt install linux-tools-common $ man usbip No manual entry for usbip [Where Problems Could Occur] Manpage packaging change, no runtime impact expected. [Additional Description] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-tools-common 5.15.0-94.104 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitry 3196 F pulseaudio /dev/snd/pcmC0D0p: dmitry 3196 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 16 12:37:42 2024 InstallationDate: Installed on 2022-04-19 (668 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. XPS 15 9500 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic root=UUID=21336f25-776c-4f5f-b70c-8cf96f1f0d22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.5.0-17-generic N/A linux-backports-modules-6.5.0-17-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.26 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-21 (543 days ago) dmi.bios.date: 08/15/2023 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.1 dmi.board.name: 0XWT2F dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.24.1:bd08/15/2023:br1.24:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0XWT2F:rvrA02:cvnDellInc.:ct10:cvr:sku097D: dmi.product.family: XPS dmi.product.name: XPS 15 9500 dmi.product.sku: 097D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055685] Re: Cranky update-dkms-versions rollout
This bug is awaiting verification that the linux/5.4.0-175.195 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal- linux' to 'verification-failed-focal-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux -- 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/2055685 Title: Cranky update-dkms-versions rollout Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] Having a common file for dkms-versions between main kernels and derivatives causes a lot of conflicts during rebase. Solution is to have a dkms-versions per kernels, under debian./dkms-version. While at it, instead of running ./update-dkms-version script, cranky update-dkms-versions was introduced. [Fix] This is needed only in the main kernels. 1. remove update-dkms-version script 2. rename debian/dkms-version with debian.master/dkms-versions 3. Replace debian/dkms-versions references in debian scripts and rules with $(DEBIAN)/dkms-versions Note for derivatives: These changes will be inherited from the parent during cranky rebase. The only change to the cranky process is: instead of using ./update-dkms-versions script, cranky-update-dkms-versions should be used [Test] Build test on cbd. No issue found. [Regression pottential] Owners have tried this last cycle in derivatives and no issues were found. We may see build failures due to wrong dkms versions, but it will be fixed along the way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055686] Re: Drop ABI checks from kernel build
This bug is awaiting verification that the linux/5.4.0-175.195 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal- linux' to 'verification-failed-focal-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-v2 verification-needed-focal-linux -- 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/2055686 Title: Drop ABI checks from kernel build Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: Drop the internal checks on the kernel ABI, module lists, et al. These checks are now applied after the fact by the workflow manager. This allows us to validate change after the builds complete so we do no waste builds which were correct but not annotated at upload time. NOTE: we still record the ABI data and publish it in linux-buildinfo files. These are used to perform the external validation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055283] Re: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2055283 Title: Intel Bluetooth AX201 needs firmware intel/ibt-0180-4150.sfi Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2055283 [Impact] We have an Lenovo laptop, after installing the oem-ubuntu-22.04 image and booting up, the bluetooth couldn't work at all. Checking the dmesg, the bluetooth driver needs to load the firmware intel/ibt-0180-4150.sfi, but there is no this firmware in the linux-firmware of Jammy, and I also checked the Mantic and Noble, Mandic doesn't have this firmware too, Noble already has the firmware since the upstream linux-firmware integrated the intel/ibt-0180-4150.sfi last year. [Fix] Backport 4 commits from upstream linux-firmware, these 4 commits are all on intel/ibt-0180-4150.sfi|ddc [Test Case] Put the firmware into the /lib/firmware/intel/, reboot the machine, check dmesg, the bluetooth driver loads the firmware successfully, run hciconfig, the hci0 shows up. run checkbox testcase, it could pass. [Checkbox job `com.canonical.certification::bluetooth/detect-output` output] [Where problems could occur] Probably could make the Intel AX201 BT adapter couldn't work, but the possibility is very low, we tested the firmware on different lenovo machines with the BT adapter AX201, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2055283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
marking the kernel task as fixed since noble has 6.8 now. ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
even though this wasn't able to get verified with the mantic kernel, I've gone ahead and released it as the update should not break anything -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056091] Re: package linux-headers-generic-hwe-22.04 6.5.0.21.20 failed to install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.
** Information type changed from Private Security to Public
--
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/2056091
Title:
package linux-headers-generic-hwe-22.04 6.5.0.21.20 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
Status in linux package in Ubuntu:
New
Bug description:
bilmiyorum
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-generic-hwe-22.04 6.5.0.21.20
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: beyzanrsr 1795 F wireplumber
/dev/snd/controlC1: beyzanrsr 1795 F wireplumber
/dev/snd/seq:beyzanrsr 1789 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Mar 5 01:09:41 2024
ErrorMessage: bağımlılık sorunları - yapılandırılmadan bırakılıyor
InstallationDate: Installed on 2023-12-02 (94 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=50c847c3-ad3a-4f4a-847e-fc7c299a1a16 ro quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
SourcePackage: linux
Title: package linux-headers-generic-hwe-22.04 6.5.0.21.20 failed to
install/upgrade: bağımlılık sorunları - yapılandırılmadan bırakılıyor
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/24/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3306
dmi.board.name: JM50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenix:bvrV0.3306:bd08/24/2009:svnAcer:pnAspire5739G:pvrNotApplicable:rvnAcer:rnJM50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:sku:
dmi.product.name: Aspire 5739G
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056091/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
This bug was fixed in the package linux-firmware - 20230919.git3672ccab-0ubuntu2.9 --- linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium * Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP: #2049220) - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) linux-firmware (20230919.git3672ccab-0ubuntu2.8) mantic; urgency=medium * DP connection swap to break eDP behavior on AMD 7735U (LP: #2049758) - SAUCE: Update DCN312 DMCUB firmware linux-firmware (20230919.git3672ccab-0ubuntu2.7) mantic; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] scripts: Fix shellcheck warnings - [Workflow] Add initial gitea workflow file - SAUCE: [Workflow] Disable markdownlint pre-commit hook - SAUCE: [Workflow] check_whence.py: Update list of known files - [Packaging] scripts/generate-changelog: Fix array initialization - [Packaging] control: Add XSBC-Original-Maintainer field - [Packaging] scripts/install-firmware: Fix installation of license files * AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading (LP: #2051636) - amdgpu: update PSP 13.0.4 firmware from 5.7 branch - amdgpu: update GC 11.0.1 firmware from 5.7 branch - amdgpu: update GC 11.0.4 firmware from 5.7 branch - amdgpu: update PSP 13.0.11 firmware from 5.7 branch - amdgpu: update GC 11.0.1 firmware - amdgpu: update PSP 13.0.4 firmware - amdgpu: update VCN 4.0.2 firmware - amdgpu: update GC 11.0.4 firmware - amdgpu: update PSP 13.0.11 firmware * Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP: #2049220) - linux-firmware: update firmware for MT7921 WiFi device - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: #2048977) - ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37 linux-firmware (20230919.git3672ccab-0ubuntu2.6) mantic; urgency=medium * occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110 (LP: #2048853) - iwlwifi: add new FWs from core83-55 release - iwlwifi: fix for the new FWs from core83-55 release - iwlwifi: update gl FW for core80-165 release * WCN6856 Wi-FI Unavailable and no function during suspend stress (LP: #2048977) - ath11k: WCN6855 hw2.0: update board-2.bin - ath11k: WCN6855 hw2.0: update to WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36 -- Juerg Haefliger Wed, 21 Feb 2024 10:41:18 +0100 ** Changed in: linux-firmware (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
linux-firmware (20230919.git3672ccab-0ubuntu2.8) mantic; urgency=medium
* DP connection swap to break eDP behavior on AMD 7735U (LP: #2049758)
- SAUCE: Update DCN312 DMCUB firmware
linux-firmware (20230919.git3672ccab-0ubuntu2.7) mantic; urgency=medium
* Miscellaneous Ubuntu changes
- [Packaging] scripts: Fix shellcheck warnings
- [Workflow] Add initial gitea workflow file
- SAUCE: [Workflow] Disable markdownlint pre-commit hook
- SAUCE: [Workflow] check_whence.py: Update list of known files
- [Packaging] scripts/generate-changelog: Fix array initialization
- [Packaging] control: Add XSBC-Original-Maintainer field
- [Packaging] scripts/install-firmware: Fix installation of license files
* AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading (LP: #2051636)
- amdgpu: update PSP 13.0.4 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware from 5.7 branch
- amdgpu: update GC 11.0.4 firmware from 5.7 branch
- amdgpu: update PSP 13.0.11 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware
- amdgpu: update PSP 13.0.4 firmware
- amdgpu: update VCN 4.0.2 firmware
- amdgpu: update GC 11.0.4 firmware
- amdgpu: update PSP 13.0.11 firmware
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7921 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37
linux-firmware (20230919.git3672ccab-0ubuntu2.6) mantic; urgency=medium
* occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
-- Juerg Haefliger Wed, 21 Feb 2024
10:41:18 +0100
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
linux-firmware (20230919.git3672ccab-0ubuntu2.8) mantic; urgency=medium
* DP connection swap to break eDP behavior on AMD 7735U (LP: #2049758)
- SAUCE: Update DCN312 DMCUB firmware
linux-firmware (20230919.git3672ccab-0ubuntu2.7) mantic; urgency=medium
* Miscellaneous Ubuntu changes
- [Packaging] scripts: Fix shellcheck warnings
- [Workflow] Add initial gitea workflow file
- SAUCE: [Workflow] Disable markdownlint pre-commit hook
- SAUCE: [Workflow] check_whence.py: Update list of known files
- [Packaging] scripts/generate-changelog: Fix array initialization
- [Packaging] control: Add XSBC-Original-Maintainer field
- [Packaging] scripts/install-firmware: Fix installation of license files
* AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading (LP: #2051636)
- amdgpu: update PSP 13.0.4 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware from 5.7 branch
- amdgpu: update GC 11.0.4 firmware from 5.7 branch
- amdgpu: update PSP 13.0.11 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware
- amdgpu: update PSP 13.0.4 firmware
- amdgpu: update VCN 4.0.2 firmware
- amdgpu: update GC 11.0.4 firmware
- amdgpu: update PSP 13.0.11 firmware
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7921 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37
linux-firmware (20230919.git3672ccab-0ubuntu2.6) mantic; urgency=medium
* occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
-- Juerg Haefliger Wed, 21 Feb 2024
10:41:18 +0100
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2048977
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
'hot reset' assert
2nd PCIe reset' assert
Asmedia 'hot reset' deassert
PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
5217b76bed90 ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37")
324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0:
update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git
history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic and
Jammy for oem-6.5 included.
== original bug report ==
Due to a
[Kernel-packages] [Bug 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
linux-firmware (20230919.git3672ccab-0ubuntu2.8) mantic; urgency=medium
* DP connection swap to break eDP behavior on AMD 7735U (LP: #2049758)
- SAUCE: Update DCN312 DMCUB firmware
linux-firmware (20230919.git3672ccab-0ubuntu2.7) mantic; urgency=medium
* Miscellaneous Ubuntu changes
- [Packaging] scripts: Fix shellcheck warnings
- [Workflow] Add initial gitea workflow file
- SAUCE: [Workflow] Disable markdownlint pre-commit hook
- SAUCE: [Workflow] check_whence.py: Update list of known files
- [Packaging] scripts/generate-changelog: Fix array initialization
- [Packaging] control: Add XSBC-Original-Maintainer field
- [Packaging] scripts/install-firmware: Fix installation of license files
* AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading (LP: #2051636)
- amdgpu: update PSP 13.0.4 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware from 5.7 branch
- amdgpu: update GC 11.0.4 firmware from 5.7 branch
- amdgpu: update PSP 13.0.11 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware
- amdgpu: update PSP 13.0.4 firmware
- amdgpu: update VCN 4.0.2 firmware
- amdgpu: update GC 11.0.4 firmware
- amdgpu: update PSP 13.0.11 firmware
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7921 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37
linux-firmware (20230919.git3672ccab-0ubuntu2.6) mantic; urgency=medium
* occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
-- Juerg Haefliger Wed, 21 Feb 2024
10:41:18 +0100
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test
[Kernel-packages] [Bug 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7922 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7922)
linux-firmware (20230919.git3672ccab-0ubuntu2.8) mantic; urgency=medium
* DP connection swap to break eDP behavior on AMD 7735U (LP: #2049758)
- SAUCE: Update DCN312 DMCUB firmware
linux-firmware (20230919.git3672ccab-0ubuntu2.7) mantic; urgency=medium
* Miscellaneous Ubuntu changes
- [Packaging] scripts: Fix shellcheck warnings
- [Workflow] Add initial gitea workflow file
- SAUCE: [Workflow] Disable markdownlint pre-commit hook
- SAUCE: [Workflow] check_whence.py: Update list of known files
- [Packaging] scripts/generate-changelog: Fix array initialization
- [Packaging] control: Add XSBC-Original-Maintainer field
- [Packaging] scripts/install-firmware: Fix installation of license files
* AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading (LP: #2051636)
- amdgpu: update PSP 13.0.4 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware from 5.7 branch
- amdgpu: update GC 11.0.4 firmware from 5.7 branch
- amdgpu: update PSP 13.0.11 firmware from 5.7 branch
- amdgpu: update GC 11.0.1 firmware
- amdgpu: update PSP 13.0.4 firmware
- amdgpu: update VCN 4.0.2 firmware
- amdgpu: update GC 11.0.4 firmware
- amdgpu: update PSP 13.0.11 firmware
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for MT7921 WiFi device
- linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37
linux-firmware (20230919.git3672ccab-0ubuntu2.6) mantic; urgency=medium
* occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start
RT ucode: -110 (LP: #2048853)
- iwlwifi: add new FWs from core83-55 release
- iwlwifi: fix for the new FWs from core83-55 release
- iwlwifi: update gl FW for core80-165 release
* WCN6856 Wi-FI Unavailable and no function during suspend stress (LP:
#2048977)
- ath11k: WCN6855 hw2.0: update board-2.bin
- ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36
-- Juerg Haefliger Wed, 21 Feb 2024
10:41:18 +0100
** Changed in: linux-firmware (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2051636
Title:
AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker
[Fix]
Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and
other prerequisites:
* amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1
firmware")
* amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4
firmware")
* amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2
firmware")
* amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4
firmware")
* amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11
firmware")
[Test Case]
Run stress tool like 3DMark or GravityMark.
[Where problems could occur]
Binary firmware update recommended by chip vendor. No known issue so
far.
[Other Info]
Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy
is also nominated for fix.
== original bug report ==
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker. Also using mantic +
v6.7 hit the hang, so need to update new FWs to fix this issue.
PHX series
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Yes, it seems so! -- 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/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly Status in linux package in Ubuntu: Fix Released Status in linux source package in Mantic: Fix Released Bug description: After the last kernel upgrade, I noticed that, in the S.M.A.R.T. monitor, parameter ID 192 "Power Off Retract Count" increased every time I turned off the system. I also noticed the "click" of the head parking when shutting down the computer. By restarting the computer with previous kernel version (6.5.0-15.15~22.04.1) the issue didn't happen, so I assume it's a kernel bug, that causes it to shut down the computer before hard drive is deactivated ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-17-generic 6.5.0-17.17~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Feb 13 16:35:55 2024 InstallationDate: Installed on 2020-10-02 (1228 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-08-11 (550 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
One other note, I only get the "unexpected memory mapping" error on
amd64. On arm64 machines with 6.5.0-25.25~22.04.1, ThreadSanitizer works
without issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Status in linux-signed-hwe-6.5 package in Ubuntu:
New
Bug description:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an
error similar to:
FATAL: ThreadSanitizer: unexpected memory mapping
0x5c4dc2bcd000-0x5c4dc2bed000
Reverting the kernel back to 6.5.0-21.21~22.04.1 and rebooting makes
the same executables work again.
There are a few older bugs including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308 and
https://github.com/google/sanitizers/issues/503 but these are from
~2015, and about gcc 7 and linux 4.1 so it does not seem to be the
same problem.
A very small program, lifted from
https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual can
be used to show the problem:
$ cat simple-race.c
#include
#include
int Global;
void *Thread1(void *x) {
Global++;
return NULL;
}
void *Thread2(void *x) {
Global--;
return NULL;
}
int main() {
pthread_t t[2];
pthread_create([0], NULL, Thread1, NULL);
pthread_create([1], NULL, Thread2, NULL);
pthread_join(t[0], NULL);
pthread_join(t[1], NULL);
}
$ cc -fsanitize=thread -fPIE -pie -g simple-race.c -o simple-race
$ ./simple-race
FATAL: ThreadSanitizer: unexpected memory mapping
0x5d161227c000-0x5d161227d000
$ uname -a
Linux buildhost 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue
Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
When running that exact same binary, on the same machine, but with
linux 6.5.0-21:
$ ./simple-race
==
WARNING: ThreadSanitizer: data race (pid=19373)
Read of size 4 at 0x560964a2d014 by thread T2:
#0 Thread2 /home/lxc-unpriv/simple-race.c:12 (simple-race+0x12d1)
Previous write of size 4 at 0x560964a2d014 by thread T1:
#0 Thread1 /home/lxc-unpriv/simple-race.c:7 (simple-race+0x128c)
Location is global 'Global' of size 4 at 0x560964a2d014 (simple-
race+0x4014)
Thread T2 (tid=19376, running) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:19 (simple-race+0x1368)
Thread T1 (tid=19375, finished) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:18 (simple-race+0x1347)
SUMMARY: ThreadSanitizer: data race /home/lxc-unpriv/simple-race.c:12 in
Thread2
==
ThreadSanitizer: reported 1 warnings
$ uname -a
Linux buildhost 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri
Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056762/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056718] Re: net: openvswitch: add missing .resv_start_op
** Description changed:
Intro:
==
- When hit a kernel warning when using openvswitch kernel module. Digging into
the source code, we found it's due to the code snippet
- if (WARN_ON(i.cmd >= family->resv_start_op &&
-(i.doit.validate || i.dumpit.validate)))
- return -EINVAL;
+ When hit a kernel warning when loading openvswitch kernel module. Digging
into the source code, we found it's due to the code snippet
+ if (WARN_ON(i.cmd >= family->resv_start_op &&
+ (i.doit.validate || i.dumpit.validate)))
+ return -EINVAL;
- in the gene_validate_ops() in net/netlink/genetlink.c, introduced in
+ in the gene_validate_ops() in net/netlink/genetlink.c, introduced in
108880a07bab genetlink: add iterator for walking family ops
- from buglink
+ from buglink
https://bugs.launchpad.net/bugs/2053155
How to fix:
===
We need to cherry-pick the missing patch
Fixes: e4ba4554209f ("net: openvswitch: add missing .resv_start_op")
Author: Jakub Kicinski
Date: Thu Oct 27 20:25:01 2022 -0700
- net: openvswitch: add missing .resv_start_op
+ net: openvswitch: add missing .resv_start_op
- I missed one of the families in OvS when annotating .resv_start_op.
- This triggers the warning added in commit ce48ebdd5651 ("genetlink:
- limit the use of validation workarounds to old ops").
+ I missed one of the families in OvS when annotating .resv_start_op.
+ This triggers the warning added in commit ce48ebdd5651 ("genetlink:
+ limit the use of validation workarounds to old ops").
- Reported-by: syzbot+40eb8c0447c0e47a7...@syzkaller.appspotmail.com
- Fixes: 9c5d03d36251 ("genetlink: start to validate reserved header bytes")
- Link: https://lore.kernel.org/r/20221028032501.2724270-1-k...@kernel.org
- Signed-off-by: Jakub Kicinski
+ Reported-by: syzbot+40eb8c0447c0e47a7...@syzkaller.appspotmail.com
+ Fixes: 9c5d03d36251 ("genetlink: start to validate reserved header bytes")
+ Link: https://lore.kernel.org/r/20221028032501.2724270-1-k...@kernel.org
+ Signed-off-by: Jakub Kicinski
Thanks!
+
+ How to reproduce:
+ =
+ simply load the openvswitch.ko and dmesg
+
+ [ 1083.518212] WARNING: CPU: 2 PID: 17269 at net/netlink/genetlink.c:554
genl_validate_ops+0x134/0x254
+ ...
+ [ 1083.518306] CPU: 2 PID: 17269 Comm: modprobe Tainted: GW OE
5.15.0-1037.39.10.g319565b-bluefield #g319565b
+ [ 1083.518309] Hardware name: https://www.mellanox.com BlueField
SoC/BlueField SoC, BIOS 4.7.0.13056 Feb 28 2024
+ [ 1083.518311] pstate: 0049 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
+ [ 1083.518313] pc : genl_validate_ops+0x134/0x254
+ [ 1083.518315] lr : genl_validate_ops+0x68/0x254
+ [ 1083.518317] sp : 8a773810
+ [ 1083.518318] x29: 8a773810 x28: 8a773ba0 x27:
b1ea36f87318
+ [ 1083.518321] x26: b1ea36f8cd20 x25: 0001 x24:
b1ea36f8cda8
+ [ 1083.518323] x23: x22: 0001 x21:
b1ea36f87210
+ [ 1083.518325] x20: b1ea36f8b410 x19: 0001 x18:
+ [ 1083.518328] x17: 000d00020008 x16: b1ea4b70c2d0 x15:
003c00010006
+ [ 1083.518330] x14: 68746170 x13: x12:
0001
+ [ 1083.518332] x11: x10: x9 :
b1ea4b709a5c
+ [ 1083.518335] x8 : x7 : x6 :
b1ea4d4218c0
+ [ 1083.518337] x5 : 0004 x4 : x3 :
0001
+ [ 1083.518339] x2 : x1 : x0 :
0003
+ [ 1083.518341] Call trace:
+ [ 1083.518343] genl_validate_ops+0x134/0x254
+ [ 1083.518344] genl_register_family+0x30/0x1f4
+ [ 1083.518347] dp_init+0xd4/0x174 [openvswitch]
+ [ 1083.518360] do_one_initcall+0x4c/0x250
+ [ 1083.518364] do_init_module+0x50/0x260
+ [ 1083.518368] load_module+0x9fc/0xbe0
+ [ 1083.518370] __do_sys_finit_module+0xa8/0x114
+ [ 1083.518372] __arm64_sys_finit_module+0x28/0x3c
+ [ 1083.518375] invoke_syscall+0x78/0x100
+ [ 1083.518379] el0_svc_common.constprop.0+0x54/0x184
+ [ 1083.518381] do_el0_svc+0x30/0xac
+ [ 1083.518383] el0_svc+0x48/0x160
+ [ 1083.518387] el0t_64_sync_handler+0xa4/0x12c
+ [ 1083.518390] el0t_64_sync+0x1a4/0x1a8
+ [ 1083.518392] ---[ end trace ec4279298c2ae7be ]---
+ [ 1083.830668] openvswitch: Open vSwitch switching datapath
** Description changed:
Intro:
==
When hit a kernel warning when loading openvswitch kernel module. Digging
into the source code, we found it's due to the code snippet
if (WARN_ON(i.cmd >= family->resv_start_op &&
(i.doit.validate || i.dumpit.validate)))
return -EINVAL;
in the gene_validate_ops() in net/netlink/genetlink.c, introduced in
108880a07bab genetlink:
[Kernel-packages] [Bug 2056762] [NEW] ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Public bug reported:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an error
similar to:
FATAL: ThreadSanitizer: unexpected memory mapping
0x5c4dc2bcd000-0x5c4dc2bed000
Reverting the kernel back to 6.5.0-21.21~22.04.1 and rebooting makes the
same executables work again.
There are a few older bugs including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308 and
https://github.com/google/sanitizers/issues/503 but these are from
~2015, and about gcc 7 and linux 4.1 so it does not seem to be the same
problem.
A very small program, lifted from
https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual can
be used to show the problem:
$ cat simple-race.c
#include
#include
int Global;
void *Thread1(void *x) {
Global++;
return NULL;
}
void *Thread2(void *x) {
Global--;
return NULL;
}
int main() {
pthread_t t[2];
pthread_create([0], NULL, Thread1, NULL);
pthread_create([1], NULL, Thread2, NULL);
pthread_join(t[0], NULL);
pthread_join(t[1], NULL);
}
$ cc -fsanitize=thread -fPIE -pie -g simple-race.c -o simple-race
$ ./simple-race
FATAL: ThreadSanitizer: unexpected memory mapping 0x5d161227c000-0x5d161227d000
$ uname -a
Linux buildhost 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb
20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
When running that exact same binary, on the same machine, but with linux
6.5.0-21:
$ ./simple-race
==
WARNING: ThreadSanitizer: data race (pid=19373)
Read of size 4 at 0x560964a2d014 by thread T2:
#0 Thread2 /home/lxc-unpriv/simple-race.c:12 (simple-race+0x12d1)
Previous write of size 4 at 0x560964a2d014 by thread T1:
#0 Thread1 /home/lxc-unpriv/simple-race.c:7 (simple-race+0x128c)
Location is global 'Global' of size 4 at 0x560964a2d014 (simple-
race+0x4014)
Thread T2 (tid=19376, running) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:19 (simple-race+0x1368)
Thread T1 (tid=19375, finished) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:18 (simple-race+0x1347)
SUMMARY: ThreadSanitizer: data race /home/lxc-unpriv/simple-race.c:12 in Thread2
==
ThreadSanitizer: reported 1 warnings
$ uname -a
Linux buildhost 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb
9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
** Affects: linux-signed-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Status in linux-signed-hwe-6.5 package in Ubuntu:
New
Bug description:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an
error similar to:
FATAL: ThreadSanitizer: unexpected memory mapping
0x5c4dc2bcd000-0x5c4dc2bed000
Reverting the kernel back to 6.5.0-21.21~22.04.1 and rebooting makes
the same executables work again.
There are a few older bugs including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308 and
https://github.com/google/sanitizers/issues/503 but these are from
~2015, and about gcc 7 and linux 4.1 so it does not seem to be the
same problem.
A very small program, lifted from
https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual can
be used to show the problem:
$ cat simple-race.c
#include
#include
int Global;
void *Thread1(void *x) {
Global++;
return NULL;
}
void *Thread2(void *x) {
Global--;
return NULL;
}
int main() {
pthread_t t[2];
pthread_create([0], NULL, Thread1, NULL);
pthread_create([1], NULL, Thread2, NULL);
pthread_join(t[0], NULL);
pthread_join(t[1], NULL);
}
$ cc -fsanitize=thread -fPIE -pie -g simple-race.c -o simple-race
$ ./simple-race
FATAL: ThreadSanitizer: unexpected memory mapping
0x5d161227c000-0x5d161227d000
$ uname -a
Linux buildhost 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue
Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
When running that exact same binary, on the same machine, but with
linux 6.5.0-21:
$ ./simple-race
==
WARNING: ThreadSanitizer: data race (pid=19373)
Read of size 4 at 0x560964a2d014 by thread T2:
#0 Thread2 /home/lxc-unpriv/simple-race.c:12
[Kernel-packages] [Bug 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Note that similar to the older gcc and upstream sanitizer bugs, this
problem may be caused by some kernel API now returning a slightly
different result, so it could be debatable whether the issue should be
fixed in ThreadSanitizer, or in the kernel itself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Status in linux-signed-hwe-6.5 package in Ubuntu:
New
Bug description:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an
error similar to:
FATAL: ThreadSanitizer: unexpected memory mapping
0x5c4dc2bcd000-0x5c4dc2bed000
Reverting the kernel back to 6.5.0-21.21~22.04.1 and rebooting makes
the same executables work again.
There are a few older bugs including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308 and
https://github.com/google/sanitizers/issues/503 but these are from
~2015, and about gcc 7 and linux 4.1 so it does not seem to be the
same problem.
A very small program, lifted from
https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual can
be used to show the problem:
$ cat simple-race.c
#include
#include
int Global;
void *Thread1(void *x) {
Global++;
return NULL;
}
void *Thread2(void *x) {
Global--;
return NULL;
}
int main() {
pthread_t t[2];
pthread_create([0], NULL, Thread1, NULL);
pthread_create([1], NULL, Thread2, NULL);
pthread_join(t[0], NULL);
pthread_join(t[1], NULL);
}
$ cc -fsanitize=thread -fPIE -pie -g simple-race.c -o simple-race
$ ./simple-race
FATAL: ThreadSanitizer: unexpected memory mapping
0x5d161227c000-0x5d161227d000
$ uname -a
Linux buildhost 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue
Feb 20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
When running that exact same binary, on the same machine, but with
linux 6.5.0-21:
$ ./simple-race
==
WARNING: ThreadSanitizer: data race (pid=19373)
Read of size 4 at 0x560964a2d014 by thread T2:
#0 Thread2 /home/lxc-unpriv/simple-race.c:12 (simple-race+0x12d1)
Previous write of size 4 at 0x560964a2d014 by thread T1:
#0 Thread1 /home/lxc-unpriv/simple-race.c:7 (simple-race+0x128c)
Location is global 'Global' of size 4 at 0x560964a2d014 (simple-
race+0x4014)
Thread T2 (tid=19376, running) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:19 (simple-race+0x1368)
Thread T1 (tid=19375, finished) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:18 (simple-race+0x1347)
SUMMARY: ThreadSanitizer: data race /home/lxc-unpriv/simple-race.c:12 in
Thread2
==
ThreadSanitizer: reported 1 warnings
$ uname -a
Linux buildhost 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri
Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056762/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056757] [NEW] The booting process blocked in 6.5.0-25 during systemd-resolve start phase
Public bug reported:
Since booting in 6.5.0-25-generic some kworker thread were stuck. This
problem with iwlwifi was new. Booting back in 6.5.0-21-generic solved
the problem.
This was a suspicious new error:
```
kernel: iwlwifi :3b:00.0: Error sending MCC_UPDATE_CMD: time out after
2000ms.
kernel: iwlwifi :3b:00.0: Current CMD queue read_ptr 16 write_ptr 17
kernel: iwlwifi :3b:00.0: DEVICE_ENABLED bit is not set. Aborting dump.
kernel: iwlwifi :3b:00.0: Queue 0 is active on fifo 7 and stuck for 2500
ms. SW [16, 17] HW [17, 17] FH TRB=0x0700010
```
example of blocked kworkers:
```
kernel: INFO: task kworker/0:1:9 blocked for more than 120 seconds.
kernel: Not tainted 6.5.0-25-generic #25-Ubuntu
kernel: task:kworker/0:1 state:D stack:0 pid:9 ppid:2
flags:0x4000
kernel: Workqueue: events cfg80211_rfkill_block_work [cfg80211]
```
```
kernel: INFO: task irq/173-iwlwifi:945 blocked for more than 120 seconds.
kernel: task:irq/173-iwlwifi state:D stack:0 pid:945 ppid:2
flags:0x4000
```
```
kernel: INFO: task modprobe:947 blocked for more than 120 seconds.
kernel: Not tainted 6.5.0-25-generic #25-Ubuntu
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
kernel: task:modprobestate:D stack:0 pid:947 ppid:583
flags:0x4002
```
```
kernel: INFO: task kworker/u32:10:1016 blocked for more than 120 seconds.
kernel: task:kworker/u32:10 state:D stack:0 pid:1016 ppid:2
flags:0x4000
kernel: Workqueue: events_power_efficient reg_check_chans_work [cfg80211]
```
```
kernel: INFO: task systemd-resolve:1093 blocked for more than 120 seconds.
kernel: task:systemd-resolve state:D stack:0 pid:1093 ppid:1
flags:0x0006
```
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-modules-extra-6.5.0-25-generic 6.5.0-25.25
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 11 11:41:51 2024
Dependencies:
linux-modules-6.5.0-25-generic 6.5.0-25.25
wireless-regdb 2022.06.06-0ubuntu2
EcryptfsInUse: Yes
InstallationDate: Installed on 2020-10-21 (1237 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-21-generic
root=/dev/mapper/vgubuntu-root ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-21-generic N/A
linux-backports-modules-6.5.0-21-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.5
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-13 (119 days ago)
dmi.bios.date: 10/11/2021
dmi.bios.release: 1.14
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.1
dmi.board.name: 024X86
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.1:bd10/11/2021:br1.14:svnDellInc.:pnPrecision5540:pvr:rvnDellInc.:rn024X86:rvrA04:cvnDellInc.:ct10:cvr:sku0906:
dmi.product.family: Precision
dmi.product.name: Precision 5540
dmi.product.sku: 0906
dmi.sys.vendor: Dell Inc.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056757
Title:
The booting process blocked in 6.5.0-25 during systemd-resolve start
phase
Status in linux package in Ubuntu:
New
Bug description:
Since booting in 6.5.0-25-generic some kworker thread were stuck. This
problem with iwlwifi was new. Booting back in 6.5.0-21-generic solved
the problem.
This was a suspicious new error:
```
kernel: iwlwifi :3b:00.0: Error sending MCC_UPDATE_CMD: time out after
2000ms.
kernel: iwlwifi :3b:00.0: Current CMD queue read_ptr 16 write_ptr 17
kernel: iwlwifi :3b:00.0: DEVICE_ENABLED bit is not set. Aborting dump.
kernel: iwlwifi :3b:00.0: Queue 0 is active on fifo 7 and stuck for 2500
ms. SW [16, 17] HW [17, 17] FH TRB=0x0700010
```
example of blocked kworkers:
```
kernel: INFO: task kworker/0:1:9 blocked for more than 120 seconds.
kernel: Not tainted 6.5.0-25-generic #25-Ubuntu
kernel: task:kworker/0:1 state:D stack:0 pid:9 ppid:2
flags:0x4000
kernel: Workqueue: events cfg80211_rfkill_block_work [cfg80211]
```
```
kernel: INFO: task irq/173-iwlwifi:945 blocked for more than 120 seconds.
kernel: task:irq/173-iwlwifi state:D stack:0 pid:945 ppid:2
flags:0x4000
```
```
kernel: INFO: task modprobe:947 blocked
[Kernel-packages] [Bug 2054121] Re: Random Freezing
Ok, running 6.8.
uname -r
6.8.0-060800rc7-generic
--
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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055037] Re: [amdgpu] My screen randomly starts flickering
Hello again Daniel, Thank you very again much for your help and again, my apologies for being unable to reply to your sooner. I have found recently that my laptop, the Lenovo V145-15AST has stopped suffering from a flickering screen. I have used the laptop extensively for normal work and the problem has disappeared. There have been two updates during the course of our discussion. Although I'm finding it difficult to give you any detailed information as typing "lsb_release -a" at the terminal only results in; No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.4 LTS Release:22.04 Codename: jammy I'm not sure how to let you know what was installed during the two updates, as I'm sure that would help. Many thanks again for all of your help in this matter, Nick. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2055037 Title: [amdgpu] My screen randomly starts flickering Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of error, a black screen with a few lines at the top. Selecting "Start linux mint in compatability mode" does boot to mint but then the trackpad does not work. I have included this reference to Linux Mint as I believe mint is based on Ubuntu. Many thanks, Nick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:33:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39ec] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [17aa:39ec] InstallationDate: Installed on 2024-02-24 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 81MT ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=e078d5fc-6eaf-4e92-9388-969fa8b6f6db ro 1915.enable_psr=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2021 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN27WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.27 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN27WW(V2.06):bd01/12/2021:br2.27:efr2.27:svnLENOVO:pn81MT:pvrLenovoV145-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau:
[Kernel-packages] [Bug 2056748] Re: Display Corruption on Chuwi Minibook X N100 (Regression)
** Description changed: Ubuntu Release: 24.04 Noble Numbat (development branch) Package: linux-image-6.8.0-11-generic Version: 6.8.0-11.11 What was expected: - An image to be displayed on the screen of the laptop free from corruption. + An image to be displayed on the integrated screen of the laptop free from corruption. What happened instead: - When booting using the specified kernel, the screen displays a corrupted image. A photo of the corruption has been attached. The photo of the corruption is of the laptop running a different distro (Fedora) but the behavior is identical and is common across many distros. + When booting using the specified kernel, the integrated screen displays a corrupted image. A photo of the corruption has been attached. The photo of the corruption is of the laptop running a different distro (Fedora) but the behavior is identical and is common across many distros. + This display corruption occurs only on the laptop's integrated display. No corruption is present on external displays. This display corruption was not present when using linux-image-6.6.0-14-generic. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/seq:thomas 1773 F pipewire - /dev/snd/controlC0: thomas 1777 F wireplumber + USERPID ACCESS COMMAND + /dev/snd/seq:thomas 1773 F pipewire + /dev/snd/controlC0: thomas 1777 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 20:35:42 2024 InstallationDate: Installed on 2024-03-02 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240223) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 002: ID 1b0a:2bc9 HYGD-220831-A Hy-Usb2.0-1*MIC - Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 1b0a:2bc9 HYGD-220831-A Hy-Usb2.0-1*MIC + Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd MiniBook X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash fbcon=rotate:1 video=DSI-1:panel_orientation=right_side_up RelatedPackageVersions: - linux-restricted-modules-6.6.0-14-generic N/A - linux-backports-modules-6.6.0-14-generic N/A - linux-firmware20240202.git36777504-0ubuntu1 + linux-restricted-modules-6.6.0-14-generic N/A + linux-backports-modules-6.6.0-14-generic N/A + linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2023 dmi.bios.release: 2.3 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: DNN20A V2.03 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.15 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrDNN20AV2.03:bd12/28/2023:br2.3:efr0.15:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnMiniBookX:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MiniBook X dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd -- 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/2056748 Title: Display Corruption on Chuwi Minibook X N100 (Regression) Status in linux package in Ubuntu: New Bug description: Ubuntu Release: 24.04 Noble Numbat (development branch) Package: linux-image-6.8.0-11-generic Version: 6.8.0-11.11 What was expected: An image to be displayed on the integrated screen of the laptop free from corruption. What happened instead: When booting using the specified kernel, the integrated screen displays a corrupted image. A photo of the corruption has been attached. The photo of the corruption is of the laptop running a different distro (Fedora) but the behavior is identical and is common across many distros.
[Kernel-packages] [Bug 2056748] Re: Display Corruption on Chuwi Minibook X N100 (Regression)
** Attachment added: "dmesg running kernel 6.8.0-11" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056748/+attachment/5754804/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056748 Title: Display Corruption on Chuwi Minibook X N100 (Regression) Status in linux package in Ubuntu: New Bug description: Ubuntu Release: 24.04 Noble Numbat (development branch) Package: linux-image-6.8.0-11-generic Version: 6.8.0-11.11 What was expected: An image to be displayed on the screen of the laptop free from corruption. What happened instead: When booting using the specified kernel, the screen displays a corrupted image. A photo of the corruption has been attached. The photo of the corruption is of the laptop running a different distro (Fedora) but the behavior is identical and is common across many distros. This display corruption was not present when using linux-image-6.6.0-14-generic. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:thomas 1773 F pipewire /dev/snd/controlC0: thomas 1777 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 20:35:42 2024 InstallationDate: Installed on 2024-03-02 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240223) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1b0a:2bc9 HYGD-220831-A Hy-Usb2.0-1*MIC Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd MiniBook X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash fbcon=rotate:1 video=DSI-1:panel_orientation=right_side_up RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2023 dmi.bios.release: 2.3 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: DNN20A V2.03 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.15 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrDNN20AV2.03:bd12/28/2023:br2.3:efr0.15:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnMiniBookX:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MiniBook X dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056635] Re: Wifi wlan0 device not present on Raspberry Pi 3A+
** Changed in: ubuntu Status: New => Invalid ** Package changed: linux (Ubuntu) => linux-raspi (Ubuntu) ** Tags added: kern-9639 -- 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/2056635 Title: Wifi wlan0 device not present on Raspberry Pi 3A+ Status in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: Ubuntu Noble beta does not currently bring up the wlan0 wifi interface on the Raspberry Pi 3A+. uname -a Linux ubuntu 6.8.0-1001-raspi #1-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 27 16:56:12 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux No wlan0 interface is present in 'ip a' output and the device isn't listed under /sys/class/net/. Netplan therefore fails to configure a connection to an access point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056748] [NEW] Display Corruption on Chuwi Minibook X N100 (Regression)
Public bug reported: Ubuntu Release: 24.04 Noble Numbat (development branch) Package: linux-image-6.8.0-11-generic Version: 6.8.0-11.11 What was expected: An image to be displayed on the screen of the laptop free from corruption. What happened instead: When booting using the specified kernel, the screen displays a corrupted image. A photo of the corruption has been attached. The photo of the corruption is of the laptop running a different distro (Fedora) but the behavior is identical and is common across many distros. This display corruption was not present when using linux-image-6.6.0-14-generic. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:thomas 1773 F pipewire /dev/snd/controlC0: thomas 1777 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 20:35:42 2024 InstallationDate: Installed on 2024-03-02 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240223) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1b0a:2bc9 HYGD-220831-A Hy-Usb2.0-1*MIC Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: CHUWI Innovation And Technology(ShenZhen)co.,Ltd MiniBook X ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash fbcon=rotate:1 video=DSI-1:panel_orientation=right_side_up RelatedPackageVersions: linux-restricted-modules-6.6.0-14-generic N/A linux-backports-modules-6.6.0-14-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2023 dmi.bios.release: 2.3 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: DNN20A V2.03 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 0.15 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrDNN20AV2.03:bd12/28/2023:br2.3:efr0.15:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnMiniBookX:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MiniBook X dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble ** Attachment added: "Photo of the display corruption" https://bugs.launchpad.net/bugs/2056748/+attachment/5754786/+files/IMG_20240224_135424_422.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056748 Title: Display Corruption on Chuwi Minibook X N100 (Regression) Status in linux package in Ubuntu: New Bug description: Ubuntu Release: 24.04 Noble Numbat (development branch) Package: linux-image-6.8.0-11-generic Version: 6.8.0-11.11 What was expected: An image to be displayed on the screen of the laptop free from corruption. What happened instead: When booting using the specified kernel, the screen displays a corrupted image. A photo of the corruption has been attached. The photo of the corruption is of the laptop running a different distro (Fedora) but the behavior is identical and is common across many distros. This display corruption was not present when using linux-image-6.6.0-14-generic. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:thomas 1773 F pipewire /dev/snd/controlC0: thomas 1777 F wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 20:35:42 2024 InstallationDate: Installed on 2024-03-02 (9 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240223) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 1b0a:2bc9 HYGD-220831-A Hy-Usb2.0-1*MIC Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 002 Device
[Kernel-packages] [Bug 2056628] Re: quando uso un dispositivo usb mi si cancella l input del touchpad ho provato con molti metodi ma niente /when I use a USB device the touchpad input is canceled I ha
** Summary changed: - quando uso un dispositivo usb mi si cancella l input del touchpad ho provato con molti metodi ma niente /when I use a USB device the touchpad input is canceled I have tried many methods but nothing + mi si cancella l input del touchpad ho provato con molti metodi ma niente / the touchpad input is canceled I have tried many methods but nothing ** Description changed: - quando uso un dispositivo usb mi si cancella l input del touchpad ho - provato con molti metodi ma niente /when I use a USB device the touchpad - input is canceled I have tried many methods but nothing + l input del touchpad ho provato con molti metodi ma niente / the touchpad input is canceled I have tried many methods but nothing + dopo poco l installazione di ubuntu il touchpad funziona ma dopo qualche ora o giorno si cancella automaticamente fra gli input ho bisogno del touchpad visto che non uso mouse + il mouse esterno funziona e ho provato a vedere molti altri report con i vari fix ma nulla ho provato tutto ad aggiungerlo manualmente o altro I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= - H: Handlers=event0 + H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= - H: Handlers=kbd event1 + H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= - H: Handlers=kbd event2 + H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= - H: Handlers=kbd event3 + H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= - H: Handlers=sysrq kbd event4 leds + H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:13/LNXVIDEO:00/input/input6 U: Uniq= - H: Handlers=kbd event5 + H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:01/input/input7 U: Uniq= - H: Handlers=kbd event6 + H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor=1043 Product= Version= N: Name="Asus Wireless Radio Control" P: Phys=asus-wireless/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/ATK4001:00/input/input9 U: Uniq= - H: Handlers=rfkill kbd event7 + H: Handlers=rfkill kbd event7 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Asus WMI hotkeys" P: Phys=asus-nb-wmi/input0 S: Sysfs=/devices/platform/asus-nb-wmi/input/input10 U: Uniq= - H: Handlers=rfkill kbd event8 + H: Handlers=rfkill kbd event8 B: PROP=0 B: EV=100013 B: KEY=400 10008 40 0 0 0 181606f00900c00 8280027801701000 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA ATI HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:01.1/sound/card0/input11 U: Uniq= - H: Handlers=event9 + H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:14.2/sound/card1/input12 U: Uniq= - H: Handlers=event10 + H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HD-Audio Generic Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:14.2/sound/card1/input13 U: Uniq= - H: Handlers=event11 + H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0003 Vendor=046d Product=c08b Version=0111 N: Name="Logitech G502 HERO Gaming Mouse" P: Phys=usb-:00:10.0-2/input0 S: Sysfs=/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.0/0003:046D:C08B.0005/input/input25 U: Uniq=1292314A3635 - H: Handlers=mouse0 event12 + H: Handlers=mouse0 event12 B: PROP=0
[Kernel-packages] [Bug 2056743] [NEW] Keyboard stops working after suspend on Dell XPS 13
Public bug reported: The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100. The issue seems to be identical to the problem reported for 6.7.0 here: https://bbs.archlinux.org/viewtopic.php?id=292203 On the page linked above is says a patch was submitted 2024-01-26 and the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17. I'm concerned that this still needs fixing in the 5.xxx kernel branch. Touchpad does not freeze and mouse-control of windows still works, so it's different from a bug reported elsewhere. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-102-generic 5.15.0-102.112 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2494 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 09:54:23 2024 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (2018 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-100-generic root=UUID=fb8af021-9abd-4e95-9458-7a78ac12bb46 ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-100-generic N/A linux-backports-modules-5.15.0-100-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.29 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2022 dmi.bios.release: 1.21 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.0 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.0:bd07/06/2022:br1.21:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-09-08T10:23:15.468001 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed -- 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/2056743 Title: Keyboard stops working after suspend on Dell XPS 13 Status in linux package in Ubuntu: New Bug description: The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100. The issue seems to be identical to the problem reported for 6.7.0 here: https://bbs.archlinux.org/viewtopic.php?id=292203 On the page linked above is says a patch was submitted 2024-01-26 and the problem solved 2024-03-04 in linux 6.7.5 or linux-lts 6.6.17. I'm concerned that this still needs fixing in the 5.xxx kernel branch. Touchpad does not freeze and mouse-control of windows still works, so it's different from a bug reported elsewhere. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-102-generic 5.15.0-102.112 ProcVersionSignature: Ubuntu 5.15.0-100.110-generic 5.15.143 Uname: Linux 5.15.0-100-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: axel 2494 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 11 09:54:23 2024 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=461ac6d0-c7ab-4f93-b97d-4d7b3f14f378 InstallationDate: Installed on 2018-08-31 (2018 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD
[Kernel-packages] [Bug 2052623] Re: Jammy update: v6.1.76 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35 --- linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090) * Jammy update: v6.1.78 upstream stable release (LP: #2054541) - ext4: regenerate buddy after block freeing failed if under fc replay - dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools - dmaengine: ti: k3-udma: Report short packet errors - dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA - dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA - phy: renesas: rcar-gen3-usb2: Fix returning wrong error code - dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV - phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP - cifs: failure to add channel on iface should bump up weight - drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case - drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case - drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup - net: stmmac: xgmac: fix handling of DPP safety error for DMA channels - wifi: mac80211: fix waiting for beacons logic - netdevsim: avoid potential loop in nsim_dev_trap_report_work() - net: atlantic: Fix DMA mapping for PTP hwts ring - selftests: net: cut more slack for gro fwd tests. - selftests: net: avoid just another constant wait - tunnels: fix out of bounds access when building IPv6 PMTU error - atm: idt77252: fix a memleak in open_card_ubr0 - octeontx2-pf: Fix a memleak otx2_sq_init - hwmon: (aspeed-pwm-tacho) mutex for tach reading - hwmon: (coretemp) Fix out-of-bounds memory access - hwmon: (coretemp) Fix bogus core_id to attr name mapping - inet: read sk->sk_family once in inet_recv_error() - drm/i915/gvt: Fix uninitialized variable in handle_mmio() - rxrpc: Fix response to PING RESPONSE ACKs to a dead call - tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() - af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. - ppp_async: limit MRU to 64K - selftests: cmsg_ipv6: repeat the exact packet - netfilter: nft_compat: narrow down revision to unsigned 8-bits - netfilter: nft_compat: reject unused compat flag - netfilter: nft_compat: restrict match/target protocol to u16 - drm/amd/display: Implement bounds check for stream encoder creation in DCN301 - netfilter: nft_ct: reject direction for ct id - netfilter: nft_set_pipapo: store index in scratch maps - netfilter: nft_set_pipapo: add helper to release pcpu scratch area - netfilter: nft_set_pipapo: remove scratch_aligned pointer - fs/ntfs3: Fix an NULL dereference bug - scsi: core: Move scsi_host_busy() out of host lock if it is for per-command - blk-iocost: Fix an UBSAN shift-out-of-bounds warning - fs: dlm: don't put dlm_local_addrs on heap - mtd: parsers: ofpart: add workaround for #size-cells 0 - ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision - ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter - ALSA: usb-audio: add quirk for RODE NT-USB+ - USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e - USB: serial: option: add Fibocom FM101-GL variant - USB: serial: cp210x: add ID for IMST iM871A-USB - usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK - usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK - hrtimer: Report offline hrtimer enqueue - Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU - Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID - io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers - Revert "ASoC: amd: Add new dmi entries for acp5x platform" - vhost: use kzalloc() instead of kmalloc() followed by memset() - RDMA/irdma: Fix support for 64k pages - f2fs: add helper to check compression level - block: treat poll queue enter similarly to timeouts - clocksource: Skip watchdog check for large watchdog intervals - net: stmmac: xgmac: use #define for string constants - ALSA: usb-audio: Sort quirk table entries - net: stmmac: xgmac: fix a typo of register name in DPP safety handling - netfilter: nft_set_rbtree: skip end interval element from gc - Linux 6.1.78 - upstream stable to v6.1.78 * There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms (LP: #2054487) - ALSA: hda/realtek: add IDs for Dell dual spk platform * Jammy update: v6.1.77 upstream stable release (LP: #2052631) - asm-generic: make sparse happy with odd-sized put_unaligned_*() - powerpc/mm: Fix null-pointer dereference in pgtable_cache_add - arm64: irq: set the correct node for VMAP stack - drivers/perf: pmuv3: don't expose SW_INCR event
[Kernel-packages] [Bug 2052599] Re: Jammy update: v6.1.74 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35 --- linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090) * Jammy update: v6.1.78 upstream stable release (LP: #2054541) - ext4: regenerate buddy after block freeing failed if under fc replay - dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools - dmaengine: ti: k3-udma: Report short packet errors - dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA - dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA - phy: renesas: rcar-gen3-usb2: Fix returning wrong error code - dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV - phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP - cifs: failure to add channel on iface should bump up weight - drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case - drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case - drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup - net: stmmac: xgmac: fix handling of DPP safety error for DMA channels - wifi: mac80211: fix waiting for beacons logic - netdevsim: avoid potential loop in nsim_dev_trap_report_work() - net: atlantic: Fix DMA mapping for PTP hwts ring - selftests: net: cut more slack for gro fwd tests. - selftests: net: avoid just another constant wait - tunnels: fix out of bounds access when building IPv6 PMTU error - atm: idt77252: fix a memleak in open_card_ubr0 - octeontx2-pf: Fix a memleak otx2_sq_init - hwmon: (aspeed-pwm-tacho) mutex for tach reading - hwmon: (coretemp) Fix out-of-bounds memory access - hwmon: (coretemp) Fix bogus core_id to attr name mapping - inet: read sk->sk_family once in inet_recv_error() - drm/i915/gvt: Fix uninitialized variable in handle_mmio() - rxrpc: Fix response to PING RESPONSE ACKs to a dead call - tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() - af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. - ppp_async: limit MRU to 64K - selftests: cmsg_ipv6: repeat the exact packet - netfilter: nft_compat: narrow down revision to unsigned 8-bits - netfilter: nft_compat: reject unused compat flag - netfilter: nft_compat: restrict match/target protocol to u16 - drm/amd/display: Implement bounds check for stream encoder creation in DCN301 - netfilter: nft_ct: reject direction for ct id - netfilter: nft_set_pipapo: store index in scratch maps - netfilter: nft_set_pipapo: add helper to release pcpu scratch area - netfilter: nft_set_pipapo: remove scratch_aligned pointer - fs/ntfs3: Fix an NULL dereference bug - scsi: core: Move scsi_host_busy() out of host lock if it is for per-command - blk-iocost: Fix an UBSAN shift-out-of-bounds warning - fs: dlm: don't put dlm_local_addrs on heap - mtd: parsers: ofpart: add workaround for #size-cells 0 - ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision - ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter - ALSA: usb-audio: add quirk for RODE NT-USB+ - USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e - USB: serial: option: add Fibocom FM101-GL variant - USB: serial: cp210x: add ID for IMST iM871A-USB - usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK - usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK - hrtimer: Report offline hrtimer enqueue - Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU - Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID - io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers - Revert "ASoC: amd: Add new dmi entries for acp5x platform" - vhost: use kzalloc() instead of kmalloc() followed by memset() - RDMA/irdma: Fix support for 64k pages - f2fs: add helper to check compression level - block: treat poll queue enter similarly to timeouts - clocksource: Skip watchdog check for large watchdog intervals - net: stmmac: xgmac: use #define for string constants - ALSA: usb-audio: Sort quirk table entries - net: stmmac: xgmac: fix a typo of register name in DPP safety handling - netfilter: nft_set_rbtree: skip end interval element from gc - Linux 6.1.78 - upstream stable to v6.1.78 * There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms (LP: #2054487) - ALSA: hda/realtek: add IDs for Dell dual spk platform * Jammy update: v6.1.77 upstream stable release (LP: #2052631) - asm-generic: make sparse happy with odd-sized put_unaligned_*() - powerpc/mm: Fix null-pointer dereference in pgtable_cache_add - arm64: irq: set the correct node for VMAP stack - drivers/perf: pmuv3: don't expose SW_INCR event
[Kernel-packages] [Bug 2052622] Re: Jammy update: v6.1.75 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35 --- linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090) * Jammy update: v6.1.78 upstream stable release (LP: #2054541) - ext4: regenerate buddy after block freeing failed if under fc replay - dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools - dmaengine: ti: k3-udma: Report short packet errors - dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA - dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA - phy: renesas: rcar-gen3-usb2: Fix returning wrong error code - dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV - phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP - cifs: failure to add channel on iface should bump up weight - drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case - drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case - drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup - net: stmmac: xgmac: fix handling of DPP safety error for DMA channels - wifi: mac80211: fix waiting for beacons logic - netdevsim: avoid potential loop in nsim_dev_trap_report_work() - net: atlantic: Fix DMA mapping for PTP hwts ring - selftests: net: cut more slack for gro fwd tests. - selftests: net: avoid just another constant wait - tunnels: fix out of bounds access when building IPv6 PMTU error - atm: idt77252: fix a memleak in open_card_ubr0 - octeontx2-pf: Fix a memleak otx2_sq_init - hwmon: (aspeed-pwm-tacho) mutex for tach reading - hwmon: (coretemp) Fix out-of-bounds memory access - hwmon: (coretemp) Fix bogus core_id to attr name mapping - inet: read sk->sk_family once in inet_recv_error() - drm/i915/gvt: Fix uninitialized variable in handle_mmio() - rxrpc: Fix response to PING RESPONSE ACKs to a dead call - tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() - af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. - ppp_async: limit MRU to 64K - selftests: cmsg_ipv6: repeat the exact packet - netfilter: nft_compat: narrow down revision to unsigned 8-bits - netfilter: nft_compat: reject unused compat flag - netfilter: nft_compat: restrict match/target protocol to u16 - drm/amd/display: Implement bounds check for stream encoder creation in DCN301 - netfilter: nft_ct: reject direction for ct id - netfilter: nft_set_pipapo: store index in scratch maps - netfilter: nft_set_pipapo: add helper to release pcpu scratch area - netfilter: nft_set_pipapo: remove scratch_aligned pointer - fs/ntfs3: Fix an NULL dereference bug - scsi: core: Move scsi_host_busy() out of host lock if it is for per-command - blk-iocost: Fix an UBSAN shift-out-of-bounds warning - fs: dlm: don't put dlm_local_addrs on heap - mtd: parsers: ofpart: add workaround for #size-cells 0 - ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision - ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter - ALSA: usb-audio: add quirk for RODE NT-USB+ - USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e - USB: serial: option: add Fibocom FM101-GL variant - USB: serial: cp210x: add ID for IMST iM871A-USB - usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK - usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK - hrtimer: Report offline hrtimer enqueue - Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU - Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID - io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers - Revert "ASoC: amd: Add new dmi entries for acp5x platform" - vhost: use kzalloc() instead of kmalloc() followed by memset() - RDMA/irdma: Fix support for 64k pages - f2fs: add helper to check compression level - block: treat poll queue enter similarly to timeouts - clocksource: Skip watchdog check for large watchdog intervals - net: stmmac: xgmac: use #define for string constants - ALSA: usb-audio: Sort quirk table entries - net: stmmac: xgmac: fix a typo of register name in DPP safety handling - netfilter: nft_set_rbtree: skip end interval element from gc - Linux 6.1.78 - upstream stable to v6.1.78 * There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms (LP: #2054487) - ALSA: hda/realtek: add IDs for Dell dual spk platform * Jammy update: v6.1.77 upstream stable release (LP: #2052631) - asm-generic: make sparse happy with odd-sized put_unaligned_*() - powerpc/mm: Fix null-pointer dereference in pgtable_cache_add - arm64: irq: set the correct node for VMAP stack - drivers/perf: pmuv3: don't expose SW_INCR event
[Kernel-packages] [Bug 2052631] Re: Jammy update: v6.1.77 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35 --- linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090) * Jammy update: v6.1.78 upstream stable release (LP: #2054541) - ext4: regenerate buddy after block freeing failed if under fc replay - dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools - dmaengine: ti: k3-udma: Report short packet errors - dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA - dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA - phy: renesas: rcar-gen3-usb2: Fix returning wrong error code - dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV - phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP - cifs: failure to add channel on iface should bump up weight - drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case - drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case - drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup - net: stmmac: xgmac: fix handling of DPP safety error for DMA channels - wifi: mac80211: fix waiting for beacons logic - netdevsim: avoid potential loop in nsim_dev_trap_report_work() - net: atlantic: Fix DMA mapping for PTP hwts ring - selftests: net: cut more slack for gro fwd tests. - selftests: net: avoid just another constant wait - tunnels: fix out of bounds access when building IPv6 PMTU error - atm: idt77252: fix a memleak in open_card_ubr0 - octeontx2-pf: Fix a memleak otx2_sq_init - hwmon: (aspeed-pwm-tacho) mutex for tach reading - hwmon: (coretemp) Fix out-of-bounds memory access - hwmon: (coretemp) Fix bogus core_id to attr name mapping - inet: read sk->sk_family once in inet_recv_error() - drm/i915/gvt: Fix uninitialized variable in handle_mmio() - rxrpc: Fix response to PING RESPONSE ACKs to a dead call - tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() - af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. - ppp_async: limit MRU to 64K - selftests: cmsg_ipv6: repeat the exact packet - netfilter: nft_compat: narrow down revision to unsigned 8-bits - netfilter: nft_compat: reject unused compat flag - netfilter: nft_compat: restrict match/target protocol to u16 - drm/amd/display: Implement bounds check for stream encoder creation in DCN301 - netfilter: nft_ct: reject direction for ct id - netfilter: nft_set_pipapo: store index in scratch maps - netfilter: nft_set_pipapo: add helper to release pcpu scratch area - netfilter: nft_set_pipapo: remove scratch_aligned pointer - fs/ntfs3: Fix an NULL dereference bug - scsi: core: Move scsi_host_busy() out of host lock if it is for per-command - blk-iocost: Fix an UBSAN shift-out-of-bounds warning - fs: dlm: don't put dlm_local_addrs on heap - mtd: parsers: ofpart: add workaround for #size-cells 0 - ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision - ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter - ALSA: usb-audio: add quirk for RODE NT-USB+ - USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e - USB: serial: option: add Fibocom FM101-GL variant - USB: serial: cp210x: add ID for IMST iM871A-USB - usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK - usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK - hrtimer: Report offline hrtimer enqueue - Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU - Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID - io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers - Revert "ASoC: amd: Add new dmi entries for acp5x platform" - vhost: use kzalloc() instead of kmalloc() followed by memset() - RDMA/irdma: Fix support for 64k pages - f2fs: add helper to check compression level - block: treat poll queue enter similarly to timeouts - clocksource: Skip watchdog check for large watchdog intervals - net: stmmac: xgmac: use #define for string constants - ALSA: usb-audio: Sort quirk table entries - net: stmmac: xgmac: fix a typo of register name in DPP safety handling - netfilter: nft_set_rbtree: skip end interval element from gc - Linux 6.1.78 - upstream stable to v6.1.78 * There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms (LP: #2054487) - ALSA: hda/realtek: add IDs for Dell dual spk platform * Jammy update: v6.1.77 upstream stable release (LP: #2052631) - asm-generic: make sparse happy with odd-sized put_unaligned_*() - powerpc/mm: Fix null-pointer dereference in pgtable_cache_add - arm64: irq: set the correct node for VMAP stack - drivers/perf: pmuv3: don't expose SW_INCR event
[Kernel-packages] [Bug 2054487] Re: There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35 --- linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090) * Jammy update: v6.1.78 upstream stable release (LP: #2054541) - ext4: regenerate buddy after block freeing failed if under fc replay - dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools - dmaengine: ti: k3-udma: Report short packet errors - dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA - dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA - phy: renesas: rcar-gen3-usb2: Fix returning wrong error code - dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV - phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP - cifs: failure to add channel on iface should bump up weight - drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case - drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case - drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup - net: stmmac: xgmac: fix handling of DPP safety error for DMA channels - wifi: mac80211: fix waiting for beacons logic - netdevsim: avoid potential loop in nsim_dev_trap_report_work() - net: atlantic: Fix DMA mapping for PTP hwts ring - selftests: net: cut more slack for gro fwd tests. - selftests: net: avoid just another constant wait - tunnels: fix out of bounds access when building IPv6 PMTU error - atm: idt77252: fix a memleak in open_card_ubr0 - octeontx2-pf: Fix a memleak otx2_sq_init - hwmon: (aspeed-pwm-tacho) mutex for tach reading - hwmon: (coretemp) Fix out-of-bounds memory access - hwmon: (coretemp) Fix bogus core_id to attr name mapping - inet: read sk->sk_family once in inet_recv_error() - drm/i915/gvt: Fix uninitialized variable in handle_mmio() - rxrpc: Fix response to PING RESPONSE ACKs to a dead call - tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() - af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. - ppp_async: limit MRU to 64K - selftests: cmsg_ipv6: repeat the exact packet - netfilter: nft_compat: narrow down revision to unsigned 8-bits - netfilter: nft_compat: reject unused compat flag - netfilter: nft_compat: restrict match/target protocol to u16 - drm/amd/display: Implement bounds check for stream encoder creation in DCN301 - netfilter: nft_ct: reject direction for ct id - netfilter: nft_set_pipapo: store index in scratch maps - netfilter: nft_set_pipapo: add helper to release pcpu scratch area - netfilter: nft_set_pipapo: remove scratch_aligned pointer - fs/ntfs3: Fix an NULL dereference bug - scsi: core: Move scsi_host_busy() out of host lock if it is for per-command - blk-iocost: Fix an UBSAN shift-out-of-bounds warning - fs: dlm: don't put dlm_local_addrs on heap - mtd: parsers: ofpart: add workaround for #size-cells 0 - ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision - ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter - ALSA: usb-audio: add quirk for RODE NT-USB+ - USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e - USB: serial: option: add Fibocom FM101-GL variant - USB: serial: cp210x: add ID for IMST iM871A-USB - usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK - usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK - hrtimer: Report offline hrtimer enqueue - Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU - Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID - io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers - Revert "ASoC: amd: Add new dmi entries for acp5x platform" - vhost: use kzalloc() instead of kmalloc() followed by memset() - RDMA/irdma: Fix support for 64k pages - f2fs: add helper to check compression level - block: treat poll queue enter similarly to timeouts - clocksource: Skip watchdog check for large watchdog intervals - net: stmmac: xgmac: use #define for string constants - ALSA: usb-audio: Sort quirk table entries - net: stmmac: xgmac: fix a typo of register name in DPP safety handling - netfilter: nft_set_rbtree: skip end interval element from gc - Linux 6.1.78 - upstream stable to v6.1.78 * There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms (LP: #2054487) - ALSA: hda/realtek: add IDs for Dell dual spk platform * Jammy update: v6.1.77 upstream stable release (LP: #2052631) - asm-generic: make sparse happy with odd-sized put_unaligned_*() - powerpc/mm: Fix null-pointer dereference in pgtable_cache_add - arm64: irq: set the correct node for VMAP stack - drivers/perf: pmuv3: don't expose SW_INCR event
[Kernel-packages] [Bug 2054541] Re: Jammy update: v6.1.78 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35 --- linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090) * Jammy update: v6.1.78 upstream stable release (LP: #2054541) - ext4: regenerate buddy after block freeing failed if under fc replay - dmaengine: fsl-dpaa2-qdma: Fix the size of dma pools - dmaengine: ti: k3-udma: Report short packet errors - dmaengine: fsl-qdma: Fix a memory leak related to the status queue DMA - dmaengine: fsl-qdma: Fix a memory leak related to the queue command DMA - phy: renesas: rcar-gen3-usb2: Fix returning wrong error code - dmaengine: fix is_slave_direction() return false when DMA_DEV_TO_DEV - phy: ti: phy-omap-usb2: Fix NULL pointer dereference for SRP - cifs: failure to add channel on iface should bump up weight - drm/msms/dp: fixed link clock divider bits be over written in BPC unknown case - drm/msm/dp: return correct Colorimetry for DP_TEST_DYNAMIC_RANGE_CEA case - drm/msm/dpu: check for valid hw_pp in dpu_encoder_helper_phys_cleanup - net: stmmac: xgmac: fix handling of DPP safety error for DMA channels - wifi: mac80211: fix waiting for beacons logic - netdevsim: avoid potential loop in nsim_dev_trap_report_work() - net: atlantic: Fix DMA mapping for PTP hwts ring - selftests: net: cut more slack for gro fwd tests. - selftests: net: avoid just another constant wait - tunnels: fix out of bounds access when building IPv6 PMTU error - atm: idt77252: fix a memleak in open_card_ubr0 - octeontx2-pf: Fix a memleak otx2_sq_init - hwmon: (aspeed-pwm-tacho) mutex for tach reading - hwmon: (coretemp) Fix out-of-bounds memory access - hwmon: (coretemp) Fix bogus core_id to attr name mapping - inet: read sk->sk_family once in inet_recv_error() - drm/i915/gvt: Fix uninitialized variable in handle_mmio() - rxrpc: Fix response to PING RESPONSE ACKs to a dead call - tipc: Check the bearer type before calling tipc_udp_nl_bearer_add() - af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. - ppp_async: limit MRU to 64K - selftests: cmsg_ipv6: repeat the exact packet - netfilter: nft_compat: narrow down revision to unsigned 8-bits - netfilter: nft_compat: reject unused compat flag - netfilter: nft_compat: restrict match/target protocol to u16 - drm/amd/display: Implement bounds check for stream encoder creation in DCN301 - netfilter: nft_ct: reject direction for ct id - netfilter: nft_set_pipapo: store index in scratch maps - netfilter: nft_set_pipapo: add helper to release pcpu scratch area - netfilter: nft_set_pipapo: remove scratch_aligned pointer - fs/ntfs3: Fix an NULL dereference bug - scsi: core: Move scsi_host_busy() out of host lock if it is for per-command - blk-iocost: Fix an UBSAN shift-out-of-bounds warning - fs: dlm: don't put dlm_local_addrs on heap - mtd: parsers: ofpart: add workaround for #size-cells 0 - ALSA: usb-audio: Add delay quirk for MOTU M Series 2nd revision - ALSA: usb-audio: Add a quirk for Yamaha YIT-W12TX transmitter - ALSA: usb-audio: add quirk for RODE NT-USB+ - USB: serial: qcserial: add new usb-id for Dell Wireless DW5826e - USB: serial: option: add Fibocom FM101-GL variant - USB: serial: cp210x: add ID for IMST iM871A-USB - usb: dwc3: host: Set XHCI_SG_TRB_CACHE_SIZE_QUIRK - usb: host: xhci-plat: Add support for XHCI_SG_TRB_CACHE_SIZE_QUIRK - hrtimer: Report offline hrtimer enqueue - Input: i8042 - fix strange behavior of touchpad on Clevo NS70PU - Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID - io_uring/net: fix sr->len for IORING_OP_RECV with MSG_WAITALL and buffers - Revert "ASoC: amd: Add new dmi entries for acp5x platform" - vhost: use kzalloc() instead of kmalloc() followed by memset() - RDMA/irdma: Fix support for 64k pages - f2fs: add helper to check compression level - block: treat poll queue enter similarly to timeouts - clocksource: Skip watchdog check for large watchdog intervals - net: stmmac: xgmac: use #define for string constants - ALSA: usb-audio: Sort quirk table entries - net: stmmac: xgmac: fix a typo of register name in DPP safety handling - netfilter: nft_set_rbtree: skip end interval element from gc - Linux 6.1.78 - upstream stable to v6.1.78 * There is sound from the speakers and headphones at the same time on Oasis 14 and 16 platforms (LP: #2054487) - ALSA: hda/realtek: add IDs for Dell dual spk platform * Jammy update: v6.1.77 upstream stable release (LP: #2052631) - asm-generic: make sparse happy with odd-sized put_unaligned_*() - powerpc/mm: Fix null-pointer dereference in pgtable_cache_add - arm64: irq: set the correct node for VMAP stack - drivers/perf: pmuv3: don't expose SW_INCR event
