From: Folkert van Heusden <folkert@vanheusden.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.21.1] soft lockup detected on CPU#1 - timers
Date: Mon, 4 Jun 2007 19:29:38 +0200 [thread overview]
Message-ID: <20070604172938.GO30199@vanheusden.com> (raw)
Hi,
Suddenly out of the blue (NO powertop was running or so) my system threw
a message in the logging about a soft lockup:
[330718.331426] BUG: soft lockup detected on CPU#1!
[330718.331483] [<c1004d53>] show_trace_log_lvl+0x1a/0x30
[330718.331574] [<c1004d7b>] show_trace+0x12/0x14
[330718.331661] [<c1004e75>] dump_stack+0x16/0x18
[330718.331747] [<c104dd77>] softlockup_tick+0xa6/0xc2
[330718.331834] [<c1026855>] run_local_timers+0x12/0x14
[330718.331923] [<c1026669>] update_process_times+0x72/0xa1
[330718.332009] [<c103867b>] tick_sched_timer+0x53/0xb6
[330718.332094] [<c1033d6a>] hrtimer_interrupt+0x189/0x1e3
[330718.332180] [<c100e9e2>] local_apic_timer_interrupt+0x55/0x5b
[330718.332268] [<c100ea12>] smp_apic_timer_interrupt+0x2a/0x39
[330718.332354] [<c1004a3f>] apic_timer_interrupt+0x33/0x38
[330718.332441] [<c10020f2>] cpu_idle+0x6b/0x85
[330718.332526] [<c130e218>] start_secondary+0xe8/0x30a
[330718.333480] [<00000000>] 0x0
[330718.333579] =======================
I'm a little puzzled why cpu_idle is called anyway as the load of the
system is on average at least 2.5 (see
http://keetweej.vanheusden.com/load.png ).
Folkert van Heusden
--
Multitail - gibkaja utilita po sledovaniju log-fajlov i vyvoda
kommand. Fil'trovanie, raskrašivanie, slijanie, vizual'noe sravnenie,
i t.d. http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
reply other threads:[~2007-06-04 17:29 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=20070604172938.GO30199@vanheusden.com \
--to=folkert@vanheusden.com \
--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