“dmesg” Alert

[HP UNIX Professionals]

Hi Experts,

We have PA-RISK HPUNIX box(B.11.11 U 9000/800),
I am getting following message for “dmesg” command

Please guid me

1.why this message is coming.
2.Anything Harmful to the server /Memory.


===============================================
memory
16 ipmi
128 processor
129 processor
136 processor
137 processor
144 processor
145 processor

System Console is on the Built-In Serial Interface
iether0: INITIALIZING HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/0
iether1: INITIALIZING HP AB352-60001 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/1/2/1
Acceleport Xr Host Adapter (PCI) at 0xffffffffd0200000: mem=0xffffffffd0000000, # of ports=8 V Version B.11.11.01 : Jun 22 2006 18:49:01
Acceleport Xr Host Adapter (PCI) at 0xffffffffd0200000: Extended Description: Digi Acceleport 8r 920 Host Adapter
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 24576000
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x21000; start = 314208, size = 12288000
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 14678016 Kbytes, lockable: 13484728 Kbytes, available: 13008636 Kbytes

USB frame sequencing 0x9f4b965 to 0x9f43967


Thanks in Advance

VINAY

[Mel Burslan]

This is what you should see right after the reboot of machine has been completed. If dmesg logs more messages in time, those are the one that you should pay close attention to, although not all messages logged there are necessarily crippling to your system. Keep this copy of dmesg output in a file and maybe set up a cron job to check it every few hours and send you an email if there are discrepancies, which means things got logged to dmesg. That would be my suggestion.

[Dennis Handly]

What particular line troubles you? I don't see any errors. Better you just look at syslog.

>Mel: maybe set up a cron job to check it every few hours

You can log dmesg(1m) output with something like:
/usr/sbin/dmesg - >> /var/adm/messages

[Torsten.]

These are normal boot up messages.

[Alzhy]

It simply means you aer likely using a later model PARISK server that has an ancient USB implementation. Likely an rp3XXX series server.