Bug 248352 - mfi: remove raid map sync functionality
Summary: mfi: remove raid map sync functionality
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.1-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2020-07-29 19:25 UTC by Chandrakanth Patil
Modified: 2020-07-31 16:00 UTC (History)
4 users (show)

See Also:

This patch removes raid map sync functionality from mfi driver (7.68 KB, patch)
2020-07-29 19:25 UTC, Chandrakanth Patil
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Chandrakanth Patil 2020-07-29 19:25:23 UTC
Created attachment 216866 [details]
This patch removes raid map sync functionality from mfi driver

We have found a raid map sync failure in invader (device id: 5d) as soon as the <mfi> driver is loaded. This is due to the failure in fetching updated raid map from the firmware as raid map is logically unsupported in driver reason being driver is not getting any raid map data as part of MFI_DCMD_LD_MAP_GET_INFO instead it is getting the config seq number as part of MFI_DCMD_LD_GET_LIST DCMD resulted in raid map sync failure. Below is the firmware log snippet where there is a config sequence number mismatch between driver and firmware:

C0:ld sync: non-matching seqNums 1
C0:ld sync: 01 unsync'd lds remaining

This issue applies to the controllers which has a raid map support like Thunderbolt (device id: 5b) invader (device id: 5d) and fury (device id: 5f) controllers and it is not applicable to till Liberator (Gen1 and Gen2) as these controllers don't have a raid map support.

Hence, We propose to remove the raid map sync functionality from <mfi> driver. I have attached the sample patch covers raid map sync functionality removal part and hasn't covered any test cases and it is just for reference.

If it looks feasible to remove raid map sync support from driver then please consider my patch.

Note: we are not seeing this issue with <mrsas> driver.