Re: [beagleboard] High CPU usage after loading a cape on Jessie

Also oddly enough, that method for loading an uio driver, at least the demonstration uio driver for ADC is broken. Exact step instructions I've created and tested personally no longer work. At least on my BBB with . . . william@beaglebone:~$ uname -r 4.4.7-bone-rt-r9 william@beaglebone:~$ cat

Re: [beagleboard] High CPU usage after loading a cape on Jessie

Anyway, if you have a device tree "compatible=uio" definition for any node in any device tree. It seems that udev rule will hammer the crap out of the system until the udev rule can actually do what it wants to. On Thu, Apr 21, 2016 at 9:05 PM, William Hermans wrote: >

Re: [beagleboard] High CPU usage after loading a cape on Jessie

@Robert, I think I found the answer to your question. From a text file based on something another person on these forums was discussing with me . . . # put in /etc/modprobe.d/uio.conf # # make driver match on compatible = "uio"; options uio_pdrv_genirq of_id=uio # put in

Re: [beagleboard] High CPU usage after loading a cape on Jessie

On Thu, Apr 21, 2016 at 10:04 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 4/21/2016 9:43 PM, Charles Steinkuehler wrote: > > On 4/21/2016 9:37 PM, Robert Nelson wrote: > >> > >> Does the uio_pruss still work if we just nuke that whole udev rule?? > > > > Testing > Thanks

Re: [beagleboard] High CPU usage after loading a cape on Jessie

On 4/21/2016 9:43 PM, Charles Steinkuehler wrote: > On 4/21/2016 9:37 PM, Robert Nelson wrote: >> >> Does the uio_pruss still work if we just nuke that whole udev rule?? > > Testing Commenting the first line (with SYMLINK+=): == No excessive CPU usage when loading a PRU device-tree

Re: [beagleboard] High CPU usage after loading a cape on Jessie

Robert, Charles, One thing that confused me, was why does the uio_pruss driver add 8 mmap() file objects in that /dev/uio directory structure. They all point to the same address in memory it seems too. Also according to older exact step how-to's from aroudn 2013-2014, this hs omehow changed

Re: [beagleboard] High CPU usage after loading a cape on Jessie

On Thu, Apr 21, 2016 at 9:01 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 4/21/2016 7:41 PM, Charles Steinkuehler wrote: > > On 4/21/2016 7:32 PM, Robert Nelson wrote: > >> On Thu, Apr 21, 2016 at 7:25 PM, Charles Steinkuehler < > char...@steinkuehler.net > >>

Re: [beagleboard] High CPU usage after loading a cape on Jessie

> > *After further testing, if you create a /dev/uio directory before* > * trying to load a uio driver (like the PRU driver), everything works* > * fine. Interestingly, there are *NO* symlinks actually generated in* > * the /dev/uio directory, but the simple fact that it exists seems to be* > *

Re: [beagleboard] High CPU usage after loading a cape on Jessie

On 4/21/2016 7:41 PM, Charles Steinkuehler wrote: > On 4/21/2016 7:32 PM, Robert Nelson wrote: >> On Thu, Apr 21, 2016 at 7:25 PM, Charles Steinkuehler >> > > wrote: >> >> and of course, i never added who pinged me on this, when i

Re: [beagleboard] High CPU usage after loading a cape on Jessie

On 4/21/2016 7:32 PM, Robert Nelson wrote: > On Thu, Apr 21, 2016 at 7:25 PM, Charles Steinkuehler > > wrote: > > OK, this doesn't appear to be a PRU issue, it's a fundamental problem > with udev. The systemd-udevd process

Re: [beagleboard] High CPU usage after loading a cape on Jessie

On Thu, Apr 21, 2016 at 7:25 PM, Charles Steinkuehler < char...@steinkuehler.net> wrote: > On 4/10/2016 3:36 PM, Charles Steinkuehler wrote: > > On 4/10/2016 3:17 PM, Charles Steinkuehler wrote: > >> On 4/10/2016 11:13 AM, Charles Steinkuehler wrote: > >>> I am experimenting with getting

Re: [beagleboard] High CPU usage after loading a cape on Jessie

On 4/10/2016 3:36 PM, Charles Steinkuehler wrote: > On 4/10/2016 3:17 PM, Charles Steinkuehler wrote: >> 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

Re: [beagleboard] High CPU usage after loading a cape on Jessie

> > *I wonder if running strace, and piping stdout to a file would provide any > useful information on the subject. I'm pretty sure this would have to be > run explicitly as root( not sudo ).* > Not really useful in the least . . . On Sun, Apr 10, 2016 at 1:51 PM, William Hermans

Re: [beagleboard] High CPU usage after loading a cape on Jessie

> > *Any hints as to how to debug would be very welcome!* > I wonder if running strace, and piping stdout to a file would provide any useful information on the subject. I'm pretty sure this would have to be run explicitly as root( not sudo ). On Sun, Apr 10, 2016 at 1:36 PM, Charles Steinkuehler

Re: [beagleboard] High CPU usage after loading a cape on Jessie

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 >

[beagleboard] High CPU usage after loading a cape on Jessie

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