Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: not syncing! error
Date: Thu, 11 Mar 2004 15:33:28 +0530
Message-ID: <1118873EE1755348B4812EA29C55A972176470@esnmail.esntechnologies.co.in>
Thread-Topic: not syncing! error
Thread-Index: AcQHUBnwmOJz+g82TfiMCK/r00CxfA==
From: "Jinu M." <jinum@esntechnologies.co.in>
To: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1415
Lines: 18

Hi All,

I have a hardware that sends in interrupts on every command that is passed to it.

What I do is when I get the initial interrupt I schedule the tasklet and carry out the device initialization from the tasklet. The tasklet is the ultimate action performer on any interrupt. The ISR just acknowledges and clears the interrupt.

The tasklet itself sends in commands to initialize the hardware. We do a interruptible_sleep_on() after a command is sent (wait for wake_up). When a command is sent an interrupt occurs and again the tasklet is scheduled (I guess so). Now from some other part in the tasklet I send a wake_up_interruptible(). This goes into trouble and the kernel ends up saying "kernel not syncing". If I remove interruptible_sleep_on the driver at least gets loaded and wake_up_interruptible() are sent..

I guess the problem is synchronization of these events. At present I have not used any locks. Can any one help me understand how I can take care of this scenario? The locking I will have to use should work for SMP too. Any pointers with easy to understand example codes is more than welcome. ?

Cheers!
-Jinu
Novice slowly trying to become guru!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/