From: szabo_p@maths.su.oz.au (Paul Szabo)
Subject: DN10k (SR10.4, 1 or 2 CPU) problems: (more) HELP
Reply-To: szabo_p@maths.su.oz.au (Paul Szabo)
Organization: Mathematics, University of Sydney
Date: Mon, 28 Sep 1992 09:17:27 GMT

Some time ago I wrote about our DN10k crashing at SR10.4.P. To test things
further, I have removed one of the CPUs (leaving it a single CPU system). 
Then I waited a few days, and voila, it crashed again, this time with stcode
00120020: the very crash that patch pd92_p0467 is supposed to fix!

In summary: (up until now) it seems as if patch pd92_p0467 would cause my
system (with one or two CPUs) to crash. (It seemed to crash more readily
with 2 CPUs.) In particular, the patch seems to have introduced, instead of
fixed, the crash with 00120020 code.

I will now de-install the patch, and run the system with both CPUs. I had
had it in that configuration for 3 weeks without any problems; if I could
only get it to forgive me ...

Boring details below.

Paul Szabo - System Manager   //        School of Mathematics and Statistics
szabo_p@maths.su.oz.au        //   University of Sydney, NSW 2006, Australia

-----

After the latest crash (while running with a single CPU, with patch
pd92_p0467 i.e. SR10.4.0.3) the node was showing:

fault in domain_os, cpu 0
E0419978: pc=E0011728 ipsw=08200045
   mmu_csr(e)=1130A00D segment fault, flt pc=E0011724, flt addr=24300000
Crash_Status 00120020  PC E0016E1C  SSP E04194E0  PID 21  CPU 0
stop on cpu 0  pc=E0016944  SSP=E0419468  status code=00120020

Then I used the commands 'DI N xxxxx' and 'DU' to get a dump file. After a
while (and many !'s) it said 'Nm sad - St = 0B030004'. Is such an incomplete
(65MB, from a 72MB system) dump file any use? Would anyone (i.e. HP: Chris?)
want a dump file anyway?

-----

From previous messages:

In article <1992Sep23.043301.15142@ucc.su.OZ.AU> I wrote:

> After each of the crashes, the machine was displaying some crash status
> messages on the screen, and was just sitting there at the 'IP0>' prompt
> (without automatically doing a reboot). Two (out of three) crash messages:
> 
> fault in domain_os, cpu 0
> E036FDB0: pc=E00135C8 ipsw=00000045
>    mmu_csr(e)=1030A000 opnd alignment, flt pc=E00135C4, flt addr=003C4371
> Crash_status 00120001  PC E0016E1C  SSP E036F918  PID 27  CPU 0
> Stop on cpu 0  pc=E0016944  SSP=E036F8A0  status 00120001
> Stop on cpu 1  pc=E0048A68  SSP=E153CF20  status 00120044
> 
> fault in domain_os, cpu 0
> E043BDB0: pc=E00135C8 ipsw=08200045
>    mmu_csr(e)=1110A000 region fault, flt pc=E00135F0, flt addr=6ADA0008
> Crash_status 00040004  PC E0016E1C  SSP E043B918  PID 2A  CPU 0
> Stop on cpu 0  pc=E0016944  SSP=E043B8A0  status 00040004
> Stop on cpu 1  pc=E0048A68  SSP=E1539F20  status 00120044
> 
> The third crash had status code 0032000A (I hoped it was a once-only crash).


In article <1992Sep23.170601.5208@alchemy.chem.utoronto.ca>
system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) wrote:

> I would be willing to bet that your crashes are the "process group id"
> problem that we fell onto after 9 days of running SR10.4.p. We got
> many crashes with status 00190016 and 00120020, plus lots of strange
> system behaviour, including about 10% of all commands randomly failing with
> segmentation faults (but would work if repeated immediately).
> 
> There is a patch for this, called "SR10.4, pgid_fix" on our system,
> but this should have made an official patch tape by now (we aren't on
> maintenance on our DN10000 any more so I don't have the official patch info).
> This patch seems to fix the above problems (but not DEX), though it was only
> designed to address the 00190016 crashes, but the system now sometimes
> just hangs with c.d.r.t. in the front panel, with the 'd.' light on solidly,
> the others flashing. These problems have stopped since the users and
> their files were moved elsewhere (it's always letting the users on the
> system that cause the problems :-) ).


In article <Bv1pGI.4KF@apollo.hp.com> beierl_c@apollo.hp.com (Christopher
Beierl) wrote:

> Patch pd92_p0467 (a88k) on the September '92 patch tape is supposed to fix both the
> 00190016 and the 00120020 crash problems.