08-03-2011
Maybe someone filled /tmp=swap, so malloc()/brk() was failing.
Maybe that link has some configuration parameter too high, tries to malloc() for 4GB in a 32 bit app.
Got all patches?
http://wesunsolve.net/bugid/id/6768523
Maybe the card is broken? Static discharge?
Last edited by DGPickett; 08-03-2011 at 01:45 PM..
9 More Discussions You Might Find Interesting
1. Solaris
All,
After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex... (2 Replies)
Discussion started by: jsandova
2 Replies
2. Solaris
Setting up a T5240 with two disks c1t0d0 and c1t1d0.
I am trying to use raidctl but when I issue.
raidctl -l
I get
Controller 1
Disk: 0.0.0
Disk: 0.1.0
So I try
raidctl -c '0.0.0 0.1.0' -r 1 1
and I get "Array in use."
I try (4 Replies)
Discussion started by: photon
4 Replies
3. Shell Programming and Scripting
Hello,
basically what this script is supposed to do is showing a list of hosts that is given a number, that you will be able to choose from a list.
A check is made to verify that the chosen number is within the array and this is where things go bad and I don't know why, bizarre.
I've spent... (5 Replies)
Discussion started by: gand
5 Replies
4. Solaris
its a fresh installation. during the OS setup, it did not prompt for IP, netmask and gateway. using Solaris 10 08/07 update 4. I tried to plumb manually but encountered no such interface error. but nxge interfaces can be greped from the /etc/path_to_inst file.
getting similar error on... (3 Replies)
Discussion started by: incredible
3 Replies
5. Solaris
I tried using raidctl earlier today to use my 2 disks in a RAID1 setup and I totally destroyed my OS install. I'm sure I did something funky and it freaked out. No big deal...right?
This is what I was seeing after a reboot.
I decided to just reinstall the OS. It let me go through all of... (3 Replies)
Discussion started by: kingdbag
3 Replies
6. Solaris
Hi,
We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions.
RJS (4 Replies)
Discussion started by: rajasekg
4 Replies
7. Solaris
Hi Friends
we have sun T5240 server, we have taken ufsdump of this server remotely with scsi tapedrive, If we need to do ufsrestore means what we have to do, since T5240 has not having scsi port, any procedure is there?
Regards
Rajasekar (5 Replies)
Discussion started by: rajasekg
5 Replies
8. Solaris
Hi !
I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before.
I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl.
... (2 Replies)
Discussion started by: delavega
2 Replies
9. Solaris
Hi Folks,
Just a quick question - hopefully!
I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
LEARN ABOUT OPENSOLARIS
device_remap
device_remap(1M) System Administration Commands device_remap(1M)
NAME
device_remap - administer the Solaris I/O remapping feature
SYNOPSIS
/usr/platform/sun4v/sbin/device_remap [-v | -R dir]
DESCRIPTION
Certain multi-node sun4v platforms, such as T5440 and T5240 servers, have an integrated PCI topology that cause the I/O device paths to
change in a CPU node failover condition. The device remapping script, device_remap, remaps the device paths in /etc/path_to_inst file and
the symlinks under /dev to match the hardware.
OPTIONS
The following options are supported:
-v
Displays the /etc/path_to_inst and /dev symlink changes.
-R dir
Perform remapping on the /etc/path_to_inst and /etc/path_to_inst files in the root image at dir.
USAGE
The primary function of device_remap is to remap the device paths in the /etc/path_to_inst file and the symlinks under /dev in a CPU node
failover condition to match the hardware.
After adding CPU node(s) or removing CPU node(s), boot the system to the OBP prompt and use the following procedure:
1. Boot either the failsafe miniroot using: boot -F failsafe , or an install miniroot using boot net -s or similar command.
2. Mount the root disk as /mnt.
3. Change directory to the mounted root disk:
# cd /mnt
4. Run device_remap script:
# /mnt/usr/platform/sun4v/sbin/device_remap
5. Boot the system from disk.
All the error messages are self-explanatory, except for the error message "missing ioaliases node" which means the firmware on the system
does not support device remapping.
EXAMPLES
Example 1 Displaying Changes Following Failover
The following command displays the path_to_inst and /dev changes following a CPU node failover.
# device_remap -v
Example 2 Changing Directory Prior to Any Changes
The following command changes the directory on which the boot image is mounted prior to making any changes.
# device_remap -R /newroot
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWkvm.v |
+-----------------------------+-----------------------------+
|Interface Stability |Unstable |
+-----------------------------+-----------------------------+
SEE ALSO
boot(1M), attributes(5)
SunOS 5.11 24 Dec 2008 device_remap(1M)