TRX is not responding error message

Hi One of our nanoBTSs startet to reboot very frequently. The debug telnet console shows this error: 12168:WARN:OAM_RES:res_trx_status.c#231:TRX is not responding - reinitialising the unit... 13251:DBG:OAM_IM:Stopping "Primary OML Fallback Client" > 13251:DBG:OAM_IM:Stopping "Secondary OML Server" > 13251:DBG:OAM_IM:Stopping "Secure Secondary OML Server" 13252:DBG:OAM_IM:Not stopping "IML Site Server" - has not been started 13252:DBG:OAM_IM:Not stopping "Secure IML Site Server" - has not been started 13252:DBG:OAM_IM:Stopping "IML Bts Server" > 13252:DBG:OAM_IM:Stopping "Secure IML Bts Server" 13252:DBG:OAM_IM:Stopping "IRL Patched Routing Link" 13252:DBG:OAM_IM:Failed to inject event=1="STOP" into link source (token=9) 13284:DBG:IP_CHAN_SERVER:Closed server listening on port 3006 > 13284:DBG:IP_CHAN_SERVER:Closed server listening on port 3026> 13285:DBG:IP_CHAN_SERVER:Closed server listening on port 3014> 13285:DBG:IP_CHAN_SERVER:Closed server listening on port 3034> 13458:DBG:IP_CHAN_RX_A:15190:ipChanConn: EVENT 0x00001743 rxd in STATE connected 13458:DBG:IP_CHAN_RX_A:15191:ipChanConn: EVENT 0x00001741 rxd in STATE disconnectclosing here is the output of openBSC <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) <0005> abis_nm.c:1970 Set Chan Attr (bts=0,trx=0,ts=7) <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) Software Activated Report <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) Software Activated Report <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=Dependency(05) ADM=Unlocked <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) IPACCESS(0xe1): RSL CONNECT ACK IP=192.168.0.1 PORT=3003 STREAM=0x00 <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) STATE CHG: OP_STATE=Disabled AVAIL=OK(ff) ADM=Unlocked <0005> abis_nm.c:518 OC=RADIO-CARRIER(02) INST=(00,00,ff) Sending OPSTART <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,00) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,01) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,02) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,03) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,04) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,05) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,06) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=CHANNEL(03) INST=(00,00,07) CHANGE ADMINISTRATIVE STATE NACK CAUSE=Message cannot be performed <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=processing failure Severity=warning level failure <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=processing failure Severity=warning level failure <0005> abis_nm.c:518 OC=BASEBAND-TRANSCEIVER(04) INST=(00,00,ff) Failure Event Report Type=processing failure Severity=warning level failure Another nanoBTS with same firmware and config works perfekt with the same openBTS installation. Switching to the second firmware bank and flashing a different firmware didnt solve the problem. Any hint where to look for more information ? mfg Peter