You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2019/07/18 01:49:47 UTC

[GitHub] [mynewt-nimble] lance-proxy edited a comment on issue #528: nimble/ll: Workaround and traces for the possible race scenario

lance-proxy edited a comment on issue #528: nimble/ll: Workaround and traces for the possible race scenario
URL: https://github.com/apache/mynewt-nimble/pull/528#issuecomment-512632125
 
 
   @rymanluk - fyi - I just updated our app to use the current top of NimBLE  master (that incorporates this PR) and I'm seeing crashes. For context, our app was previously tied to https://github.com/apache/mynewt-nimble/tree/b6da0700d25a75124793d2ed9079610260befd51 (after issue #446 was fixed you may recall - you can get the info on our NimBLE syscfs etc from that ticket) and was running stable. We do recycle alot of connections quickly.
   
   Here is a GDB backtrace of the crash:
   ```
   #0  hal_system_reset () at repos/apache-mynewt-core/hw/mcu/nordic/nrf52xxx/src/hal_system.c:56
   #1  0x0000f378 in os_default_irq (tf=0x2000ff60) at repos/apache-mynewt-core/kernel/os/src/arch/cortex_m4/os_fault.c:265
   #2  0x00010fc2 in os_default_irq_asm () at repos/apache-mynewt-core/kernel/os/src/arch/cortex_m4/m4/HAL_CM4.s:260
   #3  <signal handler called>
   #4  0x00027a0e in ble_phy_rxpdu_copy (dptr=dptr@entry=0x2000c1d8 <g_ble_phy_rx_buf+4> "\265\341\364\326\vj\247\n\303|\240\214.\303)\314P|\277\030\213\356\371\226\261\270\327\324\335X\023Z\227Tk\207\004J\275خ\333\v0O\203Ki\324\353g\213О8)\331\301\001|$\317\034<\362\241t\bnT\241\313m;\271\005VR\311Ӓ\303\312\071\230\345\376\301\356J\206DXl\303\347h.\035a\370gx\006~\336\033\244!=\227\236n\220\230\006ڱ?ɸ\205\rj\226\262\301I6\036\374\205\246\336\030I\375\306D\025\373\232\351\217{ǿF8}\210~\257&\242", rxpdu=rxpdu@entry=0x20007af8 <os_msys_1_data+1232>) at repos/apache-mynewt-nimble/nimble/drivers/nrf52/src/ble_phy.c:434
   #5  0x0001f264 in ble_ll_rx_end (rxbuf=rxbuf@entry=0x2000c1d8 <g_ble_phy_rx_buf+4> "\265\341\364\326\vj\247\n\303|\240\214.\303)\314P|\277\030\213\356\371\226\261\270\327\324\335X\023Z\227Tk\207\004J\275خ\333\v0O\203Ki\324\353g\213О8)\331\301\001|$\317\034<\362\241t\bnT\241\313m;\271\005VR\311Ӓ\303\312\071\230\345\376\301\356J\206DXl\303\347h.\035a\370gx\006~\336\033\244!=\227\236n\220\230\006ڱ?ɸ\205\rj\226\262\301I6\036\374\205\246\336\030I\375\306D\025\373\232\351\217{ǿF8}\210~\257&\242", rxhdr=rxhdr@entry=0x2000e850 <g_ble_phy_data+24>) at repos/apache-mynewt-nimble/nimble/controller/src/ble_ll.c:1059
   #6  0x00027e7a in ble_phy_rx_end_isr () at repos/apache-mynewt-nimble/nimble/drivers/nrf52/src/ble_phy.c:1070
   #7  ble_phy_isr () at repos/apache-mynewt-nimble/nimble/drivers/nrf52/src/ble_phy.c:1251
   #8  <signal handler called>
   #9  0x00000000 in ?? ()
   ````
   
   Please let me know what I can do to help uncover and debug these issues further. It seems that the 1.2 NimBLE would depend on firming up such stability issues I would hope.
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services