public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tino Keitel <tino.keitel@gmx.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 2.6.25-rc6 hangs at resume after suspend to RAM on Mac mini Core Duo
Date: Thu, 20 Mar 2008 11:54:32 +0100	[thread overview]
Message-ID: <20080320105432.GA13404@dose.home.local> (raw)
In-Reply-To: <20080320032501.f387b3ef.akpm@linux-foundation.org>

On Thu, Mar 20, 2008 at 03:25:01 -0700, Andrew Morton wrote:
> On Thu, 20 Mar 2008 07:05:50 +0100 Tino Keitel <tino.keitel@gmx.de> wrote:
> 
> > Hi folks,
> > 
> > whereas I had working suspend with 2.6.25-rc5, I had a hang at resume
> > with git HEAD from March 19th (something after 2.6.25-rc6). I tried it
> > again and got another hang, so it seems to be reproducible.
> 
> Was 2.6.24 OK?

Yes, mostly ok (some seldom failures).

> 
> > Any hints what commit might have broke suspend? I won't have the time
> > to start a git bisect or any resume debugging using CONFIG_PM_TRACE_RTC
> > until next Tuesday.
> > 
> > This is a Mac mini Core Duo.
> 
> I assume Linus doesn't use his any more ;)

That's too bad.

> > Here is the lspci -nn output:
> 
> Please try Linus's current tree - quite a few things got reverted today
> which might have fixed this.

OK, I'll try it.

Regards,
Tino

  reply	other threads:[~2008-03-20 10:54 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 [this message]
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
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=20080320105432.GA13404@dose.home.local \
    --to=tino.keitel@gmx.de \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox