[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 Michel D?nzer changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #127 from Michel D?nzer 2012-08-17 07:26:52 UTC --- (In reply to comment #126) > I won't say for sure the vm problem is fixed, but if it's still there, latest > patches helped a lot since I was able to run more than twice as long as usual > without any problem. Great! Resolving this bug as fixed. Any other remaining issues, in particular Thomas' glamor issues, should be tracked in separate bug reports. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #126 from Alexandre Demers 2012-08-17 03:18:27 UTC --- Good news on my side: I was unable to recreate the bug until now. So I went with running pilit tests. Sadly, for that part, it still locks (now tracked under bug 53111). I won't say for sure the vm problem is fixed, but if it's still there, latest patches helped a lot since I was able to run more than twice as long as usual without any problem. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #125 from Alexandre Demers 2012-08-17 03:00:53 UTC --- (In reply to comment #124) > And there are some random rendering issues that wasn't there before the > patches, like using the wrong texture. > > Good: http://img713.imageshack.us/img713/492/mcgood.png > Bad: http://img96.imageshack.us/img96/6417/mcbad.png > > Also water in the game flashes white (seems to choose the wrong texture > sometimes in the animation, too) and sometimes the whole game screen flashes > blue. I won't officially answer you question, but I think it should be tracked under a different bug since you are using Glamor. However, if I was you, I would create a new bug entry with a reference to this one. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 Michel Dänzer mic...@daenzer.net changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #127 from Michel Dänzer mic...@daenzer.net 2012-08-17 07:26:52 UTC --- (In reply to comment #126) I won't say for sure the vm problem is fixed, but if it's still there, latest patches helped a lot since I was able to run more than twice as long as usual without any problem. Great! Resolving this bug as fixed. Any other remaining issues, in particular Thomas' glamor issues, should be tracked in separate bug reports. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #124 from Thomas Rohloff 2012-08-16 21:03:39 UTC --- And there are some random rendering issues that wasn't there before the patches, like using the wrong texture. Good: http://img713.imageshack.us/img713/492/mcgood.png Bad: http://img96.imageshack.us/img96/6417/mcbad.png Also water in the game flashes white (seems to choose the wrong texture sometimes in the animation, too) and sometimes the whole game screen flashes blue. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #123 from Thomas Rohloff 2012-08-16 20:10:32 UTC --- (In reply to comment #119) > (In reply to comment #118) > > Try the Mesa patches from > http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . Not sure if this is related or if I should open a new report, but since this patches I get this when I try to start compiz with GLAMOR acceleration: http://pastebin.com/WbxMT0V9 - before I got the "conficts with" messages and without GLAMOR I get (and got) no messages at all but compiz loads slow and the screen flickers while doing so. P.S. Also the desktop is corrupted with GLAMOR. This is better since this patches but still there. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 Alex Deucher changed: What|Removed |Added CC||v10lator at myway.de --- Comment #122 from Alex Deucher 2012-08-16 16:59:49 UTC --- *** Bug 53291 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #121 from Alexandre Demers 2012-08-16 15:35:45 UTC --- (In reply to comment #120) > (In reply to comment #119) > > (In reply to comment #118) > > > > Try the Mesa patches from > > http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . > > Testing right now. > > May I suggest adding some debug info with an env variable switch to be able to > track what the vm_mgr is doing, keeping and forgetting if this doesn't fix the > problem or something similar? I've been testing to reproduce latest VA issue all evening without being able to. So if it doesn't finally fix the problem, your patches do help a lot. I'll continue to test it tonight. Good to know your patches have been commited this morning. However, keep in mind I haven't tested anything for the other lockups (piglit tests and some other OpenGL apps). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #120 from Alexandre Demers 2012-08-16 00:38:42 UTC --- (In reply to comment #119) > (In reply to comment #118) > > Try the Mesa patches from > http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . Testing right now. May I suggest adding some debug info with an env variable switch to be able to track what the vm_mgr is doing, keeping and forgetting if this doesn't fix the problem or something similar? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #121 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-16 15:35:45 UTC --- (In reply to comment #120) (In reply to comment #119) (In reply to comment #118) Try the Mesa patches from http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . Testing right now. May I suggest adding some debug info with an env variable switch to be able to track what the vm_mgr is doing, keeping and forgetting if this doesn't fix the problem or something similar? I've been testing to reproduce latest VA issue all evening without being able to. So if it doesn't finally fix the problem, your patches do help a lot. I'll continue to test it tonight. Good to know your patches have been commited this morning. However, keep in mind I haven't tested anything for the other lockups (piglit tests and some other OpenGL apps). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 Alex Deucher ag...@yahoo.com changed: What|Removed |Added CC||v10la...@myway.de --- Comment #122 from Alex Deucher ag...@yahoo.com 2012-08-16 16:59:49 UTC --- *** Bug 53291 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #123 from Thomas Rohloff v10la...@myway.de 2012-08-16 20:10:32 UTC --- (In reply to comment #119) (In reply to comment #118) Try the Mesa patches from http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . Not sure if this is related or if I should open a new report, but since this patches I get this when I try to start compiz with GLAMOR acceleration: http://pastebin.com/WbxMT0V9 - before I got the conficts with messages and without GLAMOR I get (and got) no messages at all but compiz loads slow and the screen flickers while doing so. P.S. Also the desktop is corrupted with GLAMOR. This is better since this patches but still there. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #124 from Thomas Rohloff v10la...@myway.de 2012-08-16 21:03:39 UTC --- And there are some random rendering issues that wasn't there before the patches, like using the wrong texture. Good: http://img713.imageshack.us/img713/492/mcgood.png Bad: http://img96.imageshack.us/img96/6417/mcbad.png Also water in the game flashes white (seems to choose the wrong texture sometimes in the animation, too) and sometimes the whole game screen flashes blue. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #125 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-17 03:00:53 UTC --- (In reply to comment #124) And there are some random rendering issues that wasn't there before the patches, like using the wrong texture. Good: http://img713.imageshack.us/img713/492/mcgood.png Bad: http://img96.imageshack.us/img96/6417/mcbad.png Also water in the game flashes white (seems to choose the wrong texture sometimes in the animation, too) and sometimes the whole game screen flashes blue. I won't officially answer you question, but I think it should be tracked under a different bug since you are using Glamor. However, if I was you, I would create a new bug entry with a reference to this one. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #126 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-17 03:18:27 UTC --- Good news on my side: I was unable to recreate the bug until now. So I went with running pilit tests. Sadly, for that part, it still locks (now tracked under bug 53111). I won't say for sure the vm problem is fixed, but if it's still there, latest patches helped a lot since I was able to run more than twice as long as usual without any problem. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #119 from Michel D?nzer 2012-08-15 16:07:30 UTC --- (In reply to comment #118) Try the Mesa patches from http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #119 from Michel Dänzer mic...@daenzer.net 2012-08-15 16:07:30 UTC --- (In reply to comment #118) Try the Mesa patches from http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #120 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-16 00:38:42 UTC --- (In reply to comment #119) (In reply to comment #118) Try the Mesa patches from http://lists.freedesktop.org/archives/mesa-dev/2012-August/025715.html . Testing right now. May I suggest adding some debug info with an env variable switch to be able to track what the vm_mgr is doing, keeping and forgetting if this doesn't fix the problem or something similar? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #118 from Alexandre Demers 2012-08-11 04:49:31 UTC --- Reproduced again with exactly the setup Alex told me to use (kernel 3.6-rc1+Jerome's patch v4 and latest mesa containing Christian's fix). To reproduce, I clicked repeatedly on Activities on top left corner of Gnome shell until it locked: Everything.log --- Aug 11 00:23:08 Xander kernel: [92926.580673] radeon :01:00.0: offset 0x20 is in reserved area 0x80 Aug 11 00:23:08 Xander kernel: [92926.587281] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x11 Aug 11 00:23:08 Xander kernel: [92926.587291] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! Aug 11 00:23:08 Xander kernel: [92926.597151] radeon :01:00.0: offset 0x20 is in reserved area 0x80 Aug 11 00:23:18 Xander kernel: [92937.073091] radeon :01:00.0: GPU lockup CP stall for more than 1msec Aug 11 00:23:18 Xander kernel: [92937.073105] radeon :01:00.0: GPU lockup (waiting for 0x0009ea1d last fence id 0x0009ea1c) Aug 11 00:23:18 Xander kernel: [92937.074236] radeon :01:00.0: Saved 15 dwords of commands on ring 0. Aug 11 00:23:18 Xander kernel: [92937.074243] radeon :01:00.0: GPU softreset Aug 11 00:23:18 Xander kernel: [92937.074248] radeon :01:00.0: GRBM_STATUS=0xF5700828 Aug 11 00:23:18 Xander kernel: [92937.074253] radeon :01:00.0: GRBM_STATUS_SE0=0xFC01 Aug 11 00:23:18 Xander kernel: [92937.074258] radeon :01:00.0: GRBM_STATUS_SE1=0xFC01 Aug 11 00:23:18 Xander kernel: [92937.074263] radeon :01:00.0: SRBM_STATUS=0x20020FC0 Aug 11 00:23:18 Xander kernel: [92937.074269] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 11 00:23:18 Xander kernel: [92937.074274] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x4000 Aug 11 00:23:18 Xander kernel: [92937.074279] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x8004 Aug 11 00:23:18 Xander kernel: [92937.074284] radeon :01:00.0: R_008680_CP_STAT = 0x80228647 Aug 11 00:23:18 Xander kernel: [92937.074289] radeon :01:00.0: VM_CONTEXT0_PROTECTION_FAULT_ADDR 0x00074124 Aug 11 00:23:18 Xander kernel: [92937.074294] radeon :01:00.0: VM_CONTEXT0_PROTECTION_FAULT_STATUS 0x00071001 Aug 11 00:23:18 Xander kernel: [92937.074300] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x21F1 Aug 11 00:23:18 Xander kernel: [92937.074305] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A4004 Aug 11 00:23:19 Xander kernel: [92937.223150] radeon :01:00.0: Wait for MC idle timedout ! Aug 11 00:23:19 Xander kernel: [92937.223152] radeon :01:00.0: GRBM_SOFT_RESET=0xDF7B Aug 11 00:23:19 Xander kernel: [92937.223254] radeon :01:00.0: GRBM_STATUS=0x80103828 Aug 11 00:23:19 Xander kernel: [92937.223256] radeon :01:00.0: GRBM_STATUS_SE0=0x0407 Aug 11 00:23:19 Xander kernel: [92937.223257] radeon :01:00.0: GRBM_STATUS_SE1=0x0407 Aug 11 00:23:19 Xander kernel: [92937.223258] radeon :01:00.0: SRBM_STATUS=0x20020FC0 Aug 11 00:23:19 Xander kernel: [92937.223260] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 11 00:23:19 Xander kernel: [92937.223262] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x Aug 11 00:23:19 Xander kernel: [92937.223263] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x Aug 11 00:23:19 Xander kernel: [92937.223264] radeon :01:00.0: R_008680_CP_STAT = 0x Aug 11 00:23:19 Xander kernel: [92937.224266] radeon :01:00.0: GPU reset succeeded, trying to resume Aug 11 00:23:19 Xander kernel: [92937.230003] [drm] probing gen 2 caps for device 1022:9603 = 2/0 Aug 11 00:23:19 Xander kernel: [92937.230004] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Aug 11 00:23:19 Xander kernel: [92937.388426] radeon :01:00.0: Wait for MC idle timedout ! Aug 11 00:23:19 Xander kernel: [92937.546743] radeon :01:00.0: Wait for MC idle timedout ! Aug 11 00:23:19 Xander kernel: [92937.548662] [drm] PCIE GART of 512M enabled (table at 0x0004). Aug 11 00:23:19 Xander kernel: [92937.548751] radeon :01:00.0: WB enabled Aug 11 00:23:19 Xander kernel: [92937.548754] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x88022332dc00 Aug 11 00:23:19 Xander kernel: [92937.548755] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x88022332dc04 Aug 11 00:23:19 Xander kernel: [92937.548757] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x88022332dc08 Aug 11 00:23:19 Xander kernel: [92937.752374] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) Aug 11 00:23:19 Xander kernel: [92937.752377] [drm:cayman_resume] *ERROR* cayman startup failed on resume Could it be a previously hidden bug that patches from Jerome
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #118 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-11 04:49:31 UTC --- Reproduced again with exactly the setup Alex told me to use (kernel 3.6-rc1+Jerome's patch v4 and latest mesa containing Christian's fix). To reproduce, I clicked repeatedly on Activities on top left corner of Gnome shell until it locked: Everything.log --- Aug 11 00:23:08 Xander kernel: [92926.580673] radeon :01:00.0: offset 0x20 is in reserved area 0x80 Aug 11 00:23:08 Xander kernel: [92926.587281] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0x11 Aug 11 00:23:08 Xander kernel: [92926.587291] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2! Aug 11 00:23:08 Xander kernel: [92926.597151] radeon :01:00.0: offset 0x20 is in reserved area 0x80 Aug 11 00:23:18 Xander kernel: [92937.073091] radeon :01:00.0: GPU lockup CP stall for more than 1msec Aug 11 00:23:18 Xander kernel: [92937.073105] radeon :01:00.0: GPU lockup (waiting for 0x0009ea1d last fence id 0x0009ea1c) Aug 11 00:23:18 Xander kernel: [92937.074236] radeon :01:00.0: Saved 15 dwords of commands on ring 0. Aug 11 00:23:18 Xander kernel: [92937.074243] radeon :01:00.0: GPU softreset Aug 11 00:23:18 Xander kernel: [92937.074248] radeon :01:00.0: GRBM_STATUS=0xF5700828 Aug 11 00:23:18 Xander kernel: [92937.074253] radeon :01:00.0: GRBM_STATUS_SE0=0xFC01 Aug 11 00:23:18 Xander kernel: [92937.074258] radeon :01:00.0: GRBM_STATUS_SE1=0xFC01 Aug 11 00:23:18 Xander kernel: [92937.074263] radeon :01:00.0: SRBM_STATUS=0x20020FC0 Aug 11 00:23:18 Xander kernel: [92937.074269] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 11 00:23:18 Xander kernel: [92937.074274] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x4000 Aug 11 00:23:18 Xander kernel: [92937.074279] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x8004 Aug 11 00:23:18 Xander kernel: [92937.074284] radeon :01:00.0: R_008680_CP_STAT = 0x80228647 Aug 11 00:23:18 Xander kernel: [92937.074289] radeon :01:00.0: VM_CONTEXT0_PROTECTION_FAULT_ADDR 0x00074124 Aug 11 00:23:18 Xander kernel: [92937.074294] radeon :01:00.0: VM_CONTEXT0_PROTECTION_FAULT_STATUS 0x00071001 Aug 11 00:23:18 Xander kernel: [92937.074300] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x21F1 Aug 11 00:23:18 Xander kernel: [92937.074305] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x020A4004 Aug 11 00:23:19 Xander kernel: [92937.223150] radeon :01:00.0: Wait for MC idle timedout ! Aug 11 00:23:19 Xander kernel: [92937.223152] radeon :01:00.0: GRBM_SOFT_RESET=0xDF7B Aug 11 00:23:19 Xander kernel: [92937.223254] radeon :01:00.0: GRBM_STATUS=0x80103828 Aug 11 00:23:19 Xander kernel: [92937.223256] radeon :01:00.0: GRBM_STATUS_SE0=0x0407 Aug 11 00:23:19 Xander kernel: [92937.223257] radeon :01:00.0: GRBM_STATUS_SE1=0x0407 Aug 11 00:23:19 Xander kernel: [92937.223258] radeon :01:00.0: SRBM_STATUS=0x20020FC0 Aug 11 00:23:19 Xander kernel: [92937.223260] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x Aug 11 00:23:19 Xander kernel: [92937.223262] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x Aug 11 00:23:19 Xander kernel: [92937.223263] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x Aug 11 00:23:19 Xander kernel: [92937.223264] radeon :01:00.0: R_008680_CP_STAT = 0x Aug 11 00:23:19 Xander kernel: [92937.224266] radeon :01:00.0: GPU reset succeeded, trying to resume Aug 11 00:23:19 Xander kernel: [92937.230003] [drm] probing gen 2 caps for device 1022:9603 = 2/0 Aug 11 00:23:19 Xander kernel: [92937.230004] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 Aug 11 00:23:19 Xander kernel: [92937.388426] radeon :01:00.0: Wait for MC idle timedout ! Aug 11 00:23:19 Xander kernel: [92937.546743] radeon :01:00.0: Wait for MC idle timedout ! Aug 11 00:23:19 Xander kernel: [92937.548662] [drm] PCIE GART of 512M enabled (table at 0x0004). Aug 11 00:23:19 Xander kernel: [92937.548751] radeon :01:00.0: WB enabled Aug 11 00:23:19 Xander kernel: [92937.548754] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x88022332dc00 Aug 11 00:23:19 Xander kernel: [92937.548755] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x4c04 and cpu addr 0x88022332dc04 Aug 11 00:23:19 Xander kernel: [92937.548757] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x4c08 and cpu addr 0x88022332dc08 Aug 11 00:23:19 Xander kernel: [92937.752374] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) Aug 11 00:23:19 Xander kernel: [92937.752377] [drm:cayman_resume] *ERROR* cayman startup failed on resume Could it be a previously hidden
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #117 from Alex Deucher 2012-08-09 18:50:34 UTC --- (In reply to comment #116) > > And if someone could explain me what this message/addresses means, I'd > appreciate it. How is it possible that an offset of 0x40 ends up in a > reserved area allocated at 0x80? We must not be offsetting from 0 > obviously. The first 8 MB of the client's VM space are reserved for kernel use and not available for the client to use. The client is not allowed to use an address below 0x80. If an address ends up there, the kernel flags it. That's the message you are seeing. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #116 from Alexandre Demers 2012-08-09 15:24:41 UTC --- (In reply to comment #113) > (In reply to comment #112) > > (In reply to comment #111) > > > (In reply to comment #110) > > > > I just pushed a minor bugfix to mesa master, that in conjunction with > > > > Jeromes > > > > kernel patch should eliminate the last VA issues. > > > > > > > > Please retest it again. > > > > > > > > Christian. > > > > > > You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. > > > Do I > > > still need to apply your previous patch also (attachment 65093 [details] > > > [review] [review] [review])? I'll try it > > > tonight, but it may take a bit more complicated to reproduce, I'll have > > > to play > > > for a while until it does or doesn't trigger the last reported vm error. > > > > Well, I tested it with your previous patch on top of > > 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17 and it was not working properly. > > First, I had to modify your patch to apply on top of latest git. After > > applying > > it, compiling and installing, I rebooted and I was unable to load the > > logging > > screen. I removed the patch, rebuilt a clean mesa from > > 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17, installed and relaunched Xorg > > and... > > I was able to log in. So I'm now testing latest mesa > > (68bccc40f55aee7f4af8eb64b15a95f0b49d6a17) with kernel 3.6-rc1 + Jerome's > > patch. I should be able to tell you soon if it works. Meanwhile, if I should > > have applied something different, let me know. > > > > To Jerome: I could test your [PATCH] drm/radeon: delay virtual address > > destruction to bo destruction. But first, I want to make sure Christian's > > patch > > does what it should do. > > Bug still there with latest mesa git (without your previous patch as explained > previously). > Aug 9 01:03:29 Xander kernel: [13308.165749] radeon :01:00.0: offset > 0x40 is in reserved area 0x80 > Aug 9 01:03:29 Xander kernel: [13308.232245] radeon :01:00.0: bo > 880223646400 va 0x02B0 conflict with (bo 8801e3edc400 > > Locked and reset without any notice. Two things I've noticed: 1- the error points directly at "offset 0x40 is in reserved area 0x80" since I applied Christian's and Jerome's patches, which is a different error from errors before patches. 2- the error only happens after a while, when switching between windows (under Gnome 3 in that case). I had to alt+tab and show my whole desktop (top left corner) many times before it happened. I played with my desktop all night long. So, it's like if the pointer keeps increasing until it reaches its limit. Either we are not releasing correctly previous addresses (or we are forgetting some on the way)or we are unaware of every released addresses, in both cases pushing us forward until we hit a wall. And if someone could explain me what this message/addresses means, I'd appreciate it. How is it possible that an offset of 0x40 ends up in a reserved area allocated at 0x80? We must not be offsetting from 0 obviously. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #115 from Alexandre Demers 2012-08-09 14:56:34 UTC --- (In reply to comment #114) > Please test mesa from git (no additional patches) and make sure your kernel > has > this patch: > http://lists.freedesktop.org/archives/dri-devel/2012-August/026015.html > (no other kernel patches). It looks pretty much to what I was testing with (latest mesa git without any patch as explained in comment 112) where I had already applied Jerome's patch v2 (no other patch). v4 doesn't seem to have any major differences (according to comment for v3 and v4). Nevertheless, I'll recompile kernel 3.6-rc1 with patch v4 just in case, though I would be surprised if that would make a difference from test/error reported in comment 113. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #114 from Alex Deucher 2012-08-09 14:14:04 UTC --- Please test mesa from git (no additional patches) and make sure your kernel has this patch: http://lists.freedesktop.org/archives/dri-devel/2012-August/026015.html (no other kernel patches). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #113 from Alexandre Demers 2012-08-09 05:20:04 UTC --- (In reply to comment #112) > (In reply to comment #111) > > (In reply to comment #110) > > > I just pushed a minor bugfix to mesa master, that in conjunction with > > > Jeromes > > > kernel patch should eliminate the last VA issues. > > > > > > Please retest it again. > > > > > > Christian. > > > > You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. Do > > I > > still need to apply your previous patch also (attachment 65093 [details] > > [review] [review])? I'll try it > > tonight, but it may take a bit more complicated to reproduce, I'll have to > > play > > for a while until it does or doesn't trigger the last reported vm error. > > Well, I tested it with your previous patch on top of > 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17 and it was not working properly. > First, I had to modify your patch to apply on top of latest git. After > applying > it, compiling and installing, I rebooted and I was unable to load the logging > screen. I removed the patch, rebuilt a clean mesa from > 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17, installed and relaunched Xorg and... > I was able to log in. So I'm now testing latest mesa > (68bccc40f55aee7f4af8eb64b15a95f0b49d6a17) with kernel 3.6-rc1 + Jerome's > patch. I should be able to tell you soon if it works. Meanwhile, if I should > have applied something different, let me know. > > To Jerome: I could test your [PATCH] drm/radeon: delay virtual address > destruction to bo destruction. But first, I want to make sure Christian's > patch > does what it should do. Bug still there with latest mesa git (without your previous patch as explained previously). Aug 9 01:03:29 Xander kernel: [13308.165749] radeon :01:00.0: offset 0x40 is in reserved area 0x80 Aug 9 01:03:29 Xander kernel: [13308.232245] radeon :01:00.0: bo 880223646400 va 0x02B0 conflict with (bo 8801e3edc400 Locked and reset without any notice. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #112 from Alexandre Demers 2012-08-09 01:38:41 UTC --- (In reply to comment #111) > (In reply to comment #110) > > I just pushed a minor bugfix to mesa master, that in conjunction with > > Jeromes > > kernel patch should eliminate the last VA issues. > > > > Please retest it again. > > > > Christian. > > You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. Do I > still need to apply your previous patch also (attachment 65093 [details] > [review])? I'll try it > tonight, but it may take a bit more complicated to reproduce, I'll have to > play > for a while until it does or doesn't trigger the last reported vm error. Well, I tested it with your previous patch on top of 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17 and it was not working properly. First, I had to modify your patch to apply on top of latest git. After applying it, compiling and installing, I rebooted and I was unable to load the logging screen. I removed the patch, rebuilt a clean mesa from 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17, installed and relaunched Xorg and... I was able to log in. So I'm now testing latest mesa (68bccc40f55aee7f4af8eb64b15a95f0b49d6a17) with kernel 3.6-rc1 + Jerome's patch. I should be able to tell you soon if it works. Meanwhile, if I should have applied something different, let me know. To Jerome: I could test your [PATCH] drm/radeon: delay virtual address destruction to bo destruction. But first, I want to make sure Christian's patch does what it should do. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #114 from Alex Deucher ag...@yahoo.com 2012-08-09 14:14:04 UTC --- Please test mesa from git (no additional patches) and make sure your kernel has this patch: http://lists.freedesktop.org/archives/dri-devel/2012-August/026015.html (no other kernel patches). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #115 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-09 14:56:34 UTC --- (In reply to comment #114) Please test mesa from git (no additional patches) and make sure your kernel has this patch: http://lists.freedesktop.org/archives/dri-devel/2012-August/026015.html (no other kernel patches). It looks pretty much to what I was testing with (latest mesa git without any patch as explained in comment 112) where I had already applied Jerome's patch v2 (no other patch). v4 doesn't seem to have any major differences (according to comment for v3 and v4). Nevertheless, I'll recompile kernel 3.6-rc1 with patch v4 just in case, though I would be surprised if that would make a difference from test/error reported in comment 113. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #116 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-09 15:24:41 UTC --- (In reply to comment #113) (In reply to comment #112) (In reply to comment #111) (In reply to comment #110) I just pushed a minor bugfix to mesa master, that in conjunction with Jeromes kernel patch should eliminate the last VA issues. Please retest it again. Christian. You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. Do I still need to apply your previous patch also (attachment 65093 [details] [review] [review] [review])? I'll try it tonight, but it may take a bit more complicated to reproduce, I'll have to play for a while until it does or doesn't trigger the last reported vm error. Well, I tested it with your previous patch on top of 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17 and it was not working properly. First, I had to modify your patch to apply on top of latest git. After applying it, compiling and installing, I rebooted and I was unable to load the logging screen. I removed the patch, rebuilt a clean mesa from 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17, installed and relaunched Xorg and... I was able to log in. So I'm now testing latest mesa (68bccc40f55aee7f4af8eb64b15a95f0b49d6a17) with kernel 3.6-rc1 + Jerome's patch. I should be able to tell you soon if it works. Meanwhile, if I should have applied something different, let me know. To Jerome: I could test your [PATCH] drm/radeon: delay virtual address destruction to bo destruction. But first, I want to make sure Christian's patch does what it should do. Bug still there with latest mesa git (without your previous patch as explained previously). Aug 9 01:03:29 Xander kernel: [13308.165749] radeon :01:00.0: offset 0x40 is in reserved area 0x80 Aug 9 01:03:29 Xander kernel: [13308.232245] radeon :01:00.0: bo 880223646400 va 0x02B0 conflict with (bo 8801e3edc400 Locked and reset without any notice. Two things I've noticed: 1- the error points directly at offset 0x40 is in reserved area 0x80 since I applied Christian's and Jerome's patches, which is a different error from errors before patches. 2- the error only happens after a while, when switching between windows (under Gnome 3 in that case). I had to alt+tab and show my whole desktop (top left corner) many times before it happened. I played with my desktop all night long. So, it's like if the pointer keeps increasing until it reaches its limit. Either we are not releasing correctly previous addresses (or we are forgetting some on the way)or we are unaware of every released addresses, in both cases pushing us forward until we hit a wall. And if someone could explain me what this message/addresses means, I'd appreciate it. How is it possible that an offset of 0x40 ends up in a reserved area allocated at 0x80? We must not be offsetting from 0 obviously. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #117 from Alex Deucher ag...@yahoo.com 2012-08-09 18:50:34 UTC --- (In reply to comment #116) And if someone could explain me what this message/addresses means, I'd appreciate it. How is it possible that an offset of 0x40 ends up in a reserved area allocated at 0x80? We must not be offsetting from 0 obviously. The first 8 MB of the client's VM space are reserved for kernel use and not available for the client to use. The client is not allowed to use an address below 0x80. If an address ends up there, the kernel flags it. That's the message you are seeing. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #111 from Alexandre Demers 2012-08-08 13:29:34 UTC --- (In reply to comment #110) > I just pushed a minor bugfix to mesa master, that in conjunction with Jeromes > kernel patch should eliminate the last VA issues. > > Please retest it again. > > Christian. You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. Do I still need to apply your previous patch also (attachment 65093)? I'll try it tonight, but it may take a bit more complicated to reproduce, I'll have to play for a while until it does or doesn't trigger the last reported vm error. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #110 from Christian K?nig 2012-08-08 10:48:35 UTC --- I just pushed a minor bugfix to mesa master, that in conjunction with Jeromes kernel patch should eliminate the last VA issues. Please retest it again. Christian. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #110 from Christian König deathsim...@vodafone.de 2012-08-08 10:48:35 UTC --- I just pushed a minor bugfix to mesa master, that in conjunction with Jeromes kernel patch should eliminate the last VA issues. Please retest it again. Christian. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #111 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-08 13:29:34 UTC --- (In reply to comment #110) I just pushed a minor bugfix to mesa master, that in conjunction with Jeromes kernel patch should eliminate the last VA issues. Please retest it again. Christian. You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. Do I still need to apply your previous patch also (attachment 65093)? I'll try it tonight, but it may take a bit more complicated to reproduce, I'll have to play for a while until it does or doesn't trigger the last reported vm error. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #112 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-09 01:38:41 UTC --- (In reply to comment #111) (In reply to comment #110) I just pushed a minor bugfix to mesa master, that in conjunction with Jeromes kernel patch should eliminate the last VA issues. Please retest it again. Christian. You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. Do I still need to apply your previous patch also (attachment 65093 [details] [review])? I'll try it tonight, but it may take a bit more complicated to reproduce, I'll have to play for a while until it does or doesn't trigger the last reported vm error. Well, I tested it with your previous patch on top of 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17 and it was not working properly. First, I had to modify your patch to apply on top of latest git. After applying it, compiling and installing, I rebooted and I was unable to load the logging screen. I removed the patch, rebuilt a clean mesa from 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17, installed and relaunched Xorg and... I was able to log in. So I'm now testing latest mesa (68bccc40f55aee7f4af8eb64b15a95f0b49d6a17) with kernel 3.6-rc1 + Jerome's patch. I should be able to tell you soon if it works. Meanwhile, if I should have applied something different, let me know. To Jerome: I could test your [PATCH] drm/radeon: delay virtual address destruction to bo destruction. But first, I want to make sure Christian's patch does what it should do. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #113 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-09 05:20:04 UTC --- (In reply to comment #112) (In reply to comment #111) (In reply to comment #110) I just pushed a minor bugfix to mesa master, that in conjunction with Jeromes kernel patch should eliminate the last VA issues. Please retest it again. Christian. You must be refering to commit 8c44e5a144009a03c20befa6468d19d41c802795. Do I still need to apply your previous patch also (attachment 65093 [details] [review] [review])? I'll try it tonight, but it may take a bit more complicated to reproduce, I'll have to play for a while until it does or doesn't trigger the last reported vm error. Well, I tested it with your previous patch on top of 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17 and it was not working properly. First, I had to modify your patch to apply on top of latest git. After applying it, compiling and installing, I rebooted and I was unable to load the logging screen. I removed the patch, rebuilt a clean mesa from 68bccc40f55aee7f4af8eb64b15a95f0b49d6a17, installed and relaunched Xorg and... I was able to log in. So I'm now testing latest mesa (68bccc40f55aee7f4af8eb64b15a95f0b49d6a17) with kernel 3.6-rc1 + Jerome's patch. I should be able to tell you soon if it works. Meanwhile, if I should have applied something different, let me know. To Jerome: I could test your [PATCH] drm/radeon: delay virtual address destruction to bo destruction. But first, I want to make sure Christian's patch does what it should do. Bug still there with latest mesa git (without your previous patch as explained previously). Aug 9 01:03:29 Xander kernel: [13308.165749] radeon :01:00.0: offset 0x40 is in reserved area 0x80 Aug 9 01:03:29 Xander kernel: [13308.232245] radeon :01:00.0: bo 880223646400 va 0x02B0 conflict with (bo 8801e3edc400 Locked and reset without any notice. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #109 from Alexandre Demers 2012-08-05 04:34:02 UTC --- (In reply to comment #108) > Oops, I've hit a va error again. I've been using my computer all day long, > going from one window to another, using Flash on Openstreetmap and Google Map. > The error could explain some lockups I've experienced. I hit the card's > maximum > memory from what I understand of the error. Should I put collected info here > or > under bug 53111? Here is the error message without any log for now. I'll wait to see if it should be tracked here: [54804.656571] radeon :01:00.0: offset 0x40 is in reserved area 0x80 [54805.166815] radeon :01:00.0: bo 8800c227d800 va 0x02B0 conflict with (bo 880202702400 0x0244 0x0344) [54805.177976] radeon :01:00.0: bo 8800c227b000 va 0x02C38000 conflict with (bo 880202702400 0x0244 0x0344) [54805.178980] radeon :01:00.0: bo 880061241400 va 0x02C38000 conflict with (bo 880202702400 0x0244 0x0344) [54805.253953] radeon :01:00.0: bo 88021b183800 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54806.900210] radeon :01:00.0: va above limit (0x00100200 > 0x0010) [54806.927121] radeon :01:00.0: va above limit (0x001000B0 > 0x0010) [54811.663812] radeon :01:00.0: bo 880223631c00 va 0x01278000 conflict with (bo 88020270b000 0x0120 0x0170) [54813.069082] radeon :01:00.0: bo 88021b183800 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54813.075691] radeon :01:00.0: bo 88007f002c00 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54813.075886] radeon :01:00.0: bo 88007f002000 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54813.075961] gnome-shell[1025]: segfault at 50 ip 7f8af5ebe019 sp 7fff80159650 error 4 in r600_dri.so[7f8af5e53000+4b1000] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #108 from Alexandre Demers 2012-08-05 04:29:39 UTC --- Oops, I've hit a va error again. I've been using my computer all day long, going from one window to another, using Flash on Openstreetmap and Google Map. The error could explain some lockups I've experienced. I hit the card's maximum memory from what I understand of the error. Should I put collected info here or under bug 53111? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 Alexandre Demers changed: What|Removed |Added Summary|[bisected] rendering|[bisected] rendering |regression since added |regression and va conflicts |support for virtual address |since added support for |space on cayman v11 |virtual address space on ||cayman v11 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #108 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-05 04:29:39 UTC --- Oops, I've hit a va error again. I've been using my computer all day long, going from one window to another, using Flash on Openstreetmap and Google Map. The error could explain some lockups I've experienced. I hit the card's maximum memory from what I understand of the error. Should I put collected info here or under bug 53111? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 --- Comment #109 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-05 04:34:02 UTC --- (In reply to comment #108) Oops, I've hit a va error again. I've been using my computer all day long, going from one window to another, using Flash on Openstreetmap and Google Map. The error could explain some lockups I've experienced. I hit the card's maximum memory from what I understand of the error. Should I put collected info here or under bug 53111? Here is the error message without any log for now. I'll wait to see if it should be tracked here: [54804.656571] radeon :01:00.0: offset 0x40 is in reserved area 0x80 [54805.166815] radeon :01:00.0: bo 8800c227d800 va 0x02B0 conflict with (bo 880202702400 0x0244 0x0344) [54805.177976] radeon :01:00.0: bo 8800c227b000 va 0x02C38000 conflict with (bo 880202702400 0x0244 0x0344) [54805.178980] radeon :01:00.0: bo 880061241400 va 0x02C38000 conflict with (bo 880202702400 0x0244 0x0344) [54805.253953] radeon :01:00.0: bo 88021b183800 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54806.900210] radeon :01:00.0: va above limit (0x00100200 0x0010) [54806.927121] radeon :01:00.0: va above limit (0x001000B0 0x0010) [54811.663812] radeon :01:00.0: bo 880223631c00 va 0x01278000 conflict with (bo 88020270b000 0x0120 0x0170) [54813.069082] radeon :01:00.0: bo 88021b183800 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54813.075691] radeon :01:00.0: bo 88007f002c00 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54813.075886] radeon :01:00.0: bo 88007f002000 va 0x0090 conflict with (bo 880fc000 0x0090 0x00901000) [54813.075961] gnome-shell[1025]: segfault at 50 ip 7f8af5ebe019 sp 7fff80159650 error 4 in r600_dri.so[7f8af5e53000+4b1000] -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 45018] [bisected] rendering regression and va conflicts since added support for virtual address space on cayman v11
https://bugs.freedesktop.org/show_bug.cgi?id=45018 Alexandre Demers alexandre.f.dem...@gmail.com changed: What|Removed |Added Summary|[bisected] rendering|[bisected] rendering |regression since added |regression and va conflicts |support for virtual address |since added support for |space on cayman v11 |virtual address space on ||cayman v11 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
