From: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: cpufreq@lists.linux.org.uk,
Linux Kernel <linux-kernel@vger.kernel.org>,
venkatesh.pallipadi@intel.com
Subject: Re: Suspend to RAM regression tracked down
Date: Mon, 03 Jul 2006 16:31:47 +1000 [thread overview]
Message-ID: <1151908307.8325.3.camel@localhost> (raw)
In-Reply-To: <44A8B2FC.6080806@goop.org>
On Sun, 2006-07-02 at 23:02 -0700, Jeremy Fitzhardinge wrote:
> Jean-Marc Valin wrote:
> > Any link to the patch and the thread about the problem (if any)? Also,
> > was the race introduced in 2.6.12-rc5-git6? If not, it's a completely
> > different problem because my machine worked fine with 2.6.12-rc5-git5.
> >
>
> It's in the thread on the cpufreq list titled "ondemand vs suspend";
> Venkatesh Pallipadi posted the patch.
Just read the thread and it's not clear to me whether it's the same
problem. Venkatesh, does the thread describe the same as this bug:
http://bugzilla.kernel.org/show_bug.cgi?id=6166
which appeared in 2.6.12-rc5-git6 or is it a separate problem?
Jean-Marc
next prev parent reply other threads:[~2006-07-03 6:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 10:47 Suspend to RAM regression tracked down Jean-Marc Valin
2006-07-02 18:06 ` Jeremy Fitzhardinge
2006-07-02 22:52 ` Jean-Marc Valin
2006-07-03 6:02 ` Jeremy Fitzhardinge
2006-07-03 6:31 ` Jean-Marc Valin [this message]
2006-07-03 6:08 ` Jeff Chua
2006-07-07 11:25 ` Jean-Marc Valin
2006-07-07 16:21 ` Dave Jones
2006-07-07 22:48 ` Jean-Marc Valin
2006-07-08 6:23 ` Dave Jones
2006-07-08 22:55 ` Jean-Marc Valin
2006-07-09 3:21 ` Dave Jones
2006-07-09 5:28 ` Jean-Marc Valin
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=1151908307.8325.3.camel@localhost \
--to=jean-marc.valin@usherbrooke.ca \
--cc=cpufreq@lists.linux.org.uk \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.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