My server is running NetWare 6.5 SP7. Out of the blue, it restarted.
Came back up pretty quick though. We only noticed it was down because
iFolder stopped.

I checked the abend log and I see this:

Abend 1 on P02: Server-5.70.07-0: DQ_DEQ would cause memory corruption

CS = 0008 DS = 0010 ES = 0010 FS = 0010 GS = 0023 SS = 0010
EAX = 0D2AD84C EBX = 215C045C ECX = 009ED963 EDX = 8C6D1803
ESI = 8C6D186C EDI = 8C6D186C EBP = 8A323F28 ESP = 8A323F14
EIP = 8A909836 FLAGS = 00000283
8A909836 83C404 ADD ESP, 00000004
EIP in NSS.NLM at code start +00006836h

The violation occurred while processing the following instruction:
8A909836 83C404 ADD ESP, 00000004
8A909839 8B03 MOV EAX, [EBX]
8A90983B 8907 MOV [EDI], EAX
8A90983D 897804 MOV [EAX+04], EDI
8A909840 8D43F8 LEA EAX, [EBX-08]
8A909843 C70300000000 MOV [EBX], 00000000
8A909849 85C0 TEST EAX, EAX
8A90984B 75C2 JNZ 8A90980F
8A90984D 8D65F4 LEA ESP, [EBP-0C]
8A909850 5F POP EDI

Running process: Interrupt service routine (nested count 0)
Interrupted process: Processor 2: IDLE Thread Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8A323FB8
OS Stack limit: 8A322000
CPU 2 (Thread 8A3215C0) is in a NO SLEEP state
Scheduling priority: 67371008
Wait state: 3031111 Intermedidate Goto READY

etc. etc. etc.

I look up the area on the Novell knowledge base and I found TID 3635281
which states:

This is an abend that was intentionally added in the released versions
of NSS code. It is a debug check that validates the previous and next
node's link for each node that is being de-queued from a linked list.
If the node's next node does not have a previous pointer pointing back
correctly to the node being removed, or if the node's previous node does
not have a next pointer pointing to the node being removed, then this
abend happens.

This check catches memory corruption before it can propagate further in
the file system. The NSS file system team at Novell is serious about
tracking down and eliminating all forms of memory corruption with the
NSS file system as early as possible in the chain of events, and these
types of checks help with that process.

So...with all that being said...should I try troubleshooting this
problem? Should I call up Novell and report it? Would it cost me money
to report it? This has happen to our server twice now.

What do you guys think, oh great gurus of the Novell systems~! :)