Re: BUG: sleeping function called from invalid context at kernel/fork.c:385

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
  - From: Christoph Lameter <[email protected]>

References:
- RE: BUG: sleeping function called from invalid context at kernel/fork.c:385
  - From: "Luck, Tony" <[email protected]>
- Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
  - From: Prarit Bhargava <[email protected]>
- Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
  - From: Christoph Lameter <[email protected]>

Prev by Date: [PATCH] slab: Fix slab debug for non alien caches.
Next by Date: [PATCH] sparsemem: Shut up unused symbol compiler warnings.
Previous by thread: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
Next by thread: Re: BUG: sleeping function called from invalid context at kernel/fork.c:385
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]