Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2022118

Summary: rshim: update to 2.0.6 for BlueField-2 BMC support
Product: Red Hat Enterprise Linux 8 Reporter: Fabrizio <fdangelo>
Component: rshimAssignee: Dean Nelson <dnelson>
Status: CLOSED NOTABUG QA Contact: Jeff Bastian <jbastian>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.6CC: egarver, rvr
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-01-12 18:54:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Fabrizio 2021-11-10 19:14:04 UTC
Description of problem:

rshim 2.0.4 is not compatible with the newer BlueField-2 BMC cards.
There is an issue when using the rshim console to manage the card. No input/output is received when using minicom to the /dev/rshim0/console device.
Updating to 2.0.6 resolves this problem.

Comment 1 Dean Nelson 2021-11-12 00:52:27 UTC
(In reply to Fabrizio from comment #0)
> 
> rshim 2.0.4 is not compatible with the newer BlueField-2 BMC cards.
> There is an issue when using the rshim console to manage the card. No
> input/output is received when using minicom to the /dev/rshim0/console
> device.
> Updating to 2.0.6 resolves this problem.

I have previously updated RHEL-8.5's rshim to 2.0.5, which had changes for BlueField-2. And 8.6's rshim inherited that work. Would you mind trying out one of those to see if 2.0.5 provides the functionality you are looking for.

Upstream's 2.0.6 is still a work in progress. There were 2 commits added to 2.06-1, and 7 commits to 2.0.6-2. If 2.0.5 doesn't work for you, I can look into backporting the necessary commits from these.

Comment 2 Dean Nelson 2022-01-12 17:52:12 UTC
Was wondering if you've yet had a chance to try out rshim 2.0.5, to see if it satisfies your needs?
Upstream's 2.0.6 is still a work in progress.

Comment 3 Fabrizio 2022-01-12 18:12:48 UTC
(In reply to Dean Nelson from comment #2)
> Was wondering if you've yet had a chance to try out rshim 2.0.5, to see if
> it satisfies your needs?
> Upstream's 2.0.6 is still a work in progress.

Hi Dean, sorry about the delay.

Yes, using RHEL 8.5 the problem is solved as rshim 2.0.5 is sufficient for solving the problem I was facing.

At the time of filing the bug, we were working with specifically RHEL 8.4 but that is no longer the case.

Thanks for your help!