From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Eyal Cohen <eyalc@asocstech.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Getting "BUG: sleeping function"
Date: Fri, 7 Jun 2013 10:54:01 +0200 [thread overview]
Message-ID: <20130607085401.GB10280@linutronix.de> (raw)
In-Reply-To: <3AE1C3304537E04B84F686355CB6716501C09073@mail-srv.asocstech.com>
* Eyal Cohen | 2013-05-09 11:46:11 [+0300]:
>Hello.
Hi,
>All seems to work smoothly, except I'm getting a BUG "sleeping function
>called from invalid context" print for calling "pci_unregister_driver()"
>from my module exit function.
>>From what I understand, the exit function is called from the rmmod
>process, using a regular thread and should not be in atomic mode.
>Therefore it should be able to acquire spinlocks without problem, since
>it could sleep.
>So why is this happening?
My guess would be that you disabled interrupts somewhere in MPUExit().
Sebastian
prev parent reply other threads:[~2013-06-07 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 8:46 Getting "BUG: sleeping function" Eyal Cohen
2013-06-07 8:54 ` Sebastian Andrzej Siewior [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=20130607085401.GB10280@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=eyalc@asocstech.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).