The preempt_counter shows both PREEMPT_ACTIVE and in a softirq context.
I *think* this likely means a process was in the middle of a softirq
handler or a tasklet when a subroutine put it to sleep. I'm building a
test kernel right now that will output extra debug information so we can
see what the softirq stack was as it was put to scheduled out. I'll
update this bug with a test kernel location when I get it uploaded.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chase Douglas (chasedouglas)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
BUG: scheduling while atomic: swapper/0/0x10000100
https://bugs.launchpad.net/bugs/534549
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
