Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NA #18144

Closed
Alicia-Zhu opened this issue Feb 21, 2024 · 1 comment
Closed

NA #18144

Alicia-Zhu opened this issue Feb 21, 2024 · 1 comment
Assignees
@adyeung
Labels
BRCM Triaged this issue has been triaged

Comments

@Alicia-Zhu
Copy link

Alicia-Zhu commented Feb 21, 2024 •
edited
Loading

No description provided.

@arlakshm arlakshm added Triaged this issue has been triaged BRCM labels Feb 28, 2024
@adyeung
Copy link
Collaborator

adyeung commented Feb 28, 2024

@Alicia-Zhu In the earlier description as of 2/27, you mentioned you are able to resolve with "revised sai", did you make changes to SAI or did you create a config.bcm for your target platform? Please share more info about the change.

"With our revised SAI code, the syncd container no longer experiences abnormal exits. Attached are two sets of syslog files corresponding to the SONiC version with the community SAI and our revised SONiC version."

@Alicia-Zhu Alicia-Zhu changed the title Issue with Community Broadcom's SAI Support for the Tomahawk 5 Chipset NA Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adyeung adyeung

Labels
BRCM Triaged this issue has been triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@adyeung @arlakshm @Alicia-Zhu