From: "Matthew L. Creech" <mlcreech@gmail.com>
To: Sergej.Stepanov@ids.de
Cc: linuxppc-dev@ozlabs.org
Subject: Re: fsl_udc_core: BUG: scheduling while atomic
Date: Thu, 12 May 2011 11:30:51 -0400 [thread overview]
Message-ID: <BANLkTim8ntQHkcm_yOgD+UQQb+b+tSoFqA@mail.gmail.com> (raw)
In-Reply-To: <4206182445660643B9AEB8D4E55BBD0A1533BC2780@HERMES2>
On Thu, May 12, 2011 at 4:37 AM, <Sergej.Stepanov@ids.de> wrote:
> Hi Mattheew,
>
> such oops you can get also with spi.
> For such problem helps to compile your kernel with other preemption
> model:
> =A0- preempt
> =A0- standard
> =A0- !!! but not voluntary preemption !!!
Thanks Sergej, indeed I'm currently using CONFIG_PREEMPT_VOLUNTARY on
this board. I'll change it to fix this problem for now.
Do you happen to know whether the Freescale folks intend to fix this?
If not, it seems like at least some sort of warning is in order.
--=20
Matthew L. Creech
next prev parent reply other threads:[~2011-05-12 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 21:37 fsl_udc_core: BUG: scheduling while atomic Matthew L. Creech
2011-05-12 8:37 ` Sergej.Stepanov
2011-05-12 15:30 ` Matthew L. Creech [this message]
2011-05-13 8:34 ` Sergej.Stepanov
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=BANLkTim8ntQHkcm_yOgD+UQQb+b+tSoFqA@mail.gmail.com \
--to=mlcreech@gmail.com \
--cc=Sergej.Stepanov@ids.de \
--cc=linuxppc-dev@ozlabs.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).