Nouveau - Mar 2015 - [Bug 89679] New: [NV50] Portal/Half-Life 2 will not start (native Steam)

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

            Bug ID: 89679
           Summary: [NV50] Portal/Half-Life 2 will not start (native
                    Steam)
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: nick.tenney at gmail.com
        QA Contact: nouveau at lists.freedesktop.org

Created attachment 114474
  --> https://bugs.freedesktop.org/attachment.cgi?id=114474&action=edit
Dump from Steam crash

Not particularly sure how to debug, but both titles crash immediately after
loading the menu screen. I confirmed that r600g with the same mesa build on
another machine had no issues. Let me know if there are any relevant logs I can
provide

Details:
1.17.1 xserver
1.0.11 xf86-video-nouveau
68854.2372275 mesa-git
4.0rc4 linux-git

Only relevant line in dmesg:
[ 6389.605899] streaming_clien[6094]: segfault at 0 ip 00000000f75ee410 sp
00000000ffe6c9d0 error 4 in streaming_client[f7576000+195000]

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

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

--- Comment #1 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Can you check if older mesa builds work (like 10.2 or 10.3)? If they do, you
can try bisecting. I've had another report of Portal crashing with nouveau,
and
it being a recent phenomenon...

You could also run steam in a debugger and see if the crash ends up in nouveau.
If so, give me a full backtrace. If not, might be some memory corruption... if
there's a way to run steam with valgrind, you can try that.

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

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

--- Comment #2 from Nick Tenney <nick.tenney at gmail.com> ---
I was bisecting and it *appeared* to go well. Apparently something else must be
involved as the last known good commit (worked during the bisect) no longer
worked when I restested. Digging further...

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

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

--- Comment #3 from Nick Tenney <nick.tenney at gmail.com> ---
Created attachment 114677
  --> https://bugs.freedesktop.org/attachment.cgi?id=114677&action=edit
Git bisection of Mesa

Third time's a charm! Finally got a successful bisection of the Portal
issue.

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

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

--- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to Nick Tenney from comment #3)
> Created attachment 114677 [details]
> Git bisection of Mesa
> 
> Third time's a charm! Finally got a successful bisection of the Portal
issue.
That seems very surprising. Does reverting it on top of master fix the issue?
If not, your bisect is off.

The commit does 2 things -- it increases the query alloc space to 256 and it
enables PIPE_CAP_QUERY_PIPELINE_STATISTICS (and the relevant support in the
query logic). I have a hard time believing that steam would use
ARB_pipeline_query_statistics, but... who knows.

Can you disable PIPE_CAP_QUERY_PIPELINE_STATISTICS but leave
NV50_QUERY_ALLOC_SPACE at 256 and see if it still breaks?

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

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

--- Comment #5 from Nick Tenney <nick.tenney at gmail.com> ---
Reverting 5000a5f67b556096b6ba1e9bdac3a6e5cd5a1f68 did the trick. I shall try
the query alloc space change tomorrow. Thanks!

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

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

--- Comment #6 from Nick Tenney <nick.tenney at gmail.com> ---
Now that it's tomorrow (EST) and this apparently compiled in time, reverting
the commit excepting the query alloc space change resulted in a crash. Just for
kicks and giggles, I went back to master and changed the QUERY_ALLOC_SPACE back
to 128 and all was well. We have a winner.

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

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

Nick Tenney <nick.tenney at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Nick Tenney <nick.tenney at gmail.com> ---
Commit ba353935a392d2a43422f1d258456336b40b60ea fixed the issue. Thanks!

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