bad: scheduling while atomic!: how bad?

I'm seeing the message:

bad: scheduling while atomic!

I see this dozens of times when I'm writing to a nand flash device using a vendor-provided driver from Compulab in 2.6.8.1. Does this mean the driver has a bug or is incompatible with the preemptive configuration option? How bad is "bad"? Should I turn of the preemption option, ignore the message, or what?

Thanks...

                     David

_________________________________________________________________

Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

-
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: bad: scheduling while atomic!: how bad?
    • From: Lee Revell <[email protected]>
  • Re: bad: scheduling while atomic!: how bad?
    • From: Arjan van de Ven <[email protected]>

• Prev by Date: Re: A Great Idea (tm) about reimplementing NLS.
• Next by Date: Re: 2.6.12: connection tracking broken?
• Previous by thread: Re: does AHCI work on intel 915 ICH6 controllers? Is it supposed to?
• Next by thread: Re: bad: scheduling while atomic!: how bad?
• 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]