From: Dave Jones <davej@redhat.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Nigel Cunningham <ncunningham@linuxmail.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: peculiar suspend/resume bug.
Date: Tue, 15 Aug 2006 23:53:52 -0400 [thread overview]
Message-ID: <20060816035351.GB17481@redhat.com> (raw)
In-Reply-To: <20060816024140.GA30814@srcf.ucam.org>
On Wed, Aug 16, 2006 at 03:41:40AM +0100, Matthew Garrett wrote:
> On Tue, Aug 15, 2006 at 08:37:28PM -0400, Dave Jones wrote:
>
> > cpufreq-applet crashes as soon as the cpu goes offline.
> > Now, the applet should be written to deal with this scenario more
> > gracefully, but I'm questioning whether or not userspace should
> > *see* the unplug/replug that suspend does at all.
>
> As Nigel mentioned, cpu unplug happens just before processes are frozen,
> so I guess there's a chance for it to be scheduled. On the other hand,
> it's not unreasonable for CPUs to be unplugged during runtime anyway -
> perhaps userspace should be able to deal with that?
Sure, I'm not debating that point. It's a bug in the applet that needs fixing,
but it also seems that we could be saving a whole lot of pain by
hiding this from userspace at suspend/resume time.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-16 3:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 22:10 peculiar suspend/resume bug Dave Jones
2006-08-16 0:19 ` Nigel Cunningham
2006-08-16 0:37 ` Dave Jones
2006-08-16 1:05 ` Nigel Cunningham
2006-08-16 2:41 ` Matthew Garrett
2006-08-16 3:53 ` Dave Jones [this message]
2006-08-16 8:54 ` Rafael J. Wysocki
2006-08-17 1:44 ` Nigel Cunningham
2006-08-17 5:44 ` Rafael J. Wysocki
2006-08-17 5:55 ` Nigel Cunningham
2006-08-17 6:30 ` Rafael J. Wysocki
2006-08-16 22:06 ` Pavel Machek
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=20060816035351.GB17481@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=ncunningham@linuxmail.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.