Title: | Alpha Support Conference |
Notice: | This is a new Alphanotes, please read note 2.2 |
Moderator: | VAXAXP::BERNARDO |
Created: | Thu Jan 02 1997 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 128 |
Total number of notes: | 617 |
Hi, I've got a 4100 running 6.2-1H3 it's been up for just over 200 hours with very little activity. I thought it about time to run Autogen. This was run from GETDATA - SETPARAMS, at a convenient time over the weekend it was then rebooted. It failed to BOOT with a SYSBOOT-W-ALOHUGEPAGE error and just kept looping. The system was then halted. I did a conversational boot and checked the GH_* params. I then set them back to the defaults. Rebooted and the system cam up ok. I checked the AGEN$PARAMS.REPORT file and noticed the following changes made by AUTOGEN GH_EXEC_CODE Feedback Information Old value was 512, New value is 1024 GH_EXEC_DATA Feedback Information Old value was 128, New value is 112 GH_RES_CODE Feedback Information Old value was 1024, New value is 1024 Any ideas why Autogen resized GH_EXEC_CODE to a higher value and why did it cause the system to become unbootable. Many thanks Daryl.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
66.1 | ZIMBRA::BERNARDO | Dave Bernardo, VMS Engineering | Mon Mar 24 1997 08:00 | 10 | |
See note 118 in VMSNOTES_V12 for an explanation of the boot failure. Autogen will increase the GH_* values if there was an allocation failure from the GH regions during the bootstrap. It basically means that you've loaded more execlets than can fit in 512 pages. When there is no more room in the GH regions the execlets get loaded differently. So, the system will run fine, you just won't take advantage of the granularity hint stuff for those last few execlets. d. | |||||
66.2 | EEMELI::MOSER | Orienteers do it in the bush... | Tue Mar 25 1997 11:47 | 3 | |
in short: >>> SET MEM_TEST FULL /cmos |