Mailing List Archive: F630 Panic

F630 Panic

Aug 14, 2002, 1:58 PM

Post #1 of 4 (3058 views)

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
Wed Aug 14 10:00:00 GMT [kern.uptime.filer:info]: 10:00am up 4 days,
16:33 0 NFS ops, 383717 CIFS ops, 238 HTTP ops
Wed Aug 14 11:00:00 GMT [kern.uptime.filer:info]: 11:00am up 4 days,
17:33 0 NFS ops, 385292 CIFS ops, 238 HTTP ops
Wed Aug 14 12:00:00 GMT [kern.uptime.filer:info]: 12:00pm up 4 days,
18:33 0 NFS ops, 386935 CIFS ops, 238 HTTP ops
Wed Aug 14 12:00:01 GMT [sk.panic:ALERT]: reason="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:00:01 GMT [sk.assert:ALERT]: file="../driver/scsi/scsi.c",
line="1309", expr="NULL"
Wed Aug 14 12:00:01 GMT [sk.assert:ALERT]: file="../driver/scsi/scsi.c",
line="1309", expr="NULL"
Wed Aug 14 12:03:30 GMT [kern.syslog.msg:info]: Ethernet e10a: Link up.
Wed Aug 14 12:03:31 GMT [mgr.boot.oldOFW:error]: The current boot
firmware version is too old. Please upgrade to version 2.3.
Wed Aug 14 12:03:31 GMT [kern.syslog.msg:warning]: Updated boot firmware
is available on the Network Appliance NOW site (now.netapp.com).
Wed Aug 14 12:03:32 GMT [kern.syslog.msg:info]: Replayed 0 checksum
entries
Wed Aug 14 12:03:33 GMT [kern.syslog.msg: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:35 GMT [kern.syslog.msg:ALERT]: Language not set on
volume vol0. Using language config "C". Use vol lang to set language.
Wed Aug 14 12:03:35 GMT [kern.syslog.msg:notice]: The system was down
for 191 seconds
Wed Aug 14 12:03:38 GMT [dyn_dev_qual_admin:info]: Firmware is
up-to-date on all disk drives
Wed Aug 14 12:03:38 GMT [rc:info]: Ethernet e10a: Link up.
Wed Aug 14 12:03:38 GMT [rc:info]: relog syslog Wed Aug 14 12:00:01 GMT
[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 [rc:info]: sysconfig: Note: Model F630 has no
configuration rules.
Wed Aug 14 12:03:38 GMT [mgr.boot.disk_done:info]: NetApp Release 6.1.2
boot complete. Last disk update written at Wed Aug 14 11:59:51 GMT 2002
Wed Aug 14 12:03:38 GMT [mgr.boot.reason_abnormal:ALERT]: System
rebooted due to a watchdog reset.
Wed Aug 14 12:03:38 GMT [mgr.stack.saved:notice]: Reboot with saved
panic information in log file
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

Thanks,

Blake

Re: F630 Panic [ In reply to ]

drechsau at tiny

Aug 14, 2002, 2:30 PM

Post #2 of 4 (2971 views)

Permalink

On Wed, Aug 14, 2002 at 01:58:34PM -0700, Blake Folgner 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

Looks like a problem with a stick of RAM.

But I don't work for NetApp so I could be wrong.

--
Mike Horwath Admin & Manager @ VISI.com WORK: drechsau@visi.com
IRC: Drechsau http://www.visi.com/ HOME: drechsau@geeks.org
The only Minnesota ISP with public statistics: http://noc.visi.com/
Garbage In -- Gospel Out. - berkeley fortune(6)

Re: F630 Panic [ In reply to ]

stefan.funke at arcor-online

Aug 15, 2002, 2:01 AM

Post #3 of 4 (2959 views)

Permalink

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,

--
Stefan Funke | Arcor Online GmbH
Betriebs- und Systemadministration | Stresemannallee 30
stefan.funke@arcor-online.net | D-60596 Frankfurt / www.arcor.de
Phone#: +49 69 633 97-0 | fax: +49 69 633 97-444

Re: F630 Panic [ In reply to ]

yergeau at speakeasy

Aug 15, 2002, 6:54 AM

Post #4 of 4 (2957 views)

Permalink

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,
>
>