On 11/10/2013 08:18 PM, Nathan Lynch wrote: > At this point I cannot trigger the issue without overwrite mode on > 3.11.6, but on a 3.8-based vendor kernel I can recreate it regardless of > the mode. > > Is it possible that the lttng module code is messing up the current > task's preempt count somehow?
Here's another manifestation of the issue -- when flood-pinging the board during tracing, I get this warning from __do_softirq: huh, entered softirq 3 NET_RX 804ae528 preempt_count 00000101, exited with 00000102? _______________________________________________ lttng-dev mailing list [email protected] http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
