Here are the answers I got to my problem described below
>>Hi managers,
>>
>>4 month ago I have upgraded my DEC3000/600 to OSF1/ V3.0.
>>I am running ADVfs on all filesystems. (And I am just waiting for the
>>new CD's to upgrade to V3.2).
>>
>>All worked fine, but last week and today it crashed with a PANIC error.
>>With uerf I get the following message:
>>
>>
>>----- EVENT INFORMATION -----
>>
>>EVENT CLASS                             ERROR EVENT
>>OS EVENT TYPE                  302.     PANIC
>>SEQUENCE NUMBER                  8.
>>
>>...
>>
>>/var/adm/crash/crash-data.0 shows the following:
>>
>>#
>># Crash Data Collection (Version 1.4)
>>#
>>_crash_data_collection_time: Mon Mar 20 16:51:11 MET 1995
>>_current_directory: /
>>_crash_kernel: /var/adm/crash/vmunix.0
>>_crash_core: /var/adm/crash/vmcore.0
>>_crash_arch: alpha
>>_crash_os: DEC OSF/1
>>_host_version: DEC OSF/1 V3.0 (Rev. 347); Wed Feb 15 09:21:32 MET 1995 
>>_crash_version: DEC OSF/1 V3.0 (Rev. 347); Wed Feb 15 09:21:32 MET 1995 
>>
>>...
>>
>>panic (cpu 0): kernel memory fault
>>
>>Is it a known problem with a known bug fix or can You give me a hint 
>>to solve it?
-------------------------------------------------------------------------
Simultaneously to my question to the list I contacted DEC customer support
people in Germany. Soon I have posted the chrash data for ananlysis to my 
local DEC service and I was told, that this problem looks like a known 
error on the NFS 3.0 client(see the mail from Andrew). 
Last night I have got the patch from DEC.  
-------------------------------------------------------------------------
Many thanks to
-->>  Knut Helleboe  -- (Knut.Hellebo_at_nho.hydro.com)
>Hope you're not running RAID. ... 
>Otherwise I would think those messages stem from one or more of the AdvFS
>bugs discovered. Lookup the patches in www.service.digital.com or call your
>DEC office.
-->>  Andrew Gallatin <gallatin_at_isds.Duke.EDU>
>I'm not certain, but I think this may be the error that occurs on an
>NFS client when running NFS 3.0.  I had similar panics & cured them
>temporarily by mounting remote filesystems via NFS v2 while waiting to
>upgrade to 3.2
>2 of my machines experienced the problem - one has been at 3.2 for a
>week w/no problems, the other will be upgraded to 3.2 on Saturday.  In
>short, I can't say for sure if upgrading to 3.2 fixes it or not ;)
-->>  Ben Dibble <dibble_at_zk3.dec.com>
>A kernel memory fault could be caused by many things.  If you haven't
>contacted the Customer support people in Germany, you should.  Many
>of these panics have been fixed.
Have a nice easter
Rainer
| schwierz_at_pktw03.phy.tu-dresden.de                 |
|     /_/_/_         /_/_                           |
|    /_   /_       /_                               |
|   /_/_/_        /_/_/_                            |
|  /_  /_            /_                             |
| /_    /_ainer  /_/_  chwierz,                     |
| Inst. f. Kern- und Teilchenphysik                 |
| TU Dresden                                        |
| D-01062 Dresden                                   |
| Tel. ++49 351 463 4425      FAX ++49 351 463 7292 |
Received on Thu Apr 13 1995 - 02:30:25 NZST