11-06-2008
V490 - Centerplane failed
Hi all,
I'm freshman in this forum. I'm here to ask for your help. A case about Sun Fire V490. But, before starting to ask, I want to tell you the story.
Last week, I was told about a failed V490 in Da Nang City (Vietnam). It could NOT boot. After diagnosing it remotely, I found that the problem may be on the Centerplane Board. So, I took a Centerplane from a running V490 in Ho Chi Minh City and flied to Da Nang City. After replacing the centerplane, the V490 in Da Nang showed the errors :
1:0>ERROR: TEST = Run POST from Memory
1:0>H/W under test = CPU1, All CPU1 Memory
1:0>Repair Instructions: Replace items in order listed by 'H/W under test' above.
1:0>MSG = Incorrect checksum detected!!
Expected: ae51
Observed: 119
1:0>END_ERROR
It was NOT the errors before centerplane replacing.
OK. I called to Ha Noi City and they sent me another V490 the following day. I took the Centerplane from it and put it in the V490 in Da Nang. Problem was solved !
So, obviously, the centerplane caused the errors. But, it was abnormal when I take my Centerplane back to Ho Chi Minh City, put it in the V490 in my site, it showed exactly the errors I saw in Da Nang :
1:0>ERROR: TEST = Run POST from Memory
1:0>H/W under test = CPU1, All CPU1 Memory
1:0>Repair Instructions: Replace items in order listed by 'H/W under test' above.
1:0>MSG = Incorrect checksum detected!!
Expected: ae51
Observed: 119
1:0>END_ERROR
I don't know why and how this errors could occur ! Please advice !
Thank you very much !
10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
We've upgraded/migrated our production server from Sol 9 on a Sun V480 to Sol 10 on a V490 server.
How do I set/change the following values on Solaris 10:
Solaris 9:
$> locale
LANG=
LC_CTYPE=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LC_TIME=en_US.ISO8859-1... (2 Replies)
Discussion started by: dewets
2 Replies
2. Solaris
Hi,
How can I know slot wise info on a sun v480 box. I want to have the details like which slot has which card (slot 1- HBA, slot 2 - quad NIC) ..
I know that sysdef, prtconf or prtdiag outputs will help to get this. But I dont know how to conclude from those outputs. Can anybody help me to... (4 Replies)
Discussion started by: vasu2020
4 Replies
3. Solaris
After issuing reboot command (and disconnected from PuTTY), server is not even rebooted because ping test is succesful. So I connect to ALOM and issue poweroff command. After a minute, I did poweron and get this message (only).
rsc> poweron
Are you sure you want to turn your system power on... (10 Replies)
Discussion started by: Olli.Lang
10 Replies
4. Solaris
Hi community,
I'm currently working on Server SUN V490 and I'm connecting with a Serial Port. I've a problem with vi editor, in fact everytime I type " vi filename" the cursor moves in another direction and I unable to modify this file!!!
Could provide me a solution as soon as possible!!!... (3 Replies)
Discussion started by: Sunb3
3 Replies
5. Solaris
Hi,
I going to upgrade the firmware for sunfire v490 server, current fw level is 4.15.6 and to be upgraded to 4.30.
can anyone share the pre and post firmware upgrade activity procedure and backout plan
Thanks
rjs (2 Replies)
Discussion started by: rajasekg
2 Replies
6. Solaris
Hello,
Can any kind soul please answer this? I want to boot a SunFire v490 with a dvd image we use to boot v480's. Is this possible? Are there caveats to doing this?
Thanks muchly,
mgb (1 Reply)
Discussion started by: mgb
1 Replies
7. Solaris
My V490 has been running solid for months and I was studying the OBP diagnostics. I enabled the following;
auto-boot false
diag-level max
verbosoity max
diag-switch max
reset-all
The diagnostics are erring about 5 minutes in, and it keeps reporting the same error over and over, looking... (2 Replies)
Discussion started by: Pappy52
2 Replies
8. Solaris
What are the advantages for Sun Fire 490 over Sun Fire 480 R just from a server performance perspective? Or, are they both just about the same? (1 Reply)
Discussion started by: jtamminen
1 Replies
9. Solaris
Hi All,
Been a while since I touched a Solaris box so thought I would fire one up just to keep a hand in and I am amazed I have stumbled so early on. I am using a Sun v490, running latest patch of Solaris 10. The system shows the interfaces are configured (ifconfig netstat etc) but no IP is... (4 Replies)
Discussion started by: Diar
4 Replies
10. Solaris
Got a V490 with one existing root disk. Other disk slot was never populated.
Want to ensure we've got disk mirroring.
Currently vfstab mounts the physical disk - no mirroring set up.
Whats best way to achieve this without losing current disk? (1 Reply)
Discussion started by: psychocandy
1 Replies
LEARN ABOUT DEBIAN
sigwaittest
sigwaittest(8) sigwaittest(8)
NAME
sigwaittest - Start two threads or fork two processes and measure the latency between sending and receiving a signal
SYNTAX
sigwaittest [-a|-a PROC] [-b USEC] [-d DIST] [-f] [-i INTV] [-l loops] [-p PRIO] [-t|-t NUM]
DESCRIPTION
The program sigwaittest starts two threads or, optionally, forks two processes that are synchonized via signals and measures the latency
between sending a signal and returning from sigwait().
OPTIONS
-a, --affinity[=PROC]
Run on procesor number PROC. If PROC is not specified, run on current processor.
-b, --breaktrace=USEC
Send break trace command when latency > USEC. This is a debugging option to control the latency tracer in the realtime preemption
patch. It is useful to track down unexpected large latencies of a system.
-d, --distance=DIST
Set the distance of thread intervals in microseconds (default is 500 us). When cylictest is called with the -t option and more than
one thread is created, then this distance value is added to the interval of the threads: Interval(thread N) = Interval(thread N-1) +
DIST
-f, --fork
Instead of creating threads (which is the default), fork new processes
-i, --interval=INTV
Set the base interval of the thread(s) in microseconds (default is 1000 us). This sets the interval of the first thread. See also
-d.
-l, --loops=LOOPS
Set the number of loops. The default is 0 (endless). This option is useful for automated tests with a given number of test cycles.
sigwaittest is stopped once the number of timer intervals has been reached.
-p, --prio=PRIO
Set the priority of the process.
-t, --threads[=NUM]
Set the number of test threads (default is 1, if this option is not given). If NUM is specified, create NUM test threads. If NUM is
not specifed, NUM is set to the number of available CPUs.
EXAMPLES
The following example was running on a 4-way CPU:
# sigwaittest -a -t -p99 -i100 -d25 -l1000000
#0: ID11510, P99, CPU0, I100; #1: ID11511, P99, CPU0, Cycles 1000000
#2: ID11512, P98, CPU1, I125; #3: ID11513, P98, CPU1, Cycles 817484
#4: ID11514, P97, CPU2, I150; #5: ID11515, P97, CPU2, Cycles 668213
#6: ID11516, P96, CPU3, I175; #7: ID11517, P96, CPU3, Cycles 597344
#1 -> #0, Min 1, Cur 2, Avg 3, Max 30
#3 -> #2, Min 1, Cur 26, Avg 3, Max 42
#5 -> #4, Min 1, Cur 46, Avg 4, Max 67
#7 -> #6, Min 1, Cur 2, Avg 3, Max 74
AUTHORS
Carsten Emde <C.Emde@osadl.org>
SEE ALSO
kill(2), sigwait(3)
0.1 sigwaittest(8)