All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rudorff <chris@rudorff.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: nouveau@lists.freedesktop.org, stable@vger.kernel.org,
	bskeggs@redhat.com, emil.l.velikov@gmail.com
Subject: Re: [PATCH] drm/nouveau/fbcon: fix suspend/resume fbcon
Date: Tue, 19 Nov 2013 20:23:47 +0100	[thread overview]
Message-ID: <528BBAC3.9060908@rudorff.com> (raw)
In-Reply-To: <20131119184847.GB11774@kroah.com>

On 19.11.2013 19:48, Greg KH wrote:
> On Tue, Nov 19, 2013 at 05:59:13PM +0100, Christoph Rudorff wrote:
>> Current code disables fbcon acceleration before fbcon is suspended,
>> leading to corrupted console after resume from s2disk. In a similar
>> fashion we must make sure that fbcon acceleration is enabled before we
>> revive the console.
>>
>> With this patch s2disk works correctly on my MacBookPro6,2 with GT216
>> [GeForce GT 330M]
>>
>> hibernate:
>> kernel: nouveau  [     DRM] suspending fbcon...
>> kernel: nouveau  [     DRM] suspending display...
>> kernel: nouveau  [     DRM] unpinning framebuffer(s)...
>> kernel: nouveau  [     DRM] evicting buffers...
>> kernel: nouveau  [     DRM] waiting for kernel channels to go idle...
>> kernel: nouveau  [     DRM] suspending client object trees...
>> kernel: nouveau  [     DRM] suspending kernel object tree...
>> resume:
>> kernel: nouveau  [     DRM] re-enabling device...
>> kernel: nouveau  [     DRM] resuming kernel object tree...
>> kernel: nouveau  [   VBIOS][0000:01:00.0] running init tables
>> kernel: nouveau  [     DRM] resuming client object trees...
>> kernel: nouveau  [     DRM] resuming display...
>> kernel: nouveau E[     PFB][0000:01:00.0] trapped write at 0x00007fe000 on channel 0x0000fee0 [unknown] BAR/PFIFO_WRITE/FB reason: PAGE_NOT_PRESENT
>> kernel: nouveau E[     PFB][0000:01:00.0] trapped write at 0x00007fe000 on channel 0x0000fee0 [unknown] BAR/PFIFO_WRITE/FB reason: PAGE_NOT_PRESENT
>> kernel: nouveau E[     PFB][0000:01:00.0] trapped write at 0x00007fe240 on channel 0x0000fee0 [unknown] BAR/PFIFO_WRITE/FB reason: PAGE_NOT_PRESENT
>> kernel: nouveau E[     PFB][0000:01:00.0] trapped write at 0x00007fe400 on channel 0x0000fee0 [unknown] BAR/PFIFO_WRITE/FB reason: PAGE_NOT_PRESENT
>>
>> http://lists.freedesktop.org/archives/nouveau/2013-October/014656.html
>> ---
>>  drivers/gpu/drm/nouveau/nouveau_fbcon.c |    8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> <formletter>
> 
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
> 
> </formletter>

Sorry,

I've been asked to cc it.

chris

  reply	other threads:[~2013-11-19 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19 16:59 [PATCH] drm/nouveau/fbcon: fix suspend/resume fbcon Christoph Rudorff
2013-11-19 18:48 ` Greg KH
2013-11-19 19:23   ` Christoph Rudorff [this message]
     [not found]     ` <528BBAC3.9060908-4cZEHNAa5IdBDgjK7y7TUQ@public.gmane.org>
2013-12-01 20:58       ` Emil Velikov

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=528BBAC3.9060908@rudorff.com \
    --to=chris@rudorff.com \
    --cc=bskeggs@redhat.com \
    --cc=emil.l.velikov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=stable@vger.kernel.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.