Ubuntu 18.04: LSI SAS93xx HBA detects incorrect bios version

[Amanda Gartner]

Under /sys/class/scsi_host/host*/ "version_bios" is reported as 16.00.00.00 instead of the correct bios version 08.35.04.00. The number that is reported under the version_bios is actually the version of the package used to flash the card.

Installer(SAS3FLSH) DOS:\sas3flash_dos_rel\sas3flash.exe 16.00.00.00

ProblemType: Bug

lsb_release -rd:
Description: Ubuntu 18.04 LTS
Release: 18.04

Uname: Linux

Uname -r: 4.15.0-20-generic

Date: Mon May 14 13:18 2018

Architecture: x86_64

Kernel driver in use: mpt3sas

Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc5

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1771181

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Amanda Gartner (amandagartner)]

Testing of the upstream kernel complete:

This bug occurred with 4.15.0-15-generic and after upgrade to 4.15.0-20-generic. I tested with 4.17.0-041700rc5-generic - The latest upstream kernel. The issue still occurred with the latest upstream kernel.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel