From: Nathan_Lynch@mentor.com (Nathan Lynch)
Subject: [lttng-dev] might_sleep warnings in overwrite mode
Date: Mon, 11 Nov 2013 09:47:21 -0600 [thread overview]
Message-ID: <5280FC09.7030208@mentor.com> (raw)
In-Reply-To: <52803E5D.3050109@mentor.com>
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?
next prev parent reply other threads:[~2013-11-11 15:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 2:18 Nathan Lynch
2013-11-11 15:47 ` Nathan Lynch [this message]
2013-11-14 18:16 ` Nathan Lynch
2013-11-15 2:34 ` Mathieu Desnoyers
2013-11-18 19:30 ` Nathan Lynch
2013-11-19 15:29 ` [lttng-dev] current_thread_info() not respecting program order with gcc 4.8.x Mathieu Desnoyers
2013-11-19 15:57 ` Peter Zijlstra
2013-11-19 16:13 ` Jakub Jelinek
2013-11-19 16:21 ` Peter Zijlstra
2013-11-19 16:05 ` Will Deacon
2013-11-19 17:02 ` Mathieu Desnoyers
2013-11-19 17:33 ` Peter Zijlstra
2013-11-19 21:56 ` [lttng-dev] Multiple local register variables w/ same register Richard Henderson
2013-11-19 22:08 ` Jakub Jelinek
2013-11-19 22:13 ` Måns Rullgård
2013-11-19 22:25 ` Mathieu Desnoyers
2013-11-19 22:34 ` Mathieu Desnoyers
2013-11-20 0:41 ` [lttng-dev] current_thread_info() not respecting program order with gcc 4.8.x Linus Torvalds
2013-11-20 15:10 ` Mathieu Desnoyers
2013-11-21 16:02 ` Alexander Holler
2013-11-21 22:12 ` Luis Lozano
2013-11-21 22:32 ` Linus Torvalds
2013-11-21 23:03 ` Bhaskar Janakiraman
2013-11-21 23:18 ` Alexander Holler
2013-11-21 23:45 ` Luis Lozano
2013-11-22 0:39 ` Jakub Jelinek
2013-11-22 1:57 ` Mathieu Desnoyers
2013-11-22 2:36 ` Luis Lozano
2013-11-22 3:38 ` Mathieu Desnoyers
2013-11-22 8:16 ` Luis Lozano
2013-11-22 13:02 ` Mathieu Desnoyers
2013-11-22 8:18 ` Luis Lozano
2013-11-22 8:33 ` Luis Lozano
2013-11-22 13:06 ` Mathieu Desnoyers
2013-11-22 20:33 ` Mathieu Desnoyers
2013-11-22 0:17 ` Linus Torvalds
2013-11-22 0:34 ` Alexander Holler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5280FC09.7030208@mentor.com \
--to=nathan_lynch@mentor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox