()ý
Home
Ȩ ȸҰ ý Ʈ ũ
 
 
ۼ : 06-02-28 09:59
ý ди޽ Score05/Score95
 ۾ :
ȸ : 7,692  
ý ди޽ score05/score95
ýۿ д ߻ϸ鼭 ɶ ֽϴ.
Ѱ м ؼ Ʒ ġ鿡 ߰
ֽϴ.

Solaris 2.5.1 : 103640-34
Solaris 2.6 : 105181-23
Solaris 7 : 106541-13
Solaris 8 : 108528-04

Ʒ ޼ ڼ ø (score 05) κ ֽϴ.
̰ ġ 쿡 Ÿ ޼
޼ Ÿ CPU д Ѱ ο
100 ġ ݴϴ.  05 95
׻ 05 95 ߿ ϳ
˴ϴ.(score 05: д , score 95: д /ü )

WARNING: [AFT1] Uncorrectable Memory Error on CPU10 Data access at TL=0, errID 0
x000db615.44f55a6b
    AFSR 0x00000000.80200000<PRIV,UE> AFAR 0x00000000.490b9038
    AFSR.PSYND 0x0000(score 05) AFSR.ETS 0x00 Fault_PC 0x10034be8
    UDBH 0x0000 UDBH.ESYND 0x00 UDBL 0x0203<UE> UDBL.ESYND 0x03
    UDBL Syndrome 0x3 Memory Module Board 5 J3100 J3200 J3300 J3400 J3500 J3600
J3700 J3800

AFSR(Asynchronous Fault Status Register) Ǿ ִ
Ʈ ǰϿ ˴ϴ.  CPU CPU Ÿ
ְ ϵ/Ʈ
Ÿ ϰἺ ֽϴ.  Ÿ ߰ϸ
׶ Ȳ AFSR Ϳ Ʈ õ˴ϴ.
(80200000 = 10000000001000000000000000000000)

AFSR Ȯ  CPU Ÿ û߰  CPU
Ÿ Ȯ ֽϴ.  Ÿ
û CPU ҷ ƴϰ. ׷ 32Ʈ ׻ Ȯ
ʵ Ͼ ϰ ϱ ؼ ý
д õǸ鼭 ü м ؼ ִ Դϴ.

ýۿ д ߻ д ޼ ڼ Ȯ ñ ٶϴ.
AFSR 0x00000000.######## ޼ ִ ȮϽð
ִٸ ýۿ ü м (score ##) ȮϽñ ٶϴ.

/var/adm/messages Ǵ

# adk -k unix.0 vmcore.0
$<msgbuf

ؼ ȮϽ ֽϴ.


1) CPU10 ü

WARNING: [AFT1] WP event on CPU10, errID 0x000d99f1.038e8d48
    AFSR 0x00000000.00800400<WP> AFAR 0x000001c4.f8800030
    AFSR.PSYND 0x0400(score 95) AFSR.ETS 0x00 Fault_PC 0x100826b0
    UDBH 0x0000 UDBH.ESYND 0x00 UDBL 0x0000 UDBL.ESYND 0x00
WARNING: [AFT1] Uncorrectable Memory Error on CPU11 Data access at TL=0, errID 0
x000d99f2.1f00daa0
    AFSR 0x00000000.80200000<PRIV,UE> AFAR 0x00000000.7ae96330
    AFSR.PSYND 0x0000(score 05) AFSR.ETS 0x00 Fault_PC 0x10027214
    UDBH 0x0203<UE> UDBH.ESYND 0x03 UDBL 0x0051 UDBL.ESYND 0x51
    UDBH Syndrome 0x3 Memory Module Board 5 J3100 J3200 J3300 J3400 J3500 J3600
J3700 J3800
WARNING: [AFT1] errID 0x000d99f2.1f00daa0 Syndrome 0x3 indicates that this may n
ot be a memory module problem
[AFT2] errID 0x000d99f2.1f00daa0 PA=0x00000000.7ae96330
    E$tag 0x00000000.1cc00f5d E$State: Exclusive E$parity 0x0e
[AFT2] E$Data (0x00): 0x7017d0e8.00000000
[AFT2] E$Data (0x08): 0x11594340.11594240
[AFT2] E$Data (0x10): 0x11594300.11594300
[AFT2] E$Data (0x18): 0x00000000.206f0000
[AFT2] E$Data (0x20): 0x00000000.00010000
[AFT2] E$Data (0x28): 0x00000000.00000000
[AFT2] E$Data (0x30): 0x00000000.00035271 *Bad* PSYND=0xff00
[AFT2] E$Data (0x38): 0x030208c0.00000000
[AFT3] errID 0x000d99f2.1f00daa0: cannot schedule clearing of error on page 0x00
000000.7ae96000; page not in VM system
[AFT3] errID 0x000d99f2.1f00daa0 Above Error detected by protected Kernel code
    that will try to clear error from system
WARNING: [AFT1] Uncorrectable Memory Error on CPU11 Data access at TL=0, errID 0
x000d99f2.21d007bc
    AFSR 0x00000000.80200000<PRIV,UE> AFAR 0x00000000.7ae96330
    AFSR.PSYND 0x0000(score 05) AFSR.ETS 0x00 Fault_PC 0x10027214
    UDBH 0x0203<UE> UDBH.ESYND 0x03 UDBL 0x0051 UDBL.ESYND 0x51
    UDBH Syndrome 0x3 Memory Module Board 5 J3100 J3200 J3300 J3400 J3500 J3600
J3700 J3800
WARNING: [AFT1] errID 0x000d99f2.21d007bc Syndrome 0x3 indicates that this may n
ot be a memory module problem
[AFT2] errID 0x000d99f2.21d007bc PA=0x00000000.7ae96330
    E$tag 0x00000000.1cc00f5d E$State: Exclusive E$parity 0x0e
[AFT2] E$Data (0x00): 0x7017d0e8.00000000
[AFT2] E$Data (0x08): 0x11594340.11594240
[AFT2] E$Data (0x10): 0x11594300.11594300
[AFT2] E$Data (0x18): 0x00000000.206f0000
[AFT2] E$Data (0x20): 0x00000000.00010000
[AFT2] E$Data (0x28): 0x00000000.00000000
[AFT2] E$Data (0x30): 0x00000000.00035271 *Bad* PSYND=0xff00
[AFT2] E$Data (0x38): 0x030208c0.00000000
[AFT3] errID 0x000d99f2.21d007bc: cannot schedule clearing of error on page 0x00
000000.7ae96000; page not in VM system
[AFT3] errID 0x000d99f2.21d007bc Above Error detected by protected Kernel code
    that will try to clear error from system
WARNING: [AFT1] errID 0x000d99f5.a9d4e269 Syndrome 0x3 indicates that this may n
ot be a memory module problem
[AFT2] errID 0x000d99f5.a9d4e269 PA=0x00000000.7ae96330
    E$tag 0x00000000.1cc00f5d E$State: Exclusive E$parity 0x0e
[AFT2] E$Data (0x00): 0x7017d0e8.00000000
[AFT2] E$Data (0x08): 0x11594340.11594240
[AFT2] E$Data (0x10): 0x11594300.11594300
[AFT2] E$Data (0x18): 0x00000000.206f0000
[AFT2] E$Data (0x20): 0x00000000.00010000
[AFT2] E$Data (0x28): 0x00000000.00000000
[AFT2] E$Data (0x30): 0x00000000.00035271 *Bad* PSYND=0xff00
[AFT2] E$Data (0x38): 0x030208c0.00000000
syncing file systems...panic[cpu10]/thread=40077e60: panic sync timeout
dumping to /dev/dsk/c0t0d0s1, offset 839122944

2) CPU 14 ü

WARNING: [AFT1] Uncorrectable Memory Error on CPU10 Data access at TL=0, errID 0
x000db615.44f55a6b
    AFSR 0x00000000.80200000<PRIV,UE> AFAR 0x00000000.490b9038
    AFSR.PSYND 0x0000(score 05) AFSR.ETS 0x00 Fault_PC 0x10034be8
    UDBH 0x0000 UDBH.ESYND 0x00 UDBL 0x0203<UE> UDBL.ESYND 0x03
    UDBL Syndrome 0x3 Memory Module Board 5 J3100 J3200 J3300 J3400 J3500 J3600
J3700 J3800
WARNING: [AFT1] errID 0x000db615.44f55a6b Syndrome 0x3 indicates that this may n
ot be a memory module problem
[AFT2] errID 0x000db615.44f55a6b PA=0x00000000.490b9038
    E$tag 0x00000000.0fc00921 E$State: Modified E$parity 0x07
[AFT2] E$Data (0x00): 0x00000000.701d7b24
[AFT2] E$Data (0x08): 0x00000000.baddcafe
[AFT2] E$Data (0x10): 0x00000000.00000000
[AFT2] E$Data (0x18): 0x728f4f20.728f4f20
[AFT2] E$Data (0x20): 0x00000000.00000000
[AFT2] E$Data (0x28): 0x00000000.00000000
[AFT2] E$Data (0x30): 0x00000000.baddcafe
[AFT2] E$Data (0x38): 0x00000000.00100000 *Bad* PSYND=0x00ff
WARNING: [AFT1] CP event on CPU14 (caused Data access error on CPU10), errID 0x0
00db615.44f55a6b
    AFSR 0x00000000.01000004<CP> AFAR 0x00000000.490b9038
    AFSR.PSYND 0x0004(score 95) AFSR.ETS 0x00
    UDBH 0x0000 UDBH.ESYND 0x00 UDBL 0x00c8 UDBL.ESYND 0xc8
WARNING: [AFT2] errID 0x000db615.44f55a6b No cache dump available
panic[cpu10]/thread=701d7b20: [AFT1] errID 0x000db615.44f55a6b UE Error(s)
    See previous message(s) for details
syncing file systems...WARNING: tmp_putapage: err 5

  [21] 4WARNING: tmp_putapage: err 5

  [21] 2panic[cpu10]/thread=40077e60: panic sync timeout
dumping to /dev/dsk/c0t0d0s1, offset 839122944



-----------------------------------------------------------------------------------------

The 2 pieces of info that you need to concern yourself with are:
WP event on CPU1
(score 95)

This means it is 95% likely that CPU1 was responsible for the "event" due to a WP event (Writeback Parity error). Sun's Best Practices would have you "log" CPU1 on the first occurance and replace it if it re-occured on CPU1 within 6 months. Otherwise, do nothing.

 
 

Total 185
ȣ     ۾ ¥ ȸ
125 solaris 10 sendmail online
2010/05/14 6997
124 disksuite mirror .....
2005/12/12 7068
123 solaris system å
2006/10/10 7069
122 growfs - ũ Ȯ
2008/01/10 7101
121 E3500 CPU board ü ߻ error message
2008/03/25 7111
120 cpio .
2006/04/06 7267
119 v210 Feb 16 09:33:07 backup rmclomv: [ID 211032 kern.error]
2006/02/16 7364
118 disksuite mirror .....
2005/12/12 7429
117 vmstat --- ý .
2006/11/01 7430
116 E3500 400Mhz/8M Cache CPU
2006/09/14 7452
115 /usr/lib/im/htt -port 9010 -syslog -message_locale C ǹ/.
2006/02/06 7478
114 E3500 FC on & off line
2008/04/29 7549
113 sunblade 1000 µ Ͽ ý
2008/02/14 7607
112 ֶ󸮽 7 , 8 , 9 , 10
2005/12/13 7670
111 ý ди޽ Score05/Score95
2006/02/28 7693
 1  2  3  4  5  6  7  8  9  10    
 
 
 
Administrator Login