Loading...
Loading...
Document VersionRelease DateDetails304/22/2018Updated Resolution, perform either of the following steps: RoCE feature is used or RoCE feature is not used.201/23/2018Updated information that the driver component has been removed from SPP version 2017.10 (or later).109/20/2017Original Document Release.On an HPE Gen10 system with any of the network adapters listed in the Scope section below, SUSE Linux Enterprise Server 11 SP4 with a kISO may not boot after installing any driver after installing the HPE Broadcom NetXtreme-E RoCE Kernel Driver for SUSE Linux Enterprise Server 11 SP4 (bnxt_re). This will occur with the Service Pack for ProLiant (SPP) Version 2017.07.0 (or later) using the online method, or if the HPE ProLiant Gen10 Smart Array Controller (64-bit) Driver for SUSE Linux Enterprise Server 11 (smartpqi) or any driver is installed after installing the bnxt_re.Note: The driver component has been removed from SPP version 2017.10 (or later); however, this occurs with SPP version 2017.07.0, and SPP version 2017.07.1, or after installing any driver after bnxt_re.Any driver that is installed after the bnxt_re driver will not load during boot (does not load with modprobe) and display messages similar to the following:[ 0.000000] ACPI: X2APIC (apic_id[0x1d]uid[0x1d] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x21]uid[0x21] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x23]uid[0x23] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x25]uid[0x25] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x27]uid[0x27] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x29]uid[0x29] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x2b]uid[0x2b] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x2d]uid[0x2d] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x31]uid[0x31] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x33]uid[0x33] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x35]uid[0x35] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x37]uid[0x37] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x39]uid[0x39] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x3b]uid[0x3b] enabled)[ 0.000000] ACPI: X2APIC (apic_id[0x3d]uid[0x3d] enabled)[ 0.000000] ACPI: X2APIC_NMI (uid[0x00] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x01] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x02] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x03] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x04] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x05] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x06] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x07] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x08] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x09] highlevel lint[0x1])[ 0.000000] ACPI: X2APIC_NMI (uid[0x0a] highlevel lint[0x1])[ 0.000000] ACPI:X2APIC_NMI (uid[............................Could notfind/dev/disk/by-id/scsi-3600508b1001c12b1acc8ccc81cf6dd22-part3. Want meto fallback to /dev/disk/by-id/scsi-3600508b1001c12b1acc8ccc81cf6dd22-part3?(Y/n)Waiting for device/dev/disk/by-id/scsi-3600508b1001c12b1acc8ccc81cf6dd22-part3 to appear:Warning messages similar to the following are displayed in the Smart Update Manager (SUM) log or displayed on the screen outside the SPP (standalone) when any driver is installed after HPE Broadcom NetXtreme-E RoCE Kernel Driver for SUSE Linux Enterprise Server 11 SP4 (bnxt_re):Source: smartpqi-kmp-default-1.0.4-101.sles11sp4.x86_64.rpmVersion: 1.0.4-101.sles11sp4Log Date: 8/15/17 7:07 AMPreparing... ##################################################smartpqi-kmp-default ##################################################WARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_umem_releaseWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.koneeds unknown symbol rdma_addr_find_dmac_by_grhWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.koneeds unknown symbol backport_pcie_capability_read_wordWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_modify_qp_is_okWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_unregister_deviceWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_register_deviceWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_umem_page_countWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_dispatch_eventWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_umem_getWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_dealloc_deviceWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_alloc_deviceWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.kodisagrees about version of symbol ib_query_gidWARNING: //lib/modules/3.0.101-97-default/weak-updates/updates/bnxt_re.koneeds unknown symbol backport_dependency_symbolWarning: /lib/modules/3.0.101-97-default is inconsistentWarning: weak-updates symlinks might not be createdThis occurs due to the bnxt_re that has some unresolved symbols and disagrees about the symbol versions that depend on the external Community OpenFabrics Enterprise Distribution (OFED). When the bnxt_re driver is installed first, the symbol table is created with the unresolved symbols. If any driver is installed after the bnxt_re, the SUSE Linux Enterprise Server 11 SP4 tool weak-modules2 does not create weak-updates symlink for other drivers therefore, the drivers that are installed after bnxt_re driver do not load automatically during boot. In the above example, the HPE Smart Array driver (smartpqi) was not loaded and SUSE Linux Enterprise Server 11 SP4 does not identify the root partition and does not boot.
Any HPE Gen10 system running SUSE Linux Enterprise Server 11 SP4 with any of the network adapters listed below installing the bnxt_re driver:HPE Ethernet 10Gb 2-port 535FLR-T AdapterHPE Ethernet 10Gb 2-port 535T AdapterHPE Ethernet 10/25Gb 2-port 631FLR-SFP28 AdapterHPE Ethernet 10/25Gb 2-port 631SFP28 Adapter
Perform either of the following:Option: RoCE feature is not usedWhile deploying components using the SPP and if the RoCE feature for the network cards listed in the scope section is not used, deselect the HPE Broadcom NetXtreme-E RoCE Kernel Driver for SUSE Linux Enterprise Server 11 SP4 (bnxt_re) from the deployment list.While deploying the components outside of SPP (standalone), do not install the HPE Broadcom NetXtreme-E RoCE Kernel Driver for SUSE Linux Enterprise Server 11 SP4 (bnxt_re) if the RoCE feature is not used for the network adapters listed in the scope section above.OROption: RoCE feature is usedWhile deploying the components using SPP or outside SPP (standalone) and if the RoCE feature is used for the network cards listed in the scope section above, perform the following:Install all the drivers excluding the HPE Broadcom NetXtreme-E RoCE Kernel Driver for SUSE Linux EnterpriseServer 11 SP4 (bnxt_re).Install the OpenFabrics Enterprise Distribution, version 3.18-2 available at the below URL.http://downloads.openfabrics.org/downloads/OFEDNote:The link above will take you outside the HPE website. HPE is not responsible for content outside of the HPE website.Install the HPEBroadcom NetXtreme-E RoCE Kernel Driver for SUSE Linux Enterprise Server 11 SP4 (bnxt_re).If the HPE Broadcom NetXtreme-E RoCEKernel Driver for SUSE Linux Enterprise Server 11 SP4 (bnxt_re) and OFED are already installed, to update the driver, uninstall both the components i.e. bnxt_re and OFED and then follow Step 1 through Step 3 listed above.Note:If this has already occurred and SUSE Linux Enterprise Server 11 SP4 does not boot, reinstall the OS and follow the steps as listed above based on the options of using the RoCE feature or not.Note 1:If any driver does not load during boot or using modprobe then first uninstall the corresponding driver component,bnxt_re and OFED if it is installed. Then follow the workaround steps as mentioned above based on the options of using the RoCE feature or not.RECEIVE PROACTIVE UPDATES: Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL:Proactive Updates Subscription Form.NAVIGATION TIP: For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to theNavigation Tips document.SEARCH TIP: For hints on locating similar documents on HPE.com, refer to theSearch Tips Document.To search for additional advisories related to Linux, use the following search string:+Advisory +ProLiant -"Software and Drivers" +Linux
Operating Systems Affected:Linux - SuSE Linux Enterprise Server 11
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.