All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Sanjoy Mahajan <sanjoy-Bhlo64W4KxTQzY9nttDBhA@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3 and sigwait (was Re: 2.6.13-rc3: swsusp works (TP 600X))
Date: Sat, 30 Jul 2005 12:30:34 +0200	[thread overview]
Message-ID: <20050730103034.GC1942@elf.ucw.cz> (raw)
In-Reply-To: <E1DyfYO-0006oI-00-KmINTRm7+bkRAIupTkoUWTYRy0cijUJx@public.gmane.org>

Hi!

> >> One other glitch is that pdnsd (a nameserver caching daemon) has crashed
> >> when the system wakes up from swsusp.  It also happens when waking up
> >> from S3, which was working with 2.6.11.4 although not with 2.6.13-rc3.
> >> Many people have said mysql also does not suspend well.  Is their use of
> >> a named pipe or socket causing the problem?
> 
> > No idea, strace?
> 
> The upshot of stracing is in tthe Debian BTS <bugs.debian.org>
> #319572.  Paul Rombouts, an author of pdnsd, reproduced the strace
> crash and found the problem:
> 
> > Apparently strace causes sigwait to return EINTR, which is
> > inconsistent with the documentation I could find on sigwait.
> 
> Which is true.  The sigwait man entry (Debian 'etch') says:
>        The !sigwait! function never returns an error.
> 
> His patch (available in the BTS and included below) fixed the problem
> of strace or S3 sleep crashing pdnsd.

If you think it is a linux bug, can you produce small test case doing
just the sigwait, and post it on l-k with big title "sigwait() breaks
when straced, and on suspend"?

That way it is going to get some attetion, and you'll get either
documentation or kernel fixed.
								Pavel


-- 
teflon -- maybe it is a trademark, but it should not be.


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] S3 and sigwait (was Re: 2.6.13-rc3: swsusp works (TP 600X))
Date: Sat, 30 Jul 2005 12:30:34 +0200	[thread overview]
Message-ID: <20050730103034.GC1942@elf.ucw.cz> (raw)
In-Reply-To: <E1DyfYO-0006oI-00@skye.ra.phy.cam.ac.uk>

Hi!

> >> One other glitch is that pdnsd (a nameserver caching daemon) has crashed
> >> when the system wakes up from swsusp.  It also happens when waking up
> >> from S3, which was working with 2.6.11.4 although not with 2.6.13-rc3.
> >> Many people have said mysql also does not suspend well.  Is their use of
> >> a named pipe or socket causing the problem?
> 
> > No idea, strace?
> 
> The upshot of stracing is in tthe Debian BTS <bugs.debian.org>
> #319572.  Paul Rombouts, an author of pdnsd, reproduced the strace
> crash and found the problem:
> 
> > Apparently strace causes sigwait to return EINTR, which is
> > inconsistent with the documentation I could find on sigwait.
> 
> Which is true.  The sigwait man entry (Debian 'etch') says:
>        The !sigwait! function never returns an error.
> 
> His patch (available in the BTS and included below) fixed the problem
> of strace or S3 sleep crashing pdnsd.

If you think it is a linux bug, can you produce small test case doing
just the sigwait, and post it on l-k with big title "sigwait() breaks
when straced, and on suspend"?

That way it is going to get some attetion, and you'll get either
documentation or kernel fixed.
								Pavel


-- 
teflon -- maybe it is a trademark, but it should not be.

  parent reply	other threads:[~2005-07-30 10:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-23  0:19 2.6.13-rc3: swsusp works (TP 600X) Sanjoy Mahajan
2005-07-23  0:35 ` Pavel Machek
2005-07-28 20:17   ` Sanjoy Mahajan
2005-07-28 21:36     ` Pavel Machek
2005-07-28 21:55       ` Rafael J. Wysocki
2005-07-29  3:48         ` Sanjoy Mahajan
2005-07-29  4:33         ` Sanjoy Mahajan
     [not found]   ` <20050723003544.GC1988-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-07-30  0:50     ` S3 and sigwait (was Re: 2.6.13-rc3: swsusp works (TP 600X)) Sanjoy Mahajan
2005-07-30  0:50       ` Sanjoy Mahajan
     [not found]       ` <E1DyfYO-0006oI-00-KmINTRm7+bkRAIupTkoUWTYRy0cijUJx@public.gmane.org>
2005-07-30 10:30         ` Pavel Machek [this message]
2005-07-30 10:30           ` [ACPI] " Pavel Machek
     [not found]           ` <20050730103034.GC1942-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-08-01  6:51             ` Shaohua Li
2005-08-01  6:51               ` [ACPI] " Shaohua Li
     [not found]               ` <1122879094.3285.2.camel-ECwVeV2eNyQD0+JXs3kMbRL4W9x8LtSr@public.gmane.org>
2005-08-01  7:09                 ` Pavel Machek
2005-08-01  7:09                   ` [ACPI] " Pavel Machek
2005-08-02  5:16                   ` Shaohua Li
  -- strict thread matches above, loose matches on Subject: below --
2005-08-01 12:36 Li, Shaohua

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050730103034.GC1942@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sanjoy-Bhlo64W4KxTQzY9nttDBhA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.