Subscribe

PANIC: sk_allocate_memory: out of memory in SK process main_proc on release 8.2.1 (C)

Hi Everyone,

 

I ran into this issue today on the cDot simulator running on my laptop.  Sim begins boot process and then panics after memory and network checks...

 

VLOADER>
VLOADER>
VLOADER> boot
x86_64/freebsd/image1/kernel data=0x91bd88+0x302210 syms=[0x8+0x45168+0x8+0x2e6e2]
x86_64/freebsd/image1/platform.ko size 0x2a8130 at 0xd92000
bootarg.init.low_mem set. This will set the FreeBSD size to 512MB
NetApp Data ONTAP 8.2.1 Cluster-Mode
Copyright (C) 1992-2014 NetApp.
All rights reserved.
md1.uzip: 39168 x 16384 blocks
md2.uzip: 5760 x 16384 blocks
*******************************
*                             *
* Press Ctrl-C for Boot Menu. *
*                             *
*******************************
route: writing to routing socket: Network is unreachable
add net 0.0.0.0: gateway 192.168.11.1: Network is unreachable
Using fake nvram. No need to check battery for fake nvram. Data loss is possible.
Oct 31 21:09:17 [bigmomma-02:nv.fake:CRITICAL]: 32 MB system memory being used to simulate NVRAM.
Oct 31 21:09:20 [bigmomma-02:snmp.link.up:info]: Interface 6 is up
Oct 31 21:09:20 [bigmomma-02:netif.linkUp:info]: Ethernet e0f: Link up.
Oct 31 21:09:20 [bigmomma-02:snmp.link.up:info]: Interface 5 is up
Oct 31 21:09:20 [bigmomma-02:netif.linkUp:info]: Ethernet e0e: Link up.
Oct 31 21:09:20 [bigmomma-02:snmp.link.up:info]: Interface 4 is up
Oct 31 21:09:20 [bigmomma-02:netif.linkUp:info]: Ethernet e0d: Link up.
Oct 31 21:09:20 [bigmomma-02:snmp.link.up:info]: Interface 3 is up
Oct 31 21:09:20 [bigmomma-02:netif.linkUp:info]: Ethernet e0c: Link up.
Oct 31 21:09:20 [bigmomma-02:snmp.link.up:info]: Interface 2 is up
Oct 31 21:09:20 [bigmomma-02:netif.linkUp:info]: Ethernet e0b: Link up.
Oct 31 21:09:20 [bigmomma-02:snmp.link.up:info]: Interface 1 is up
Oct 31 21:09:20 [bigmomma-02:netif.linkUp:info]: Ethernet e0a: Link up.
Oct 31 21:09:22 [bigmomma-02:diskown.isEnabled:info]: software ownership has been enabled for this system
route add: bad address: gw 127.0.20.1 equal to destination 127.0.20.1.
PANIC  : sk_allocate_memory: out of memory
version: 8.2.1: Fri Mar 21 14:48:58 PDT 2014
conf   : x86_64
cpuid = 0
Uptime: 43s

PANIC: sk_allocate_memory: out of memory in SK process main_proc on release 8.2.1 (C) on Fri Oct 31 21:09:22 GMT 2014
version: 8.2.1: Fri Mar 21 14:48:58 PDT 2014
compile flags: x86_64
recursive PANIC: page_t has no physical address
cpuid = 0
Uptime: 43s

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

 

The simulator has run well historically and this is the first time encountering this error. 

 

Has anyone run into this error before?  A quick search of the forums and google did not yield any obvious solutions.

 

laptop = lenovo T430S

- running windows 7 64bit

- Processor(s): i5-3320M
    [01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~2601 Mhz
    BIOS Version: LENOVO G7ET99WW (2.59 ), 3/18/2014

- 6GB memory

- SSD storage

- VMware Workstation v 10.0.3

- only 2 node cluster powered on in VMWS

- putty and chrome only other apps running

 

Thanks in advance!!

 

-Brandon

 

Re: PANIC: sk_allocate_memory: out of memory in SK process main_proc on release 8.2.1 (C)

I hit this last night on 8.2.1. The fix was simple enough, increase vm ram to 2gb.