[Info-vax] XPERR analysis

[VAXman- at SendSpamHere.ORG]

In article <22cea124-e174-49d5-9030-1976a8dd7b06 at p32g2000vbi.googlegroups.com>, GerMarsh <marsh.family at tirhir.com> writes:
>On 30 Nov, 12:47, VAXman-  @SendSpamHere.ORG wrote:
>> In article <cb000042-3d16-4e3d-8518-b6cffb2c3... at s31g2000yqs.googlegroups=
>..com>, GerMarsh <marsh.fam... at tirhir.com> writes:
>>
>> >Sorry - I meant the XPQERR bugcheck.
>>
>> Would this be a VAX 7000-620 (now) by any chance?
>>
>> --
>> VAXman- A Bored Certified VMS Kernel Mode Hacker =A0 =A0VAXman(at)TMESIS(=
>dot)ORG
>>
>> =A0http://www.quirkfactory.com/popart/asskey/eqn2.png
>>
>> =A0 "Well my son, life is like a beanstalk, isn't it?"
>
>Yes - It is! That was well deducted!

Not really.  I received information regarding your crash; however, in your
first post you said:

>(Different images and processes but always concerning the particular
>shadowset. The crashes only started since installing the new processor
>but it didn't crash at all for a few weeks.)

which has given me cause to put this on the back burner as it is not very
likely to be caused by anything I should be concerned with.  The initial
report fingered one image in one product but you now claim that it is NOT
an isolated case, and that different processes and images have fallen vic-
tim.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

  http://www.quirkfactory.com/popart/asskey/eqn2.png
  
  "Well my son, life is like a beanstalk, isn't it?"