From: Hannes Dorbath <light@theendofthetunnel.de>
To: xfs@oss.sgi.com
Subject: BUG: soft lockup detected on CPU#0!
Date: Tue, 19 Jun 2007 16:34:38 +0200 [thread overview]
Message-ID: <4677E97E.5070802@theendofthetunnel.de> (raw)
I got this on a server box today. Kernel 2.6.21, x86_64, LVM2:
Jun 19 10:58:16 phoenix Ending XFS recovery on filesystem: dm-5 (logdev:
internal)
Jun 19 10:58:16 phoenix BUG: soft lockup detected on CPU#0!
Jun 19 10:58:16 phoenix
Jun 19 10:58:16 phoenix Call Trace:
Jun 19 10:58:16 phoenix <IRQ> [<ffffffff80277a60>]
wake_up_process+0x10/0x20
Jun 19 10:58:16 phoenix [<ffffffff80297829>] softlockup_tick+0xe9/0x110
Jun 19 10:58:16 phoenix [<ffffffff8024dc93>] run_local_timers+0x13/0x20
Jun 19 10:58:16 phoenix [<ffffffff802815e7>] update_process_times+0x57/0x90
Jun 19 10:58:16 phoenix [<ffffffff8026eea4>]
smp_local_timer_interrupt+0x34/0x60
Jun 19 10:58:16 phoenix [<ffffffff8026f49e>]
smp_apic_timer_interrupt+0x4e/0x70
Jun 19 10:58:16 phoenix [<ffffffff8025ed56>] apic_timer_interrupt+0x66/0x70
Jun 19 10:58:16 phoenix <EOI> [<ffffffff8026368c>]
_spin_unlock_irqrestore+0xc/0x10
Jun 19 10:58:16 phoenix [<ffffffff80221acb>] __up_read+0x9b/0xb0
Jun 19 10:58:16 phoenix [<ffffffff8028d6e9>] up_read+0x9/0x10
Jun 19 10:58:16 phoenix [<ffffffff8034699d>] xfs_iunlock+0x3d/0xa0
Jun 19 10:58:16 phoenix [<ffffffff80362b1a>] xfs_rwunlock+0x3a/0x50
Jun 19 10:58:16 phoenix [<ffffffff80369c46>] xfs_vm_bmap+0x66/0x90
Jun 19 10:58:16 phoenix [<ffffffff8025cecc>] bmap+0x1c/0x20
Jun 19 10:58:16 phoenix [<ffffffff802a684e>] sys_swapon+0x6ae/0xae0
Jun 19 10:58:16 phoenix [<ffffffff8025e11e>] system_call+0x7e/0x83
What does it tell me?
--
Regards,
Hannes Dorbath
next reply other threads:[~2007-06-19 14:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 14:34 Hannes Dorbath [this message]
2007-06-20 3:29 ` BUG: soft lockup detected on CPU#0! David Chinner
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 22:54 Luke S Crawford
2007-09-10 2:14 Abhinav Srivastava
2007-07-25 19:41 Christoph Pfister
2007-07-27 19:30 ` Michal Piotrowski
2007-07-27 20:04 ` Christoph Pfister
2007-08-07 8:49 ` Christoph Pfister
2007-07-14 11:19 CIJOML
2007-05-09 12:41 Ralf Hildebrandt
2006-06-06 13:06 robee
2006-06-02 1:02 Marc Koschewski
2006-06-02 1:04 ` Marc Koschewski
2006-06-02 1:54 ` Andrew Morton
2006-05-11 17:33 Linux 2.6.16.16 Chris Wright
2006-05-11 18:03 ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51 ` Winn Johnston
2006-04-05 2:39 Christopher S. Aker
2006-04-05 2:45 ` Itamar Reis Peixoto
2006-04-05 10:16 ` Keir Fraser
2006-04-05 18:32 ` Christopher S. Aker
2006-04-06 6:56 ` Keir Fraser
2006-04-06 9:23 ` Keir Fraser
2006-03-05 12:26 Norbert Wegener
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=4677E97E.5070802@theendofthetunnel.de \
--to=light@theendofthetunnel.de \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.