<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - GF108 (NVC1) GPU lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=69488#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - GF108 (NVC1) GPU lockup" href="https://bugs.freedesktop.org/show_bug.cgi?id=69488">bug 69488</a> from <a class="email" href="mailto:vekinn@gmail.com" title="Kevin N. <vekinn@gmail.com>"> Kevin N.</a> <pre>(In reply to <a href="show_bug.cgi?id=69488#c11">comment #11</a>) > The IORESOURCE_BUSY patch is already on its way to Linus. However, all it > does is suppressing this warning. > > Could you describe what exactly the bug is you were seeing? You said it > falls back to "software frame buffer". The log doesn't say anything like > this, what do you mean by that? > Also, how did you detect a GPU lock-up? > > If the warning is all you see but everything was working just fine, this bug > can be closed. As the warning says "Your kernel is fine." this isn't serious > at all and shouldn't cause any issues. If you saw any other weird behavior, > please describe what exactly happened (apart from the oops message in the > log). My nvidia card doesn't work right with optimus and nouveau on 3.12-rc2. Starting X does sometimes work but the display stops responding soon after or when I run xrandr. Having my displayport plugged in seems to prevent that. GPU lockup was probably poor choice in words, display stops responding is more accurate. I end up having to power the machine off.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>