From: Pavel Machek <pavel@ucw.cz>
To: Hu Gang <hugang@soulinfo.com>
Cc: EricAltendorf@orst.edu, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Bug: swsusp in 2.5.42: "Scheduling while atomic"
Date: Wed, 23 Oct 2002 11:05:03 +0200 [thread overview]
Message-ID: <20021023090503.GA3416@elf.ucw.cz> (raw)
In-Reply-To: <20021018092521.3180fd42.hugang@soulinfo.com>
Hi!
> |[1.] One line summary of the problem:
> |
> |Scheduling while atomic debug message during swsusp
> |
> |[2.] Full description of the problem/report:
> |
> |While swsusp'ing to disk, vast quantities of error messages are echoed to the
> |console, along the lines of the following pulled from /var/log/messages:
>
> This Problem is net lay resume recall problem. Try this patch, From
> |my test it can works in net card device, but it can not work in
> |sound card device.
With this and CONFIG_PREEMPT on, do you see any "scheduling while
atomic" messages? I do not think this can fix them completely...
Pavel
> -------------------------
> --- linus-2.5/kernel/suspend.c Fri Oct 18 09:22:36 2002
> +++ linus-2.5-suspend/kernel/suspend.c Thu Oct 17 20:42:08 2002
> @@ -627,7 +627,7 @@
> /* Make disk drivers accept operations, again */
> static void drivers_unsuspend(void)
> {
> - device_resume(RESUME_RESTORE_STATE);
> + /* device_resume(RESUME_RESTORE_STATE); */
> device_resume(RESUME_ENABLE);
> }
>
> @@ -655,7 +655,7 @@
> static void drivers_resume(int flags)
> {
> if (flags & RESUME_PHASE1) {
> - device_resume(RESUME_RESTORE_STATE);
> + /* device_resume(RESUME_RESTORE_STATE); */
> device_resume(RESUME_ENABLE);
> }
> if (flags & RESUME_PHASE2) {
>
>
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
prev parent reply other threads:[~2002-10-26 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 23:36 Bug: swsusp in 2.5.42: "Scheduling while atomic" Eric Altendorf
2002-10-18 1:25 ` Hu Gang
2002-10-23 9:05 ` Pavel Machek [this message]
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=20021023090503.GA3416@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=EricAltendorf@orst.edu \
--cc=hugang@soulinfo.com \
--cc=linux-kernel@vger.kernel.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.