[riot-devel] question on a possibility for a netdev deadlock
mail at daniel-krebs.net
Wed Jun 24 10:14:04 CEST 2015
all the mentioned function are not called in interrupt context. Take a look at ng_at86rf2xx.c. There you find the real ISR that sends a msg to the next higher level notifying about the IRQ. Then from there everything else in the driver is executed from thread context.
So I guess this is unrelated to the problems you are having.
Am 24. Juni 2015 09:54:09 MESZ, schrieb Martin <martin.landsmann at haw-hamburg.de>:
>I've tested the ng_ stack with samr21-xpro boards using the new
>Since I sometimes encountered hardfaults I took a look in the ISR
>handling of the driver .
>There we handle incoming packets when the receiver has finished the RX
>Since we are in a ISR, all other processes has been interrupted.
>Now when we call _receive_data() function inside the ISR, that in turn
>calls pktbuf handling/manipulating functions ,
>we try to acquire the mutex protecting the pktbuf .
>Since we are still inside of the ISR probably the mutex is acquired by
>If true this leads to a deadlock since the ISR would wait forever to
>acquire the mutex and never return to leave the ISR.
>Additionally if we successfully acquire the mutex,
>we could produce inconsistencies iff the protection is not performed
>Just wanted to ask if I'm mistaken here and missed something.
>devel mailing list
>devel at riot-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel