topic Re: ICX7150 - c12P fails to boot after Power Trip - Tried recovering but still failing. in RUCKUS Support for Lennar Homes

ICX7150 - c12P fails to boot after Power Trip - Tried recovering but still failing.

ShanPSP — Tue, 26 Dec 2023 02:25:28 GMT

Hi Admin,

My ICX7150 switch failed with SYST amber light on. Tried updating primary, secondary and uboot. Post update when I do the reset, I continue to get the below message on the console. Pls help me.

[BrcdSoftlockup]: BUG: soft lockup - CPU#0 stuck for 89s! [mount:601]

000066a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

Re: ICX7150 - c12P fails to boot after Power Trip - Tried recovering but still failing.

Imran_ruckus — Tue, 26 Dec 2023 13:34:03 GMT

Hi @ShanPSP

Greetings!!!

Thank you for contacting RUCKUS Lennar Home Community.

I hope you are doing well!!!

Thank you for the information you shared.

As per the case description, I understand that your RUCKUS setup is not working, and you are trying to software recover on the Switch.

Could you please share a screenshot of the error and a picture of the software recovery cable connections between the Switch and the laptop?

Before uploading the photos please log in to the RUCKUS account and you can upload the image.

Please let me know the answers to ALL the above queries or let me know if you have any queries in this regard.

Thank you again for your patience and understanding.

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.

Re: ICX7150 - c12P fails to boot after Power Trip - Tried recovering but still failing.

ShanPSP — Tue, 26 Dec 2023 15:05:28 GMT

Hi Imran, Thank you for the support. I was successfully able to console into the switch. Looks like my software recovery. has worked. But I get the below error message when I boot the switch. I get the warning messages as below. Also Now there are no Amber lights. Now what's the next step after the software recovery to configure the switch.

Hash value: c027c7ec

## Loading kernel from FIT Image at 70000200 ...

Using 'conf@1' configuration

Trying 'kernel@2' kernel subimage

Description: Ruckus Linux MN VER=08.0.90k

Type: Kernel Image

Compression: lzma compressed

Data Start: 0x7024fcd0

Data Size: 2401842 Bytes = 2.3 MiB

Architecture: ARM

OS: Linux

Load Address: 0x61008000

Entry Point: 0x61008000

Hash algo: crc32

Hash value: c027c7ec

Verifying Hash Integrity ... crc32+ OK

## Loading ramdisk from FIT Image at 70000200 ...

Using 'conf@1' configuration

Trying 'ramdisk@1' ramdisk subimage

Description: Ramdisk -rootfs

Type: RAMDisk Image

Compression: lzma compressed

Data Start: 0x704a0cb8

Data Size: 23843872 Bytes = 22.7 MiB

Architecture: ARM

OS: Linux

Load Address: 0x00000000

Entry Point: 0x00000000

Hash algo: crc32

Hash value: 1e3b36e9

Verifying Hash Integrity ... crc32+ OK

## Loading fdt from FIT Image at 70000200 ...

Using 'conf@1' configuration

Trying 'fdt@3' fdt subimage

Description: Flattened Device Tree blob

Type: Flat Device Tree

Compression: uncompressed

Data Start: 0x7049ea60

Data Size: 8607 Bytes = 8.4 KiB

Architecture: ARM

Hash algo: crc32

Hash value: 6fc9a37b

Verifying Hash Integrity ... crc32+ OK

Loading fdt from 0x7049ea60 to 0x65008000

Booting using the fdt blob at 0x65008000

Uncompressing Kernel Image ... OK

Using Device Tree in place at 65008000, end 6500d19e

Starting kernel ...

Mounting file system...

booting with 4.4 kernel

NAND Type: Micron NAND 2GiB (x 1)

PLATFORM MN

dd cmd: UBI

Hash value: c027c7ec

## Loading kernel from FIT Image at 70000200 ...

Using 'conf@1' configuration

Trying 'kernel@2' kernel subimage

Description: Ruckus Linux MN VER=08.0.90k

Type: Kernel Image

Compression: lzma compressed

Data Start: 0x7024fcd0

Data Size: 2401842 Bytes = 2.3 MiB

Architecture: ARM

OS: Linux

Load Address: 0x61008000

Entry Point: 0x61008000

Hash algo: crc32

Hash value: c027c7ec

Verifying Hash Integrity ... crc32+ OK

## Loading ramdisk from FIT Image at 70000200 ...

Using 'conf@1' configuration

Trying 'ramdisk@1' ramdisk subimage

Description: Ramdisk -rootfs

Type: RAMDisk Image

Compression: lzma compressed

Data Start: 0x704a0cb8

Data Size: 23843872 Bytes = 22.7 MiB

Architecture: ARM

OS: Linux

Load Address: 0x00000000

Entry Point: 0x00000000

Hash algo: crc32

Hash value: 1e3b36e9

Verifying Hash Integrity ... crc32+ OK

## Loading fdt from FIT Image at 70000200 ...

Using 'conf@1' configuration

Trying 'fdt@3' fdt subimage

Description: Flattened Device Tree blob

Type: Flat Device Tree

Compression: uncompressed

Data Start: 0x7049ea60

Data Size: 8607 Bytes = 8.4 KiB

Architecture: ARM

Hash algo: crc32

Hash value: 6fc9a37b

Verifying Hash Integrity ... crc32+ OK

Loading fdt from 0x7049ea60 to 0x65008000

Booting using the fdt blob at 0x65008000

Uncompressing Kernel Image ... OK

Using Device Tree in place at 65008000, end 6500d19e

Starting kernel ...

Mounting file system...

booting with 4.4 kernel

NAND Type: Micron NAND 2GiB (x 1)

PLATFORM MN

dd cmd: UBI

Starting kernel ...

Mounting file system...

booting with 4.4 kernel

NAND Type: Micron NAND 2GiB (x 1)

PLATFORM MN

dd cmd: UBI

Config partition mounted

Resource partition is mounted!!

Processing packages from primary partition

Incompatible version of booted application and packages stored in UFI image

Error, cannot install packages

Uninstalling old packages if any..

Error in processing packages

Package installation is incomplete, related functionalities may not be available

dhcpd executable file is not present.

Starting up system statistics daemon...

Starting systatsd done

Log Level 7: Daemonized systatsd

Systatsd Logging Env is not set, initializing loglevel to: 7

Setting connection to systemlogger

Starting up health monitor daemon...

Starting hmond done

Hmond Logging Env is not set, initializing loglelvel to: I

Setting connection to systemlogger

Backup is fine

Kernel crashdump is disabled.

dma_mem_base: 0x96000000, dma_mem_len: 0x8000000, warm_mem_base: 0x9f500000, warm_mem_len: 0xb00000

Creating TUN device

Starting TPM Infra

Group tss and User tss created

kernel.hostname = localhost

hostname set to localhost

Starting TCSD Daemon

TCSD Up and Running

Enabling time stamp

==========================================================

========== WARNING: Boot-monitor version mismatch!!! ==========

========== Please use "show boot-monitor" command for details ==========

==========================================================================

======================================================================================

=============== WARNING: FI image is not booted from UFI!!! ===============

====== Please download UFI image and reboot the system for full functionality ======

======================================================================================

Re: ICX7150 - c12P fails to boot after Power Trip - Tried recovering but still failing.

Imran_ruckus — Tue, 26 Dec 2023 15:22:52 GMT

Hi @ShanPSP

Thank you for the information you shared.

On your switch while it's plugged into the outlet, do you see any lights on? (Amber or green) Please let us know which lights are on. (Please refer to the below picture and share a picture of the same, showing the light status and the FULL Switch panel cable connections to the Switch ports)

Please help us with pictures of your ICX-7150-C12P Switch showing the status of the lights and cable connections to the Switch ports.

Before uploading the photos please log in to the RUCKUS account and you can upload the image.

Please let me know the answer to the above query or let me know if you have any queries in this regard.

Thank you again for your patience and understanding.

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.

Re: ICX7150 - c12P fails to boot after Power Trip - Tried recovering but still failing.

ShanPSP — Tue, 02 Jan 2024 21:31:35 GMT

Hi Imran, yes I was able to solve the problem. Thank you for all the support.

Re: ICX7150 - c12P fails to boot after Power Trip - Tried recovering but still failing.

Imran_ruckus — Wed, 03 Jan 2024 12:19:44 GMT

Hi @ShanPSP

Greetings!!!

Thank you for the response and the update.

Great!!! Good to know that the issue is now resolved.

We appreciate your time and patience on this case.

Thank you again for contacting RUCKUS Lennar Home Community and feel free to contact us for future queries.

Have a great day ahead!!!

Best regards,

Imran Sanadi

RUCKUS Lennar Home Community.