If this issue comes up when you are using bluetooth, please test the
kernel with version ending in ~lp534549 at
http://people.canonical.com/~cndougla/534549/. Otherwise, if you can
figure out how to trigger the issue please install the other kernel (the
sched_trace one) and do the following:
# echo function >/sys/kernel/debug/tracing/current_tracer
# ech0 1 >/sys/kernel/debug/tracing/options/latency-format
# echo 1 >/sys/kernel/debug/tracing/tracing_enabled
Then do whatever you need to trigger the issue. Once the bug has been
triggered, do:
# cat /sys/kernel/debug/tracing/trace | bzip2 >/tmp/trace.bz2
Finally, attach the trace.bz2 file to this bug so we can take a look.
If you can't figure out a reproduction scenario, try to run the commands
anyways. When you get an apport notification of the bug, capture the
trace output. I think this will still be safe, but I'm not 100%
positive. If you've captured the trace file and it's exceedingly large,
feel free to cut out all but the last few hundred lines.
Thanks
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** Changed in: linux (Ubuntu)
Importance: Low => Medium
--
BUG: scheduling while atomic: swapper/0/0x10000100
https://bugs.launchpad.net/bugs/530435
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
