LSI 9305 weird messages

dorinxev

Active Member
Apr 3, 2019
21
3
43
57
Hi,
I have a proxmox server (8.1) with an LSI 3905-16i cards. There are 8 disks attached to this HBA and I've created a ZFS pool on those disks

I've created a virtual disk from this pool and shared it with a VM which runs proxmox backup server.

Everything runs fine, but the syslog message is flooded with the same messages each time the pool on the host (including the virtual disk) is being accessed:

Code:
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)
May 01 11:30:51 prox kernel: mpt3sas_cm0: log_info(0x30030109): originator(IOP), code(0x03), sub_code(0x0109)

I have checked few time: Before and after those messages, I don't see any error on the syslog or the journal, and the pool shows no errors.

Any suggestions?
 
After further investigation and testing, it seems a kernel issue, so upgrading to the latest (6.8.4 at the time of writing this reply) - the issue is being resolved.