public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@dell.com>
To: Philipp Matthias Hahn <pmhahn@svs.Informatik.Uni-Oldenburg.de>
Cc: openipmi-developer@lists.sourceforge.net,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Soft lockup (and reboot): IPMI
Date: Mon, 14 Aug 2006 16:02:31 -0500	[thread overview]
Message-ID: <20060814210231.GB3637@lists.us.dell.com> (raw)
In-Reply-To: <44E0A176.8070907@svs.Informatik.Uni-Oldenburg.de>

On Mon, Aug 14, 2006 at 06:14:46PM +0200, Philipp Matthias Hahn wrote:
> Hello!
> 
> While playing with "openipmigui", the server just rebooted with the
> following last message:
> 
> BUG: soft lockup detected on CPU#0!
> <c0103416> show_trace+0xd/0xf
> <c01034e5> dump_stack+0x15/0x17
> <c01382b0> softlockup_tick+0x9d/0xae
> <c012190a> run_local_timers+0x12/0x14
> <c0121748> update_process_times+0x3c/0x61
> <c010e1d9> smp_apic_timer_interrupt+0x57/0x5f
> <c010307c> apic_timer_interrupt+0x1c/0x24
> <f8aa8783> ipmi_thread+0x43/0x71 [ipmi_si]
> <c0129e62> kthread+0x78/0xa0
> <c0100e31> kernel_thread_helper+0x5/0xb
> 
> Any idea on what went wrong?

What kernel please?  If 2.6.17 or higher, this is new.  If < 2.6.17,
this is most likely due to the udelay(1) call in ipmi_thread() which
in 2.6.17 was replaced with a schedule().

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

  reply	other threads:[~2006-08-14 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 16:14 Soft lockup (and reboot): IPMI Philipp Matthias Hahn
2006-08-14 21:02 ` Matt Domsch [this message]
2006-08-15  6:50   ` Philipp Matthias Hahn
2006-08-17 14:15     ` [Openipmi-developer] " Corey Minyard

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=20060814210231.GB3637@lists.us.dell.com \
    --to=matt_domsch@dell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=pmhahn@svs.Informatik.Uni-Oldenburg.de \
    /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