T.R | Title | User | Personal Name | Date | Lines |
---|
716.1 | HW? | ZENDIA::DBIGELOW | Innovate, Integrate, Evaporate | Mon May 08 1995 21:12 | 9 |
| Not sure ehat to say here, except that it sounds like the problem lies
outside of PCM. I don't believe that we do anything outside of the
ordinary which wouls cause the system to core dump. It seems like a
sporadic error and I would be suspicious that this might be some sort
of hardware error. (I know, it sounds like I'm passing the buck, but
the operting system should be protected from allowing users to cause a
core dump).
Dave
|
716.2 | | CSC32::PITT | | Mon May 08 1995 23:09 | 16 |
|
I agree....but the facts do tend to incriminate PCM!
This node was up and running without any problems for several weeks.
He is running other network protocols so the controller is getting a
workout outside of pcm.
As soon as he fired up PCM, core dump.
If he leaves it down, no problem. Start it up, core dump.
Question. If you have no systems configured under PCM yet, is it even
going to use the network controller? It's not doing any polling or
soliciting, so the network controller wouldn't come into play yet?
thanks !!!!!!!!
Cathy
|
716.3 | | YOSSAM::SIMON | Simon Jackson @reo 830 X3879 | Tue May 09 1995 09:40 | 8 |
| There is a known big in version 3.2 of OSF/1 LAT code which is seen when using
PCM. It causes the Kernel Memory Panic you have seen. It is seen when you use
LAT as the PCM management transport. There is a patch available for this problem
from the CSC.
See note 624.last as this has the patch reference.
Cheers SImon...
|
716.4 | | CSC32::PITT | | Wed May 10 1995 06:01 | 5 |
|
thanks Simon, I'll try the patch!
Cathy
|