[Kernel-packages] [Bug 2060437] Re: The module ib_ipoib does not load automatically on ubuntu server 24.04
I suspect it's not necessarily related to the card model, but just in case that is relevant, could you provide the model of the mellanox card you're using? -- 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/2060437 Title: The module ib_ipoib does not load automatically on ubuntu server 24.04 Status in linux package in Ubuntu: New Bug description: 1. Fresh install Ubuntu server 24.04 on a server with mellanox card and infiniband mode 2. As the module "ib_ipoib" does not load automatically, it fail to display the port via the command "ip a". The port can display after load manually. Please help to fix it, thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060437/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta
Is this still happening with the latest images? -- 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/2061373 Title: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta Status in linux package in Ubuntu: New Bug description: 1.The Version of product # lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 2.The version of package root@t:/tmp# apt-cache policy linux-image-6.8.0-22-generic linux-image-6.8.0-22-generic: Installed: 6.8.0-22.22 Candidate: 6.8.0-22.22 Version table: *** 6.8.0-22.22 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status 3.Expected to happen Print kernel output information after the server's POST screen disappears 4.Actual happend Print kernel output information before the server's POST screen disappears Please refer to the attached screenshot for details ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 07:46 seq crw-rw 1 root audio 116, 33 Apr 15 07:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 15 08:26:52 2024 InstallationDate: Installed on 2024-04-15 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Lenovo ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=77cf1cbe-6d2e-4dec-9439-c7aa2a69b5d9 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2023 dmi.bios.release: 3.10 dmi.bios.vendor: Lenovo dmi.bios.version: ESE121R-3.10 dmi.board.asset.tag: None dmi.board.name: STA7B05327 dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: None dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.ec.firmware.release: 3.90 dmi.modalias: dmi:bvnLenovo:bvrESE121R-3.10:bd11/15/2023:br3.10:efr3.90:svnLenovo:pnThinkSystemSR650V3MB,EGS,DDR5,SH,2U:pvr05:rvnLenovo:rnSTA7B05327:rvr05:cvnLenovo:ct23:cvrNone:sku7D75CTO0WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U dmi.product.sku: 7D75CTO0WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"
** Also affects: subiquity (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/2060924 Title: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)" Status in linux package in Ubuntu: New Status in subiquity package in Ubuntu: New Bug description: Description: When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk and boot up to OS, the OS can not detect the remote iscsi disk either. Reproduce Steps: 1. Install Ubunut 24.04 2. Boot into OS 3. perform command lsblk check remote disk, there isn't one appeared. Configuration: System: Lenovo SR655V3 OS:noble-live-server-amd64-0401.iso BMC Version ：2.30 (Build ID: KAX321V) UEFI Version:3.10 (Build ID: KAE115K) CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8 NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet Adapte storage：Lenovo D7000 or Lenovo V7000 Expected results: OS can recognize the remote iscsi disk Actual results: OS cannot recognize the remote iscsi disk. Additional info: 1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)
Closing, this is an old bug and this support likely landed long ago. ** Changed in: dellserver Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => 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/1772434 Title: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches) Status in dellserver: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: The purpose of this bug is to track the patches needed to enable the IT (HBA) driver into 18.04. Below are upstream commit ids of IT driver which went in over the in- box driver of Ubuntu18.04 OS’s base kernel, 864449eea7c600596e305ffdc4a6a846414b222c scsi: mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM 6f9e09fd6488de7661ee20efb5d8ab4e05a59735 scsi: mpt3sas: clarify mmio pointer types 40114bde9773ccaf9ad77233ac2cc9039f0f2941 scsi: mpt3sas: Do not use 32-bit atomic request descriptor for Ventura controllers. b4472d7180894c96b6133ef5ff3df50836591eaa scsi: mpt3sas: Introduce function to clone mpi reply. e5747439366c1079257083f231f5dd9a84bf0fd7 scsi: mpt3sas: Introduce function to clone mpi request. 182ac784b41faee02e8b44cd7149575258ad6858 scsi: mpt3sas: Introduce Base function for cloning. 22ae5a3c2599381cf7aaa5aca25c515a3166adcc scsi: mpt3sas: Introduce API to get BAR0 mapped buffer address 0448f0195124e33f11d15b7d1e1cab959989eee7 scsi: mpt3sas: Configure reply post queue depth, DMA and sgl tablesize. c520691b38cde1d94f53e5782feba892f5645043 scsi: mpt3sas: Add PCI device ID for Andromeda. 4a8842de8db4953fdda7866626b78b12fb8adb97 scsi: mpt3sas: fix an out of bound write 61dfb8a5fb7e93e692856026fa4c778a27f28984 scsi: mpt3sas: make function _get_st_from_smid static dbec4c9040edc15442c3ebdb65408aa9d3b82c24 scsi: mpt3sas: lockless command submission 272e253c7bcabfeef5f4d0aaed94a413e13e520f scsi: mpt3sas: simplify _wait_for_commands_to_complete() 6da999fe5a9285c2a78f3cf1e768abcd48d7607e scsi: mpt3sas: simplify mpt3sas_scsi_issue_tm() 74fcfa5371b7a681e864d3a9d3b9ecfd5737d8ea scsi: mpt3sas: simplify task management functions b0cd285eb57cd3cb18d882565c22d39bccffe7f0 scsi: mpt3sas: always use first reserved smid for ioctl passthrough 9961c9bbf2b43acaaf030a0fbabc9954d937ad8c scsi: mpt3sas: check command status before attempting abort 12e7c6782bc58128392b768fc2a87b230414a2a5 scsi: mpt3sas: Introduce mpt3sas_get_st_from_smid() 02a386df3678275b01eec71fee39735c379e4a2a scsi: mpt3sas: open-code _scsih_scsi_lookup_get() 6a2d4618aef3d4ffb83514e5e58a091d61e54a03 scsi: mpt3sas: separate out _base_recovery_check() 05303dfb738066ad597d7feb422ff9fa2d3d8ef3 scsi: mpt3sas: use list_splice_init() ba4494d47bd02e5757b449a2ccfa3ff87bc8 scsi: mpt3sas: set default value for cb_idx f49d4aed1315a7b766d855f1367142e682b0cc87 scsi: mpt3sas: Proper handling of set/clear of "ATA command pending" flag. 45b7aef7fb7d5f5bfa3a2a6727f1accf7660f6fd scsi: mpt3sas: Remove unused variable requeue_event To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1772434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Marking Fix Committed as these are all in our 6.8 tree and will land in 24.04, there's nothing more to do here but track it for release. linux-image-generic | 6.8.0-11.11 | noble-proposed | amd64, arm64, ppc64el, s390x ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Michael Reed (mreed8855) ** Also affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Michael Reed (mreed8855) Status: 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/2046726 Title: [24.04 LTS]: megaraid_sas driver update Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Committed 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 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Tags removed: verification-needed-jammy-linux-hwe-6.5 verification-needed-mantic-linux ** Tags added: verification-done-jammy-linux-hwe-6.5 verification-done-mantic-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 Committed Status in linux source package in Noble: Confirmed 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 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
This is for 24.04 and there is no test kernel yet. This one we can start working on this week now that the 24.04 kernel tree has been updated to 6.8. -- 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: Confirmed Status in linux source package in Noble: Confirmed 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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
If those patches are all in 6.7 mainline, then yes, they are already included for 24.04. There is a 6.7 kernel in noble-proposed for 24.04 that could technically be installed now. And thanks for the new bug. We added that to the stuff to work on this next cycle (The next two weeks) -- 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 2046722] Re: [22.04.04]: megaraid_sas: Critical Bug Fixes
We will work on these this next week and shoot for the next SRU for 6.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/2046722 Title: [22.04.04]: megaraid_sas: 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: 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. 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
Additionally, this says 24.04... is that the correct target? Your email to me says otherwise. -- 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 2046726] Re: [24.04 LTS]: megaraid_sas driver update
24.04 only recently rolled the kernel tree to 6.7, and we are planning on 6.8. Where are these upstream currently? If they are in 6.8 there is nothing to do here until we roll the kernel tree to 6.8 later this cycle. Can you tell me which mainline version these exist in currently? -- 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 2033416] Re: [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
** Summary changed: - change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y + [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Description changed: - Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro - kernels. + [Impact] + Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels. However, unlike plug and play devices, there is no way to load uncore module when user tries to use uncore event. Also, a primary motivation to add module support in uncore driver was to ease development (https://git.kernel.org/torvalds/c/05485745ad482). - So, ask ubuntu to switch to CONFIG_PERF_EVENTS_AMD_UNCORE=y. + Its not immediately apparent from perf tool output that the "amd-uncore" + module is not loaded when opening "amd_df" or "amd_l3" events fail or + when they do not show up in "perf list" despite using a compatible + kernel. Since the primary motivation of the commit [1] that made it + possible for this to be loaded as a module was to make development + easier, CONFIG_PERF_EVENTS_AMD_UNCORE defaults to 'y' [2]. + + [1] https://git.kernel.org/torvalds/c/05485745ad482 + [2] https://github.com/torvalds/linux/blob/master/arch/x86/events/Kconfig#L40 + + [Fix] + + Change kernel config to CONFIG_PERF_EVENTS_AMD_UNCORE=y + + [Test case] + + (How can this change be tested/verified?) + + [Where problems may occur] + + (What side effects or regressions could this change create?) -- 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/2033416 Title: [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: [Impact] Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels. However, unlike plug and play devices, there is no way to load uncore module when user tries to use uncore event. Also, a primary motivation to add module support in uncore driver was to ease development (https://git.kernel.org/torvalds/c/05485745ad482). Its not immediately apparent from perf tool output that the "amd- uncore" module is not loaded when opening "amd_df" or "amd_l3" events fail or when they do not show up in "perf list" despite using a compatible kernel. Since the primary motivation of the commit [1] that made it possible for this to be loaded as a module was to make development easier, CONFIG_PERF_EVENTS_AMD_UNCORE defaults to 'y' [2]. [1] https://git.kernel.org/torvalds/c/05485745ad482 [2] https://github.com/torvalds/linux/blob/master/arch/x86/events/Kconfig#L40 [Fix] Change kernel config to CONFIG_PERF_EVENTS_AMD_UNCORE=y [Test case] (How can this change be tested/verified?) [Where problems may occur] (What side effects or regressions could this change create?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
Still no update, it's apparently a very low priority to be looked at. -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in linux package in Ubuntu: Confirmed Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045796] Re: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters
https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958/2 Once we have a 6.8 kernel available for Noble, test that and then we can just close this. -- 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/2045796 Title: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Confirmed Bug description: [IMPACT] This is requested by one of our larger server hardware partners and Broadcom to to update the bnxt_en network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic. The goal is to have these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and pick cleanly with the exception of the two noted at the end of this section. For Mantic all are picked. For Noble, only the subset currently in linux-next will be picked, depending on what happens in our Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices
[Kernel-packages] [Bug 2046270] Re: Add Support for Broadcom 5760X RoCE adapters to 24.04 (patches in 6.8)
https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- the-24-04-noble-numbat-release/41958/2 Once we have a 6.8 kernel available for Noble, test that and then we can just close this. -- 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/2046270 Title: Add Support for Broadcom 5760X RoCE adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: Confirmed Bug description: This request is to add support for the patches for the Broadcom RoCE driver included in v6.8 to 24.04. The thread where these were posted is here: https://lore.kernel.org/all/1701946060-13931-1-git-send-email- selvin.xav...@broadcom.com/ These are the commits from linux-rdma: 07f830ae4913 RDMA/bnxt_re: Adds MSN table capability for Gen P7 adapters cdae3936b2fe RDMA/bnxt_re: Doorbell changes 6027c20dad1a RDMA/bnxt_re: Get the toggle bits from CQ completions 880a5dd1880a RDMA/bnxt_re: Update the HW interface definitions a62d68581441 RDMA/bnxt_re: Update the BAR offsets 1801d87b3598 RDMA/bnxt_re: Support new 5760X P7 devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046270] Re: Add Support for Broadcom 5760X RoCE adapters to 24.04 (patches in 6.8)
For now, no. I can't do anything anyway until we've finally rolled to 6.7 which hasn't happened yet. So once that happens I have this and one other patch pull queued up. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046270 Title: Add Support for Broadcom 5760X RoCE adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: Confirmed Bug description: This request is to add support for the patches for the Broadcom RoCE driver included in v6.8 to 24.04. The thread where these were posted is here: https://lore.kernel.org/all/1701946060-13931-1-git-send-email- selvin.xav...@broadcom.com/ These are the commits from linux-rdma: 07f830ae4913 RDMA/bnxt_re: Adds MSN table capability for Gen P7 adapters cdae3936b2fe RDMA/bnxt_re: Doorbell changes 6027c20dad1a RDMA/bnxt_re: Get the toggle bits from CQ completions 880a5dd1880a RDMA/bnxt_re: Update the HW interface definitions a62d68581441 RDMA/bnxt_re: Update the BAR offsets 1801d87b3598 RDMA/bnxt_re: Support new 5760X P7 devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
Hi... could you provide a patch to backport 65248a9a9ee1 perf/x86/uncore: Add a quirk for UPI on SPR To 5.15? I started and it became a bit of a rabbit hole trying to figure out the prerequisite patches for that one which has merge conflicts when trying to cherry pick it. ** Changed in: intel Assignee: Jeff Lane (bladernr) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Jeff Lane (bladernr) => (unassigned) ** Changed in: linux (Ubuntu Jammy) Assignee: Jeff Lane (bladernr) => (unassigned) ** Changed in: intel Status: In Progress => Confirmed ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) -- 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Jeff Lane (bladernr) ** 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Changed in: intel Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: intel Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: intel Status: New => In Progress ** Changed in: linux (Ubuntu) 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: In Progress Status in linux package in Ubuntu: In Progress Bug description: [Impact] On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] ke
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Description changed: - 5.15 Kernel Warnings with some Sapphire Rapids CPUs - - On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: + [Impact] + On some Sapphire Rapids CPUs we are seeing Kernel warnings in the kern.log: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.770054] ret_from_fork+0x1f/0x30 Oct 31 03:35:55 N8 kernel: [ 95.812906] Oct 31 03:35:55 N8 kernel: [ 95.839108] ---[ end trace 2d0c57130f45fd62 ]--- https://certification.canonical.com/hardware/202305-31570/submission/312593/ Intel(R) Xeon(R) Gold 6426Y Apr 14 17:29:28 ML110Gen11 kernel: [2.135184]
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
Found this commit in mainline and our 6.5 HWE kernel. Checking now to see if there are any prerequisites as well. commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 Author: Kan Liang Date: Thu Jan 12 12:01:05 2023 -0800 perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table -- 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: New Status in linux package in Ubuntu: New Bug description: 5.15 Kernel Warnings with some Sapphire Rapids CPUs On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55
[Kernel-packages] [Bug 2049637] Re: Some SPR systems throw kernel warnings from uncore_discovery.c
** Also affects: intel 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/2049637 Title: Some SPR systems throw kernel warnings from uncore_discovery.c Status in intel: New Status in linux package in Ubuntu: New Bug description: 5.15 Kernel Warnings with some Sapphire Rapids CPUs On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.770054] ret_from_fork+0x1f/0x30 Oct 31 03:35:55 N8 kernel: [
[Kernel-packages] [Bug 2049637] [NEW] Some SPR systems throw kernel warnings from uncore_discovery.c
Public bug reported: 5.15 Kernel Warnings with some Sapphire Rapids CPUs On some Sapphire Rapids CPUs we are seeing Kernel warnings in the syslog: https://certification.canonical.com/hardware/202311-32288/submission/341156/ Intel(R) Xeon(R) Gold 6442Y Oct 31 03:35:55 N8 kernel: [ 92.770372] [ cut here ] Oct 31 03:35:55 N8 kernel: [ 92.825738] WARNING: CPU: 48 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 92.953850] Modules linked in: Oct 31 03:35:55 N8 kernel: [ 92.990464] CPU: 48 PID: 1 Comm: swapper/0 Not tainted 5.15.0-88-generic #98-Ubuntu Oct 31 03:35:55 N8 kernel: [ 93.082179] Hardware name: ASUSTeK COMPUTER INC. ESC N8-E11/Z13PN-D32 Series, BIOS 0402 09/08/2023 Oct 31 03:35:55 N8 kernel: [ 93.189501] RIP: 0010:uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 93.206419] Freeing initrd memory: 106936K Oct 31 03:35:55 N8 kernel: [ 93.253138] 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 b2 07 33 00 4c 89 f7 e8 aa 07 33 00 5b 41 5c 41 Oct 31 03:35:55 N8 kernel: [ 93.527071] RSP: :ff5c25ed800efc98 EFLAGS: 00010246 Oct 31 03:35:55 N8 kernel: [ 93.589669] RAX: 0008 RBX: RCX: 0003 Oct 31 03:35:55 N8 kernel: [ 93.675160] RDX: 0002 RSI: 00018000 RDI: 0003 Oct 31 03:35:55 N8 kernel: [ 93.760654] RBP: ff5c25ed800efcc0 R08: 0010 R09: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 93.846130] R10: 0246 R11: R12: ff32ac8a8b8412a0 Oct 31 03:35:55 N8 kernel: [ 93.931613] R13: ff5c25ed800efcf8 R14: ff32ac8a8aa32cb0 R15: ff32ac8a801df260 Oct 31 03:35:55 N8 kernel: [ 94.017099] FS: () GS:ff32ac99bfa0() knlGS: Oct 31 03:35:55 N8 kernel: [ 94.114042] CS: 0010 DS: ES: CR0: 80050033 Oct 31 03:35:55 N8 kernel: [ 94.182871] CR2: CR3: 000d07e10001 CR4: 00771ee0 Oct 31 03:35:55 N8 kernel: [ 94.268360] DR0: DR1: DR2: Oct 31 03:35:55 N8 kernel: [ 94.353828] DR3: DR6: fffe07f0 DR7: 0400 Oct 31 03:35:55 N8 kernel: [ 94.439332] PKRU: 5554 Oct 31 03:35:55 N8 kernel: [ 94.471788] Call Trace: Oct 31 03:35:55 N8 kernel: [ 94.501100] Oct 31 03:35:55 N8 kernel: [ 94.526275] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.578457] ? show_trace_log_lvl+0x1d6/0x2ea Oct 31 03:35:55 N8 kernel: [ 94.630686] ? parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 kernel: [ 94.693295] ? show_regs.part.0+0x23/0x29 Oct 31 03:35:55 N8 kernel: [ 94.741331] ? show_regs.cold+0x8/0xd Oct 31 03:35:55 N8 kernel: [ 94.785212] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.841591] ? __warn+0x8c/0x100 Oct 31 03:35:55 N8 kernel: [ 94.880281] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 94.936636] ? report_bug+0xa4/0xd0 Oct 31 03:35:55 N8 kernel: [ 94.978460] ? handle_bug+0x39/0x90 Oct 31 03:35:55 N8 kernel: [ 95.020246] ? exc_invalid_op+0x19/0x70 Oct 31 03:35:55 N8 kernel: [ 95.066232] ? asm_exc_invalid_op+0x1b/0x20 Oct 31 03:35:55 N8 kernel: [ 95.116341] ? uncore_insert_box_info+0x134/0x350 Oct 31 03:35:55 N8 kernel: [ 95.172708] ? uncore_insert_box_info+0xe3/0x350 Oct 31 03:35:55 N8 kernel: [ 95.228032] parse_discovery_table.isra.0+0x162/0x1a0 Oct 31 03:35:55 N8 cloud-init[1992]: |.+.o .o .o o +| Oct 31 03:35:55 N8 kernel: [ 95.288570] intel_uncore_has_discovery_tables+0x19e/0x270 Oct 31 03:35:55 N8 kernel: [ 95.354298] ? type_pmu_register+0x2f/0x42 Oct 31 03:35:55 N8 kernel: [ 95.403385] intel_uncore_init+0xe3/0x226 Oct 31 03:35:55 N8 kernel: [ 95.451409] ? type_pmu_register+0x42/0x42 Oct 31 03:35:55 N8 kernel: [ 95.500506] do_one_initcall+0x46/0x1e0 Oct 31 03:35:55 N8 kernel: [ 95.546475] do_initcalls+0x12f/0x159 Oct 31 03:35:55 N8 kernel: [ 95.590372] kernel_init_freeable+0x162/0x1b5 Oct 31 03:35:55 N8 kernel: [ 95.642556] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.685405] kernel_init+0x1b/0x150 Oct 31 03:35:55 N8 kernel: [ 95.727228] ? rest_init+0x100/0x100 Oct 31 03:35:55 N8 kernel: [ 95.770054] ret_from_fork+0x1f/0x30 Oct 31 03:35:55 N8 kernel: [ 95.812906] Oct 31 03:35:55 N8 kernel: [ 95.839108] ---[ end trace 2d0c57130f45fd62 ]--- https://certification.canonical.com/hardware/202305-31570/submission/312593/ Intel(R) Xeon(R) Gold 6426Y Apr 14 17:29:28 ML110Gen11 kernel: [2.135184] [ cut here ] Apr 14 17:29:28 ML110Gen11 kernel: [2.135185] WARNING: CPU: 0 PID: 1 at arch/x86/events/intel/uncore_discovery.c:184 uncore_insert_box_info+0x134/0x350 Apr 14 17:29:28 ML110Gen11
[Kernel-packages] [Bug 2045796] Re: Update bnxt with bug fixes and support for Broadcom 5760X network adapters
PR made for 6.5. 6.7 will have to wait until the Noble tree is merged with 6.7 mainline. -- 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/2045796 Title: Update bnxt with bug fixes and support for Broadcom 5760X network adapters Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Confirmed Bug description: [IMPACT] This is requested by one of our larger server hardware partners and the upstream (Broadcom) to update the bnxt network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic with the goal of having these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and pick cleanly with the exception of the two noted at the end of this section. For Mantic all are picked. For Noble, only the subset currently in linux-next will be picked, depending on what happens in our Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN"
[Kernel-packages] [Bug 2045796] Re: Update bnxt with bug fixes and support for Broadcom 5760X network adapters
** Description changed: [IMPACT] This is requested by one of our larger server hardware partners and the upstream (Broadcom) to update the bnxt network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic with the goal of having these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] - These are all in mainline and pick cleanly with the exception of the two - noted at the end of this section. + These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and + pick cleanly with the exception of the two noted at the end of this + section. For Mantic all are picked. For Noble, only the subset + currently in linux-next will be picked, depending on what happens in our + Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN" cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs e76d44fe7227 bnxt_en: Support QOS and TPID settings for the SRIOV VLAN a19b4801457b bnxt_en: Event handler for Thermal event 3d9cf962067b bnxt_en: Use non-standard attribute to expose shutdown temperature cd13244f19eb bnxt_en: Expose threshold temperatures through hwmon 847da8b1178c bnxt_en: Modify the
[Kernel-packages] [Bug 2045796] Re: Update bnxt with bug fixes and support for Broadcom 5760X network adapters
** Description changed: - These patches are needed on top of v6.7 to support Broadcom 5760X - Adapters. These patches currently reside in the net-next tree and will - be included in v6.8. + [IMPACT] - Prerequisite commits in net-next today: + This is requested by one of our larger server hardware partners and the + upstream (Broadcom) to update the bnxt network driver code to add some + bug fixes and support for the newer 5760X adapters into Mantic with the + goal of having these land in 22.04.4 HWE and the installer environment + via the HWE kernel. + Missing these patches will mean customers running this hardware will not + be able to use it with Ubuntu Server 22.04 LTS until the much later + 22.04.5 point release, setting up a months-long gap in support for these + adapters. + + [FIXES] + + These are all in mainline and pick cleanly with the exception of the two + noted at the end of this section. + + d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc + 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs + 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new + firmware interface + 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields + 30c0bb63c2ea bnxt_en: Support new firmware link parameters + cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic + a7445d69809f bnxt_en: Add support for new RX and TPA_START completion + types for P7 + 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). + c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. + 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions + 8243345bfaec bnxt_en: Refactor RSS capability fields + d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism + on P7 chips + d3c16475dc06 bnxt_en: Consolidate DB offset calculation + a432a45bdba4 bnxt_en: Define basic P7 macros + 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 + 08b386b132c6 bnxt_en: Fix backing store V2 logic + 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips + f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips + c09d22674b94 bnxt_en: Modify RX ring indexing logic. + 6d1add95536b bnxt_en: Modify TX ring indexing logic. + b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. + 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 + firmware calls + 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API + b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function + 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct + 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type + 76087d997a84 bnxt_en: Restructure context memory data structures + e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() + aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always + free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings - f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings + f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings + required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field + 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters + 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes + 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API + 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic + 94c89e73d377 bnxt_en: refactor speed independent ethtool modes + d6263677bb1b bnxt_en: support lane configuration via ethtool + ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode + fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event + 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI + 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices + c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN" + cbdbf0aa41ba bnxt_en: Update VNIC resource calculation for VFs + e76d44fe7227 bnxt_en: Support QOS and TPID settings for the SRIOV VLAN + a19b4801457b bnxt_en: Event handler for Thermal event + 3d9cf962067b bnxt_en: Use non-standard attribute to expose shutdown temperature + cd13244f19eb bnxt_en: Expose threshold temperatures through hwmon + 847da8b1178c bnxt_en: Modify the driver to use
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters and some bug fixes.
** Summary changed: - Add Support for Broadcom 5760X Network Controllers + Add Support for Broadcom 5760X Network adapters and some bug fixes. ** Summary changed: - Add Support for Broadcom 5760X Network adapters and some bug fixes. + Add Support for Broadcom 5760X Network adapters and some bug fixes ** Summary changed: - Add Support for Broadcom 5760X Network adapters and some bug fixes + Update bnxt with bug fixes and support for Broadcom 5760X network adapters -- 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/2045796 Title: Update bnxt with bug fixes and support for Broadcom 5760X network adapters Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: In Progress Status in linux source package in Noble: Confirmed Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)
** 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/2045796 Title: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: New Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
If you get a patch to fix the warning upstream we can pull it later once it's accepted. On Thu, Dec 14, 2023 at 3:25 AM Chandrakanth Patil < 2045...@bugs.launchpad.net> wrote: > ok, Jeff. Regarding warning: > > 1. Since there is no functional impact, we can ignore it as of now. > 2. We will submit the warning fix to upstream ASAP. > > > Do you have any suggestions on this? > > -- > You received this bug notification because you are subscribed to the bug > report. > 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: > Confirmed > Status in linux source package in Noble: > Confirmed > > 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 > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=Confirmed; importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=Opinion; importance=Wishlist; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=mantic; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=noble; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: bladernr cpatubuntu > Launchpad-Bug-Reporter: Chandrakanth Pati
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8)
** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Jeff Lane (bladernr) ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Mantic) 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/2045796 Title: Add Support for Broadcom 5760X Network adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: New Status in linux source package in Mantic: In Progress Status in linux source package in Noble: New Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
Bug: distribution=ubuntu; distroseries=mantic; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=noble; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: bladernr cpatubuntu > Launchpad-Bug-Reporter: Chandrakanth Patil (cpatubuntu) > Launchpad-Bug-Modifier: Chandrakanth Patil (cpatubuntu) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr > > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- 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: Confirmed Status in linux source package in Noble: Confirmed 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
** Description changed: [Impact] - This BZ has been initiated to incorporate the mpi3mr driver from + 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. + 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 -- 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: Confirmed Status in linux source package in Noble: Confirmed 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:
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Description changed: - This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu - releases (Ubuntu 22.04.x point releases). Below are the commit IDs for the latest upstream version (v6.8). + [Impact] + + This BZ 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. + 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 - 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:
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
These patches are all in Ubuntu from 5.19 to 6.5. I've moved them to this comment and out of the original summary to tidy that up. These are in log order. 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 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 a4e1d0b76e7b block: Change the return type of blk_mq_map_queues() into void --> This patch includes additional kernel changes as well. 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 2dd6532e9591 blk-mq: Drop 'reserved' arg of busy_tag_iter_fn --> This patch
[Kernel-packages] [Bug 2045233] Re: [SRU][22.04.04]: mpi3mr driver update
** Summary changed: - [Ubuntu 22.04.04]: mpi3mr driver update request + [SRU][22.04.04]: mpi3mr driver 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/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: Confirmed Status in linux source package in Noble: Confirmed Bug description: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 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
Re: [Kernel-packages] [Bug 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
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 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 > a4e1d0b76e7b block: Change the return type of blk_mq_map_queues() into > void--> This patch includes additional kernel changes as well. > 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 > 2dd6532e9591 blk-mq: Drop 'reserved' arg of busy_tag_iter_fn >--> This patch includes additional kernel changes as well. > 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 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=Confirmed; importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=Opinion; importance=Wishlist; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=mantic; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=noble; > sourcepackage=linux; component=main; status=Confirmed; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: bladernr cpatubuntu > Launchpad-Bug-Reporter: Chandrakanth Patil (cpatubuntu) > Launchpad-Bug-Modifier: Chandrakanth Patil (cpatubuntu) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr > > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- You received this bug notification because you are a member of
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
** Changed in: linux (Ubuntu Lunar)
Assignee: Jeff Lane (bladernr) => 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/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 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
Hi Chandrakanth, Can you install and test this test kernel onto a 22.04.3 deployment? THere's a tarball you can find here: https://people.canonical.com/~kamal/for-jeffl/ that has all the test packages for you. YOu probably don't need all of them, at a minimum: linux-image-unsigned linux-modules linux-modules-extra Possibly linux-headers too. Please let me know ASAP, that shoudl include all the requested commits. -- 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: [Ubuntu 22.04.04]: mpi3mr driver update request Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 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:
[Kernel-packages] [Bug 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
The cutoff is January 3 for patch submission. And We are closed for the holidays after this friday. I do not nkow that these are going to make 22.04.4 initially. -- 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: [Ubuntu 22.04.04]: mpi3mr driver update request Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 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
[Kernel-packages] [Bug 2045796] Re: Add Support for Broadcom 5760X Adapters
Is there any chance of these being backported upstream into 6.7? ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Summary changed: - Add Support for Broadcom 5760X Adapters + Add Support for Broadcom 5760X Adapters to 24.04 (patches in 6.8) -- 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/2045796 Title: Add Support for Broadcom 5760X Adapters to 24.04 (patches in 6.8) Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: These patches are needed on top of v6.7 to support Broadcom 5760X Adapters. These patches currently reside in the net-next tree and will be included in v6.8. Prerequisite commits in net-next today: c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field These 13 patches below were submitted on 11/20/23 and accepted on 11/21/23. These are the initial patches with 5760X contents. 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx The next 15 patches were submitted on 12/1/23 and accepted on 12/4/23. These are all the basic L2 patches for 5760X including the PCI IDs: 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045425] Re: Windows VM slower performance with Passmark vs Ubuntu VM
Is this also an issue on Zen 4? What about Zen 2? I'm wondering if this is specific to Zen 3 or more generic to AMD and KVM setups? -- 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/2045425 Title: Windows VM slower performance with Passmark vs Ubuntu VM Status in linux package in Ubuntu: New Bug description: Summary : A Windows VM(KVM) on 22.04.3 is 10%(SMT off) to 16%(SMT on) slower running Passmark vs a Ubuntu 22.04.3 VM(KVM). The results should be within 1% of each other. System Information : Dell - AMD EPYC 7543 32-Core Processor, 2801 Mhz, 32 Core(s), 32 Logical Processor(s) Zen 3 (Milan) BIOS - 2.12.4 FW (iDRAC Firmware Version7.00.30.00) NUMA Nodes Per Socket 1(default) Memory - 512 GB of DRAM DDR4 OS : Ubuntu 22.04.3 Setup: Install Ubuntu 22.04.3 and then setup 2 VMs one with Win 22 std. and another one with Ubuntu 22.04.3. Install Passmark benchmark on both the VMs and then run the “Single CPU Threaded” benchmark on both the OS with SMT enable and disable mode. Passmark Download link : https://www.passmark.com/products/pt_linux/download.php Linux Setup version: PerformanceTest Linux x86 64-bit 5.4 MB, v11.0 Build 1002, October 19 2023 Microsoft setup version: Download PerformanceTest 11.0 x86 102 MB, Build 1007 For Intel and AMD x86 CPUs Results : *** Bare metal *** Windows 2022 SMT ON: Win22 VM 1% slower SMT OFF: Win22 VM 1% slower SMT Run1Run2Run3Average On2766276827712768.33 OFF 2773276627652768 Ubuntu 22.04 SMT Run1Run2Run3Average On2777277727752776.33 OFF 2798279227922794 KVM SMT ON : Win22 VM 16% slower SMT OFF: Win22 VM 10% slower Host: Ubuntu 22.04 VM: Win server 22 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On2356228722892310.67 OFF 2424245925662483 Host Ubuntu 22.04 KVM with Ubuntu 22.04 VM - Single CPU Threaded SMT Run1Run2Run3AVERAGE On2730274127292733.33 OFF 2745274627462745.67 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: [Ubuntu 22.04.04]: mpi3mr driver update request
I ran a quick check. Everything up to these exists already in our 6.5 kernel. 9134211f7bed missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~5 6f81b1cfdf33 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~4 d9adb81e67e9 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~3 e7a8648e1ce2 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~2 d9a5ab0ea98f missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2~1 9a9068b2afa0 missing in Ubuntu, possibly upstream at v6.6-rc1~11^2~45^2 82b2fb52d6ec does not appear in Ubuntu. Best guess on first appearance upstream: v6.7-rc1 6fa21eab82be does not appear in either ubuntu or the upstream kernel. c9260ff28ee5 does not appear in either ubuntu or the upstream kernel. cb5b60894602 does not appear in either ubuntu or the upstream kernel. 1193a89d2b6d does not appear in either ubuntu or the upstream kernel. b4d94164ff32 does not appear in either ubuntu or the upstream kernel. Those last five are not in any tree I checked (mainline, linux-next). I'd rather not pull any of these until they've landed at least in linux- next. Otherwise, -- 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: [Ubuntu 22.04.04]: mpi3mr driver update request Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 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
[Kernel-packages] [Bug 2045233] Re: [Ubuntu 22.04.04]: mpi3mr driver update request
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Opinion ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => Medium ** 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/2045233 Title: [Ubuntu 22.04.04]: mpi3mr driver update request Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Opinion Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: This BZ has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). 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. 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 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 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 f0
[Kernel-packages] [Bug 2044589] Re: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2044589 Title: [Ubuntu 24.04 LTS] mpi3mr: Add support for SAS5116 controller and include critical fixes Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Confirmed 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 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
so that said, I still don't know where the issue is... I suspect this will likely never be fixed... When when you say: # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". where do you run that command? On the laptop, or on the remote machine via the xcc console? In other words, where are you changing the keymap? -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in linux package in Ubuntu: Confirmed Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988023] Re: Could not switch uppercase/lowercase by using keyboard of laptop
I was finally able to recreate this from a Jammy VM on my Macbook. Steps to recreate: In Jammy open browser and connect to a Lenovo XCC (BMC) Log in and launch the remote console. type some characters (anywhere works, I did this in the login: prompt on the ubuntu install ** chars will be all lower case tap the caps lock and type chars ** chars will be all lower case double tap the caps lock key (you have to hit it twice) fairly quickly ** chars are now upper case when typed single tap the caps lock key ** chars remain upper case when typed double tap the caps lock key ** chars are once again lower case when typed. It gets weirder because I can get to a point where the caps lock light is off, but the chars are all upper case, or where the caps lock light is on but the chars are all lower case. I was also able to recreate this against a Dell iDRAC console, though in that case once I managed to get the letters in all caps, I could not get caps lock back off again. Finally, I tried this against an HPE iLO5. I was not able to reproduce this issue against the iLO5 device. So all in all I was able to reproduce this issue on 4 different servers (3 Lenovo, 1 Dell) and unable on 1 server (HPE) I then tried this on my desktop and was also able to reproduce this (perhaps in hte past I was just failing to properly set it up? ) from my desktop, this is how it went: open XCC remote console Caps Lock Light Off: type some chars -- all lowercase Hit Caps Lock Key Caps Lock Light On: type some chars -- all lower case Hit Caps Lock Key Caps Lock Light Off: type some chars -- all upper case Hit Caps Lock Key Caps Lock Light On: type some chars -- all upper case Hit Caps Lock Key Caps Lock Light Off: type some chars -- all lower case again. -- 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/1988023 Title: Could not switch uppercase/lowercase by using keyboard of laptop Status in linux package in Ubuntu: Confirmed Bug description: 1. Fresh install ubuntu server 22.04.1 on Lenovo server. 2. Install console-data package 3. Get locale status: # localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: n/a X11 Layout: us X11 Model: pc105 4. Fail to ist and set keymap with command "localectl", but the kmap file can be found in the /usr/share./keymaps/ #localectl list-keymaps Failed to read list of keymaps: No such file or directory # localectl set-keymap us Failed to set keymap: Keymap us is not installed. # find /usr/ -name us.kmap.gz /usr/share/keymaps/i386/qwerty/us.kmap.gz 5. It need type "CapsLock" twice when want to switch uppercase/lowercase by using keyboard of laptop, not once, the other keyboard has no issue about it. # dumpkeys | grep -E "keymaps|58" keymaps 0-127 keycode 58 = CtrlL_Lock 6. It can switch uppercase/lowercase normally after run command "loadkeys us". Please help check why need type twice "CapsLock" for switching uppercase/lowercase and how to fix it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-29 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809) MachineType: Lenovo ThinkSystem SR630 V2 Package: systemd 249.11-0ubuntu3.4 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. Tags: jammy uec-images Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/21/2022 dmi.bios.release: 1.30 dmi.bios.vendor: Lenovo dmi.bios.version: AFE118I-1.30 dmi.board.asset.tag: none dmi.board.name: 7Z70CTO1WW dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.ec.firmware.release: 1.80 dmi.modalias: dmi:bvnLenovo:bvrAFE118I-1.30:bd04/21/2022:br1.30:efr1.80:svnLenovo:pnThinkSystemSR630V2:pvr05:rvnLenovo:rn7Z70CTO1WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z70CTO1WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR630 V2 dmi.product.sku: 7Z70CTO1WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to:
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
Can you install one of the daily ISOs for mantic (23.10) and test to see
if this is an issue? The patches you mention are included in the Mantic
kernel already, so that one should not see the failure.
We're still trying to figure out how to get you a working 6.2 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/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
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 2029905] Re: [Ubuntu] mpi3mr: Include the latest patchset from upstream into 22.04.1/later LTS
Why is this being requested? What specific certification blockers or customer deployments does this affect? We don't generally just pull large numbers of patches in like this without a business justification to backport them, unfortunately, the aim is to update the driver to resolve issues that are affecting folks in the field. If someone needs a new driver version the first suggestion is that they should be running the latest HWE kernel which is where those updates normally land. -- 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: Incomplete 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
[Kernel-packages] [Bug 2033416] Re: change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
Logs not needed for this, it's a feature request for Mantic ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033416 Title: change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels. However, unlike plug and play devices, there is no way to load uncore module when user tries to use uncore event. Also, a primary motivation to add module support in uncore driver was to ease development (https://git.kernel.org/torvalds/c/05485745ad482). So, ask ubuntu to switch to CONFIG_PERF_EVENTS_AMD_UNCORE=y. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033416] [NEW] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
Public bug reported: Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels. However, unlike plug and play devices, there is no way to load uncore module when user tries to use uncore event. Also, a primary motivation to add module support in uncore driver was to ease development (https://git.kernel.org/torvalds/c/05485745ad482). So, ask ubuntu to switch to CONFIG_PERF_EVENTS_AMD_UNCORE=y. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033416 Title: change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y Status in linux package in Ubuntu: New Bug description: Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels. However, unlike plug and play devices, there is no way to load uncore module when user tries to use uncore event. Also, a primary motivation to add module support in uncore driver was to ease development (https://git.kernel.org/torvalds/c/05485745ad482). So, ask ubuntu to switch to CONFIG_PERF_EVENTS_AMD_UNCORE=y. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
doesn't apply to iotg or tegra kernels ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux 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 Released 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 2018443] Re: Cannot setup status IPv6 address for the specific network during installation
For reference:
https://manpages.ubuntu.com/manpages/focal/man7/dracut.cmdline.7.html
https://manpages.ubuntu.com/manpages/focal/en/man7/casper.7.html
ip=:[]:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[][:]]
explicit network configuration. If you want do define a IPv6
address, put it in
brackets (e.g. [2001:DB8::1]). This parameter can be specified
multiple times.
is optional and is the address of the remote endpoint for
pointopoint interfaces and
it may be followed by a slash and a decimal number, encoding the
network prefix
length.
optionally set on the . This cannot be used
in conjunction
with the ifname argument for the same .
(dracut is a universe package).
All I can find online seems to point that Fedora carries patches that
support ipv6 addresses from the kernel command line. The only docs in
the kernel itself relate to ipv4 as part of nfsroot.
Documentation/admin-guide/kernel-parameters.txt
Documentation/admin-guide/nfs/nfsroot.rst
--
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/2018443
Title:
Cannot setup status IPv6 address for the specific network during
installation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Try to install Ubuntu server 20.04/22.04 and setup static IPv4/IPv6
address via kernel parameters for the specific network MAC address,
below solution can work for IPv4, but IPv6 will be failed with the
message “ipconfig: can’t parse IP address ‘ens3f1,[2002”， please help
to check if is the usage for IPv6 incorrect or provide the solution
about IPv6.
Kernel parameters for IPv4(Pass): ksdevice=bootif
BOOTIF=68:05:ca:44:03:87
ip=10.10.10.120::10.10.10.1:255.255.255.010.10.10.1 ds=nocloud-
net;s=http://XX.XX.XX.XX/
Kernel parameters for IPv6(Fail): ksdevice=bootif BOOTIF=68:05:ca:44:03:87
ip=[2002:97b:c2bb:830:10:240:210:31]:::64::eno1:none
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw+ 1 root audio 116, 1 May 5 15:55 seq
crw-rw+ 1 root audio 116, 33 May 5 15:55 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CasperVersion: 1.470.2
DistroRelease: Ubuntu 22.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
LiveMediaBuild: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230217.1)
MachineType: Lenovo ThinkAgile VX7330-N Appliance
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz fsck.mode=skip ksdevice=bootif
BOOTIF=BC:97:E1:1F:62:3C ip=[2002:97b:c2bb:830:10:240:210:31]:::64:::none ---
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
RelatedPackageVersions:
linux-restricted-modules-5.15.0-60-generic N/A
linux-backports-modules-5.15.0-60-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.15.0-60-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/30/2023
dmi.bios.release: 1.51
dmi.bios.vendor: Lenovo
dmi.bios.version: AFE122I-1.51
dmi.board.asset.tag: none
dmi.board.name: 7Z62CTO3WW
dmi.board.vendor: Lenovo
dmi.board.version: 05
dmi.chassis.asset.tag: none
dmi.chassis.type: 23
dmi.chassis.vendor: Lenovo
dmi.chassis.version: none
dmi.ec.firmware.release: 2.20
dmi.modalias:
dmi:bvnLenovo:bvrAFE122I-1.51:bd03/30/2023:br1.51:efr2.20:svnLenovo:pnThinkAgileVX7330-NAppliance:pvr05:rvnLenovo:rn7Z62CTO3WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z62CTO3WW:
dmi.product.family: ThinkSystem
dmi.product.name: ThinkAgile VX7330-N Appliance
dmi.product.sku: 7Z62CTO3WW
dmi.product.version: 05
dmi.sys.vendor: Lenovo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2018443] Re: Cannot setup status IPv6 address for the specific network during installation
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2018443
Title:
Cannot setup status IPv6 address for the specific network during
installation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Try to install Ubuntu server 20.04/22.04 and setup static IPv4/IPv6
address via kernel parameters for the specific network MAC address,
below solution can work for IPv4, but IPv6 will be failed with the
message “ipconfig: can’t parse IP address ‘ens3f1,[2002”， please help
to check if is the usage for IPv6 incorrect or provide the solution
about IPv6.
Kernel parameters for IPv4(Pass): ksdevice=bootif
BOOTIF=68:05:ca:44:03:87
ip=10.10.10.120::10.10.10.1:255.255.255.010.10.10.1 ds=nocloud-
net;s=http://XX.XX.XX.XX/
Kernel parameters for IPv6(Fail): ksdevice=bootif BOOTIF=68:05:ca:44:03:87
ip=[2002:97b:c2bb:830:10:240:210:31]:::64::eno1:none
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw+ 1 root audio 116, 1 May 5 15:55 seq
crw-rw+ 1 root audio 116, 33 May 5 15:55 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}
CasperVersion: 1.470.2
DistroRelease: Ubuntu 22.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
LiveMediaBuild: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release amd64
(20230217.1)
MachineType: Lenovo ThinkAgile VX7330-N Appliance
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz fsck.mode=skip ksdevice=bootif
BOOTIF=BC:97:E1:1F:62:3C ip=[2002:97b:c2bb:830:10:240:210:31]:::64:::none ---
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
RelatedPackageVersions:
linux-restricted-modules-5.15.0-60-generic N/A
linux-backports-modules-5.15.0-60-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.10
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: jammy uec-images
Uname: Linux 5.15.0-60-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/30/2023
dmi.bios.release: 1.51
dmi.bios.vendor: Lenovo
dmi.bios.version: AFE122I-1.51
dmi.board.asset.tag: none
dmi.board.name: 7Z62CTO3WW
dmi.board.vendor: Lenovo
dmi.board.version: 05
dmi.chassis.asset.tag: none
dmi.chassis.type: 23
dmi.chassis.vendor: Lenovo
dmi.chassis.version: none
dmi.ec.firmware.release: 2.20
dmi.modalias:
dmi:bvnLenovo:bvrAFE122I-1.51:bd03/30/2023:br1.51:efr2.20:svnLenovo:pnThinkAgileVX7330-NAppliance:pvr05:rvnLenovo:rn7Z62CTO3WW:rvr05:cvnLenovo:ct23:cvrnone:sku7Z62CTO3WW:
dmi.product.family: ThinkSystem
dmi.product.name: ThinkAgile VX7330-N Appliance
dmi.product.sku: 7Z62CTO3WW
dmi.product.version: 05
dmi.sys.vendor: Lenovo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018443/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1967848] Re: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 Status in linux package in Ubuntu: Invalid Bug description: This bug is raised as per the suggestion by Jeff Email snapshot: -- File a bug, point me to a patch, and I'll see if I can pull it. Though we'd need more info... for are we talking the 4.15 GA kernel, or the 5.4 kernel? It would be a bit more involved If I have to pull the patch into 4 different kernels in order to get it back into 4.15 to avoid regressions. BUT it's not difficult, assuming any patches are only applied to lpfc. Once it lands in the scsi tree we can start looking, though I'd be more comfy for it to be in linux-next or mainline. I'll also need someone to fill out some info on the bug to create the SRU justification. -- There is an issue in which we are seeing login failure with Ubuntu 18.04.3, inbox driver version 12.0.0.0 but this issue is not seen with Ubuntu 20.04.2 with inbox driver 12.0.0.6. I found that upstream commit id [0a9e9687acaf6ac1198fd41f03d64f8b92e4515e] could potentially fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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, When you say you redacted those two patches, just to be clear you're saying to remove them from the list of patches to apply, correct? 0ca190805784 scsi: smartpqi: Call scsi_done() directly 64fc9015fbeb scsi: smartpqi: Switch to attribute groups I have a member of my team working through them to apply to the current master-next for our 5.15 kernel and he said he's having trouble getting them to pick cleanly and is working through them 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/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 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Current status:
I had to apply all the patches to a much older kernel because there are
conflicts when cherry picking on the latest version on master-next.
After applying the patches successfully on tag: Ubuntu-5.15.0-56.62 I
started rebasing each tag in sequence trying to find where it first
breaks.
I made it to Ubuntu-5.15.0-58.64 successfully and when I then rebased on
Ubuntu-5.15.0-59.65 the cherrypicks start failing.
I got stuck trying to find what was pulled in between those two tag
that's causing the conflict. As the advice I got from the kernel team
was "everything should be a clean cherry pick except for the backported
patches" I ended up banging my head trying to find the culprit. Then
resources became an issue. Michael has also started looking at this to
put fresh eyes on it and also since I'm finding I have even less time
(and too many things going on at once).
Michael is now taking a look to figure out what changed between those
two tags.
--
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
[Kernel-packages] [Bug 1976228] Re: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan-scsi-bus.sh -r' command is executed
Moved this because it seems to be an issue specifically with rescan_scsi_bus.sh... it may be that there IS a kernel component too, but for now I was able to obliterate a system using "rescan-scsi-bus.sh -r" on a system wiht a pretty simple local FS setup: ubuntu@barbos:~$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=32718576k,nr_inodes=8179644,mode=755,inode64) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6555388k,mode=755,inode64) /dev/sda2 on / type ext4 (rw,relatime,stripe=128) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=131329) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) none on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700) tmpfs on /run/qemu type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64) /var/lib/snapd/snaps/lxd_24322.snap on /snap/lxd/24322 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) /var/lib/snapd/snaps/snapd_18357.snap on /snap/snapd/18357 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/sdb1 on /data-sdb type ext4 (rw,relatime,stripe=64) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=6555388k,mode=755,inode64) nsfs on /run/snapd/ns/lxd.mnt type nsfs (rw) /var/lib/snapd/snaps/core20_1828.snap on /snap/core20/1828 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) /var/lib/snapd/snaps/snapd_18596.snap on /snap/snapd/18596 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) /var/lib/snapd/snaps/core20_1852.snap on /snap/core20/1852 type squashfs (ro,nodev,relatime,errors=continue,x-gdu.hide) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=6555384k,nr_inodes=1638846,mode=700,uid=1000,gid=1000,inode64) ubuntu@barbos:~$ sudo apt install sg3-utils Reading package lists... Done Building dependency tree... Done Reading state information... Done sg3-utils is already the newest version (1.46-1build1). sg3-utils set to manually installed. kiujln ,0 upgraded, 0 newly installed, 0 to remove and 0 not
[Kernel-packages] [Bug 2008750] Re: [SRU] Daxctl gets the error of resource busy on HBM devices
This needs more information before I can pass it upstream. What hardware (don't need make model but do need things like "we're using X version NVDIMM and Y CPU with AA.BB Ubuntu and kernel C.DD.EE) Also, explicit steps to reproduce this would be useful as well. And more info hopefully like some syslog snippets when this occurs, etc. As it stands, this is not actionable information. -- 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/2008750 Title: [SRU] Daxctl gets the error of resource busy on HBM devices Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On Ubuntu, it gets the error of "Device or resource busy." fuser shows that the kernel thread "kdevtmpfs" is occupying the HBMs. I tried to build a kernel without CONFIG_DEVTMPFS set. But it got stuck in initramfs If it is possible, please get this issue a quick triage, just to get a basic estimate how hard this issue is and how much effort is needed for Ubuntu for support it. [Fix] [Test Plan] [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008750] Re: [SRU] Daxctl gets the error of resource busy on HBM devices
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008750 Title: [SRU] Daxctl gets the error of resource busy on HBM devices Status in linux package in Ubuntu: Incomplete Bug description: [Impact] On Ubuntu, it gets the error of "Device or resource busy." fuser shows that the kernel thread "kdevtmpfs" is occupying the HBMs. I tried to build a kernel without CONFIG_DEVTMPFS set. But it got stuck in initramfs If it is possible, please get this issue a quick triage, just to get a basic estimate how hard this issue is and how much effort is needed for Ubuntu for support it. [Fix] [Test Plan] [Where problems could occur] [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 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] -- 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 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 2004262] Re: Intel E810 NICs driver in causing hangs when booting and bonds configured
Update from upstream:
The patch (v2) was dropped because a customer reported it did not fix
their issue. I just reached out to the developer for an ETA to fix it
and will keep you posted.
Additionally there is ongoing discussion around the V2 of that patch here:
https://lore.kernel.org/intel-wired-lan/ygay1oxikvo.fsf@localhost/T/#m31a3f2847d013a41104524bd81e7f2fa481b4b97
--
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/2004262
Title:
Intel E810 NICs driver in causing hangs when booting and bonds
configured
Status in linux package in Ubuntu:
Incomplete
Bug description:
jammy 22.04.1
linux-image-generic 5.15.0-58-generic
Intel E810-XXV Dual Port NICs in Dell PowerEdge 650
- 5.15 in jammy -> reproducible
- 5.19 in hwe-edge -> reproducible
- 6.2.rc6 in the mainline build -> works
- Intel's ice driver 1.10.1.2.2 -> works
After beonding is enabled on switch and server side, the system will hang at
initialing ubuntu. The kernel loads but around starting the Network Services
the system can hang for sometimes 5 minutes, and in other cases, indefinitely.
The message of:
echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve
blocked for more than 120 seconds
appears, and eventually the Network services just attempts to start
and never does. This is with or without DHCP enabled.
Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and
linux-oem kernels and all exhibit the same failure.
To work around this. installing the Intel 'ice' driver of version
1.10.1.2.2 works. The system doesn't even remotely hang at startup
and all networking functions remain working (ping, DNS, general
accessibility).
The driver can be found at
https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jan 31 13:08 seq
crw-rw 1 root audio 116, 33 Jan 31 13:08 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5json:
{
"result": "skip"
}DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2023-01-27 (3 days ago)InstallationMedia:
Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Dell Inc. PowerEdge R650
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic
root=UUID=668aab7c-abe9-434b-a810-acc6eab76cbc ro fsck.mode=skip
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
RelatedPackageVersions:
linux-restricted-modules-5.15.0-58-generic N/A
linux-backports-modules-5.15.0-58-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'Tags: jammy
uec-images
Uname: Linux 5.15.0-58-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/14/2022
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 0PJ7YJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.2:bd09/14/2022:br1.8:svnDellInc.:pnPowerEdgeR650:pvr:rvnDellInc.:rn0PJ7YJ:rvrA01:cvnDellInc.:ct23:cvr:skuSKU=0912;ModelName=PowerEdgeR650:
dmi.product.family: PowerEdge
dmi.product.name: PowerEdge R650
dmi.product.sku: SKU=0912;ModelName=PowerEdge R650
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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, The kernel team tried applying these pulls today and the test builds broke, this is the comment from the update on the mailing list: Those will be dropped again because they break the build: https://kernel.ubuntu.com/~kernel-ppa/test- build/jammy/linux/LP%231998643-- bf73a7aff8a9516a913af89dc7a3bba77c2de62d/amd64/log ** Changed in: linux (Ubuntu Jammy) Status: In Progress => 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/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 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: Don Brace (bracedon) => Jeff Lane (bladernr) -- 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 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 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
Update: Everything applied fine, but my PR got kicked back again because
they didn't like how I did it (I ended up doing a single commit with all
the patches, so I need to now go back and redo this with a commit for
each individual patch)
I'll work on that today and tomorrow and try to get a new PR by friday
afternoon.
--
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
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
Hey Don, Everything has been accepted by the kernel team. I don't have an eta on when it will be merged, but there's nothing more to do now but wait and eventually this should be updated with a request to test a proposed kernel in the next few weeks. -- 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: 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 1998643] Re: smartpqi: Update 22.04 driver to latest kernel.org
** 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. - [impact] - This patches correct some bugs and add support for more PCI devices. Also, the in-box driver is largely out-of-date with kernel.org. + [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. - [fix] - Applying these patches (along with the patches noted below) bring smartpqi up to date with our OOB driver and kernel.org. Both have been tested. - [Test Plan] Our OOB driver has undergone extensive testing by our test team. + One should be able to load the smartpqi driver and verify the version is + at 2.1.18-045 ** Summary changed: - smartpqi: Update 22.04 driver to latest kernel.org + smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices -- 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: 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
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
** Summary changed:
- Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
+ Update Broadcom Emulex FC HBA lpfc driver to 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
[Kernel-packages] [Bug 1986717] Re: Update ice driver to support E823 devices
Update from OEM: Hi Rick and Jeff, I have tested those packages. E823 can be recognized by Ubuntu 18.04.6 OS(kernel ) and i can use them to ping “www.google.com” But the name is not complete when I use "lspci" command and some pkgs have dependency issue when I installed. “linux-cloud- tools-5.4.0-136-generic_5.4.0-136.153_amd64.deb and linux- tools-5.4.0-136-generic_5.4.0-136.153_amd64.deb” Test result is below=== root@hakuba:~# uname -mrs Linux 5.4.0-136-generic x86_64 root@hakuba:~# root@hakuba:~# ethtool -i eno6 driver: ice version: 0.8.1-k firmware-version: 2.28 0x8001028e 0.0.0 expansion-rom-version: bus-info: :89:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes root@hakuba:~# lspci |grep -i ethernet 03:00.0 Ethernet controller: Intel Corporation Device 125d (rev 04) 04:00.0 Ethernet controller: Intel Corporation Device 125d (rev 04) 89:00.0 Ethernet controller: Intel Corporation Device 188e 89:00.1 Ethernet controller: Intel Corporation Device 188e 89:00.2 Ethernet controller: Intel Corporation Device 188e 89:00.3 Ethernet controller: Intel Corporation Device 188e root@hakuba:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno6: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:00:00:00:01:00 brd ff:ff:ff:ff:ff:ff inet 10.241.99.166/24 brd 10.241.99.255 scope global eno6 valid_lft forever preferred_lft forever inet6 fe80::200:ff:fe00:100/64 scope link valid_lft forever preferred_lft forever 3: eno5: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:01:01 brd ff:ff:ff:ff:ff:ff 4: eno4: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:01:02 brd ff:ff:ff:ff:ff:ff 5: eno3: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:01:03 brd ff:ff:ff:ff:ff:ff root@hakuba:~# ping www.google.com PING www.google.com (142.250.186.132) 56(84) bytes of data. 64 bytes from fra24s07-in-f4.1e100.net (142.250.186.132): icmp_seq=1 ttl=105 time=266 ms 64 bytes from fra24s07-in-f4.1e100.net (142.250.186.132): icmp_seq=2 ttl=105 time=266 ms 64 bytes from fra24s07-in-f4.1e100.net (142.250.186.132): icmp_seq=3 ttl=105 time=265 ms 64 bytes from fra24s07-in-f4.1e100.net (142.250.186.132): icmp_seq=4 ttl=105 time=265 ms 64 bytes from fra24s07-in-f4.1e100.net (142.250.186.132): icmp_seq=5 ttl=105 time=265 ms 64 bytes from fra24s07-in-f4.1e100.net (142.250.186.132): icmp_seq=6 ttl=105 time=265 ms -- 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/1986717 Title: Update ice driver to support E823 devices Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: Impact: Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. Fix: After talking with engineers upstream this should be the only patch needed to add the support that is missing in 5.4 e36aeec0f4e5 ice: add support for E823 devices Testcase: Load ice driver on system with E823 device present and ensure the device is seen by the system Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
c should indicate version is 14.2.0.5 or greater. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988711/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=In Progress; importance=Medium; assignee=jeffrey.l...@canonical.com > ; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=In Progress; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=kinetic; > sourcepackage=linux; component=main; status=Fix Released; > importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Tags: kernel-spammed-kinetic-linux scd-1 > verification-needed-kinetic > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: aravindvalloormana bladernr janitor > ketan-mukadam ubuntu-kernel-bot > Launchpad-Bug-Reporter: Aravind Valloor Mana (aravindvalloormana) > Launchpad-Bug-Modifier: Ketan Mukadam (ketan-mukadam) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr > > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- 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 for Ubuntu 22.04 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
[Kernel-packages] [Bug 1976228] Re: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan-scsi-bus.sh -r' command is executed
The R630 is no longer sold by Dell and has not been certifed since 16.04. While usually these continue working fine with OS versions newer than the one that was certified, there is no guarantee that will always be the case. What is driving this? -- 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/1976228 Title: [Ubuntu 22.04 LTS]The host OS becomes read-only after the 'rescan- scsi-bus.sh -r' command is executed Status in linux package in Ubuntu: Confirmed Bug description: OS:Ubuntu 22.04 LTS kernel:5.15.0-33-generic host model:Dell PowerEdge R630 issue description: After I mapped luns from array to my host, I ran 'rescan-scsi-bus.sh -r' to scan for luns, my host crashed and became read-only.After the KVM forcibly restarts the host, the host is restored to normal. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 08:33 seq crw-rw 1 root audio 116, 33 May 30 08:33 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-26 (4 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-33-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/14/2021 dmi.bios.release: 2.13 dmi.bios.version: 2.13.0 dmi.board.name: 02C2CP dmi.board.version: A01 dmi.chassis.type: 23 dmi.modalias: dmi:bvn:bvr2.13.0:bd05/14/2021:br2.13:svn:pn:pvr:rvn:rn02C2CP:rvrA01:cvn:ct23:cvr:skuSKU=NotProvided;ModelName=: dmi.product.sku: SKU=NotProvided;ModelName= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986717] Re: Update ice driver to support E823 devices
** Changed in: linux (Ubuntu) Status: In Progress => 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/1986717 Title: Update ice driver to support E823 devices Status in linux package in Ubuntu: Incomplete Bug description: SRU Justification: Impact: Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is part of the Ice Lake D platform which is otherwise supported in 5.4. One of the hardware vendors has requested that we update Ice in 5.4 to support E823. Fix: After talking with engineers upstream this should be the only patch needed to add the support that is missing in 5.4 e36aeec0f4e5 ice: add support for E823 devices Testcase: Load ice driver on system with E823 device present and ensure the device is seen by the system Other Info: https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e823_intel_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 latest kernel.org
Thanks, Don... sorry to ask but to make this easier on me (I'm the one who has to find the time do do this) could you revise the list in the summary with all the desired patches (including the ones from the 6.2 MKP tree) in pick order? And just to be sure, they all cleanly pick with no missing prerequisites or conflicts? I will have to sort out what to pick for each affected kernel, as I will have to pull them back from 6.2 -> 5.19. Also, Gerry said the target was 20.04.2, so that means the 5.19 HWE kernel, yes? 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/1998643 Title: smartpqi: Update 22.04 driver to latest kernel.org Status in linux package in Ubuntu: Incomplete Bug description: 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. [impact] This patches correct some bugs and add support for more PCI devices. Also, the in-box driver is largely out-of-date with kernel.org. [fix] Applying these patches (along with the patches noted below) bring smartpqi up to date with our OOB driver and kernel.org. Both have been tested. [Test Plan] Our OOB driver has undergone extensive testing by our test team. 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 1998168] Re: System went crash during Ubuntu 20.04.5 installation
Also, are you sure this isn't an issue with the lab networking, since
you said that it works fine if you disable networking.
I will raise this with the team that handles the installer, because this
could be handled more gracefully.
--
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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998168] Re: System went crash during Ubuntu 20.04.5 installation
can you collect a sosreport and attach 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/1998168
Title:
System went crash during Ubuntu 20.04.5 installation
Status in linux package in Ubuntu:
Confirmed
Bug description:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso
CPU:INTEL(R)XEON(R)PLATINUM8470QSAPPHIRERAPIDSE3105MB52cFC-LGA350WQ16Q
EV-QS*2
SSD:Intel S4620 2.5'1.92T Mainstream SATA 6Gb Hot Swap SSD* 2
Boot mode:UEFI
Reproduce Steps:
Install ubuntu 22.04 on disk
Current behaviors:
System will crash during installation
2022-09-28 22:18:59,807 INFO subiquitycore.common.errorreport:406 saving
crash report 'install failed crashed with CalledProcessError' to
/var/crash/1664403539.805207491.install_fail.crash
2022-09-28 22:18:59,807 ERROR root:39 finish: subiquity/Install/install:
FAIL: Command '['systemd-run', '--wait', '--same-dir', '--property',
'SyslogIdentifier=subiquity_log.5855', '--property', 'PrivateMounts=yes',
'--setenv',
'PATH=/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/subiquity/3698/bin:/snap/subiquity/3698/bin',
'--setenv',
'PYTHONPATH=:/snap/subiquity/3698/lib/python3.8/site-packages:/snap/subiquity/3698/lib/python3.8/site-packages',
'--setenv', 'PYTHON=/snap/subiquity/3698/usr/bin/python3.8', '--setenv',
'SNAP=/snap/subiquity/3698', '--', '/snap/subiquity/3698/usr/bin/python3.8',
'-m', 'curtin', '--showtrace', '-vvv', '--set', 'json:reporting={"subiquity":
{"type": "journald", "identifier": "curtin_event.5855.2"}}', 'in-target', '-t',
'/tmp/tmpq8qjbbe5/mount', '--', 'apt-get', 'update']' returned non-zer
o exit status 100.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998168/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997213] Re: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add
apport-collect only launches the browser to authorize collection via Launchpad. You can copy and paste, or type the URL into any browser on a different machine and authorize 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/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: Confirmed Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems：Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage： 7MM Drive 0-1：7.68TB 7MM NVMe SSD（PN：MTFDKCB7T6TFR，FW：E2MU110） Drive 0：240GB SATA SSD （PN：SSS7B07725 ，FW：MQ31） Drive 1-2：1.92TB NVMe SSD（PN：SSDPF2KX019T1O，FW：9CV10320） Drive 3-4：400GB NVMe SSD（PN：SSDPF21Q400GB，FW：L0310600） Drive 5-8：12.0TB SATA HDD（PN：01GV193，FW：LEGNK9R5） Drive 9：240GB SATA SSD（PN：SSS7B07725，FW：MQ31） Drive 10-11：960GB SATA SSD（PN：SSS7A43198，FW：MP33） Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
gt; native SLI4 > a680a9298e7b scsi: lpfc: SLI path split: Refactor lpfc_iocbq > dc2646417d54 scsi: lpfc: Use kcalloc() > 9a866e6aaf4e scsi: lpfc: Fix typos in comments > e81ce97f5716 scsi: lpfc: Use rport as argument for lpfc_chk_tgt_mapped() > 123a3af35d08 scsi: lpfc: Use rport as argument for lpfc_send_taskmgmt() > bb21fc9911ee scsi: lpfc: Use fc_block_rport() > 45c59287ff01 scsi: lpfc: Drop lpfc_no_handler() > bf180cc1a5da scsi: lpfc: Kill lpfc_bus_reset_handler() > 7f4c5a26f735 scsi: lpfc: Fix pt2pt NVMe PRLI reject LOGO loop > 5852ed2a6a39 scsi: lpfc: Reduce log messages seen after firmware download > c80b27cfd93b scsi: lpfc: Remove NVMe support if kernel has NVME_FC > disabled > d1d87c33f47d scsi: lpfc: Remove redundant flush_workqueue() call > ce5a58a96ccc scsi: lpfc: Use irq_set_affinity() > > [TESTCASE] > modinfo for lpfc should indicate version is 14.2.0.5 or greater. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988711/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=In Progress; importance=Medium; assignee=jeffrey.l...@canonical.com > ; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=In Progress; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=kinetic; > sourcepackage=linux; component=main; status=In Progress; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Tags: scd-1 > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: aravindvalloormana bladernr ubuntu-kernel-bot > Launchpad-Bug-Reporter: Aravind Valloor Mana (aravindvalloormana) > Launchpad-Bug-Modifier: Aravind Valloor Mana (aravindvalloormana) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr > > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- 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 for Ubuntu 22.04 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 Committed 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
Re: [Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
Hi Kim, Just like with Focal, for the Bionic backport of this fix, could you just quickly confirm it's there and didn't break anything as you see it? Thanks On Tue, Nov 1, 2022 at 11:00 AM Ubuntu Kernel Bot < 1990...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux/4.15.0-196.207 kernel > in -proposed solves the problem. Please test the kernel and update this > bug with the results. If the problem is solved, change the tag > 'verification-needed-bionic' to 'verification-done-bionic'. If the > problem still exists, change the tag 'verification-needed-bionic' to > 'verification-failed-bionic'. > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1990985 > > Title: > ACPI: processor idle: Practically limit "Dummy wait" workaround to old > Intel systems > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > Fix Committed > Status in linux source package in Focal: > Fix Committed > Status in linux source package in Jammy: > Fix Committed > Status in linux source package in Kinetic: > In Progress > > Bug description: > IMPACT: > Old, circa 2002 chipsets have a bug: they don't go idle when they are > supposed to. So, a workaround was added to slow the CPU down and > ensure that the CPU waits a bit for the chipset to actually go idle. > This workaround is ancient and has been in place in some form since > the original kernel ACPI implementation. > > But, this workaround is very painful on modern systems. The "inl()" > can take thousands of cycles (see Link: for some more detailed > numbers and some fun kernel archaeology). > > First and foremost, modern systems should not be using this code. > Typical Intel systems have not used it in over a decade because it is > horribly inferior to MWAIT-based idle. > > Despite this, people do seem to be tripping over this workaround on > AMD system today. > > Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD > systems from tripping over the workaround. Remotely modern Intel > systems use intel_idle instead of this code and will, in practice, > remain unaffected by the dummy wait. > > Reported-by: K Prateek Nayak > Suggested-by: Rafael J. Wysocki > Signed-off-by: Dave Hansen > Reviewed-by: Mario Limonciello > Tested-by: K Prateek Nayak > Link: > https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ > Link: > https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com > > FIX: > > This issue pertains to all Zen based processors starting with > Naples(Zen1). All LTS releases will need this fix: > > > https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 > > TESTCASE: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=In Progress; importance=Medium; assignee=jeffrey.l...@canonical.com > ; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=linux; component=main; status=Fix Committed; > importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=focal; > sourcepackage=linux; component=main; status=Fix Committed; > importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=Fix Committed; > importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=kinetic; > sourcepackage=linux; component=main; status=In Progress; importance=Medium; > assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Tags: verification-done-focal verification-done-jammy > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: bladernr kim-naru ubuntu-kernel-bot > Launchpad-Bug-Reporter: Kim Naru (kim-naru) > Launchpad-Bug-Modifier: Ubuntu Kernel Bot (ubuntu-kernel-bot) > Launchpad-Message-Rationale: Assignee > Launchpad-Message-For: bladernr > > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Not sure why you were seeing this, if those patches fix the issue, but they have existed in 5.15 for a while from what I can see. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
the 5.15 kernel has contained these patches since Ubuntu-5.15.0-1.1 bladernr@arcadia:~/development/kernels-ubuntu/jammy$ git tag --contains 10764815ff4728d2c57da677cd5d3dd6f446cf5f |head -1 Ubuntu-5.15.0-1.1 bladernr@arcadia:~/development/kernels-ubuntu/jammy$ git tag --contains de3ea66e9d23a34eef5e17f960d6473f78a1c54b |head -1 Ubuntu-5.15.0-1.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1986668] Re: [VROC] Kernel does not contain fixes for iostat for md devices
》Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top 》 on the revert patch: 〉- first commit from series: 10764815ff415728d2c57da677cd5d3dd6f446cf5f 》(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/？id=10) 》- last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b 》(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id66=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) both of those patches exist in 5.15 since the beginning from Ubuntu-5.15.0-1.1 ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
Hi Arvind, The Kinetic (5.19) ones went in pretty easily and are likely to be in the next SRU kernel for 5.19. The Jammy pull (5.15) is another story. In the time it took for me to apply all 100ish patches and submit my tree, the kernel team had made a ton of stable updates and when they went to apply my changes for this, there were numerous conflicts and duplicates. So I'm going to have to now go through all 100 or so patches and figure out what needs to be pulled and what isn't cleanly applying otherwise. Cheers Jeff -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." On Tue, Oct 18, 2022 at 6:40 AM Aravind Valloor Mana < 1988...@bugs.launchpad.net> wrote: > Hi Jeff, > > Do you have the kernel version which has these lpfc patches integrated? > If not, any ETA? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1988711 > > Title: > Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04 > > 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: > [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: F
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
** 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990342] Re: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5, Ubuntu 22.04 and Ubuntu 22.04.1
Both of those patches are in 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/1990342 Title: Intel EGS PCH tSATA RAID cannot be detected in Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 22.04.1 Status in linux package in Ubuntu: Confirmed Bug description: Configuration: OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN BMC Version 0.48 (Build ID: ESX303K) UEFI Version 0.62 (Build ID: ESE105G) SSD:931.51GB 7.2K SATA HDD S471A08RSH20K04054 00LF039 SSD*2(SATA 0/1):894.25GB SATA SSD HDD*2(SATA 2 alias tsata): 1TB SATA HDD Boot mode:UEFI Reproduce Steps: 1.Boot UEFI,System Settings->Devices and I/O ports,Onboard SATA 2 mode set to "RAID",save and reboot. 2.Boot UEFI,UEFI,System Settings->Storage->Intel VROC tSATA Controller,via drive 12,13 HDD to create RAID Volume,save and reboot. 3.During the installation of Ubuntu(Ubuntu20.04.5,Ubuntu 22.04 and Ubuntu 22.004.1),the raid group under tSATA is not detected. 4.In the OS,the RAID of the tSATA group is not detected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 for Ubuntu 22.04
** Description changed:
[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. These all are limited to
the lpfc driver itself, no patches to core code are requested.
+ 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.
+ 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 scsi: lpfc: Revise FDMI reporting of supported port speed for
trunk groups
d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O
[Kernel-packages] [Bug 1991620] Re: NDCTL test failed on platform of FHF/SPR-DNP/SPR-CYP
*** This bug is a duplicate of bug 1987923 *** https://bugs.launchpad.net/bugs/1987923 This patch is already in 22.10: bladernr@galactica:~/development/kernels/ubuntu/kinetic$ check-patch 8d12ec10292877751ee4463b11a63bd850bc09b5 8d12ec10292877751ee4463b11a63bd850bc09b5 is provided by 8cbf9291e8da in Ubuntu starting at Ubuntu-5.19.0-16.16~529 So I've marked this as a duplicate of the bug that pulled this patch in with several other patches. ** Package changed: ubuntu => linux (Ubuntu) ** This bug has been marked a duplicate of bug 1987923 Kinetic update: v5.19.4 upstream stable 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/1991620 Title: NDCTL test failed on platform of FHF/SPR-DNP/SPR-CYP Status in intel: Fix Committed Status in linux package in Ubuntu: New Bug description: [Bug Description] we detect this defect in Ubuntu 22.10 because it comes from virtio block driver. It only could be duplicated within VM guest OS as 50% probability. When this defect had been triggered, kernel would crash behaved as NULL pointer bug. [ 221.737864] xhci_hcd :02:00.0: xHC error in resume, USBSTS 0x401, Reinit [ 221.737869] usb usb1: root hub lost power or was reset [ 221.737870] usb usb2: root hub lost power or was reset [ 221.739103] virtio_blk virtio2: 144/0/0 default/read/poll queues [ 221.792639] BUG: kernel NULL pointer dereference, address: 0038 [ 221.792646] #PF: supervisor read access in kernel mode [ 221.792650] #PF: error_code(0x) - not-present page [ 221.792654] PGD 0 P4D 0 [ 221.792660] Oops: [#1] PREEMPT SMP PTI [ 221.792667] CPU: 127 PID: 4679 Comm: kworker/u288:62 Tainted: G O 5.19.3-nd-07 #1 [ 221.792674] Hardware name: Red Hat KVM/RHEL, BIOS 1.15.0-1.el9 04/01/2014 [ 221.792677] Workqueue: writeback wb_workfn (flush-252:0) [ 221.792692] RIP: 0010:virtqueue_add_sgs+0x5b/0xe0 [ 221.792705] Code: 8d 2c de 49 89 f4 31 db 49 8b 3c 24 48 85 ff 74 10 e8 29 50 e7 ff 83 c3 01 48 89 c7 48 85 c0 75 f0 49 83 c4 08 4d 39 ec 75 de <45> 0f b6 66 38 41 80 fc 01 0f 87 6b 23 58 00 41 83 e4 01 8b 45 c4 [ 221.792710] RSP: 0018:baec0e7bbb48 EFLAGS: 00010046 [ 221.792715] RAX: RBX: 0003 RCX: 0001 [ 221.792719] RDX: 0003 RSI: baec0e7bbbe0 RDI: [ 221.792722] RBP: baec0e7bbb88 R08: 9626232c2960 R09: 0a20 [ 221.792725] R10: 96262323f640 R11: 9626232c19c8 R12: baec0e7bbbf8 [ 221.792728] R13: baec0e7bbbf8 R14: R15: baec0e7bbbe0 [ 221.792731] FS: () GS:96353f9c() knlGS: [ 221.792736] CS: 0010 DS: ES: CR0: 80050033 [ 221.792740] CR2: 0038 CR3: 0001ce410005 CR4: 003706e0 [ 221.792751] DR0: DR1: DR2: [ 221.792753] DR3: DR6: fffe0ff0 DR7: 0400 [ 221.792757] Call Trace: [ 221.792760] [ 221.792776] virtblk_add_req+0x9f/0x110 [virtio_blk] [ 221.792791] virtio_queue_rqs+0xfb/0x214 [virtio_blk] [ 221.792800] blk_mq_flush_plug_list+0x1ee/0x2c0 [ 221.792811] __blk_flush_plug+0xe9/0x130 [ 221.792820] blk_finish_plug+0x2d/0x50 [ 221.792826] wb_writeback+0x29f/0x2d0 [ 221.792834] wb_workfn+0x2cf/0x4c0 [ 221.792840] ? _raw_spin_unlock_irqrestore+0xe/0x40 [ 221.792853] ? try_to_wake_up+0x260/0x600 [ 221.792866] process_one_work+0x211/0x3d0 [ 221.792874] worker_thread+0x50/0x3d0 [ 221.792879] ? rescuer_thread+0x3b0/0x3b0 [ 221.792884] kthread+0xe9/0x110 [ 221.792893] ? kthread_complete_and_exit+0x20/0x20 [ 221.792901] ret_from_fork+0x22/0x30 [ 221.792914] Commits:8d12ec10292877751ee4463b11a63bd850bc09b5 # git tag --contains 8d12ec10292877751ee4463b11a63bd850bc09b5 v6.0 The defect was introduced to upstream Kernel in v5.18, but the patch was released after v5.19. So current Ubuntu 22.10 Kernel, which based on v5.19, doesn’t have the fix. [HW/SW Information] Target Kernel: 5.19+ Target Release: 22.10 Platform affected: Sapphire Rapids/Fish Halk Falls [Business Justification] Bug fixing To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1991620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
Focal requires 1 addtional patch: fa583f71a99c8 2019-10-24 Yin Fengwei ACPI: processor_idle: Skip dummy wait if kernel is in guest ** Changed in: linux (Ubuntu Kinetic) 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
Hi Laurie, Just wanted to confirm that it's sufficient for this to be in 22.04 GA (5.15) before I close it out -- 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/1971193 Title: Server Crash while running IO and switch port bounce test with 2K login session Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Bug description: [Impact] Server crash and Call trace reported on one of the servers running IO and switch port bounce test from the 2K login session configuration. Call Trace: [56048.470488] Call Trace: [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470492] ? __schedule+0x280/0x700 [56048.470492] ? finish_wait+0x80/0x80 [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470493] kthread+0x112/0x130 [56048.470493] ? kthread_flush_work_fn+0x10/0x10 [56048.470494] ret_from_fork+0x1f/0x40 [56048.470494] Kernel panic - not syncing: Hard LOCKUP [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G IOE- - - 4.18.0-240.el8.x86_64 #1 [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2 004/21/2021 [56048.470496] Call Trace: [56048.470496] [56048.470496] dump_stack+0x5c/0x80 [56048.470497] panic+0xe7/0x2a9 [56048.470497] ? __switch_to_asm+0x51/0x70 [56048.470497] nmi_panic.cold.9+0xc/0xc [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 [56048.470498] __perf_event_overflow+0x52/0xf0 [56048.470499] handle_pmi_common+0x1db/0x270 [56048.470499] ? __set_pte_vaddr+0x32/0x50 [56048.470499] ? __native_set_fixmap+0x24/0x30 [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 [56048.470500] intel_pmu_handle_irq+0xbf/0x160 [56048.470501] perf_event_nmi_handler+0x2d/0x50 [56048.470501] nmi_handle+0x63/0x110 [56048.470501] default_do_nmi+0x4e/0x100 [56048.470502] do_nmi+0x128/0x190 [56048.470502] end_repeat_nmi+0x16/0x6a [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 [56048.470505] RAX: 0101 RBX: 0246 RCX: 001f [56048.470505] RDX: RSI: RDI: 94dcf5341dc0 [56048.470506] RBP: 94dcf534 R08: 0002 R09: 00029600 [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: 94dcf5341db0 [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15: 0003 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470508] [56048.470508] _raw_spin_lock_irqsave+0x32/0x40 [56048.470509] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470509] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470509] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470510] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470510] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470510] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470511] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470511] ? __schedule+0x280/0x700 [56048.470511] ? finish_wait+0x80/0x80 [56048.470512] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470512] kthread+0x112/0x130 [56048.470513] ? kthread_flush_work_fn+0x10/0x10 [56048.470513] ret_from_fork+0x1f/0x40 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/module/lpfc/version 0:14.0.390.2 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/modeldesc Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/fwrev 14.0.390.1, sli-4:2:c 14.0.390.1, sli-4:2:c [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat
[Kernel-packages] [Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
** Also affects: linux (Ubuntu Jammy) 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/1971193 Title: Server Crash while running IO and switch port bounce test with 2K login session Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: New Bug description: [Impact] Server crash and Call trace reported on one of the servers running IO and switch port bounce test from the 2K login session configuration. Call Trace: [56048.470488] Call Trace: [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470492] ? __schedule+0x280/0x700 [56048.470492] ? finish_wait+0x80/0x80 [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470493] kthread+0x112/0x130 [56048.470493] ? kthread_flush_work_fn+0x10/0x10 [56048.470494] ret_from_fork+0x1f/0x40 [56048.470494] Kernel panic - not syncing: Hard LOCKUP [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G IOE- - - 4.18.0-240.el8.x86_64 #1 [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2 004/21/2021 [56048.470496] Call Trace: [56048.470496] [56048.470496] dump_stack+0x5c/0x80 [56048.470497] panic+0xe7/0x2a9 [56048.470497] ? __switch_to_asm+0x51/0x70 [56048.470497] nmi_panic.cold.9+0xc/0xc [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 [56048.470498] __perf_event_overflow+0x52/0xf0 [56048.470499] handle_pmi_common+0x1db/0x270 [56048.470499] ? __set_pte_vaddr+0x32/0x50 [56048.470499] ? __native_set_fixmap+0x24/0x30 [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 [56048.470500] intel_pmu_handle_irq+0xbf/0x160 [56048.470501] perf_event_nmi_handler+0x2d/0x50 [56048.470501] nmi_handle+0x63/0x110 [56048.470501] default_do_nmi+0x4e/0x100 [56048.470502] do_nmi+0x128/0x190 [56048.470502] end_repeat_nmi+0x16/0x6a [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 [56048.470505] RAX: 0101 RBX: 0246 RCX: 001f [56048.470505] RDX: RSI: RDI: 94dcf5341dc0 [56048.470506] RBP: 94dcf534 R08: 0002 R09: 00029600 [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: 94dcf5341db0 [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15: 0003 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470508] [56048.470508] _raw_spin_lock_irqsave+0x32/0x40 [56048.470509] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470509] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470509] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470510] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470510] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470510] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470511] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470511] ? __schedule+0x280/0x700 [56048.470511] ? finish_wait+0x80/0x80 [56048.470512] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470512] kthread+0x112/0x130 [56048.470513] ? kthread_flush_work_fn+0x10/0x10 [56048.470513] ret_from_fork+0x1f/0x40 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/module/lpfc/version 0:14.0.390.2 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/modeldesc Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/fwrev 14.0.390.1, sli-4:2:c 14.0.390.1, sli-4:2:c [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/fc_host/host*/port_name 0x1090faf09459
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
PRs made for both Jammy and Kinetic. Kinetic was only missing the last 6
patches.
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Kinetic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Jeff Lane (bladernr)
--
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 for Ubuntu 22.04
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:
[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. 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
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
Hi, could you please update the summary with a test case that verifies
this fix?
** Description changed:
[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. These all are limited to
the lpfc driver itself, no patches to core code are requested.
[FIX]
- Please integrate the latest set of bug fix patches accepted in mkp/scsi
- 5.20/scsi-staging
+ 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 scsi: lpfc: Revise FDMI reporting of supported port speed for
trunk groups
d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
39a1a86b9da2 scsi: lpfc: Move MI module parameter check to handle dynamic
disable
d531d9874da8 scsi: lpfc: Remove unnecessary NULL pointer assignment for
ELS_RDF path
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
PR made for Jammy and Kinetic. Not a clean pick to Focal or Bionic, will need more work here. -- 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
Kim, I'm going to target this just to Bionic for now... I realize that
you said "all LTS" but Xenial and Trusty are comparatively ancient and
are no longer receiving non-security updates.
** Description changed:
+ IMPACT:
+ Old, circa 2002 chipsets have a bug: they don't go idle when they are
+ supposed to. So, a workaround was added to slow the CPU down and
+ ensure that the CPU waits a bit for the chipset to actually go idle.
+ This workaround is ancient and has been in place in some form since
+ the original kernel ACPI implementation.
+
+ But, this workaround is very painful on modern systems. The "inl()"
+ can take thousands of cycles (see Link: for some more detailed
+ numbers and some fun kernel archaeology).
+
+ First and foremost, modern systems should not be using this code.
+ Typical Intel systems have not used it in over a decade because it is
+ horribly inferior to MWAIT-based idle.
+
+ Despite this, people do seem to be tripping over this workaround on
+ AMD system today.
+
+ Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD
+ systems from tripping over the workaround. Remotely modern Intel
+ systems use intel_idle instead of this code and will, in practice,
+ remain unaffected by the dummy wait.
+
+ Reported-by: K Prateek Nayak
+ Suggested-by: Rafael J. Wysocki
+ Signed-off-by: Dave Hansen
+ Reviewed-by: Mario Limonciello
+ Tested-by: K Prateek Nayak
+ Link:
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
+ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com
+
+ FIX:
+
This issue pertains to all Zen based processors starting with
Naples(Zen1). All LTS releases will need this fix:
https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9
+
+ TESTCASE:
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Kinetic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Jeff Lane (bladernr)
--
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/1990985
Title:
ACPI: processor idle: Practically limit "Dummy wait" workaround to old
Intel systems
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
IMPACT:
Old, circa 2002 chipsets have a bug: they don't go idle when they are
supposed to. So, a workaround was added to slow the CPU down and
ensure that the CPU waits a bit for the chipset to actually go idle.
This workaround is ancient and has been in place in some form since
the original kernel ACPI implementation.
But, this workaround is very painful on modern systems. The "inl()"
can take thousands of cycles (see Link: for some more detailed
numbers and some fun kernel archaeology).
First and foremost, modern systems should not be using this code.
Typical Intel systems have not used it in over a decade because it is
horribly inferior to MWAIT-based idle.
Despite this, people do seem to be tripping over this workaround on
AMD system today.
Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD
systems from tripping over the workaround. Remotely modern Intel
systems use intel_idle instead of this code and will, in practice,
remain unaffected by the dummy wait.
Reported-by: K Prateek Nayak
Suggested-by: Rafael J. Wysocki
Signed-off-by: Dave Hansen
Reviewed-by: Mario Limonciello
Tested-by: K Prateek Nayak
Link:
https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/
Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com
FIX:
This issue pertains to all Zen based processors starting with
Naples(Zen1). All LTS releases will need this fix:
https://github.com/torvalds/linux/commit/
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
** Tags added: servcert-550 -- 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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: Confirmed Bug description: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 for Ubuntu 22.04
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Jammy)
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/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
New
Status in linux source package in Kinetic:
Confirmed
Bug description:
[IMPACT/Justification]
[FIX]
Please integrate the latest set of bug fix patches accepted in
mkp/scsi 5.20/scsi-staging
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 scsi: lpfc: Revise FDMI reporting of supported port speed for
trunk groups
d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
39a1a86b9da2 scsi: lpfc: Move MI module
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
I may have missed this one... I meant to add it if it's not already picked up in a different commit: ice: Fix not stopping Tx queues for VFs https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/intel/ice?id=b385cca47363316c6d9a74ae9db407bbc281f815 -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
additional patch to pick up that is supposed to help address the issue with MTUs ice: Fix interface being down after reset with link-down-on-close flag on https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git/commit/drivers/net/ethernet/intel?h=dev-queue=a2aa0cec547579cc137970c772ea82cbf5ee2608 So lets see if we can pull this in too, either with these patches or in a separate PR -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983656] Re: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf)
Update from upstream: Please check out the other patches below that were sent together with the one patch I listed in my previous reply. Cherry-picking patches can be challenging with ice driver from later kernels as new features and bug fixes are sent continuously in each kernel and the dependency can be tricky. 5951a2b9812dv5.16-rc6 iavf: Fix VLAN feature flags after VFR e6ba5273d4edv5.16-rc6 ice: Fix race conditions between virtchnl handling and VF ndo ops b385cca47363v5.16-rc6 ice: Fix not stopping Tx queues for VFs 0299faeaf8ebv5.16-rc6 ice: Remove toggling of antispoof for VF trusted promiscuous mode 1a8c7778bcdev5.16-rc6 ice: Fix VF true promiscuous mode Regarding the issue of changing MTU, it is a known one in ice driver and the team is actively working on a fix. I will share once it is ready to be sent Linux upstream. Another note, for E810 NICs, please recommend customers to update the NVM image on the NIC to the latest one if possible. Here is the latest one: https://www.intel.com/content/www/us/en/download/19626/non-volatile-memory-nvm-update-utility-for-intel-ethernet-network-adapters-e810-series-linux.html -- 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/1983656 Title: SR-IOV VFs no traffic flow and error on Intel E810 (ice / iavf) Status in linux package in Ubuntu: Incomplete Bug description: Virtual Machines with SR-IOV VFs from an Intel E810-XXV [8086:159b] get no traffic flow and produce error messages in both the host and guest during network configuration. Environment: Ubuntu OpenStack Focal-Ussuri with OVN Host Kernel: v5.15.0-41-generic 20.04 Focal-HWE Guest Kernels: v5.4.x Focal, v5.15.0-41-generic Jammy Host Error Messages: ice :98:00.1: VF 7 failed opcode 6, retval: -5 Guest Error Messages: iavf :00:05.0: PF returned error -5 (IAVF_ERR_PARAM) to our request 6 In the context of these errors "6" refers to the value of VIRTCHNL_OP_CONFIG_VSI_QUEUES It was found in these cases that the VM is able to successfully transmit packets but never receives any and the RX packet drop counters for the VF in "ip link" on the host increase equal to the RX packet count. There is a prior commit e6ba5273d4ede03d075d7a116b8edad1f6115f4d claiming to resolve this error in some cases. It is already included in the test kernel v5.15.0-41 and did not resolve the issue. These Virtual Machines do work with the Mainline v5.19 build on the host and it includes the following two VIRTCHNL_OP_CONFIG_VSI_QUEUES related commits that are not currently backported to v5.15 or any upstream stable kernel: 6096dae926a22e2892ef9169f582589c16d39639 ice: clear stale Tx queue settings before configuring [v5.18] be2af71496a54a7195ac62caba6fab49cfe5006c ice: Fix queue config fail handling [v5.19] Additionally during testing if we link down an interface and/or try to use netplan apply to start DHCP instead of manual configuration we triggered the following memory corruption bug: efe41860008e57fb6b69855b4b93fdf34bc42798 ice: Fix memory corruption in VF driver [v5.19] It appears that this ice/iavf driver is quite immature as many significant SR-IOV related fixes have landed in each of the recent kernel releases and we may need to consider pro-actively backporting more fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 for Ubuntu 22.04
** Description changed:
+ [IMPACT/Justification]
+
+
+ [FIX]
+
Please integrate the latest set of bug fix patches accepted in mkp/scsi
5.20/scsi-staging
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 scsi: lpfc: Revise FDMI reporting of supported port speed for
trunk groups
d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
39a1a86b9da2 scsi: lpfc: Move MI module parameter check to handle dynamic
disable
d531d9874da8 scsi: lpfc: Remove unnecessary NULL pointer assignment for
ELS_RDF path
76395c88d0af scsi: lpfc: Transition to NPR state upon LOGO cmpl if link down
or aborted
31e887864eb2 scsi: lpfc: Update fc_prli_sent outstanding only after
guaranteed IOCB submit
672d1cb40551 scsi: lpfc: Protect memory leak for NPIV ports sending PLOGI_RJT
577a942df3de scsi: lpfc: Fix null pointer dereference after failing to issue
FLOGI and PLOGI
3483a44bdfb4 scsi: lpfc: Clear fabric topology flag before
[Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988711
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
Status in linux package in Ubuntu:
Confirmed
Bug description:
Please integrate the latest set of bug fix patches accepted in
mkp/scsi 5.20/scsi-staging
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 scsi: lpfc: Revise FDMI reporting of supported port speed for
trunk groups
d6d45f67a111 scsi: lpfc: Fix call trace observed during I/O with CMF enabled
5295d19d4f97 scsi: lpfc: Correct CRC32 calculation for congestion stats
39a1a86b9da2 scsi: lpfc: Move MI module parameter check to handle dynamic
disable
d531d9874da8 scsi: lpfc: Remove unnecessary NULL pointer assignment for
ELS_RDF path
76395c88d0af scsi: lpfc: Transition to NPR state upon LOGO cmpl if link down
or aborted
31e887864eb2 scsi: lpfc:
