public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Bombe <aeb@debian.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] perf merge breaks resume from standby, bisected
Date: Fri, 11 Nov 2011 01:47:52 +0100	[thread overview]
Message-ID: <20111111004752.GA4412@amos.fritz.box> (raw)
In-Reply-To: <20111110145319.GB29614@elte.hu>

On Thu, Nov 10, 2011 at 03:53:20PM +0100, Ingo Molnar wrote:
> 
> * Andreas Bombe <aeb@debian.org> wrote:
> 
> > I found that resuming from suspend to memory stopped working with the
> > recent merges to mainline after 3.1. I have observed different modes of
> > failure even with the same version. Most often I just get the blinking
> > caps/scroll lock LEDs on the keyboard and no video output.
> > 
> > Sometimes I get the normal text output from a resume ending with an oops
> > dump. It has been mostly NULL pointer dereferences, but I think there
> > was a scheduling in atomic context at one time. I have a photo of the
> > NULL deref on the latest kernel attached, according to gdb the IP points
> > to the return statement of the event_sched_out() function.
> > 
> > Anyway, I bisected the problem down to 144060f "perf: Add PM notifiers
> > to fix CPU hotplug races". The hardware is a Core 2 Duo E8500 on an Asus
> > P5Q, config attached.
> 
> v3.2-rc1 should have this resolved, the commit got reverted.

Thanks, but I already knew since I saw that thread. FWIW, the revert did
fix the problem.

-- 
Andreas Bombe

      reply	other threads:[~2011-11-11  0:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 17:38 [REGRESSION] perf merge breaks resume from standby, bisected Andreas Bombe
2011-11-10 14:53 ` Ingo Molnar
2011-11-11  0:47   ` Andreas Bombe [this message]

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=20111111004752.GA4412@amos.fritz.box \
    --to=aeb@debian.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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