All of lore.kernel.org
 help / color / mirror / Atom feed
* [Xenomai-help] soft lockup after 11s
@ 2008-06-24 16:07 Robert McCullough
  2008-06-24 16:18 ` Gilles Chanteperdrix
  0 siblings, 1 reply; 2+ messages in thread
From: Robert McCullough @ 2008-06-24 16:07 UTC (permalink / raw)
  To: xenomai

[-- Attachment #1: Type: text/plain, Size: 689 bytes --]

Hi,

 

I am using Linux 2.6.23.14 and Xenomai 2.4.2 on a MPC5200.

 

My problem is this:

 

My RTDM driver communicates to a slave device via a dual-ported RAM (DPR)
interface.  In my module_init() I have to give the slave a SAVE command via
the DPR.

The SAVE command stores the slave's parameters to a non-volatile memory
(FLASH or EEPROM).  I then wait in a loop for a flag in the DPR to be set
stating the command is complete.

The SAVE command takes about 22 seconds to complete.  Before the command
completes I get a "BUG:  soft lock-up - CPU#0 stuck for 11s!" message.

How would I solve this problem?

Is there a way to increase this 11 second timeout?

 

Best regards, 

Rob


[-- Attachment #2: Type: text/html, Size: 3474 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Xenomai-help] soft lockup after 11s
  2008-06-24 16:07 [Xenomai-help] soft lockup after 11s Robert McCullough
@ 2008-06-24 16:18 ` Gilles Chanteperdrix
  0 siblings, 0 replies; 2+ messages in thread
From: Gilles Chanteperdrix @ 2008-06-24 16:18 UTC (permalink / raw)
  To: rob; +Cc: xenomai

Robert McCullough wrote:
> Hi,
> 
>  
> 
> I am using Linux 2.6.23.14 and Xenomai 2.4.2 on a MPC5200.
> 
>  
> 
> My problem is this:
> 
>  
> 
> My RTDM driver communicates to a slave device via a dual-ported RAM (DPR)
> interface.  In my module_init() I have to give the slave a SAVE command via
> the DPR.
> 
> The SAVE command stores the slave's parameters to a non-volatile memory
> (FLASH or EEPROM).  I then wait in a loop for a flag in the DPR to be set
> stating the command is complete.
> 
> The SAVE command takes about 22 seconds to complete.  Before the command
> completes I get a "BUG:  soft lock-up - CPU#0 stuck for 11s!" message.
> 
> How would I solve this problem?

Since module_init() is a non real-time context, you can safely call
schedule() in the loop.

> Is there a way to increase this 11 second timeout?

You can disable the soft-lockup detector feature, a driver which loops
for 22 seconds without yielding to the OS is a bit hard for the OS, to
say the least.

-- 
                                                 Gilles.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-06-24 16:18 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-24 16:07 [Xenomai-help] soft lockup after 11s Robert McCullough
2008-06-24 16:18 ` Gilles Chanteperdrix

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.