NetApp Community Update
This site will enter Read Only mode on July 23 as we prepare to move to a new platform. You will still be able to view content, but posting and replying will be temporarily disabled.
We're excited to launch our new Community experience on July 30 and more information will follow soon.
Stay connected during the transition - Join our Discord community today.

ONTAP Discussions

PANIC : page fault (supervisor read, page not present)

response
6,764 Views

PANIC  : page fault (supervisor read, page not present) on VA 0x28 cs:rip = 0x8:0xffffffff843ebec3 rflags = 0x10246 ,

have anyone hit?

1 ACCEPTED SOLUTION

response
6,750 Views

OnTAP release 8.1.3P3,
I found the similar case need to upgrade to 8.2.1 and later , but what is really root cause.
https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/639665

View solution in original post

5 REPLIES 5

akiendl
6,760 Views

Which ONTAP release are you running? But without seeing the core file it might become very much guess work.

response
6,751 Views

OnTAP release 8.1.3P3,
I found the similar case need to upgrade to 8.2.1 and later , but what is really root cause.
https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/639665

pedro_rocha
6,698 Views

Does it happen during boot? Any other msg right before or after?

 

EMS shows any different message or additional info?

response
6,643 Views

It's reboot before panic, about msg is bloew,

 

Sun Feb 7 19:42:23 CST [NAS02:cf.fsm.takeover.panic:ALERT]: Failover monitor: takeover attempted after partner panicSun Feb 7 19:42:23 CST [NAS02:cf.fsm.stateTransit:info]: Failover monitor: UP --> TAKEOVERSun Feb 7 19:42:23 CST [NAS02:cf.fm.takeoverStarted:notice]: Failover monitor: takeover started

 

and panic messages is "PANIC: page fault (supervisor read, page not present) on VA 0x28 cs:rip = 0x8:0xffffffff843eceb3 rflags = 0x10246 in SK process Auth00 on release 8.1.3P3 on Wed Feb 10 08:49:26 CST 2021'

paul_stejskal
6,603 Views

Without a core it is impossible to say. I would upgrade to 8.2.5P5 first and if it still happens engage Support.

Public