[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

9749.0. "uerf problem?" by NNTPD::"[email protected]" (Ludmila Mala) Thu May 08 1997 01:00

I have a client with a strange problem. He is running DU V3.2G. He has
noticed, that his uerf 
no longer displays all messages. When he boots of genvmunix, the uerf performs
normally. As soon 
as he compiles the kernel to customise it, immediatelly the uerf stops
displaying the messages.

This is example of normal uerf :
----- EVENT INFORMATION -----

EVENT CLASS                             OPERATIONAL EVENT
OS EVENT TYPE                  300.     SYSTEM STARTUP
SEQUENCE NUMBER                  0.
OPERATING SYSTEM                        DEC OSF/1
OCCURRED/LOGGED ON                      Sat Apr 12 11:30:21 1997
OCCURRED ON SYSTEM                      wcau015
SYSTEM ID                 x00050009     CPU TYPE:  DEC 2100
SYSTYPE                   x00000000
MESSAGE                                 PCXAL keyboard, language English
                                         _(American)

                                        Alpha boot: available memory from
                                         _0x13d4000 to 0x1ffee000
                                        Digital UNIX V3.2G (Rev. 62); Thu Jul

                                         _18 22:21:57 EDT 1996
                                        physical memory = 512.00 megabytes.
                                        available memory = 492.10 megabytes.
                                        using 1958 buffers containing 15.29
                                         _megabytes of memory
                                        Master cpu at slot 0.
                                        Firmware revision: 4.7
                                        PALcode: OSF version 1.21
                                        ibus0 at nexus
                                        AlphaServer 2100 5/300
                                        cpu 0 EV-5 4mb b-cache
                                        cpu 1 EV-5 4mb b-cache
                                        gpc0 at ibus0
                                        pci0 at ibus0 slot 0
                                        tu0: DECchip 21040-AA: Revision: 2.3
                                        tu0 at pci0 slot 0
                                        tu0: DEC TULIP Ethernet Interface,
                                         etc
When he compiles the kernel, all he gets is:


----- EVENT INFORMATION -----

EVENT CLASS                             OPERATIONAL EVENT
OS EVENT TYPE                  300.     SYSTEM STARTUP
SEQUENCE NUMBER                  0.
OPERATING SYSTEM                        DEC OSF/1
OCCURRED/LOGGED ON                      Sat Apr 12 11:50:49 1997
OCCURRED ON SYSTEM                      wcau015
SYSTEM ID                 x00050009     CPU TYPE:  DEC 2100
SYSTYPE                   x00000000
MESSAGE                                 ts reserved.

************
Or he gets this :
************
 
----- EVENT INFORMATION -----

EVENT CLASS                             OPERATIONAL EVENT
OS EVENT TYPE                  300.     SYSTEM STARTUP
SEQUENCE NUMBER                  0.
OPERATING SYSTEM                        DEC OSF/1
OCCURRED/LOGGED ON                      Sun Apr 13 04:06:37 1997
OCCURRED ON SYSTEM                      wcau015
SYSTEM ID                 x00050009     CPU TYPE:  DEC 2100
SYSTYPE                   x00000000
MESSAGE                                 ed.
 
He believes, that nothing happened on the systems during the week
this appeared the first time, ie no hardware or software changes. 
He of course cannot exclude some an unexpected action of any of his 
users.

Does anybody know what these messages : ts reserved. or ed. 
are trying to tell us? The system works with no problems.

Thanks for any ideas or pointers.

Regards,

Ludmila

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
9749.1Check for option uerfNNTPD::"[email protected]"Adrian MorrissonThu May 08 1997 02:177
Ludmilla
	Check the kernel config file for the line
	options         UERF
	

Adrian
[Posted by WWW Notes gateway]
9749.2config fileNNTPD::"[email protected]"Ludmila MALASun May 11 1997 21:4310
Adrian,

Thanks for the idea, but no go. I modified it on my alfa and it still 
works correctly.

Regards,

Ludmila

[Posted by WWW Notes gateway]
9749.3why not dia??KYOSS1::GREENWed May 14 1997 11:363
    	Why isn't the customer using DECevent. uerf is going away, or at
    least not supported.
    
9749.4DecEventNNTPD::"[email protected]"Ludmila MalaWed May 14 1997 20:018
Yes, that is a good point, but it still does not answer his  question. He
forever will believe, that his system has a problem. I would like to prove him
wrong.


Ludmila

[Posted by WWW Notes gateway]
9749.5INDYX::ramRam Rao, PBPGINFWMYWed May 14 1997 22:4910
>    	Why isn't the customer using DECevent. uerf is going away, or at
>    least not supported.
    
Why is DECevent PAK protected?

Where can I get a PAK for internal use?

Thanks,

Ram
9749.6LEXS01::GINGERRon GingerThu May 15 1997 10:216
    DECevent has 2 parts- the reporting part is NOT pak protected. The
    analysis part is. To simply replace uerf you need only the reporting
    part.
    
    I tried the analysis part a while ago, and it never had anything
    usefull to say. I use the reporter at all my customers.
9749.7BIGUN::nessus.cao.dec.com::MayneA wretched hive of scum and villainyThu May 15 1997 19:254
If you read the DECevent installation notes or the online documentation, it 
tells you exactly where to get a PAK.

PJDM