| Summary: | [nv20] glx-swap-event hangs X server | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Ian Romanick <idr> |
| Component: | Drivers/DRI/nouveau | Assignee: | Nouveau Project <nouveau> |
| Status: | RESOLVED MOVED | QA Contact: | Nouveau Project <nouveau> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Ian Romanick
2017-06-06 22:37:42 UTC
A few things you may be interested in: (a) The pid always comes back as Xorg, since that's who opens the FD, even in a dri3 scenario. Only time that it's the real application is when you're using DRI3 *and* running on a secondary GPU. (b) Hangs in nouveau_bo_wait indicate that the GPU hung. Basically it's an ioctl that stalls until a fence is hit (the command for writing the fence is sent by the kernel on command submission). If it never returns, that means the fence is never hit. [Or there's a bug in our fence logic... I wonder if there's some sort of 32-bit wraparound sadness in there which is helped by piglit.] Since you have a reproducible hang, might want to check dmesg *before* running the test, and then seeing what happens. FWIW I always run piglit with "-x glx" -- that stuff never ends well on any generation with nouveau, and I've never had the desire to investigate it. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1134. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.