Operating System - HP-UX
1830899 Members
2901 Online
110017 Solutions
New Discussion

vmunix message on an Itanium

 
SOLVED
Go to solution
Betty Fessler
Frequent Advisor

vmunix message on an Itanium

Does any know what this means;
vmunix: USB frame sequencing 0x1d771bc9 to 0x1d76c98d
I also got the following message around the same time;
LVM[17102]: /sbin/lvlnboot -v /dev/vg00
Both of these messages were received this morning and the system hasn't been booted for 55 days.
I can't find anything on the USB message.
Thx.
5 REPLIES 5
Patrick Wallek
Honored Contributor
Solution

Re: vmunix message on an Itanium

The "LVM[17102]: /sbin/lvlnboot -v /dev/vg00" just means that someone executed an 'lvlnboot -v' command to have a look at the lvlnboot configuration. This could also have been done by Ignite if a make_[tape|net]_recovery was done.

About the USB message -- was a USB keyborad or mouse or something unplugged at any point?
Betty Fessler
Frequent Advisor

Re: vmunix message on an Itanium

This system is rack mounted and shares a keyboard/mouse & monitor with other systems on the rack. Does that mean whenever we set the paradyne moniter to connect/disconnect to this system we will get these messages?
Patrick Wallek
Honored Contributor

Re: vmunix message on an Itanium

It is possible.

I would do some testing and see if you can correlate the time of the message to the times you switch the console to another machine.

If they are the same, you've found your culprit. If not, more investigation is in order.
Betty Fessler
Frequent Advisor

Re: vmunix message on an Itanium

Could another possibility be that around that time of morning we have a script running thats doing a configuration check? and we don't currently have a monitor/keyboard/mouse attached?
Devender Khatana
Honored Contributor

Re: vmunix message on an Itanium

Hi,

lvlnboot -v could be resulted from this monitoring script. Yes this USB message also could be a result of some scanning through that script. Posibally that script does collect ioscan & all outputs during config collection resulting out in these messages. Running all command listed in the script one by one will help you know the exact one which causes this message.

HTH,
Devender
Impossible itself mentions "I m possible"