From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 18rc1 soft lockup
Date: Tue, 11 Jul 2006 15:03:46 -0400 [thread overview]
Message-ID: <20060711190346.GK5362@redhat.com> (raw)
Just saw this during boot of a HT P4 box.
BUG: soft lockup detected on CPU#0!
[<c04051af>] show_trace_log_lvl+0x54/0xfd
[<c0405766>] show_trace+0xd/0x10
[<c0405885>] dump_stack+0x19/0x1b
[<c0450ec7>] softlockup_tick+0xa5/0xb9
[<c042d496>] run_local_timers+0x12/0x14
[<c042d81b>] update_process_times+0x3c/0x61
[<c04179e0>] smp_apic_timer_interrupt+0x6d/0x75
[<c0404ada>] apic_timer_interrupt+0x2a/0x30
BUG: soft lockup detected on CPU#1!
[<c04051af>] show_trace_log_lvl+0x54/0xfd
[<c0405766>] show_trace+0xd/0x10
[<c0405885>] dump_stack+0x19/0x1b
[<c0450ec7>] softlockup_tick+0xa5/0xb9
[<c042d496>] run_local_timers+0x12/0x14
[<c042d81b>] update_process_times+0x3c/0x61
[<c04179e0>] smp_apic_timer_interrupt+0x6d/0x75
[<c0404ada>] apic_timer_interrupt+0x2a/0x30
BUG: soft lockup detected on CPU#0!
[<c04051af>] show_trace_log_lvl+0x54/0xfd
[<c0405766>] show_trace+0xd/0x10
[<c0405885>] dump_stack+0x19/0x1b
[<c0450ec7>] softlockup_tick+0xa5/0xb9
[<c042d496>] run_local_timers+0x12/0x14
[<c042d81b>] update_process_times+0x3c/0x61
[<c04179e0>] smp_apic_timer_interrupt+0x6d/0x75
[<c0404ada>] apic_timer_interrupt+0x2a/0x30
It then continued booting just fine..
Dave
--
http://www.codemonkey.org.uk
next reply other threads:[~2006-07-11 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 19:03 Dave Jones [this message]
2006-07-11 19:13 ` 18rc1 soft lockup john stultz
2006-07-11 19:16 ` Dave Jones
2006-07-13 22:07 ` Dave Jones
2006-07-13 22:15 ` john stultz
2006-07-13 22:28 ` Dave Jones
2006-07-14 9:22 ` Roman Zippel
2006-07-14 14:09 ` Dave Jones
2006-07-14 23:30 ` john stultz
2006-07-13 23:05 ` Roman Zippel
2006-07-14 0:02 ` john stultz
2006-07-14 0:12 ` Dave Jones
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=20060711190346.GK5362@redhat.com \
--to=davej@redhat.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