[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9721.0. "" by NNTPD::"[email protected]" (Tony Chen) Tue May 06 1997 00:27

Hi,
my customer had a problem about SMP,the following was customer's envirment:

machine:AlphaServer 2100 4/200
memory:256MB
Processors:4 CPUs

When users used dbx to debug a program,the system would be down(I couldnot
determine
whether the phenomenon was associated with using dbx),sometimes very
frequently.
I read the messages produced by the system,and thought there would be some 
paremeters unmatch the system.I need your help,it will be appericiate if I
received
the reply.The following was the messages:

EVENT class                                    ERROR EVENT
OS EVENT TYPE             302                  PANIC
SEQUENCE NUMBER             1
OPERATING SYSTEM                               DEC OSF/1
OCCURRED/LOGGED ON                             Fri Apr 25 12:05:10 1997
SYSTEM ID               X00020009              CPU TYPE :DEC 2100
SYSTYPE                 X00000000
PROCESSOR COUNT         4
PROCESSOR WHO LOGGED    X00000002
MESSAGE                                        panic(cpu 2)delete_pv_entry
                                               _mapping not in pv_list

And the 4 CPUs occurred the same error messages.

Thanks & Regards
Tony Chen
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
9721.1Can only guess without more information...QUARRY::petertrigidly defined areas of doubt and uncertaintyTue May 06 1997 12:5913
Which operating system is this on?  Several people have reported problems
with debuggers on V4.0B, so I've been checking that one first.  
That started showing up at V4.0B when the kernel is built with the KDEBUG
option.  Not all machines experience the problem, and I'm not sure if
the 2100 is one that does.  If the above applies, rebuild without 
KDEBUG, and the problem should clear up.  

But then again, it may be something else entirely.  Start with the OS
version and see if there is a crash_data file produced in /var/adm/crash.
Otherwise the information you have given us is a bit small to start
with.

PeterT