On 4/10/2016 11:13 AM, Charles Steinkuehler wrote: > I am experimenting with getting Machinekit running on Debian Jessie, > and have run into an issue with loading capes. > > After I manually load a cape: > > $ SLOTS=/sys/devices/bone_capemgr.*/slots > $ sudo -A su -c "echo cape-bebopr-brdg:R2 > $SLOTS" > > ...CPU usage maxes out and I have eight systemd-udevd tasks running > that are each taking a good chunk of the CPU. These typically go away > after apx. 17 seconds of CPU time (each), or about 2-1/2 minutes, but > I'm wondering what in the world is going on. > > Is this a known issue? Any ideas how to tell what the systemd-udevd > processes are doing? > > The kernel is 3.8.13-xenomai-r78, which works fine under Wheezy.
I get the same results with a "stock" Debian Jessie image ( debian@beaglebone:~$ cat /etc/dogtag BeagleBoard.org Debian Image 2016-03-27 ...using the 3.8.13-bone79 kernel. The 4.1.18-ti-r55 kernel provide with the Jessie image has a cape manager (although the slots file is in a different location), but trying to load the cape-bebopr-brdg:R2 cape fails. Any hints as to how to debug would be very welcome! -- Charles Steinkuehler [email protected] -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
