From: Karsten Wiese <fzuuzf@googlemail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Georgiewskiy Yuriy <bottleman@icf.org.ru>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.0.14-rt31
Date: Sat, 24 Dec 2011 01:02:54 +0100 [thread overview]
Message-ID: <CAM=nh0S1zNoR7WHgQDQ2rspc3qGcKxF8nQ-VyLPhcCCGV+5gEA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1112222031390.22183@icf.org.ru>
Hi Steven,
below trace shows regularly here:
[ 3560.172428] BUG: sleeping function called from invalid context at
kernel/rtmutex.c:645
[ 3560.172431] in_atomic(): 1, irqs_disabled(): 1, pid: 28, name: irq/9-acpi
[ 3560.172434] 1 lock held by irq/9-acpi/28:
[ 3560.172436] #0: (acpi_gbl_gpe_lock){+.+...}, at: [<c0644c8e>]
acpi_ev_gpe_detect+0x29/0x12f
[ 3560.172447] irq event stamp: 9680
[ 3560.172449] hardirqs last enabled at (9679): [<c0850a19>]
_raw_spin_unlock_irq+0x27/0x48
[ 3560.172455] hardirqs last disabled at (9680): [<c0850831>]
_raw_spin_lock_irqsave+0x1c/0x82
[ 3560.172460] softirqs last enabled at (0): [<c043ed99>]
copy_process+0x530/0x1086
[ 3560.172464] softirqs last disabled at (0): [< (null)>] (null)
[ 3560.172469] Pid: 28, comm: irq/9-acpi Not tainted
3.0.14-1.rt31.1.fc16.ccrma.i686.rt #1
[ 3560.172471] Call Trace:
[ 3560.172476] [<c0432ad7>] __might_sleep+0xf4/0xfb
[ 3560.172479] [<c085004e>] rt_spin_lock+0x1f/0x56
[ 3560.172483] [<c04f5c71>] __local_lock_irq+0x1e/0x5b
[ 3560.172486] [<c04f5cc7>] __local_lock_irqsave+0x19/0x27
[ 3560.172490] [<c04f75ce>] kmem_cache_alloc_trace+0x67/0xf5
[ 3560.172493] [<c0644833>] ? acpi_os_allocate_zeroed+0x2f/0x2f
[ 3560.172497] [<c0632a9f>] __acpi_os_execute+0x66/0x15b
[ 3560.172501] [<c0644833>] ? acpi_os_allocate_zeroed+0x2f/0x2f
[ 3560.172504] [<c0632bab>] acpi_os_execute+0x17/0x19
[ 3560.172508] [<c0644c0c>] acpi_ev_gpe_dispatch+0xe4/0x13d
[ 3560.172511] [<c0644d54>] acpi_ev_gpe_detect+0xef/0x12f
[ 3560.172516] [<c064314e>] acpi_ev_sci_xrupt_handler+0x1a/0x20
[ 3560.172519] [<c0632c22>] acpi_irq+0x13/0x2e
[ 3560.172522] [<c049c730>] irq_forced_thread_fn+0x1d/0x36
[ 3560.172525] [<c049c607>] irq_thread+0xc0/0x1a0
[ 3560.172529] [<c0439b19>] ? migrate_enable+0x124/0x133
[ 3560.172532] [<c049c713>] ? irq_thread_fn+0x2c/0x2c
[ 3560.172535] [<c049c547>] ? irq_finalize_oneshot+0x94/0x94
[ 3560.172539] [<c045b336>] kthread+0x76/0x7b
[ 3560.172544] [<c05f24b4>] ? trace_hardirqs_on_thunk+0xc/0x10
[ 3560.172548] [<c0850cbd>] ? restore_all+0xf/0xf
[ 3560.172551] [<c045b2c0>] ? __init_kthread_worker+0x67/0x67
[ 3560.172555] [<c0856802>] kernel_thread_helper+0x6/0x10
next prev parent reply other threads:[~2011-12-24 0:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 3:40 [ANNOUNCE] 3.0.14-rt31 Steven Rostedt
2011-12-22 11:08 ` Raz
2011-12-22 11:50 ` Steven Rostedt
2011-12-22 14:00 ` Georgiewskiy Yuriy
2011-12-22 14:44 ` Steven Rostedt
2011-12-22 15:29 ` Georgiewskiy Yuriy
2011-12-22 16:23 ` Steven Rostedt
2011-12-22 16:35 ` Georgiewskiy Yuriy
2011-12-24 0:02 ` Karsten Wiese [this message]
2011-12-24 14:13 ` Steven Rostedt
2011-12-24 16:16 ` Clark Williams
2012-01-10 18:53 ` Steven Rostedt
2012-01-10 23:56 ` Karsten Wiese
2012-01-04 15:19 ` Georgiewskiy Yuriy
2012-01-11 11:10 ` Karsten Wiese
2012-01-11 15:39 ` Steven Rostedt
2012-01-12 10:18 ` Tim Sander
2012-01-12 13:54 ` Steven Rostedt
2012-01-12 16:57 ` Tim Sander
2012-01-13 9:42 ` Tim Sander
2012-01-13 18:45 ` Bernardo Barros
2012-01-13 20:30 ` Tim Sander
2012-01-13 23:51 ` Steven Rostedt
2012-01-17 14:27 ` [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Tim Sander
2012-01-17 14:42 ` Steven Rostedt
2012-01-17 17:40 ` Mike Galbraith
2012-01-18 11:11 ` [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Yep Tim Sander
2012-01-18 13:54 ` Mike Galbraith
2012-01-18 15:37 ` Steven Rostedt
2012-01-24 10:52 ` Tim Sander
2012-01-25 9:31 ` Tim Sander
2012-02-01 20:27 ` Steven Rostedt
2012-02-01 23:11 ` Tim Sander
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='CAM=nh0S1zNoR7WHgQDQ2rspc3qGcKxF8nQ-VyLPhcCCGV+5gEA@mail.gmail.com' \
--to=fzuuzf@googlemail.com \
--cc=bottleman@icf.org.ru \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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;
as well as URLs for NNTP newsgroup(s).