[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Description changed: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 == linux-meta, linux-meta-unstable, linux-meta-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The main fixes are in kernel & dkms packages. This adds ivsc-modules to Provides list of linux-image-generic as other built-in linux-modules-foo packages do. [Test Case] The generated meta package linux-image-generic should then provides "ivsc-modules". [Where problems could occur] Meta package changes only. No real effect but in package dependency. [Other Info] While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will only be nominated for Unstable/Noble/OEM-6.8. - == ipu6-drivers == + == ipu6-drivers, linux, linux-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem-6.8 package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: In Progress Status in linux-meta-oem-6.8 source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 == linux-meta, linux-meta-unstable, linux-meta-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The main fixes are in kernel & dkms packages. This adds ivsc-modules to Provides list of linux-image-generic as other built-in linux-modules-foo packages do. [Test Case] The generated meta package linux-image-generic should then provides "ivsc-modules". [Where problems could occur] Meta package changes only. No real effect but in package dependency. [Other Info] While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will only be nominated for Unstable/Noble/OEM-6.8. == ipu6-drivers, linux, linux-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
Please don't fail the verification for things you're not sure. ** Tags removed: verification-failed-noble verification-needed ** Tags added: verification-done verification-done-noble ** Description changed: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 + + == linux-meta, linux-meta-unstable, linux-meta-oem-6.8 + == + + [Impact] + + Starting from kernel v6.8, Intel demands the use of in-tree VSC driver + instead of the out-of-tree dkms originated from + https://github.com/intel/ivsc-driver. + + [Fix] + + The main fixes are in kernel & dkms packages. This adds ivsc-modules to + Provides list of linux-image-generic as other built-in linux-modules-foo + packages do. + + [Test Case] + + The generated meta package linux-image-generic should then provides + "ivsc-modules". + + [Where problems could occur] + + Meta package changes only. No real effect but in package dependency. + + [Other Info] + + While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will + only be nominated for Unstable/Noble/OEM-6.8. + + == ipu6-drivers == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem-6.8 package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: In Progress Status in linux-meta-oem-6.8 source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 == linux-meta, linux-meta-unstable, linux-meta-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The main fixes are in kernel & dkms packages. This adds ivsc-modules to Provides list of linux-image-generic as other built-in linux-modules-foo packages do. [Test Case] The generated meta package linux-image-generic should then provides "ivsc-modules". [Where problems could occur] Meta package changes only. No real effect but in package dependency. [Other Info] While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will only be nominated for Unstable/Noble/OEM-6.8. == ipu6-drivers, linux, linux-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
SRU: * https://lists.ubuntu.com/archives/kernel-team/2024-April/150635.html (linux-meta: noble, unstable) * https://lists.ubuntu.com/archives/kernel-team/2024-April/150637.html (linux-meta-oem-6.8) ** Changed in: linux-meta (Ubuntu Noble) Status: Triaged => In Progress ** Changed in: linux-meta-oem-6.8 (Ubuntu Noble) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem-6.8 package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: In Progress Status in linux-meta-oem-6.8 source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060914] Re: kernel NULL pointer dereference in ipu6 driver
*** This bug is a duplicate of bug 2061747 *** https://bugs.launchpad.net/bugs/2061747 This should have been fixed by updating ipu6-drivers in bug 2061747. ** This bug has been marked a duplicate of bug 2061747 obsolete out-of-tree ivsc dkms in favor of in-tree one -- 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/2060914 Title: kernel NULL pointer dereference in ipu6 driver Status in OEM Priority Project: New Status in linux package in Ubuntu: New Bug description: pr 11 14:43:43 OCBYM2-DVT1-C3 kernel: BUG: kernel NULL pointer dereference, address: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: supervisor read access in kernel mode Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: #PF: error_code(0x) - not-present page Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PGD 0 P4D 0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Oops: [#1] PREEMPT SMP NOPTI Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CPU: 16 PID: 568 Comm: (udev-worker) Tainted: G O 6.8.0-22-generic #22-Ubuntu Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Hardware name: Dell Inc. Precision 5490/, BIOS 1.1.0 02/07/2024 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RIP: 0010:__wake_up_common+0x2f/0xb0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Code: 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 89 fb 48 83 c3 08 48 83 ec 08 48 8b 47 08 89 75 d4 89 55 d0 48 39 c3 74 51 4d 89 c7 <4c> 8b 00 41 89 ce 48 8d 78 e8 4d 8d 68 e8 eb 25 74 0c 41 83 e4 01 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RSP: 0018:b5ebc3063768 EFLAGS: 00010086 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RAX: RBX: 8fb79e181d50 RCX: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RDX: RSI: 0003 RDI: 8fb79e181d48 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: RBP: b5ebc3063798 R08: R09: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R10: R11: R12: 8fb79e181d48 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: R13: 0003 R14: 0246 R15: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: FS: 77cceb6148c0() GS:8fc6cf60() knlGS: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: CR2: CR3: 0001068ae003 CR4: 00f70ef0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR0: DR1: DR2: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: DR3: DR6: 07f0 DR7: 0400 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: PKRU: 5554 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Call Trace: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? show_regs+0x6d/0x80 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? __die+0x24/0x80 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? page_fault_oops+0x99/0x1b0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? do_user_addr_fault+0x2ee/0x6b0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? exc_page_fault+0x83/0x1b0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? asm_exc_page_fault+0x27/0x30 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? __wake_up_common+0x2f/0xb0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __wake_up+0x37/0x70 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __vb2_queue_cancel+0xcd/0x300 [videobuf2_common] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: vb2_core_queue_release+0x23/0x70 [videobuf2_common] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: vb2_queue_release+0xe/0x20 [videobuf2_v4l2] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_isys_queue_cleanup+0x12/0x20 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_isys_video_cleanup+0x2e/0x40 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_isys_csi2_be_soc_cleanup+0x37/0x50 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: isys_unregister_subdevices+0x40/0xa0 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: isys_probe+0x5c5/0xb80 [intel_ipu6_isys] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? kernfs_create_link+0x66/0xe0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ipu_bus_probe+0x72/0x130 [intel_ipu6] Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: really_probe+0x1c4/0x410 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __driver_probe_device+0x8c/0x180 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: driver_probe_device+0x24/0xd0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: __driver_attach+0x10b/0x210 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ? __pfx___driver_attach+0x10/0x10 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: bus_for_each_dev+0x8a/0xf0 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: driver_attach+0x1e/0x30 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: bus_add_driver+0x156/0x260 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: driver_register+0x5e/0x130 Apr 11 14:43:43 OCBYM2-DVT1-C3 kernel: ?
[Kernel-packages] [Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
verified linux-firmware/mantic-proposed version 20230919.git3672ccab-0ubuntu2.10, linux-firmware/jammy-proposed version 20220329.git681281e4-0ubuntu3.30. ** Tags added: verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Mantic: Fix Committed Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-oem-6.8 (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-meta-oem-6.8 (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-meta-oem-6.8 (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-meta (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-meta (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-meta (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-oem-6.8 package in Ubuntu: Triaged Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: Triaged Status in linux-meta-oem-6.8 source package in Noble: Triaged Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2061747 Proposed DKMS update for ipu6-drivers/noble based on new upstream release Release_20240409. Need sponsor. ** Patch added: "ipu6-drivers_0~git202404110253.97c94720-0ubuntu1~ppa.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.8/+bug/2061747/+attachment/5768025/+files/ipu6-drivers_0~git202404110253.97c94720-0ubuntu1~ppa.1.debdiff -- 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/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still need a few fixes to archive the same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple versions, yet the in- tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
No further update to ivsc-driver shall be necessary as we're removing it. ** Changed in: ipu6-drivers (Ubuntu Noble) Status: New => In Progress ** Changed in: ipu6-drivers (Ubuntu Noble) Importance: Undecided => High ** Changed in: ipu6-drivers (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still need a few fixes to archive the same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple versions, yet the in- tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
And for kernel-versions: https://kernel.ubuntu.com/gitea/kernel/kernel- versions/pulls/290 ** Changed in: linux-oem-6.8 (Ubuntu Noble) Status: Fix Released => In Progress ** Changed in: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-oem-6.8 (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: ivsc-driver (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still need a few fixes to archive the same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple versions, yet the in- tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
SRU: * https://lists.ubuntu.com/archives/kernel-team/2024-April/150378.html (linux/noble, linux-unstable/noble) * https://kernel.ubuntu.com/gitea/kernel/noble-linux-oem/pulls/7 (linux-oem-6.8/noble) ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: In Progress Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: In Progress Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still need a few fixes to archive the same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple versions, yet the in- tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Description changed: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still need a few fixes to archive the same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall - also be built along with the kernel itself as linux-modules-ipu6-. - Install the corresponding kernel/modules packages and test camera - functions. + also be built along with the kernel itself as linux-modules- + ipu6-. Install the corresponding kernel/modules packages and + test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple versions, yet the in- tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. -- 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/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: New Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still need a few fixes to archive the same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple versions, yet the in- tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Description changed: + [SRU Justification] + + BugLink: https://bugs.launchpad.net/bugs/2061747 + + [Impact] + + Starting from kernel v6.8, Intel demands the use of in-tree VSC driver + instead of the out-of-tree dkms originated from + https://github.com/intel/ivsc-driver. + + [Fix] + + The in-tree vsc driver as of v6.8 still need a few fixes to archive the + same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and + 4 are to add supported devices and platforms. Commit 2 resolves an issue + after resumed. + + [Test Case] + + This is supposed to work together with the updated dkms, which shall + also be built along with the kernel itself as linux-modules-ipu6-. + Install the corresponding kernel/modules packages and test camera + functions. + + [Where problems could occur] + + While this is the first time we switch to in-tree VSC driver, and the + out-of-tree driver is not aligned at the time of transition and probably + never will, the provided functions and verified stability issues may + vary. + + [Other Info] + + The dkms is created to be compatible of multiple versions, yet the in- + tree vsc driver transitioning should only happen for kernel >= v6.8. + That is, oem-6.8, noble and linux-unstable will be nominated. + + == original bug description == + Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. -- 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/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: Fix Released Status in ipu6-drivers source package in Noble: New Status in ivsc-driver source package in Noble: New Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still need a few fixes to archive the same supportness to launched Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules-ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple versions, yet the in- tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] [NEW] obsolete out-of-tree ivsc dkms in favor of in-tree one
Public bug reported: Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. ** Affects: ipu6-drivers (Ubuntu) Importance: Undecided Status: New ** Affects: ivsc-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Affects: ipu6-drivers (Ubuntu Noble) Importance: Undecided Status: New ** Affects: ivsc-driver (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ipu6-drivers (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ivsc-driver (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ipu6-drivers (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.8 (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem-6.8 package in Ubuntu: New Status in ipu6-drivers source package in Noble: New Status in ivsc-driver source package in Noble: New Status in linux source package in Noble: New Status in linux-oem-6.8 source package in Noble: New Bug description: Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060101] Re: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: ipu6-drivers (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: ipu6-drivers (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: ipu6-drivers (Ubuntu Mantic) Importance: Undecided => High ** Changed in: ipu6-drivers (Ubuntu Mantic) Status: New => In Progress ** Changed in: ipu6-drivers (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: ipu6-drivers (Ubuntu Noble) Importance: Undecided => High ** Changed in: ipu6-drivers (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Mantic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Noble) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in HWE Next: New Status in ipu6-drivers package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in ipu6-drivers source package in Jammy: Won't Fix Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: In Progress Status in ipu6-drivers source package in Mantic: In Progress Status in linux source package in Mantic: Won't Fix Status in linux-oem-6.5 source package in Mantic: Invalid Status in ipu6-drivers source package in Noble: In Progress Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060101/+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 2060101] Re: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
** Tags added: oem-priority originate-from-2044254 sutton -- 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/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2060101/+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 2060101] [NEW] Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
Public bug reported: TBD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060101 Title: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera Status in linux package in Ubuntu: New Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060101/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053277] Re: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy
SRU: * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/20 (jammy) * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/21 (mantic) ** Description changed: + [SRU Justification] + + [Impact] + + Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) + during warm boot stress test. + + [Fix] + + AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The + affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first + revision since Jammy is ever released. However, the related commits from + the upgrade path have also included blob updates to all kinds of + different, unrelated hardware models. + + This pull request bumps only the affected binary to the target commit + per online discussion with AMD. + + [Test Case] + + Perform checkbox warmboot stress test: + + $ checkbox-cli run com.canonical.certification::stress/reboot + + [Where problems could occur] + + While DCN blob maybe shared with several hardware models, with + confirmation from IHV, there should be little risk to upgrade it. + + [Other Info] + + Affects both Jammy and Mantic. + + == original bug report == + Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. - - DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. + 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. ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2053277 Title: add the updated navi3.x DMCUB FW (ver 0x07002600) to 22.04 Jammy Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: [SRU Justification] [Impact] Devices hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. [Fix] AMD GPU dcn firmware upgrade to upstream commit bd2ad5e6 needed. The affected blob is amdgpu/dcn_3_2_0_dmcub.bin, which has stayed the first revision since Jammy is ever released. However, the related commits from the upgrade path have also included blob updates to all kinds of different, unrelated hardware models. This pull request bumps only the affected binary to the target commit per online discussion with AMD. [Test Case] Perform checkbox warmboot stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] While DCN blob maybe shared with several hardware models, with confirmation from IHV, there should be little risk to upgrade it. [Other Info] Affects both Jammy and Mantic. == original bug report == Dell reported sporadically hang up at its desktop (Intel based platform + AMD Navi3.x dGPU) during warm boot stress test. After updating DMCUB firmware version to 0x07002600, they observed a significant improvement in passing rate. And Dell wants to add the updated DMCUB firmware (ver 0x7002600) to its OEM image. DMCUB firmware (ver 0x7002600) is at https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/amdgpu/dcn_3_2_0_dmcub.bin?id=bd2ad5e65d3bc38fc35eed8c3dbb5e40ae45df20. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2053277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058333] Re: daisy chained thunderbolt devices not working at reboot on AMD strix platforms
** Tags added: amd oem-priority originate-from-2058213 ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058333 Title: daisy chained thunderbolt devices not working at reboot on AMD strix platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058333/+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 2058333] [NEW] daisy chained thunderbolt devices not working at reboot on AMD strix platforms
Public bug reported: Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-2058213 -- 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/2058333 Title: daisy chained thunderbolt devices not working at reboot on AMD strix platforms Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: Boot firmware (typically BIOS) might have created tunnels of its own. The tunnel configuration that it does might be sub-optimal. For instance it may only support HBR2 monitors so the DisplayPort tunnels it created may limit Linux graphics drivers. In addition there is an issue on some AMD based systems where the BIOS does not allocate enough PCIe resources for future topology extension. By resetting the USB4 topology the PCIe links will be reset as well allowing Linux to re-allocate. This aligns the behavior with Windows Connection Manager. Fixes merged to linus tree for v6.9-rc1: * 59a54c5f3dbde thunderbolt: Reset topology created by the boot firmware * ec8162b3f0683 thunderbolt: Make tb_switch_reset() support Thunderbolt 2, 3 and USB4 routers * b35c1d7b11da8 thunderbolt: Introduce tb_path_deactivate_hop() * 01da6b99d49f6 thunderbolt: Introduce tb_port_reset() To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058333/+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 2058331] [NEW] Update amd_sfh for AMD strix series
Public bug reported: Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-2058211 ** Tags added: amd oem-priority originate-from-2058211 ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058331 Title: Update amd_sfh for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Extend MP2 register region to enable family 1AH based family on the supported OEM platforms, needs to be backported into oem-6.8. [ 0.784296] pcie_mp2_amd: probe of :c4:00.7 failed with error -12 Following fixes applied to linus tree: * 90184f90c9ac5 HID: amd_sfh: Set the AMD SFH driver to depend on x86 * 6296562f30b1c HID: amd_sfh: Extend MP2 register access to SFH * 2105e8e00da46 HID: amd_sfh: Improve boot time when SFH is available * c1db0073212ef HID: amd_sfh: Avoid disabling the interrupt * bbf0dec306966 HID: amd_sfh: Update HPD sensor structure elements * 333861f4cca6d HID: amd_sfh: Increase sensor command timeout To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058331/+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 2058330] Re: Update amd-pmf for AMD strix series
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+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 2058330] [NEW] Update amd-pmf for AMD strix series
Public bug reported: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-2058194 ** Tags added: amd oem-priority originate-from-2058194 -- 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/2058330 Title: Update amd-pmf for AMD strix series Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: These updates will be enhanced amd-pmf for family 1AH on the supported OEM platforms, including enabling new revision for BIOS notify events, support static slider by APTS (AMD Performance and Thermal State)...etc. Needs to be backported into oem-6.8. Following are commits merged to linus tree for v6.9-rc1: * 8362e862fb879 platform/x86/amd/pmf: Update sps power thermals according to the platform-profiles * 3eecb434d7f21 platform/x86/amd/pmf: Add support to get sps default APTS index values * 48d38f569261b platform/x86/amd/pmf: Add support to get APTS index numbers for static slider * 6262938eef282 platform/x86/amd/pmf: Add support to notify sbios heart beat event * 5fdc8b82aab4c platform/x86/amd/pmf: Add support to get sbios requests in PMF driver * 233f78e11e1fa platform/x86/amd/pmf: Disable debugfs support for querying power thermals * a33e9e106601b platform/x86/amd/pmf: Differentiate PMF ACPI versions To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058330/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057424] Re: No variable refresh rate (VRR) on the Framework 16
** Changed in: linux (Ubuntu Noble) Status: Incomplete => 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/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057424] Re: No variable refresh rate (VRR) on the Framework 16
The proposed v1 patch still has review comments to be addressed. Stay tuned. ** Changed in: linux (Ubuntu Noble) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057424] [NEW] No variable refresh rate (VRR) on the Framework 16
Public bug reported: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Incomplete ** Tags: amd oem-priority originate-from-2056602 ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Tags added: amd oem-priority originate-from-2056602 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2057424 Title: No variable refresh rate (VRR) on the Framework 16 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: Quoted from AMD proposed fix in https://lore.kernel.org/amd- gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f > The monitor shipped with the Framework 16 supports VRR [1], but it's not > being advertised. > > This is because the detailed timing block doesn't contain > `EDID_DETAIL_MONITOR_RANGE` which amdgpu looks for to find min and max > frequencies. This check however is superfluous for this case because > update_display_info() calls drm_get_monitor_range() to get these ranges > already. > > So if the `DRM_EDID_FEATURE_CONTINUOUS_FREQ` EDID feature is found then > turn on freesync without extra checks. See: https://www.reddit.com/r/framework/comments/1b4y2i5/no_variable_refresh_rate_on_the_framework_16_on/ See: https://www.reddit.com/r/framework/comments/1b6vzcy/framework_16_variable_refresh_rate/ See: https://community.frame.work/t/resolved-no-vrr-freesync-with-amd-version/42338 Link: https://gist.github.com/superm1/e8fbacfa4d0f53150231d3a3e0a13faf To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2057424/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056716] Re: To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0
SRU: * https://lists.ubuntu.com/archives/kernel-team/2024-March/149487.html (noble) * https://kernel.ubuntu.com/gitea/kernel/noble-linux-unstable/src/branch/vicamo/bug-2056716-amdgpu-abm (unstable, to create PR when base branch is synced) ** Description changed: + [SRU Justification] + + [Impact] + + power-profiles-daemon >= 2.0 now utilizes AMD GPU panel_power_savings + sysfs entry to set desired panel power saving level. Related kernel + fixes are to be released in v6.9. + + [Fix] + + Two linux-next committed fixes are required. The first one introduces + panel_power_savings sysfs entry itself, and the second one extends + abmlevel sysfs entry to allow an auto mode. + + [Test Case] + + 1. Check existence of panel_power_savings sysfs entry: + +$ cat /sys/class/drm/card0-eDP-1/amdgpu/panel_power_savings +-1 + + 2. Remove power cable and switch between power profiles from Power + Management settings. The content of above panel_power_savings sysfs + entry should be updated correspondingly. + + [Where problems could occur] + + While the abmlevel entry now has a different default value that allows + automatic power management, the behavior may differ from users' + expectation. + + [Other Info] + + power-profiles-daemon >= 0.20 is only available on Noble or later at + this moment, so only Noble/Unstable will be nominated for fix. + + == original bug report == + Required kernel fixes (in linux-next): * https://gitlab.freedesktop.org/agd5f/linux/-/commit/63d0b87213a0ba241b3fcfba3fe7b0aed0cd1cc5 * https://gitlab.freedesktop.org/agd5f/linux/-/commit/040fdcde288a2830edc31dd507963d6aadf990d2 See also power-profiles-daemon merge request https://gitlab.freedesktop.org/upower/power-profiles- daemon/-/merge_requests/137 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056716 Title: To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: [SRU Justification] [Impact] power-profiles-daemon >= 2.0 now utilizes AMD GPU panel_power_savings sysfs entry to set desired panel power saving level. Related kernel fixes are to be released in v6.9. [Fix] Two linux-next committed fixes are required. The first one introduces panel_power_savings sysfs entry itself, and the second one extends abmlevel sysfs entry to allow an auto mode. [Test Case] 1. Check existence of panel_power_savings sysfs entry: $ cat /sys/class/drm/card0-eDP-1/amdgpu/panel_power_savings -1 2. Remove power cable and switch between power profiles from Power Management settings. The content of above panel_power_savings sysfs entry should be updated correspondingly. [Where problems could occur] While the abmlevel entry now has a different default value that allows automatic power management, the behavior may differ from users' expectation. [Other Info] power-profiles-daemon >= 0.20 is only available on Noble or later at this moment, so only Noble/Unstable will be nominated for fix. == original bug report == Required kernel fixes (in linux-next): * https://gitlab.freedesktop.org/agd5f/linux/-/commit/63d0b87213a0ba241b3fcfba3fe7b0aed0cd1cc5 * https://gitlab.freedesktop.org/agd5f/linux/-/commit/040fdcde288a2830edc31dd507963d6aadf990d2 See also power-profiles-daemon merge request https://gitlab.freedesktop.org/upower/power-profiles- daemon/-/merge_requests/137 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056716] Re: To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0
** Tags added: amd oem-priority originate-from-2055169 ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056716 Title: To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Required kernel fixes (in linux-next): * https://gitlab.freedesktop.org/agd5f/linux/-/commit/63d0b87213a0ba241b3fcfba3fe7b0aed0cd1cc5 * https://gitlab.freedesktop.org/agd5f/linux/-/commit/040fdcde288a2830edc31dd507963d6aadf990d2 See also power-profiles-daemon merge request https://gitlab.freedesktop.org/upower/power-profiles- daemon/-/merge_requests/137 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2056716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056716] [NEW] To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0
Public bug reported: Required kernel fixes (in linux-next): * https://gitlab.freedesktop.org/agd5f/linux/-/commit/63d0b87213a0ba241b3fcfba3fe7b0aed0cd1cc5 * https://gitlab.freedesktop.org/agd5f/linux/-/commit/040fdcde288a2830edc31dd507963d6aadf990d2 See also power-profiles-daemon merge request https://gitlab.freedesktop.org/upower/power-profiles- daemon/-/merge_requests/137 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056716 Title: To support AMD Adaptive Backlight Management (ABM) for power profiles daemon >= 2.0 Status in linux package in Ubuntu: New Bug description: Required kernel fixes (in linux-next): * https://gitlab.freedesktop.org/agd5f/linux/-/commit/63d0b87213a0ba241b3fcfba3fe7b0aed0cd1cc5 * https://gitlab.freedesktop.org/agd5f/linux/-/commit/040fdcde288a2830edc31dd507963d6aadf990d2 See also power-profiles-daemon merge request https://gitlab.freedesktop.org/upower/power-profiles- daemon/-/merge_requests/137 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated
SRU: * https://lists.ubuntu.com/archives/kernel-team/2024-March/149332.html (noble) * https://kernel.ubuntu.com/gitea/kernel/noble-linux-unstable/src/branch/vicamo/bug-2049793-mtl-sysfs-cacheinfo (unstable, to create pull request once branch sync is done) ** Description changed: + [SRU Justification] + + [Impact] + + The interface /sys/devices/system/cpu/cpuX/cache is broken (not populated) if + CPUs have different numbers of subleaves in CPUID 4. This is the case of Intel + Meteor Lake. + + [Fix] + + https://lore.kernel.org/all/2023121519.12834-1-ricardo.neri-calde...@linux.intel.com/ + Reviewed, but probably will only land in v6.9. + + [Test Case] + + Check existence of cpu cache info: + + $ ls /sys/devices/system/cpu/cpu0/cache/ + index0 index1 index2 index3 uevent + + [Where problems could occur] + + This populates sysfs entries that should have been available, not + something new or alters existing interface. + + [Other Info] + + While this is targets v6.8 for Intel LPMD (Low Power Model Daemon)'s + use, only Noble and Unstable will be nominated for fix. + + == original bug report == + [Description] - The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. + The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. [Hardware Information] - Architecture: - Intel / AMD (x86_64) - Platform(s): - Meteor Lake - Date HW is expected at Canonical: - - Component(s): - x86 + Architecture: + Intel / AMD (x86_64) + Platform(s): + Meteor Lake + Date HW is expected at Canonical: + + Component(s): + x86 [Software Information] - Target Version: - 24.04 - Target Kernel: - 6.8 - Commit IDs: - TBD - External Links: - https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ + Target Version: + 24.04 + Target Kernel: + 6.8 + Commit IDs: + TBD + External Links: + https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ [Business Justification] - [Testing guidance] - [External ID] - LFE-6901 + LFE-6901 -- 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/2049793 Title: [MTL] x86: Fix Cache info sysfs is not populated Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: [SRU Justification] [Impact] The interface /sys/devices/system/cpu/cpuX/cache is broken (not populated) if CPUs have different numbers of subleaves in CPUID 4. This is the case of Intel Meteor Lake. [Fix] https://lore.kernel.org/all/2023121519.12834-1-ricardo.neri-calde...@linux.intel.com/ Reviewed, but probably will only land in v6.9. [Test Case] Check existence of cpu cache info: $ ls /sys/devices/system/cpu/cpu0/cache/ index0 index1 index2 index3 uevent [Where problems could occur] This populates sysfs entries that should have been available, not something new or alters existing interface. [Other Info] While this is targets v6.8 for Intel LPMD (Low Power Model Daemon)'s use, only Noble and Unstable will be nominated for fix. == original bug report == [Description] The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Meteor Lake Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: TBD External Links: https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ [Business Justification] [Testing guidance] [External ID] LFE-6901 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated
Verified this populates cpu cache info for MTL platform: $ ls /sys/devices/system/cpu/cpu0/cache/ index0 index1 index2 index3 uevent ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/2049793 Title: [MTL] x86: Fix Cache info sysfs is not populated Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: [Description] The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Meteor Lake Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: TBD External Links: https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ [Business Justification] [Testing guidance] [External ID] LFE-6901 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049793/+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
verified:
* linux-firmware/jammy-proposed version 20220329.git681281e4-0ubuntu3.29
* linux-firmware/noble-proposed version 20230919.git3672ccab-0ubuntu2.9
** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/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]]
[Kernel-packages] [Bug 2049793] Re: [MTL] x86: Fix Cache info sysfs is not populated
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049793 Title: [MTL] x86: Fix Cache info sysfs is not populated Status in intel: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: [Description] The interface /sys/devices/system/cpu/cpu*/cache is empty. In Meteorlake, not all CPUs have the same number of subleaves in the CPUID 4 leaf. The compute die CPUs have 3 subleaves whereas the CPUs in the SoC die have 2. This problem happens because Linux assumes that all CPUs have the same number of subleaves. [Hardware Information] Architecture: Intel / AMD (x86_64) Platform(s): Meteor Lake Date HW is expected at Canonical: Component(s): x86 [Software Information] Target Version: 24.04 Target Kernel: 6.8 Commit IDs: TBD External Links: https://lore.kernel.org/all/2023121519.12834-5-ricardo.neri-calde...@linux.intel.com/ [Business Justification] [Testing guidance] [External ID] LFE-6901 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049793/+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 2037390] Re: Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
** Changed in: linux-firmware (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2037390
Title:
Missing firmware for Intel CNVi AX211 on Intel Meteor Lake platform
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing firmware for Intel CNVi AX211/AX201 on Intel MTL/RPL platforms. For
example:
iwlwifi :00:14.3: PCI dev 7e40/4090, rev=0x441, rfid=0x2010d000
iwlwifi :00:14.3: no suitable firmware found!
iwlwifi :00:14.3: minimum version required: iwlwifi-ma-b0-gf-a0-59
iwlwifi :00:14.3: maximum version supported: iwlwifi-ma-b0-gf-a0-83
iwlwifi :00:14.3: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
And Bluetooth:
Bluetooth: hci0: Failed to load Intel firmware file
intel/ibt-0180-0041.sfi (-2)
[Fix]
There are plenty of commits to be SRUed in the WiFi part due to modifications
to
pnvm files. Intel may and may not update their unversioned pnvm file upon new
releases, therefore on pulling any ucode version of iwlwifi firmware, the full
history of an unversioned pnvm file has to be pulled as well, and each may or
may not pull an older ucode version of that firmware.
Most of the commits have been included in Mantic and newer. For Noble, it
depends on an additional commit 92e24e048136 ("iwlwifi: add a missing FW from
core80-39 release") that has been backported to Jammy and Mantic in bug
2042716.
Also note that commit a6744df81a30 ("iwlwifi: add FWs for new GL and MA device
types with multiple RF modules") is also being backported in bug 2028065.
[Test Case]
Boot with firmware blobs installed, and iwlwifi and btintel should probe
successfully without error.
[Where problems could occur]
While this introduces support for new hardware on new platforms, expect every
possible problem.
[Other Info]
We're to support oem-6.5/jammy, and mantic for best effort.
V2: pull also core80 firmware blobs for AX211 on RPL and AX201.
== original bug report ==
WIFI FW:
Line 1092: [ 7.971227] iwlwifi :00:14.3: PCI dev 7e40/4090,
rev=0x441, rfid=0x2010d000
Line 1118: [ 7.971719] iwlwifi :00:14.3: no suitable
firmware found!
Line 1119: [ 7.971720] iwlwifi :00:14.3: minimum version
required: iwlwifi-ma-b0-gf-a0-59
Line 1120: [ 7.971721] iwlwifi :00:14.3: maximum version
supported: iwlwifi-ma-b0-gf-a0-83
Line 1121: [ 7.971721] iwlwifi :00:14.3: check
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Bluetooth FW:
Line 1123: [ 7.974156] Bluetooth: hci0: Failed to load Intel
firmware file intel/ibt-0180-0041.sfi (-2)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Dependencies: firmware-sof-signed 2.0-1ubuntu4.2+exp.7 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-jiayi-jammy-amd64-20230706-44
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-07-06 (82 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
pc-jiayi-jammy-amd64-20230706-44
MachineType: Intel Corporation Meteor Lake Client Platform
Package: linux-firmware 20220329.git681281e4-0ubuntu3.19+exp.83 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9004-oem
root=UUID=3019b32e-e421-4827-87dd-877e9cff7126 ro i915.force_probe=7d55 quiet
splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.11-oem 6.5.3
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-oem N/A
linux-backports-modules-6.5.0-9004-oem N/A
linux-firmware
20220329.git681281e4-0ubuntu3.19+exp.83
Tags: third-party-packages jammy
Uname: Linux 6.5.0-9004-oem x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party
[Kernel-packages] [Bug 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
Changes have been landed under tag 20230919.git3672ccab-0ubuntu2.6, and
verified in 20230919.git3672ccab-0ubuntu2.8, which is lately respined as
20230919.git3672ccab-0ubuntu2.9 with no additional change made.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048853/+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 2045561] Re: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules
SRU: * https://kernel.ubuntu.com/gitea/kernel/noble-linux-unstable/pulls/18 (unstable) * https://lists.ubuntu.com/archives/kernel-team/2024-February/149078.html (noble, mantic, jammy) ** Description changed: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux-virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kernels from being configurable using qemu or cloud-hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider moving this module to linux-modules. These are already enabled in the 'main' kernel config, and in other distros. In Debian/Archlinux/Fedora it is a built-in, and on SUSE it is a module installed by default. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this module installed and loaded, the directory won't be there. Once enabled, it will be there. + [Test] + + 1. pull built linux-modules packages for architectures with do_extras_package +set to true; + 2. extract the deb and check if dmi-sysfs kernel module file exists: + +$ dpkg-deb -R linux-modules-*.deb . +$ find . -name dmi-sysfs.ko\* + [Regression Potential] Moving a module from a less-common to a more-common package should not have any negative side effects. The main effect will be a little more disk space used by the more common package, whether the module is in use or not. There will also be more functionality available in the default installation, which means a slightly increased surface and possibility of new bugs in case it gets used. ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux: please move dmi-sysfs.ko (CONFIG_DMI_SYSFS for SMBIOS support) from linux-modules-extra to linux-modules Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: SRU Justification [Impact] The dmi-sysfs.ko module (CONFIG_DMI_SYSFS) is currently shipped in linux-modules-extra. This makes it hard to pull in via the linux- virtual package, it can only come from the linux-generic one that also pulls in the firmware and everything else needed for baremetal, and that serves no purpose in a qemu VM. This stops VMs using these kern
[Kernel-packages] [Bug 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
Per discussion in https://github.com/intel/ivsc-driver/issues/42,
upstreamed ivsc drivers are recommended since kernel v6.8, and it takes
additional fixes to be landed in ipu6-drivers dkms (filed as upstream
issue https://github.com/intel/ipu6-drivers/issues/210).
Mark as INCOMPLETE because we need more inputs.
** Bug watch added: github.com/intel/ivsc-driver/issues #42
https://github.com/intel/ivsc-driver/issues/42
** Bug watch added: github.com/intel/ipu6-drivers/issues #210
https://github.com/intel/ipu6-drivers/issues/210
** Changed in: linux-firmware (Ubuntu Noble)
Status: Confirmed => Incomplete
--
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/2048991
Title:
upstream Intel VSC firmware paths moved to intel/vsc/
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Noble:
Incomplete
Bug description:
[SRU Justification]
[Impact]
In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
char-misc-next targeting v6.8, the VSC firmware paths have been changed to
intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
[Fix]
Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
Sensing Controller").
In order to keep backward compatibility for Jammy oem/hwe kernels, an
additional
patch adds symlinks for each moved binary.
[Test Case]
The binaries are bit-to-bit identical, except for the destination path
installed. With extra symlinks created, all the IPU6 platforms should keep
working as usual.
[Where problems could occur]
No problem is expected.
[Other Info]
We're switching to upstreamed binaries in Jammy and Noble, because they're
likely to receive furhter updates for both linux-firmware and vsc drivers.
== original bug report ==
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2034103] Re: Missing firmware for AMD GPU GC 11.0.3
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.28.
** 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/2034103
Title:
Missing firmware for AMD GPU GC 11.0.3
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux source package in Lunar:
Won't Fix
Status in linux-firmware source package in Lunar:
Won't Fix
Bug description:
[Impact]
linux-firmare is missing updates to amdgpu VCN 4.0.0 firmware for
Navi32 hardware.
Of the original list below, only VCN fw update is missing still.
[Test case]
Install the update
Validate brightness control works.
Validate that PSR works.
Validate that eDP works after suspend/resume.
Validate that external display works.
[Where problems could happen]
This is new hw, where the current fw isn't fresh enough. It can't
regress other hw.
--
Add new FWs for GPU with GC 11.0.3:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=d6d655ade8fed37b93631ef17e406afc4fff5f21
("amdgpu: add initial GC 11.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b1a7d7624fd227ebbc46a04a34fdcd08795ee69c
("amdgpu: add initial PSP 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b3f512fb5386e462269ad5a43fbbed6b19fd4b4f
("amdgpu: add initial SDMA 6.0.3 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=22fb12f2f61a3748b155fe083fe71b79bad7c897
("amdgpu: add initial SMU 13.0.10 firmware")
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=59fbffa9ec8e4b0b31d2d13e715cf6580ad0e99c
("amdgpu: update VCN 4.0.0 firmware")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2034103/+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 2031882] Re: Missing firmware for Intel VPU on Intel Meteor Lake platforms
Already fixed in linux-firmware/noble version 20240202.git36777504-0ubuntu1. ** Changed in: linux-firmware (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2031882 Title: Missing firmware for Intel VPU on Intel Meteor Lake platforms Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware source package in Noble: Fix Released Bug description: [SRU Justification] [Impact] Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform. intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 intel_vpu :00:0b.0: Failed to initialize VPU device: -2 intel_vpu: probe of :00:0b.0 failed with error -2 [Fix] Upstream Intel VPU linux driver project https://github.com/intel/linux-vpu-driver stores firmware blob in git- lfs. [Test Case] Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded. [Where problems could occur] Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet. [Other Info] While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default. == original bug report == Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https://github.com/intel/linux-vpu-driver, and firmware is the first one missing. [ 68.602028] intel_vpu :00:0b.0: enabling device ( -> 0002) [ 68.604010] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [ 68.604013] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 [ 68.604263] intel_vpu :00:0b.0: Failed to initialize VPU device: -2 [ 68.604272] intel_vpu: probe of :00:0b.0 failed with error -2 The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/intel/vpu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031882/+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 2031882] Re: Missing firmware for Intel VPU on Intel Meteor Lake platforms
** Also affects: linux-firmware (Ubuntu Noble) Importance: High Assignee: You-Sheng Yang (vicamo) Status: Fix Released ** Changed in: linux-firmware (Ubuntu Noble) Status: Fix Released => In Progress -- 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/2031882 Title: Missing firmware for Intel VPU on Intel Meteor Lake platforms Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware source package in Noble: In Progress Bug description: [SRU Justification] [Impact] Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform. intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 intel_vpu :00:0b.0: Failed to initialize VPU device: -2 intel_vpu: probe of :00:0b.0 failed with error -2 [Fix] Upstream Intel VPU linux driver project https://github.com/intel/linux-vpu-driver stores firmware blob in git- lfs. [Test Case] Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded. [Where problems could occur] Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet. [Other Info] While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default. == original bug report == Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https://github.com/intel/linux-vpu-driver, and firmware is the first one missing. [ 68.602028] intel_vpu :00:0b.0: enabling device ( -> 0002) [ 68.604010] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [ 68.604013] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2 [ 68.604263] intel_vpu :00:0b.0: Failed to initialize VPU device: -2 [ 68.604272] intel_vpu: probe of :00:0b.0 failed with error -2 The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/intel/vpu. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2031882/+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 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
verified linux-firmware/mantic-proposed version
20230919.git3672ccab-0ubuntu2.8.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048853/+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 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
linux-firmware/noble version 20240202.git36777504-0ubuntu1 has all the
required commits already.
** Changed in: linux-firmware (Ubuntu Noble)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048853/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
verified:
* linux-firmware/jammy-proposed version 20220329.git681281e4-0ubuntu3.28
* linux-firmware/mantic-proposed version 20230919.git3672ccab-0ubuntu2.8
** Tags removed: verification-failed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2048977
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
'hot reset' assert
2nd PCIe reset' assert
Asmedia 'hot reset' deassert
PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
5217b76bed90 ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37")
324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0:
update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git
history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes
from suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048977/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
> With the last jigsaw in position, people may then test all necessary
components as a whole. So, yes, they were verified as an integrated set
with all proposed parts installed.
* linux/mantic-proposed version 6.5.0-17.17
* linux-oem-6.5 version 6.5.0-1010.11
* firmware-sof/mantic-proposed version 2.2.6-1ubuntu1.3
* firmware-sof/jammy-proposed version 2.0-1ubuntu4.5.
** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Released
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
@Juerg,
Hi, since it takes an additional commit (fw rev 36 -> 37) to fix it, I
have resubmitted SRU pull request to Mantic with only one commit atop of
currecnt Mantic HEAD. For Jammy, four commits resubmitted.
SRU:
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/11 (jammy)
* https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/12 (mantic)
** Description changed:
[SRU Justification]
+
+ BugLink: https://bugs.launchpad.net/bugs/2048977
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
- 1. 'hot reset' assert
- 2. 2nd PCIe reset' assert
- 3. Asmedia 'hot reset' deassert
- 4. PT21 GPIO13 2nd PCIe reset' deassert.
-
+ 'hot reset' assert
+ 2nd PCIe reset' assert
+ Asmedia 'hot reset' deassert
+ PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
- * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
- * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
- And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
- update board-2.bin") to forfill git history dependency.
+ 5217b76bed90 ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37")
+ 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
+ And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0:
+ update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36") to forfill git
history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
- This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
+ This affects all series with WCN6855/WCN6856 support, Noble/Mantic and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- The FW is to support new China regulatory support.
** Changed in: linux-firmware (Ubuntu Jammy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Lunar:
Won't Fix
Status in linux-firmware source package in Mantic:
Fix Committed
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2048977
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
'hot reset' assert
2nd PCIe reset' assert
Asmedia 'hot reset' deassert
PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
5217b76bed90 ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.37")
324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480f ("ath11k: WCN6855 hw2.0:
update board-2.bin"), 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
@Robie,
The proposed patches, binaries are first included in intermediate PPAs
meant for oem integration since the day it's confirmed effective for the
issue, and then SRU process proceeds to ensure these changes will be
included in targeted milestones. That is, while -proposed packages for
different source packages, e.g. kernel and firmware-sof here, may not
arrive at the same time for testing, we're still able to verify them
separately against existing intermediate PPAs. With the last jigsaw in
position, people may then test all necessary components as a whole. So,
yes, they were verified as an integrated set with all proposed parts
installed.
HWE kernels are based on the corresponding -generic kernel. Once the
kernel fixes are in -generic, HWE kernels will rebase onto them and
receive the same fixes as well. OEM-6.5 is also based on generic-6.5
(linux/mantic), but usually with a tie schedule and we may like to land
it on oem-6.5 first and release early. It will also rebase onto
linux/mantic in the next cycle, and oem-6.5 will no longer carry the
fixes itself but from linux/mantic instead.
** Tags removed: verification-needed-jammy verification-needed-mantic
** Tags added: verification-done-jammy verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f
[Kernel-packages] [Bug 2043542] Re: Support Mediatek MT7925 WiFi/BT
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.26 and linux-oem-6.5/jammy-proposed
version 6.5.0-1014.15.
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049758] Re: DP connection swap to break eDP behavior on AMD 7735U
While the proposed firmware fix is already in upstream repository, it shall be included when linux-firmware/noble is rebased to the latest HEAD. ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Noble) Status: New => Triaged ** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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: Triaged 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: In Progress Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Won't Fix Status in linux-firmware source package in Mantic: In Progress 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: Triaged 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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
** Description changed:
+ [SRU Justification]
+
+ BugLink: https://bugs.launchpad.net/bugs/2049220
+
+ [Impact]
+
+ MT7921 - IPv6 no longer working (Not receiving Multicast).
+
+ [Fix]
+
+ Update WiFi/Bluetooth firmware to upstream commits:
+ * WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
+ * Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
+
+ [Test Case]
+
+ 1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi adapter
+ and connect it to a Dual-stack network leveraging Router Advertisements
+ for IPv6.
+
+ 2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
+- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
+- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
+
+ 3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
+- IPv6 only configures link-local address (fe80::) and no public/global
address.
+- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
+
+ [Where problems could occur]
+
+ Opaque binary. No known dependency to kernel version.
+
+ [Other Info]
+
+ Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
+ Mantic. All the commits are in upstream repository, so Noble should have
+ them after rebased.
+
+ == original bug report ==
+
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for
Linux kernel drivers
3) What you expected to happen
WiFi working
4) What happened instead
Multicast packets dropped, mDNS not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2049220
Title:
Update firmware for MT7921 in order to fix Framework 13 AMD 7040
Status in linux-firmware package in Ubuntu:
Triaged
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Status in linux-firmware source package in Noble:
Triaged
Bug description:
[SRU Justification]
BugLink: https://bugs.launchpad.net/bugs/2049220
[Impact]
MT7921 - IPv6 no longer working (Not receiving Multicast).
[Fix]
Update WiFi/Bluetooth firmware to upstream commits:
* WiFI: commit 0a18a7292a66 ("linux-firmware: update firmware for MT7921 WiFi
device")
* Bluetooth: commit 1366b827c213 ("linux-firmware: update firmware for
mediatek bluetooth chip (MT7921)")
[Test Case]
1. Have Ubuntu 22.04 LTS installed on a laptop with MT7921 Wifi
adapter and connect it to a Dual-stack network leveraging Router
Advertisements for IPv6.
2. Run it with HWE Kernel image linux-image-6.2.0-39-generic and observe the
following:
- IPv6 stateless autoconfiguration works and a public/global address is
assigned.
- Inbound IPv6 Multicast packets are seen when using tcpdump/wireshark.
3. Update the HWE Kernel to linux-image-6.5.0-14-generic and observe the
following:
- IPv6 only configures link-local address (fe80::) and no public/global
address.
- No inbound IPv6 multicast packets are seen when using tcpdump/wireshark.
[Where problems could occur]
Opaque binary. No known dependency to kernel version.
[Other Info]
Nominate Jammy for linux-oem-6.5/jammy and linux-hwe-6.5/jammy, and
Mantic. All the commits are in upstream repository, so Noble should
have them after rebased.
== original bug report ==
The current firmware for MT7921 WiFi is giving me problems like dropping
multicast packets (mDNS).
I manually updated the firmware files and that fixed the issue.
To be more specific, please include this commit:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc
And possibly also this:
https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e
Thanks!
We also need:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 22.04.3 LTS
2) The version of the package you are using, via 'apt-cache
[Kernel-packages] [Bug 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
SRU: * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/9 (jammy) * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/10 (mantic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Triaged Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
All the fixes are in upstream repository. Should have no work to do for Noble once it migrates to upstream HEAD. ** Changed in: linux-firmware (Ubuntu Noble) Status: In Progress => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Triaged Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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
** Description changed:
+ [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: amdgpu: MODE2 reset
[ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to
resume
[ 417.026909] [drm] PCIE GART of 512M enabled (table at 0x00801FD0).
[ 417.027149] amdgpu :0d:00.0: amdgpu: SMU is resuming...
[ 417.029520] amdgpu :0d:00.0: amdgpu: SMU is resumed successfully!
[ 417.032154] [drm] DMUB hardware initialized: version=0x08003000
[ 417.190837] [drm] kiq ring mec 3 pipe 1 q 0
[ 417.192870] [drm] VCN decode and encode initialized successfully(under DPG
Mode).
[ 417.193037] amdgpu :0d:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG
decode initialized successfully.
[ 417.193447] amdgpu :0d:00.0: amdgpu: ring
[Kernel-packages] [Bug 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
SRU: * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/6 (jammy) * https://kernel.ubuntu.com/gitea/kernel/linux-firmware/pulls/8 (mantic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2051636 Title: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Triaged Bug description: 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: amdgpu: MODE2 reset [ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to resume [ 417.026909] [drm] PCIE GART of 512M enabled (table at 0x00801FD0). [ 417.027149] amdgpu :0d:00.0: amdgpu: SMU is resuming... [ 417.029520] amdgpu :0d:00.0: amdgpu: SMU is resumed successfully! [ 417.032154] [drm] DMUB hardware initialized: version=0x08003000 [ 417.190837] [drm] kiq ring mec 3 pipe 1 q 0 [ 417.192870] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 417.193037] amdgpu :0d:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully. [ 417.193447] amdgpu :0d:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 417.193449] amdgpu :0d:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 417.193451] amdgpu :0d:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 417.193452] amdgpu :0d:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [ 417.193453] amdgpu :0d:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [ 417.193454]
[Kernel-packages] [Bug 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
All the fixes are in upstream repository, so there should be no work to do for Noble once it migrate to upstream HEAD. -- 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 linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Triaged Bug description: 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: amdgpu: MODE2 reset [ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to resume [ 417.026909] [drm] PCIE GART of 512M enabled (table at 0x00801FD0). [ 417.027149] amdgpu :0d:00.0: amdgpu: SMU is resuming... [ 417.029520] amdgpu :0d:00.0: amdgpu: SMU is resumed successfully! [ 417.032154] [drm] DMUB hardware initialized: version=0x08003000 [ 417.190837] [drm] kiq ring mec 3 pipe 1 q 0 [ 417.192870] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 417.193037] amdgpu :0d:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully. [ 417.193447] amdgpu :0d:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 417.193449] amdgpu :0d:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 417.193451] amdgpu :0d:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 417.193452] amdgpu :0d:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [ 417.193453] amdgpu :0d:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [ 417.193454] amdgpu :0d:00.0: amdgpu:
[Kernel-packages] [Bug 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Noble) Status: New => Incomplete ** Changed in: linux-firmware (Ubuntu Noble) Status: Incomplete => Triaged ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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 linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: Triaged Bug description: 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: amdgpu: MODE2 reset [ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to resume [ 417.026909] [drm] PCIE GART of 512M enabled (table at 0x00801FD0). [ 417.027149] amdgpu :0d:00.0: amdgpu: SMU is resuming... [ 417.029520] amdgpu :0d:00.0: amdgpu: SMU is resumed successfully! [ 417.032154] [drm] DMUB hardware initialized: version=0x08003000 [ 417.190837] [drm] kiq ring mec 3 pipe
[Kernel-packages] [Bug 2051636] Re: AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading
** Summary changed: - AMD phenix/phenix2 platforms facing amdgpu(PHX) hangs during stress loading + AMD phoenix/phoenix2 platforms facing amdgpu(PHX) hangs during stress loading -- 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 linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Mantic: New Status in linux-firmware source package in Noble: New Bug description: 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: amdgpu: MODE2 reset [ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to resume [ 417.026909] [drm] PCIE GART of 512M enabled (table at 0x00801FD0). [ 417.027149] amdgpu :0d:00.0: amdgpu: SMU is resuming... [ 417.029520] amdgpu :0d:00.0: amdgpu: SMU is resumed successfully! [ 417.032154] [drm] DMUB hardware initialized: version=0x08003000 [ 417.190837] [drm] kiq ring mec 3 pipe 1 q 0 [ 417.192870] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 417.193037] amdgpu :0d:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully. [ 417.193447] amdgpu :0d:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 417.193449] amdgpu :0d:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 417.193451] amdgpu :0d:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 417.193452] amdgpu :0d:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [ 417.193453] amdgpu :0d:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [
[Kernel-packages] [Bug 2051636] [NEW] AMD phenix/phenix2 platforms facing amdgpu(PHX) hangs during stress loading
Public bug reported: 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: amdgpu: MODE2 reset [ 417.026498] amdgpu :0d:00.0: amdgpu: GPU reset succeeded, trying to resume [ 417.026909] [drm] PCIE GART of 512M enabled (table at 0x00801FD0). [ 417.027149] amdgpu :0d:00.0: amdgpu: SMU is resuming... [ 417.029520] amdgpu :0d:00.0: amdgpu: SMU is resumed successfully! [ 417.032154] [drm] DMUB hardware initialized: version=0x08003000 [ 417.190837] [drm] kiq ring mec 3 pipe 1 q 0 [ 417.192870] [drm] VCN decode and encode initialized successfully(under DPG Mode). [ 417.193037] amdgpu :0d:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully. [ 417.193447] amdgpu :0d:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 417.193449] amdgpu :0d:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 417.193451] amdgpu :0d:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 417.193452] amdgpu :0d:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [ 417.193453] amdgpu :0d:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [ 417.193454] amdgpu :0d:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 [ 417.193455] amdgpu :0d:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 [ 417.193456] amdgpu :0d:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 [ 417.193458] amdgpu :0d:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 [ 417.193459] amdgpu :0d:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 417.193460] amdgpu :0d:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8 [ 417.193461] amdgpu :0d:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8 [ 417.193462] amdgpu :0d:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0 [ 417.195893] amdgpu :0d:00.0: amdgpu: recover vram bo from
[Kernel-packages] [Bug 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
verified l-f/jammy-proposed version 20220329.git681281e4-0ubuntu3.25,
mantic-proposed version 20230919.git3672ccab-0ubuntu2.6.
** Tags added: verification-done-jammy verification-done-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Triaged
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:
Triaged
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0: 0x002B79AE | interruptlink1
..
iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
iwlwifi :05:00.0: Function Scratch status:
iwlwifi :05:00.0: 0x01010101 | Func Scratch
iwlwifi :05:00.0: Failed to start RT ucode: -110
iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
[Fix]
Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
release").
While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
more:
* 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
* a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
* f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
These contain firmware blob for ucore 84/86, and are not used by
kernels < v6.7.
[Test Case]
Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects series with kernels that load iwlwifi ucode 83 firmware, namely
Noble, Mantic, and for oem-6.5, Jammy.
== original bug report ==
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048853/+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 1989046] Re: support independent clock and LED GPIOs for Intel IPU6 platforms
For v6.3-rc1 or above, mainline commit 5ae20a8050d08 ("platform/x86:
int3472/discrete: Create a LED class device for the privacy LED")
replaced that sauced patch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1989046
Title:
support independent clock and LED GPIOs for Intel IPU6 platforms
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
Fix Released
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Bug description:
[SRU Justification]
[Impact]
When migrated from power_ctrl_logic driver to int3472, two additional
independent CLK/LED GPIOs other than powerdown/reset must be probed
exceptionally.
[Fix]
Vendor provided patch in
https://github.com/intel/ipu6-drivers/blob/2b8a592dc63e117d8f5af5f32a10d7e0651832d2/patch/int3472-support-independent-clock-and-LED-gpios-5.17+.patch.
[Test Case]
Tested on both TGL/ADL platforms against nominated kernels.
[Where problems could occur]
This adds exceptional cases with fallbacks to the original function. No
one else is affected.
[Other Info]
This is an essential part for switching from power_ctrl_logic based GPIO
control mechanism to the generic, upstreamed int3472 driver. Affects all
IPU6 platforms that are to run new IPU6 driver dump in 202208.
== original bug report ==
Per
https://github.com/intel/ipu6-drivers/commit/f771bd3cb9f324a393a75e068a039bd1f9611026
and
https://github.com/intel/ipu6-drivers/commit/2b8a592dc63e117d8f5af5f32a10d7e0651832d2,
additional fix for INT3472 is necessary to probe camera sensor GPIOs
on Intel IPU6 platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1989046/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
kernel SRU:
* https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/128 (oem-6.5)
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.25
** Tags added: verification-done-jammy
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.25.
** 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/2048991
Title:
upstream Intel VSC firmware paths moved to intel/vsc/
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-firmware source package in Noble:
Confirmed
Bug description:
[SRU Justification]
[Impact]
In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
char-misc-next targeting v6.8, the VSC firmware paths have been changed to
intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
[Fix]
Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
Sensing Controller").
In order to keep backward compatibility for Jammy oem/hwe kernels, an
additional
patch adds symlinks for each moved binary.
[Test Case]
The binaries are bit-to-bit identical, except for the destination path
installed. With extra symlinks created, all the IPU6 platforms should keep
working as usual.
[Where problems could occur]
No problem is expected.
[Other Info]
We're switching to upstreamed binaries in Jammy and Noble, because they're
likely to receive furhter updates for both linux-firmware and vsc drivers.
== original bug report ==
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048747] Re: Dell dock station WD22TB4 loses ether dev after reboot/power off
verified linux-firmware/jammy-proposed version
20220329.git681281e4-0ubuntu3.25, and linux-firmware/lunar-proposed
version 20230323.gitbcdcfbcf-0ubuntu1.10.
** Tags added: verification-done-jammy verification-done-lunar
--
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/2048747
Title:
Dell dock station WD22TB4 loses ether dev after reboot/power off
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 Lunar:
Fix Committed
Status in linux-firmware source package in Mantic:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Dell dock station WD22TB4 loses ether dev after reboot/power off.
[Fix]
Upstream firmware update commit e88bdbe4b5a9 ("rtl_nic: update firmware of USB
devices").
[Test Case]
1. Connect WD22TB4 with ethernet cable
2. Boot into OS
3. power off (or just reboot)
4. power on and check if ethernet connection is still available.
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
The proposed fix has been included in Mantic and Noble, so nominate only for
Lunar and Jammy (for oem-6.5).
== original bug report ==
[Steps to reproduce]
1. Connect WD22TB4 with ethernet
2. Boot into OS
3. poweroff (or just reboot)
4. poweron
[Fix]
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=e88bdbe4b5a98370e30f8b6cbbfebf09cd604b4d
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2048747/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042090] Re: Orchid Bay MLK2/Maya Bay MLK soundwire support
verified linux/mantic-proposed version 6.5.0-17.17.
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042090
Title:
Orchid Bay MLK2/Maya Bay MLK soundwire support
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Mantic:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Status in linux-oem-6.5 source package in Mantic:
Invalid
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For the kernel part,
following upstream commits are mandatory:
* commit e70ca580e9c8 ("ASoC: Intel: soc-acpi-intel-mtl-match: add rt713
rt1316 config")
* commit b6d6e5abf645 ("ASoC: Intel: sof_sdw_rt_sdca_jack_common: add rt713
support")
* commit 5124d08d0ea4 ("ASoC: Intel: sof_sdw_rt712_sdca: construct
cards->components by name_prefix")
* commit 817178e7674b ("ASoC: Intel: soc-acpi: rt713+rt1316, no sdw-dmic
config"): linux-next
[Test Case]
1. enable -proposed pocket and install the latest kernel
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== firmware-sof ==
[Impact]
Audio doesn't work on Dell Orchid Bay MLK2/Maya Bay MLK platforms.
[Fix]
Kernel driver, ALSA ucm, and firmware fixes are needed. For firmware-
sof, it's the upstream commit 99466c05f15f ("Add Intel SOF2.7.2
topology files").
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. browse youtube, hold backspace on virtual terminal or whatever makes some
noises
3. expected sound system brought up and reacts accordingly
[Where problems could occur]
While this enables new devices on new platforms, we may bump into
burst noises, power consumption problems at corner cases not covered
by test program.
[Other Info]
This is to enable sof devices on Intel MTL platform, which is only
supported since 6.5 kernels, e.g. oem-6.5. Nominate Noble, Mantic, and
Jammy.
== original bug report ==
The kernel patches has been applied in the ASoC tree.
Re: [PATCH 00/23] ASoC: Intel: boards: updates for 6.7 — ALSA Devel
(spinics.net) [spinics.net]
https://www.spinics.net/lists/alsa-devel/msg167273.html
We need 3/23, 4/23, 6/23, and
https://github.com/thesofproject/linux/commit/037809ef79874a610216fd6b6d50f53e069b5176
And the UCM PR is submitted
ucm2: soundwire: add rt713 SDCA device by shumingfan · Pull Request #363 ·
alsa-project/alsa-ucm-conf (github.com) [github.com]
https://github.com/alsa-project/alsa-ucm-conf/pull/363
See bug 2042902.
For firmware-sof, need upstream commit 99466c05f15f ("Add Intel
SOF2.7.2 topology files").
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2042090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044330] Re: Update soundwire topology files for Intel RPL platforms
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2044330 Title: Update soundwire topology files for Intel RPL platforms Status in firmware-sof package in Ubuntu: Fix Released Status in firmware-sof source package in Jammy: Fix Committed Status in firmware-sof source package in Mantic: Fix Committed Bug description: [Impact] Old RPL soundwire topology files are found to be muted when doing audio capture on left channel. [Fix] The commit from https://github.com/thesofproject/sof-bin/ is required. * https://github.com/thesofproject/sof-bin/commit/0abfe1a0aebec57bde94c5cfb9b21d6726bd804d (Update v2.2.8 topology files for Intel RPL platforms) [Test Case] Test audio functions on Dell MayaBay RTL platforms. [Where problems could occur] Most topology files for Intel RPL are updated. Need more confirmation on Intel RPL platforms. [Other info] Lunar is skipped, as it'll be EOL soon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2044330/+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 2049220] Re: Update firmware for MT7921 in order to fix Framework 13 AMD 7040
** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Mantic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2049220 Title: Update firmware for MT7921 in order to fix Framework 13 AMD 7040 Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Mantic: In Progress Status in linux-firmware source package in Noble: In Progress Bug description: The current firmware for MT7921 WiFi is giving me problems like dropping multicast packets (mDNS). I manually updated the firmware files and that fixed the issue. To be more specific, please include this commit: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/0a18a7292a66532633d9586521f0b954c68a9fbc And possibly also this: https://gitlab.com/kernel-firmware/linux-firmware/-/commit/1366b827c21351b37665303397e161dd4158316e Thanks! We also need: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ii linux-firmware 20220329.git681281e4-0ubuntu3.24 all Firmware for Linux kernel drivers 3) What you expected to happen WiFi working 4) What happened instead Multicast packets dropped, mDNS not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2049220/+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 2048735] Re: Disable keyboard wakeup for Framework 13
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Noble) Status: New => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048735 Title: Disable keyboard wakeup for Framework 13 Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: New Status in linux-oem-6.5 source package in Jammy: New Status in linux source package in Noble: Fix Released Status in linux-oem-6.1 source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Framework 13" AMD version has an unexpected behavior that EC triggers a keyboard wakeup event every time the system exits s0i3. This EC keyboard wakeup event is to workaround a different bug. Because of this, the following series is sent to mailing list to disable wakeup from keyboard when on latest BIOS for Framework 13 AMD. https://lore.kernel.org/platform-driver-x86/20231212045006.97581-1-mario.limoncie...@amd.com/T/#mca26ce4d4358b188fc61e8b32c27d62410780c5a 85980669a863 platform/x86/amd/pmc: Move platform defines to header 2d53c0ab61e6 platform/x86/amd/pmc: Only run IRQ1 firmware version check on Cezanne b614a4bd73ef platform/x86/amd/pmc: Move keyboard wakeup disablement detection to pmc-quirks a55bdad5dfd1 platform/x86/amd/pmc: Disable keyboard wakeup on AMD Framework 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048735/+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 2049358] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739461/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739458/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739460/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739459/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739457/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739453/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739454/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739455/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739456/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739452/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739450/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739451/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739447/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739449/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739448/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] Re: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
apport information ** Tags added: apport-collected jammy ** Description changed: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 1157 F pulseaudio + CasperMD5CheckMismatches: ./preseed/project.cfg + CasperMD5CheckResult: fail + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-stella-jammy-amd64-20231228-670 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-12-28 (18 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 + MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-6.5.0-3011-oem N/A + linux-backports-modules-6.5.0-3011-oem N/A + linux-firmware 20220329.git681281e4-0ubuntu3.24 + Tags: jammy + Uname: Linux 6.5.0-3011-oem x86_64 + UnreportableReason: This report is about a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: False + dmi.bios.date: 01/05/2024 + dmi.bios.release: 1.1 + dmi.bios.vendor: HP + dmi.bios.version: W70 Ver. 01.01.01 + dmi.board.name: 8C26 + dmi.board.vendor: HP + dmi.board.version: KBC Version 02.35.00 + dmi.chassis.type: 31 + dmi.chassis.vendor: HP + dmi.ec.firmware.release: 2.53 + dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: + dmi.product.family: 103C_5336AN HP Elite x360 + dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC + dmi.product.sku: 1234567#ABA + dmi.product.version: SBKPF + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739444/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list']
[Kernel-packages] [Bug 2049358] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739446/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2049358/+attachment/5739445/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1157 F pulseaudio CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-jammy-amd64-20231228-670 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-12-28 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-stella-jammy-amd64-20231228-670 MachineType: HP HP Elite x360 830 13 inch G11 2-in-1 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3011-oem root=UUID=34294b64-68b6-4f94-9606-9be6144aa431 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-3011.12-oem 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.5.0-3011-oem N/A linux-backports-modules-6.5.0-3011-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.24 Tags: jammy Uname: Linux 6.5.0-3011-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 01/05/2024 dmi.bios.release: 1.1 dmi.bios.vendor: HP dmi.bios.version: W70 Ver. 01.01.01 dmi.board.name: 8C26 dmi.board.vendor: HP dmi.board.version: KBC Version 02.35.00 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.53 dmi.modalias: dmi:bvnHP:bvrW70Ver.01.01.01:bd01/05/2024:br1.1:efr2.53:svnHP:pnHPElitex36083013inchG112-in-1NotebookPC:pvrSBKPF:rvnHP:rn8C26:rvrKBCVersion02.35.00:cvnHP:ct31:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP Elite x360 dmi.product.name: HP Elite x360 830 13 inch G11 2-in-1 Notebook PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2049358] [NEW] mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1
Public bug reported: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-2048144 stella ** Tags added: oem-priority originate-from-2048144 stella -- 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/2049358 Title: mtk_t7xx WWAN module fails to probe with: Invalid device status 0x1 Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: At booting up: mtk_t7xx :56:00.0: enabling device ( -> 0002) mtk_t7xx :56:00.0: Invalid device status 0x1 mtk_t7xx :56:00.0: Port AT is not opened, drop packets mtk_t7xx :56:00.0: Packet drop on channel 0x1004, port not found And at suspending: mtk_t7xx :56:00.0: Not ready for system sleep mtk_t7xx :56:00.0: PM: device_prepare(): pci_pm_prepare+0x0/0x80 returns -110 mtk_t7xx :56:00.0: PM: not prepared for power transition: code -110 PM: Some devices failed to suspend, or early wake event detected To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2049358/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
All commits are already in linux/noble 6.7.0-1.1.
** Changed in: linux (Ubuntu Noble)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Fix Released
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
** Description changed:
+ [kernel SRU Justification]
+
+ [Impact]
+
+ Mediatek MT7925 WiFi/Bluetooth not supported yet.
+
+ [Fix]
+
+ For WiFi, there are tons of patches to be backported from upstream
+ kernel v6.7 due to a massive refactoring was done to integrate multiple
+ mt79xx drivers into one before landing support for mt7925. While these
+ changes, mostly clean cherry-picks, are tied to each other, and
+ separating them may cause more efforts in the future, a huge patchset of
+ total number 144 is proposed.
+
+ For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
+ support Mediatek MT7925") is required.
+
+ [Test Case]
+
+ Initial hardware support. One should be able to find WiFi/BT interfaces
+ up available along with proposed kernels.
+
+ [Where problems could occur]
+
+ Features for MT7925 are not all available at this moment, and expect
+ more fixes for every corner case.
+
+ [Other Info]
+
+ MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
+ Nominate for Jammy and Noble.
+
+
+
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
- chip (MT7925)")
+ chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Confirmed
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[kernel SRU Justification]
[Impact]
Mediatek MT7925 WiFi/Bluetooth not supported yet.
[Fix]
For WiFi, there are tons of patches to be backported from upstream
kernel v6.7 due to a massive refactoring was done to integrate
multiple mt79xx drivers into one before landing support for mt7925.
While these changes, mostly clean cherry-picks, are tied to each
other, and separating them may cause more efforts in the future, a
huge patchset of total number 144 is proposed.
For Bluetooth, upstream commit 4c92ae75ea7d ("Bluetooth: btusb: Add
support Mediatek MT7925") is required.
[Test Case]
Initial hardware support. One should be able to find WiFi/BT
interfaces up available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect
more fixes for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well.
Nominate for Jammy and Noble.
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b
[Kernel-packages] [Bug 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148071.html (jammy)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
+ char-misc-next targeting v6.8, the VSC firmware paths have been changed to
+ intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
+ existing Intel IPU6 camera platforms.
+
+ [Fix]
+
+ Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
+ Sensing Controller").
+
+ In order to keep backward compatibility for Jammy oem/hwe kernels, an
additional
+ patch adds symlinks for each moved binary.
+
+ [Test Case]
+
+ The binaries are bit-to-bit identical, except for the destination path
+ installed. With extra symlinks created, all the IPU6 platforms should keep
+ working as usual.
+
+ [Where problems could occur]
+
+ No problem is expected.
+
+ [Other Info]
+
+ We're switching to upstreamed binaries in Jammy and Noble, because they're
+ likely to receive furhter updates for both linux-firmware and vsc drivers.
+
+ == original bug report ==
+
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
--
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/2048991
Title:
upstream Intel VSC firmware paths moved to intel/vsc/
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Noble:
Confirmed
Bug description:
[SRU Justification]
[Impact]
In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
char-misc-next targeting v6.8, the VSC firmware paths have been changed to
intel/vsc instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
[Fix]
Upstream linux-firmware commit cfc997c6 ("intel: vsc: Add firmware for Visual
Sensing Controller").
In order to keep backward compatibility for Jammy oem/hwe kernels, an
additional
patch adds symlinks for each moved binary.
[Test Case]
The binaries are bit-to-bit identical, except for the destination path
installed. With extra symlinks created, all the IPU6 platforms should keep
working as usual.
[Where problems could occur]
No problem is expected.
[Other Info]
We're switching to upstreamed binaries in Jammy and Noble, because they're
likely to receive furhter updates for both linux-firmware and vsc drivers.
== original bug report ==
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
For noble, bug 2042074 is still not yet accepted. Mark this as CONFIRMED at this moment. ** Changed in: linux-firmware (Ubuntu Noble) Status: New => Confirmed ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/2048991 Title: upstream Intel VSC firmware paths moved to intel/vsc/ Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Noble: Confirmed Bug description: In upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char- misc.git/commit/?h=char-misc- next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next targeting v6.8, the VSC firmware paths have been changed to intel/vsc instead of the original vsc/soc_a1_prod that has been used for all existing Intel IPU6 camera platforms. The corresponding linux-firmware commit is in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Noble) 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/2048991 Title: upstream Intel VSC firmware paths moved to intel/vsc/ Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Noble: New Bug description: In upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char- misc.git/commit/?h=char-misc- next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next targeting v6.8, the VSC firmware paths have been changed to intel/vsc instead of the original vsc/soc_a1_prod that has been used for all existing Intel IPU6 camera platforms. The corresponding linux-firmware commit is in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048991] Re: upstream Intel VSC firmware paths moved to intel/vsc/
** Summary changed: - upstream Intel VSC firmware paths changed to intel/vsc/ + upstream Intel VSC firmware paths moved to intel/vsc/ -- 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/2048991 Title: upstream Intel VSC firmware paths moved to intel/vsc/ Status in linux-firmware package in Ubuntu: New Bug description: In upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char- misc.git/commit/?h=char-misc- next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next targeting v6.8, the VSC firmware paths have been changed to intel/vsc instead of the original vsc/soc_a1_prod that has been used for all existing Intel IPU6 camera platforms. The corresponding linux-firmware commit is in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148065.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148066.html (noble)
** Description changed:
+ [linux-firmware SRU Justification]
+
+ [Impact]
+
+ Missing firmware for Mediatek MT7925 WiFi/BT.
+
+ [Fix]
+
+ Upstream firmware commits:
+ - WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
+ - Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
+ chip (MT7925)")
+
+ [Test Case]
+
+ Initial hardware support. One should be able to find WiFi/BT interfaces up
+ available along with proposed kernels.
+
+ [Where problems could occur]
+
+ Features for MT7925 are not all available at this moment, and expect more
fixes
+ for every corner case.
+
+ [Other Info]
+
+ MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
+ for Jammy and Noble.
+
+ == original bug report ==
+
* WiFi
- - kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
+ - kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- - firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
+ - firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- - firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
+ - firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Confirmed
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
[Kernel-packages] [Bug 2043542] Re: Support Mediatek MT7925 WiFi/BT
So far Wifi kernel driver will be ready since v6.7-rc1 (with fixes from
-rc7), and Bluetooth since v6.6. While linux/noble is currently at v6.6,
mark it as confirmed at this moment.
** Changed in: linux (Ubuntu Noble)
Status: New => Confirmed
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng Yang (vicamo)
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Confirmed
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
Three more fixes available in v6.7-rc4 and -rc7:
* cd607f2cbbbec wifi: mt76: fix crash with WED rx support enabled
* 695bfba7ca781 wifi: mt76: mt7925: fix typo in mt7925_init_he_caps
* 7a934b5cc3f45 wifi: mt76: mt7921: fix 6GHz disabled by the missing default
CLC config
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux source package in Noble:
Confirmed
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[linux-firmware SRU Justification]
[Impact]
Missing firmware for Mediatek MT7925 WiFi/BT.
[Fix]
Upstream firmware commits:
- WiFi: 4de2d71b322b ("linux-firmware: add firmware for MT7925")
- Bluetooth: b83108216200 ("linux-firmware: add firmware for mediatek
bluetooth
chip (MT7925)")
[Test Case]
Initial hardware support. One should be able to find WiFi/BT interfaces up
available along with proposed kernels.
[Where problems could occur]
Features for MT7925 are not all available at this moment, and expect more
fixes
for every corner case.
[Other Info]
MT7925 is supported since v6.7, and we need it for oem-6.5 as well. Nominate
for Jammy and Noble.
== original bug report ==
* WiFi
- kernel:
https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/
* ebe81e6b8659 wifi: mt76: connac: add more unified event IDs
* 3c1199134874 wifi: mt76: connac: add more unified command IDs
* 473f26fb167e wifi: mt76: connac: add data field in struct tlv
* 975cd4d6d547 wifi: mt76: connac: add eht support for tx power
* e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config
* d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925
* 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init
* 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a
* Bluetooth
- kernel:
https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786
- firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2043542] Re: Support Mediatek MT7925 WiFi/BT
** Summary changed: - Add MT7925 WiFi/BT support + Support Mediatek MT7925 WiFi/BT -- 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/2043542 Title: Support Mediatek MT7925 WiFi/BT Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Incomplete Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: * WiFi - kernel: https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/ * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs * 3c1199134874 wifi: mt76: connac: add more unified command IDs * 473f26fb167e wifi: mt76: connac: add data field in struct tlv * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925 * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset - firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a * Bluetooth - kernel: https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786 - firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2043542] Re: Add MT7925 WiFi/BT support
** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Noble) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/2043542 Title: Support Mediatek MT7925 WiFi/BT Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.5 source package in Jammy: Incomplete Status in linux-firmware source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: * WiFi - kernel: https://lore.kernel.org/all/cover.1690863143.git.deren...@mediatek.com/ * ebe81e6b8659 wifi: mt76: connac: add more unified event IDs * 3c1199134874 wifi: mt76: connac: add more unified command IDs * 473f26fb167e wifi: mt76: connac: add data field in struct tlv * 975cd4d6d547 wifi: mt76: connac: add eht support for tx power * e9eac4eb1bbd wifi: mt76: connac: add eht support for phy mode config * d3d7f57e5c1c wifi: mt76: connac: export functions for mt7925 * 69f94b9fab06 wifi: mt76: mt792x: support mt7925 chip init * 525209262f9c wifi: mt76: connac: introduce helper for mt7925 chipset - firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4de2d71b322b9289a9851b9e1ef8c29ebf01071a * Bluetooth - kernel: https://github.com/torvalds/linux/commit/4c92ae75ea7d41b6bafe10ee6f4c12ec12624786 - firmware: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=b83108216200dfece891ddc52bcde2e2860f5dc2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2043542/+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 2048977] Re: WCN6856 Wi-FI Unavailable and no function during suspend stress
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148054.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148056.html (lunar)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148057.html
(mantic)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148058.html (noble)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Due to a known silicon limitation, the following sequence is needed while
+ initialing the PCIE device on a certain devices with ASMedia chipset involved:
+
+ 1. 'hot reset' assert
+ 2. 2nd PCIe reset' assert
+ 3. Asmedia 'hot reset' deassert
+ 4. PT21 GPIO13 2nd PCIe reset' deassert.
+
+ In certain caes, the WIFI link training failed while system resumes from
+ suspend.
+
+ [Fix]
+
+ Upstream commits:
+ * 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
+ * 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
+
+ And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
+ update board-2.bin") to forfill git history dependency.
+
+ And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
+ bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
+ has not yet accept the PR for bug 2042534, it has no such problem at this
+ moment.
+
+ [Test Case]
+
+ This can be reproduced with suspend/resume stress test.
+
+ $ checkbox-cli run com.canonical.certification::stress-
+ suspend-30-cycles-with-reboots-automated
+
+ [Where problems could occur]
+
+ Opaque firmware update. No known issue found yet after the update.
+
+ [Other Info]
+
+ This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
+ Jammy for oem-6.5 included.
+
+ == original bug report ==
+
Due to a known silicon limitation, the following sequence is needed
while initialing the PCIE device on a certain devices with ASMedia
chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
The proposed fixes are:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=17509e53b97baaefeb287b98d3358da8a6e1c199
- - This FW include this LP ticket issue fix
+ - This FW include this LP ticket issue fix
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=324cc56975d7b5a375259a49667c24f2f5a4c8fe
- - The FW is to support new China regulatory support.
+ - The FW is to support new China regulatory support.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048977
Title:
WCN6856 Wi-FI Unavailable and no function during suspend stress
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Lunar:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Status in linux-firmware source package in Noble:
In Progress
Bug description:
[SRU Justification]
[Impact]
Due to a known silicon limitation, the following sequence is needed while
initialing the PCIE device on a certain devices with ASMedia chipset involved:
1. 'hot reset' assert
2. 2nd PCIe reset' assert
3. Asmedia 'hot reset' deassert
4. PT21 GPIO13 2nd PCIe reset' deassert.
In certain caes, the WIFI link training failed while system resumes from
suspend.
[Fix]
Upstream commits:
* 17509e53b97b ("ath11k: WCN6855 hw2.0: update to
WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.36")
* 324cc56975d7 ("ath11k: WCN6855 hw2.0: update board-2.bin")
And Jammy takes an additional commit d1dc30480fef ("ath11k: WCN6855 hw2.0:
update board-2.bin") to forfill git history dependency.
And while we pulled a firmware fix from github.com/kvalo/ath11k-firmware in
bug 2042534, it fails to clean cherry-pick of commit 17509e53b97b. Since Noble
has not yet accept the PR for bug 2042534, it has no such problem at this
moment.
[Test Case]
This can be reproduced with suspend/resume stress test.
$ checkbox-cli run com.canonical.certification::stress-
suspend-30-cycles-with-reboots-automated
[Where problems could occur]
Opaque firmware update. No known issue found yet after the update.
[Other Info]
This affects all series with WCN6855/WCN6856 support, Noble/Mantic/Lunar and
Jammy for oem-6.5 included.
== original bug report ==
Due to a known silicon limitation, the following
[Kernel-packages] [Bug 2048853] Re: occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to start RT ucode: -110
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
+ and finally makes wifi operative.
+
+ iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
+ iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
+ iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
+ iwlwifi :05:00.0: 0x | trm_hw_status1
+ iwlwifi :05:00.0: 0x002C27F2 | branchlink2
+ iwlwifi :05:00.0: 0x002B79AE | interruptlink1
+ ..
+ iwlwifi :05:00.0: UMAC CURRENT PC: 0x8026934e
+ iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
+ iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
+ iwlwifi :05:00.0: UMAC CURRENT PC 1: 0x8026934c
+ iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
+ iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
+ iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
+ iwlwifi :05:00.0: Function Scratch status:
+ iwlwifi :05:00.0: 0x01010101 | Func Scratch
+ iwlwifi :05:00.0: Failed to start RT ucode: -110
+ iwlwifi :05:00.0: WRT: Collecting data: ini trigger 13 fired
(delay=0ms).
+
+ [Fix]
+
+ Resolved in upstream commit 318c64abfb33 ("iwlwifi: update gl FW for
core80-165
+ release").
+
+ While the iwlwifi firmware updates come with a sequential manner, it pulls a
few
+ more:
+
+ * 765492b8b ("iwlwifi: add new FWs from core81-65 release"), already in Mantic
+ * a07fd0b96 ("iwlwifi: add new FWs from core83-55 release")
+ * f27dec616 ("iwlwifi: fix for the new FWs from core83-55 release")
+
+ These contain firmware blob for ucore 84/86, and are not used by kernels
+ < v6.7.
+
+ [Test Case]
+
+ Use checkbox reboot stress test case to observe iwlwifi dmesg logs:
+
+ $ checkbox-cli run com.canonical.certification::stress/reboot
+
+ [Where problems could occur]
+
+ Opaque firmware update. No known issue found yet after the update.
+
+ [Other Info]
+
+ This affects series with kernels that load iwlwifi ucode 83 firmware, namely
+ Noble, Mantic, and for oem-6.5, Jammy.
+
+ == original bug report ==
+
Within stress reboot tests, iwlwifi may fail to load firmware and
triggers retry, and finally makes wifi operative.
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Loaded firmware version:
83.d24e06ed.0 gl-c0-fm-c0-83.ucode
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x0071 |
NMI_INTERRUPT_UMAC_FATAL
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x02F0 |
trm_hw_status0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x |
trm_hw_status1
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002C27F2 | branchlink2
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x002B79AE |
interruptlink1
..
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC:
0x8026934e
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: LMAC2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: UMAC CURRENT PC 1:
0x8026934c
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: TCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM1 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: RCM2 CURRENT PC: 0xd0
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Function Scratch status:
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: 0x01010101 | Func Scratch
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: Failed to start RT ucode:
-110
Oct 12 00:16:21 32090 kernel: iwlwifi :05:00.0: WRT: Collecting data: ini
trigger 13 fired (delay=0ms).
Test steps:
$ checkbox-cli run com.canonical.certification::stress/reboot
Proposed fix:
* https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-
firmware.git/commit/?id=318c64abfb33c4211b002f5e5b4ff25cd19f712b
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2048853
Title:
occasional wifi firmware loading failures: wiwlwifi: BE200: Failed to
start RT ucode: -110
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Triaged
Status in linux-firmware source package in Jammy:
In Progress
Status in linux-firmware source package in Mantic:
In Progress
Status in linux-firmware source package in Noble:
Triaged
Bug description:
[SRU Justification]
[Impact]
Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
and finally makes wifi operative.
iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
iwlwifi :05:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
iwlwifi :05:00.0: 0x02F0 | trm_hw_status0
iwlwifi :05:00.0: 0x | trm_hw_status1
iwlwifi :05:00.0: 0x002C27F2 | branchlink2
iwlwifi :05:00.0:
[Kernel-packages] [Bug 2048991] Re: upstream Intel VSC firmware paths changed to intel/vsc/
Verified vsc firmware is identical to what we have at this moment, jammy
version 20220329.git681281e4-0ubuntu3.24.
for f in intel/vsc/*; do
f="${f##*/}";
if [ -f vsc/soc_a1_prod/$f ]; then
sum_new=$(md5sum intel/vsc/$f | awk '{print $1}');
sum_cur=$(md5sum vsc/soc_a1_prod/$f | awk '{print $1}');
[ "${sum_new}" = "${sum_cur}" ] || echo "Checksum mismatch for $f";
else
echo "missing $f in vsc/soc_a1_prod/"
fi;
done
--
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/2048991
Title:
upstream Intel VSC firmware paths changed to intel/vsc/
Status in linux-firmware package in Ubuntu:
New
Bug description:
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/soc_a1_prod that has been used for all
existing Intel IPU6 camera platforms.
The corresponding linux-firmware commit is in
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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 2048991] [NEW] upstream Intel VSC firmware paths changed to intel/vsc/
Public bug reported: In upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char- misc.git/commit/?h=char-misc- next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next targeting v6.8, the VSC firmware paths have been changed to intel/vsc instead of the original vsc/soc_a1_prod that has been used for all existing Intel IPU6 camera platforms. The corresponding linux-firmware commit is in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd. ** 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/2048991 Title: upstream Intel VSC firmware paths changed to intel/vsc/ Status in linux-firmware package in Ubuntu: New Bug description: In upstream commit https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char- misc.git/commit/?h=char-misc- next=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next targeting v6.8, the VSC firmware paths have been changed to intel/vsc instead of the original vsc/soc_a1_prod that has been used for all existing Intel IPU6 camera platforms. The corresponding linux-firmware commit is in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfc997c664f076c6800b749ed7ef315b1e8e76fd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2048991/+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
