Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problems after AIX 5.2 update to ML01

Status
Not open for further replies.

axelsche

MIS
Sep 5, 2001
53
DE
Hi,

after upgrade my p630 to AIX 5.2 ML01 (update_all) and rebooting my system,
I seem to hang in a reboot loop.

System comes up with normal console messages (last is "starting tcpip daemons")
and after that the system shows the following on it's LCD:

OOc9
CDT: bos

00c9
CDT: ipc

00c9
CDT: vmm

BOFF

The system switches off and after a while restarts booting again.

Any ideas??

TIA
Axel
 
if i were in your shoes, i would call IBM for some walkthrough on the phone. i like figuring out things but when my systems are down, i go to the support crew.

IBM Certified -- AIX 4.3 Obfuscation
 
If I were you, I would implement my backout plan. I would revert back to the earlier operating system and then confirm the system resources to support AIX 5.2 on the P630, including filesystem space, ram, paging space, etc.
You may also want to research and compare you scenario with other administrators.
 
hi ,

We have also been experiencing problems running AIX 5.2 and ML01 , in the sense that certain aspects in our case HACMP when syncing used to hang and certain fiels not being populated. We found out that increasing the memory from 512MB to 3GB appeared to have solved the problem .

How much memory have you got installed in your server ?
Plus you can do an lslpp -L , get the output and compare this when you go to the APARS AIX Fix datbase , there is this option for AIX 5 , and see what filesets they recommend you are missing if any.

HTH
 
HI,

We now had the same problem - AIX crashing and rebooting with AIX 5.2 ML1.

0c9 means that the system dump fails.
We are now investigating with IBM,they admit that they have changed some drivers (networking,etc) behaviour.
This causes our third party communication software to crash the system on each boot.

"Long live king Moshiach !"
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top