All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Marc Koschewski <marc@osknowledge.org>,
	Jeff Chua <jeff.chua.linux@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_
Date: Sun, 6 Feb 2011 21:06:18 +1000	[thread overview]
Message-ID: <AANLkTimURab9M5-LQxU0wjo=gEVBjHyv6osudadq4nNO@mail.gmail.com> (raw)
In-Reply-To: <s5hei7lwhmg.wl%tiwai@suse.de>

>>
>> I reverted the specified commit and my box still suffers the
>> resume-turns-into-cold-boot behavior. Retried two times with the commit reverted
>> on top of HEAD...
>
> The cold-boot problem is very likely irrelevant with i915 patches.
> I've got the same issue with and without the i915 fix patches on test
> machines here.
>
Yeah its the 32-bit NX stuff most likely if you are using 32-bit kernels.

Dave.

  reply	other threads:[~2011-02-06 11:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06  1:50 Commit 500f7147cf5bafd139056d521536b10c2bc2e154 breaks _resume_ Jeff Chua
2011-02-06  8:19 ` Marc Koschewski
2011-02-06 11:02   ` Takashi Iwai
2011-02-06 11:06     ` Dave Airlie [this message]
2011-02-06 12:21       ` Marc Koschewski
2011-02-06 13:04         ` Rafael J. Wysocki
2011-02-06 13:44           ` Marc Koschewski
2011-02-06 13:55             ` Rafael J. Wysocki
2011-02-06 11:00 ` Takashi Iwai
2011-02-06 12:24   ` Marc Koschewski
2011-02-06 13:19     ` Takashi Iwai
2011-02-06 14:01   ` Jeff Chua
2011-02-06 14:47     ` Chris Wilson
2011-02-06 14:51       ` Jeff Chua
2011-02-06 14:49     ` Jeff Chua
2011-02-06 15:27       ` Chris Wilson
2011-02-07  4:48         ` Jeff Chua
2011-02-07  5:02           ` Jeff Chua
2011-02-07  8:25             ` Takashi Iwai
2011-02-07  8:36               ` Jeff Chua
2011-02-07  8:45                 ` Jeff Chua
2011-02-07  8:54                   ` Takashi Iwai
2011-02-07  8:52                 ` Takashi Iwai
2011-02-07 10:15                   ` Takashi Iwai
2011-02-07 13:38                     ` Jeff Chua
2011-02-07 14:11                       ` Jeff Chua
2011-02-07 21:20                         ` Rafael J. Wysocki
2011-02-08  1:40                           ` Jeff Chua
2011-02-08 13:36                         ` Chris Wilson
2011-02-09  0:55                           ` Jeff Chua
2011-02-09  1:05                             ` Jeff Chua
2011-02-09  2:56                               ` Indan Zupancic
2011-02-09  5:45                                 ` Jeff Chua
2011-02-09  9:42                                   ` Indan Zupancic
2011-02-09  9:32                                 ` Chris Wilson
2011-02-09 10:20                                   ` Indan Zupancic
2011-02-07 10:02               ` Marc Koschewski
2011-02-07 10:06                 ` Takashi Iwai
2011-02-07 10:09                   ` Marc Koschewski

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='AANLkTimURab9M5-LQxU0wjo=gEVBjHyv6osudadq4nNO@mail.gmail.com' \
    --to=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=jeff.chua.linux@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@osknowledge.org \
    --cc=rjw@sisk.pl \
    --cc=tiwai@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.