From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 79518] nouveau causes lockup and reboot on GT215 Date: Wed, 06 Apr 2016 20:27:40 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1856282945==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============1856282945== Content-Type: multipart/alternative; boundary="14599744601.515eead81.10932"; charset="UTF-8" --14599744601.515eead81.10932 Date: Wed, 6 Apr 2016 20:27:40 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=79518 --- Comment #6 from Ilia Mirkin --- (In reply to Adam Borowski from comment #5) > > Unfortunately I have no clue why those timeouts happen... basically it's an indication that the GPU is "done". > > I believe my hardware itself is ok, at least as in "never had any issue with > the proprietary driver". Those bastards dropped support for GT215 though... Yeah, I'm sure your HW is fine. But it just stops responding (reasonably) to nouveau when this happens, and we don't know what to do about it. Perhaps this is "normal" and the blob drivers know how to kick it in that case. Or perhaps we're doing something wrong to push the hw over the brink of sanity. > > Perhaps the memory comes up in a (slightly) funny state? You could try reclocking it and see if that improves matters, have a look in /sys/kernel/debug/dri/0/pstate for the available perf levels, you can echo those values in to change states. > > What values would you suggest? I'm afraid I did not find documentation > that's idiot-proof -- and I sadly got exactly 0 clue about this kind of > stuff so I require some handholding to give you useful debug info. cat /sys/kernel/debug/dri/0/pstate I can provide more instructions when you give me the output of that. -- You are receiving this mail because: You are the assignee for the bug. --14599744601.515eead81.10932 Date: Wed, 6 Apr 2016 20:27:40 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 6 on bug 79518 from 
(In reply to Adam Borowski from comment #5)
> > Unfortunately I have no clue why those timeouts happen... basically it's an indication that the GPU is "done".
> 
> I believe my hardware itself is ok, at least as in "never had any issue with
> the proprietary driver".  Those bastards dropped support for GT215 though...

Yeah, I'm sure your HW is fine. But it just stops responding (reasonably) to
nouveau when this happens, and we don't know what to do about it. Perhaps this
is "normal" and the blob drivers know how to kick it in that case. Or perhaps
we're doing something wrong to push the hw over the brink of sanity.

> > Perhaps the memory comes up in a (slightly) funny state? You could try reclocking it and see if that improves matters, have a look in /sys/kernel/debug/dri/0/pstate for the available perf levels, you can echo those values in to change states.
> 
> What values would you suggest?  I'm afraid I did not find documentation
> that's idiot-proof -- and I sadly got exactly 0 clue about this kind of
> stuff so I require some handholding to give you useful debug info.

cat /sys/kernel/debug/dri/0/pstate

I can provide more instructions when you give me the output of that.

You are receiving this mail because:
  • You are the assignee for the bug.
--14599744601.515eead81.10932-- --===============1856282945== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============1856282945==--