1. Fusion Utilization Improvement
Gap improvement in Standby Time
Analsys from ACS.
Fusion in FTF by C.S.Tu

2. All down mode Analysis
Compared with all down rates ,unknown down is the top one .
All downmode analsys in Aug,2002 .
13 Unstable 14 Handler Unstable 2 No record of down
18 ACS Down
14% 1% Unknown down
0%
16%
11 Change Type
5%
3 Standby
10 Other 7%
8%
8 Handler Down 4 Calibration
5% 9%
7 Type當
13% 5 工Engineering
6 系統當
11% 11%

3. Compared with standby time
1.Unknow down occupy 34% of standby time.
2.Small down occupy 27% of standby time.
. Standby Time Status in Aug, 2002
Others Idle
Handler/Prob
10% 7%
er Cal./PM
0% Small down
27%
Unknown
down
34% Handler/ Type down
Prober down 16%
6%

4. Small down Happen
1.It happen when production stop over 2
minutes.
2.Each problem happened will casue small
stop first, why ?
System down
Handler down
ACS
Small
stop
Unknown
stop ? Type down
t
When do you found problem ? or

5. Small down v.s Others
 The relativity of top six down modes .
Unknow down 34% System Down
Small down 27%
Handler
TypeDown 16% down
Other &
Idle 7%

6. Type Down Analysis
OneC 4058XH have more problem with Fusion.
VP40584 OM635X
6% 15%
PCD80XXH
13%
VP40581
35%
PCF50601
1%
VP40554 PCF50872
2% VP22344 9%
PCF87750
5%
14%

7. System Down
 Hardware fail :
PECHF,FARMNT,DPS,PSCM…
 Hang problem.
Hardware hang, bad die hang &
software hang …

8. System Down Analysis
System Down in Aug, 2002
Power
75% Casued by printer
without paper ,and summary out Cut
wait for processing 22% 2%
(hang). Compared with
system down.
Tester Hang
Teste down
64%
11%
Vaccum Source
1%

9. Handler Down
 TESEC handlers loader have more problem 38% in Aug.
Handler down in Aug,2002
Peripheral problem Socket problem
ofhandler 0%
4%
Index abnormal Pin bend problem
20% 6%
Handler temperature
problem
7%
Loader problem
Handler test area 38%
Unloader problem
problem
19%
6%

10. 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 …

11. Cause Analysis & Team members
Small Stop
UnknowStop Unknow Stop Unknow Stop
from handler from Type from System
OneC have more 40%
Handler down 5% System down have 11%
Of type down 13%:
And Unstable 1% 40581H occupy 35% of all down mode:
Loader problem occupy (40575 WT) Hang have 64 % of
38% of all handler 40584 6% system down.
problem Om635X 15%
J.R Wang Peace Lin C.S Tu

12. 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)

13. Secondary 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.

14. 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 1
prod 6240 6190 0 10:24:22 ? 0:01 dataviewer -name DataViewerDefault:prod:6190:head_1 -tester fusion12 -head 1
prod 6190 1 0 10:24:14 ? 0:03 optool -head 1 -load /tp/devices/vp40581h_R1084/V09/Prog/vp40581H_V09.eva time
This the one caused longer test time in Fusion .
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 1
prod 22072 1 0 05:49:40 ? 0:13 optool -head 1 -load /tp/devices/pcf50872_R1084/V1E/019/Prog/pcf50872-V1E_019.e
This the one caused longer test time in Fusion .
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 1
prod 10499 1 32 18:52:10 ? 90:37 dataviewer -name DataViewerDefault:prod:10449:head_1 -tester fusion13 -head 1

15. How serious is it ?
• FTF would have more problems than WTF, because it happened
when one exit optool after unload TP .
Users Happen Times
WeekUser 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
These with records!!!

16. The result after using pkill before
 Short-term solution :
Pload
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 0
Week233 4 0 2 0 0 0 1
Week234 0 0 1 0 0 0 0
Week235 0 1 1 0 0 0 0
J uly to ta l 19 3 7 0 1 0 2

17. Improvement result and Target
• Compared to with pkill and without pkill.
Dataviewer casue long test time
120
104
100
Secondary
80
Dataviewer
happen 60
Times
40
19 17
13 11
20 3
7
3 5 2 4 2
1 0 1 0
0
Prod Envdiag Preprod Pre_vlsi Str Vlsi Pre_3gsm Others
No Pkill 104 17 13 1 11 3 5 4
Pkill 19 3 7 0 1 0 2 2
User account
• Finally target is no secondary dataviewer found .