dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Pontus Fuchs <pontus.fuchs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Resume regression with nouveau 3.8rc1 (bisected)
Date: Thu, 3 Jan 2013 13:58:10 +0100	[thread overview]
Message-ID: <20130103125810.GA3198@joi.lan> (raw)
In-Reply-To: <50E45007.5080706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On Wed, Jan 02, 2013 at 04:19:35PM +0100, Pontus Fuchs wrote:
> Hi,
> 
> Starting with 3.8rc1 I get a black screen when resuming after suspend. 
> The kernel is alive because I can switch to VT1 and reboot with 
> ctrl-alt-delete.
> 
> I bisected the problem down to this commit:
> 
> 186ecad21: drm/nv50/disp: move remaining interrupt handling into core
> 
> Hardware is 8400M GS (10de:0427) in a Dell XPS M1330.

There's already open bug report for that:
https://bugs.freedesktop.org/show_bug.cgi?id=58729

And my nv92 does not resume too, with similar symptoms, since nouveau display
rework hit the tree.

Marcin

  parent reply	other threads:[~2013-01-03 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 15:19 Resume regression with nouveau 3.8rc1 (bisected) Pontus Fuchs
     [not found] ` <50E45007.5080706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-03 12:58   ` Marcin Slusarz [this message]
2013-01-03 19:12     ` Marcin Slusarz
     [not found]       ` <20130103191201.GA25680-OI9uyE9O0yo@public.gmane.org>
2013-01-05  9:10         ` Pontus Fuchs
     [not found]           ` <50E7EDEE.9090403-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-05 14:03             ` Marcin Slusarz

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=20130103125810.GA3198@joi.lan \
    --to=marcin.slusarz-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=pontus.fuchs-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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