mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Pavel Machek <pavel@suse.cz>
Subject: Re: soft lockup detected in acpi_processor_idle() -- false positive?
Date: Fri, 13 Jan 2006 08:55:24 +0800	[thread overview]
Message-ID: <1137113724.5750.113.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <200601122054.14128.rjw@sisk.pl>

On Thu, 2006-01-12 at 20:54 +0100, Rafael J. Wysocki wrote:
> On Thursday, 12 January 2006 19:43, Dominik Brodowski wrote:
> > Latest git, fresh after resuming from suspend-to-disk (in-kernel variant):
> > 
> > [4294914.586000] Restarting tasks... done
> > [4294922.657000] BUG: soft lockup detected on CPU#0!
> > [4294922.657000] 
> > [4294922.657000] Pid: 0, comm:              swapper
> > [4294922.657000] EIP: 0060:[<f003084c>] CPU: 0
> > [4294922.657000] EIP is at acpi_processor_idle+0x1f3/0x2d5 [processor]
> > [4294922.657000]  EFLAGS: 00000282    Not tainted  (2.6.15)
> > [4294922.657000] EAX: fffff000 EBX: 005543a8 ECX: 00000000 EDX: 00000000
> > [4294922.657000] ESI: edcc3064 EDI: edcc2f60 EBP: c041cfdc DS: 007b ES: 007b
> > [4294922.657000] CR0: 8005003b CR2: 080c3000 CR3: 2d530000 CR4: 000006d0
> > 
> > 
> > As acpi_processor_idle doesn't take any locks AFAIK, it seems to me to be a
> > false positive -- or do I miss something obvious?
> 
> I think it's a false-positive.
> 
> This "soft lockup" message has been appearing for me for quite some time now
> (actually since the softlockup patch made it into -mm ;-)), in a
> non-reproducible manner, but I haven't been able to nail it down.
> 
> Still, I thought it was x86-64-specific, but your machine is an i386,
> so there's more to it, apparently.  Probably there's missing
> touch_softlockup_watchdog() somewhere, or the timer .suspend()/.resume()
> routines need some additional review.
I got some similar reports for S3:
http://bugzilla.kernel.org/show_bug.cgi?id=5825
I guess x86-64 lacks .suspend/.resume for timer. Last time I looked at
such issue in ia32, and I fixed it, but I didn't fix x86-64.

Thanks,
Shaohua


  reply	other threads:[~2006-01-13  0:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-12 18:43 Dominik Brodowski
2006-01-12 19:54 ` Rafael J. Wysocki
2006-01-13  0:55   ` Shaohua Li [this message]
2006-01-13 11:17     ` Rafael J. Wysocki

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=1137113724.5750.113.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /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®