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.

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

[bcm syncd]: Wait initializing led_proc for 60 seconds #1863

Merged
merged 7 commits into from
Jul 18, 2018

Conversation

pavel-shirshov
Copy link
Contributor

- What I did
Added a pause 60 seconds before initializing led processor. Otherwise bcmcmd will fail with error -5 in some cases.

- How I did it
sleep 60

- How to verify it
Build an image and run on your DUT

- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)

@pavel-shirshov
Copy link
Contributor Author

retest this please

@qiluo-msft
Copy link
Collaborator

Seems this is a bcmcmd bug and you mitigate it from outside. Could you just add a comment?

## TODO: Otherwise bcmcmd will fail with error -5, remove this workaround after bug fixed

@pavel-shirshov
Copy link
Contributor Author

Hi Qi,

I think this is not a bug. It's a normal behavior just bcmcmd was run before the socket was ready to get connections. How bcmcmd could fix this? So I think it's better to wait as a quick fix. In the future we could add several attempts with exponentional backoff.

@pavel-shirshov
Copy link
Contributor Author

retest this please

@qiluo-msft qiluo-msft requested a review from lguohan July 18, 2018 01:16
@pavel-shirshov pavel-shirshov merged commit f033cbe into sonic-net:master Jul 18, 2018
@pavel-shirshov pavel-shirshov deleted the pavelsh/led_init branch July 18, 2018 16:38
yxieca added a commit that referenced this pull request Jul 19, 2018
* Wait initializing led_proc for 60 seconds. bcm sdk need time to be ready accept a connection
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants