Sponsored Content
Operating Systems AIX aix5.3 migration locked on 7026 with 0c46 LED-screen code Post 302252843 by shockneck on Thursday 30th of October 2008 12:02:47 PM
Old 10-30-2008
IIRC c46 means installation is in progress. Make sure that you do not use Half Duplex with your ethernet and if you don't give it more time. If you use Half Duplex interrupt the inst, change settings and start over.
 

9 More Discussions You Might Find Interesting

1. AIX

Re-Installation of AIX 5.2 in RS6000 7026

Hi There!! I need to reinstall the operating system AIX 5.2 in a RS6000 7026/6H1 that has AIX 4.3 but I need a firmware upgrade that I dón´t know where can I obtain. - Platform firmware version 3 or later. Someone can help me please, I will be very grateful !! Thank´s. (1 Reply)
Discussion started by: terron79
1 Replies

2. UNIX for Advanced & Expert Users

Need older version of System Firmware for 7026-H80

Hi all, I have an H80 that I'm migrating to 5.3 and prior to doing so it needed the firmware upgraded. I don't have copies of the old firmware that was on it since I was not the one who installed it and there were no copies to be found on the server itself. I installed the latest version and... (4 Replies)
Discussion started by: howardle
4 Replies

3. UNIX for Dummies Questions & Answers

Ibm 7026-h80

HAI GUYS Man have i had the worst time with this thing. Its 400kg and doesnt respond very well to my commands. I want to install linux or unix, dont really care, onto my IBM server. My problem is how? I more want to install the ubunut OS on to it, but have tried every iso installer... (1 Reply)
Discussion started by: benzies
1 Replies

4. AIX

LED Code

Anyone know what led code 626 means please. This is on a VIO server running vios 1.3.0.1-FP-8.1 and AIX 5.3 ML5. (8 Replies)
Discussion started by: johnf
8 Replies

5. Shell Programming and Scripting

code migration

Hi, I am working on migration project. thier are 50,000 scripts. As we are doing 70% of automization for changing the scripts. The remaining 30% doing manually. After doing manual changes i have to find the wheather the change is dont or not and also clode review process. Is there any... (2 Replies)
Discussion started by: unihp1
2 Replies

6. AIX

How to upgrade AIX5.3TL6-07 to AIX5.3TL8-04?

Hello All, After creating lpp_source/spot from AIX 5.3TL6-07 DVD on the NIM(AIX6.1), I went online and download the fix pack for reaching TL8-04. (it was less than 200Mgegs total) then I did define a newer lpp_source530TL8-04 via a copy from the older lpp_source530TL6-07 (I diduse a command... (2 Replies)
Discussion started by: sangers
2 Replies

7. HP-UX

C++ Code migration from HP Unix 11.11 to 11.31

i'm facing some problem to make my source code work in HP Unix 11.31 which works fine in HP Unix 11.11. Recently our unix server is upgraded to HP Unix 11.31, i was able to compile my source code successfully in 11.31 but i see some system call failure and socket failure. is there any steps to... (5 Replies)
Discussion started by: Madanxyz
5 Replies

8. AIX

IBM rs/6000 7026-c2

I have just purchased an old IBM RS/6000 7026-C2 with the intention of installing AIX 5.2 to do some testing. I have no AIX or RS/6000 experience, but I have managed to access the console/service menu through a hyper terminal console via the com port. I get the service processor menu and I can't... (12 Replies)
Discussion started by: AIX5.2
12 Replies

9. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
_lwp_mutex_lock(2)						   System Calls 						_lwp_mutex_lock(2)

NAME
_lwp_mutex_lock, _lwp_mutex_unlock, _lwp_mutex_trylock - mutual exclusion SYNOPSIS
#include <sys/lwp.h> int _lwp_mutex_lock(lwp_mutex_t *mp); int _lwp_mutex_trylock(lwp_mutex_t *mp); int _lwp_mutex_unlock(lwp_mutex_t *mp); DESCRIPTION
These functions serialize the execution of lightweight processes. They are useful for ensuring that only one lightweight process can exe- cute a critical section of code at any one time (mutual exclusion). LWP mutexes must be initialized to 0 before use. The _lwp_mutex_lock() function locks the LWP mutex pointed to by mp. If the mutex is already locked, the calling LWP blocks until the mutex becomes available. When _lwp_mutex_lock() returns, the mutex is locked and the calling LWP is the "owner". The _lwp_mutex_trylock() function attempts to lock the mutex. If the mutex is already locked it returns with an error. If the mutex is unlocked, it is locked and _lwp_mutex_trylock() returns. The _lwp_mutex_unlock() function unlocks a locked mutex. The mutex must be locked and the calling LWP must be the one that last locked the mutex (the owner). If any other LWPs are waiting for the mutex to become available, one of them is unblocked. RETURN VALUES
Upon successful completion, 0 is returned. A non-zero value indicates an error. ERRORS
If any of the following conditions are detected, _lwp_mutex_lock(), _lwp_mutex_trylock(), and _lwp_mutex_unlock() fail and return the cor- responding value: EINVAL The mp argument points to an invalid LWP mutex. EFAULT The mp argument points to an illegal address. If any of the following conditions occur, _lwp_mutex_trylock() fails and returns the corresponding value: EBUSY The mp argument points to a locked mutex. SEE ALSO
Intro(2), _lwp_cond_wait(2) SunOS 5.11 30 Jul 1992 _lwp_mutex_lock(2)
All times are GMT -4. The time now is 09:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy