Interrupt Problems (again).

[Nick Thomas]

I don't know if this makes any difference, but I am also experiencing an
unusual lockup problem.
I originally thought this was an unrelated resource deadlock problem, but
when the lockup occurs I notice that _ISR_Nest_level is stuck at 1. The
system hasn't crashed, but none of the tasks are getting chance to run
(probably because _ISR_Nest_level is not zero).

Does this shed any light on my problem?


Regards

Nick


> -----Original Message-----
> From: rtems-users-bounces at rtems.org [mailto:rtems-users-
> bounces at rtems.org] On Behalf Of Nick Thomas
> Sent: 12 February 2010 16:47
> To: rtems-users at rtems.com
> Subject: Interrupt Problems (again).
> 
> Hi,
> 
> I am still having problems with interrupts.
> 
> I reported a while ago that rtems_interrupt_is_in_progress() was
> returning the wrong value occasionally.
> Now, I see that I am getting an error 18 (RTEMS_CALLED_FROM_ISR) at a
> place in the code that definitely back-traces to a task!
> 
> At the point of the crash I see that _ISR_Nest_level is zero, and
> _Thread_Dispatch_disable_level is 1 .
> 
> I am using RTEMS 4.7.1 on a PowerPC 405, if that helps.
> 
> I know that RTEMS 4.7.1 is quite old now, but I don't realistically
> have the ability to upgrade at this point in the project.
> 
> 
> Any help/comments/suggestions welcomed.
> 
> 
> Regards
> 
> Nick
> 
> -----------------------------
> Nick Thomas
> Email: nick.thomas at pixsan.com
> 
> 
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users