07-10-2012
Unplug power from Sparc Server T5440 when in OpenBoot
show /HOST command shows that
status = OpenBoot Running
when in this state, can the power be unplugged from the server ?
we are unable to bring the status to "powered off". Even if we issue "stop /SYS" it will momentarily be in the powered off status and then go back to power on status automatically.
Any help would be much appreciated.
8 More Discussions You Might Find Interesting
1. Programming
can anybody please tell that how can I use this software interrupt on
POWER and SPARC i.e. AIX and Sun Solaris
__asm("int3"); (2 Replies)
Discussion started by: jeet_xp
2 Replies
2. Red Hat
hi..
I unplug my eth0 lan cable.. and suddenly my system shutdown... no idea :eek::confused: (3 Replies)
Discussion started by: flekzout
3 Replies
3. Solaris
Hi All,
I recently had issues with my new T2000 server. I purchased a new mainboard and swapped the CPU and DIMMs to the new board. Now when i power on the server im unable to do so. I get the following error:
‘SC Alert: Host system poweron failed due to fault at MB/FF_POK.'
When i do... (2 Replies)
Discussion started by: Caully
2 Replies
4. Solaris
I need to add two new hard drives of 300 GB capacity to a SunSPARC T5440 server. The server currently has two hard drives of 146 GB each.
How do I add the new drives to the existing UFS?
What are the procedures involved in setting this server with the new hard drives? I am very new to Solaris... (6 Replies)
Discussion started by: ramatnmcc
6 Replies
5. UNIX for Advanced & Expert Users
i have doubt about how to power on server from remote location with out contacting with data center people? please anybody replay with whole info.
thank you. (3 Replies)
Discussion started by: bhaskerreddy.ch
3 Replies
6. Solaris
Hi all,
I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly.
Here is my server T5440 info:
... (6 Replies)
Discussion started by: insatiable1610
6 Replies
7. Solaris
SPARC Enterprise T5440 Server, can not power off
I connect to Service Processor via serial port and submit the following to boot the system, it boots fine but can not power off the system. Can someone help?
The following takes me to unix login
-> start /SYS
-> start /SP/console... (6 Replies)
Discussion started by: paulk93
6 Replies
8. Solaris
Hi all,
I have written the following program and run on both T5440 and T5220 on same OS version. I found that T5540 server takes more time than T5220. Please find below the details.
test1.cpp
#include <iostream>
#include <pthread.h>
using namespace std;
#define NUM_OF_THREADS 20... (17 Replies)
Discussion started by: sanjay_singh85
17 Replies
power(9E) Driver Entry Points power(9E)
NAME
power - power a device attached to the system
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
int prefixpower(dev_info_t *dip, int component, int level);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL
must be used in the cb_ops(9S) structure instead.
PARAMETERS
dip Pointer to the device's dev_info structure.
component Component of the driver to be managed.
level Desired component power level.
DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set
the power level of component to level.
The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is inter-
preted by the framework to mean "powered off," the interpretation of level is entirely up to the driver.
The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver.
When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a
requested power transition requires state to be restored, the driver must restore that state.
If a requested power transition for one component requires another component to change power state before it can be completed, the driver
must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered.
If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just
become busy), then the power level should not be changed and power should return DDI_FAILURE.
RETURN VALUES
The power() function returns:
DDI_SUCCESS Successfully set the power to the requested level.
DDI_FAILURE Failed to set the power to the requested level.
CONTEXT
The power() function is called from user or kernel context only.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S)
Writing Device Drivers
Using Power Management
SunOS 5.10 12 Dec 2003 power(9E)