From: Steven Rostedt <rostedt@goodmis.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jikos@kernel.org>, Tejun Heo <tj@kernel.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: Tracing IRQ-flags
Date: Sun, 27 Sep 2015 12:51:29 -0400 [thread overview]
Message-ID: <20150927125129.7741bbcf@gandalf.local.home> (raw)
In-Reply-To: <CA+icZUXtUtUXfYTzr7Qzn6+F4zwhHWpvcGVD1dT1bmGJ+d5m+Q@mail.gmail.com>
On Sun, 27 Sep 2015 15:25:41 +0200
Sedat Dilek <sedat.dilek@gmail.com> wrote:
> Hi Ingo, Hi Steven,
>
> I am still fighting with a llvmlinux problem in the area...
>
> workqueue | hid | irq-flags (hardirqs/sofirqs disabled) | whatever?!
>
> ...(see [0]).
>
> [ 24.705463] BUG: sleeping function called from invalid context at
> kernel/workqueue.c:2680
> [ 24.705576] in_atomic(): 0, irqs_disabled(): 1, pid: 1447, name: acpid
>
> Several people had ideas where to look at - Thanks.
>
> Finally, Jiri encouraged me to try with a ftrace graph trace (see [1]).
Actually, if you are looking for where interrupts were disabled last
before triggering the "sleeping function called from invalid context",
lockdep, not ftrace, would be your better bet.
Enable lockdep with CONFIG_PROVE_LOCKING. It will give you better
information about where the last irq was disabled.
-- Steve
prev parent reply other threads:[~2015-09-27 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 13:25 Sedat Dilek
2015-09-27 16:51 ` Steven Rostedt [this message]
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=20150927125129.7741bbcf@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jikos@kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sedat.dilek@gmail.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®