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

[master][202012] E1031 Bootloop after first cold reboot #7133

Closed
Blueve opened this issue Mar 24, 2021 · 1 comment
Closed

[master][202012] E1031 Bootloop after first cold reboot #7133

Blueve opened this issue Mar 24, 2021 · 1 comment
Labels
Bug 🐛 Issue for 202012 Master Branch Quality Platform: Celestica

Comments

@Blueve
Copy link
Contributor

Blueve commented Mar 24, 2021

Description

Observed bootloop after first cold reboot.
Test with below images and all of them are encounter this issue.

  • master-616
  • master-565
  • 202012-57
  • 202012-13

Steps to reproduce the issue:

  1. Install OS from ONIE
  2. Run sudo reboot

Describe the results you received:

Bootloop

Describe the results you expected:

Reboot and enter SONiC cli

Output of show version:

admin@sonic:~$ show version

SONiC Software Version: SONiC.master.616-8f83b33e
Distribution: Debian 10.8
Kernel: 4.19.0-12-2-amd64
Build commit: 8f83b33e
Build date: Sat Mar 20 11:09:26 UTC 2021
Built by: johnar@jenkins-worker-4

Platform: x86_64-cel_e1031-r0
HwSKU: Celestica-E1031-T48S4
ASIC: broadcom
ASIC Count: 1
Traceback (most recent call last):
  File "/usr/local/bin/decode-syseeprom", line 18, in <module>
    import sonic_platform
ModuleNotFoundError: No module named 'sonic_platform'
Serial Number: 
Uptime: 06:56:22 up 10 min,  1 user,  load average: 4.69, 7.83, 4.11

Docker images:
REPOSITORY                    TAG                   IMAGE ID            SIZE
docker-syncd-brcm             latest                4bedb764fd70        681MB
docker-syncd-brcm             master.616-8f83b33e   4bedb764fd70        681MB
docker-snmp                   latest                9870bfea10c6        438MB
docker-snmp                   master.616-8f83b33e   9870bfea10c6        438MB
docker-teamd                  latest                8988ce642831        408MB
docker-teamd                  master.616-8f83b33e   8988ce642831        408MB
docker-nat                    latest                fa5cabfd53a4        411MB
docker-nat                    master.616-8f83b33e   fa5cabfd53a4        411MB
docker-router-advertiser      latest                11ab5e4f5bbc        398MB
docker-router-advertiser      master.616-8f83b33e   11ab5e4f5bbc        398MB
docker-platform-monitor       latest                dc7d2cdabeb2        606MB
docker-platform-monitor       master.616-8f83b33e   dc7d2cdabeb2        606MB
docker-lldp                   latest                270c6c69d47c        438MB
docker-lldp                   master.616-8f83b33e   270c6c69d47c        438MB
docker-dhcp-relay             latest                f4e5c03e71c1        405MB
docker-dhcp-relay             master.616-8f83b33e   f4e5c03e71c1        405MB
docker-sonic-mgmt-framework   latest                25e5cb2ad875        616MB
docker-sonic-mgmt-framework   master.616-8f83b33e   25e5cb2ad875        616MB
docker-orchagent              latest                66c818b0409b        427MB
docker-orchagent              master.616-8f83b33e   66c818b0409b        427MB
docker-macsec                 latest                ac5b0e4e1bc2        412MB
docker-macsec                 master.616-8f83b33e   ac5b0e4e1bc2        412MB
docker-sonic-telemetry        latest                c64fffe86092        487MB
docker-sonic-telemetry        master.616-8f83b33e   c64fffe86092        487MB
docker-fpm-frr                latest                41f14f5d42fb        427MB
docker-fpm-frr                master.616-8f83b33e   41f14f5d42fb        427MB
docker-sflow                  latest                4e953e0d66a8        409MB
docker-sflow                  master.616-8f83b33e   4e953e0d66a8        409MB
docker-database               latest                b9f3ba43113e        398MB
docker-database               master.616-8f83b33e   b9f3ba43113e        398MB

Additional information you deem important (e.g. issue happens only occasionally):

Celestica has identified this issue were caused by DSP driver and following up.
@Blueve Blueve mentioned this issue Mar 24, 2021
Closed
@Blueve
Copy link
Contributor Author

Blueve commented Apr 7, 2021

Fix: sonic-net/sonic-linux-kernel#207

@schobtr schobtr mentioned this issue Apr 7, 2021
Merged
4 tasks
yxieca pushed a commit that referenced this issue May 9, 2021
@schobtr
[Haliburton-Celestica] Use psu driver dps200 from Linux kernel (#7247)
da7c80d 
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.
raphaelt-nvidia pushed a commit to raphaelt-nvidia/sonic-buildimage that referenced this issue May 23, 2021
@schobtr @raphaelt-nvidia
[Haliburton-Celestica] Use psu driver dps200 from Linux kernel (sonic…
f06a3ad 
…-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.
qiluo-msft pushed a commit that referenced this issue May 24, 2021
@schobtr @qiluo-msft
[Haliburton-Celestica] Use psu driver dps200 from Linux kernel (#7247)
86e78d2 
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.
carl-nokia pushed a commit to carl-nokia/sonic-buildimage that referenced this issue Aug 7, 2021
@schobtr
[Haliburton-Celestica] Use psu driver dps200 from Linux kernel (sonic…
177cdd8 
…-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.
@Blueve Blueve closed this as completed Aug 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug 🐛 Issue for 202012 Master Branch Quality Platform: Celestica
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Blueve