From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: "Andrew Morton" <akpm@osdl.org>, "Ingo Molnar" <mingo@elte.hu>,
"Arjan van de Ven" <arjan@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc5-mm3: "BUG: scheduling while atomic" flood when resuming from disk
Date: Mon, 5 Jun 2006 17:56:19 +0200 [thread overview]
Message-ID: <200606051756.19715.rjw@sisk.pl> (raw)
In-Reply-To: <986ed62e0606042223l2381d877g4bc798ec64804d43@mail.gmail.com>
On Monday 05 June 2006 07:23, Barry K. Nathan wrote:
> Quoting myself from another recent e-mail:
>
> > BTW, I also tried 2.6.17-rc5-mm3 (with no other patches) on another
> > box of mine, running Ubuntu Dapper Drake. (It was installed with one
> > of the flights but has been updated to the final release.) It got hit
> > with a flood of scheduling-while-atomic BUGs when either suspending to
> > disk or resuming, and eth0 didn't come back up automatically as usual
> > -- I had to manually modprobe r8169 and then run
> > "/etc/init.d/networking restart" to get to the outside world again. I
> > might not be able to provide a more detailed report on this box for
> > another day or two.
>
> The messages definitely happen while resuming. My screen is blank
> during suspend-to-disk so I have no way to know what's going on
> then...
Please try doing "echo 8 > /proc/sys/kernel/printk" before suspend.
Greetings,
Rafael
next prev parent reply other threads:[~2006-06-05 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 5:23 Barry K. Nathan
2006-06-05 5:51 ` Andrew Morton
2006-06-05 6:28 ` Barry K. Nathan
2006-06-07 10:14 ` Barry K. Nathan
2006-06-14 3:57 ` Barry K. Nathan
2006-06-05 15:56 ` Rafael J. Wysocki [this message]
2006-06-05 16:45 ` Barry K. Nathan
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=200606051756.19715.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®