From: Sedat Dilek <sedat.dilek@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Darren Hart <dvhart@linux.intel.com>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [Linux v4.2] workqueue: llvmlinux: acpid: BUG: sleeping function called from invalid context at kernel/workqueue.c:2680
Date: Sun, 27 Sep 2015 10:33:35 +0200 [thread overview]
Message-ID: <CA+icZUUYQotTKZQowMdNrVB4Bit1PizztS8PqN2FKPyHWwJnpw@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUW1XeBxJP7Ju5-M5qbqqLi5VvezY0qODA5RJKt1fb5g1A@mail.gmail.com>
On Sun, Sep 27, 2015 at 10:10 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On Fri, Sep 25, 2015 at 3:13 PM, Jiri Kosina <jikos@kernel.org> wrote:
>> On Fri, 25 Sep 2015, Sedat Dilek wrote:
>>
>>> > The sequence looks correct. So I don't really see what call sequence could
>>> > lead to calling flush_work() from __cancel_work_timer() with IRQs
>>> > disabled (which is what your stacktrace is suggesting).
>>> >
>>> > The fact that this doesn't happen with GCC-compiled kernels is really
>>> > suspicious.
>>> >
>>>
>>> Hm, and now?
>>
>> I guess one of the things to try is to generate ftrace graph trace to see
>> what exact function sequence leads to this warning.
>>
>
> Which kernel-config settings are helpful for ftrace and tracing at all?
>
> I have here...
>
> CONFIG_IRQSOFF_TRACER=n
>
> ...is that helpful to trigger why I see "irqs_disabled"...
>
> [ 23.874836] BUG: sleeping function called from invalid context at
> kernel/workqueue.c:2678
> [ 23.874902] in_atomic(): 0, irqs_disabled(): 1, pid: 1411, name: acpid
>
> Also independent of this issue I would like to set...
>
> CONFIG_LOCKDEP=y
> CONFIG_DEBUG_LOCKDEP=y <--- XXX: New setting
>
> I recall something like a trace/tracing filesystem?
> I cannot find or remember the Kconfig - do you?
>
It is CONFIG_TRACING=y (see [1] and "tracefs: Add new tracefs file
system" from [2]).
- Sedat -
[1] https://lwn.net/Articles/631798/
[2] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4282d60689d4f21b40692029080440cc58e8a17d
next prev parent reply other threads:[~2015-09-27 8:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 10:24 Sedat Dilek
2015-09-10 1:04 ` Lai Jiangshan
2015-09-10 14:52 ` Tejun Heo
2015-09-10 14:53 ` Tejun Heo
2015-09-11 16:12 ` Sedat Dilek
2015-09-14 11:41 ` Sedat Dilek
2015-09-14 14:00 ` Sedat Dilek
2015-09-14 15:25 ` Sedat Dilek
2015-09-23 23:59 ` Sedat Dilek
2015-09-24 6:41 ` Sedat Dilek
2015-09-24 7:57 ` Jiri Kosina
2015-09-24 8:03 ` Jiri Kosina
2015-09-24 8:12 ` Sedat Dilek
2015-09-24 8:21 ` Jiri Kosina
2015-09-25 6:43 ` Sedat Dilek
[not found] ` <CA+icZUWL38tTepmnV0T=TD6aGQKyHbg1rGzD-b_ZW06CPR9s6g@mail.gmail.com>
2015-09-25 12:00 ` Jiri Kosina
2015-09-25 12:13 ` Sedat Dilek
2015-09-25 12:16 ` Jiri Kosina
2015-09-25 12:22 ` Sedat Dilek
2015-09-25 12:40 ` Jiri Kosina
2015-09-25 12:47 ` Sedat Dilek
2015-09-25 13:13 ` Jiri Kosina
2015-09-25 13:18 ` Sedat Dilek
2015-09-27 8:10 ` Sedat Dilek
2015-09-27 8:33 ` Sedat Dilek [this message]
2015-09-28 6:50 ` Sedat Dilek
2015-09-28 7:17 ` Sedat Dilek
2015-09-25 12:36 ` Sedat Dilek
2015-09-24 8:08 ` Sedat Dilek
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=CA+icZUUYQotTKZQowMdNrVB4Bit1PizztS8PqN2FKPyHWwJnpw@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=jiangshanlai@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®