Call NetApp support and send them the core dump. They will tell you exactly why it panicked, if there is a fix they will tell you the revision of ONTAP to install and if not they will send the bug to the developers to fix.
Service contracts.. that's why you buy them. :-)
On Thu, 15 Aug 2002, Stefan Funke wrote:
On 2002-08-14 (13:58, -0700), Blake Folgner blake@webrunners.com wrote:
Hello All,
My F630 has generated these errors below. The Filer is running 6.1.2 and it's in a CIFS environment only. Any Ideas?
Wed Aug 14 09:30:04 GMT [raid_xor_server:CRITICAL]: 1 CORR PROC ERR 86 eia:a011720 fs:94 eis:c5000000 isr:100000000 CPU ECC error on SIMM=J100, Address=ffffff000a01172f [wafl_hipri:CRITICAL]: 3 CORR PROC ERR 86 eia:117e0 fs:3 eis:1c5000000 isr:100000000 CPU ECC e Wed Aug 14 12:03:38 GMT [rc:ALERT]: relog syslog PANIC: MM fault MMCSR=1, type=0, VA=0x0, PC=0xfffffc00000110d8, RA=0x55360 in process wafl_hipri on release NetApp Rel Wed Aug 14 12:03:38 GMT [mgr.stack.string:notice]: Panic string: MM fault MMCSR=1, type=0, VA=0x0, PC=0xfffffc00000110d8, RA=0x55360 in process wafl_hipri on release NetApp Release 6.1.2 Wed Aug 14 12:03:38 GMT [mgr.stack.at:notice]: Panic occurred at: Wed Aug 14 12:00:01 2002 Wed Aug 14 12:03:38 GMT [mgr.stack.proc:notice]: Panic in process: wafl_hipri Wed Aug 14 12:03:38 GMT [mgr.stack.noFrames:notice]: No stack frames available
Login to now.netapp.com, grab the diagnostic disk (in download -> tools) section and run some RAM-diag tests. (to do that you have to shut down your filer, boot from disk and run into diag-mode - the filer can't handle CIFS/NFS/whatever connections during that time so running that tests means down time but can help a lot)
Greetings,