From: Roberto Oppedisano <roberto.oppedisano@gmail.com>
To: Paul Rolland <rol@as2917.net>
Cc: Thomas Meyer <thomas@m3y3r.de>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zou Nan hai <nanhai.zou@intel.com>,
"Xiang Hai hao" <haihao.xiang@intel.com>,
Eric Anholt <eric@anholt.net>, David Airlie <airlied@linux.ie>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: 2.6.35-rc6+: i915: Bisected regression
Date: Sun, 1 Aug 2010 17:17:54 +0200 [thread overview]
Message-ID: <4C559022.1010406@gmail.com> (raw)
In-Reply-To: <20100801151409.252be86b@tux.DEF.witbe.net>
On 01/08/2010 15:14, Paul Rolland wrote:
> My machine has :
> 00:02.0 0300: 8086:2a42 (rev 07)
> 00:02.1 0380: 8086:2a43 (rev 07)
>
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
>
> (Dell Vostro 1520, BIOS Revision A04)
>
>>> Is it suspend
>>> or resume that is unreliable?
>> suspend never finishes/hangs.
> and is randomly suffering from exactly the same problems...
>
> So, I've applied your hint (in i915_drv.h), rebuilt a kernel, booted, and
> I've now successfully managed to go thru several suspend/resume cycles
> without having the machine hanging while suspend !
I have to add a me too (HP 6730B, same PCI ids).
I was suffering from the same problem which seem completely gone with
the suggested hint.
R
next prev parent reply other threads:[~2010-08-01 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 9:01 2.6.35-rc6+: i915: Bisected regression Thomas Meyer
2010-08-01 11:42 ` Stefan Richter
2010-08-01 10:51 ` Thomas Meyer
2010-08-01 13:14 ` Paul Rolland
2010-08-01 15:17 ` Roberto Oppedisano [this message]
2010-08-24 17:36 ` Thomas Meyer
2010-08-25 3:02 ` Roberto Oppedisano
2010-08-25 13:41 ` Paul Rolland
2010-08-05 5:43 ` Shuang He
2010-08-06 3:26 ` David John
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=4C559022.1010406@gmail.com \
--to=roberto.oppedisano@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=haihao.xiang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--cc=rol@as2917.net \
--cc=stefanr@s5r6.in-berlin.de \
--cc=thomas@m3y3r.de \
/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