• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT
    Make New Entry, Make Followup Entry

    User name Pengjia

    Log entry time 10:54:01 on December 05, 2011

    Entry number 359563

    keyword=The problem of arbitration timeout for the intel cpu fastbus gone

    Yesterday ROC1 crate(intel cpu) have the problem of arbitration timeout(can not identify any tdc and adc slot), Ryan and I tried to reboot the crate several times and it is working right now, maybe it is the connection problem.

    I used tdc test code for check, the code is in /root/halla120/coda/linuxvme/sfi/test at root@hallavme15, the error is: JLAB SFI Tests ---------------------------- Opening A32 Window (opened at [0xb7f0b000,0xb7f1b000]) Opening A32Blt Window (opened at [0xadf0b000,0xb7f0b000]) Opening A24 Window (opened at [0xacf0b000,0xadf0b000]) Opening A16 Window (opened at [0xacefb000,0xacf0b000]) jlabgefMapTsi: Tempe Chip Userspace map successful VME Bus Error IRQ Disabled vmeBusCreateLockShm: vmeBus shared memory mutex created Address total free busy size incr (KBytes) Name ---------- ----- ---- ---- ----- ---- -------- ---- 0xb7f25000 1 1 0 3145784 0 (3073) vmeIN 0xb7f24000 0 0 0 56 0 (0) vmeOUT resetRegisterGroupLca2 = 0xadd0d01c FastbusTimeoutRegister = 0xadd0d000 FastbusdArbitrationLevelReg = 0xadd0d004 fastPrimDsr = 0xadd1b004 ERROR: Read Module ID, res=0x1c020 SFI_ADR_ERR: Fastbus Arbitration timeout ** Resetting Sequencer ** Closing A16 Window Closing A24 Window Closing A32Blt Window Closing A32 Window Calling gefVmeClose