Re: [reconos-devel] ML605 automated tests

[Ariane Keller]

Hi all

On Dec 14, 2010, at 4:17 PM, Markus wrote:

> Hi *,
> 
> I performed the automated tests on the ML605. 64 of 65 tests succeeded, but 
> one test failed (mutex_test_posix). 
> 
> Thus, I run the failed test some more times, in total 7 times.
>   - 3 runs: 
>   went fine
>   - 3 runs: 
>   the mutex was not locked in-between by the hw thread 1 of 10 times
>   - 1 run: 
>   the mutex was not locked in-between by the hw thread 2 of 10 times
> 
> The debug output of the last run with 2 unsuccessful mutex_lock's is 
> attached. Interestingly, the delegate receives the command to lock a mutex 
> before the mutex is locked by the software, which should not happen. I could 
> not reproduce this error for the ecos API, which is a bit odd.
> 
> It would be interesting to know, if anyone can reproduce this failure.

I finally managed to do the tests.  The exec_mutex_posix test also failed in my 
setup.
My statistics are:
Success: 6 runs
1 failure: 4 runs

failure:
mutex lock and release by hwthread: too early
(occurrence: once but at different stages)

All the other tests were ok.

Cheers,
Ariane

___
Reconos-devel_lists.reconos.de mailing list
reconos-devel@lists.reconos.de
https://ml01.ispgateway.de/mailman/listinfo/reconos-devel_lists.reconos.de

Re: [reconos-devel] ML605 automated tests

[Markus]

Hi *,

I performed the automated tests on the ML605. 64 of 65 tests succeeded, but one 
test failed (mutex_test_posix). 

Thus, I run the failed test some more times, in total 7 times.
   - 3 runs: 
   went fine
   - 3 runs: 
   the mutex was not locked in-between by the hw thread 1 of 10 times
   - 1 run: 
   the mutex was not locked in-between by the hw thread 2 of 10 times

The debug output of the last run with 2 unsuccessful mutex_lock's is attached. 
Interestingly, the delegate receives the command to lock a mutex before the 
mutex is locked by the software, which should not happen. I could not reproduce 
this error for the ecos API, which is a bit odd.

It would be interesting to know, if anyone can reproduce this failure.

Cheers,

 Markus

-- 
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt auch mit 
gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl
self = 0xB00974D0
init_data = 0x
delegate_semaphore = 0x
slot num = 0
slot = 0xB009E444
slot->thread = 0xB00974D0
resources = 0xB0095D08
resource_count = 0x0001
fifo_read_index = 0x
fifo_write_index = 0x
flags = 0x0001
next = 0x
thread '': slot 0: resetting
thread '': slot 0: initializing with data 0x
thread '': slot 0: setting FIFO handles: read: 
0x, write: 0x
thread '': slot 0: enabling bus macros
thread '': slot 0: unblocking
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
mutex lock and release by hwthread: too early (3)
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
mutex lock and release by hwthread: too early (3)
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
thread '': slot 0: unblocking and writing result 
0x
<< delegate processing done for task at DCR 0x8000
thread '': **task in slot 0:**
  cmd: 0x0200 (code: 0x02), data: 0x, datax: 0x
<< delegate processing done for task at DCR 0x8000
mutex lock and release by hwthread: success (34)
thread '': **task in slot 0:**
  cmd: 0x8240 (code: 0x82), data: 0x, datax: 0x
mutex_test_posix done.

__