You have a good location from the trap: PC is at lowpan_rcv+0x576/0x714 [6lowpan] You are 3/4 of the way into lowpan_rcv.
Add a bunch of printks in that routine starting about half way in that print out the relevant variables around the crash point. Plan B - use a JTAG on the kernel, but printks will do the trick 98% of the time. I suspect it is unlikely that the code has been significantly tested on dual interfaces since no one has the hardware. The Ethernet support I mentioned in another post would provide a way to test dual interfaces. -- Jon Smirl jonsm...@gmail.com ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
