[Verification NOT DONE] ---- Jammy linux-bluefield/5.15.0-1076.78
Verified this bug on two machines
A30X - Bluefield-2
BF3220 - Bluefield-3
** The verification on the BF3220 (Bluefield-3) are successful, but the
verification on the A30X (Bluefield-2) has not passed **
** A possible regression could be observed on Bluefield-2 **
After issuing the command "ipmitool mc info", the Bluefield-2 board started
misbehaving, reporting on dmesg the following message
```
[ 1144.235475] ipmb-host 1-1011: ERROR: ipmb_send_request failed during ipmb
detection
[ 1144.243170] ipmb-host 1-1011: Unable to get response from slave device at
this time
[ 1144.250895] i2c i2c-1: new_device: Instantiated device ipmb-host at 0x11
```
Every 6 minutes. The I2C slave couldn't be accessed anymore after this step.
Multiple reboots have failed to solve the issue.
More information can be found in the following verification log.
[Verification log]
---------------------------------------------------------------------------------------------
********************************************************************************
* Verify MLXBF I2C driver builds and loads without errors on Bluefield 2 and
Bluefield 3
A30X: Bluefield-2
~$ lsmod | grep i2c_mlxbf
i2c_mlxbf 28672 0
**** Bluefield 2 -> PASSED
BF3220: Bluefield-3
~$ lsmod | grep i2c_mlxbf
i2c_mlxbf 28672 0
**** Bluefield 3 -> PASSED
********************************************************************************
* Verify I2C block read of a device that requires repeated start conditions
succeeds using the following command: "i2cget -y <bus> <target> <reg> i <bytes>"
A30X Bluefield-2:
sudo i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x08-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: 10 UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
**** Bluefield-2 -> PARTIALLY PASSED (See note below)
BF3220 Bluefield-3:
sudo i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x08-0x77.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: 10 UU -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
**** Bluefield-3 -> PARTIALLY PASSED (See note below)
*******NOTES********
**** Can't do more than this, unknown which address should be used to read from
I2C.
Considering partially passed.
*******************************************************************************
* Verify IPMB communication with BMC to regression test general I2C behavior.
Used the following command which will result in several I2C transactions:
"ipmitool mc info".
A30X: Bluefield-2
~$ sudo ipmitool mc info
Device ID : 1
Device Revision : 1
Firmware Revision : 2.08
IPMI Version : 2.0
Manufacturer ID : 33049
Manufacturer Name : Unknown (0x8119)
Product ID : 2 (0x0002)
Product Name : Unknown (0x2)
Device Available : yes
Provides Device SDRs : yes
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
Chassis Device
Aux Firmware Rev Info :
0x03
0x00
0x27
0x00
***WARNING - Regression? ***
After the command, in dmesg I started getting the following message
constantly roughly every 6 minutes
```
[ 216.716143] ipmb-host 1-1011: ERROR: ipmb_send_request failed during ipmb
detection
[ 216.723853] ipmb-host 1-1011: Unable to get response from slave device at
this time
[ 216.731579] i2c i2c-1: new_device: Instantiated device ipmb-host at 0x11
```
and can't speak with I2C device anymore.
On sudo ipmitool mc info I get
```
$ sudo ipmitool mc info
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such
file or directory
```
The device still exists in the file system
```
~$ ls /dev/ipmi0 -lah
crw------- 1 root root 508, 0 Sep 4 12:16 /dev/ipmi0
```
******
**** Bluefield 2: PASSED then FAILED (See Warning Above)
BF3220: Bluefield-3
~$ sudo ipmitool mc info
Device ID : 1
Device Revision : 1
Firmware Revision : 23.04
IPMI Version : 2.0
Manufacturer ID : 33049
Manufacturer Name : Unknown (0x8119)
Product ID : 4 (0x0004)
Product Name : Unknown (0x4)
Device Available : yes
Provides Device SDRs : yes
Additional Device Support :
Sensor Device
SDR Repository Device
SEL Device
FRU Inventory Device
IPMB Event Receiver
Chassis Device
Aux Firmware Rev Info :
0x10
0x03
0x00
0x00
**** Bluefield 3: PASSED
---------------------------------------------------------------------------------------------
Marking as NOT DONE
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2119651
Title:
i2c-mlxbf: Replace SAUCE patches with upstream content
Status in linux-bluefield package in Ubuntu:
New
Status in linux-bluefield source package in Jammy:
New
Bug description:
[Impact]
The BlueField I2C driver in Jammy and Noble repos consists of several SAUCE
patches.
There are now equivalent upstream patches that should be used instead.
[Fix]
* Revert SAUCE patches and then cherry-pick upstream patches that implement
the same functionality
* Include missing patches that were added upstream
[Test Case]
* Verify MLXBF I2C driver builds and loads without errors on Bluefield 2 and
Bluefield 3.
* Verify I2C block read of a device that requires repeated start conditions
succeeds using the following command: "i2cget -y <bus> <target> <reg> i
<bytes>".
* Verify IPMB communication with BMC to regression test general I2C behavior.
Used the following command which will result in several I2C transactions:
"ipmitool mc info".
[Regression Potential]
Low potential, as upstream commits have been tested and vetted by
upstream maintainers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2119651/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
