Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1233710
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Tracing IRQ-flags |
| Date | 2015-09-27 19:00 +0200 |
| Message-ID | <qdnsR-4yp-3@gated-at.bofh.it> (permalink) |
| References | <qdkbE-8pw-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Tracing IRQ-flags Sedat Dilek <sedat.dilek@gmail.com> - 2015-09-27 15:30 +0200 Re: Tracing IRQ-flags Steven Rostedt <rostedt@goodmis.org> - 2015-09-27 19:00 +0200
csiph-web