[Nouveau] [Bug 76818] [NVE7] GPU lockup

[bugzilla-daemon at freedesktop.org]

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

--- Comment #8 from jw.hendy at gmail.com ---
@Max: can you confirm that this was only an issue due to two minotors? I'm
trying to decide if my similar issue is a replicate or if not since I'm simply
on a laptop here, no additional monitor issue.

@Ilia: I was experiencing similar issues (GPU Lockup, switching to fbcon in
dmesg) and system failure on `startx` back in Oct 2013. Here's an example log
after issuing `startx`:
- http://pastebin.com/qVY7WznX

I'm on Arch Linux and tried nouveau + the AUR nouveau-fw package (basically a
packaged version of nouveau's VideoAcceleration instructions), but was still
getting issues. Here's two dmesg outputs:
- http://pastebin.com/dV7gHS61
- http://pastebin.com/ZsCQmEwQ

I have been getting overheating cores and failure to suspend on lid close
lately, which prompted me to see about returning to nouveau and I found this
post. Your suggestion of:

nouveau.config=NvGrUseFw=1

Seems to have worked! I need to reboot once more to verify, as I'm on linux-lts
kernel (3.10.36) at the moment, but this was the first time I was able to
`startx` with nouveau and did not see the GPU lockup message in dmesg.

I'm trying to understand why this kernel line is necessary. I haven't seen it
at all before, either on the Arch Wiki or in the nouveau firmware instructions.
In fact, in googling it, I find primarily hits on bug reports regarding GPU
lockups! I'd think this would be more widespread in setup/debugging
instructions.

Thanks for any feedback -- I'd like to get information from someone who knows
and then update the Arch Wiki with this information in case it affects others.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20140412/91eaabe4/attachment.html>