-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[OS][master][202012] SONiC not start well in Celestica E1031 #6602
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
Comments
If anything information need collect from my side, feel free to share the command and I will update the ticket. |
Additional information, can be reproduce on both 202012 and master image After install the image, we can login in to the SONiC.
|
@119064273 I am not seen any error log related to SAI_OBJECT_TYPE_PORT. There are some log mentioned container starting fail (around Line 3682).
|
Celestica report that they couldn't repro this issue with newest master branch image. |
Couldn't repro with master 616:
|
Couldn't repro with 202012-57
|
The issue not observed, for the additional issue(bootloop), i opened a new issue: #7133 |
@Blueve I see the docker of "swss" not up ? is it right ? |
Most dockers are failed with same reason |
@119064273 |
Fix sonic-net/sonic-buildimage#6602 This change is add new dps200 PSU module driver for fix this issue sonic-net/sonic-buildimage#6602 I have try to use the generic pmbus driver, but it not support. [ 5733.051510] pmbus 12-005a: Chip identification failed [ 5733.112598] i2c i2c-12: new_device: Instantiated device pmbus at 0x5a [ 5748.459851] pmbus 13-005b: Chip identification failed [ 5748.520975] i2c i2c-13: new_device: Instantiated device pmbus at 0x5b
Why I did it Fix issues below. #7133 #6602 So, remove the dps200 driver from the platform-specific driver. Then, add the dps200 module driver to the Linux kernel tree. How I did it Remove the dps200 driver from the platform-specific driver and add the dps200 module driver to the Linux kernel. How to verify it Build an image with sonic-net/sonic-linux-kernel#207 Then, install to the Haliburton.
Fix sonic-net/sonic-buildimage#6602 This change is add new dps200 PSU module driver for fix this issue sonic-net/sonic-buildimage#6602 I have try to use the generic pmbus driver, but it not support. [ 5733.051510] pmbus 12-005a: Chip identification failed [ 5733.112598] i2c i2c-12: new_device: Instantiated device pmbus at 0x5a [ 5748.459851] pmbus 13-005b: Chip identification failed [ 5748.520975] i2c i2c-13: new_device: Instantiated device pmbus at 0x5b
…-net#7247) Why I did it Fix issues below. sonic-net#7133 sonic-net#6602 So, remove the dps200 driver from the platform-specific driver. Then, add the dps200 module driver to the Linux kernel tree. How I did it Remove the dps200 driver from the platform-specific driver and add the dps200 module driver to the Linux kernel. How to verify it Build an image with sonic-net/sonic-linux-kernel#207 Then, install to the Haliburton.
Why I did it Fix issues below. #7133 #6602 So, remove the dps200 driver from the platform-specific driver. Then, add the dps200 module driver to the Linux kernel tree. How I did it Remove the dps200 driver from the platform-specific driver and add the dps200 module driver to the Linux kernel. How to verify it Build an image with sonic-net/sonic-linux-kernel#207 Then, install to the Haliburton.
…-net#7247) Why I did it Fix issues below. sonic-net#7133 sonic-net#6602 So, remove the dps200 driver from the platform-specific driver. Then, add the dps200 module driver to the Linux kernel tree. How I did it Remove the dps200 driver from the platform-specific driver and add the dps200 module driver to the Linux kernel. How to verify it Build an image with sonic-net/sonic-linux-kernel#207 Then, install to the Haliburton.
Description
System required dockers not start as expect in Celestica E1031.
Steps to reproduce the issue:
show version
sudo docker ps
after a few minutesRun above test for
SONiC.202012.13-c8b3a709
andSONiC.master.565-e616a329
Describe the results you received:
Test Result for
SONiC.202012.13-c8b3a709
Show version
Test Result for
SONiC.master.565-e616a329
Describe the results you expected:
All SONiC docker should start properly.
Additional information you deem important (e.g. issue happens only occasionally):
Ying Xie mentioned this issue might be the SAI problem with Celestica.
The text was updated successfully, but these errors were encountered: