romwa@gpu.utcs.toronto.edu (Mark Dornfeld) (01/30/88)
I have a Xenix 2.2.1 system regularly doing a panic (5 times today). The console error message is usually like this: TRAP 000C in SYSTEM ax=0000, bx=08DC, cx=002E, dx=0006, si=0000, di=0716 bp=0316, fl=0212, uds=0018, es=0070 pc=0030:5B6D, ksp=03F2, ss:sp=0058:0314 panic: stack fault Can anyone help me identify the subsystem that is causing the error? It seems to be a memory problem, but I have no way of knowing because I cannot translate the above addresses into anything meaningful. Mark T. Dornfeld Royal Ontario Museum mark@utgpu!rom -or- romwa@utgpu
chip@ateng.UUCP (Chip Salzenberg) (02/04/88)
In article <1988Jan29.180354.15087@gpu.utcs.toronto.edu> romwa@gpu.utcs.toronto.edu (Mark Dornfeld) writes: >I have a Xenix 2.2.1 system regularly doing a panic (5 times >today). The console error message is usually like this: > >TRAP 000C in SYSTEM >ax=0000, bx=08DC, cx=002E, dx=0006, si=0000, di=0716 >bp=0316, fl=0212, uds=0018, es=0070 >pc=0030:5B6D, ksp=03F2, ss:sp=0058:0314 >panic: stack fault My system (also 2.2.1) was doing this too. Since the kernel is linked in Medium model, the near data (DGROUP) includes both 'near' data and the stack. On a hunch, I ran /usr/sys/conf/configure and lowered some values (max buffers, max message queues, max clists, etc.). The stack faults went away. My guess: If your configuration has too much stuff in the data segment, you may be leaving too little room in DGROUP for the kernel stack. -- Chip Salzenberg UUCP: "{codas,uunet}!ateng!chip" A T Engineering My employer's opinions are a trade secret. "Anything that works is better than anything that doesn't."