From: "Jeff Chua" <jeff.chua.linux@gmail.com>
To: "Pavel Machek" <pavel@suse.cz>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"Jesse Barnes" <jbarnes@virtuousgeek.org>,
"Arjan van de Ven" <arjan@infradead.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
len.brown@intel.com, "Shaohua Li" <shaohua.li@intel.com>,
"Greg KH" <greg@kroah.com>, "Len Brown" <lenb@kernel.org>
Subject: Re: recent 2.6.26 kernel hangs at suspend
Date: Wed, 21 May 2008 00:11:10 +0800 [thread overview]
Message-ID: <b6a2187b0805200911x4cccd060v5644c87b51d7db9b@mail.gmail.com> (raw)
In-Reply-To: <20080520074819.GA15659@elf.ucw.cz>
On Tue, May 20, 2008 at 3:48 PM, Pavel Machek <pavel@suse.cz> wrote:
>> If I don't enter X, it'll not hang on suspend to ram.
>
> Ok, so we have X in the mix.
>
> Can you try if it happens if you disable Intel framebuffer driver?
The whole problem went away after the latest git pull.
Looks like the commit below fixes the problem of failing on 2nd suspense.
I've tested whole day and it's suspending-resuming after many cycles.
Sorry, couldn't get to email whole day. Traveling. Slow train.
Thank you all for your help!!!
Jeff.
commit 860da5e578c25d1ab4528c0d1ad13f9969e3490f
Merge: 1bf9947... e948e99...
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon May 19 13:30:40 2008 -0700
Merge branch 'drm-patches' of git://git.kernel.org/pub/scm/linux/kernel/git/
airlied/drm-2.6
* 'drm-patches' of git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm
-2.6:
drm/i915: save and restore dsparb and d_state registers.
drm/i915: fix off by one in VGA save/restore of AR & CR regs.
drm: disable tasklets not IRQs when taking the drm lock spinlock
Revert "drm/vbl rework: rework how the drm deals with vblank."
prev parent reply other threads:[~2008-05-20 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 15:07 Jeff Chua
2008-05-19 15:26 ` Linus Torvalds
2008-05-19 22:25 ` Jeff Chua
2008-05-19 18:38 ` Len Brown
2008-05-19 22:25 ` Jeff Chua
2008-05-19 22:30 ` Len Brown
2008-05-20 7:48 ` Pavel Machek
2008-05-20 16:11 ` Jeff Chua [this message]
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=b6a2187b0805200911x4cccd060v5644c87b51d7db9b@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=shaohua.li@intel.com \
--cc=torvalds@linux-foundation.org \
/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®