From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: LKML <linux-kernel@vger.kernel.org>
Cc: bugzilla-daemon@bugzilla.kernel.org, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [Bug 15559] Bad performance after suspend on Intel i7 and i5
Date: Thu, 18 Mar 2010 20:56:40 +0100 [thread overview]
Message-ID: <201003182056.40655.rjw@sisk.pl> (raw)
In-Reply-To: <201003181842.o2IIgUSL031098@demeter.kernel.org>
Hi,
Here's an interesting issue, apparently Core i5 and i7 have problems after
resume from suspend/standby.
I wonder whom at Intel I should let know about that.
Rafael
On Thursday 18 March 2010, bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=15559
>
>
>
>
>
> --- Comment #3 from Thomas Bächler <thomas@archlinux.org> 2010-03-18 18:42:26 ---
> I have only tested 2.6.33 and 2.6.33.1, as this machine is quite new. Besides
> other unrelated suspend problems, I can always reproduce this one on a Core
> i5-520M, the symptoms are exactly the ones that Florian describes.
>
> The diversity of hardware and different kernels here suggests that this is a
> general problem with the i5 and i7 CPUs on Linux. Also interesting is that
> Florian is using an i7 of the 2009 generation, while I use the 2010 i5 CPU and
> the bug is the same on both.
>
> On the same kernel(s), my old Core 2 Duo CPU has no trouble after resume, all
> cores are still being used as usual.
>
> If you need any more info, I think we will be able to provide anything you
> need. Maybe it might also be useful to bring someone from Intel in on this.
parent reply other threads:[~2010-03-18 19:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201003181842.o2IIgUSL031098@demeter.kernel.org>]
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=201003182056.40655.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®