Title: | DECmcc user notes file. Does not replace IPMT. |
Notice: | Use IPMT for problems. Newsletter location in note 6187 |
Moderator: | TAEC::BEROUD |
Created: | Mon Aug 21 1989 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 6497 |
Total number of notes: | 27359 |
Hi: I have been working with DECmcc EFT 1.2.7 (and before with EFT 1.2.4) For ULTRIX using the next configuration: DECstation 2100 RZ56 (665 MB) 20 MB I have a doubt: Reading the BMS SPD file (note 3164), in special the system support addendum, I did not find that a DECstation 2100 is a supported system some comment about this? The reason of work in this system is that we have a customer who has a lot of them and we want to offer DECmcc For ULTRIX like the Network Management System, however they want to use one of their DECstation's 2100 like the Network Management Station By another hand, let me explain a problem we have had in these systems ( working with both field test of DECmcc For ULTRIX: T 1.2.4 and T1.2.7 using the same configuration ) sometimes doing anything like openning since the iconic map the DECmcc reports option or registering some entity, the system had a Kernel Panic event who give us the next message: --------------------- MUNLOCK:dup page unlock --------------------- and then the system crashs is this a memory problem? Some idea of what is the reason of this problem? Any comment would be appreciate Thanks in advance, Julio Lerios (Digital Mexico)
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3268.1 | Patch your ULTRIX kernel | TOOK::MINTZ | Erik Mintz, dtn 226-5033 | Tue Jun 30 1992 00:25 | 20 |
We do not support the 2100 because we haven't tested with it, and expect that performance will be unacceptably slow. Otherwise, it should work, as far as we know. >the system had a Kernel Panic event who give us the next message: > >--------------------- MUNLOCK:dup page unlock --------------------- > >and then the system crashs > >is this a memory problem? This is a known bug in ULTRIX, which is exposed by DECmcc (and probably other products that use DECthreads). There is a patch available for the ULTRIX kernel. I believe you will find information on the patch in the T1.2.7 release notes. -- Erik |