From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 67878] [NV98] [BISECTED] Hardware freeze after resume from suspend Date: Sun, 08 Dec 2013 20:15:13 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0579793780==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0579793780== Content-Type: multipart/alternative; boundary="1386533713.FBBa73.11755"; charset="us-ascii" --1386533713.FBBa73.11755 Date: Sun, 8 Dec 2013 20:15:13 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=67878 --- Comment #34 from Pontus Fuchs --- (In reply to comment #32) > One idea I just randomly had was that there might be a difference in the > teardown process. For example, in the removed code, nv50_display_fini did > stuff. In the current code, it's basically empty (well, some small bits in > nouveau_display_fini). > > It looks like the old code > > (a) blanked each crtc > (b) sent out a EVO_UPDATE command > (c) waited for each crtc to hit a vblank > (d) did something with the cursor (cleared it?) > (e) waited for some sort of DPMS thing > > It could well be that this now happens elsewhere, but I just wanted to put > that thought down on "paper". I tried this idea by doing the following: 1) Checked out 4f6029da58ba9204c98e33f4f3737fe085c87a6f^1 (= f9887d091149406de5c8b388f7e0bb6932dd621b) 2) Deleted everything in nv50_display_fini With that change suspend/resume works so I guess the problem is elsewhere. -- You are receiving this mail because: You are the assignee for the bug. --1386533713.FBBa73.11755 Date: Sun, 8 Dec 2013 20:15:13 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 34 on bug 67878 from 
(In reply to comment #32)
> One idea I just randomly had was that there might be a difference in the
> teardown process. For example, in the removed code, nv50_display_fini did
> stuff. In the current code, it's basically empty (well, some small bits in
> nouveau_display_fini).
> 
> It looks like the old code
> 
> (a) blanked each crtc
> (b) sent out a EVO_UPDATE command
> (c) waited for each crtc to hit a vblank
> (d) did something with the cursor (cleared it?)
> (e) waited for some sort of DPMS thing
> 
> It could well be that this now happens elsewhere, but I just wanted to put
> that thought down on "paper".

I tried this idea by doing the following:

1) Checked out 4f6029da58ba9204c98e33f4f3737fe085c87a6f^1 (=
f9887d091149406de5c8b388f7e0bb6932dd621b)
2) Deleted everything in nv50_display_fini

With that change suspend/resume works so I guess the problem is elsewhere.

You are receiving this mail because:
  • You are the assignee for the bug.
--1386533713.FBBa73.11755-- --===============0579793780== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Nouveau mailing list Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org http://lists.freedesktop.org/mailman/listinfo/nouveau --===============0579793780==--