Mon system shows high CPU
- VolkerHalle
- Topic Author
- Visitor
14 years 8 months ago #4920
by VolkerHalle
Replied by VolkerHalle on topic RE: Mon system shows high CPU
John,
thanks for the data
Are you actually running something, which could be generating that much interrupts ?
Please post SDA> PCS SHOW TRACE/STAT summary data, not the trace data itself.
Could you put the dump on a WO:R directory on EISNER:: and send me mail (EISNER::HALLE) ?
Please consider to run a quick test with PersonalAlpha to try and verify, if these seem to be OpenVMS or emulator related problems. Much less work than copying this system disk to your real Alpha...
Volker.<hr>
thanks for the data
Are you actually running something, which could be generating that much interrupts ?
Please post SDA> PCS SHOW TRACE/STAT summary data, not the trace data itself.
Could you put the dump on a WO:R directory on EISNER:: and send me mail (EISNER::HALLE) ?
Please consider to run a quick test with PersonalAlpha to try and verify, if these seem to be OpenVMS or emulator related problems. Much less work than copying this system disk to your real Alpha...
Volker.<hr>
Please Log in or Create an account to join the conversation.
- VolkerHalle
- Topic Author
- Visitor
14 years 8 months ago #4921
by VolkerHalle
Replied by VolkerHalle on topic RE: floating point implementation bug ?
John,
initial analysis of the MONITOR.DMP file indicates, that there should not have been a HPARITH trap, so this could be a floating point emulation problem in the emulator:
DBG> exa/ins @pc-20:@pc+10
SHARE$MONITOR_DATA2+147FC: LDQ_U R31,(SP)
SHARE$MONITOR_DATA2+14800: LDQ R19,#XF2C8(R2)
SHARE$MONITOR_DATA2+14804: LDS F10,#XF32C(R2)
SHARE$MONITOR_DATA2+14808: STL R31,(R19)
SHARE$MONITOR_DATA2+1480C: LDS F11,#XF378(R2)
SHARE$MONITOR_DATA2+14810: LDQ R20,#XF2C0(R2)
SHARE$MONITOR_DATA2+14814: BIS R31,R4,R16
SHARE$MONITOR_DATA2+14818: BIS R31,R3,R17
SHARE$MONITOR_DATA2+1481C: LDA R27,#XFE90(R2)
SHARE$MONITOR_DATA2+14820: DIVS/SU F11,F10,F12
SHARE$MONITOR_DATA2+14824: STS F12,(R20)
SHARE$MONITOR_DATA2+14828: TRAPB
SHARE$MONITOR_DATA2+1482C: BSR R26,#X0005D8
DBG> exa/s_float @r2+0fffff32c
SHARE$MONITOR_DATA0+714: 100.0000
DBG> exa/s_float @r2+0fffff378
SHARE$MONITOR_DATA0+760: 40.00000
DBG> exa/s_float f10
0\%F10: 100.0000
DBG> exa/s_float f11
0\%F11: 40.00000
DBG> exa/s_float f12
0\%F12: 0.4000000
DBG> exa f10
0\%F10: 100.000003814697
DBG> exa f11
0\%F11: 40.0000000000000
DBG> exa f12
0\%F12: 0.399999999642373
Dividing 100./40. should give about 0.4 and not report an HPARITH exception, so the correct execution of the DIVS/SU F11,F10,F12 instruction is most questionable.
And if you look at the value stored in F10, it looks 'suspicious':
DBG> exa/hex f10
0\%F10: 4059000010000000
DBG> exa f10
0\%F10: 100.000003814697
The instruction LDS F10,#XF32C(R2) can NOT have picked up that bit in the low-order longword.
The instruction stream matches with the Fmask=00001000 as reported in the exception (= F12 has been modified). Also summary=01 indicates Software Completion, which matches the /S flag.
Which version of FreeAXP are you using ?
Volker.<hr>
initial analysis of the MONITOR.DMP file indicates, that there should not have been a HPARITH trap, so this could be a floating point emulation problem in the emulator:
DBG> exa/ins @pc-20:@pc+10
SHARE$MONITOR_DATA2+147FC: LDQ_U R31,(SP)
SHARE$MONITOR_DATA2+14800: LDQ R19,#XF2C8(R2)
SHARE$MONITOR_DATA2+14804: LDS F10,#XF32C(R2)
SHARE$MONITOR_DATA2+14808: STL R31,(R19)
SHARE$MONITOR_DATA2+1480C: LDS F11,#XF378(R2)
SHARE$MONITOR_DATA2+14810: LDQ R20,#XF2C0(R2)
SHARE$MONITOR_DATA2+14814: BIS R31,R4,R16
SHARE$MONITOR_DATA2+14818: BIS R31,R3,R17
SHARE$MONITOR_DATA2+1481C: LDA R27,#XFE90(R2)
SHARE$MONITOR_DATA2+14820: DIVS/SU F11,F10,F12
SHARE$MONITOR_DATA2+14824: STS F12,(R20)
SHARE$MONITOR_DATA2+14828: TRAPB
SHARE$MONITOR_DATA2+1482C: BSR R26,#X0005D8
DBG> exa/s_float @r2+0fffff32c
SHARE$MONITOR_DATA0+714: 100.0000
DBG> exa/s_float @r2+0fffff378
SHARE$MONITOR_DATA0+760: 40.00000
DBG> exa/s_float f10
0\%F10: 100.0000
DBG> exa/s_float f11
0\%F11: 40.00000
DBG> exa/s_float f12
0\%F12: 0.4000000
DBG> exa f10
0\%F10: 100.000003814697
DBG> exa f11
0\%F11: 40.0000000000000
DBG> exa f12
0\%F12: 0.399999999642373
Dividing 100./40. should give about 0.4 and not report an HPARITH exception, so the correct execution of the DIVS/SU F11,F10,F12 instruction is most questionable.
And if you look at the value stored in F10, it looks 'suspicious':
DBG> exa/hex f10
0\%F10: 4059000010000000
DBG> exa f10
0\%F10: 100.000003814697
The instruction LDS F10,#XF32C(R2) can NOT have picked up that bit in the low-order longword.
The instruction stream matches with the Fmask=00001000 as reported in the exception (= F12 has been modified). Also summary=01 indicates Software Completion, which matches the /S flag.
Which version of FreeAXP are you using ?
Volker.<hr>
Please Log in or Create an account to join the conversation.
- malmberg
- Topic Author
- Visitor
14 years 8 months ago #4922
by malmberg
Replied by malmberg on topic RE: Mon system shows high CPU
The emulator claims:
x86 version 1.0 patch 6 build 271 (Apr 10 2010 21:04:10)
I also had a crash last night:
NETDLLERR, DECnet Datalink Layer detected a fatal error.
Looks like it occurred when the MacBook came out of power save state.
x86 version 1.0 patch 6 build 271 (Apr 10 2010 21:04:10)
I also had a crash last night:
NETDLLERR, DECnet Datalink Layer detected a fatal error.
Looks like it occurred when the MacBook came out of power save state.
Please Log in or Create an account to join the conversation.
- VolkerHalle
- Topic Author
- Visitor
14 years 8 months ago #4923
by VolkerHalle
Replied by VolkerHalle on topic RE: please send CLUE file from crash
John,
could you also send me the CLUE file from the crash (CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS) for analysis.
Volker.
could you also send me the CLUE file from the crash (CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS) for analysis.
Volker.
Please Log in or Create an account to join the conversation.
- Bruce Claremont
- Topic Author
- Visitor
14 years 8 months ago #4924
by Bruce Claremont
Replied by Bruce Claremont on topic RE: Mon system shows high CPU
We have just posted FreeAXP 283. It corrects a floating point bug that may impact Monitor behavior. Visit the FreeAXP page for download, documentation, and forum links:
<center> www.FreeAXP.com </center>
<center> www.FreeAXP.com </center>
Please Log in or Create an account to join the conversation.
- malmberg
- Topic Author
- Visitor
14 years 8 months ago #4925
by malmberg
Replied by malmberg on topic RE: Mon system shows high CPU
I removed SRI IDLE and that solved the excessive CPU problem.
Please Log in or Create an account to join the conversation.
Moderators: iamcamiel
Time to create page: 0.188 seconds