Menu

some error when my phone connects to openlte

Jennifer
2015-11-06
2018-07-17
  • Jennifer

    Jennifer - 2015-11-06

    Hi,
    I tried to connect my commercial phone(HTC) to openlte but failed. I ran "telnet 127.0.0.1 30001" on a terminal and it printed lots of error information as following:
    Trying 127.0.0.1...
    Connected to 127.0.0.1.
    Escape character is '^]'.
    11/06/2015 16:09:17.000589 info iface LTE_fdd_enb_interface.cc 771 LTE FDD ENB DEBUG INTERFACE
    11/06/2015 16:09:20.703199 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_phy circular buffer empty on receive
    11/06/2015 16:09:20.773688 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_phy circular buffer empty on receive
    11/06/2015 16:09:20.973697 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_phy circular buffer empty on receive
    11/06/2015 16:09:20.973752 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_phy circular buffer empty on receive
    11/06/2015 16:09:21.446302 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (685) does not match PHY (695)
    11/06/2015 16:09:21.447156 error phy LTE_fdd_enb_phy.cc 405 Late DL subframe from MAC:695, PHY is currently on 696
    11/06/2015 16:09:21.447242 error phy LTE_fdd_enb_phy.cc 440 Late UL subframe from MAC:692, PHY is currently on 693
    11/06/2015 16:09:21.447343 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (686) does not match PHY (696)
    11/06/2015 16:09:21.447508 error phy LTE_fdd_enb_phy.cc 440 Late UL subframe from MAC:693, PHY is currently on 694
    11/06/2015 16:09:21.447670 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_phy circular buffer empty on receive
    11/06/2015 16:09:21.447714 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_phy circular buffer empty on receive
    11/06/2015 16:09:21.447800 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_phy circular buffer empty on receive
    11/06/2015 16:09:21.447971 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_timer circular buffer empty on receive
    11/06/2015 16:09:21.448003 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_timer circular buffer empty on receive
    11/06/2015 16:09:21.448035 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_timer circular buffer empty on receive
    11/06/2015 16:09:21.448163 error msgq LTE_fdd_enb_msgq.cc 220 phy_to_mac circular buffer empty on receive
    11/06/2015 16:09:21.448191 error msgq LTE_fdd_enb_msgq.cc 220 phy_to_mac circular buffer empty on receive
    11/06/2015 16:09:21.448220 error msgq LTE_fdd_enb_msgq.cc 220 phy_to_mac circular buffer empty on receive
    11/06/2015 16:09:21.448272 error msgq LTE_fdd_enb_msgq.cc 220 phy_to_mac circular buffer empty on receive
    11/06/2015 16:09:21.839007 error msgq LTE_fdd_enb_msgq.cc 220 phy_to_mac circular buffer empty on receive
    11/06/2015 16:09:23.392719 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_timer circular buffer empty on receive
    11/06/2015 16:09:39.745367 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_timer circular buffer empty on receive
    11/06/2015 16:09:39.745523 error msgq LTE_fdd_enb_msgq.cc 220 mac_to_timer circular buffer empty on receive
    11/06/2015 16:10:03.171710 error radio LTE_fdd_enb_radio.cc 714 RX old time spec 1925185918 1925185920
    11/06/2015 16:10:03.171832 error radio LTE_fdd_enb_radio.cc 722 RX overrun 1925187838 1925185920
    11/06/2015 16:10:03.173041 info radio LTE_fdd_enb_radio.cc 682 RX modifying recv_size to sync 1925208958 1925207040
    11/06/2015 16:10:03.173075 info radio LTE_fdd_enb_radio.cc 669 RX synced 1925207040 1925207040
    11/06/2015 16:10:03.175047 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1453) does not match PHY (1463)
    11/06/2015 16:10:03.176130 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1454) does not match PHY (1464)
    11/06/2015 16:10:03.177040 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1455) does not match PHY (1465)
    11/06/2015 16:10:03.177968 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1456) does not match PHY (1466)
    11/06/2015 16:10:03.179031 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1457) does not match PHY (1467)
    11/06/2015 16:10:03.179963 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1458) does not match PHY (1468)
    11/06/2015 16:10:03.181027 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1459) does not match PHY (1469)
    11/06/2015 16:10:03.181977 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1460) does not match PHY (1470)
    11/06/2015 16:10:03.183026 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1461) does not match PHY (1471)
    11/06/2015 16:10:03.183990 error phy LTE_fdd_enb_phy.cc 642 PDSCH current_tti from MAC (1462) does not match PHY (1472)

    And then the phone showed your sim card does not allow conncection to this network.

    Any reply is warmly appreciated.
    With my best regards.

     
    • bwojtowi

      bwojtowi - 2015-11-08

      Please examine the generated pcap file /tmp/LTE_fdd_enodeb.pcap in wireshark. If the only content is MIB, SIB1, and SIB2, then your UE is not attempting to attach. If there is more content, it can help diagnose connection failures.

      Hope this helps,
      Ben

       
      • Jennifer

        Jennifer - 2015-11-09

        Thank you very much for your replying. The /tmpLTE_fdd_enodeb.pcap is only 24bytes. I opened it in wireshark and nothing was displayed. Could you give me some suggestion to find out the problem? Thank you very much. With my best regards.

         
        • bwojtowi

          bwojtowi - 2015-12-23

          Jennifer,

          Sorry for the delayed response. My apologies, PCAP support is turned off
          by default. Please turn on PCAP support within the eNodeB before running
          your test (write enable_pcap 1).

          Thanks,
          Ben

          On Mon, Nov 9, 2015 at 12:25 PM, Jennifer jenniferchen@users.sf.net wrote:

          Thank you very much for your replying. The /tmpLTE_fdd_enodeb.pcap is only
          24bytes. I opened it in wireshark and nothing was displayed. Could you give
          me some suggestion to find out the problem? Thank you very much. With my
          best regards.


          some error when my phone connects to openlte
          https://sourceforge.net/p/openlte/discussion/general/thread/18ab37cb/?limit=25#acb2/cbb0/53eb


          Sent from sourceforge.net because you indicated interest in
          https://sourceforge.net/p/openlte/discussion/general/

          To unsubscribe from further messages, please visit
          https://sourceforge.net/auth/subscriptions/

           
          • sajal

            sajal - 2017-06-25

            i tried write enable_pcap 1 but the errors still persisted . i am using openlte_v00-20-04 please help me with this problem.

             
  • Billy

    Billy - 2018-07-17

    I am using Ettus USRP N210, enode is up but i am unable to find the network during scan. Also, pcap file shown 0 bytes captured, although i have set the parameter as 1. Anyone to guide

     

Log in to post a comment.