From: louis@museresearch.com
To: linux-rt-users@vger.kernel.org
Subject: Suspend: Mem leak and "sleeping function .. invalid context"
Date: Tue, 22 Jun 2010 13:11:24 -0700 [thread overview]
Message-ID: <668e33c19aa7d25f3a95bc750068e2bb.squirrel@master.museresearch.com> (raw)
Hi, I've come across a bug when using the RT patch in Fedora 8 (CCRMA
kernel derivative): When I suspend, I get a "BUG: sleeping function
called from invalid context pm-suspend" message. After resuming, I see a
memory leak that can rapidly eat memory just by doing this in BASH:
"while /bin/true; do continue; done". The system will slow and then
finally lock up with "free" reporting approx. 1 GB left (on a 2 GB
system).
This has been seen on both the Intel D510MO motherboard and the Intel
DQ35JOE board. I have tried the CCRMA kernel
2.6.33.4-106.rt20.1.fc13.ccrma.i686.rtPAE and a custom kernel based off
the 2.6.24.3-1 CCRMA kernel. Versions of the kernel without the rt patch
do not fail (tried the stock FC8 kernel and stock FC11 kernel).
Here is a snippit of the backtrace I get:
kernel: BUG: sleeping function called from invalid context
pm-suspend(14941) at kernel/rtmutex.c:638
kernel: in_atomic():1 [00000001], irqs_disabled():1
kernel: Pid: 14941, comm: pm-suspend Not tainted
2.6.24.3-1.rec15.rt1.fc8rt #1
kernel: [<c0699de1>] __rt_spin_lock+0x21/0x5e
kernel: [<c04898ce>] kfree+0x29/0x88
kernel: [<c0427be5>] rq_attach_root+0x5b/0xac
kernel: [<c042a2df>] cpu_attach_domain+0x2af/0x2ef
kernel: [<c0489929>] kfree+0x84/0x88
kernel: [<c0489929>] kfree+0x84/0x88
kernel: [<c042a33f>] detach_destroy_domains+0x20/0x33
The line number in question is:
/* Temporary HACK! */
if (!current->in_printk)
might_sleep(); <--- line 638
I've found similar threads before, but did not see a resolution to this
problem on the x86 architecture (it looks like a similar problem might
have been solved on ARM..?).
Thanks for your help,
Louis
reply other threads:[~2010-06-22 20:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=668e33c19aa7d25f3a95bc750068e2bb.squirrel@master.museresearch.com \
--to=louis@museresearch.com \
--cc=linux-rt-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).