From: Andrew Morton <akpm@linux-foundation.org>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: linux-acpi@vger.kernel.org, mingo@redhat.com,
len.brown@intel.com, bunk@stusta.de,
linux-kernel@vger.kernel.org, linux-pm@linux-foundation.org
Subject: Re: 2.6.21-rc1: T60 resume from suspend to RAM issues
Date: Fri, 23 Feb 2007 02:09:04 -0800 [thread overview]
Message-ID: <20070223020904.c8fc8a3e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070222233803.GA4447@mellanox.co.il>
> On Fri, 23 Feb 2007 01:38:03 +0200 "Michael S. Tsirkin" <mst@mellanox.co.il> wrote:
> I tested this:
> commit 9654640d0af8f2de40ff3807d3695109d3463f54
> and see 2 issues:
>
> 1. After suspend to RAM, system wakes up but no screen.
> I can log in through ssh though.
> dmesg output at this point below.
> Works fine on 2.6.20 and below, with same .config
> .config and log file for this issue attached.
>
> 2. As a separate test, I enabled DynTicks in .config.
> Seems to work fine but won't come out of suspend to memory at all:
> pressing Fn/F4 seems to have no effect.
>
Do you believe that the second problem was caused by dynticks?
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: linux-kernel@vger.kernel.org, bunk@stusta.de, pavel@suse.cz,
linux-pm@linux-foundation.org, linux-acpi@vger.kernel.org,
len.brown@intel.com, mingo@redhat.com
Subject: Re: 2.6.21-rc1: T60 resume from suspend to RAM issues
Date: Fri, 23 Feb 2007 02:09:04 -0800 [thread overview]
Message-ID: <20070223020904.c8fc8a3e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070222233803.GA4447@mellanox.co.il>
> On Fri, 23 Feb 2007 01:38:03 +0200 "Michael S. Tsirkin" <mst@mellanox.co.il> wrote:
> I tested this:
> commit 9654640d0af8f2de40ff3807d3695109d3463f54
> and see 2 issues:
>
> 1. After suspend to RAM, system wakes up but no screen.
> I can log in through ssh though.
> dmesg output at this point below.
> Works fine on 2.6.20 and below, with same .config
> .config and log file for this issue attached.
>
> 2. As a separate test, I enabled DynTicks in .config.
> Seems to work fine but won't come out of suspend to memory at all:
> pressing Fn/F4 seems to have no effect.
>
Do you believe that the second problem was caused by dynticks?
next prev parent reply other threads:[~2007-02-23 10:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 23:38 2.6.21-rc1: T60 resume from suspend to RAM issues Michael S. Tsirkin
2007-02-22 23:38 ` Michael S. Tsirkin
2007-02-23 10:09 ` Andrew Morton [this message]
2007-02-23 10:09 ` Andrew Morton
2007-02-24 21:11 ` Michael S. Tsirkin
2007-02-24 21:11 ` Michael S. Tsirkin
2007-02-27 10:14 ` Ingo Molnar
2007-02-27 10:14 ` Ingo Molnar
2007-02-27 10:28 ` Michael S. Tsirkin
2007-02-27 10:28 ` Michael S. Tsirkin
2007-02-27 11:03 ` Ingo Molnar
2007-02-27 11:33 ` Michael S. Tsirkin
2007-02-27 11:33 ` Michael S. Tsirkin
2007-02-27 11:03 ` Ingo Molnar
2007-02-27 10:38 ` Pavel Machek
2007-02-27 10:38 ` Pavel Machek
2007-02-25 9:03 ` Thomas Gleixner
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=20070223020904.c8fc8a3e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@linux-foundation.org \
--cc=mingo@redhat.com \
--cc=mst@mellanox.co.il \
/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.