nanosleep blocks inifinity (internal rtems deathlock?) even CPU is in idle Task

[Matthias Goldhoorn]

On 15.11.2012 19:45, Chris Johns wrote:
> Matthias Goldhoorn wrote:
>> On 15.11.2012 14:52, Sebastian Huber wrote:
>>> On 11/15/2012 01:26 PM, Matthias Goldhoorn wrote:
>>>> On 15.11.2012 11:52, Sebastian Huber wrote:
>>>>> On 11/15/2012 10:44 AM, Matthias Goldhoorn wrote:
>>>>>
>>>> Yeah it's both defined.
>>>> The nanosleep sometimes (mostly) works.
>>>> Only if some interrupts during the sleep i got this non-awaking
>>>> behavior it seems strange.
>
> Which interrupts are happening that cause the sleep to not wake up, ie 
> the timer to not fire ?
>
> What concerns me with the 'rtems_posix_threads' list you posted is no 
> IDLE task which leads me to think any classic threads are not listed. 
> Is there something else loading the CPU ? Maybe a classic thread 
> created by the BSP.
>
> Chris
First of all:

Questions to _Watchdog_Ticks_since_boot
the _Watchdog_Ticks_since_boot is incrementing after watch interrupt 
that results of the br to rtems_clock_tick()


Question regarding to an simple example or my current setup:
i attached the RTEMS initialization classes for my base-system. The 
whole rest is rock standard, but i don't have an out of the box 
bootstrap or simple example because i glued rock and rtems together.
I currently working by side of this problem to integrate the whole RTEMs 
think into ROCK itself as an clean bootstrap. If i finished this 
(hopefully in the next days) i could send you the link howto bootstrap this.
This might then also be interesting for RTEMs users that to Robot 
control in general. But i got offtopic...

Questions to another bsp:
Not yet

Regarding to the missing idle thread:
I think this idle function is only directly called from the scheduler 
and not an "real" rtems thread or thread?!

To the point no source lines available:
I dont know why GDB could not figure out the code inside of the clock 
interrupt function for everything expect this function i have code lines...

Current State:
I currently try to debug more into the scheduling from rtems_clock_tick 
on...

Matthias





-- 
  Dipl.-Inf. Matthias Goldhoorn
  Space and Underwater Robotic

  Universität Bremen
  FB 3 - Mathematik und Informatik
  AG Robotik
  Robert-Hooke-Straße 5
  28359 Bremen, Germany

  Tel.:     +49 421 178 45-4193
  Zentrale: +49 421 178 45-6550
  Fax:      +49 421 178 45-4150
  E-Mail:   matthias.goldhoorn at uni-bremen.de

  Weitere Informationen: http://www.informatik.uni-bremen.de/robotik

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtemscfg.h
Type: text/x-chdr
Size: 2104 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20121116/3ca760c4/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: net_cfg.h
Type: text/x-chdr
Size: 5028 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20121116/3ca760c4/attachment-0005.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: main-orogen_default_message_producer__Task.cpp
Type: text/x-c++src
Size: 7919 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20121116/3ca760c4/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtems_init.cpp
Type: text/x-c++src
Size: 8165 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20121116/3ca760c4/attachment-0007.bin>