From: joel silvestre <j.silvestre@wanadoo.fr>
To: linux-kernel@vger.kernel.org
Subject: 2.6.19-rc6-rt9
Date: Wed, 29 Nov 2006 18:16:47 +0100 [thread overview]
Message-ID: <1164820607.3923.50.camel@zordi> (raw)
Hi,
down is an excerpt from dmesg.
Comes from an Intel core duo laptop running
kernel-rt-2.6.18-3.rt9.0001.i686.rpm and Fedora 6.
This kernel boot and run.
joël
BUG: scheduling with irqs disabled: IRQ 9/0x00000001/77
caller is rt_spin_lock_slowlock+0x106/0x18a
[<c0104e1b>] dump_trace+0x64/0x1cc
[<c0104f9c>] show_trace_log_lvl+0x19/0x2e
[<c01052e0>] show_trace+0x12/0x14
[<c01052f9>] dump_stack+0x17/0x19
[<c0334b5b>] schedule+0x71/0xe7
[<c03356b3>] rt_spin_lock_slowlock+0x106/0x18a
[<c0335b55>] rt_spin_lock+0x20/0x22
[<c0137e1a>] __queue_work+0xf/0x4e
[<c0138511>] queue_work+0x70/0x7f
[<c0217e46>] acpi_os_execute+0x62/0x7b
[<c0230cb3>] acpi_ec_gpe_handler+0x6b/0x8b
[<c021e0bd>] acpi_ev_gpe_dispatch+0x68/0x163
[<c021e251>] acpi_ev_gpe_detect+0x99/0xe0
[<c021c859>] acpi_ev_sci_xrupt_handler+0x15/0x1d
[<c02175f4>] acpi_irq+0xe/0x18
[<c0159387>] handle_IRQ_event+0x45/0xc1
[<c01599fa>] thread_simple_irq+0x39/0x6c
[<c0159e3d>] do_irqd+0xdd/0x298
[<c013a9bf>] kthread+0xc2/0xef
[<c0104b5b>] kernel_thread_helper+0x7/0x10
DWARF2 unwinder stuck at kernel_thread_helper+0x7/0x10
Leftover inexact backtrace:
[<c0104f9c>] show_trace_log_lvl+0x19/0x2e
[<c01052e0>] show_trace+0x12/0x14
[<c01052f9>] dump_stack+0x17/0x19
[<c0334b5b>] schedule+0x71/0xe7
[<c03356b3>] rt_spin_lock_slowlock+0x106/0x18a
[<c0335b55>] rt_spin_lock+0x20/0x22
[<c0137e1a>] __queue_work+0xf/0x4e
[<c0138511>] queue_work+0x70/0x7f
[<c0217e46>] acpi_os_execute+0x62/0x7b
[<c0230cb3>] acpi_ec_gpe_handler+0x6b/0x8b
[<c021e0bd>] acpi_ev_gpe_dispatch+0x68/0x163
[<c021e251>] acpi_ev_gpe_detect+0x99/0xe0
[<c021c859>] acpi_ev_sci_xrupt_handler+0x15/0x1d
[<c02175f4>] acpi_irq+0xe/0x18
[<c0159387>] handle_IRQ_event+0x45/0xc1
[<c01599fa>] thread_simple_irq+0x39/0x6c
[<c0159e3d>] do_irqd+0xdd/0x298
[<c013a9bf>] kthread+0xc2/0xef
[<c0104b5b>] kernel_thread_helper+0x7/0x10
=======================
BUG: scheduling while atomic: IRQ 9/0x00000001/77, CPU#0
[<c0104e1b>] dump_trace+0x64/0x1cc
[<c0104f9c>] show_trace_log_lvl+0x19/0x2e
[<c01052e0>] show_trace+0x12/0x14
[<c01052f9>] dump_stack+0x17/0x19
[<c0333cac>] __schedule+0x84/0xd98
[<c0334bb5>] schedule+0xcb/0xe7
[<c03356b3>] rt_spin_lock_slowlock+0x106/0x18a
[<c0335b55>] rt_spin_lock+0x20/0x22
[<c0137e1a>] __queue_work+0xf/0x4e
[<c0138511>] queue_work+0x70/0x7f
[<c0217e46>] acpi_os_execute+0x62/0x7b
[<c0230cb3>] acpi_ec_gpe_handler+0x6b/0x8b
[<c021e0bd>] acpi_ev_gpe_dispatch+0x68/0x163
[<c021e251>] acpi_ev_gpe_detect+0x99/0xe0
[<c021c859>] acpi_ev_sci_xrupt_handler+0x15/0x1d
[<c02175f4>] acpi_irq+0xe/0x18
[<c0159387>] handle_IRQ_event+0x45/0xc1
[<c01599fa>] thread_simple_irq+0x39/0x6c
[<c0159e3d>] do_irqd+0xdd/0x298
[<c013a9bf>] kthread+0xc2/0xef
[<c0104b5b>] kernel_thread_helper+0x7/0x10
DWARF2 unwinder stuck at kernel_thread_helper+0x7/0x10
Leftover inexact backtrace:
[<c0104f9c>] show_trace_log_lvl+0x19/0x2e
[<c01052e0>] show_trace+0x12/0x14
[<c01052f9>] dump_stack+0x17/0x19
[<c0333cac>] __schedule+0x84/0xd98
[<c0334bb5>] schedule+0xcb/0xe7
[<c03356b3>] rt_spin_lock_slowlock+0x106/0x18a
[<c0335b55>] rt_spin_lock+0x20/0x22
[<c0137e1a>] __queue_work+0xf/0x4e
[<c0138511>] queue_work+0x70/0x7f
[<c0217e46>] acpi_os_execute+0x62/0x7b
[<c0230cb3>] acpi_ec_gpe_handler+0x6b/0x8b
[<c021e0bd>] acpi_ev_gpe_dispatch+0x68/0x163
[<c021e251>] acpi_ev_gpe_detect+0x99/0xe0
[<c021c859>] acpi_ev_sci_xrupt_handler+0x15/0x1d
[<c02175f4>] acpi_irq+0xe/0x18
[<c0159387>] handle_IRQ_event+0x45/0xc1
[<c01599fa>] thread_simple_irq+0x39/0x6c
[<c0159e3d>] do_irqd+0xdd/0x298
[<c013a9bf>] kthread+0xc2/0xef
[<c0104b5b>] kernel_thread_helper+0x7/0x10
=======================
reply other threads:[~2006-11-29 17:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1164820607.3923.50.camel@zordi \
--to=j.silvestre@wanadoo.fr \
--cc=linux-kernel@vger.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®