* what does this mean?
@ 2006-05-16 16:51 Steve Iribarne (GMail)
2006-05-16 17:38 ` Walter L. Wimer III
0 siblings, 1 reply; 4+ messages in thread
From: Steve Iribarne (GMail) @ 2006-05-16 16:51 UTC (permalink / raw)
To: linuxppc-embedded
My code is hitting in sched.c ->
=09if (unlikely(in_interrupt())) {
=09=09printk("Scheduling in interrupt\n");
=09=09BUG();
=09}
It is hitting this printk. So is this telling me I'm calling schedule
from within an interrupt? How can this be? Has anyone else seen
something like this and can anyone give me a hint as to what to look
for.
Thanks.
-stv
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: what does this mean?
2006-05-16 16:51 what does this mean? Steve Iribarne (GMail)
@ 2006-05-16 17:38 ` Walter L. Wimer III
2006-05-16 17:42 ` Walter L. Wimer III
0 siblings, 1 reply; 4+ messages in thread
From: Walter L. Wimer III @ 2006-05-16 17:38 UTC (permalink / raw)
To: Steve Iribarne (GMail); +Cc: linuxppc-embedded
On Tue, 2006-05-16 at 09:51 -0700, Steve Iribarne (GMail) wrote:
> My code is hitting in sched.c ->
>
> if (unlikely(in_interrupt())) {
> printk("Scheduling in interrupt\n");
> BUG();
> }
> It is hitting this printk. So is this telling me I'm calling schedule
> from within an interrupt? How can this be? Has anyone else seen
> something like this and can anyone give me a hint as to what to look
> for.
Check to make sure that in your interrupt handler you are not calling
something that can sleep. E.g. sleep(), usleep(), kmalloc(), vmalloc(),
etc.
> Thanks.
> -stv
Best regards,
Walt Wimer
TimeSys Corporation
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: what does this mean?
2006-05-16 17:38 ` Walter L. Wimer III
@ 2006-05-16 17:42 ` Walter L. Wimer III
2006-05-16 18:04 ` Steve Iribarne (GMail)
0 siblings, 1 reply; 4+ messages in thread
From: Walter L. Wimer III @ 2006-05-16 17:42 UTC (permalink / raw)
To: Steve Iribarne (GMail); +Cc: linuxppc-embedded
On Tue, 2006-05-16 at 13:38 -0400, Walter L. Wimer III wrote:
> Check to make sure that in your interrupt handler you are not calling
> something that can sleep. E.g. sleep(), usleep(), kmalloc(),
> vmalloc(), etc.
Also watch out for semaphore operations such as down() and
down_interruptible(). They can sleep too.
Walt
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: what does this mean?
2006-05-16 17:42 ` Walter L. Wimer III
@ 2006-05-16 18:04 ` Steve Iribarne (GMail)
0 siblings, 0 replies; 4+ messages in thread
From: Steve Iribarne (GMail) @ 2006-05-16 18:04 UTC (permalink / raw)
To: Walter L. Wimer III; +Cc: linuxppc-embedded
Thanks. That's what I think it is, but I didn't write this code so
I'm trying to track down
who is calling down at interrupt time.
On 5/16/06, Walter L. Wimer III <walt.wimer@timesys.com> wrote:
> On Tue, 2006-05-16 at 13:38 -0400, Walter L. Wimer III wrote:
> > Check to make sure that in your interrupt handler you are not calling
> > something that can sleep. E.g. sleep(), usleep(), kmalloc(),
> > vmalloc(), etc.
>
> Also watch out for semaphore operations such as down() and
> down_interruptible(). They can sleep too.
>
>
> Walt
>
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-05-16 18:04 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-16 16:51 what does this mean? Steve Iribarne (GMail)
2006-05-16 17:38 ` Walter L. Wimer III
2006-05-16 17:42 ` Walter L. Wimer III
2006-05-16 18:04 ` Steve Iribarne (GMail)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox