From: "Michael S. Tsirkin" <mst@mellanox.co.il>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-acpi@vger.kernel.org, mingo@redhat.com,
len.brown@intel.com, Andrew Morton <akpm@linux-foundation.org>,
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: Tue, 27 Feb 2007 12:28:09 +0200 [thread overview]
Message-ID: <20070227102809.GD10548@mellanox.co.il> (raw)
In-Reply-To: <20070227101451.GA11981@elte.hu>
> Quoting Ingo Molnar <mingo@elte.hu>:
> Subject: Re: 2.6.21-rc1: T60 resume from suspend to RAM issues
>
>
> * Michael S. Tsirkin <mst@mellanox.co.il> wrote:
>
> > > > 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?
> >
> > Assuming these are 2 different problems, yes, the second one seems to
> > be caused by dyntics.
>
> on my T60 current -git does not resume even without dynticks. v2.6.20
> with the same .config resumes fine (except for the display).
>
> after pressing Fn/F4 the disk light flashes briefly, which suggests that
> action is probably back to the Linux kernel at that point, and that we
> hung somewhere there. Will try a bisection thing.
That's exactly the behaviour I have with DynTicks: the disk light flashes
briefly.
--
MST
next prev parent reply other threads:[~2007-02-27 10:28 UTC|newest]
Thread overview: 9+ 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-23 10:09 ` Andrew Morton
2007-02-24 21:11 ` Michael S. Tsirkin
2007-02-27 10:14 ` Ingo Molnar
2007-02-27 10:28 ` Michael S. Tsirkin [this message]
2007-02-27 11:03 ` Ingo Molnar
[not found] ` <20070227110306.GE20927@elte.hu>
2007-02-27 11:33 ` Michael S. Tsirkin
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=20070227102809.GD10548@mellanox.co.il \
--to=mst@mellanox.co.il \
--cc=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@elte.hu \
--cc=mingo@redhat.com \
/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