All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benjamin S." <sbenni@gmx.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, js@sig21.net
Subject: Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
Date: Sun, 14 Jun 2009 12:57:04 +0200	[thread overview]
Message-ID: <20090614125704.2240023d@pluto-lenny.milky.way> (raw)
In-Reply-To: <200906141235.24942.rjw@sisk.pl>


On Sun, 14 Jun 2009 12:35:24 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> Thanks for the report, the problem seems to be related to the chipset, because
> I'm unable to reproduce it with SB600 and a fairly new AMD CPU.
> 
> Does the resume work if you comment out suspend_device_irqs() and
> resume_device_irqs() in drivers/base/power/main.c ?

Yes, 2.6.30 without the two lines resumes without problems.


Benjamin

  reply	other threads:[~2009-06-14 10:55 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 10:09 2.6.30 enabling cpu1 on resume fails after suspend to memory Benjamin S.
2009-06-14 10:35 ` Rafael J. Wysocki
2009-06-14 10:57   ` Benjamin S. [this message]
2009-06-14 11:19     ` Rafael J. Wysocki
2009-06-14 11:48       ` Benjamin S.
2009-06-14 12:00         ` Rafael J. Wysocki
2009-06-14 12:09           ` Thomas Gleixner
2009-06-14 12:09           ` Thomas Gleixner
2009-06-14 12:15             ` Rafael J. Wysocki
2009-06-14 12:15             ` Rafael J. Wysocki
2009-06-14 12:37               ` Benjamin S.
2009-06-14 12:37               ` Benjamin S.
2009-06-14 12:43                 ` Thomas Gleixner
2009-06-14 12:43                 ` Thomas Gleixner
2009-06-14 12:59                   ` Benjamin S.
2009-06-14 13:05                     ` Thomas Gleixner
2009-06-14 13:05                     ` Thomas Gleixner
2009-06-14 13:35                       ` Benjamin S.
2009-06-14 13:35                       ` Benjamin S.
2009-06-14 12:59                   ` Benjamin S.
2009-06-14 12:46                 ` Thomas Gleixner
2009-06-14 12:46                 ` Thomas Gleixner
2009-06-14 13:12                   ` Pallipadi, Venkatesh
2009-06-14 13:17                     ` Thomas Gleixner
2009-06-14 13:26                       ` Pallipadi, Venkatesh
2009-06-14 13:49                         ` Thomas Gleixner
2009-06-14 13:49                         ` Thomas Gleixner
2009-06-14 14:45                           ` Thomas Gleixner
2009-06-14 15:03                             ` Benjamin S.
2009-06-14 15:03                             ` Benjamin S.
2009-06-14 15:41                               ` Thomas Gleixner
2009-06-14 15:41                               ` Thomas Gleixner
2009-06-14 16:12                                 ` Greg KH
2009-06-14 16:12                                 ` Greg KH
2009-06-14 16:19                                   ` Thomas Gleixner
2009-06-14 16:19                                   ` Thomas Gleixner
2009-06-15 13:12                               ` Johannes Stezenbach
2009-06-15 13:12                               ` Johannes Stezenbach
2009-06-14 14:45                           ` Thomas Gleixner
2009-06-14 13:17                     ` Thomas Gleixner
2009-06-14 12:00         ` 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=20090614125704.2240023d@pluto-lenny.milky.way \
    --to=sbenni@gmx.de \
    --cc=js@sig21.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.