On 6/25/11, Werner Almesberger <wer...@almesberger.net> wrote: > Dmitry Eremin-Solenikov wrote: >> Again, have you seen the problem with PHR in wild, or is just smart >> thought? > > Yes, I've seen it in real life, usually in the presence of background > WLAN traffic. The following three types of corruption happen > frequently if there are interferences: > > [ 4897.570000] ieee802154: Bad frame received (type = 4) > [ 4981.920000] security support is not implemented > [ 6099.450000] at86rf230 spi2.0: invalid PHR 0xfa > > Before I added the PHR check, I would regularly find my systems > crashed after letting them sit idle (but receiving) for a few hours. > > With CSMA and CRC checking, the number of such events should drop, > but every once in a while, something would still slip through.
ACK, I'll apply this patch today in the evening. Thank you for debugging this event! -- With best wishes Dmitry ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
