> On 10 Oct 2019, at 7:00 pm, mben...@windhoverlabs.com wrote:
>
> I’m fairly certain I’m running into this reported issue:
>
> https://devel.rtems.org/ticket/2792
It does seem similar.
> Is there any status change on this? Is there a temporary workaround recovery
> procedure?
No work has
I’m fairly certain I’m running into this reported issue:
https://devel.rtems.org/ticket/2792
Is there any status change on this? Is there a temporary workaround recovery
procedure? I’m tempted to give the conditional wait a timeout.
Sent from my iPhone
> On Oct 9, 2019, at 23:05, Mathew Bens
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
I don't have a test case that I can post or give away, yet. I may put one
together later.
Yes. All 4 tasks are on that same conditional wait. The condition is a
response from a block device. The test case is hammering the RAM disk. I
wrote some of the flash drivers but as far as I know, the R
On 8/10/19 12:53 pm, Mathew Benson wrote:
> I'm using RTEMS 5 on a LEON3. I'm troubleshooting a failure condition that
> occurs when stress test reading and writing to and from RAM disk. RAM disk to
> RAM disk. When the condition is tripped, it appears that I have 4 tasks that
> are pending on c
I'm using RTEMS 5 on a LEON3. I'm troubleshooting a failure condition that
occurs when stress test reading and writing to and from RAM disk. RAM disk
to RAM disk. When the condition is tripped, it appears that I have 4 tasks
that are pending on conditions that just never happens. The task comma
