From: Sam Ravnborg <sam@ravnborg.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
"Luck, Tony" <tony.luck@intel.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
David Chinner <dgc@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-ia64@vger.kernel.org
Subject: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
Date: Fri, 1 Jun 2007 06:17:22 +0200 [thread overview]
Message-ID: <20070601041722.GA30506@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705312105280.30098@schroedinger.engr.sgi.com>
On Thu, May 31, 2007 at 09:05:54PM -0700, Christoph Lameter wrote:
> On Thu, 31 May 2007, Prarit Bhargava wrote:
>
> > I used the sn2_defconfig in the tree :)
>
> That is a static kernel build. Ideal for that kind of bug.
Quite the opposite.
If modpost cannot resolve symbols you are jsut told what
top-level file it is in.
A allmodconfig should be more useful and give you warnings in all normal
cases.
Let me know if I shall look over some of the warnings.
Sam
next prev parent reply other threads:[~2007-06-01 4:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 6:31 BUG: sleeping function called from invalid context at kernel/fork.c:385 David Chinner
2007-05-23 6:43 ` Andrew Morton
2007-05-23 17:44 ` Luck, Tony
2007-05-30 3:30 ` David Chinner
2007-05-30 4:44 ` David Chinner
2007-05-30 20:11 ` Luck, Tony
2007-05-30 22:39 ` Christoph Lameter
2007-05-30 23:19 ` Luck, Tony
2007-05-30 23:31 ` Christoph Lameter
2007-05-30 23:34 ` Randy Dunlap
2007-05-30 23:53 ` Christoph Lameter
2007-05-30 23:55 ` Randy Dunlap
2007-05-31 0:09 ` Christoph Lameter
2007-05-31 2:37 ` Luck, Tony
2007-05-31 3:19 ` Christoph Lameter
2007-05-31 15:20 ` Prarit Bhargava
2007-05-31 19:54 ` Sam Ravnborg
2007-05-31 20:04 ` Sam Ravnborg
2007-05-31 20:08 ` [PATCH] net/hp100: fix section mismatch warning Sam Ravnborg
2007-05-31 20:17 ` [PATCH] kvm: fix section mismatch warning in kvm-intel.o Sam Ravnborg
2007-05-31 20:24 ` [PATCH] acpi: fix section mismatch warning in asus_acpi.o Sam Ravnborg
2007-05-31 20:29 ` [PATCH] acpi: fix section mismatch warning in asus + toshiba Sam Ravnborg
2007-05-31 20:46 ` [PATCH] isdn: fix section mismatch warnings Sam Ravnborg
2007-05-31 20:51 ` [PATCH] microcode: fix section mismatch warning Sam Ravnborg
2007-05-31 20:42 ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Christoph Lameter
2007-06-01 3:18 ` Luck, Tony
2007-06-01 3:31 ` Prarit Bhargava
2007-06-01 4:05 ` Christoph Lameter
2007-06-01 4:17 ` Sam Ravnborg [this message]
2007-06-01 4:45 ` Christoph Lameter
2007-06-01 6:42 ` Sam Ravnborg
2007-06-01 8:00 ` Luck, Tony
2007-06-01 10:30 ` Prarit Bhargava
2007-06-01 10:37 ` Luck, Tony
2007-06-05 14:55 ` linux-ia64 build warning messages Russ Anderson
2007-06-07 5:00 ` Peter Chubb
2007-05-31 6:12 ` BUG: sleeping function called from invalid context at kernel/fork.c:385 Randy Dunlap
2007-05-31 4:43 ` Sam Ravnborg
2007-05-31 0:53 ` David Chinner
2007-06-04 5:14 ` Peter Chubb
[not found] <f1318b470705301650y5ed9fdbn12ad0ebe30233336@mail.gmail.com>
2007-05-30 23:56 ` Yu, Fenghua
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=20070601041722.GA30506@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=dgc@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=randy.dunlap@oracle.com \
--cc=tony.luck@intel.com \
/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