interresting question

[Donny Jekels]

does anyone know how to check which kernel /stand/vmuni* was loaded at boot time. after the system is up and running?

[Pete Randall]

Donny,

I recall seeing this same question a while back, but with the search engine being stubborn today, there doesn't seem to be anyway to find it.

I suppose you might be able to check the contents of /stand/system against kmtune output (assuming the last kernel change was a configurable parameter modification). A "what /stand/vmunix" might lead you to discern what the latest kernel patch was (with some effort).

Other than that, I don't know of any easy way.


Pete

[Donny Jekels]

Pete,

Thinking about the load process, ISL mounts the /stand filesystem in read only mode, and thus the inodes does not even gets modified for access time at that time.

and therefore you cannot run

find . -atime on the /stand fs

[Patrick Wallek · Accepted solution]

From TKB document KBRC00001823:

# echo 'boot_string/S' | adb /stand/vmunix /dev/mem

It appears to work on 11.0 and 11.11.

[A. Clay Stephenson]

This is tricky because adb needs a matching executable (/stand/vmunix) to properly read /dev/mem BUT if this command works then that is the kernel you booted from:

echo "boot_string/S" | adb /stand/vmunix /dev/mem

You can keep trying various kernel files until adb returns meaningful data.

[Donny Jekels]

Patrick,

where can I get these knowledge base info?

thanks
Donny

[Geoff Wild]

echo "boot_string/s" | adb -k /stand/vmunix /dev/kmem

will tell - even if /stand/vmunix.prev

IE:

boot_string: disk(0/0/0/3/0.6.0.0.0.0.0;0)/stand/vmunix

or

boot_string: disk(0/0/0/3/0.6.0.0.0.0.0;0)/stand/vmunix.prev

Rgds...Geoff

[curt larson_1]

here is a thread where i asked this question before. There are a lot of possible solutions for you to choose from.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=54652

[curt larson_1]

here is a C program to do it

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=53301

[Patrick Wallek]

Donny,

Go to http://itrc.hp.com

Click the "Technical Knowledge Base" link in the left column.

When the page comes up, just put your search string in the field. To find this I searched on "which kernel booted" and the first document in the list of a bunch that were returned was the doc id I gave you. If you want to search by doc id, use the pull down menu and select "search by docid" and then put the Doc ID in the field.

The direct link to the document I gave you is:
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000065450534

According to this document the command should work regardless of vmunix or vmunix.prev being the booted kernel.

[Donny Jekels]

thanks all!

[Sridhar Bhaskarla]

Hi Donny,

My 2 cents.

You can use the same adb to find out if the kernel that you used does in fact matches the /dev/mem.

Any adb command should give you an error (and probably a false value) if you are not booted from /stand/vmunix. For ex.,

echo 'nfile/D' | adb -k /stand/vmunix /dev/mem

Should complain about version mismatch between the kernel and the core and probably give you a wrong value if the system was not booted from vmunix.

-Sri