Re: scheduling while atomic & hang.

[H. Peter Anvin]

On 07/03/2013 07:49 PM, Linus Torvalds wrote:
> >  [<ffffffff816f42bf>] __schedule+0x94f/0x9c0
> >  [<ffffffff816f487e>] schedule_user+0x2e/0x70
> >  [<ffffffff816f6de4>] retint_careful+0x12/0x2e

This call trace does indeed indicate that we took a hardware interrupt 
which caused a reschedule.  It doesn't necessarily have to be a quantum 
expiration interrupt, it could just as easily be an I/O completion 
interrupt.

	-hpa

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/