From: <bug...@an...> - 2006-08-29 12:52:29
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 Summary: r200: enabling/disabling of vertex programs (even in subsequent run apps) may cause lockups) Product: Mesa Version: CVS Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Drivers/DRI/r200 AssignedTo: dri...@li... ReportedBy: rsc...@gm... It seems that there is some initialization problem wrt to vertex programs, if you use them apps run after that may cause lockups. This was reported in bug #8009, with running celestia and then running World of Warcraft (with wine). (New bug because old one was really about a different problem). Without WoW I'm unable to reproduce the exact same problem but it's probably really nasty. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-08-29 13:03:30
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-08-29 06:03 ------- Created an attachment (id=6735) --> (https://bugs.freedesktop.org/attachment.cgi?id=6735&action=view) more vap state flushs to potentially prevent gpu lockups Could you try the attached patch (against drm). It's kinda ugly and I don't quite know why it would fix things, but this allowed to remove some other really ugly hack in the dri driver without getting lockups in doom3 (see next patch). I suspect somehow that if you enable/disable vertex programs you need a vap state flush, similar to that you sometimes need one when changing tcl parameters. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-08-29 13:06:25
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 rsc...@gm... changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dri- |rsc...@gm... |de...@li... | Status|NEW |ASSIGNED ------- Additional Comments From rsc...@gm... 2006-08-29 06:06 ------- Created an attachment (id=6736) --> (https://bugs.freedesktop.org/attachment.cgi?id=6736&action=view) disable the really ugly vp disable hack This patch removes the ugly, non-understood hack required to prevent lockups in doom3. You will experience lockups without the previous patch. Actually, I was sure I tried something along the lines of the previous patch earlier and it didn't work at that time :-(. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. |
From: <bug...@an...> - 2006-08-29 21:02:21
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-29 14:02 ------- Nope, those patches didn't help: - Replaced both drm/radeon kernel modules, as well as r200_dri.so object. - Rebooted - Enabled GL_ARB_vertex_program in celestia.cfg file - Ran celestia with planet rendering enabled - Ran World of Warcraft in OpenGL mode - *GPU LOCKUP* -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 08:11:14
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 01:11 ------- The problem with this bug is that I can't be sure which application is responsible for crashing my Radeon's GPU: celestia or Warcraft. Running celestia 1.4.1 once such that it uses the hardware's GL_ARB_vertex_program feature and renders planets is enough such that running Warcraft under Wine in OpenGL mode later will lock things up. HOWEVER, you should keep bug #8027 in mind. #8027 has two screen shots from Warcraft running "successfully" in both Direct3D mode and OpenGL mode, and you'll notice that the OpenGL screen is not exactly correct! More importantly, while Wine has no choice but to implement Direct3D using OpenGL primitives, the Direct3D mode doesn't cause lockups at all. Warcraft OpenGL has already been found to call the GetProgramiv() function for a vertex program that hasn't been loaded yet, and so it's possible that celestia is blameless in this bug and that Warcraft is performing another (unhandled) illegal thing. Maybe any vertex-using OpenGL application run before Warcraft would cause the same lock-up? Certainly any insight into what could be making Warcraft's OpenGL screen misrender the buttons (when pressed) and cursors would be welcome. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 09:44:09
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-08-30 02:44 ------- (In reply to comment #4) > HOWEVER, you should keep bug #8027 in mind. #8027 has two screen shots from > Warcraft running "successfully" in both Direct3D mode and OpenGL mode, and > you'll notice that the OpenGL screen is not exactly correct! More importantly, > while Wine has no choice but to implement Direct3D using OpenGL primitives, the > Direct3D mode doesn't cause lockups at all. Well, the gl commands generated may be quite different - there are even options for wine if it should emulate vertex shaders. > Warcraft OpenGL has already been found to call the GetProgramiv() function for a > vertex program that hasn't been loaded yet, and so it's possible that celestia > is blameless in this bug and that Warcraft is performing another (unhandled) > illegal thing. Maybe any vertex-using OpenGL application run before Warcraft > would cause the same lock-up? I'd suspect something like that, I'll need to double check the driver never "half-enables" vertex programs. Just to be clear, if you run celestia, but WoW not immidiately thereafter but after something else (say glxgears) it still locks up? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 22:30:43
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 15:30 ------- (In reply to comment #5) > Just to be clear, if you run celestia, but WoW not immidiately thereafter but > after something else (say glxgears) it still locks up? Yes: - Enable GL_ARB_vertex_program for celestia - Run celestia with planet rendering enabled, then exit - Run glxgears, then exit - Run Warcraft in OpenGL mode - *GPU lockup* This is as expected. After all, I can run Warcraft in Direct3D mode after celestia without locking up the GPU, and that is still an OpenGL program under the covers. BTW, I have also grabbed r200_vertprog.c 1.11 from CVS, but that hasn't affected anything either. And I've backed out the two patches (DRM and Mesa) that you posted as part of this bug because they had no effect. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 22:35:46
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-08-30 15:35 ------- (In reply to comment #6) > Yes: > - Enable GL_ARB_vertex_program for celestia > - Run celestia with planet rendering enabled, then exit > - Run glxgears, then exit > - Run Warcraft in OpenGL mode > - *GPU lockup* Guess it's time for that 3GB download :-(. > BTW, I have also grabbed r200_vertprog.c 1.11 from CVS, but that hasn't affected > anything either. Yes, that's expected, just fixes some other little things. > And I've backed out the two patches (DRM and Mesa) that you > posted as part of this bug because they had no effect. Those will go in the respective development repos soon, as it's "the right thing to do". I'm really happy to see the workaround in the dri driver go, workarounds you have no idea why they work are not a so good idea if you can actually fix the real problem... Even if it doesn't help for that bug. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 22:39:16
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 15:39 ------- About those two patches: Can the patched kernel module be used with the unpatched Mesa code? I already know that the GPU crashes if you patch Mesa without patching the kernel. (Your warning, plus personal experience...) -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 22:56:20
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 15:56 ------- Have just run arbvtest1: libGL warning: 3D driver claims to not support visual 0x4b Mesa: CPU vendor: GenuineIntel Mesa: CPU name: Intel(R) Xeon(TM) CPU 2.66GHz Mesa: MMX cpu detected. Mesa: SSE cpu detected. Mesa: Not testing OS support for SSE, leaving enabled. arbvptest1: r200_vertprog.c:564: r200_translate_vertex_program: Assertion `mesa_vp->Base.OutputsWritten & (1 << 0)' failed. Aborted (core dumped) Oops. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:01:20
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-08-30 16:01 ------- (In reply to comment #8) > About those two patches: Can the patched kernel module be used with the > unpatched Mesa code? I already know that the GPU crashes if you patch Mesa > without patching the kernel. (Your warning, plus personal experience...) Yes. It won't help, however. And if it does I'm going to cry. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:10:01
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 16:09 ------- Other things to report, from Mesa's test programs: - arpvptorus is another program like celestia that will lock Warcraft up. - arbvpwarpmesh does *not* lock Warcraft up later, although I was worried that it might. The Warcraft login screen took slightly longer to appear once I had run arbvpwarpmesh, but appear it did... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:19:09
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From bri...@tu... 2006-08-30 16:19 ------- The failing assertion: arbvptest1: r200_vertprog.c:564: r200_translate_vertex_program: Assertion `mesa_vp->Base.OutputsWritten & (1 << 0)' failed. might be an invalid assertion. I just double-checked the GL_ARB_v_p spec and apparently it's not an error to use a vertex program that does not write to result.position. It IS an error for GL_NV_v_p. The spec says the results will be undefined if result.position is not written (but we shouldn't crash). The arbvptest1.c program tests several program strings, one of which does not write result.position. That's probably the one that's failing. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:21:25
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 16:21 ------- arbvptest3 is Warcraft-friendly. Having arbvptest1 core-dump on me doesn't hurt Warcraft either. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:27:17
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-08-30 16:27 ------- (In reply to comment #9) > arbvptest1: r200_vertprog.c:564: r200_translate_vertex_program: Assertion > `mesa_vp->Base.OutputsWritten & (1 << 0)' failed. > Aborted (core dumped) > Oops. It's not really that big of a problem, and moreover it's not exactly new, it just wasn't exposed previously. arbvptest1 just loads some vertex programs, and never exececutes them, previous to the last commits such programs were never translated to hw, but now they are. The driver doesn't handle vertex progs which don't output position data, we'd need to either output some generated position data or just do a fallback. Such programs are apparently legal so there shouldn't be an abort(), though likely don't exist in practice. (In reply to comment #11) > Other things to report, from Mesa's test programs: > > - arpvptorus is another program like celestia that will lock Warcraft up. I'd guess any program which will actually run a vertex prog on the hardware will. > - arbvpwarpmesh does *not* lock Warcraft up later, although I was worried that > it might. The Warcraft login screen took slightly longer to appear once I had > run arbvpwarpmesh, but appear it did... arbvpwarpmesh uses generic attribs which aren't supported right now in the driver, thus this test never runs a vertex program on the hardware, just triggers a fallback. Not sure why arbvptest3 won't lock up later, probably we get lucky... -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:29:40
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 16:29 ------- I have removed the assertion from r200_vertprog.c, and can now say that arbvptest1 is Warcraft-friendly as well. So it's just arbvptorus that damages things, although arbvpwarpmesh seems to rattle them slightly (non-lethally) too. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:45:09
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 16:45 ------- (In reply to comment #14) > Not sure why arbvptest3 won't lock up later, probably we get lucky... Could it depend on what the vertex program was supposed to do? Something presumably has to parse them, assign parameters etc. And arbvptest1 just puts a black window on my screen. Is it supposed to do that? arbvptest3 gives me a multi-hued triangle. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:55:10
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From bri...@tu... 2006-08-30 16:55 ------- Don't worry about the output of the arb[vf]ptest?.c programs. They were intended for testing the program parser during development. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-30 23:59:35
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-08-30 16:59 ------- (In reply to comment #12) > The failing assertion: > > arbvptest1: r200_vertprog.c:564: r200_translate_vertex_program: Assertion > `mesa_vp->Base.OutputsWritten & (1 << 0)' failed. > > might be an invalid assertion. I just double-checked the GL_ARB_v_p spec and > apparently it's not an error to use a vertex program that does not write to > result.position. It IS an error for GL_NV_v_p. The spec says the results will > be undefined if result.position is not written (but we shouldn't crash). > > The arbvptest1.c program tests several program strings, one of which does not > write result.position. That's probably the one that's failing. Yes. I'm going to add a fallback instead. I'll also fix up writing to the BFC outputs just the same (this is actually strange, r200 can handle that with tnl, but I _never_ got fglrx to write a vertex prog to the hardware which writes that - the instruction to write it gets optimized away completely, and if you actually enable two-side lighting for vertex progs it runs a lot slower so presumably hits a fallback). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-31 00:16:23
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-08-30 17:16 ------- I've just discovered a workaround for the Warcraft lock-up bug: - Run celestia with GL_ARB_vertex_program enabled and planet rendering, then exit. - Switch to a console via (e.g) Alt-F6. - Switch back into X. - Run Warcraft in OpenGL mode. - Ta Da! I don't know if it helps, but I've also applied the patch in comment #1, and not applied the patch in comment #2. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-08-31 01:13:52
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-08-30 18:13 ------- (In reply to comment #12) > The failing assertion: > > arbvptest1: r200_vertprog.c:564: r200_translate_vertex_program: Assertion > `mesa_vp->Base.OutputsWritten & (1 << 0)' failed. > > might be an invalid assertion. Ok that's fixed, just use a fallback (if the shader is actually run) instead. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-09-01 19:03:19
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-09-01 12:03 ------- (In reply to comment #19) > I've just discovered a workaround for the Warcraft lock-up bug: > > - Run celestia with GL_ARB_vertex_program enabled and planet rendering, then exit. > - Switch to a console via (e.g) Alt-F6. > - Switch back into X. > - Run Warcraft in OpenGL mode. Since this seems to be some kind of initialization bug, that is probably due to the chip reset which is done when switching back to X. Actually I think I know what could cause it, I'll check in a patch soon. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-09-01 21:04:59
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-09-01 14:04 ------- (In reply to comment #19) Ok hopefully fixed in cvs (and if not another not yet discovered bug at least got fixed...). If WoW not only queried but actually also tried to execute a not specified shader, a lockup probably would have happened since the driver would not have set up a vertex program but enabled it anyway, so random junk (tnl data) would have got executed (except after a chip reset where it probably defaults to program length 0). If you can verify it no longer locks up you can close this bug. Note however that WoW most likely will still render wrong if this indeed fixes the lockup, I can't imagine that it would try to use non-existing shaders on purpose. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-09-01 22:03:03
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From ran...@ya... 2006-09-01 15:02 ------- Yes, you fixed the lockup. And WoW renders even more wrongly too, because there's now a curious item on the left of the login screen. Possibly this email might explain wine's behaviour: http://www.winehq.org/pipermail/wine-patches/2006-September/030335.html However, what worries me is that the flickering shadow on Saturn's rings is back in celestia 1.4.1. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |
From: <bug...@an...> - 2006-09-01 22:56:52
|
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=8060 ------- Additional Comments From rsc...@gm... 2006-09-01 15:56 ------- (In reply to comment #23) > Yes, you fixed the lockup. And WoW renders even more wrongly too, because > there's now a curious item on the left of the login screen. Possibly this email > might explain wine's behaviour: > > http://www.winehq.org/pipermail/wine-patches/2006-September/030335.html Maybe. In any case, doesn't appear to be a mesa bug then. > However, what worries me is that the flickering shadow on Saturn's rings is back > in celestia 1.4.1. You mean with the arb_vp path? Strange. Nothing in that patch should really change anything, as long as you don't specify bogus shader. Works just fine for me. Are you sure it's picking up the right driver file? The default location changed somewhat recently. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. |