From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: swsusp-devel@lists.sourceforge.net,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: suspend2 problems on SMP machine, incorrect tainting
Date: Sat, 29 May 2004 17:34:29 +1000 [thread overview]
Message-ID: <40B83D05.1020701@linuxmail.org> (raw)
In-Reply-To: <20040528103549.GA2789@elf.ucw.cz>
Hi.
Pavel Machek wrote:
> Hi!
>
> I tried suspend2 2.0.0.81 on Toshiba HT machine, and it did not
> work :-(. First test was with "noapic nosmp", last messages are
Hmm. I haven't tried it with noapic or nosmp options before. It ought to work; I'll see if I can
reproduce this issue.
> Tainted: S is due to suspend2, right? It abuses flag that origally means
> "invalid SMP configuration". You might want to fix that.
Yes. I've been meaning to change that; must get around to it.
> Tried without noapic nosmp... display got "interesting" at one point,
Yes. The sequence of operations to force a redraw of the screen works okay under 2.4 but needs
looking at under 2.6.
> but hey, it worked! I have "sleeping function called rom invalid
> context at arch/i386/mm/highmem.c:5" called from kmap, copy_pageset1.
Yes. It needs to be atomic (it's the atomic copy) and pages might well be HighMem so I guess the
answer is to suppress the message rather than changing something in suspend.
Nigel
--
Nigel & Michelle Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6254 0216 (home)
After homosexuality, they'll be arguing paedophilia is normal.
next prev parent reply other threads:[~2004-05-29 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 10:35 suspend2 problems on SMP machine, incorrect tainting Pavel Machek
2004-05-29 7:34 ` Nigel Cunningham [this message]
2004-05-29 8:47 ` [Swsusp-devel] " Nigel Cunningham
2004-05-29 7:43 ` [Swsusp-devel] " Nigel Cunningham
2004-05-29 11:34 ` 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=40B83D05.1020701@linuxmail.org \
--to=ncunningham@linuxmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=swsusp-devel@lists.sourceforge.net \
/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.