Filesystem test failures on v850sim

[Joel Sherrill]

Checking v850sim BSP. Not sure about other variants. Looks like all of the DOSFS and RFS tests fail:

Could be a generic alignment issue or simply the test not really fitting in memory.

Starting as 4.11 milestone until Sebastian says what to do.

(gdb) r
Starting program: /users/joel/rtems-4.11-work/b-v850sim/v850-rtems4.11/c/v850sim/testsuites/fstests/fsdosfsname01/fsdosfsname01.exe
core: 1 byte write to unmapped address 0x22c9c8 at 0x100032

Program received signal SIGSEGV, Segmentation fault.
0x00100032 in start ()
(gdb) bt
#0 0x00100032 in start ()

[Joel Sherrill]

I am wondering if this is a broader issue of more tests not working on simulators without a clock tick. After running fsdosfssync01.exe for a LONG time, _Watchdog_Ticks_since_boot was still zero. Does the bdbuf code require a clock tick? Does it poll waiting for something to happen in the background?

In gdb, I see it stuck in the bdbuf tasks.

[Chris Johns]

The output path waits a period of time before flushing the data. It stops the output path being hit with a group of small writes generating mostly overhead. What happens if the timer value is set to 0 ?

Is it adding an un-natual constrain on RTEMS, its sub-systems and tests by requiring the code to work without a clock tick ? I think it it is. In this case is the simulator at fault because it or we do not support a tick ?

[Joel Sherrill]

This is a case where the simulator does not have a clock tick source. So we just may have more tests which can't be run successfully.

I am not asking for code changes if this is the case, just more tests to be added to the simulator clock idle task ignore test list.

[Joel Sherrill]

OK. This is not related to lack of a clock tick ISR source. The gdb arm simulator and arm920 BSP passed all but 3 tests (spfatal26, heapwalk, and block01). This is something else and likely specific to the v850.

[Chris Johns]

Are those BSP's which are passing simulating a clock tick using a BSP option and so working ?

[Joel Sherrill]

arm920-testsuite.tcfg only has this:

include: testdata/require-tick-isr.tcfg

All the v850 testsuite.tcfg files also have that. So that list doesn't kick the dosfs tests out.

Seems to be something more v850 specific.

[Chris Johns]

I would check the BSPOPTS for the passing vs the failing. Some BSPOPTS default to that fast tick hack (which I cannot remember off the top of my head) which is in the generic tick ISR handler code.

[Joel Sherrill]

Hmm... Thanks for bumping these tickets Sebastian.

We may have a solution (or work around) we didn't have when this ticket was filed. Do you know the set of file system tests which require a clock tick?

They should be added to testsuites/testdata/require-tick-isr.tcfg.

I agree that production HW should have a clock tick source but many gdb simulators do not have interrupts and we already account for that in a broad way.

This should not be "FIXED". We should just add the tests to the list.

[Sebastian Huber]

I don't have time for the v850 at the moment.