From: Chris Rankin <rankincj@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Soft lockup with 2.6.17.7
Date: Sat, 26 Aug 2006 12:35:41 +0100 (BST) [thread overview]
Message-ID: <20060826113541.35969.qmail@web52906.mail.yahoo.com> (raw)
[Linux 2.6.17.7-SMP, dual P4 Xeon (hyperthreaded), 2 GB RAM]
Hi,
My 2.6.17.7 workstation locked up the other night, and wrote these messages to the serial console:
The system is going down for reboot NOW!
[root@volcano chris]# BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
BUG: soft lockup detected on CPU#2!
<c0130b5f> softlockup_tick+0x9c/0xb1 <c011fae8> update_process_times+0x3d/0x60
<c010d5ea> smp_apic_timer_interrupt+0x52/0x58 <c0103320> apic_timer_interrupt+0x1c/0x24
<c010c192> flush_tlb_others+0x7e/0xab <c010c364> flush_tlb_page+0x85/0xa6
<c013b7f7> do_wp_page+0x223/0x283 <c013ca3f> __handle_mm_fault+0x6aa/0x70d
<c0110f99> do_page_fault+0x20f/0x532 <c0110d8a> do_page_fault+0x0/0x532
<c01033eb> error_code+0x4f/0x54
I was trying to run World of Warcraft under Wine, while simultaneously compiling MESA, and so I
suspect that a lot of my RAM was active at the time.
Cheers,
Chris
___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
reply other threads:[~2006-08-26 11:35 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=20060826113541.35969.qmail@web52906.mail.yahoo.com \
--to=rankincj@yahoo.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
all inboxes | Powered by JetHome®