[Kernel-packages] [Bug 2053224] [NEW] 22.04.x - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems
Private bug reported: Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems Hello Team, One of our internal team has assessed that having only the 1st patch included in OS will cause issue of encountering I/O lock-up while running PowerFlex I/O workloads on drives connected to PowerEdge R750s with HBA355i. The remedy is to include the 2nd patch as well into the OS as early as possible. I have attached the details of two patches for which I would like to know status of whether they are included in the below OS already? If not, when will be they included(Need ETA)? o Ubuntu22.04.3 & 22.04.4 Patch Details: 1.Patch-1 https://lkml.kernel.org/linux- scsi/20230713075302.10073-1-ranjan.ku...@broadcom.com/T/ 2.Patch-2 https://lore.kernel.org/linux- scsi/169868005494.2933713.2562282002343167126.b4...@oracle.com/T/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private ** Description changed: Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems + + Hello Team, + + One of our internal team has assessed that having only the 1st patch + included in OS will cause issue of encountering I/O lock-up while + running PowerFlex I/O workloads on drives connected to PowerEdge R750s + with HBA355i. The remedy is to include the 2nd patch as well into the OS + as early as possible. + + I have attached the details of two patches for which I would like to + know status of whether they are included in the below OS already? If + not, when will be they included(Need ETA)? + + o Ubuntu22.04.3 & 22.04.4 + + Patch Details: + + 1.Patch-1 https://lkml.kernel.org/linux- + scsi/20230713075302.10073-1-ranjan.ku...@broadcom.com/T/ + + 2.Patch-2 https://lore.kernel.org/linux- + scsi/169868005494.2933713.2562282002343167126.b4...@oracle.com/T/ ** Summary changed: - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems + 22.04.x - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems -- 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/2053224 Title: 22.04.x - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems Status in linux package in Ubuntu: New Bug description: Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems Hello Team, One of our internal team has assessed that having only the 1st patch included in OS will cause issue of encountering I/O lock-up while running PowerFlex I/O workloads on drives connected to PowerEdge R750s with HBA355i. The remedy is to include the 2nd patch as well into the OS as early as possible. I have attached the details of two patches for which I would like to know status of whether they are included in the below OS already? If not, when will be they included(Need ETA)? o Ubuntu22.04.3 & 22.04.4 Patch Details: 1.Patch-1 https://lkml.kernel.org/linux- scsi/20230713075302.10073-1-ranjan.ku...@broadcom.com/T/ 2.Patch-2 https://lore.kernel.org/linux- scsi/169868005494.2933713.2562282002343167126.b4...@oracle.com/T/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053069] Re: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing
** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/2053069 Title: performance: address_space: add padding for i_map and i_mmap_rwsem to mitigate a false sharing Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034983 [Description] When running UnixBench/shell1&shell8&exelc cases, we observed high false sharing for accessing i_mmap against i_mmap_rwsem. The patch places the i_mmap and i_mmap_rwsem in separate cache lines to avoid this false sharing problem. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): DNP Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: TBD Commit IDs: aee79d4e5271 fs/address_space: add alignment padding for i_map and i_mmap_rwsem to mitigate a false sharing. External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5159 Here's the commit ID: aee79d4e5271cee4ffa89ed830189929a6272eb8 https://github.com/torvalds/linux/commit/aee79d4e5271cee4ffa89ed830189929a6272eb8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
This bug was fixed in the package mesa - 23.2.1-1ubuntu3.1~22.04.2 --- mesa (23.2.1-1ubuntu3.1~22.04.2) jammy; urgency=medium * patches: Revert a patch that caused GUI fail with OEM-6.1 kernel on Intel DG2. (LP: #2051068) mesa (23.2.1-1ubuntu3.1~22.04.1) jammy; urgency=medium * Backport to 22.04. (LP: #2037604) * rules: Disable rusticl, FTBFS on jammy. -- Timo Aaltonen Wed, 24 Jan 2024 14:01:34 +0200 ** Changed in: mesa (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051068] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 Status in linux-oem-6.1 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Won't Fix Status in mesa source package in Jammy: Fix Released Bug description: [Impact] OEM-6.1 kernel is missing support for minimum page size of 64k on DG2 (gfx12.5). Mesa 23.2 started using that, so it broke initializing the gpu on boot, causing a blank screen with no GDM running (with wayland, and fallback to X failed too). [Fix] Revert the commit that allows using 64k page size, since that's what the current version in jammy-updates is using. OEM-6.1 kernel is going away, no need to patch that anymore. No other kernel is affected, >6.2 works fine and thus this revert is not necessary in mantic or noble. [Test case] Install the update, boot up a machine with DG2 (iGPU or dGPU, doesn't matter). The login screen should appear. [Where things could go wrong] Hard to see how this could regress anything, as it just restores the limits for intel gfx12.5 as they were in the current mesa version in jammy. --- [Summary] After installed proposed package libegl-mesa0, reboot system. GUI crashed but still able to access system by ssh. [Steps to reproduce] 1. Boot into OS 2. sudo apt update 3. sudo apt upgrade 4. After upgrade process finished, reboot system. 5. GUI crashed. [Expected result] GUI displayed normally [Actual result] GUI crashed [Failure rate] 100% Tester comments --- if we don't upgrade libegl-mesa0, GUI will be fine. [Additional information] CID: 202303-31429 SKU: MYBY-DVT2-C5 Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso system-manufacturer: Dell Inc. system-product-name: Precision 5680 CPU: Intel(R) Core(TM) i7-13700H kernel-version: 6.1.0-1028-oem [Stage] Issue reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053152] Re: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing
Changed devel (main) task to fix-released since the proposed patch is upstream as of v6.5-rc1. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/2053152 Title: performance: mm/percpu-internal.h: Re-layout pcpu_chunk to mitigate false sharing Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034984 [Description] When running UnixBench/Execl throughput case, false sharing is observed due to frequent read on base_addr and write on free_bytes, chunk_md. UnixBench/Execl represents a class of workload where bash scripts are spawned frequently to do some short jobs. It will do system call on execl frequently, and execl will call mm_init to initialize mm_struct of the process. mm_init will call __percpu_counter_init for percpu_counters initialization. Then pcpu_alloc is called to read the base_addr of pcpu_chunk for memory allocation. Inside pcpu_alloc, it will call pcpu_alloc_area to allocate memory from a specified chunk. This function will update "free_bytes" and "chunk_md" to record the rest free bytes and other meta data for this chunk. Correspondingly, pcpu_free_area will also update these 2 members when free memory. In current pcpu_chunk layout, `base_addr' is in the same cache line with `free_bytes' and `chunk_md', and `base_addr' is at the last 8 bytes. This patch moves `bound_map' up to `base_addr', to let `base_addr' locate in a new cacheline. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Platform-Independent Date HW is expected at Canonical: Component(s): Performance and Scalability [Software Information] Target Version: 23.10 Target Kernel: 6.5 Commit IDs: 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing External Links: [Business Justification] [Testing guidance] [External ID] OSVE-5160 The following requested patch has been applied upstream for v6.5-rc1: - 3a6358c0dbe6 percpu-internal/pcpu_chunk: re-layout pcpu_chunk structure to reduce false sharing https://github.com/torvalds/linux/commit/3a6358c0dbe6a286a4f4504ba392a6039a9fbd12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027926] Re: [24.04 FEAT] [VS2308] KVM: Implement counters for nested guest shadow events
** Information type changed from Private 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/2027926 Title: [24.04 FEAT] [VS2308] KVM: Implement counters for nested guest shadow events Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Guest-3 memory needs to be represented by shadow page tables in the Guest-1 hypervisor. These shadow tables are discarded in certain conditions and need to be rebuilt in consequence, which negatively impacts the nested guest's performance. KVM performance counters for the shadow/unshadow events can help to diagnose performance issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2027926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Hi everyone, Would it be possible if you could try 6.8-rc4 mainline to see if the issue is fixed there? https://kernel.ubuntu.com/mainline/v6.8-rc4/ $ wget https://kernel.ubuntu.com/mainline/v6.8-rc4/amd64/linux-headers-6.8.0-060800rc4-generic_6.8.0-060800rc4.202402112032_amd64.deb $ wget https://kernel.ubuntu.com/mainline/v6.8-rc4/amd64/linux-headers-6.8.0-060800rc4_6.8.0-060800rc4.202402112032_all.deb $ wget https://kernel.ubuntu.com/mainline/v6.8-rc4/amd64/linux-image-unsigned-6.8.0-060800rc4-generic_6.8.0-060800rc4.202402112032_amd64.deb $ wget https://kernel.ubuntu.com/mainline/v6.8-rc4/amd64/linux-modules-6.8.0-060800rc4-generic_6.8.0-060800rc4.202402112032_amd64.deb $ sudo dpkg -i ./linux-* $ sudo reboot I had a look at the differences between 6.5.0-15-generic and 6.5.0-17-generic, and the number of ata, sata, scsi changes is huge. There seems to have been a real refactor of scsi in 6.6, and they all got marked for 6.5 stable, so they got pulled in. https://paste.ubuntu.com/p/8VCbhBmDjj/ I will try reproduce in the lab tomorrow. None of my systems at home have spinning disks, you see. If I can't see it in the lab, would anyone be interested in helping me git bisect? I will build the kernels, you just need to test them and say if they are good or bad. Please try 6.8-rc4 mainline and see if its still an issue. If it is, we will talk to the ata and scsi subsystem maintainers. 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/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly Status in linux package in Ubuntu: New Status in linux source package in Mantic: New 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 2052835] Re: Error running program on cifs filesystem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Confirmed -- 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/2052835 Title: Error running program on cifs filesystem Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: Hi When I try and run a shell script which is on a cifs mounted system I get an error. This is on a 22.04 system - Linux bicr-compression 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux nkhan@bicr-compression:/mnt/cephfs/home/users/nkhan$ ~/data/NKHAN/linux-home/date.sh bash: /nfs/home/users/nkhan/data/NKHAN/linux-home/date.sh: /usr/bin/bash: bad interpreter: Input/output error In the kernel log there is: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014745] [ cut here ] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014761] WARNING: CPU: 16 PID: 5834 at fs/smb/client/file.c:3341 cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014849] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 nfsv3 nfs_acl nfs lockd grace fscache netfs vsock_loopback vmw_vsock_virtio_transport_common intel_rapl_msr vmw_vsock_vmci_transport intel_rapl_common vsock intel_uncore_frequency_common binfmt_misc coretemp rapl nls_iso8859_1 vmw_balloon input_leds joydev serio_raw vmw_vmci mac_hid sch_fq_codel msr parport_pc auth_rpcgss ppdev lp parport efi_pstore sunrpc ip_tables x_tables autofs4 vmwgfx crct10dif_pclmul drm_ttm_helper crc32_pclmul polyval_clmulni ttm polyval_generic ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd mptspi mptscsih cryptd mptbase ahci drm psmouse libahci vmxnet3 scsi_transport_spi i2c_piix4 pata_acpi Feb 9 20:10:01 bicr-compression kernel: [ 1421.014910] CPU: 16 PID: 5834 Comm: bash Tainted: GW 6.5.0-17-generic #17~22.04.1-Ubuntu Feb 9 20:10:01 bicr-compression kernel: [ 1421.014914] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/30/2014 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014916] RIP: 0010:cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.014969] Code: c0 48 29 c2 75 c4 41 89 0b 4c 89 c0 48 8b 5d f8 c9 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 45 31 db c3 cc cc cc cc <0f> 0b 45 31 c0 4c 89 c0 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014971] RSP: 0018:b4ee07117b90 EFLAGS: 00010297 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014974] RAX: 9de487836418 RBX: 9de4878363c0 RCX: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014975] RDX: b4ee07117bdc RSI: 0100 RDI: 9de487836418 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014977] RBP: b4ee07117c18 R08: 0100 R09: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014978] R10: R11: R12: 9de48f998000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014979] R13: 9de48f982400 R14: 0100 R15: 9de49ba32000 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014981] FS: 7f8f2ae67740() GS:9dfb5e20() knlGS: Feb 9 20:10:01 bicr-compression kernel: [ 1421.014982] CS: 0010 DS: ES: CR0: 80050033 Feb 9 20:10:01 bicr-compression kernel: [ 1421.014984] CR2: 558a1cb1bf98 CR3: 0001abfd4001 CR4: 003706e0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015030] DR0: DR1: DR2: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015033] DR3: DR6: fffe0ff0 DR7: 0400 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015034] Call Trace: Feb 9 20:10:01 bicr-compression kernel: [ 1421.015036] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015040] ? show_regs+0x6d/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015116] ? __warn+0x89/0x160 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015127] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015181] ? report_bug+0x17e/0x1b0 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015198] ? handle_bug+0x46/0x90 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015212] ? exc_invalid_op+0x18/0x80 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015215] ? asm_exc_invalid_op+0x1b/0x20 Feb 9 20:10:01 bicr-compression kernel: [ 1421.015226] ? cifs_limit_bvec_subset.constprop.0+0x11a/0x190 [cifs] Feb 9 20:10:01 bicr-compression kernel: [ 1421.015277] ? cifs_send_async_read+0x11f/0
[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
Facing same issue on 6.6.10-76060610-generic on Pop!_OS 22.04 LTS using Dell Inspiron 15 7567. Screen fails to recover after suspend/sleep giving this error, can't switch to ttys either, only solution is to force reboot, which is very annoying as I lose all my work from the session. I've seen several forums with this bug with open issue going back to several years but there seems to be no solution, is no one working on it ?... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003608] Re: [i915] LSPCON failure
*** This bug is a duplicate of bug 1973098 *** https://bugs.launchpad.net/bugs/1973098 ** This bug has been marked a duplicate of bug 1973098 [i915] Intermittent freezing and LSPCON init failed kernel messages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003608 Title: [i915] LSPCON failure Status in linux package in Ubuntu: Confirmed Bug description: External monitor connected with HDMI goes black when cable is disconnected and reconnected. Same thing happens when the screen saver kicks in. Gnome still thinks that there is an external monitor and an extended desktop, but the external monitor is black. Work-around: Disconnect the HDMI cable, reboot and then connect HDMI. This is probably a duplicate of bug #1992563. I tried to run "apport-collect 1992563" bug but was rejected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 21 11:46:00 2023 DistUpgraded: 2022-04-30 16:34:04,182 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-H GT2 [UHD Graphics] [17aa:22c2] InstallationDate: Installed on 2020-11-28 (783 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20TH001EMX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=fe3b788b-eaf4-4f94-b43a-4cbc16309a90 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-30 (265 days ago) dmi.bios.date: 10/27/2022 dmi.bios.release: 1.26 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET41W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TH001EMX dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrN2VET41W(1.26):bd10/27/2022:br1.26:efr1.11:svnLENOVO:pn20TH001EMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH001EMX:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20TH_BU_Think_FM_ThinkPadP1Gen3: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TH001EMX dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 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/+bug/2003608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed 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 2053237] [NEW] nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2: nvidia kernel module failed to build
Public bug reported: nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-94-generic Date: Mon Feb 12 20:34:29 2024 DuplicateSignature: dkms:nvidia-dkms-450:450.102.04-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/450.102.04/build/nvidia/os-interface.c:702:18: error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘stats’? InstallationDate: Installed on 2020-09-05 (1257 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 450.102.04-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/2053237 Title: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-94-generic Date: Mon Feb 12 20:34:29 2024 DuplicateSignature: dkms:nvidia-dkms-450:450.102.04-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/450.102.04/build/nvidia/os-interface.c:702:18: error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘stats’? InstallationDate: Installed on 2020-09-05 (1257 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 450.102.04-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/2053237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed 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 2053237] Re: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2: nvidia kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/2053237 Title: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: New Bug description: nil ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-94-generic Date: Mon Feb 12 20:34:29 2024 DuplicateSignature: dkms:nvidia-dkms-450:450.102.04-0ubuntu0.20.04.2:/var/lib/dkms/nvidia/450.102.04/build/nvidia/os-interface.c:702:18: error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘stats’? InstallationDate: Installed on 2020-09-05 (1257 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 450.102.04-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.5 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/2053237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878838] Re: [nvidia] Black screen (wrong VT) upon login
Would this mean, this is solved now and can be closed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1878838 Title: [nvidia] Black screen (wrong VT) upon login Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: OS: Fresh install of ubuntu 20.04 Steps: 1. Enter password to login (Black screen is shown) Workaround: 2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt) 3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 14:08:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-04-28 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053155] Re: Add DPLL and syncE support
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2053155 Title: Add DPLL and syncE support Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: New Bug description: * intro Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking that facilitates the transference of clock signals over the Ethernet physical layer. It is used to pass timing from node to node and is particularly important for mobile networks. The DPLL subsystem in the Linux kernel provides a general interface for configuring devices that use any kind of Digital PLL. This subsystem is designed to manage the clock signal synchronization of a device with an external clock signal. * Explain the bug(s) We need to support mlx5 SyncE feature. The following patches are needed. [net-next,v8,0/9] Create common DPLL configuration API [net-next,v8,1/9] dpll: documentation on DPLL subsystem interface [net-next,v8,2/9] dpll: spec: Add Netlink spec in YAML [net-next,v8,3/9] dpll: core: Add DPLL framework base functions [net-next,v8,4/9] dpll: netlink: Add DPLL framework base functions [net-next,v8,5/9] netdev: expose DPLL pin handle for netdevice [net-next,v8,6/9] ice: add admin commands to access cgu configuration [net-next,v8,7/9] ice: implement dpll interface to control cgu [net-next,v8,8/9] ptp_ocp: implement DPLL ops [net-next,v8,9/9] mlx5: Implement SyncE support using DPLL infrastructure https://lore.kernel.org/netdev/20230913204943.1051233-1-vadim.fedore...@linux.dev/ * Brief explanation of fixes We identify several dependent patches, especially related to netlink gap between current master-next. We cherry-pick/backport series of patches related to netlink. * How to test $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --dump device-get (mlx5 device should show up) $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --do pin-get * list of patches applied to 5.15 jammy based on 911f816f4c04 mlxbf_gige: fix receive packet race condition we applied the following 83a11d94c436 UBUNTU: SAUCE: fix build error after resv_start_op 036b2fecd315 genetlink: allow families to use split ops directly 9f40a82f73ea genetlink: inline old iteration helpers d8ae137b98fc genetlink: use iterator in the op to policy map dumping 095792a3a723 genetlink: add iterator for walking family ops 764747ba0085 genetlink: limit the use of validation workarounds to old ops 35b95f016392 genetlink: inline genl_get_cmd() c448680485e6 genetlink: support split policies in ctrl_dumppolicy_put_op() a17efffb8ce8 genetlink: add policies for both doit and dumpit in ctrl_dumppolicy_start() 82af441de2fa genetlink: check for callback type at op load time dc17c9675d6d genetlink: load policy based on validation flags d867b1e130d3 genetlink: move the private fields in struct genl_family b515a3664ef5 genetlink: piggy back on resv_op to default to a reject policy 1fa6e0ec60a4 genetlink: refactor the cmd <> policy mapping dump c8ba54011c1d netlink: add helpers for extack attr presence checking 3d9c79882136 netlink: add support for ext_ack missing attributes a0edd1e6e99c netlink: factor out extack composition 181e77073d7c genetlink: introduce split op representation 58077e5acc95 genetlink: reject use of nlmsg_flags for new commands 199935182e01 genetlink: start to validate reserved header bytes 137d6fb11693 kernel: make taskstats available from all net namespaces 75acbd978295 genetlink: fix kdoc warnings 05670bbfb561 dpll: remove leftover mode_supported() op and use mode_get() instead e878653f5370 dpll: netlink/core: change pin frequency set behavior d483a8e43651 dpll: netlink/core: add support for pin-dpll signal phase offset/adjust 71574fa963d0 dpll: spec: add support for pin-dpll signal phase offset/adjust 2b004af8572d netlink: specs: remove redundant type keys from attributes in subsets 473b6cb3696f dpll: docs: add support for pin signal phase offset/adjust 015ea1e2fbda Documentation: dpll: wrap DPLL_CMD_PIN_GET output in a code block 5167a94e40e1 Documentation: dpll: Fix code blocks 16ab1010e92d netdev: expose DPLL pin handle for netdevice aa78df66e66b dpll: netlink: Add DPLL framework base functions d0eafb969ef9 dpll: core: Add DPLL framework base functions 8bb4159242d6 dpll: spec: Add Netlink spec in YAML 3dbcbef38d8e dpll: documentation on DPLL subsystem interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155/+subscriptions -- Mailing list: https://launchpad.n
[Kernel-packages] [Bug 2052376] Re: Speakers make the sound of sand when audio is played over HDMI in stereo mode
Also happens when using laptop speakers to listen to the soundtrack of Legend of Keepers in the main menu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2052376 Title: Speakers make the sound of sand when audio is played over HDMI in stereo mode Status in alsa-ucm-conf package in Ubuntu: New Bug description: Since updating the package from 1.2.6.3-1ubuntu1.9 to 1.2.6.3-1ubuntu1.10, when playing audio from a speaker connected over HDMI, using the default stereo audio preset adds the sound of sand to the audio being played. Switching to the 5.1 audio preset fixes the issue. In case it's relevant: My HDMI port is connected to an NVIDIA GPU, which is the dedicated GPU in the laptop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-ucm-conf 1.2.6.3-1ubuntu1.10 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Feb 4 09:41:15 2024 InstallationDate: Installed on 2022-02-19 (714 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: alsa-ucm-conf UpgradeStatus: Upgraded to jammy on 2022-06-05 (608 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2052376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049234 Title: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101&id=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049234] Re: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049234 Title: non-Ethernet tunnel interface creation fails on jammy 5.15.0-81 or later Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: jammy kernel 5.15.0-81.90 includes the following backport: https://github.com/torvalds/linux/commit/b0ad3c179059089d809b477a1d445c1183a7b8fe https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu-5.15.0-91.101&id=1dcafa2582f335f0d929f3e9e736775a95271c43 https://bugs.launchpad.net/bugs/2029401 This causes creation of ip6tnl tunnel interface to fail through systemd-networkd. The following systemd commit also has to be applied to jammy: https://github.com/systemd/systemd/commit/3be64aa462642de9fbe9f95536f8d167c19994bb (Other commits might be required along with above) Since the systemd commit is missing on jammy, Kind=ip6tnl netdev configuration fails as follows: > eno1: Could not create stacked netdev: Invalid argument I believe this is a regression; We encountered this linux- image-5.15.0-91-generic installed via unattended-upgrade -- Also EINVAL during creating tunnel interfaces let AcceptIPv6RA function not to start, so we lose connection to our server due to missing IP address. ``` # eno1.network [Match] Name=eno1 [Network] Tunnel=test_tun ``` ``` # test_tun.netdev [NetDev] Name=test_tun Kind=ip6tnl [Tunnel] Local=2001:db8::a Remote=2001:db8::b Mode=any ``` ``` # test_tun.network [Match] Name=test_tun [Network] Address=10.0.0.1/24 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
Internal team at AMD has tested across a number of different OEM PHX
systems using OEM 6.5-1014 kernel. This is testing well.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2051636
Title:
AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress
loading
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker
[Fix]
Upstream firmware fixes for Phoenix (GC 11.0.1)/Phoenix 2 (GC 11.0.4), and
other prerequisites:
* amdgpu/gc_11_0_1_* up to commit 56c0e7e ("amdgpu: update GC 11.0.1
firmware")
* amdgpu/psp_13_0_4_ta.bin up to commit ed7ddfb ("amdgpu: update PSP 13.0.4
firmware")
* amdgpu/vcn_4_0_2.bin up to commit 34ccb75 ("amdgpu: update VCN 4.0.2
firmware")
* amdgpu/gc_11_0_4_* up to commit 680d98c ("amdgpu: update GC 11.0.4
firmware")
* amdgpu/psp_13_0_11_ta.bin up to commit 72227fe ("amdgpu: update PSP 13.0.11
firmware")
[Test Case]
Run stress tool like 3DMark or GravityMark.
[Where problems could occur]
Binary firmware update recommended by chip vendor. No known issue so
far.
[Other Info]
Phoenix is supported in linux-oem-6.5/jammy, so linux-firmware/jammy
is also nominated for fix.
== original bug report ==
With stress tool like 3DMark or GravityMark, facing amdgpu(PHX) hangs
within a few minutes or sometimes even quicker. Also using mantic +
v6.7 hit the hang, so need to update new FWs to fix this issue.
PHX series
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=680d98c62b13bd441949280c77ca31efb021b68a
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=72227fe463af85648523300543287a68e6c6de5f
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=56c0e7e688427270729fce6e85ecd98f1fe2a6e1
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ed7ddfb5d136c3b9b1eeb48f7568550c0e5d99da
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=34ccb7502e075607682f0f0984a83022bfa0da85
[ 415.782623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0
timeout, signaled seq=27035, emitted seq=27037
[ 415.782833] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process gnome-shell pid 1361 thread gnome-shel:cs0 pid 1421
[ 415.783004] amdgpu :0d:00.0: amdgpu: GPU reset begin!
[ 415.944129] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 415.944317] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.074161] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.074327] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.204184] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.204356] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.334204] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.334377] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.464226] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.464398] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.594247] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.594418] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.724265] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.724432] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.854275] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.854437] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.984284] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0
[amdgpu]] *ERROR* MES failed to response msg=3
[ 416.984456] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to
unmap legacy queue
[ 416.996743] amdgpu :0d:00.0: amd
[Kernel-packages] [Bug 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
Internal team at AMD has tested an OEM RMB that doesn't need the DP swap change to check for any potential regression. They tested using OEM 6.5-1014 kernel. This testing well. Anson will confirm results on the system needing DP swap after he's back from holiday. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2049758 Title: DP connection swap to break eDP behavior on AMD 7735U Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Committed Status in linux-oem-6.5 source package in Jammy: Fix Released Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: New Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Some OEM platforms swap DP connections on the Rembrandt-R, which causes improper eDP behavior. The following issues will occur in these designs: - Fn key failed to control brightness - eDP remains black screen during S0i3 cycle AMD has fixed these issues, but it requires both a kernel patch and an updated DMCUB microcode. [Test Plan] Validate brightness control works. Validate that PSR works. Validate that eDP works after suspend/resume. Validate that external display works. Run above test plan on Rembrandt or Rembrandt-R system with swapped DP as well as one without swapped DP. [Where problems can occur] The code and DMCUB microcode are localized to AMD Rembrandt/Rembrandt-R systems. Issues would occur specifically on these designs, which is why they should be tested. [Other Info] Patch: https://github.com/torvalds/linux/commit/b17ef04bf3a4346d66404454d6a646343ddc9749 DMCUB FW: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=2909bf41a051601e86129a9c2fcebf31c15eebc8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049758/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053250] [NEW] package linux-objects-nvidia-535-6.1.0-1033-oem 6.1.0-1033.33 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it bef
Public bug reported: I don't have any further details ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-objects-nvidia-535-6.1.0-1033-oem 6.1.0-1033.33 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-objects-nvidia-535-6.1.0-1033-oem:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 15:54:36 2024 DpkgTerminalLog: dpkg: error processing package linux-objects-nvidia-535-6.1.0-1033-oem (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal dpkg: too many errors, stopping ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2024-01-17 (28 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-restricted-modules-oem-6.1 Title: package linux-objects-nvidia-535-6.1.0-1033-oem 6.1.0-1033.33 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2053250 Title: package linux-objects-nvidia-535-6.1.0-1033-oem 6.1.0-1033.33 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in linux-restricted-modules-oem-6.1 package in Ubuntu: New Bug description: I don't have any further details ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-objects-nvidia-535-6.1.0-1033-oem 6.1.0-1033.33 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: linux-objects-nvidia-535-6.1.0-1033-oem:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 15:54:36 2024 DpkgTerminalLog: dpkg: error processing package linux-objects-nvidia-535-6.1.0-1033-oem (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal dpkg: too many errors, stopping ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2024-01-17 (28 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-restricted-modules-oem-6.1 Title: package linux-objects-nvidia-535-6.1.0-1033-oem 6.1.0-1033.33 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-6.1/+bug/2053250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052676] Re: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-6.5 (Ubuntu) Status: New => Confirmed -- 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/2052676 Title: Linux kernel 6.5.0.17-generic fails to get IPv6 using SLAAC Status in linux-signed-hwe-6.5 package in Ubuntu: Confirmed Bug description: IPv6 SLAAC using 6.5.0.17-generic does not work, running on Linux mint 21.3 Edge. This problem was also seen on kernel 6.5.0.15 and 6.5.0.14 generic kernels. The same system running on 6.2.0.33-generic works without any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2052676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053251] [NEW] performance: Scheduler: Improve cache bouncing on tg->load_avg
Public bug reported: 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/1528c661c24b407e92194426b0adbb43de859ce0 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Philip Cox (philcox) Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Philip Cox (philcox) Status: In Progress ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Philip Cox (philcox) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- 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: Improve cache bouncing on tg->load_avg Status in linux package in Ubuntu: New Status in linux source package in Jammy: In Progress 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/1528c661c24b407e92194426b0adbb43de859ce0 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 2044657] Re: Multiple data corruption issues in zfs
Verification done for jammy-proposed. TEST CASE: I did test the -proposed package on a clean install of jammy (without the HWE kernel) and a test pool. Since you need a tool that uses lseek SEEK_HOLE/SEEK_DATA and the coreutils bundled with Ubuntu 22.04 are still at version 8.x, I manually downloaded the tarball of coreutils 9.1 from https://www.gnu.org/software/coreutils/ and installed the newly compiled version of "cp" that is used by the zhammer script. test@zfstest:/test$ cp --version cp (GNU coreutils) 9.1 Then I used the zhammer.sh script linked in #16 to test for data corruption: test@zfstest:~$ sudo parallel --lb --halt-on-error now,fail=1 ./zhammer.sh /test 1000 16k 1 ::: $(seq $(nproc)) ... As expected on an unpatched system I immediately got the error on the first run: [zhammer::765410] zhammer_765410_0 differed from zhammer_765410_5930! [zhammer::765410] Hexdump diff follows --- zhammer_765410_0.hex2024-02-15 15:27:22.370732491 + +++ zhammer_765410_5930.hex 2024-02-15 15:27:22.370732491 + @@ -1,3 +1,3 @@ - ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff || + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 || * 4000 [zhammer::765410] Uname: Linux zfstest 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 GNU/Linux [zhammer::765410] ZFS userspace: zfs-2.1.5-1ubuntu6~22.04.2 [zhammer::765410] ZFS kernel: zfs-kmod-2.1.5-1ubuntu6~22.04.2 [zhammer::765410] Module: /lib/modules/5.15.0-94-generic/kernel/zfs/zfs.ko [zhammer::765410] Srcversion: 5A94B4662A7A991696CC35F [zhammer::765410] SHA256: d83e630d4e46280ba6b8bf922850899318ebd24dedd14ab5672574c4bd811ffc [zhammer::765391] checking 1 files at iteration 0 parallel: This job failed: ./zhammer.sh /test 1000 16k 1 5 ... Then I enabled the -proposed repository, installed the patched zfs-version and enabled the dkms kernel module for zfs. After a reboot I re-ran the zhammer.sh and it didn't trigger the bug any more after 5 iterations (x10.000 files). [zhammer::4265] Uname: Linux zfstest 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 GNU/Linux [zhammer::4265] ZFS userspace: zfs-2.1.5-1ubuntu6~22.04.3 [zhammer::4265] ZFS kernel: zfs-kmod-2.1.5-1ubuntu6~22.04.3 [zhammer::4265] Module: /lib/modules/5.15.0-94-generic/updates/dkms/zfs.ko [zhammer::4265] Srcversion: 9CA2EC22B1B594D0C432666 [zhammer::4265] SHA256: f78e84e7f995c15b715f6010ec939ca4202a73654bfafd24572d214ebfcb6364 [zhammer::4265] Work dir: /test [zhammer::4265] Count: 1000 files [zhammer::4265] Block size: 16k [zhammer::4265] Check every: 1 files [zhammer::4265] writing 1 files at iteration 0 [...] [zhammer::4253] writing 1 files at iteration 4 [zhammer::4248] writing 1 files at iteration 4 [zhammer::4246] writing 1 files at iteration 4 [zhammer::4256] writing 1 files at iteration 4 [zhammer::4252] writing 1 files at iteration 4 [zhammer::4280] writing 1 files at iteration 4 [zhammer::4271] writing 1 files at iteration 4 [zhammer::4265] writing 1 files at iteration 4 [zhammer::4246] checking 1 files at iteration 4 [zhammer::4253] checking 1 files at iteration 4 [zhammer::4265] checking 1 files at iteration 4 [zhammer::4248] checking 1 files at iteration 4 [zhammer::4252] checking 1 files at iteration 4 [zhammer::4280] checking 1 files at iteration 4 [zhammer::4256] checking 1 files at iteration 4 [zhammer::4271] checking 1 files at iteration 4 ... Therefore I can report that the proposed fix is also working for jammy. P.S.: I am not sure if I am supposed to change the verification-tag, but since there seems to be very little other activity here and the fix for jammy is still not released I just went ahead. Hopefully this helps to get the fix released in less then (already humiliating) three months. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Jammy: Fix Committed Status in zfs-linux source package in Lunar: Won't Fix Status in zfs-linux source package in Mantic: Fix Released Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Meanwhile, on Ubuntu 22.04, what should I do to work around the issue? -- 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: Confirmed Status in linux source package in Mantic: Confirmed 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 2045931] Re: ps3 sixasis controller request pin to connect to bt
Particularly on the case of PS3 controller, I still think this is a regression that could be fixed. PS3 controllers do not use the standard Bluetooth connection procedure. Instead, they require a connection via USB, and keys are exchanged via there. There is the special `sixaxis` BlueZ plugin to support that protocol, and before that there was the `sixpair.c` utility found here: https://www.pabr.org/sixlinux/sixlinux.en.html Thus, it seems that there could be an exception for wire-paired devices, as it would still fix the issue raised by the CSV for us, PS3 controller users. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: [ Workaround ] 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf 2. Run: systemctl restart bluetooth # or reboot [ Original Description ] Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053251] Re: performance: Scheduler: ratelimit updating of load_avg
** Summary changed: - performance: Scheduler: Improve cache bouncing on tg->load_avg + performance: Scheduler: ratelimit updating of load_avg ** Description changed: This is a public version of https://bugs.launchpad.net/bugs/2040026 [Description] - Improve cache bouncing on tg->load_avg + Improve cache bouncing on tg->load_avg [Hardware Information] - Architecture: - Intel / AMD (x86_64) - Platform(s): - Sapphire Rapids - Date HW is expected at Canonical: + Architecture: + Intel / AMD (x86_64) + Platform(s): + Sapphire Rapids + Date HW is expected at Canonical: - Component(s): - Perf-Scalability + 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: + 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 + LFE-7154 Here's the commit ID:1528c661c24b407e92194426b0adbb43de859ce0 - https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859ce0 + https://github.com/torvalds/linux/commit/1528c661c24b407e92194426b0adbb43de859c0 -- 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: New Status in linux source package in Jammy: In Progress 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 2052453] Re: Azure: Fix regression introduced in LP: #2045069
This bug was fixed in the package linux-azure - 5.15.0-1056.64 --- linux-azure (5.15.0-1056.64) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1056.64 -proposed tracker (LP: #2052545) * Azure: Fix regression introduced in LP: #2045069 (LP: #2052453) - hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove - hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed linux-azure (5.15.0-1055.63) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1055.63 -proposed tracker (LP: #2048291) * Azure - Kernel crashes when removing gpu from pci (LP: #2042568) - Revert "PCI: hv: Use async probing to reduce boot time" * Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance (LP: #2039208) - RDMA/mlx5: Reorder calls to pcie_relaxed_ordering_enabled() - RDMA/mlx5: Remove pcie_relaxed_ordering_enabled() check for RO write * Azure: Deprecate Netvsc and implement MANA direct (LP: #2045069) - hv_netvsc: fix race of netvsc and VF register_netdevice - hv_netvsc: Fix race of register_netdevice_notifier and VF register - hv_netvsc: Mark VF as slave before exposing it to user-mode [ Ubuntu: 5.15.0-94.104 ] * jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777) * [SRU] Duplicate Device_dax ids Created and hence Probing is Failing. (LP: #2028158) - device-dax: Fix duplicate 'hmem' device registration * Add ODM driver f81604 usb-can (LP: #2045387) - can: usb: f81604: add Fintek F81604 support - [Config] updateconfigs for ODM drivers CONFIG_CAN_F81604 * Add ODM driver gpio-m058ssan (LP: #2045386) - SAUCE: ODM: gpio: add M058SSAN gpio driver - [Config] updateconfigs for ODM drivers CONFIG_GPIO_M058SSAN * Add ODM driver rtc-pcf85263 (LP: #2045385) - SAUCE: ODM: rtc: add PCF85263 RTC driver - [Config] updateconfigs for ODM drivers CONFIG_RTC_DRV_PCF85263 * AppArmor patch for mq-posix interface is missing in jammy (LP: #2045384) - SAUCE: (no-up) apparmor: reserve mediation classes - SAUCE: (no-up) apparmor: Add fine grained mediation of posix mqueues * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts [ Ubuntu: 5.15.0-93.103 ] * jammy/linux: 5.15.0-93.103 -proposed tracker (LP: #2048330) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6622 - netfilter: nf_tables: bail out on mismatching dynset and set expressions * CVE-2024-0193 - netfilter: nf_tables: skip set commit for deleted/destroyed sets * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * Patches needed for AmpereOne (arm64) (LP: #2044192) - clocksource/arm_arch_timer: Add build-time guards for unhandled register accesses - clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read accessors - clocksource/drivers/arm_arch_timer: Extend write side of timer register accessors to u64 - clocksource/drivers/arm_arch_timer: Move system register timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Move drop _tval from erratum function names - clocksource/drivers/arm_arch_timer: Fix MMIO base address vs callback ordering issue - clocksource/drivers/arm_arch_timer: Move MMIO timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the core code - clocksource/drivers/arm_arch_timer: Work around broken CVAL implementations - clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL programming interface - clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL programming - clocksource/drivers/arm_arch_timer: Fix masking for high freq counters - clocksource/drivers/arch_arm_timer: Move workaround synchronisation around * Add quirk to disable i915 fastboot on B&R PC (LP: #2047630) - SAUCE: i915: force disable fastboot quirk * Some machines can't pass the pm-graph test (LP: #2046217) - wifi: iwlwifi: pcie: rescan bus if no parent * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105) - ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5 * linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision (LP: #2035971) - [Packaging] Statically link libcpupower into cpupower tool * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - per
[Kernel-packages] [Bug 2045069] Re: Azure: Deprecate Netvsc and implement MANA direct
This bug was fixed in the package linux-azure - 5.15.0-1056.64 --- linux-azure (5.15.0-1056.64) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1056.64 -proposed tracker (LP: #2052545) * Azure: Fix regression introduced in LP: #2045069 (LP: #2052453) - hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove - hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed linux-azure (5.15.0-1055.63) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1055.63 -proposed tracker (LP: #2048291) * Azure - Kernel crashes when removing gpu from pci (LP: #2042568) - Revert "PCI: hv: Use async probing to reduce boot time" * Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance (LP: #2039208) - RDMA/mlx5: Reorder calls to pcie_relaxed_ordering_enabled() - RDMA/mlx5: Remove pcie_relaxed_ordering_enabled() check for RO write * Azure: Deprecate Netvsc and implement MANA direct (LP: #2045069) - hv_netvsc: fix race of netvsc and VF register_netdevice - hv_netvsc: Fix race of register_netdevice_notifier and VF register - hv_netvsc: Mark VF as slave before exposing it to user-mode [ Ubuntu: 5.15.0-94.104 ] * jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777) * [SRU] Duplicate Device_dax ids Created and hence Probing is Failing. (LP: #2028158) - device-dax: Fix duplicate 'hmem' device registration * Add ODM driver f81604 usb-can (LP: #2045387) - can: usb: f81604: add Fintek F81604 support - [Config] updateconfigs for ODM drivers CONFIG_CAN_F81604 * Add ODM driver gpio-m058ssan (LP: #2045386) - SAUCE: ODM: gpio: add M058SSAN gpio driver - [Config] updateconfigs for ODM drivers CONFIG_GPIO_M058SSAN * Add ODM driver rtc-pcf85263 (LP: #2045385) - SAUCE: ODM: rtc: add PCF85263 RTC driver - [Config] updateconfigs for ODM drivers CONFIG_RTC_DRV_PCF85263 * AppArmor patch for mq-posix interface is missing in jammy (LP: #2045384) - SAUCE: (no-up) apparmor: reserve mediation classes - SAUCE: (no-up) apparmor: Add fine grained mediation of posix mqueues * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts [ Ubuntu: 5.15.0-93.103 ] * jammy/linux: 5.15.0-93.103 -proposed tracker (LP: #2048330) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6622 - netfilter: nf_tables: bail out on mismatching dynset and set expressions * CVE-2024-0193 - netfilter: nf_tables: skip set commit for deleted/destroyed sets * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * Patches needed for AmpereOne (arm64) (LP: #2044192) - clocksource/arm_arch_timer: Add build-time guards for unhandled register accesses - clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read accessors - clocksource/drivers/arm_arch_timer: Extend write side of timer register accessors to u64 - clocksource/drivers/arm_arch_timer: Move system register timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Move drop _tval from erratum function names - clocksource/drivers/arm_arch_timer: Fix MMIO base address vs callback ordering issue - clocksource/drivers/arm_arch_timer: Move MMIO timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the core code - clocksource/drivers/arm_arch_timer: Work around broken CVAL implementations - clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL programming interface - clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL programming - clocksource/drivers/arm_arch_timer: Fix masking for high freq counters - clocksource/drivers/arch_arm_timer: Move workaround synchronisation around * Add quirk to disable i915 fastboot on B&R PC (LP: #2047630) - SAUCE: i915: force disable fastboot quirk * Some machines can't pass the pm-graph test (LP: #2046217) - wifi: iwlwifi: pcie: rescan bus if no parent * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105) - ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5 * linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision (LP: #2035971) - [Packaging] Statically link libcpupower into cpupower tool * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - per
[Kernel-packages] [Bug 2039208] Re: Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance
This bug was fixed in the package linux-azure - 5.15.0-1056.64 --- linux-azure (5.15.0-1056.64) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1056.64 -proposed tracker (LP: #2052545) * Azure: Fix regression introduced in LP: #2045069 (LP: #2052453) - hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove - hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed linux-azure (5.15.0-1055.63) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1055.63 -proposed tracker (LP: #2048291) * Azure - Kernel crashes when removing gpu from pci (LP: #2042568) - Revert "PCI: hv: Use async probing to reduce boot time" * Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance (LP: #2039208) - RDMA/mlx5: Reorder calls to pcie_relaxed_ordering_enabled() - RDMA/mlx5: Remove pcie_relaxed_ordering_enabled() check for RO write * Azure: Deprecate Netvsc and implement MANA direct (LP: #2045069) - hv_netvsc: fix race of netvsc and VF register_netdevice - hv_netvsc: Fix race of register_netdevice_notifier and VF register - hv_netvsc: Mark VF as slave before exposing it to user-mode [ Ubuntu: 5.15.0-94.104 ] * jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777) * [SRU] Duplicate Device_dax ids Created and hence Probing is Failing. (LP: #2028158) - device-dax: Fix duplicate 'hmem' device registration * Add ODM driver f81604 usb-can (LP: #2045387) - can: usb: f81604: add Fintek F81604 support - [Config] updateconfigs for ODM drivers CONFIG_CAN_F81604 * Add ODM driver gpio-m058ssan (LP: #2045386) - SAUCE: ODM: gpio: add M058SSAN gpio driver - [Config] updateconfigs for ODM drivers CONFIG_GPIO_M058SSAN * Add ODM driver rtc-pcf85263 (LP: #2045385) - SAUCE: ODM: rtc: add PCF85263 RTC driver - [Config] updateconfigs for ODM drivers CONFIG_RTC_DRV_PCF85263 * AppArmor patch for mq-posix interface is missing in jammy (LP: #2045384) - SAUCE: (no-up) apparmor: reserve mediation classes - SAUCE: (no-up) apparmor: Add fine grained mediation of posix mqueues * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts [ Ubuntu: 5.15.0-93.103 ] * jammy/linux: 5.15.0-93.103 -proposed tracker (LP: #2048330) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6622 - netfilter: nf_tables: bail out on mismatching dynset and set expressions * CVE-2024-0193 - netfilter: nf_tables: skip set commit for deleted/destroyed sets * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * Patches needed for AmpereOne (arm64) (LP: #2044192) - clocksource/arm_arch_timer: Add build-time guards for unhandled register accesses - clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read accessors - clocksource/drivers/arm_arch_timer: Extend write side of timer register accessors to u64 - clocksource/drivers/arm_arch_timer: Move system register timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Move drop _tval from erratum function names - clocksource/drivers/arm_arch_timer: Fix MMIO base address vs callback ordering issue - clocksource/drivers/arm_arch_timer: Move MMIO timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the core code - clocksource/drivers/arm_arch_timer: Work around broken CVAL implementations - clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL programming interface - clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL programming - clocksource/drivers/arm_arch_timer: Fix masking for high freq counters - clocksource/drivers/arch_arm_timer: Move workaround synchronisation around * Add quirk to disable i915 fastboot on B&R PC (LP: #2047630) - SAUCE: i915: force disable fastboot quirk * Some machines can't pass the pm-graph test (LP: #2046217) - wifi: iwlwifi: pcie: rescan bus if no parent * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105) - ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5 * linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision (LP: #2035971) - [Packaging] Statically link libcpupower into cpupower tool * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - per
[Kernel-packages] [Bug 2042568] Re: Azure - Kernel crashes when removing gpu from pci
This bug was fixed in the package linux-azure - 5.15.0-1056.64 --- linux-azure (5.15.0-1056.64) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1056.64 -proposed tracker (LP: #2052545) * Azure: Fix regression introduced in LP: #2045069 (LP: #2052453) - hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove - hv_netvsc: Register VF in netvsc_probe if NET_DEVICE_REGISTER missed linux-azure (5.15.0-1055.63) jammy; urgency=medium * jammy/linux-azure: 5.15.0-1055.63 -proposed tracker (LP: #2048291) * Azure - Kernel crashes when removing gpu from pci (LP: #2042568) - Revert "PCI: hv: Use async probing to reduce boot time" * Azure: mlx5e: Add support for PCI relaxed ordering (RO) for better performance (LP: #2039208) - RDMA/mlx5: Reorder calls to pcie_relaxed_ordering_enabled() - RDMA/mlx5: Remove pcie_relaxed_ordering_enabled() check for RO write * Azure: Deprecate Netvsc and implement MANA direct (LP: #2045069) - hv_netvsc: fix race of netvsc and VF register_netdevice - hv_netvsc: Fix race of register_netdevice_notifier and VF register - hv_netvsc: Mark VF as slave before exposing it to user-mode [ Ubuntu: 5.15.0-94.104 ] * jammy/linux: 5.15.0-94.104 -proposed tracker (LP: #2048777) * [SRU] Duplicate Device_dax ids Created and hence Probing is Failing. (LP: #2028158) - device-dax: Fix duplicate 'hmem' device registration * Add ODM driver f81604 usb-can (LP: #2045387) - can: usb: f81604: add Fintek F81604 support - [Config] updateconfigs for ODM drivers CONFIG_CAN_F81604 * Add ODM driver gpio-m058ssan (LP: #2045386) - SAUCE: ODM: gpio: add M058SSAN gpio driver - [Config] updateconfigs for ODM drivers CONFIG_GPIO_M058SSAN * Add ODM driver rtc-pcf85263 (LP: #2045385) - SAUCE: ODM: rtc: add PCF85263 RTC driver - [Config] updateconfigs for ODM drivers CONFIG_RTC_DRV_PCF85263 * AppArmor patch for mq-posix interface is missing in jammy (LP: #2045384) - SAUCE: (no-up) apparmor: reserve mediation classes - SAUCE: (no-up) apparmor: Add fine grained mediation of posix mqueues * Packaging resync (LP: #1786013) - [Packaging] update annotations scripts [ Ubuntu: 5.15.0-93.103 ] * jammy/linux: 5.15.0-93.103 -proposed tracker (LP: #2048330) * Packaging resync (LP: #1786013) - [Packaging] resync git-ubuntu-log - [Packaging] resync update-dkms-versions helper - [Packaging] remove helper scripts - [Packaging] update annotations scripts - debian/dkms-versions -- update from kernel-versions (main/2024.01.08) * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382) - Revert "PCI: acpiphp: Reassign resources on bridge if necessary" * CVE-2023-6622 - netfilter: nf_tables: bail out on mismatching dynset and set expressions * CVE-2024-0193 - netfilter: nf_tables: skip set commit for deleted/destroyed sets * CVE-2023-6040 - netfilter: nf_tables: Reject tables of unsupported family * Patches needed for AmpereOne (arm64) (LP: #2044192) - clocksource/arm_arch_timer: Add build-time guards for unhandled register accesses - clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read accessors - clocksource/drivers/arm_arch_timer: Extend write side of timer register accessors to u64 - clocksource/drivers/arm_arch_timer: Move system register timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Move drop _tval from erratum function names - clocksource/drivers/arm_arch_timer: Fix MMIO base address vs callback ordering issue - clocksource/drivers/arm_arch_timer: Move MMIO timer programming over to CVAL - clocksource/drivers/arm_arch_timer: Advertise 56bit timer to the core code - clocksource/drivers/arm_arch_timer: Work around broken CVAL implementations - clocksource/drivers/arm_arch_timer: Remove any trace of the TVAL programming interface - clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on CVAL programming - clocksource/drivers/arm_arch_timer: Fix masking for high freq counters - clocksource/drivers/arch_arm_timer: Move workaround synchronisation around * Add quirk to disable i915 fastboot on B&R PC (LP: #2047630) - SAUCE: i915: force disable fastboot quirk * Some machines can't pass the pm-graph test (LP: #2046217) - wifi: iwlwifi: pcie: rescan bus if no parent * Sound: Add rtl quirk of M90-Gen5 (LP: #2046105) - ALSA: hda/realtek: Enable headset on Lenovo M90 Gen5 * linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision (LP: #2035971) - [Packaging] Statically link libcpupower into cpupower tool * [Debian] autoreconstruct - Do not generate chmod -x for deleted files (LP: #2045562) - [Debian] autoreconstruct - Do not generate chmod -x for deleted files * CVE-2023-6931 - perf/core: Add a new read format to get a number of lost samples - per
[Kernel-packages] [Bug 2053155] Re: Add DPLL and syncE support
my first time sending pull request, do I make any mistake so it's Invalid? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2053155 Title: Add DPLL and syncE support Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: New Bug description: * intro Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking that facilitates the transference of clock signals over the Ethernet physical layer. It is used to pass timing from node to node and is particularly important for mobile networks. The DPLL subsystem in the Linux kernel provides a general interface for configuring devices that use any kind of Digital PLL. This subsystem is designed to manage the clock signal synchronization of a device with an external clock signal. * Explain the bug(s) We need to support mlx5 SyncE feature. The following patches are needed. [net-next,v8,0/9] Create common DPLL configuration API [net-next,v8,1/9] dpll: documentation on DPLL subsystem interface [net-next,v8,2/9] dpll: spec: Add Netlink spec in YAML [net-next,v8,3/9] dpll: core: Add DPLL framework base functions [net-next,v8,4/9] dpll: netlink: Add DPLL framework base functions [net-next,v8,5/9] netdev: expose DPLL pin handle for netdevice [net-next,v8,6/9] ice: add admin commands to access cgu configuration [net-next,v8,7/9] ice: implement dpll interface to control cgu [net-next,v8,8/9] ptp_ocp: implement DPLL ops [net-next,v8,9/9] mlx5: Implement SyncE support using DPLL infrastructure https://lore.kernel.org/netdev/20230913204943.1051233-1-vadim.fedore...@linux.dev/ * Brief explanation of fixes We identify several dependent patches, especially related to netlink gap between current master-next. We cherry-pick/backport series of patches related to netlink. * How to test $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --dump device-get (mlx5 device should show up) $ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \ --do pin-get * list of patches applied to 5.15 jammy based on 911f816f4c04 mlxbf_gige: fix receive packet race condition we applied the following 83a11d94c436 UBUNTU: SAUCE: fix build error after resv_start_op 036b2fecd315 genetlink: allow families to use split ops directly 9f40a82f73ea genetlink: inline old iteration helpers d8ae137b98fc genetlink: use iterator in the op to policy map dumping 095792a3a723 genetlink: add iterator for walking family ops 764747ba0085 genetlink: limit the use of validation workarounds to old ops 35b95f016392 genetlink: inline genl_get_cmd() c448680485e6 genetlink: support split policies in ctrl_dumppolicy_put_op() a17efffb8ce8 genetlink: add policies for both doit and dumpit in ctrl_dumppolicy_start() 82af441de2fa genetlink: check for callback type at op load time dc17c9675d6d genetlink: load policy based on validation flags d867b1e130d3 genetlink: move the private fields in struct genl_family b515a3664ef5 genetlink: piggy back on resv_op to default to a reject policy 1fa6e0ec60a4 genetlink: refactor the cmd <> policy mapping dump c8ba54011c1d netlink: add helpers for extack attr presence checking 3d9c79882136 netlink: add support for ext_ack missing attributes a0edd1e6e99c netlink: factor out extack composition 181e77073d7c genetlink: introduce split op representation 58077e5acc95 genetlink: reject use of nlmsg_flags for new commands 199935182e01 genetlink: start to validate reserved header bytes 137d6fb11693 kernel: make taskstats available from all net namespaces 75acbd978295 genetlink: fix kdoc warnings 05670bbfb561 dpll: remove leftover mode_supported() op and use mode_get() instead e878653f5370 dpll: netlink/core: change pin frequency set behavior d483a8e43651 dpll: netlink/core: add support for pin-dpll signal phase offset/adjust 71574fa963d0 dpll: spec: add support for pin-dpll signal phase offset/adjust 2b004af8572d netlink: specs: remove redundant type keys from attributes in subsets 473b6cb3696f dpll: docs: add support for pin signal phase offset/adjust 015ea1e2fbda Documentation: dpll: wrap DPLL_CMD_PIN_GET output in a code block 5167a94e40e1 Documentation: dpll: Fix code blocks 16ab1010e92d netdev: expose DPLL pin handle for netdevice aa78df66e66b dpll: netlink: Add DPLL framework base functions d0eafb969ef9 dpll: core: Add DPLL framework base functions 8bb4159242d6 dpll: spec: Add Netlink spec in YAML 3dbcbef38d8e dpll: documentation on DPLL subsystem interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2053155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : http
[Kernel-packages] [Bug 2053269] [NEW] ubuntu not recognizing touchpad, only connected mouse
Public bug reported: Brand new linux install, cannot use mouse pad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-94-generic 5.15.0-94.104~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-94.104~20.04.1-generic 5.15.136 Uname: Linux 5.15.0-94-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 14:20:03 2024 InstallationDate: Installed on 2024-02-15 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.15 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Devices recognized" https://bugs.launchpad.net/bugs/2053269/+attachment/5746469/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2053269 Title: ubuntu not recognizing touchpad, only connected mouse Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: Brand new linux install, cannot use mouse pad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-94-generic 5.15.0-94.104~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-94.104~20.04.1-generic 5.15.136 Uname: Linux 5.15.0-94-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 14:20:03 2024 InstallationDate: Installed on 2024-02-15 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2053269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053101] Re: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-gcp-5.15 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-gcp-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2053101 Title: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules Status in linux-signed-gcp-5.15 package in Ubuntu: Confirmed Bug description: 3rd party kernel modules for Ubuntu 20.04 break due to the recently backported change of renaming GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART linux-gcp-5.15-headers-5.15.0-1049 still uses GENHD_FL_NO_PART_SCAN which the 3rd party kernel modules use, while linux- gcp-5.15-headers-5.15.0-1051 has brought the rename to GENHD_FL_NO_PART in. This is a breaking change and should not have been backported. The 3rd party modules have been updated for newer kernels on 22.04, but can't be updated on 20.04 with this breaking change. $ grep GENHD_FL_NO_PART /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN`` (0x0200): partition scanning is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN``. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h:#define GENHD_FL_NO_PART_SCAN 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: !(disk->flags & GENHD_FL_NO_PART_SCAN); /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART`` (0x0200): partition support is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART``. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h:#define GENHD_FL_NO_PART 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: return disk_max_parts(disk) > 1 && !(disk->flags & GENHD_FL_NO_PART); $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt policy linux-image-5.15.0-1051-gcp linux-image-5.15.0-1051-gcp: Installed: 5.15.0-1051.59~20.04.1 Candidate: 5.15.0-1051.59~20.04.1 Version table: *** 5.15.0-1051.59~20.04.1 500 500 http://australia-southeast1.gce.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-1051-gcp 5.15.0-1051.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-1051.59~20.04.1-gcp 5.15.136 Uname: Linux 5.15.0-1051-gcp x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 14 12:07:11 2024 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-gcp-5.15 UpgradeStatus: Upgraded to focal on 2023-05-07 (282 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-gcp-5.15/+bug/2053101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053277] [NEW] add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
Public bug reported: Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in linux-firmware package in Ubuntu: New Bug description: Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053101] Re: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules
Just chiming in to say this is affecting us on 22.04 kernels from 5.15.0-94-generic on. It's causing Veeam's veeamsnap module to not compile any more. /var/lib/dkms/veeamsnap/5.0.2.4567/build/snapimage.c: In function ‘snapimage_create’: /var/lib/dkms/veeamsnap/5.0.2.4567/build/snapimage.c:923:24: error: ‘GENHD_FL_NO_PART_SCAN’ undeclared (first use in this function); did you mean ‘GENHD_FL_NO_PART’? 923 | disk->flags |= GENHD_FL_NO_PART_SCAN; |^ |GENHD_FL_NO_PART /var/lib/dkms/veeamsnap/5.0.2.4567/build/snapimage.c:923:24: note: each undeclared identifier is reported only once for each function it appears in We have raised with the vendor (Veeam) but also surprised this change made it into a stable kernel series. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-gcp-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2053101 Title: Backported rename of GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART breaks existing modules Status in linux-signed-gcp-5.15 package in Ubuntu: Confirmed Bug description: 3rd party kernel modules for Ubuntu 20.04 break due to the recently backported change of renaming GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART linux-gcp-5.15-headers-5.15.0-1049 still uses GENHD_FL_NO_PART_SCAN which the 3rd party kernel modules use, while linux- gcp-5.15-headers-5.15.0-1051 has brought the rename to GENHD_FL_NO_PART in. This is a breaking change and should not have been backported. The 3rd party modules have been updated for newer kernels on 22.04, but can't be updated on 20.04 with this breaking change. $ grep GENHD_FL_NO_PART /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN`` (0x0200): partition scanning is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: * ``GENHD_FL_NO_PART_SCAN``. /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h:#define GENHD_FL_NO_PART_SCAN 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1049/include/linux/genhd.h: !(disk->flags & GENHD_FL_NO_PART_SCAN); /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART`` (0x0200): partition support is disabled. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: * ``GENHD_FL_NO_PART``. /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h:#define GENHD_FL_NO_PART 0x0200 /usr/src/linux-gcp-5.15-headers-5.15.0-1051/include/linux/genhd.h: return disk_max_parts(disk) > 1 && !(disk->flags & GENHD_FL_NO_PART); $ lsb_release -rd Description:Ubuntu 20.04.6 LTS Release:20.04 $ apt policy linux-image-5.15.0-1051-gcp linux-image-5.15.0-1051-gcp: Installed: 5.15.0-1051.59~20.04.1 Candidate: 5.15.0-1051.59~20.04.1 Version table: *** 5.15.0-1051.59~20.04.1 500 500 http://australia-southeast1.gce.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-1051-gcp 5.15.0-1051.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-1051.59~20.04.1-gcp 5.15.136 Uname: Linux 5.15.0-1051-gcp x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 14 12:07:11 2024 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-gcp-5.15 UpgradeStatus: Upgraded to focal on 2023-05-07 (282 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-gcp-5.15/+bug/2053101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
** Changed in: linux-oracle (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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Mantic: Fix Committed Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053280] [NEW] System randomly freezing and coming back seconds after
Public bug reported: Randomly all the system (the mouse pointer included) freezes and after some seconds it unfreeze, this happens each a couple of minutes, I don't saw any pattern, nor any strange messages on dmesg. When I boot to the kernel 6.2 everything is normal. uname -a Linux PC 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I am using Linux Mint, but the link in the kernel package manager for bug reports brought me here lsb_release -rd Description:Linux Mint 21.3 Release:21.3 fabio@PC:~$ cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" fabio@PC:~$ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=21.3 DISTRIB_CODENAME=virginia DISTRIB_DESCRIPTION="Linux Mint 21.3 Virginia" fabio@PC:~$ cat /etc/os-release NAME="Linux Mint" VERSION="21.3 (Virginia)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Linux Mint 21.3" VERSION_ID="21.3" HOME_URL="https://www.linuxmint.com/"; SUPPORT_URL="https://forums.linuxmint.com/"; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"; PRIVACY_POLICY_URL="https://www.linuxmint.com/"; VERSION_CODENAME=virginia UBUNTU_CODENAME=jammy ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sudo lspci -vnvn > lspci-vnvn.log" https://bugs.launchpad.net/bugs/2053280/+attachment/5746502/+files/lspci-vnvn.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/2053280 Title: System randomly freezing and coming back seconds after Status in linux package in Ubuntu: New Bug description: Randomly all the system (the mouse pointer included) freezes and after some seconds it unfreeze, this happens each a couple of minutes, I don't saw any pattern, nor any strange messages on dmesg. When I boot to the kernel 6.2 everything is normal. uname -a Linux PC 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I am using Linux Mint, but the link in the kernel package manager for bug reports brought me here lsb_release -rd Description: Linux Mint 21.3 Release: 21.3 fabio@PC:~$ cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" fabio@PC:~$ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=21.3 DISTRIB_CODENAME=virginia DISTRIB_DESCRIPTION="Linux Mint 21.3 Virginia" fabio@PC:~$ cat /etc/os-release NAME="Linux Mint" VERSION="21.3 (Virginia)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Linux Mint 21.3" VERSION_ID="21.3" HOME_URL="https://www.linuxmint.com/"; SUPPORT_URL="https://forums.linuxmint.com/"; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"; PRIVACY_POLICY_URL="https://www.linuxmint.com/"; VERSION_CODENAME=virginia UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053155] Re: Add DPLL and syncE support
** Description changed:
* intro
Synchronous Ethernet, or SyncE, is an ITU-T standard for computer networking
that facilitates the transference of clock signals over the Ethernet physical
layer. It is used to pass timing from node to node and is particularly
important for mobile networks.
The DPLL subsystem in the Linux kernel provides a general interface for
configuring devices that use any kind of Digital PLL. This subsystem is
designed to manage the clock signal synchronization of a device with an
external clock signal.
* Explain the bug(s)
We need to support mlx5 SyncE feature. The following patches are needed.
[net-next,v8,0/9] Create common DPLL configuration API
[net-next,v8,1/9] dpll: documentation on DPLL subsystem interface
[net-next,v8,2/9] dpll: spec: Add Netlink spec in YAML
[net-next,v8,3/9] dpll: core: Add DPLL framework base functions
[net-next,v8,4/9] dpll: netlink: Add DPLL framework base functions
[net-next,v8,5/9] netdev: expose DPLL pin handle for netdevice
[net-next,v8,6/9] ice: add admin commands to access cgu configuration
[net-next,v8,7/9] ice: implement dpll interface to control cgu
[net-next,v8,8/9] ptp_ocp: implement DPLL ops
[net-next,v8,9/9] mlx5: Implement SyncE support using DPLL infrastructure
https://lore.kernel.org/netdev/20230913204943.1051233-1-vadim.fedore...@linux.dev/
* Brief explanation of fixes
We identify several dependent patches, especially related to netlink gap
between current master-next.
We cherry-pick/backport series of patches related to netlink.
-
* How to test
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
--dump device-get
- (mlx5 device should show up)
+ ex:
+ root@bfqa-dell013-roy-oob:~/mlnx-ofa_kernel-4.0# /root/tools-net/ynl/cli.py
--spec ~/netlink/specs/dpll.yaml --dump device-get
+ [{'clock-id': 5237736944144095348,
+ 'id': 0,
+ 'lock-status': 'unlocked',
+ 'mode': 'manual',
+ 'mode-supported': ['manual'],
+ 'module-name': 'mlx5_core',
+ 'type': 'eec'}]
+
$ sudo ./tools/net/ynl/cli.py --spec Documentation/netlink/specs/dpll.yaml \
- --do pin-get
+ --do pin-get
+ ex:
+ root@bfqa-dell013-roy-oob:~# /root/tools-net/ynl/cli.py --spec
~/netlink/specs/dpll.yaml --dump pin-get
+ [{'capabilities': 4,
+ 'clock-id': 5237736944144095348,
+ 'id': 0,
+ 'module-name': 'mlx5_core',
+ 'parent-device': [{'direction': 'input',
+ 'parent-id': 0,
+ 'state': 'disconnected'}],
+ 'phase-adjust-max': 0,
+ 'phase-adjust-min': 0,
+ 'type': 'synce-eth-port'},
+ {'capabilities': 4,
+ 'clock-id': 5237736944144095348,
+ 'id': 1,
+ 'module-name': 'mlx5_core',
+ 'parent-device': [{'direction': 'input',
+ 'parent-id': 0,
+ 'state': 'disconnected'}],
+ 'phase-adjust-max': 0,
+ 'phase-adjust-min': 0,
+ 'type': 'synce-eth-port'}]
* list of patches applied to 5.15 jammy
based on
911f816f4c04 mlxbf_gige: fix receive packet race condition
- we applied the following
+ we applied the following
83a11d94c436 UBUNTU: SAUCE: fix build error after resv_start_op
036b2fecd315 genetlink: allow families to use split ops directly
9f40a82f73ea genetlink: inline old iteration helpers
d8ae137b98fc genetlink: use iterator in the op to policy map dumping
095792a3a723 genetlink: add iterator for walking family ops
764747ba0085 genetlink: limit the use of validation workarounds to old ops
35b95f016392 genetlink: inline genl_get_cmd()
c448680485e6 genetlink: support split policies in ctrl_dumppolicy_put_op()
a17efffb8ce8 genetlink: add policies for both doit and dumpit in
ctrl_dumppolicy_start()
82af441de2fa genetlink: check for callback type at op load time
dc17c9675d6d genetlink: load policy based on validation flags
d867b1e130d3 genetlink: move the private fields in struct genl_family
b515a3664ef5 genetlink: piggy back on resv_op to default to a reject policy
1fa6e0ec60a4 genetlink: refactor the cmd <> policy mapping dump
c8ba54011c1d netlink: add helpers for extack attr presence checking
3d9c79882136 netlink: add support for ext_ack missing attributes
a0edd1e6e99c netlink: factor out extack composition
181e77073d7c genetlink: introduce split op representation
58077e5acc95 genetlink: reject use of nlmsg_flags for new commands
199935182e01 genetlink: start to validate reserved header bytes
137d6fb11693 kernel: make taskstats available from all net namespaces
75acbd978295 genetlink: fix kdoc warnings
05670bbfb561 dpll: remove leftover mode_supported() op and use mode_get()
instead
e878653f5370 dpll: netlink/core: change pin frequency set behavior
d483a8e43651 dpll: netlink/core: add support for pin-dpll signal phase
offset/adjust
71574fa963d0 dpll: spec: add support for pin-dpll signal phase offset/adjust
2b004af8572d netlink: specs: remove redundant type keys from attributes in
subsets
473b6cb36
[Kernel-packages] [Bug 2053280] Re: System randomly freezing and coming back seconds after
** Tags added: jammy kernel-bug -- 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/2053280 Title: System randomly freezing and coming back seconds after Status in linux package in Ubuntu: New Bug description: Randomly all the system (the mouse pointer included) freezes and after some seconds it unfreeze, this happens each a couple of minutes, I don't saw any pattern, nor any strange messages on dmesg. When I boot to the kernel 6.2 everything is normal. uname -a Linux PC 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I am using Linux Mint, but the link in the kernel package manager for bug reports brought me here lsb_release -rd Description: Linux Mint 21.3 Release: 21.3 fabio@PC:~$ cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" fabio@PC:~$ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=21.3 DISTRIB_CODENAME=virginia DISTRIB_DESCRIPTION="Linux Mint 21.3 Virginia" fabio@PC:~$ cat /etc/os-release NAME="Linux Mint" VERSION="21.3 (Virginia)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Linux Mint 21.3" VERSION_ID="21.3" HOME_URL="https://www.linuxmint.com/"; SUPPORT_URL="https://forums.linuxmint.com/"; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"; PRIVACY_POLICY_URL="https://www.linuxmint.com/"; VERSION_CODENAME=virginia UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053280/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045931] Re: ps3 sixasis controller request pin to connect to bt
Regardless of how the bluetooth device works, enabling unbonded devices in BlueZ makes a computer vulnerable to CVE-2023-45866. It won't be enabled by the security team. Perhaps GNOME or other desktops could become more aware of gaming controllers with these issues to make pairing easier, without needing to open a terminal. If there are feature requests for this, please link them in this bug for others. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2045931 Title: ps3 sixasis controller request pin to connect to bt Status in bluez package in Ubuntu: Won't Fix Bug description: [ Workaround ] 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf 2. Run: systemctl restart bluetooth # or reboot [ Original Description ] Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able to connect my PS3 Sixasis controller via bluetooth. It is aking to enter a PIN in the device (not possible to enter a pin in the gamepad). Source pacakge (from "apt list -a bluez"): bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64 Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again without asking for a connection PIN. Ubuntu release: Description: Ubuntu 22.04.3 LTS Release: 22.04 Package version: bluez: Installed: 5.64-0ubuntu1.1 Expected to happen: Connect PS3 Controller by Bluetooth without asking for a PIN code Happened instead: PS3 Controller cannot connect because PIN code is requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053283] [NEW] package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el c
Public bug reported: El problema persiste después de algunas semanas... linux 6.5.0-18-generic. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 16:31:46 2024 ErrorMessage: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2022-09-01 (532 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2053283 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: El problema persiste después de algunas semanas... linux 6.5.0-18-generic. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 16:31:46 2024 ErrorMessage: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2022-09-01 (532 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2053283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
Kernel 6.5.0-18.18 - the problem is not solved, the HDD heads park loudly in an emergency. -- 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: Confirmed Status in linux source package in Mantic: Confirmed 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 1878838] Re: [nvidia] Black screen (wrong VT) upon login
Indeed it's been years since I remember seeing this bug. It might have been fixed when the Nvidia drivers switched over to using KMS by default. Let's leave it incomplete and if there are no more comments after 2 months then the bug will close automatically. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1878838 Title: [nvidia] Black screen (wrong VT) upon login Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: OS: Fresh install of ubuntu 20.04 Steps: 1. Enter password to login (Black screen is shown) Workaround: 2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt) 3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 14:08:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-04-28 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1878838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Hi R. Diez, Steve posted a new patch [1] that also rounds the wsize down when specified on the mount command line, just as we wanted: [1] https://lore.kernel.org/linux- cifs/CAH2r5mvPz2CUyKDZv_9fYGu=9L=3uime7xajgbbu+if8ch8...@mail.gmail.com/ I tested it, and it works great. $ sudo mount -t cifs -o username=ubuntu,vers=1.0,wsize=16850 //192.168.122.172/sambashare ~/share $ mount -l //192.168.122.172/sambashare on /home/ubuntu/share type cifs (rw,relatime,vers=1.0,cache=strict,username=ubuntu,uid=0,noforceuid,gid=0,noforcegid, addr=192.168.122.172,soft,unix,posixpaths,serverino,mapposix,acl,rsize=1048576,wsize=16384,bsize=1048576,retrans=1,echo_interval=60,actimeo=1,closetimeo=1) $ sudo dmesg | tail [ 48.767560] Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [ 48.768399] CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers [ 48.769427] CIFS: VFS: wsize rounded down to 16384 to multiple of PAGE_SIZE 4096 [ 48.770069] CIFS: Attempting to mount //192.168.122.172/sambashare I no longer get data corruption when specifying wsize on the mount command line. I built the new patch ontop of 6.5.0-15-generic again for you to try, if you want. Please note this package is NOT SUPPORTED by Canonical, and is for TESTING PURPOSES ONLY. ONLY Install in a dedicated test environment. You probably have my ppa already in place, you can just do a: $ sudo apt update $ sudo apt install linux-image-unsigned-6.5.0-15-generic linux-modules-6.5.0-15-generic linux-modules-extra-6.5.0-15-generic linux-headers-6.5.0-15-generic $ sudo reboot $ uname -rv 6.5.0-15-generic #15~22.04.1+TEST2049634v20240216b1-Ubuntu SMP PREEMPT_DYNAMIC Fr Note the date change to 20240216. I kept using 6.5.0-15-generic over -17 due to some other bugs I have been debugging on -17 that I am looking into. Anyway, please test the new kernel, and try mount your smb1 share, and paste back the last lines of dmesg with the CIFS: strings, so we can see the round down take place. Feel free to write back to Steve on linux-cifs too. Hopefully we get this patch merged into upstream, and then I'll make sure we get this into the next Ubuntu SRU cycle. 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/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: In Progress Status in linux source package in Noble: In Progress Bug description: [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 1.0 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. A workaround is to increase wsize, but this only works for small files, as any files larger than wsize will see the bug. Most users will want to use the 6.2 HWE kernel until this is fixed. [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] [Other info] Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline 6.8-rc3. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2053283] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el cód
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2053283 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: El problema persiste después de algunas semanas... linux 6.5.0-18-generic. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Feb 15 16:31:46 2024 ErrorMessage: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2022-09-01 (532 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-390 script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2053283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053603] [NEW] package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script su
Public bug reported: Performed simple update & upgrade - issue encountered when processing: linux-headers-6.5.0-18-generic linux-headers-generic-hwe-22.04 linux-generic-hwe-22.04 linux-image-6.5.0-18-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-18-generic 6.5.0-18.18~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: pass Date: Thu Feb 15 23:34:42 2024 ErrorMessage: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-11 (4 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2053603 Title: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Performed simple update & upgrade - issue encountered when processing: linux-headers-6.5.0-18-generic linux-headers-generic-hwe-22.04 linux-generic-hwe-22.04 linux-image-6.5.0-18-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-headers-6.5.0-18-generic 6.5.0-18.18~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: pass Date: Thu Feb 15 23:34:42 2024 ErrorMessage: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-02-11 (4 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: linux-hwe-6.5 Title: package linux-headers-6.5.0-18-generic 6.5.0-18.18~22.04.1 failed to install/upgrade: installed linux-headers-6.5.0-18-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2053603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053041] Re: Issue when shutting down computer: internal hard drive is not shut down properly
I tried on a random lab machine with 2x HP MM0500GBKAK disks. With 6.5.0-18-generic: Before: SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE ... 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 293 ... 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 293 ... 192 Power-Off_Retract_Count 0x0032 100 100 000Old_age Always - 292 ... and after: SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE ... 4 Start_Stop_Count0x0032 100 100 020Old_age Always - 294 ... 12 Power_Cycle_Count 0x0032 100 100 020Old_age Always - 294 ... 192 Power-Off_Retract_Count 0x0032 100 100 000Old_age Always - 293 ... Seems Power-Off_Retract_Count increments regardless. I rolled back to 6.5.0-15-generic, and saw the same behaviour. I think I need to try a different lab machine with different disks. 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/2053041 Title: Issue when shutting down computer: internal hard drive is not shut down properly Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed 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 2049634] Re: smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
The patch does seem like a step forwards, but the warning messages are still easy to miss and misleading. I would rather abort the connection than risking a non-functional connection (in the case of the round-up I described with PAGE_SIZE = 64 KiB). I do not think it is a good idea either to modify the user's wsize value (if specified) and carry on: if the system cannot fulfill the user's request due to a temporary software bug, I would rather abort and state the truth. In order to test the new patch, I would have to devote more of my private time again, and this feels like an uphill battle with diminishing returns. You (or the cifs developers) should be able to automate tests simulating an old Windows Server with smbd by setting "max xmit" in smb.conf, for example, to an unaligned value just below the current PAGE_SIZE. -- 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: In Progress Status in linux source package in Noble: In Progress Bug description: [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 1.0 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. A workaround is to increase wsize, but this only works for small files, as any files larger than wsize will see the bug. Most users will want to use the 6.2 HWE kernel until this is fixed. [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] [Other info] Currently bisecting. Introduced in 6.3-rc1. Currently broken on mainline 6.8-rc3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
