public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Tino Keitel <tino.keitel@gmx.de>
Cc: "Rafael J\. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: Re: 2.6.25-rc6 hangs at resume after suspend to RAM on Mac mini Core Duo
Date: Tue, 01 Apr 2008 06:38:18 +0000	[thread overview]
Message-ID: <1207031898.11035.38.camel@localhost> (raw)
In-Reply-To: <20080401062734.GA8824@dose.home.local>

On Tue, 2008-04-01 at 08:27 +0200, Tino Keitel wrote:
> On Tue, Apr 01, 2008 at 06:23:11 +0000, Soeren Sonnenburg wrote:
> > On Mon, 2008-03-31 at 23:28 +0200, Tino Keitel wrote:
> > > On Sat, Mar 29, 2008 at 00:03:15 +0100, Rafael J. Wysocki wrote:
> > > 
> > > [...]
> > > 
> > > > Can you please try to boot with acpi_new_pts_ordering and retest?
> > > 
> > > I just tried current -git (a9edadbf790d72adf6ebed476cb5caf7743e7e4a),
> > > without success. I still got the same hand at resume.
> > 
> > I am having the hang on resume problem too (macbook pro), cf.
> > http://bugzilla.kernel.org/show_bug.cgi?id=10319, 2.6.24 was fine.
> 
> What about 2.6.25-rc5? Up to this, resume works for me. -rc6 is broken.

No never worked in 2.6.25 (at least from rc2 on) and still does not in
rc7-current-git. But note that on console I could suspend to ram and
resume but the display is not anymore coming back with s2ram - from
within X it freezes though.

Soeren


  reply	other threads:[~2008-04-01  6:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  6:05 2.6.25-rc6 hangs at resume after suspend to RAM on Mac mini Core Duo Tino Keitel
2008-03-20 10:10 ` Rafael J. Wysocki
2008-03-20 10:25 ` Andrew Morton
2008-03-20 10:54   ` Tino Keitel
2008-03-25 23:13     ` Tino Keitel
2008-03-28 23:03       ` Rafael J. Wysocki
2008-03-31 21:28         ` Tino Keitel
2008-03-31 21:50           ` Pavel Machek
2008-03-31 22:01             ` Tino Keitel
2008-03-31 22:17               ` Rafael J. Wysocki
2008-04-01  8:04                 ` Tino Keitel
2008-04-01 21:03                   ` Rafael J. Wysocki
2008-04-01  6:23           ` Soeren Sonnenburg
2008-04-01  6:27             ` Tino Keitel
2008-04-01  6:38               ` Soeren Sonnenburg [this message]
2008-04-01 21:05                 ` Rafael J. Wysocki
2008-04-02 17:33                   ` Soeren Sonnenburg
2008-04-02 17:56                     ` Rafael J. Wysocki
2008-04-02 18:42                       ` Soeren Sonnenburg
2008-04-01 10:52               ` Pavel Machek
2008-04-01 12:55                 ` Tino Keitel
2008-04-01 18:37                 ` Tino Keitel
2008-04-01 19:06                   ` Alan Stern
2008-04-01 20:25                     ` Tino Keitel
2008-04-01 21:02                       ` Alan Stern
2008-04-01 21:06                         ` Tino Keitel
2008-04-02 14:25                           ` Alan Stern
2008-04-02 19:26                           ` Alan Stern
2008-04-02 19:47                             ` Tino Keitel
2008-04-02 20:37                               ` Soeren Sonnenburg
2008-04-01 20:06                   ` David Brownell

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=1207031898.11035.38.camel@localhost \
    --to=kernel@nn7.de \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=tino.keitel@gmx.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