[Kernel-packages] [Bug 2077140] Re: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
I will need to see what this issue is here before I submit this to the kernel team mailing list. -- 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/2077140 Title: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: New Status in linux source package in Noble: In Progress Bug description: [Impact] Add Arrow Lake H support According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. [Fix] " commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 drm/xe/arl: Add Arrow Lake H support ARL-H uses the same media and display IP as MTL, and a version 12.74 graphics IP (referred to as Xe_LPG+). From a driver point of view, we should be able to just treat the whole platform as MTL and rely on GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs different handling from MTL's Xe_LPG (i.e., workarounds). v2: Resolve conflict and Reorder PCI ids in sorted order v3: Append signed-off-by commiter to this commit Bspec: 55420 Signed-off-by: Matt Roper Signed-off-by: Dnyaneshwar Bhadane Reviewed-by: Matt Atwood Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ MACRO__(0x7D55, ## __VA_ARGS__),\ MACRO__(0x7D60, ## __VA_ARGS__),\ MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ MACRO__(0x7DD5, ## __VA_ARGS__) #define XE_LNL_IDS(MACRO__, ...) \ " https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077140_intel_arrowlake However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2081079] Re: [SRU]Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP)
HPE verified that the test kernel I provided resolved the issue. ** Description changed: [Impact] Description: Failed to install Ubuntu 24.04 on a DL380a Gen12 with Intel Sierra Forest 2P GPU There is a random write to VF BAR0's memory region that causes the kernel got MCE error. Version-Release number : Ubuntu 24.04 How reproducible: Each time Steps to reproduce - PCI segment, Intel VT-d and SR-IOV , all enabled in the BIOS - Run a fresh install on a DL380a server with 2P with GPU in slot17 Expected results No MCE and run installation w/o problem Actual results The kernel got MCE errors. Additional info: We have tracked this issue with RHEL9.4, it's caused by the following pathes. cb4a6ccf3583 perf/x86/intel/uncore: Support Sierra Forest and Grand Ridge (v6.8-rc1) 388d76175bd9 perf/x86/intel/uncore: Support IIO free-running counters on GNR (v6.8-rc1) 632c4bf6d007 perf/x86/intel/uncore: Support Granite Rapids (v6.8-rc1) b560e0cd882b perf/x86/uncore: Use u64 to replace unsigned for the uncore offsets array (v6.8-rc1) cf35791476fc perf/x86/intel/uncore: Generic uncore_get_uncores and MMIO format of SPR (v6.8-rc1) [Fix] Intel gave us a patch set that resolves the issue. https://lore.kernel.org/lkml/20240614134631.1092359-1-kan.li...@linux.intel.com/#r The following patches are required. f8a86a9bb5f7 perf/x86/intel/uncore: Support HBM and CXL PMON counters (v6.11-rc1) 15a4bd51853b perf/x86/uncore: Cleanup unused unit structure (v6.11-rc1) f76a8420444b perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (v6.11-rc1) b1d9ea2e1ca4 perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (v6.11-rc1) 80580dae65b9 perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (v6.11-rc1) 585463fee642 perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (v6.11-rc1) c74443d92f68 perf/x86/uncore: Support per PMU cpumask (v6.11-rc1) 0007f3932592 perf/x86/uncore: Save the unit control address of all units (v6.11-rc1) [Where problems could occur] [Other Info] + + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2081079_dl380a_gen12 ** Description changed: [Impact] Description: - Failed to install Ubuntu 24.04 on a DL380a Gen12 with Intel Sierra Forest 2P GPU + Failed to install GPU with Ubuntu 24.04 on a DL380a Gen12 with Intel Sierra Forest 2P There is a random write to VF BAR0's memory region that causes the kernel got MCE error. Version-Release number : Ubuntu 24.04 How reproducible: Each time Steps to reproduce - PCI segment, Intel VT-d and SR-IOV , all enabled in the BIOS - Run a fresh install on a DL380a server with 2P with GPU in slot17 Expected results No MCE and run installation w/o problem Actual results The kernel got MCE errors. Additional info: We have tracked this issue with RHEL9.4, it's caused by the following pathes. cb4a6ccf3583 perf/x86/intel/uncore: Support Sierra Forest and Grand Ridge (v6.8-rc1) 388d76175bd9 perf/x86/intel/uncore: Support IIO free-running counters on GNR (v6.8-rc1) 632c4bf6d007 perf/x86/intel/uncore: Support Granite Rapids (v6.8-rc1) b560e0cd882b perf/x86/uncore: Use u64 to replace unsigned for the uncore offsets array (v6.8-rc1) cf35791476fc perf/x86/intel/uncore: Generic uncore_get_uncores and MMIO format of SPR (v6.8-rc1) [Fix] Intel gave us a patch set that resolves the issue. https://lore.kernel.org/lkml/20240614134631.1092359-1-kan.li...@linux.intel.com/#r The following patches are required. f8a86a9bb5f7 perf/x86/intel/uncore: Support HBM and CXL PMON counters (v6.11-rc1) 15a4bd51853b perf/x86/uncore: Cleanup unused unit structure (v6.11-rc1) f76a8420444b perf/x86/uncore: Apply the unit control RB tree to PCI uncore units (v6.11-rc1) b1d9ea2e1ca4 perf/x86/uncore: Apply the unit control RB tree to MSR uncore units (v6.11-rc1) 80580dae65b9 perf/x86/uncore: Apply the unit control RB tree to MMIO uncore units (v6.11-rc1) 585463fee642 perf/x86/uncore: Retrieve the unit ID from the unit control RB tree (v6.11-rc1) c74443d92f68 perf/x86/uncore: Support per PMU cpumask (v6.11-rc1) 0007f3932592 perf/x86/uncore: Save the unit control address of all units (v6.11-rc1) [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2081079_dl380a_gen12 ** Summary changed: - [SRU]Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP) + [SRU]Ubuntu 24.04 - GPU cannot be installed with DL380a Gen12 (2P, SRF-SP) ** Summary changed: - [SRU]Ubuntu 24.04 - GPU cannot be installed with DL380a Gen12 (2P, SRF-SP) + [SRU] Ubuntu 24.04 - GPU cannot be installed with DL380a Gen12 (2P, SRF-SP) ** Description changed: [Impact] Description: Failed to install GPU with Ubuntu 24.04 on
[Kernel-packages] [Bug 2081079] [NEW] [SRU]Ubuntu 24.04 - It cannot be installed with DL380a Gen12 (2P, SRF-SP)
Public bug reported:
[Impact]
Description:
Failed to install Ubuntu 24.04 on a DL380a Gen12 with Intel Sierra Forest 2P GPU
There is a random write to VF BAR0's memory region that causes the
kernel got MCE error.
Version-Release number :
Ubuntu 24.04
How reproducible:
Each time
Steps to reproduce
- PCI segment, Intel VT-d and SR-IOV , all enabled in the BIOS
- Run a fresh install on a DL380a server with 2P with GPU in slot17
Expected results
No MCE and run installation w/o problem
Actual results
The kernel got MCE errors.
Additional info:
We have tracked this issue with RHEL9.4, it's caused by the following
pathes.
cb4a6ccf3583 perf/x86/intel/uncore: Support Sierra Forest and Grand Ridge
(v6.8-rc1)
388d76175bd9 perf/x86/intel/uncore: Support IIO free-running counters on GNR
(v6.8-rc1)
632c4bf6d007 perf/x86/intel/uncore: Support Granite Rapids (v6.8-rc1)
b560e0cd882b perf/x86/uncore: Use u64 to replace unsigned for the uncore
offsets array (v6.8-rc1)
cf35791476fc perf/x86/intel/uncore: Generic uncore_get_uncores and MMIO format
of SPR (v6.8-rc1)
[Fix]
Intel gave us a patch set that resolves the issue.
https://lore.kernel.org/lkml/20240614134631.1092359-1-kan.li...@linux.intel.com/#r
The following patches are required.
f8a86a9bb5f7 perf/x86/intel/uncore: Support HBM and CXL PMON counters
(v6.11-rc1)
15a4bd51853b perf/x86/uncore: Cleanup unused unit structure (v6.11-rc1)
f76a8420444b perf/x86/uncore: Apply the unit control RB tree to PCI uncore
units (v6.11-rc1)
b1d9ea2e1ca4 perf/x86/uncore: Apply the unit control RB tree to MSR uncore
units (v6.11-rc1)
80580dae65b9 perf/x86/uncore: Apply the unit control RB tree to MMIO uncore
units (v6.11-rc1)
585463fee642 perf/x86/uncore: Retrieve the unit ID from the unit control RB
tree (v6.11-rc1)
c74443d92f68 perf/x86/uncore: Support per PMU cpumask (v6.11-rc1)
0007f3932592 perf/x86/uncore: Save the unit control address of all units
(v6.11-rc1)
[Where problems could occur]
[Other Info]
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Michael Reed (mreed8855)
Status: Fix Released
** Affects: linux (Ubuntu Noble)
Importance: Undecided
Status: In Progress
** Affects: linux (Ubuntu Oracular)
Importance: Medium
Assignee: Michael Reed (mreed8855)
Status: Fix Released
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Michael Reed (mreed8855)
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Medium
Assignee: Michael Reed (mreed8855)
Status: In Progress
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Status: In Progress => Fix Released
** Description changed:
+ [Impact]
Description:
Failed to install Ubuntu 24.04 on a DL380a Gen12 with Intel Sierra Forest 2P
+ NVidia L40 GPU in slot17.
There is a random write to VF BAR0's memory region that causes the
kernel got MCE error.
Version-Release number :
Ubuntu 24.04
How reproducible:
Each time
Steps to reproduce
- PCI segment, Intel VT-d and SR-IOV , all enabled in the BIOS
- Run a fresh install on a DL380a server with 2P with GPU (NVidia L40) in
slot17
Expected results
No MCE and run installation w/o problem
Actual results
The kernel got MCE errors.
Additional info:
We have tracked this issue with RHEL9.4, it's caused by the following
pathes.
cb4a6ccf3583 perf/x86/intel/uncore: Support Sierra Forest and Grand Ridge
(v6.8-rc1)
388d76175bd9 perf/x86/intel/uncore: Support IIO free-running counters on GNR
(v6.8-rc1)
632c4bf6d007 perf/x86/intel/uncore: Support Granite Rapids (v6.8-rc1)
b560e0cd882b perf/x86/uncore: Use u64 to replace unsigned for the uncore
offsets array (v6.8-rc1)
cf35791476fc perf/x86/intel/uncore: Generic uncore_get_uncores and MMIO
format of SPR (v6.8-rc1)
+
+ [Fix]
+
+ [Where problems could occur]
+
+ [Other Info]
** Description changed:
[Impact]
Description:
Failed to install Ubuntu 24.04 on a DL380a Gen12 with Intel Sierra Forest 2P
+ NVidia L40 GPU in slot17.
There is a random write to VF BAR0's memory region that causes the
kernel got MCE error.
Version-Release number :
Ubuntu 24.04
How reproducible:
Each time
Steps to reproduce
- PCI segment, Intel VT-d and SR-IOV , all enabled in the BIOS
- Run a fresh install on a DL380a server with 2P with GPU (NVidia L40) in
slot17
Expected results
No MCE and run installation w/o problem
Actual results
The kernel got MCE errors.
Additional info:
We have tracked this issue with RHEL9.4, it's caused by the following
pathes.
cb4a6ccf3583 perf/x86/intel/uncore: Support Sierra Forest an
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Changed in: linux (Ubuntu Noble) Status: Won't Fix => 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Invalid Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
Closing this request for noble per Dell's request. ** Changed in: linux (Ubuntu Noble) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Noble) Status: Invalid => Won't Fix -- 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/2045233 Title: [SRU][22.04.04]: mpi3mr driver update Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Fix Released Status in linux source package in Noble: Won't Fix Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). This has been requested by both Broadcom as the upstream and by one of the larger OEM partners who are going to be selling systems with these storage controllers to customers. This series of patches includes bug fixes and support for current Broadcom controllers. [Fixes] Below are the commit IDs for the latest upstream version (v6.8). The 22.04 LTS point kernel already includes the latest mpi3mr driver version 8.0.0.69.0. Therefore, the listed commit IDs below correspond to the subsequent patches. The commit IDs listed below are in sequential order from bottom to top, indicating the order for applying the patches. linux-next d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-3 fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-2 c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data buffers part-1 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status reply descriptor f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset and Unrecoverable State c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs Mainline at 6.6/6.7 82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset 9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0 d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after controller reset e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O 6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28 9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time out [Testing] verify the mpi3mr driver is loaded verify the version string shows 8.5.1.0.0 [Regression Risk] Low. These patches are contained to the mpi3mr driver code itself and are all already accepted upstream. They cleanly pick into our 6.5 kernel tree. Broadcom has tested these and the only concern is the kernel warning below in Comment #7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2079038] Re: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch
Bun and Kinga, I need you to identify the exact patches with patch ID's from upstream needed from 6.11 to even consider this. Once I see those and if it doesn't take a major effort to backport them to 6.8 then we can consider it. Otherwise you may have to use the hwe kernel when it reaches 6.11. Lets start with the exact patch set in addition the fix you already identified. -- 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/2079038 Title: [VROC] [Ub 24.04.0/1] Kernel bug and reboot hang during recovery - missing patch Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Create RAID array (example for IMSM): mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1 mdadm -CR vol1 -l1 -n2 /dev/nvme[01]n1 2. Hot-remove one of the drive. 3. Insert drive back - recovery should start. 4. Reboot platform Expected: reboot is performed successfully. Recovery is continued. Actual: reboot hanged and call trace appeared. [ 776.416504] (sd-umoun[3359]: Failed to unmount /run/shutdown/mounts/bd36b757b23bbc6f: Device or resource busy [ 776.445568] shutdown[1]: Could not stop MD /dev/md126: Device or resource busy mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot stop container /dev/md127: member md126 still active mdadm: Cannot get exclusive access to /dev/md126:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot st[ 784.636276] (sd-exec-[3360]: /usr/lib/systemd/system-shutdown/mdadm.finalrd failed with exit status 1. op container /dev/md127: member [ 784.647309] shutdown[1]: Unable to finalize remaining file systems, MD devices, ignoring. md126 still active [ 986.549746] INFO: task shutdown:1 blocked for more than 122 seconds. [ 986.556158] Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.561586] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 986.569440] task:shutdownstate:D stack:0 pid:1 tgid:1 ppid:0 flags:0x4002 [ 986.578769] Call Trace: [ 986.581236] [ 986.583352] __schedule+0x27c/0x6b0 [ 986.586864] schedule+0x33/0x110 [ 986.590111] stop_sync_thread+0x135/0x1b0 [ 986.594143] ? __pfx_autoremove_wake_function+0x10/0x10 [ 986.599388] __md_stop_writes+0x19/0xf0 [ 986.603240] md_notify_reboot+0x93/0x160 [ 986.607186] notifier_call_chain+0x5e/0xe0 [ 986.611301] blocking_notifier_call_chain+0x41/0x70 [ 986.616201] kernel_restart+0x21/0xa0 [ 986.619881] __do_sys_reboot+0x156/0x250 [ 986.623824] __x64_sys_reboot+0x1b/0x30 [ 986.627680] x64_sys_call+0x223c/0x25c0 [ 986.631535] do_syscall_64+0x7f/0x180 [ 986.635218] ? irqentry_exit+0x43/0x50 [ 986.638990] ? exc_page_fault+0x94/0x1b0 [ 986.642932] entry_SYSCALL_64_after_hwframe+0x73/0x7b [ 986.648003] RIP: 0033:0x7da6531dea07 [ 986.651623] RSP: 002b:7fff2babce18 EFLAGS: 0246 ORIG_RAX: 00a9 [ 986.659211] RAX: ffda RBX: 0003 RCX: 7da6531dea07 [ 986.666362] RDX: 01234567 RSI: 28121969 RDI: fee1dead [ 986.673509] RBP: 7fff2babd050 R08: 0069 R09: [ 986.680662] R10: R11: 0246 R12: 0001 [ 986.687808] R13: R14: R15: 01234567 [ 986.694956] [ 986.697665] Kernel panic - not syncing: hung_task: blocked tasks [ 986.703732] CPU: 0 PID: 982 Comm: khungtaskd Not tainted 6.8.0-31-generic #31-Ubuntu [ 986.711510] Hardware name: Intel Corporation WilsonCity/WilsonCity, BIOS WLYDCRB1.SYS.0020.P84.2103030140 03/03/2021 [ 986.722061] Call Trace: [ 986.724529] [ 986.726639] dump_stack_lvl+0x48/0x70 [ 986.730326] dump_stack+0x10/0x20 [ 986.733661] panic+0x35f/0x3c0 [ 986.736738] check_hung_uninterruptible_tasks+0x279/0x320 [ 986.742157] ? __pfx_watchdog+0x10/0x10 [ 986.746011] watchdog+0xad/0xb0 [ 986.749164] kthread+0xef/0x120 [ 986.752317] ? __pfx_kthread+0x10/0x10 [ 986.756080] ret_from_fork+0x44/0x70 [ 986.760081] ? __pfx_kthread+0x10/0x10 [ 986.764201] ret_from_fork_asm+0x1b/0x30 [ 986.768473] [ 986.771197] Kernel Offset: 0x1c0 from 0x8100 (relocation range: 0x8000-0xbfff) [ 986.913304] ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- This issue is fixed in md. Please apply patch: https://github.com/torvalds/linux/commit/1ddeeb2a058d7b2a58ed9e820396b4ceb715d529 But customer also see other issue and reboot is delayed with this patch (not hanged). I cannot reproduce it on my platform, but I know that newer kernel (6.11-rc4)
[Kernel-packages] [Bug 2077140] Re: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
I have created a test kernel. Please test and provide feedback https://people.canonical.com/~mreed/misc/lp_2077140_intel_arrowlake/ -- 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/2077140 Title: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: New Status in linux source package in Noble: In Progress Bug description: [Impact] Add Arrow Lake H support According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. [Fix] " commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 drm/xe/arl: Add Arrow Lake H support ARL-H uses the same media and display IP as MTL, and a version 12.74 graphics IP (referred to as Xe_LPG+). From a driver point of view, we should be able to just treat the whole platform as MTL and rely on GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs different handling from MTL's Xe_LPG (i.e., workarounds). v2: Resolve conflict and Reorder PCI ids in sorted order v3: Append signed-off-by commiter to this commit Bspec: 55420 Signed-off-by: Matt Roper Signed-off-by: Dnyaneshwar Bhadane Reviewed-by: Matt Atwood Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ MACRO__(0x7D55, ## __VA_ARGS__),\ MACRO__(0x7D60, ## __VA_ARGS__),\ MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ MACRO__(0x7DD5, ## __VA_ARGS__) #define XE_LNL_IDS(MACRO__, ...) \ " https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077140_intel_arrowlake However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077140] Re: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
** Summary changed: - Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server + [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server ** Description changed: - According to - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c - and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel - Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. + [Impact] + Add Arrow Lake H support + + According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and + https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. + + + [Fix] " commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 - - drm/xe/arl: Add Arrow Lake H support - - ARL-H uses the same media and display IP as MTL, and a version 12.74 - graphics IP (referred to as Xe_LPG+). From a driver point of view, we - should be able to just treat the whole platform as MTL and rely on - GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs - different handling from MTL's Xe_LPG (i.e., workarounds). - - v2: Resolve conflict and Reorder PCI ids in sorted order - v3: Append signed-off-by commiter to this commit - - Bspec: 55420 - Signed-off-by: Matt Roper - Signed-off-by: Dnyaneshwar Bhadane - Reviewed-by: Matt Atwood - Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 + + drm/xe/arl: Add Arrow Lake H support + + ARL-H uses the same media and display IP as MTL, and a version 12.74 + graphics IP (referred to as Xe_LPG+). From a driver point of view, we + should be able to just treat the whole platform as MTL and rely on + GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs + different handling from MTL's Xe_LPG (i.e., workarounds). + + v2: Resolve conflict and Reorder PCI ids in sorted order + v3: Append signed-off-by commiter to this commit + + Bspec: 55420 + Signed-off-by: Matt Roper + Signed-off-by: Dnyaneshwar Bhadane + Reviewed-by: Matt Atwood + Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com - + diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ - MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ - MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ - MACRO__(0x7D55, ## __VA_ARGS__),\ - MACRO__(0x7D60, ## __VA_ARGS__),\ - MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7D55, ## __VA_ARGS__),\ + MACRO__(0x7D60, ## __VA_ARGS__),\ + MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ - MACRO__(0x7DD5, ## __VA_ARGS__) - + MACRO__(0x7DD5, ## __VA_ARGS__) + #define XE_LNL_IDS(MACRO__, ...) \ " https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h - However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server - version, which are using Linux kernel 6.8, due to this reason, can this - feature be backport to these two version, thanks! + [Where problems could occur] + + [Other Info] + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077140_intel_arrowlake + + + However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! -- 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/2077140 Title: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: New Status in linux source package in Noble: In Progress Bug description: [Impact] Add Arrow Lake H support According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. [Fix] " commit 6a9b38cc68a03b948d
[Kernel-packages] [Bug 2077140] Re: Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2077140 Title: Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: New Status in linux source package in Noble: In Progress Bug description: According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. """"" commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 drm/xe/arl: Add Arrow Lake H support ARL-H uses the same media and display IP as MTL, and a version 12.74 graphics IP (referred to as Xe_LPG+). From a driver point of view, we should be able to just treat the whole platform as MTL and rely on GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs different handling from MTL's Xe_LPG (i.e., workarounds). v2: Resolve conflict and Reorder PCI ids in sorted order v3: Append signed-off-by commiter to this commit Bspec: 55420 Signed-off-by: Matt Roper Signed-off-by: Dnyaneshwar Bhadane Reviewed-by: Matt Atwood Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ MACRO__(0x7D55, ## __VA_ARGS__),\ MACRO__(0x7D60, ## __VA_ARGS__),\ MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ MACRO__(0x7DD5, ## __VA_ARGS__) #define XE_LNL_IDS(MACRO__, ...) \ """"" https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074118] Re: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin
*** This bug is a duplicate of bug 2073525 *** https://bugs.launchpad.net/bugs/2073525 ** This bug has been marked a duplicate of bug 2073525 [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids -- 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/2074118 Title: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Noble: New Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 [Fix] Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 [Test Plan] Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: - No firmware error found. [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2074118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
** Description changed: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] + The regression risk is low + [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2076675_fvl_intel_nic_fix -- 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/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] The regression risk is low [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2076675_fvl_intel_nic_fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029905] Re: [SRU][Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.4/later LTS
A test kernel has been available since Dec. 23. I am going to close this for now. If Dell wishes to revisit this in the future I will reopen it. ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Won't Fix -- 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/2029905 Title: [SRU][Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.4/later LTS Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Won't Fix Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Won't Fix Bug description: [Impact] This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. [Fix] Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get ta
[Kernel-packages] [Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Thanks Ian, I will submit this to the kernel team mailing list for review. -- 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/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2076675_fvl_intel_nic_fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Hi Ian, I have the correct test kernel located here https://people.canonical.com/~mreed/hpe/lp_2076675_intel_fvl_fw_fails/noble/ Please test it and provide feed back. Also can you provide the regression risk for this field? [Where problems could occur] Low, medium or high risk for regression errors? Thanks, Michael -- 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/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2076675_fvl_intel_nic_fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074118] Re: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin
** Changed in: linux-firmware (Ubuntu Oracular) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu Oracular) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2074118 Title: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Noble: New Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 [Fix] Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 [Test Plan] Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: - No firmware error found. [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2074118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Oracular) Importance: Medium Assignee: Michael Reed (mreed8855) Status: In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Michael Reed (mreed8855) ** Description changed: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] + + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2076675_fvl_intel_nic_fix -- 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/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] https://code.launchpad.net/~mr
[Kernel-packages] [Bug 2076675] [NEW] [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Public bug reported: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] ** Affects: linux (Ubuntu) Importance: Medium Assignee: Michael Reed (mreed8855) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: In Progress Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Ian My apologies, I conflated this with another bug and I am sorting this out now. -- 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/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: In Progress Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073924] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
** No longer affects: linux-firmware (Ubuntu) ** No longer affects: linux-firmware (Ubuntu Oracular) -- 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/2073924 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux-firmware source package in Noble: In Progress Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/noble/+source/linux-firmware/+bug/2073924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073924] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Hi Ian, I have since found out that I need to apply this against linux-firmware. So ignore those test kernels for now. ** Package changed: linux (Ubuntu Noble) => linux-firmware (Ubuntu Noble) ** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/2073924 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Noble: In Progress Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2073924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073583] Re: [SRU][22.04.5]: mpi3mr driver update
Hi Ranjan, What is the regression risk? Also in your steps for testing, what does r0 and r1 stand for in this step "ro and r1 creation and deletion"? ** Description changed: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). [Fix] - cf82b9e866b6 : mpi3mr: Driver version update - 1c342b0548e3 : mpi3mr: Prevent PCI writes from driver during PCI error recovery - 30bafe1774f0 : mpi3mr: Support PCI Error Recovery callback handlers - 78b506984ebe : mpi3mr: Add ioctl support for HDB - d8d08d1638ce : mpi3mr: Trigger support - fc941140: mpi3mr: HDB allocation and posting for hardware and firmware buffers [Test Plan] + - Driver load/unload + - ro and r1 creation and deletion + - By using management command tested hdb + - Use sg_reset -H + - Resetting the controller in a loop. [Where problems could occur] - [Other Info] noble https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2073583_mpi3mr_update oracular https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/oracular/+ref/lp_2073583_mpi3mr_update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2073583 Title: [SRU][22.04.5]: mpi3mr driver update Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Won't Fix Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). [Fix] - cf82b9e866b6 : mpi3mr: Driver version update - 1c342b0548e3 : mpi3mr: Prevent PCI writes from driver during PCI error recovery - 30bafe1774f0 : mpi3mr: Support PCI Error Recovery callback handlers - 78b506984ebe : mpi3mr: Add ioctl support for HDB - d8d08d1638ce : mpi3mr: Trigger support - fc941140: mpi3mr: HDB allocation and posting for hardware and firmware buffers [Test Plan] - Driver load/unload - ro and r1 creation and deletion - By using management command tested hdb - Use sg_reset -H - Resetting the controller in a loop. [Where problems could occur] [Other Info] noble https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2073583_mpi3mr_update oracular https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/oracular/+ref/lp_2073583_mpi3mr_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073583] Re: [SRU][22.04.5]: mpi3mr driver update
This cherry pick will cover noble and oracular. Backporting this from 6.10 to 5.15 is not feasible for the Jammy kernel. Also this will be in the 6.8 kernel in 22.04.5. ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Won't Fix -- 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/2073583 Title: [SRU][22.04.5]: mpi3mr driver update Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Won't Fix Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). [Fix] - cf82b9e866b6 : mpi3mr: Driver version update - 1c342b0548e3 : mpi3mr: Prevent PCI writes from driver during PCI error recovery - 30bafe1774f0 : mpi3mr: Support PCI Error Recovery callback handlers - 78b506984ebe : mpi3mr: Add ioctl support for HDB - d8d08d1638ce : mpi3mr: Trigger support - fc941140: mpi3mr: HDB allocation and posting for hardware and firmware buffers [Test Plan] [Where problems could occur] [Other Info] noble https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2073583_mpi3mr_update oracular https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/oracular/+ref/lp_2073583_mpi3mr_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053224] Re: 22.04.x - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems
** Changed in: linux (Ubuntu Mantic) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053224 Title: 22.04.x - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: Won't Fix Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Bug description: [Impact] Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems Hello Team, One of our internal team has assessed that having only the 1st patch included in OS will cause issue of encountering I/O lock-up while running PowerFlex I/O workloads on drives connected to PowerEdge R750s with HBA355i. The remedy is to include the 2nd patch as well into the OS as early as possible. I have attached the details of two patches for which I would like to know status of whether they are included in the below OS already? If not, when will be they included(Need ETA)? o Ubuntu22.04.3 & 22.04.4 [Fix] Patch Details: 1.Patch-1 https://lkml.kernel.org/linux- scsi/20230713075302.10073-1-ranjan.ku...@broadcom.com/T/ 2.Patch-2 https://lore.kernel.org/linux- scsi/169868005494.2933713.2562282002343167126.b4...@oracle.com/T/ This request is for both LTS and HWE kernels. [Test Plan] On a system configured with HBA and installed ubuntu 22.04.3 1. Perform IO stress on the drives connected to HBA. 2. Observe IO applications are not functioning as anticipated, resulting in the HBA being reset and OS logs may show the following messages. “mpt3sas_cm0: sending diag reset !!" "mpt3sas_cm0: mpt3sas_base_hard_reset_handler: SUCCESS" [ Where problems could occur ] The IO-Lock up issue is observed on a system running the latest kernel of Ubuntu 22.04.3 which consist of below mentioned patch. - scsi: mpt3sas: Perform additional retries if doorbell read returns 0 [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2053224_ifix_io_lockup Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fix_io_loop_poweredge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2053224] Re: 22.04.x - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems
** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: Fix Committed ** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress ** Information type changed from Private to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2053224 Title: 22.04.x - Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: Incomplete Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Released Bug description: [Impact] Request to Add Patches to fix the I/O Lock Up issues on PowerEdge Systems Hello Team, One of our internal team has assessed that having only the 1st patch included in OS will cause issue of encountering I/O lock-up while running PowerFlex I/O workloads on drives connected to PowerEdge R750s with HBA355i. The remedy is to include the 2nd patch as well into the OS as early as possible. I have attached the details of two patches for which I would like to know status of whether they are included in the below OS already? If not, when will be they included(Need ETA)? o Ubuntu22.04.3 & 22.04.4 [Fix] Patch Details: 1.Patch-1 https://lkml.kernel.org/linux- scsi/20230713075302.10073-1-ranjan.ku...@broadcom.com/T/ 2.Patch-2 https://lore.kernel.org/linux- scsi/169868005494.2933713.2562282002343167126.b4...@oracle.com/T/ This request is for both LTS and HWE kernels. [Test Plan] On a system configured with HBA and installed ubuntu 22.04.3 1. Perform IO stress on the drives connected to HBA. 2. Observe IO applications are not functioning as anticipated, resulting in the HBA being reset and OS logs may show the following messages. “mpt3sas_cm0: sending diag reset !!" "mpt3sas_cm0: mpt3sas_base_hard_reset_handler: SUCCESS" [ Where problems could occur ] The IO-Lock up issue is observed on a system running the latest kernel of Ubuntu 22.04.3 which consist of below mentioned patch. - scsi: mpt3sas: Perform additional retries if doorbell read returns 0 [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2053224_ifix_io_lockup Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fix_io_loop_poweredge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074118] Re: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Noble) ** No longer affects: linux (Ubuntu Oracular) ** Changed in: linux-firmware (Ubuntu Noble) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux-firmware (Ubuntu Oracular) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/2074118 Title: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Noble: New Status in linux-firmware source package in Oracular: New Bug description: [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 [Fix] Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 [Test Plan] Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: - No firmware error found. [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2074118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073583] Re: [SRU][22.04.5]: mpi3mr driver update
Hi Ranjan, 1: What kernel version you want this to land in. 22.04.5 has two different kernel versions. [Ranjan] : It should be included in both LTS and HWE Just to clarify, when 22.04.5 is released the kernel version will bump up to 6.8. Are you requesting that the 5.15 kernel is patched also? I ask this because I did a preliminary cherry-pick of two patches to 5.15 and they did not pick cleanly. 2: I already patched and built noble and oracular and those test kernels are ready to be tested. -- 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/2073583 Title: [SRU][22.04.5]: mpi3mr driver update Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Incomplete Status in linux source package in Noble: In Progress Status in linux source package in Oracular: In Progress Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). [Fix] - cf82b9e866b6 : mpi3mr: Driver version update - 1c342b0548e3 : mpi3mr: Prevent PCI writes from driver during PCI error recovery - 30bafe1774f0 : mpi3mr: Support PCI Error Recovery callback handlers - 78b506984ebe : mpi3mr: Add ioctl support for HDB - d8d08d1638ce : mpi3mr: Trigger support - fc941140: mpi3mr: HDB allocation and posting for hardware and firmware buffers [Test Plan] [Where problems could occur] [Other Info] noble https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2073583_mpi3mr_update oracular https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/oracular/+ref/lp_2073583_mpi3mr_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074118] Re: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin
** Also 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 in Ubuntu. https://bugs.launchpad.net/bugs/2074118 Title: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Status in linux source package in Noble: New Status in linux-firmware source package in Noble: New Status in linux source package in Oracular: New Status in linux-firmware source package in Oracular: New Bug description: [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 [Fix] Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 [Test Plan] Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: - No firmware error found. [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074118] Re: Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin
Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 -- 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/2074118 Title: [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin Status in linux package in Ubuntu: New Status in linux source package in Noble: New Status in linux source package in Oracular: New Bug description: [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 [Fix] Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 [Test Plan] Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: - No firmware error found. [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074118] Re: Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin
dmesg ** Attachment added: "dmesg-1-qat-firmware_error.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074118/+attachment/5800366/+files/dmesg-1-qat-firmware_error.txt ** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: New ** Summary changed: - Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin + [SRU] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin ** Description changed: + [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 Additional info: The required firmware qat_402xx_mmp.bin has not yet been released to linux-firmware.git. We hope the firwmare can be included to the OS system once Intel releases the FW. + + [Fix] + + Intel pushed required firmware qat_402xx.* firmware to the upstream + linux-firmware git repo. + + https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- + firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 + + [Test Plan] + + Steps to reproduce: + - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) + - boot to system and the firmware errors are observed + + Expected results: + - No firmware error found. + + [Where problems could occur] + + [Other Info] ** Description changed: [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 - Additional info: - The required firmware qat_402xx_mmp.bin has not yet been released to linux-firmware.git. - - We hope the firwmare can be included to the OS system once Intel - releases the FW. - [Fix] Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 [Test Plan] Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: - No firmware error found. [Where problems could occur] [Other Info] ** Description changed: [Impact] Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 [Fix] - - Intel pushed required firmware qat_402xx.* firmware to the upstream - linux-firmware git repo. + Intel pushed required firmware qat_402xx.* firmware to the upstream linux-firmware git repo. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=74e4ad17d748f29d25d0f31e070519375522e6a1 + [Test Plan] - Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system
[Kernel-packages] [Bug 2074118] [NEW] Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin
Public bug reported: Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 Additional info: The required firmware qat_402xx_mmp.bin has not yet been released to linux-firmware.git. We hope the firwmare can be included to the OS system once Intel releases the FW. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** 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/2074118 Title: Ubuntu 24.04 Failed to load MMP firmware qat_402xx_mmp.bin Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Description: Intel QAT device cannot work properly since there is no required firmware. How reproducible: Each time Steps to reproduce: - install Ubuntu 24.04 server on a server with a Intel Sierra Forest SP CPU (Gen12) - boot to system and the firmware errors are observed Expected results: No firmware error found. Actual results: The firmware errors are observed [ 7.448283] 4xxx :01:00.0: enabling device (0140 -> 0142) [ 7.456559] 4xxx :01:00.0: Direct firmware load for qat_402xx_mmp.bin failed with error -2 [ 7.456564] 4xxx :01:00.0: Failed to load MMP firmware qat_402xx_mmp.bin [ 7.456570] 4xxx :01:00.0: Failed to load acceleration FW [ 7.457112] 4xxx :01:00.0: Resetting device qat_dev0 [ 7.568591] 4xxx: probe of :01:00.0 failed with error -14 Additional info: The required firmware qat_402xx_mmp.bin has not yet been released to linux-firmware.git. We hope the firwmare can be included to the OS system once Intel releases the FW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073924] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
Hi Ian, When I refer to regression risk, I am asking what are the chances this breaks the kernel for any release. -- 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/2073924 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Source: https://www.kernel.org/doc/Documentation/memory-hotplug.txt
How to online memory
When the memory is hot-added, the kernel decides whether or not to "online"
it according to the policy which can be read from "auto_online_blocks" file::
% cat /sys/devices/system/memory/auto_online_blocks
The default depends on the CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE kernel config
option. If it is disabled the default is "offline" which means the newly added
memory is not in a ready-to-use state and you have to "online" the newly added
memory blocks manually. Automatic onlining can be requested by writing "online"
to "auto_online_blocks" file::
% echo online > /sys/devices/system/memory/auto_online_blocks
This sets a global policy and impacts all memory blocks that will subsequently
be hotplugged.
If this is enabled by default then the following should achieve the same
goal as disabling the config option:
echo offline > /sys/devices/system/memory/auto_online_blocks
--
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/2028158
Title:
[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set
to flat mode. Duplicate device_dax ids were created and hence probing
is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"6
[Kernel-packages] [Bug 2057454] Re: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM.
I have not been able to recreate this issue. I was able to install an R760 with 24.04 with and without enabling openssh during an install using the Virtual Media. Can you try the latest daily build image that was released today? https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/ -- 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/2057454 Title: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM. Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: On Dell PowerEdge system unable to complete Installation of Ubuntu 24.04 using ISO mounted by Virtual media option. Steps to Reproduce: - 1. Attach Ubuntu 24.04 ISO to RFS path of Virtual media. 2. Boot to F11 and select the Virtual Optical drive from Oneshot UEFI boot menu. 3. Begin the Ubuntu24.04 Installation. 4. Installation was failed. Expected Results: - The Installation should be successful without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057454] Re: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM.
This issue can be reproducible on 16G Platform also and below are the possible workarounds found during the experiments on 16G Platform. 1. During Installation of Ubuntu 24.04 when we disable/exclude [] Openssh server package issue won't be reproduced. After reboot and installing openssh server using 'apt-get install openssh-server' system is working as expected. 2. During Installation of Ubuntu 24.04 when we enable/include [x]Openssh server package. we are able to repro the issue. Thanks, Shubhakara P S -- 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/2057454 Title: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM. Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: On Dell PowerEdge system unable to complete Installation of Ubuntu 24.04 using ISO mounted by Virtual media option. Steps to Reproduce: - 1. Attach Ubuntu 24.04 ISO to RFS path of Virtual media. 2. Boot to F11 and select the Virtual Optical drive from Oneshot UEFI boot menu. 3. Begin the Ubuntu24.04 Installation. 4. Installation was failed. Expected Results: - The Installation should be successful without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2057454] Re: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM.
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Also affects: linux (Ubuntu Noble) Importance: Critical 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/2057454 Title: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM. Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: On Dell PowerEdge system unable to complete Installation of Ubuntu 24.04 using ISO mounted by Virtual media option. Steps to Reproduce: - 1. Attach Ubuntu 24.04 ISO to RFS path of Virtual media. 2. Boot to F11 and select the Virtual Optical drive from Oneshot UEFI boot menu. 3. Begin the Ubuntu24.04 Installation. 4. Installation was failed. Expected Results: - The Installation should be successful without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes
** Description changed: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] 1. Driver load and unload 2. Create and delete different virtual drives (R0, R1, R5 etc.,) 3. create JBOD 4. Run IOs with different profiles (io_depth, io_size etc.,) on VD and JBOD 5. controller reset while running IOs - [ Where problems could occur ] It has a critical patch which fixes the issue related to various register reads. So IO runs and various internal commands where problems could occur [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update + + Noble + These patches are already in Noble -- 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/2046722 Title: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] 1. Driver load and unload 2. Create and delete different virtual drives (R0, R1, R5 etc.,) 3. create JBOD 4. Run IOs with different profiles (io_depth, io_size etc.,) on VD and JBOD 5. controller reset while running IOs [ Where problems could occur ] It has a critical patch which fixes the issue related to various register reads. So IO runs and various internal commands where problems could occur [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update Noble These patches are already in Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes
Hi Chandrakanth, Thank you for filing is the requested fields. I have one more request, can you also add what the regression risk will be? This will be included under [ Where problems could occur ]. Thanks, Michael ** Description changed: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: - [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] + 1. Driver load and unload + 2. Create and delete different virtual drives (R0, R1, R5 etc.,) + 3. create JBOD + 4. Run IOs with different profiles (io_depth, io_size etc.,) on VD and JBOD + 5. controller reset while running IOs + + [ Where problems could occur ] - + It has a critical patch which fixes the issue related to various register reads. So IO runs and various internal commands where problems could occur [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update - Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046722 Title: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] 1. Driver load and unload 2. Create and delete different virtual drives (R0, R1, R5 etc.,) 3. create JBOD 4. Run IOs with different profiles (io_depth, io_size etc.,) on VD and JBOD 5. controller reset while running IOs [ Where problems could occur ] It has a critical patch which fixes the issue related to various register reads. So IO runs and various internal commands where problems could occur [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes
Hi Chandrakanth, Thank you for testing the test kernels. Can you also fill in these fields for the SRU process? I need that information when submitting these to the mailing list. [Test Plan] [ Where problems could occur ] [ Other Info ] -- 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/2046722 Title: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] [ Where problems could occur ] [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
All of these patches are in the latest master-next noble kernel. git describe --tags Ubuntu-6.8.0-11.11-1-g04cdb2da2df3 ** Changed in: linux (Ubuntu Noble) Status: Confirmed => Fix Committed -- 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/2044589 Title: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: This request is to add support for SAS5116 controller and few critical bug-fixes in Ubuntu 24.04 LTS. Below is the list of upstream commits that adds support for SAS5116: b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50 1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32 c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from SAS4116 6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046875] Re: [22.04.04]: mpt3sas: Critical Bug Fixes
This is a public version of the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224 -- 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/2046875 Title: [22.04.04]: mpt3sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: 3c978492c333 : scsi: mpt3sas: Fix loop logic 0854065092a7 : scsi: mpt3sas: Remove volatile qualifier 4ca10f3e3174 : scsi: mpt3sas: Perform additional retries if doorbell read returns 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes
This is a public version of the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053224 -- 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/2046722 Title: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] [ Where problems could occur ] [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
I have created tests kernels for both Jammy and Mantic. Please test and provide feedback. Jammy https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/jammy/ Mantic https://people.canonical.com/~mreed/misc/lp_2046722_megaraid_sas_update/mantic/ -- 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/2046722 Title: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] [ Where problems could occur ] [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
These patches are already in 6.8 ** Summary changed: - [22.04.04]: megaraid_sas: Critical Bug Fixes + [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Michael Reed (mreed8855) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Michael Reed (mreed8855) Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Fix Committed ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/2046722 Title: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] [ Where problems could occur ] [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
Hi Chandrakanth, Can you also fill in these fields for the SRU process in addition to testing the test kernels [Test Plan] [ Where problems could occur ] [ Other Info ] -- 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/2046722 Title: [SRU][22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Fix Committed Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] [ Where problems could occur ] [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
** Description changed: + [Impact] + This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: + + [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() + The change log for the above commit IDs is small and doesn't require + rigorous validation. So please include these patches. - The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. + [Test Plan] + + [ Where problems could occur ] + + [ Other Info ] + + Jammy + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update + + + Mantic + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046722 Title: [22.04.04]: megaraid_sas: Critical Bug Fixes Status in linux package in Ubuntu: New Bug description: [Impact] This update has been initiated to include a few critical bug fixes from upstream into the upcoming 22.04.04 point kernel. Below are the upstream commit IDs: [Fix] 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() The change log for the above commit IDs is small and doesn't require rigorous validation. So please include these patches. [Test Plan] [ Where problems could occur ] [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2046722_megaraid_sas_update Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/lp_2046722_megaraid_sas_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046726] Re: [24.04 LTS]: megaraid_sas driver update
I have verified that all of the patches listed in the description are indeed in the currently 6.8 proposed kernel and should be in 24.04. $ git describe --tags Ubuntu-6.8.0-11.11-1-g04cdb2da2df3 -- 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: New Bug description: This update has been initiated to incorporate the megaraid_sas driver from upstream into the upcoming Ubuntu 24.04 LTS release. Assuming the 24.04 already included the patches up to driver version 07.725.01.00-rc1. So, below are the commit IDs after it. 0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1 2d83fb023c90 scsi: megaraid_sas: Log message when controller reset is requested but not issued 8e3ed9e78651 scsi: megaraid_sas: Increase register read retry count from 3 to 30 for selected registers 0b0747d507bf scsi: megaraid_sas: Fix deadlock on firmware crashdump bb1459cb84da scsi: megaraid: Use pci_dev_id() to simplify the code a46421fdf7e9 scsi: megaraid_sas: Use pci_dev_id() to simplify the code d67790ddf021 overflow: Add struct_size_t() helper aa67380056a4 scsi: megaraid_sas: Convert union megasas_sgl to flex-arrays 2309df27111a scsi: megaraid_sas: Fix crash after a double completion 0808ed6ebbc2 scsi: megaraid_sas: Fix fw_crash_buffer_show() 264e222b004c scsi: megaraid: Declare SCSI host template const To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
r CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get target object based on rphy e22bae30667a scsi: mpi3mr: Add expander devices to STL c4723e68a0d8 scsi: mpi3mr: Enable STL on HBAs where multipath is disabled 42fc9fee116f scsi: mpi3mr: Add helper functions to manage device's port 125ad1e6b445 scsi: mpi3mr: Add helper functions to retrieve device objects fc7212fd3100 scsi: mpi3mr: Add framework to add phys to STL 7188c03ff884 scsi: mpi3mr: Enable Enclosure device add event 64a8d9315b85 scsi: mpi3mr: Add helper functions to retrieve config pages 32d457d5a2af scsi: mpi3mr: Add framework to issue config requests 3b73c45e6fd2 scsi: mpi3mr: Add config and transport related debug flags 502f4c18704d scsi: mpi3mr: Delete a stray tab 2a8a0147cb52 scsi: mpi3mr: Unlock on error path cf1ce8b71524 scsi: mpi3mr: Reduce VD queue depth on detecting throttling f10af057325c scsi: mpi3mr: Resource Based Metering d29ea7b71621 scsi: mpi3mr: Increase cmd_per_lun to 128 465191d6526a scsi: mpi3mr: Enable shared host tagset 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [ Where problems could occur ] [ Other Info ] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_update3 ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2029905 Title: [SRU][Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.4/later LTS Status in linux package in Ubuntu: Fix Committed 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: Fix Committed Bug description: [Impact] This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. [Fix] Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=
[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
In the latest branch CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE is no longer
disabled
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
** Description changed:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set to
flat mode. Duplicate device_dax ids were created and hence probing is
failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
By default this is enabled, but it is causing an issue reconfiguring device
dax memory, thus
it is being disabled.
Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE
Set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=N
[Where problems could occur]
[Other Info]
+
+
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2028158_device_dax_2
+
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
},
{
"chardev":"dax5.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabl
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
** Description changed:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
- * The regression leads to the boot failure (cannot boot info OS
successfully).
+ * The regression leads to the boot failure (cannot boot info OS successfully).
[ Other Info ]
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
+
+
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022
** Description changed:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS successfully).
[ Other Info ]
-
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
+
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022
--
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/2020022
Title:
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
in UEFI setup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue
[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy
Here is the test kernel for Mantic https://people.canonical.com/~mreed/cisco/lp_2036777/mantic/ -- 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/2036777 Title: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. 924cb24df4fcscsi: fnic: Stop using the SCSI pointer b559b99a5c081 scsi: fnic: Replace DMA mask of 64 bits with 47 bits 5a43b07a87835 scsi: fnic: Replace return codes in fnic_clean_pending_aborts() 15924b0503630 scsi: fnic: Replace sgreset tag with max_tag_id 514f0c400bde6 scsi: fnic: Fix sg_reset success path [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/fnic_11_10_23 Mantic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fnic_update_2036777 Links to first 3 patches https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy
These patches were also needed. 924cb24df4fcscsi: fnic: Stop using the SCSI pointer b559b99a5c081 scsi: fnic: Replace DMA mask of 64 bits with 47 bits ** Description changed: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] + + Jammy + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/fnic_11_10_23 + + Mantic + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fnic_update_2036777 ** Description changed: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. - https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ + 924cb24df4fcscsi: fnic: Stop using the SCSI pointer + b559b99a5c081 scsi: fnic: Replace DMA mask of 64 bits with 47 bits + 5a43b07a87835 scsi: fnic: Replace return codes in fnic_clean_pending_aborts() + 15924b0503630 scsi: fnic: Replace sgreset tag with max_tag_id + 514f0c400bde6 scsi: fnic: Fix sg_reset success path - https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ - - https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] - Jammy - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/fnic_11_10_23 - Mantic - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/mantic/+ref/fnic_update_2036777 + + Links to first 3 patches + https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ + https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ + https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ ** Description changed: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
I created a 6.2 test kernel for Lunar.Please test
https://people.canonical.com/~mreed/lenovo/lp_2020022_vmd/lunar/12062023/
--
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/2020022
Title:
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
in UEFI setup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS
successfully).
[ Other Info ]
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy
** Changed in: linux (Ubuntu Noble) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Mantic) 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/2036777 Title: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Jeff Lane (bladernr)
Status: Fix Released
--
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/2020022
Title:
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
in UEFI setup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
In Progress
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS
successfully).
[ Other Info ]
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/lunar/+ref/LP2020022
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy
Here is a test kernel for Jammy. https://people.canonical.com/~mreed/cisco/lp_2036777/ ** Also affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Michael Reed (mreed8855) Status: Incomplete ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: Invalid => New ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036777 Title: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy Status in linux package in Ubuntu: Incomplete 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: Incomplete Status in linux source package in Noble: Incomplete Bug description: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
This patch is also needed for a clean build. 3d8fa78ebd61 scsi: scsi_transport_sas: Add 22.5 Gbps link rate definitions -- 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/2029905 Title: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Bug description: This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get target object based on rphy e22ba
[Kernel-packages] [Bug 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
Here is the test kernel. https://people.canonical.com/~mreed/dell/lp_2029905_mpi3mr/ -- 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/2029905 Title: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Incomplete Status in linux source package in Lunar: Won't Fix Status in linux source package in Mantic: Fix Committed Bug description: This BUG is created to integrate the latest mpi3mr driver available upstream into the upcoming Ubuntu LTS OS inbox driver. - The mpi3mr inbox driver version available in the latest LTS (22.04.02) is 8.0.0.69.0. which is considerably the base driver + management app support. - The latest mpi3mr driver available in the upstream is 8.4.1.0.0 which has various important features and critical bugs. Please include below the latest mpi3mr upstream patset: git online commit id and description: f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O f762326b2baa scsi: mpi3mr: Propagate sense data for admin queue SCSI I/O 144679dfb584 scsi: mpi3mr: Fix the type used for pointers to bitmap 2a954832015d scsi: mpi3mr: Use -ENOMEM instead of -1 in mpi3mr_expander_add() 2acc635a0e5e scsi: mpi3mr: Use IRQ save variants of spinlock to protect chain frame allocation a3d27dfdcfc2 scsi: mpi3mr: Handle soft reset in progress fault code (0xF002) b85f82f3c92a scsi: mpi3mr: Declare SCSI host template const 1ea41edd88f2 scsi: mpi3mr: Update driver version to 8.4.1.0.0 e74f2fbd8b06 scsi: mpi3mr: Update copyright year 80b8fd0231d5 scsi: mpi3mr: Fix W=1 compilation warnings e5f596bc2592 scsi: mpi3mr: Update MPI Headers to revision 27 f1dec6b1e25e scsi: mpi3mr: Avoid escalating to higher level reset when target is removed 22beef38e52c scsi: mpi3mr: Modify MUR timeout value to 120 seconds 23b3d1cf1572 scsi: mpi3mr: Fix admin queue memory leak upon soft reset 3f1254ed01d0 scsi: mpi3mr: Successive VD delete and add causes FW fault ce756daa36e1 scsi: mpi3mr: Fix expander node leak in mpi3mr_remove() c798304470ca scsi: mpi3mr: Fix memory leaks in mpi3mr_init_ioc() d4caa1a4255c scsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove() d0f3c3728da8 scsi: mpi3mr: Fix mpi3mr_hba_port memory leak in mpi3mr_remove() 7d2b02172b6a scsi: mpi3mr: Fix config page DMA memory leak f305a7b6ca21 scsi: mpi3mr: Fix throttle_groups memory leak 8e45183978d6 scsi: mpi3mr: Bad drive in topology results kernel crash 4f297e856a7b scsi: mpi3mr: NVMe command size greater than 8K fails ba8a9ba41fbd scsi: mpi3mr: Return proper values for failures in firmware init path 0a319f162949 scsi: mpi3mr: Wait for diagnostic save during controller init 5b06a7169c59 scsi: mpi3mr: Driver unload crashes host when enhanced logging is enabled 02ca7da2919a scsi: mpi3mr: ioctl timeout when disabling/enabling interrupt 66b381d874fa scsi: mpi3mr: Remove unneeded version.h include e39ea831ebad scsi: mpi3mr: Fix missing mrioc->evtack_cmds initialization 339e61565f81 scsi: mpi3mr: Use number of bits to manage bitmap sizes eeb270aee3e0 scsi: mpi3mr: Remove unnecessary memcpy() to alltgt_info->dmi fb428a2005fc scsi: mpi3mr: Fix issues in mpi3mr_get_all_tgt_info() ae7d45f5283d scsi: mpi3mr: Fix an issue found by KASAN f0a43ba6c66c scsi: mpi3mr: Refer CONFIG_SCSI_MPI3MR in Makefile d347a951906b scsi: mpi3mr: Remove usage of dma_get_required_mask() API 7d21fcfb4095 scsi: mpi3mr: Suppress command reply debug prints 65244389b1b3 scsi: mpi3mr: Select CONFIG_SCSI_SAS_ATTRS c863a2dcb9b0 scsi: mpi3mr: Remove unnecessary cast f616efbee9d6 scsi: mpi3mr: Update driver version to 8.2.0.3.0 2e31be8697b1 scsi: mpi3mr: Fix scheduling while atomic type bug f84e8b5bb57e scsi: mpi3mr: Scan the devices during resume time 130fc180a481 scsi: mpi3mr: Free enclosure objects during driver unload bad2f28da625 scsi: mpi3mr: Handle 0xF003 Fault Code f2a79d2030ad scsi: mpi3mr: Graceful handling of surprise removal of PCIe HBA 7f9f953d537a scsi: mpi3mr: Schedule IRQ kthreads only on non-RT kernels 47cd930ee6ae scsi: mpi3mr: Support new power management framework ee6f2d6bb2a0 scsi: mpi3mr: Update mpi3 header files 5ba207e55e7f scsi: mpi3mr: Fix error code in mpi3mr_transport_smp_handler() a113c02f5738 scsi: mpi3mr: Fix error codes in mpi3mr_report_manufacture() 7f90bc70d1a6 scsi: mpi3mr: Block I/Os while refreshing target dev objects 2745ce0e6d30 scsi: mpi3mr: Refresh SAS ports during soft reset 176d4aa69c6e scsi: mpi3mr: Support SAS transport class callbacks 2bd37e284914 scsi: mpi3mr: Add framework to issue MPT transport cmds 7f56c791969e scsi: mpi3mr: Add SAS SATA end devices to STL 626665e9c38d scsi: mpi3mr: Get target object based on rphy e22bae30667a scsi: mpi3mr: Add expander dev
[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy
The first patch is already in Jammy commit 06adda263bd3776b019f282318efe18dd5bfa173 Author: Karan Tilak Kumar Date: Thu Jul 27 12:39:19 2023 -0700 scsi: fnic: Replace return codes in fnic_clean_pending_aborts() BugLink: https://bugs.launchpad.net/bugs/2038382 commit 5a43b07a87835660f91d88a4db11abfea8c523b7 upstream. fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. Reviewed-by: Sesidhar Baddela Tested-by: Karan Tilak Kumar Signed-off-by: Karan Tilak Kumar Link: https://lore.kernel.org/r/20230727193919.2519-1-karti...@cisco.com Signed-off-by: Martin K. Petersen Signed-off-by: Greg Kroah-Hartman Signed-off-by: Kamal Mostafa Signed-off-by: Stefan Bader -- 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/2036777 Title: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Incomplete Bug description: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036777] Re: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy
** Summary changed: - [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Focal + [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2036777 Title: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Jammy Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Incomplete Bug description: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036777] Re: fnic driver on needs to be updated to 1.6.0.57 on Focal
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Michael Reed (mreed8855) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: Michael Reed (mreed8855) Status: Incomplete ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Summary changed: - fnic driver on needs to be updated to 1.6.0.57 on Focal + [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Focal ** Description changed: + [Impact] + fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. - sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. + [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. + Below are the kernel patches which picked for the newer version of fins + driver. + + https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ + + https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ + + https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ + + [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. - below are the kernel patches which picked for the newer version of fins - driver. + [ Where problems could occur ] - - https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ - - https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ - - https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ + [ Other Info ] ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/2036777 Title: [SRU] Fnic driver on needs to be updated to 1.6.0.57 on Focal Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Status in linux source package in Lunar: New Status in linux source package in Mantic: Incomplete Bug description: [Impact] fnic_clean_pending_aborts() was returning a non-zero value irrespective of failure or success. This caused the caller of this function to assume that the device reset had failed, even though it would succeed in most cases. As a consequence, a successful device reset would escalate to host reset. sgreset is issued with a scsi command pointer. The device reset code assumes that it was issued on a hardware queue, and calls block multiqueue layer. However, the assumption is broken, and there is no hardware queue associated with the sgreset, and this leads to a crash due to a null pointer exception. [Fix] Fix the code to use the max_tag_id as a tag which does not overlap with the other tags issued by mid layer. Below are the kernel patches which picked for the newer version of fins driver. https://lore.kernel.org/lkml/20230727193919.2519-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230817182146.229059-1-karti...@cisco.com/ https://lore.kernel.org/lkml/20230919182436.6895-1-karti...@cisco.com/ [Test Plan] Tested by running FC traffic for a few minutes, and by issuing sgreset on the device in parallel. Without the fix, the crash is observed right away. With this fix, no crash is observed. sg_reset performs a device reset/lun reset on a lun. Since it is issued by the user, it does not come into the driver with a tag or a queue id. Fix the fnic driver to create an io_req and use a scsi command tag. Fix the ITMF path to special case the sg_reset response. [ Where problems could occur ] [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.laun
[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
** Description changed:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set to
flat mode. Duplicate device_dax ids were created and hence probing is
failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE
Set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=N
[Where problems could occur]
+
[Other Info]
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can change the devdax
to
system-ram
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"devdax" ---> HBM CPU 1, This we can change the devdax
to
system-ram
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i error
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
After reconfig-device devdax to system-ram below are the results:
---
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax0.0 -u
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl reconfigure-device -m system-ram dax1.0 -u
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
reconfigured 1 device
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax4.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
},
{
"chardev":"dax5.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram", ---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i dax
[ 12.748880] device_dax dax2.0: mapping0: 0x208000-0x307f
[Kernel-packages] [Bug 2028158] Re: [SRU] Duplicate device_dax ids created and hence probing is failing.
bled"
},
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"system-ram",---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
},
{
"chardev":"dax5.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax2.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax3.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3, > Duplicate device
"align":2097152,
"mode":"devdax",
"state":"disabled"
},
{
"chardev":"dax0.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":2,
"align":2097152,
"mode":"system-ram", ---> Converted from devdax - system-ram
"online_memblocks":32,
"total_memblocks":32,
"movable":true
}
]
root@ubuntu:/home/ubuntu# dmesg | grep -i dax
[ 12.748880] device_dax dax2.0: mapping0: 0x208000-0x307fff could
not reserve range
[ 12.748884] device_dax: probe of dax2.0 failed with error -16
[ 12.748901] device_dax dax3.0: mapping0: 0x508000-0x607fff could
not reserve range
[ 12.748902] device_dax: probe of dax3.0 failed with error -16
[ 812.677056] device_dax dax4.0: mapping0: 0x208000-0x307fff could
not reserve range
[ 812.677070] device_dax: probe of dax4.0 failed with error -16
[ 821.092762] device_dax dax5.0: mapping0: 0x508000-0x607fff could
not reserve range
[ 821.092774] device_dax: probe of dax5.0 failed with error -16
** Information type changed from Private to Public
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Michael Reed (mreed8855)
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2028158
Title:
[SRU] Duplicate Device_dax ids Created and hence Probing is Failing.
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
In Progress
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[Impact]
Description of problem:
Observed device_dax related probe errors in dmesg when HBM CPU is set
to flat mode. Duplicate device_dax ids were created and hence probing
is failing.
How reproducible:
Frequently
Version-Release
Release:22.04.2, 22.10
[Test Case]
Steps to Reproduce:
1. Set HBM cpu to flat mode in memory settings in BIOS.
2. Boot to the OS.
3. Perform OS warm boot cycle test.
4. Observe the dax2.0/dax3.0/dax4.0/dax5.0 probe error.
Actual results:
Observed device_dax related errors in dmesg, device Dax is creating
dummy/duplicate devices and probe failing.
Expected results:
Dummy/duplicate devices should not create.
[Fix]
Upstream Fix
https://lore.kernel.org/linux-mm/166890823379.4183293.15333502171004313377.st...@dwillia2-xfh.jf.intel.com/T/
Disable CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE
Set CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE=N
[Where problems could occur]
[Other Info]
Additional info:
SUT is having 2*32C HBM cpus. Eligible system-ram mode change devices should
be only 2[dax0.0, dax1.0], but under "daxctl list -u" is showing 1st time 4
devices [dax0.0, 1.0, 2.0, 3.0], 2 is "state":"disabled" and 2 more devices is
"mode":"devdax" which are actuall devadax to system-ram convertible devices.
After reconfigure-device dax0.0, dax1.0 when you list the devices couple of
more dummy/dumplicate devices are creating with "state":"disabled"[Ex: dax4.0,
5.0 etc..].
root@ubuntu:/home/ubuntu# daxctl list -u
[
{
"chardev":"dax1.0",
"size":"64.00 GiB (68.72 GB)",
"target_node":3,
"align":2097152,
"mode":"devdax"---> HBM CPU 1, This we can cha
[Kernel-packages] [Bug 2029332] Re: Reboot command powers off the system
sudo apt-cache search linux-generic-hwe linux-generic-hwe-20.04 - Complete Generic Linux kernel and headers (dummy transitional package) linux-generic-hwe-20.04-edge - Complete Generic Linux kernel and headers (dummy transitional package) linux-generic-hwe-22.04 - Complete Generic Linux kernel and headers linux-generic-hwe-22.04-edge - Complete Generic Linux kernel and headers Try installing the latest 6.2 sudo apt install linux-generic-hwe-22.04-edge uname -a Linux 6.2.0-34-generic #34~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 7 13:12:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2029332 Title: Reboot command powers off the system Status in linux package in Ubuntu: Confirmed Status in linux-hwe-6.2 package in Ubuntu: Confirmed Status in linux-hwe-6.2 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Issue: When a reboot (or init 6) command is issued the server shuts down instead. Expected behaviour: To reboot and NOT shutdown Impacted HW: HPE DL 380 OR Synergy 480 Gen 10 Plus Server 2P core count greater than 16 (like 24,28 or 32) Impacted OS: Ubuntu 22.04.2 kernel higher than 15.17.15 When the CPU count is 1, issue is not observed. When core count is less than 24 (like 16) issue not observed. [Fix] Problem introduced in v5.18 with commit: 08f253ec3767 x86/cpu: Clear SME feature flag when not in use Fixes for the above:0 9b040453d444 x86/smp: Dont access non-existing CPUID leaf 1f5e7eb7868e x86/smp: Make stop_other_cpus() more robust [Test Case] $ sudo reboot Server should reboot and not power off. [Where Problems Could Occur] The fixes modify x86 stop-CPU code so reboot/poweroff of x86 machines could be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2029332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
I have created a test kernel can anyone provide feedback?
https://people.canonical.com/~mreed/misc/lp_1988711_lpfc_14_2_0_5/
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post
RSCN completion
6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in
Fabric topology
6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2 -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux source package in Lunar: In Progress Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
Hi Keng-Yu, Here is a test kernel for lunar. I had only included the source before and not the debs. Can you please test and verify the config_numa_emu option works and provides the performance boost. https://people.canonical.com/~mreed/hpe/lp_2008745_config_numa_emu/lunar/ ** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] + Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). + + * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html + ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html + + An improvement to performance on a Sapphire Rapids CPU with HBM should + be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar ** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] - Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). + Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_2_lunar ** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed885
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Gerry, This is in our currently SRU cycle. https://kernel.ubuntu.com/If everything goes smoothly then the target release date is June 5. However, that is not guaranteed. I would not notify any of your customers about the driver until it actually gets released. -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don, These patches are currently in the proposed kernel (linux: 5.15.0-74.81). Can you test them in the proposed kernel and verify they are working properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
This has been ack'ed by the kernel team and will need to be tested once it hits the proposed kernel. -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Ketan,
Currently the reverted patches have already been pulled into our master-
next kernel because they are apart of the upstream kernel. Cherry
picking the affected patches on top of those causes all types of issues.
We need a solution with those reverted patches in place. Can you
provide a revised list of commits that takes the reverted patches into
account?
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
10455
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Ketan,
Are you stating that I should not apply the Revert patches at all?
Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq"
Revert "scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4"
Revert "scsi: lpfc: SLI path split: Refactor SCSI paths"
Revert "scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup()"
Revert "scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()"
Revert "scsi: lpfc: Resolve some cleanup issues following SLI path refactoring"
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: R
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Ketan, I found that the following patches are currently in our tree and revert the patches listed below. Revert Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq" Revert "scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4" Revert "scsi: lpfc: SLI path split: Refactor SCSI paths" Revert "scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup()" Revert "scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()" Revert "scsi: lpfc: Resolve some cleanup issues following SLI path refactoring" Patches not needed: a680a9298e7b scsi: lpfc: SLI path split: Refactor lpfc_iocbq 1b64aa9eae28 scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4 3512ac094293 scsi: lpfc: SLI path split: Refactor SCSI paths c26bd6602e1d scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup() 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring Are there any other patches that have been reverted upstream that I need to know about? Most of the issues that I am seeing now are with iocb_cmpl being changed to cmd_cmpl. The "Revert" patches do the opposite and I doing the same. -- 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/1988711 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Fix Released Bug description: [IMPACT/Justification] There are numerous bug fixes included in the more recent version of lpfc That Broadcom has asked to pull into Jammy and Kinetic to better support customers in the field who are using the GA kernel and cant or wont move to the HWE kernels. These all are limited to the lpfc driver itself, no patches to core code are requested. [FIX] A few of these were already landed in Jammy, and all but 6 (ones landed in 6.0 upstream) were already in Kinetic. b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5 b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into lpfc_sli_prep_abort_xri() ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved configuration ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF WQE 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in queuecommand after VMID 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in XMIT_ELS_RSP64_CX iocb f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with malformed user input 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in lpfc_nvme_cancel_iocb() 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for aborted NVMe cmds 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after starget_to_rport() e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path refactoring 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path refactoring 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in lpfc_ct_reject_event() a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol independent ed913cf4a533 scsi: lpfc: Commonize VMID code location fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3 a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for NVMe I/O e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric parameters dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link() 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in rscn_recovery_check() 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event() ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths 84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() 775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE c2024e3b33
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
** Changed in: linux (Ubuntu Jammy) 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don, I have created a test kernel based on this branch https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 Test Kernel https://people.canonical.com/~mreed/misc/lp_1998643_smartpqi/ Can you please test it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Incomplete Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
** Description changed: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. - [Test Plan] - The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. + [Test Plan] + The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 + + [Other Info] + + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Incomplete Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: sma
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don,
I re-added this patch "(64fc9015fbeb scsi: smartpqi: Switch to attribute
groups)" as it fixed the issues with cherry picking. The need to verify
that I need to add this and remove the .attr suffix? This currently
builds and it is in the 5.19 kernel as is. I just need to verify that
I need to remove the .attr suffix?
static struct attribute *pqi_sdev_attrs[] = {
&dev_attr_lunid.attr,
&dev_attr_unique_id.attr,
&dev_attr_path_info.attr,
&dev_attr_sas_address.attr,
&dev_attr_ssd_smart_path_enabled.attr,
&dev_attr_raid_level.attr,
&dev_attr_raid_bypass_cnt.attr,
&dev_attr_sas_ncq_prio_enable.attr,
NULL
};
Second, this following line breaks the build.
+ .shost_groups = pqi_shost_groups,
I need to know if it is needed? or is there another patch that fixes it or can
I just remove it?
When I removed it, the build succeeded.
--
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/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Incomplete
Bug description:
[Impact]
These patches provide bug fixes and add support for the latest generation of
OEM PCI devices to ensure customers are able to use Jammy on the recent
generations of server hardware. This will bring us in line with the other major
linux distros.
[Fix]
There are some outstanding patches already in Linus's tree that can be
applied to 22.04.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
The following patches apply to
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
297bdc540f0e scsi: smartpqi: Close write read holes
dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
1d393227fc76 scsi: smartpqi: Add controller fw version to console log
4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
8946ea283808 scsi: smartpqi: Fix typo in comment
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
27655e9db479 scsi: smartpqi: Update volume size after expansion
b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
c57ee4ccb358 scsi: smartpqi: Add PCI IDs
c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
I added the above SHA1 IDs to a file called:
backport_linus_6.1_into_22.04
git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
git am -s /tmp/patches/*.diff
All patches applied without any conflicts.
[Test Plan]
The upstream driver has undergone extensive testing by Microchip's test team
before submitting those patches to the upstream kernel. All patches are tested
and accepted in the upstream kernel at this time.
One should be able to load the smartpqi driver and verify the version
is at 2.1.18-045
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions
--
Mailing list: h
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
** Description changed: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] Jammy - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1 Kinetic - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1 -- 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/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don,
Here are the changes I made to the second patch
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
drivers/scsi/smartpqi/smartpqi_init.c
@@ -7256,8 +7265,9 @@ static struct scsi_host_template pqi_driver_template = {
.slave_alloc = pqi_slave_alloc,
.slave_configure = pqi_slave_configure,
.map_queues = pqi_map_queues,
- .sdev_attrs = pqi_sdev_attrs,
- .shost_attrs = pqi_shost_attrs,
+ .sdev_groups = pqi_sdev_groups,
+ .shost_groups = pqi_shost_groups,
+ .cmd_size = sizeof(struct pqi_cmd_priv),
};
The issue here is that the added lines cause the build to break. If I didn't
add
+ .sdev_groups = pqi_sdev_groups,
+ .shost_groups = pqi_shost_groups,
and keep
- .sdev_attrs = pqi_sdev_attrs,
- .shost_attrs = pqi_shost_attrs,
My guess is that it will build. I haven't tried it yet but wanted some
guidance.
--
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/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Incomplete
Bug description:
[Impact]
These patches provide bug fixes and add support for the latest generation of
OEM PCI devices to ensure customers are able to use Jammy on the recent
generations of server hardware. This will bring us in line with the other major
linux distros.
[Fix]
There are some outstanding patches already in Linus's tree that can be
applied to 22.04.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
The following patches apply to
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
297bdc540f0e scsi: smartpqi: Close write read holes
dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
1d393227fc76 scsi: smartpqi: Add controller fw version to console log
4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
8946ea283808 scsi: smartpqi: Fix typo in comment
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
27655e9db479 scsi: smartpqi: Update volume size after expansion
b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
c57ee4ccb358 scsi: smartpqi: Add PCI IDs
c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
I added the above SHA1 IDs to a file called:
backport_linus_6.1_into_22.04
git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
git am -s /tmp/patches/*.diff
All patches applied without any conflicts.
[Test Plan]
The upstream driver has undergone extensive testing by Microchip's test team
before submitting those patches to the upstream kernel. All patches are tested
and accepted in the upstream kernel at this time.
One should be able to load the smartpqi driver and verify the version
is at 2.1.18-045
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions
--
Mailing list: https://la
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don,
Here are the changes I made to adjust/backport the first patch. Is this
correct?
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
drivers/scsi/smartpqi/smartpqi_init.c
@@ -7126,15 +7234,18 @@ static DEVICE_ATTR(sas_address, 0444,
pqi_sas_address_show, NULL);
static DEVICE_ATTR(ssd_smart_path_enabled, 0444,
pqi_ssd_smart_path_enabled_show, NULL);
static DEVICE_ATTR(raid_level, 0444, pqi_raid_level_show, NULL);
static DEVICE_ATTR(raid_bypass_cnt, 0444, pqi_raid_bypass_cnt_show, NULL);
-
-static struct device_attribute *pqi_sdev_attrs[] = {
- &dev_attr_lunid,
- &dev_attr_unique_id,
- &dev_attr_path_info,
- &dev_attr_sas_address,
- &dev_attr_ssd_smart_path_enabled,
- &dev_attr_raid_level,
- &dev_attr_raid_bypass_cnt,
+static DEVICE_ATTR(sas_ncq_prio_enable, 0644,
+ pqi_sas_ncq_prio_enable_show, pqi_sas_ncq_prio_enable_store);
+
+static struct attribute *pqi_sdev_attrs[] = {
+ &dev_attr_lunid.attr,
+ &dev_attr_unique_id.attr,
+ &dev_attr_path_info.attr,
+ &dev_attr_sas_address.attr,
+ &dev_attr_ssd_smart_path_enabled.attr,
+ &dev_attr_raid_level.attr,
+ &dev_attr_raid_bypass_cnt.attr,
+ &dev_attr_sas_ncq_prio_enable.attr,
NULL
};
--
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/1998643
Title:
smartpqi: Update 22.04 driver to include recent bug fixes and support
current generation devices
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
Incomplete
Bug description:
[Impact]
These patches provide bug fixes and add support for the latest generation of
OEM PCI devices to ensure customers are able to use Jammy on the recent
generations of server hardware. This will bring us in line with the other major
linux distros.
[Fix]
There are some outstanding patches already in Linus's tree that can be
applied to 22.04.
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
The following patches apply to
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045
e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year
6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter
2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs
cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints
6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition
69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests
85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures
2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers
44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i
331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang
904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices
297bdc540f0e scsi: smartpqi: Close write read holes
dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers
1d393227fc76 scsi: smartpqi: Add controller fw version to console log
4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal
8946ea283808 scsi: smartpqi: Fix typo in comment
c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer
31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang
62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035
291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses
c66e078ad89e scsi: smartpqi: Fix hibernate and suspend
5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements
c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init
00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives
5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads
27655e9db479 scsi: smartpqi: Update volume size after expansion
b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend
42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value
9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io()
b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code
94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer
70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot
2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs
c57ee4ccb358 scsi: smartpqi: Add PCI IDs
c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
I added the above SHA1 IDs to a file called:
backport_linus_6.1_into_22.04
git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04
git am -s /tmp/patches/*.diff
All patches applied without any conflicts.
[Test Plan]
The upstream driver has undergone extensive testing by Microchip's test team
bef
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hi Don, I have 2 patches that do not cherry-pick cleanly to the jammy kernel based on master-next tags. git describe --tags Ubuntu-5.15.0-72.79-43-gc85205fa6c05 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer -- 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/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Incomplete Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
Hi Keng-Yu, In comment #4, you mentioned there was an improvement in the performance on the Sapphire Rapids CPU with HBM, how exactly did you quantify that? -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic + + Lunar + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Hi Laurie,
This update is in the Kinetic (5.19) kernel. It has not made it into
Jammy 5.15 yet.
--
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
Fix Released
Bug description:
[IMPACT/Justification]
There are numerous bug fixes included in the more recent version of lpfc That
Broadcom has asked to pull into Jammy and Kinetic to better support customers
in the field who are using the GA kernel and cant or wont move to the HWE
kernels. These all are limited to the lpfc driver itself, no patches to core
code are requested.
[FIX]
A few of these were already landed in Jammy, and all but 6 (ones landed in
6.0 upstream) were already in Kinetic.
b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
lpfc_sli_prep_abort_xri()
ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
configuration
ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress test
2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue CMF
WQE
0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
queuecommand after VMID
35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
XMIT_ELS_RSP64_CX iocb
f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
malformed user input
4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
lpfc_nvme_cancel_iocb()
1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
nvme_admin_async_event cmd completion
ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
aborted NVMe cmds
336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT
topology
b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is
aborted
6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
starget_to_rport()
e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
refactoring
24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort path
refactoring
44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
lpfc_ct_reject_event()
a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
independent
ed913cf4a533 scsi: lpfc: Commonize VMID code location
fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros for
NVMe I/O
e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
parameters
dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
lpfc_err_lost_link()
4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
rscn_recovery_check()
596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event()
ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is inserted
b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
84c6f99e3907 scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
775266207105 scsi: lpfc: Correct BDE DMA address assignment for GEN_REQ_WQE
cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
92bd903da12b scsi: lpfc: Fix additional reference counting in
lpfc_bsg_rport_els()
db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
646db1a560f4 scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()
3d1d34ec1fbc scsi: lpfc: Remove unnecessary null ndlp check in
lpfc_sli_prep_wqe()
a346f28ad231 scsi: lpfc: Remove unneeded variable
66c20a97367a scsi: lpfc: Copyright updates for 14.2.0.2 patches
4af4d0e2ea94 scsi: lpfc: Update lpfc version to 14.2.0.2
fd4a0c6da5c1 scsi: lpfc: Expand setting ELS_ID field in ELS_REQUEST64_WQE
f4fbf4acaa50 scsi: lpfc: Update stat accounting for READ_STATUS mbox command
ef47575fd982 scsi: lpfc: Refactor cleanup of mailbox commands
d51cf5bd926c scsi: lpfc: Fix field overload in lpfc_iocbq data structure
1045592fc968 scsi: lpfc: Introduce FC_RSCN_MEMENTO flag for tracking post
RSCN completion
6c983d327b9e scsi: lpfc: Register for Application Services FC-4 type in
Fabric topology
6c8a3ce64b2c scsi: lpfc: Remove false FDMI NVMe FC-4 support for NPIV ports
c364c453d30a sc
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
I have created a test kernel for Kinetic https://people.canonical.com/~mreed/hpe/lp_2008745_config_numa_emu/kinetic/ ** Description changed: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some case, Intel's SPR-HBM needs this. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] + Jammy + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu + + Kinetic + + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Michael Reed (mreed8855) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Michael Reed (mreed8855) ** Description changed: [Impact] + Currently Ubuntu kernel has this kernel config disabled. - But in some case, Intel's SPR-HBM needs this. + But in some cases, Intel's Sapphire Rapids High Bandwith + Memory (SPR-HBM) needs this option. + + Memory bandwidth has been a bottleneck of increasingly memory bound + workloads. Sapphire Rapids plus HBM is specifically targeted to + cater to these workloads, traditionally served using overprovisioning + of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
I created, built and tested the patch for Kinetic. https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic -- 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/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
** Description changed: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] + Jammy + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc + Kinetic + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic -- 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/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
I have created built and tested a version for Kinetic. https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic ** Description changed: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] + Jammy + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt + Kinetic + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Medium Assignee: Michael Reed (mreed8855) Status: 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some case, Intel's SPR-HBM needs this. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Michael Reed (mreed8855) -- 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/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
This needs to be backported to 5.19 first before 5.15. I will generate a test kernel for kinetic. ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Low ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
This needs to be backported to 5.19 first before 5.15. I will generate a test kernel for kinetic ** Also affects: linux (Ubuntu Kinetic) 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/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: New Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
** Description changed: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] + Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] + Regression Risk is Low + [Other Info] - https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_1998544_hpwdt + + https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt -- 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/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
Dell has stated that this has been tested on systems with both AMD and Intel CPU's mproved boot up time in Performance Per Watt (DAPC) before/after boot times results, With PATCH # systemd-analyze Startup finished in 13.569s (kernel) + 9.136s (userspace) = 22.705s graphical.target reached after 8.460s in userspace # systemd-analyze Startup finished in 13.188s (kernel) + 8.504s (userspace) = 21.692s graphical.target reached after 8.123s in userspace # systemd-analyze Startup finished in 13.720s (kernel) + 9.235s (userspace) = 22.956s graphical.target reached after 8.807s in userspace # systemd-analyze Startup finished in 13.967s (kernel) + 8.896s (userspace) = 22.863s graphical.target reached after 8.489s in userspace WithOut PATCH # systemd-analyze Startup finished in 14.137s (kernel) + 14.879s (userspace) = 29.016s graphical.target reached after 14.460s in userspace # systemd-analyze Startup finished in 14.149s (kernel) + 12.344s (userspace) = 26.494s graphical.target reached after 11.900s in userspace # systemd-analyze Startup finished in 14.434s (kernel) + 13.047s (userspace) = 27.481s graphical.target reached after 12.602s in userspace # systemd-analyze Startup finished in 14.462s (kernel) + 12.908s (userspace) = 27.371s graphical.target reached after 12.481s in userspace -- 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/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
HPE has tested this and hasn't seen any issues. ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] [Where Problems Could Occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_1998544_hpwdt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008037] Re: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
There appears to be a patch set that fixes this issue but I do not think it has been accepted upstream yet. https://lore.kernel.org/lkml/167429456532.4906.14087166098724750776.tip- bot2@tip-bot2/T/ If you search for "SPR MCC" the explanation for this issue is under the 3rd occurrence. Mao, if you are able to apply these patches can you check to see if it fixes the issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008037] Re: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
Partial Dmesg log Jan 4 07:49:51 proven-gnu kernel: [4.202465] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Jan 4 07:49:51 proven-gnu kernel: [4.202474] Modules linked in: Jan 4 07:49:51 proven-gnu kernel: [4.202478] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-56-generic #62-Ubuntu Jan 4 07:49:51 proven-gnu kernel: [4.202482] Hardware name: Dell Inc. PowerEdge T560/0PWDKY, BIOS 0.2.13 12/09/2022 Jan 4 07:49:51 proven-gnu kernel: [4.202485] RIP: 0010:uncore_insert_box_info+0x134/0x350 Jan 4 07:49:51 proven-gnu kernel: [4.202488] Code: c2 01 48 83 c0 04 39 d1 0f 8e c6 01 00 00 49 8b 4c 24 38 8b 0c 01 41 89 0c 07 49 8b 74 24 40 8b 34 06 41 89 34 06 39 f9 75 cf <0f> 0b 4c 89 ff e8 52 86 32 00 4c 89 f7 e8 4a 86 32 00 5b 41 5c 41 Jan 4 07:49:51 proven-gnu kernel: [4.202494] RSP: :ff58c947c01efc98 EFLAGS: 00010246 Jan 4 07:49:51 proven-gnu kernel: [4.202498] RAX: 0008 RBX: RCX: 0003 Jan 4 07:49:51 proven-gnu kernel: [4.202500] RDX: 0002 RSI: 00018000 RDI: 0003 Jan 4 07:49:51 proven-gnu kernel: [4.202503] RBP: ff58c947c01efcc0 R08: 0010 R09: ff356d890b9282f0 Jan 4 07:49:51 proven-gnu kernel: [4.202505] R10: ff356d988a2e2000 R11: e000 R12: ff356d9889edc6c0 Jan 4 07:49:51 proven-gnu kernel: [4.202507] R13: ff58c947c01efcf8 R14: ff356d890b928db0 R15: ff356d890b9282f0 Jan 4 07:49:51 proven-gnu kernel: [4.202510] FS: () GS:ff356d983fa0() knlGS: Jan 4 07:49:51 proven-gnu kernel: [4.202513] CS: 0010 DS: ES: CR0: 80050033 Jan 4 07:49:51 proven-gnu kernel: [4.202515] CR2: CR3: 0010be610001 CR4: 00771ee0 Jan 4 07:49:51 proven-gnu kernel: [4.202518] DR0: DR1: DR2: Jan 4 07:49:51 proven-gnu kernel: [4.202520] DR3: DR6: fffe07f0 DR7: 0400 Jan 4 07:49:51 proven-gnu kernel: [4.202522] PKRU: 5554 Jan 4 07:49:51 proven-gnu kernel: [4.202524] Call Trace: Jan 4 07:49:51 proven-gnu kernel: [4.202526] Jan 4 07:49:51 proven-gnu kernel: [4.202530] parse_discovery_table.isra.0+0x162/0x1a0 Jan 4 07:49:51 proven-gnu kernel: [4.202534] intel_uncore_has_discovery_tables+0x19e/0x270 Jan 4 07:49:51 proven-gnu kernel: [4.202538] ? type_pmu_register+0x16/0x42 Jan 4 07:49:51 proven-gnu kernel: [4.202545] intel_uncore_init+0xe3/0x226 Jan 4 07:49:51 proven-gnu kernel: [4.202549] ? type_pmu_register+0x42/0x42 Jan 4 07:49:51 proven-gnu kernel: [4.202553] do_one_initcall+0x46/0x1e0 Jan 4 07:49:51 proven-gnu kernel: [4.202559] do_initcalls+0x12f/0x159 Jan 4 07:49:51 proven-gnu kernel: [4.202564] kernel_init_freeable+0x162/0x1b5 Jan 4 07:49:51 proven-gnu kernel: [4.202568] ? rest_init+0x100/0x100 Jan 4 07:49:51 proven-gnu kernel: [4.202575] kernel_init+0x1b/0x150 Jan 4 07:49:51 proven-gnu kernel: [4.202578] ? rest_init+0x100/0x100 Jan 4 07:49:51 proven-gnu kernel: [4.202581] ret_from_fork+0x1f/0x30 Jan 4 07:49:51 proven-gnu kernel: [4.202586] Jan 4 07:49:51 proven-gnu kernel: [4.202588] ---[ end trace 8ed67df079f38d94 ]--- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008037] Re: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350
I opened a similar issue that I will close because this is a kernel issue. https://github.com/canonical/checkbox/issues/312 The following kernel warning causes this warning: WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 The kernel warning message is triggered when SPR MCC is used. ** Bug watch added: github.com/canonical/checkbox/issues #312 https://github.com/canonical/checkbox/issues/312 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2008037 Title: kernel warning of uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Status in linux-hwe-5.15 package in Ubuntu: New Bug description: Kernel taitned 512 ude to warning of below: #grep taint /var/log/syslog -b2 235407-Feb 20 15:27:14 xfusion kernel: [3.779483] WARNING: CPU: 64 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 235561-Feb 20 15:27:14 xfusion kernel: [3.779495] Modules linked in: 235627:Feb 20 15:27:14 xfusion kernel: [3.779499] CPU: 64 PID: 1 Comm: swapper/0 Not tainted 5.15.0-60-generic #66-Ubuntu 235746-Feb 20 15:27:14 xfusion kernel: [3.779505] Hardware name: XFUSION 2288 V7/BC15MBSC, BIOS 2.00.20.Btg 02/08/2023 235862-Feb 20 15:27:14 xfusion kernel: [3.779509] RIP: 0010:uncore_insert_box_info+0x134/0x350 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/2008037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
