From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: linux-pm@osdl.org, netdev@vger.kernel.org,
Adrian Bunk <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc1 regression: airo suspend fails
Date: Sat, 07 Oct 2006 13:17:13 -0700 [thread overview]
Message-ID: <873b9zhody.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <1160250771.24902.6.camel@kleikamp.austin.ibm.com> (message from Dave Kleikamp on Sat, 07 Oct 2006 14:52:51 -0500)
Dave Kleikamp <shaggy@austin.ibm.com> writes:
> I believe it was broken by:
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=3b4c7d640376dbccfe80fc4f7b8772ecc7de28c5
>
> I have seen this in the -mm tree, but didn't follow up at the time. I
> was able to fix it with the following patch. I don't know if it's the
> best fix, but it seems to follow the same logic as the original code.
>
>
> The airo driver used to break out of while loop if there were any signals
> pending. Since it no longer checks for signals, it at least needs to check
> if it needs to be frozen.
>
> Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
>
> diff -Nurp linux-2.6.19-rc1/drivers/net/wireless/airo.c linux/drivers/net/wireless/airo.c
> --- linux-2.6.19-rc1/drivers/net/wireless/airo.c 2006-10-05 07:22:39.000000000 -0500
> +++ linux/drivers/net/wireless/airo.c 2006-10-07 13:42:13.000000000 -0500
> @@ -3090,7 +3090,8 @@ static int airo_thread(void *data) {
> set_bit(JOB_AUTOWEP, &ai->jobs);
> break;
> }
> - if (!kthread_should_stop()) {
> + if (!kthread_should_stop() &&
> + !freezing(current)) {
> unsigned long wake_at;
> if (!ai->expires || !ai->scan_timeout) {
> wake_at = max(ai->expires,
> @@ -3102,7 +3103,8 @@ static int airo_thread(void *data) {
> schedule_timeout(wake_at - jiffies);
> continue;
> }
> - } else if (!kthread_should_stop()) {
> + } else if (!kthread_should_stop() &&
> + !freezing(current)) {
> schedule();
> continue;
> }
>
thanks. with this patch applied i can suspend to ram with the airo
module loaded.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
next prev parent reply other threads:[~2006-10-07 20:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0610042017340.3952@g5.osdl.org>
[not found] ` <871wpmoyjv.fsf@sycorax.lbl.gov>
2006-10-06 18:47 ` 2.6.19-rc1 regression: airo suspend fails Adrian Bunk
2006-10-07 3:54 ` Alex Romosan
2006-10-07 19:52 ` Dave Kleikamp
2006-10-07 20:17 ` Alex Romosan [this message]
2006-10-08 6:43 ` Pavel Machek
2006-10-07 21:46 ` 2.6.19-rc1: known regressions (v2) Adrian Bunk
2006-10-08 7:12 ` x60 backlight Re: [discuss] " Pavel Machek
2006-10-08 17:38 ` Adrian Bunk
2006-10-08 17:59 ` Michael S. Tsirkin
2006-10-08 19:30 ` Adrian Bunk
2006-10-16 19:39 ` Michael S. Tsirkin
2006-10-08 18:36 ` Pavel Machek
2006-10-08 19:29 ` Adrian Bunk
2006-10-08 23:44 ` Jeremy Fitzhardinge
2006-10-08 8:56 ` matthieu castet
2006-10-10 5:10 ` 2.6.19-rc1: known regressions (v3) Adrian Bunk
2006-10-10 22:58 ` Paul Mackerras
2006-10-11 3:08 ` Adrian Bunk
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=873b9zhody.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@osdl.org \
--cc=netdev@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
/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