From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: ncunningham@linuxmail.org
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] Per kthread freezer flags
Date: Thu, 29 Jul 2004 18:10:07 +0200 [thread overview]
Message-ID: <1091117407.2521.3.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <1091103080.2703.6.camel@desktop.cunninghams>
On Thu, 2004-07-29 at 22:11 +1000, Nigel Cunningham wrote:
> Hi.
>
> On Thu, 2004-07-29 at 20:02, Felipe Alfaro Solana wrote:
> > > It doesn't look like I've touched any of those threads. I have doubts
> > > about irqd/0 (is that kirqd reworked?), so you might try making setting
> > > PF_NOFREEZE and seeing if it makes a difference. I haven't done the
> > > switch to rc2-mm1 yet, so haven't gotten to those issues.
> >
> > kirqd is voluntary-preempt patch by Ingo Molnar. I have also applied
> > several other patches, like Con's Staircase scheduler policy and some
> > latency fixes.
>
> Okay. So, just to make sure I understand you correctly, suspending works
> fine with all of these other patches added and adding the extra
> refrigerator calls breaks it. Are you at all able to narrow it down to a
> particular change?
Exactly! I'm currently running a highly patched kernel based on 2.6.8-
rc2-bk7 plus Con's work and Ingo's voluntary preempt. They work fine
when suspending to memory (S3) and to disk (S4 via swsusp), but adding
your kthread freezer flags to the mix keeps my CardBus NIC from being
recognized when resuming from S3: I need to unplug it, then plug it to
make it functional again.
However, I'm not sure what causes this behavior.
next prev parent reply other threads:[~2004-07-29 16:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 7:22 Nigel Cunningham
2004-07-28 21:20 ` Andrew Morton
2004-07-28 22:25 ` Nigel Cunningham
2004-07-28 22:30 ` Felipe Alfaro Solana
2004-07-28 22:27 ` Nigel Cunningham
2004-07-28 22:36 ` Nigel Cunningham
2004-07-28 23:21 ` Felipe Alfaro Solana
2004-07-29 0:46 ` Nigel Cunningham
2004-07-29 10:02 ` Felipe Alfaro Solana
2004-07-29 12:11 ` Nigel Cunningham
2004-07-29 16:10 ` Felipe Alfaro Solana [this message]
2004-07-29 22:39 ` Nigel Cunningham
2004-07-30 8:12 ` Felipe Alfaro Solana
2004-07-29 22:57 ` Felipe Alfaro Solana
2004-07-29 23:01 ` Nigel Cunningham
2004-07-29 19:04 ` Pavel Machek
2004-07-29 22:24 ` Nigel Cunningham
2004-07-29 22:44 ` Pavel Machek
2004-07-29 22:46 ` Nigel Cunningham
2004-07-29 23:25 ` [Patch] Per kthread freezer flags (Version 2) Nigel Cunningham
2004-07-30 9:18 ` Pavel Machek
2004-07-31 16:53 ` Felipe Alfaro Solana
2004-07-30 12:11 ` [Patch] Per kthread freezer flags Peter Osterlund
2004-07-30 22:15 ` Nigel Cunningham
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=1091117407.2521.3.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®