signal in the kernel for wait_event_interruptible()

lordofring · 08-22-2005, 04:39 PM

Hello,

My device driver will sleep on wait_event_interruptible() function. With testing, I noticed that it is waked up by a signal.

Code:

if (wait_event_interruptible(my_queue, myCondition) == -ERESTARTSYS)
{
	printk(KERN_ERR "sig[0] is 0x%08x, sig[1] is 0x%08x\n", 
			current->pending.signal.sig[0], 
			current->pending.signal.sig[1]);
	return -ERESTARTSYS;
}

I know that the sig[0] is the normal signal, for example 0x02 is SIGINT for Ctrl-C. In my case, I get: "sig[0] is 0x00000000, sig[1] is 0x00000001" I'm wondering what's in sig[1]? And why are there 2 signals?

The background of my driver:
The driver is for the i2c device which works with interrupt. It's works fine in most time. When I testing it with multithread, very frequency i2c access functions, it receives the unknown (for me

) signal.
The driver is in an embedded system. I debug it through serial port. So only one console for it. And I didn't press any key when it received the unknown signal.

Thanks,

lordofring

sundialsvcs · 08-23-2005, 10:11 AM

Looking at kernel/signal.c, asm/signal.h, and include/signal.h, it appears that this is a bitset stored in multiple words. (See the macro: sigaddset.) There is one bit in this mask for each signal.

There are numerous routines in signal.c that handle it.

jailbait · 08-23-2005, 10:18 AM

"it receives the unknown (for me ) signal"

Here are the signals available in Linux.

http://www.comptechdoc.org/os/linux/...pgsignals.html

------------------------
Steve Stites

lordofring · 08-23-2005, 03:14 PM

I read more about the linux signal. I believe sig[1] is the real time signal. But I still don't know, where and when is the signal sent?