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

> `.exit.text' referenced in section `.init.text' of drivers/built-in.o: 
> defined in discarded section `.exit.text' of drivers/built-in.o


This one is a fatal error ... the code is trying to call a function
that has been marked __exit in a driver that has been built-in, instead
of as a module.  Since a builtin driver can never be unloaded, the kernel
has thrown away all the __exit routines (at link time).

The error message appears less than helpful in tracking down which
routine in which driver is the problem though.

-Tony
-
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: Christoph Lameter <[email protected]>

• Prev by Date: Re: tty-related oops in latest kernel(s)?
• Next by Date: Re: megaraid.c, all kernel versions, problem with multi-luns
• 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]