public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Harald Dunkel <harald.dunkel@t-online.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.23.8, ondemand scaling governor: "BUG: soft lockup detected on CPU#0!"
Date: Tue, 20 Nov 2007 09:17:14 +0100	[thread overview]
Message-ID: <4742980A.60407@t-online.de> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEE251A40@orsmsx423.amr.corp.intel.com>

Pallipadi, Venkatesh wrote:
> 
> Can you try switching to powersave governor (which should always run CPU
> at 400MHz) and see whether you see similar error?
> 

Yes, if I move from performance to powersave, then I see a similar
error:

Nov 20 09:06:48 bugs kernel: BUG: soft lockup detected on CPU#0!
Nov 20 09:06:48 bugs kernel:  [<c013cf8d>] softlockup_tick+0x91/0xa6
Nov 20 09:06:48 bugs kernel:  [<c012269c>] update_process_times+0x3a/0x5d
Nov 20 09:06:48 bugs kernel:  [<c0131219>] tick_sched_timer+0x115/0x164
Nov 20 09:06:48 bugs kernel:  [<c012d311>] hrtimer_interrupt+0x102/0x191
Nov 20 09:06:48 bugs kernel:  [<c0106cd6>] timer_interrupt+0x2e/0x34
Nov 20 09:06:48 bugs kernel:  [<c013d1f6>] handle_IRQ_event+0x1a/0x3f
Nov 20 09:06:48 bugs kernel:  [<c013e4e1>] handle_level_irq+0xa8/0xb7
Nov 20 09:06:48 bugs kernel:  [<c0106367>] do_IRQ+0x53/0x6c
Nov 20 09:06:48 bugs kernel:  [<c0104853>] common_interrupt+0x23/0x28
Nov 20 09:06:48 bugs kernel:  =======================


Please mail. Regards

Harri


  reply	other threads:[~2007-11-20  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  0:19 2.6.23.8, ondemand scaling governor: "BUG: soft lockup detected on CPU#0!" Harald Dunkel
2007-11-20  1:01 ` Pallipadi, Venkatesh
2007-11-20  8:17   ` Harald Dunkel [this message]
2007-11-20 14:29     ` Pallipadi, Venkatesh
2007-11-20 21:39       ` Harald Dunkel

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=4742980A.60407@t-online.de \
    --to=harald.dunkel@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox