I am using Linux in an embedded platform with x86. Applications don't do anything special. The system call which is returning EINTR is poll. Also in one of the thread read is returning ENODATA after resume. If I just try the system calls again in case of EINTR or ENODATA everything works fine. >From your mail it looks like freezer is not supposed to be interrupting system calls. Is that true?
-----Original Message----- From: Nigel Cunningham [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 3:19 PM To: Agarwal, Lomesh Cc: [EMAIL PROTECTED]; Rafael Wysocki; linux-kernel@vger.kernel.org Subject: Re: which signal is sent to freeze process? Hi. On Friday 20 July 2007 07:06:01 Agarwal, Lomesh wrote: > So basically I can not install a signal handler to catch freeze signal > in the process. Right? > Is there any other way to solve the problem I am facing? After resume > some of the system calls are failing in some of my applications with > errno set as EINTR. I wanted to explore a way to not check for this > error all over the place and somehow retry failed system call. Any > ideas? Well, if you tell us which syscalls are returning with EINTR, maybe we can do something on our side. The freezer is supposed to be as transparent as possible to userspace, so it may be the case that we can do something to continue waiting or whatever you were doing after the freezing is done. Regards, Nigel -- See http://www.tuxonice.net for Howtos, FAQs, mailing lists, wiki and bugzilla info. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
