On 9/10/19 10:02 am, Chris Johns wrote:
> On 9/10/19 3:31 am, Sebastian Huber wrote:
>> - Am 8. Okt 2019 um 4:04 schrieb Jonathan Brandmeyer
>> jbrandme...@planetiq.com:
>>
>>> On Mon, Oct 7, 2019 at 12:32 AM Sebastian Huber
>>> wrote:
Hello,
I need your help to figure out
I enabled RTEMS_RAMDISK_TRACE. That appears to be dead code in my build.
Change didn't do anything. I checked the symbol table and none of those
functions are in my build. The actual ram disk driver is in a different
location and didn't have a trace equivalent. Is there another way to get a
tra
On 10/10/19 6:23 am, Mathew Benson wrote:
> I added the tracerfs command to the shell. Not sure why that's not already
> there.
The command is not in the shell directory and I did not add it to the config for
the shell. Maybe is should be. I am not sure.
> I enabled all with "tracerfs set all".
I added the tracerfs command to the shell. Not sure why that's not already
there. I enabled all with "tracerfs set all". It took a while, but I did
run into the problem. The end of the log is below. Can you see what the
kernel is trying to do and what its waiting on from this? It's going to b
