Fusion Utilization ImprovementFusion Utilization Improvement
Gap improvement in Standby Time Analsys from ACS.
Fusion in FTF by C.S.Tu
All down mode AnalysisAll down mode Analysis
All downmode analsys in Aug,2002 .
7 Type當13%
6 系統當11%
3 Standby7%
4 Calibration9%
5 Engineering工11%
10 Other8%
8 Handler Down5%
13 Unstable14%
11 Change Type5%
18 ACS Down0%
14 Handler Unstable1%
2 No record of downUnknown down
16%
Compared with all down rates ,unknown down is the top one .
Compared with standby time Compared with standby time
Standby Time Status in Aug, 2002
Small down27%
Idle7%
Others10%
Handler/Prober Cal./PM
0%
Unknowndown34% Handler/
Prober down6%
Type down16%
1.Unknow down occupy 34% of standby time.
2.Small down occupy 27% of standby time.
.
Small down HappenSmall down Happen
1.It happen when production stop over 2 minutes.
2.Each problem happened will casue small
stop first, why ?
Small stopACS
Unknownstop
System down
Handler down
?Type down
orWhen do you found problem ?
t
Small down v.s OthersSmall down v.s OthersThe relativity of top six down modes .
Small down 27%
Unknow down 34% System Down
TypeDown 16%Handler
downOther &Idle 7%
Type Down AnalysisType Down Analysis OneC 4058XH have more problem with Fusion.
VP223445%
VP405542%
VP4058135%
VP405846%
OM635X15%
PCD80XXH13%
PCF506011%
PCF508729%
PCF8775014%
System Down System Down
Hardware fail :
PECHF,FARMNT,DPS,PSCM…
Hang problem.
Hardware hang, bad die hang &
software hang …
System Down AnalysisSystem Down Analysis
System Down in Aug, 2002
summary out22%
PowerCut2%
Teste down11%
Vaccum Source1%
Tester Hang64%
75% Casued by printer without paper ,and wait for processing (hang).
Compared with system down.
Handler Down Handler Down TESEC handlers loader have more problem 38% in Aug.
Handler down in Aug,2002
Pin bend problem6%
Socket problem0%
Peripheral problemofhandler
4%Index abnormal
20%
Handler temperatureproblem
7%
Handler test areaproblem
6%
Unloader problem19%
Loader problem38%
Unknown Down Unknown Down
Unknow down occupy 34% of standby time in ACS.
Why we don’t know it down ?
No one found it .
No down happened .
or Other …
Cause Analysis & Team membersCause Analysis & Team members
UnknowStop from handler
Unknow Stop from Type
Unknow Stop from System
Small Stop
OneC have more 40%Of type down 13%:40581H occupy 35%
(40575 WT)40584 6%
Om635X 15%
Handler down 5%And Unstable 1%
Loader problem occupy38% of all handler
problem
System down have 11% of all down mode:Hang have 64 % of
system down.
C.S TuPeace LinJ.R Wang
Hang problem Hang problem Production hang . Double dataviewers casue test time longer.
(Need support from System,C.S.Tu and Vendor)
MS_Dlog could not worte (OneC DC log). (Need support from CSTD, Peace.Lin & BL)
Fail die casue hang (OneC). (Need support from CSTD. Peace.Lin & BL)
Hardware hang . Load board casued it hung when failed TXD1. (Need support from CSTD. Peace.Lin )
Hardware configuration miss. (Need support from System,C.S.Tu and Vendor)
Secondary dataviewers problemSecondary dataviewers problem Why Fusion processes have two dataviewers? 1. Normally only one work with optool , but when test program was unloaded , it still exited .Next launcher command be run , a new dataviewer will popup. 2. It casue test time longer than default for all types. For example : OneC > 1.5 times (normally dual sites 8.5sec ,become 12.8sec , but not always)
3. It influence output . 4. A bug of OS.
Two dataviewers delay test time Two dataviewers delay test time ==== :fusion12 dataviewer monitor : =============================prod 1529 1 50 19:52:07 ? 236:51 dataviewer -name DataViewerDefault:prod:1480:head_1 -tester fusion12 -head 1prod 6240 6190 0 10:24:22 ? 0:01 dataviewer -name DataViewerDefault:prod:6190:head_1 -tester fusion12 -head 1prod 6190 1 0 10:24:14 ? 0:03 optool -head 1 -load /tp/devices/vp40581h_R1084/V09/Prog/vp40581H_V09.eva \time Thu Jul 25 11:10:21 CST 2002==== :fusion09 dataviewer monitor : =============================preprod 18666 1 50 15:37:56 ? 314:31 dataviewer -name DataViewerDefault:preprod:18628:head_1 -tester fusion09 -head prod 22120 22072 0 05:49:49 ? 0:02 dataviewer -name DataViewerDefault:prod:22072:head_1 -tester fusion09 -head 1prod 22072 1 0 05:49:40 ? 0:13 optool -head 1 -load /tp/devices/pcf50872_R1084/V1E/019/Prog/pcf50872-V1E_019.e Thu Jul 25 11:10:32 CST 2002==== :fusion13 dataviewer monitor : =============================envdiag 11442 11428 0 09:15:22 pts/3 0:07 dataviewer -name DataViewerDefault:envdiag:11428:head_1 -tester fusion13 -head prod 9532 1 42 16:10:57 ? 829:14 dataviewer -name DataViewerDefault:prod:9482:head_1 -tester fusion13 -head 1prod 10499 1 32 18:52:10 ? 90:37 dataviewer -name DataViewerDefault:prod:10449:head_1 -tester fusion13 -head 1
This the one caused longer test time in Fusion .
This the one caused longer test time in Fusion .
How serious is it ?How serious is it ?
Users Happen Times
Week\User Prod Envdiag Preprod Pre_vlsi Str Vlsi Pre_3gsm Others
Week227 27 4 3 1 3 1 2 2
Week228 32 7 5 0 2 0 1 1
Week229 20 5 2 0 5 1 1 0
Week230 25 1 3 0 1 1 1 1
July,2002 total 104 17 13 1 11 3 5 4
Users Happen Times
Week\User Prod Envdiag Preprod Pre_vlsi Str Vlsi Pre_3gsm Others
Week227 27 4 3 1 3 1 2 2
Week228 32 7 5 0 2 0 1 1
Week229 20 5 2 0 5 1 1 0
Week230 25 1 3 0 1 1 1 1
July,2002 total 104 17 13 1 11 3 5 4
• FTF would have more problems than WTF, because it happened
when one exit optool after unload TP .
These with records!!!
The result after using pkill before PlThe result after using pkill before Pload oad
Short-term solution :
a .Kill the process before next optool popup automatically .
b. Two dataviewer prevention process was execute in Aug,2002 week 231.
Long-term solution :
Vendor’s SPR and improvement of OS are necessary.
Week\User Prod Envdiag Preprod Pre_vlsi Str Vlsi Pre_3gsm* Week231(Aug/1 ) 9 1 2 0 1 0 1
Week232 6 1 1 0 0 0 0Week233 4 0 2 0 0 0 1Week234 0 0 1 0 0 0 0Week235 0 1 1 0 0 0 0July total 19 3 7 0 1 0 2
Improvement result and TargetImprovement result and Target
Dataviewer casue long test time
1713
1
113 5 43 0 1 0 2 2
104
7
19
0
20
40
60
80
100
120
User account
SecondaryDataviewer
happenTimes
No Pkill 104 17 13 1 11 3 5 4
Pkill 19 3 7 0 1 0 2 2
Prod Envdiag Preprod Pre_vlsi Str Vlsi Pre_3gsm Others
• Finally target is no secondary dataviewer found .
• Compared to with pkill and without pkill.