No solution here yet, but I have found some very relevant discussions out there. Something must have changed with the kernel scheduler that requires drivers (CAN in our case) to be updated. I copied the BeagleBone kernel support guru to this post (Robert Nelson). Perhaps he is already aware of this problem and knows of a work-around. I will post something if/when I get this figured out. Until then, here are some relevant links.
http://stackoverflow.com/questions/3537252/how-to-solve-bug-scheduling-while-atomic-swapper-0x00000103-0-cpu0-in-ts http://e2e.ti.com/support/omap/f/849/t/250383.aspx https://community.freescale.com/thread/330079 On Thursday, November 20, 2014 5:36:51 PM UTC-5, Me Nee wrote: > > Haven't figured a software way around this yet. For now we're avoiding > the "direct" CAN interface to the Beaglebone and instead using our external > custom hardware to relay serial "CAN" messages to the Beaglebone. We don't > have issues with this format. > > That said, if you have a fix I'd love to hear about it. > > On Thursday, November 20, 2014 3:04:20 PM UTC-7, beagler001 wrote: > >> Hello Me Nee, >> >> Yes. I am having the same problem. How are you doing on this? Have you >> figured anything out? >> >> I too am using the CAN interface on the BeagleBone Black device. >> >> Let me know, and I can update you with my findings if you still need help. >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
