All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@gmx.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: 2.6.25-rc6 hangs at resume after suspend to RAM on Mac mini Core Duo
Date: Tue, 1 Apr 2008 10:04:38 +0200	[thread overview]
Message-ID: <20080401080438.GA9906@dose.home.local> (raw)
In-Reply-To: <200804010017.54799.rjw@sisk.pl>

On Tue, Apr 01, 2008 at 00:17:53 +0200, Rafael J. Wysocki wrote:
> On Tuesday, 1 of April 2008, Tino Keitel wrote:
> > On Mon, Mar 31, 2008 at 23:50:27 +0200, Pavel Machek wrote:
> > > On Mon 2008-03-31 23:28:12, 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.
> > > 
> > > You should put "acpi_new_pts_ordering" on kernel command line.
> > 
> > I did, just forgot to mention it.
> 
> OK, thanks.
> 
> Have you tried to do:
> 
> # echo core > /sys/power/pm_test
> # echo mem > /sys/power/state
> 
> (it's good to boot the kernel with no_console_suspend and do
> "echo 8 > /proc/sys/kernel/printk" before that to see the messages)?

Thanks, I'll try this evening. What should I look for in the kernel
messages?

Regards,
Tino

  reply	other threads:[~2008-04-01  8:04 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 [this message]
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
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=20080401080438.GA9906@dose.home.local \
    --to=tino.keitel@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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 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.