topic Re: PANIC: The 0 is not a supported platform, cpu_reset called on cpu#0 in ONTAP Hardware

PANIC: The 0 is not a supported platform, cpu_reset called on cpu#0

aaronswtelogis — Wed, 03 Feb 2016 19:34:07 GMT

Hello

Inherited a FAS3210. Seeing the following:

Phoenix TrustedCore(tm) Server
Copyright 1985-2006 Phoenix Technologies Ltd.
All Rights Reserved
BIOS version: 5.1.1
Portions Copyright (c) 2007-2011 NetApp, Inc. All Rights Reserved

CPU = 1 Processors Detected, Cores per Processor = 2
Intel(R) Xeon(R) CPU E5220 @ 2.33GHz
Testing RAM
512MB RAM tested
5120MB RAM installed
6144 KB L2 Cache
System BIOS shadowed
USB 2.0: MICRON eUSB DISK
BIOS is scanning PCI Option ROMs, this will take few seconds...
+++++++++++++++++++

CPU Type: Intel(R) Xeon(R) CPU E5220 @ 2.33GHz

Starting AUTOBOOT press Ctrl-C to abort...
Loading X86_64/freebsd/image1/kernel:0x100000/3401320 0x53f000/3229520 0x853750/1227824 Entry at 0x80148a80
Loading X86_64/freebsd/image1/platform.ko:0x980000/569180 0xab4480/535320 0xa0af60/17256 0xb36f98/29808 0xa0f2c8/1360 0xb3e408/4080 0xa0f818/54268 0xa1cc18/71003 0xa2e178/1504 0xb3f3f8/4512 0xa2e758/256 0xb40598/768 0xa2e858/968 0xb40898/2904 0xa2ec20/112 0xb413f0/336 0xa2eca0/137088 0xb41540/142200 0xa50420/425 0xa75c60/8377 0xab4392/237 0xa77d20/126120 0xa969c8/121290
NetApp Data ONTAP 8.0.2P4 7-Mode

PANIC: The 0 is not a supported platform

version: NetApp Release 8.0.2P4: Tue Nov 15 16:16:47 PST 2011
cpuid = 0
Uptime: 1s

The operating system has halted.
Please press any key to reboot.

System halting...
cpu_reset called on cpu#0

Any idea for direction? I want to reseat the RAM. All shelves are unplugged from controllers, still get the same error.

thanks

Re: PANIC: The 0 is not a supported platform, cpu_reset called on cpu#0

ritusangha — Wed, 03 Feb 2016 20:00:16 GMT

If filer is on LOADER prompt, what does "printenv" show you?

You should see Model or other information. ( I bet its not there)

You should open a P1 Support case.

It might be a hardware failure/ bug.

Re: PANIC: The 0 is not a supported platform, cpu_reset called on cpu#0

aaronswtelogis — Wed, 03 Feb 2016 21:10:02 GMT

greetings!

I reseated all DIMMs in either controller, the error is gone.

thank you for the reply, this is solved.

hope to get a reply as well on cabling issue. same chassis, trying to figure out what the cabling should be fits the circle->square priciple.

thanks again

Re: PANIC: The 0 is not a supported platform, cpu_reset called on cpu#0

econde — Fri, 01 Dec 2017 17:57:07 GMT

Hola, tengo el mismo problema. Crees que sea físico e tema? qué debo hacer con los DIMMs?

Hice netboot según estos pasos: https://library.netapp.com/ecmdocs/ECMP1636018/html/GUID-A8CC3DD0-D5DF-424A-84E9-830A5CD00430.html

pero al intentar reiniciar por completo el data ontap o al intentar ingresar en modo de mantenimiento, sigo con estos mensajes:

Please choose one of the following:

(1) Normal Boot.
(2) Boot without /etc/rc.
(3) Change password.
(4) Clean configuration and initialize all disks.
(5) Maintenance mode boot.
(6) Update flash from backup config.
(7) Install new software first.
(8) Reboot node.
Selection (1-8)? 5
Chelsio T3 RDMA Driver - version 0.1
Ipspace "iwarp-ipspace" created
Fri Dec 1 17:20:18 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4a.
Fri Dec 1 17:20:18 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4b.
Fri Dec 1 17:20:18 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4c.
Fri Dec 1 17:20:18 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 4d.
Fri Dec 1 17:20:18 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0d.
Fri Dec 1 17:20:18 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0c.
Fri Dec 1 17:20:19 GMT [netif.linkDown:info]: Ethernet Wrench Port: Link down, check cable.
Fri Dec 1 17:20:23 GMT [diskown.isEnabled:info]: software ownership has been enabled for this system
PANIC: sanown: not enough filer table entries
version: NetApp Release 8.0.5: Sun Jan 20 21:53:54 PST 2013
cpuid = 0
Uptime: 50s

PANIC: sanown: not enough filer table entries in SK process sanown_io on release NetApp Release 8.0.5 on Fri Dec 1 17:20:24 GMT 2017

version: NetApp Release 8.0.5: Sun Jan 20 21:53:54 PST 2013
compile flags: amd64, x86_64
Writing panic info to HA mailbox disks.

DUMPCORE: START
Raid assimilation incomplete

DUMPCORE: END -- coredump *NOT* written.
Dumpcore failed
coredump: primary dumper failed -1.
coredump: trying secondary dumper...
no tftp server ip specified
netdump: no targets available to dump
coredump: secondary dumper failed -1.
Logging shutdown event to the SP...
System halting...
cpu_reset called on cpu#0

CPU = 1 Processors Detected, Cores per Processor = 4
@Intel(R) Xeon(R) CPU L5410 @ 2.33GHz
Testing RAM
512MB RAM tested
8192MB RAM installed
6144 KB L2 Cache
System BIOS shadowed
USB 2.0: MICRON eUSB DISK
BIOS is scanning PCI Option ROMs, this may take a few seconds...
+++++++++++++++++++

@CPU Type: Intel(R) Xeon(R) CPU L5410 @ 2.33GHz
LOADER-A>

@aaronswtelogis wrote:
greetings!

I reseated all DIMMs in either controller, the error is gone.

thank you for the reply, this is solved.

hope to get a reply as well on cabling issue. same chassis, trying to figure out what the cabling should be fits the circle->square priciple.

thanks again

Re: PANIC: The 0 is not a supported platform, cpu_reset called on cpu#0

AlexDawson — Mon, 04 Dec 2017 07:01:08 GMT

Hola econde,

Lo sentimos, su problema no son los módulos DIMM, es debido a que el nombre del sistema cambia dos veces sin reiniciar - https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=782865 . Intente ingresar al modo de mantenimiento sin los discos encendidos, luego encienda los discos y ejecute "disk show -an".

Si tiene un contrato de soporte, puede llamarnos para obtener ayuda en español - https://www.netapp.com/es/services-support/ngs-contacts.aspx

Sorry, your problem is not the DIMMs - it is (usually) due to the system name changing twice without a reboot.

Attempt to enter maintenance mode without the disks powered on, then turn on the disks, and run "disk show -an"

If you have a support contract, you may call us for help in Spanish - https://www.netapp.com/es/services-support/ngs-contacts.aspx

https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=782865