10-05-2009
it's memory errors...
look to me like it maybe in CPU cache.
cediag is the SUN tool that can decode the messages.
10 More Discussions You Might Find Interesting
1. Solaris
Got an curious issue.
I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on.
The patch modified mainly the linker libraries and commands.
... (2 Replies)
Discussion started by: BOFH
2 Replies
2. Solaris
Hello,
I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies
3. Solaris
Hi Guyz,
I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso.
When trying to boot at the ok> boot cdrom
i get the following error:
-----------------------------------------------------------------------
Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies
4. Solaris
First of all it's shut down 60 second after power on and write on console :
SC Alert: Correct SCC not replaced - shutting managed system down!
This is cured by moving out battery from ALOM card.
Now server start to loop during the testing.
That's on the console:
>@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies
5. Solaris
Hi,
I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection.
... (0 Replies)
Discussion started by: jimmy54321
0 Replies
6. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
7. Solaris
Dear Team,
I need some expert advice to my problem.
We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies
8. Solaris
Hi,
I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken.
Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies
9. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
10. Solaris
Hi,
I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error:
WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1):
SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
LEARN ABOUT DEBIAN
stressapptest
STRESSAPPTEST(1) General Commands Manual STRESSAPPTEST(1)
NAME
stressapptest - stress test application for simulating high load situations
SYNOPSIS
stressapptest [options]
DESCRIPTION
This manual page documents briefly the stressapptest command.
stressapptest (unix name for Stressful Application Test) is a program that tries to maximize randomized traffic to memory from processor
and I/O, with the intent of creating a realistic high load situation in order to test the existing hardware devices in a computer.
OPTIONS
This program supports the following options:
-A Run in degraded mode on incompatible systems.
-C <threads>
Number of memory CPU stress threads to run.
-d <device>
Add a direct write disk thread with block device (or file) 'device'.
-f <filename>
Add a disk thread with tempfile 'filename'.
-F Don't result check each transaction.
-i <threads>
Number of memory invert threads to run.
-l <logfile>
Log output to file 'logfile'.
-m <threads>
Number of memory copy threads to run.
-M <mbytes>
Megabytes of RAM to test.
-n <ipaddr>
Add a network thread connecting to system at 'ipaddr'.
-p <pagesize>
Size in bytes of memory chunks.
-s <seconds>
Number of seconds to run.
-v <level>
Verbosity (0-20), default is 8.
-W Use more CPU-stressful memory copy.
--blocks-per-segment <number>
Number of blocks to read/write per segment per iteration (-d).
--cache-size <size>
Size of disk cache (-d).
--cc_inc_count <number>
Number of times to increment the cacheline's member.
--cc_line_count <number>
Mumber of cache line sized datastructures to allocate for the cache coherency threads to operate.
--cc_test
Do the cache coherency testing.
--destructive
Write/wipe disk partition (-d).
--filesize <size>
Size of disk IO tempfiles.
--findfiles
Find locations to do disk IO automatically.
--force_errors
Inject false errors to test error handling.
--force_errors_like_crazy
Inject a lot of false errors to test error handling.
--listen
Run threads that listen for incoming net connections.
--local_numa
Choose memory regions associated with each CPU to be tested by that CPU.
--max_errors <number>
Exit early after finding specified number of errors.
--monitor_mode
Only do ECC error polling, no stress load.
--no_errors
Run without checking for ECC or other errors.
--paddr_base <address>
Allocate memory starting from this address.
--pause_delay <seconds>
Delay (in seconds) between power spikes.
--pause_duration <seconds>
Duration (in seconds) of each pause.
--random-threads <number>
Number of random threads for each disk write thread (-d).
--read-block-size <size>
Size of block for reading (-d).
--read-threshold <time>
Maximum time (in us) a block read should take (-d).
--remote_numa <time>
Choose memory regions not associated with each CPU to be tested by that CPU.
--segment-size <size>
Size of segments to split disk into (-d).
--stop_on_errors
Stop after finding the first error.
--write-block-size <size>
Size of block for writing (-d). If not defined, the size of block for writing will be defined as the size of block for reading.
--write-threshold <time>
Maximum time (in us) a block write should take (-d).
SEE ALSO
http://code.google.com/p/stressapptest/
AUTHOR
stressapptest was written by Nick Sanders and Rapahel Menderico (Google Inc).
This manual page was written by Michael Prokop <mika@debian.org> for the Debian project (and may be used by others).
2009-10-20 STRESSAPPTEST(1)