All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 81136] New: [NV92] Regression in Linux 3.15: GPU lockup after suspend
Date: Thu, 10 Jul 2014 00:35:07 +0000	[thread overview]
Message-ID: <bug-81136-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2004 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=81136

          Priority: medium
            Bug ID: 81136
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: [NV92] Regression in Linux 3.15: GPU lockup after
                    suspend
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: agustin-G80yVrlpk+aH0oMTQjrRWA@public.gmane.org
          Hardware: All
            Status: NEW
           Version: git
         Component: Driver/nouveau
           Product: xorg

Created attachment 102508
  --> https://bugs.freedesktop.org/attachment.cgi?id=102508&action=edit
Logs for git kernel

After a suspend I get messages such as these: 

<3>[   39.550435] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH TLB flush idle
timeout fail
<3>[   39.550435] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH_STATUS  : 0x01000001
BUSY ROP
<3>[   39.550435] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH_VSTATUS0: 0x00000000
<3>[   39.550435] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH_VSTATUS1: 0x00000000
<3>[   39.550435] nouveau E[  PGRAPH][0000:01:00.0] PGRAPH_VSTATUS2: 0x00200000
ROP
<3>[   41.685486] nouveau E[     DRM] GPU lockup - switching to software fbcon

And if I was running X it crashes and the screen ends up looking like this:
http://imgur.com/a/D3VKw

This is always reproducible but only since Linux 3.15, so I ran a git bisect.
The first bad commit is [ecf24de071f4f6cea79ecef5d990794df5875ee1] drm/nouveau:
fix fbcon not being accelerated after suspend. After reverting the commmit the
machine resumes properly.

The issue persists in drm-nouveau-next (last commit 0b4e8e7... from Jul 8),
even if I boot with noaccel=1 nofbaccel=1.

Relevant IRC logs:
http://people.freedesktop.org/~cbrill/dri-log/index.php?channel=nouveau&highlight_names=Nitsuga&date=2014-07-09

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3637 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2014-07-10  0:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10  0:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-81136-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-07-10  0:35   ` [Bug 81136] [NV92] Regression in Linux 3.15: GPU lockup after suspend bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-10  0:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10  7:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10  7:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-10  9:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-11  4:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-16  5:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-25 21:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-27 22:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28  1:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28  2:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28  3:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-28  3:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-04-30  4:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-81136-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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 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.