https://bugzilla.kernel.org/show_bug.cgi?id=29022
--- Comment #9 from Marc Koschewski <marc(a)osknowledge.org> 2011-03-06 11:42:29 ---
I updated the whole X11 stuff to current git and the problem seems to be gone.
I have the freezing kernel running for about 15 minutes now and tried anything
to make it freeze (composite WM, Firefox, several glxgears instances and
fullscreen terminals just doing some stuff to make it print a lot of text (like
cat'ing dmesg in loops)). Weird.
... …
[View More]but the workaround cannot be to upgrade X11 to HEAD. :)
Any hints on what one could do to track this down?
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=26852
Matt Turner <mattst88(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mattst88(a)gmail.com
--- Comment #9 from Matt Turner <mattst88(a)gmail.com> 2011-03-05 18:07:50 PST ---
(In reply to comment #8)
> (In reply to comment #7)
> > Ping? As described in the initial …
[View More]report, there's no reason to prefer system
> > headers over those in the same source… I don't understand Sérgio's objection (I
> > fail to see what's illogical).
>
> The illogical is, without that depending on kernel, you may try compile very
> new libdrm with a older kernel.
> libdrm-2.4.21 needs kms on kernel but kernel <= 2.6.26 don't have it.
>
> my 2 cents
I think you're failing to understand the issue.
xf86drm.h is provided by libdrm. libkms (which is part of libdrm) uses
xf86drm.h, but the Makefile searches in /usr/include instead of the $(top_src)
directory, where libdrm's xf86drm.h is.
This is like if you have a library that consists of lib.c and lib.h, where
lib.c includes lib.h. The Makefile would be incorrect in using lib.h found in
/usr/include over the lib.h in the same folder as lib.c.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=26852
--- Comment #8 from Sérgio M. B. <sergio(a)sergiomb.no-ip.org> 2011-03-05 17:28:01 PST ---
(In reply to comment #7)
> Ping? As described in the initial report, there's no reason to prefer system
> headers over those in the same source… I don't understand Sérgio's objection (I
> fail to see what's illogical).
The illogical is, without that depending on kernel, you may try compile very
new libdrm with a older kernel.
libdrm-2.4.…
[View More]21 needs kms on kernel but kernel <= 2.6.26 don't have it.
my 2 cents
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
Signed-off-by: Cyril Brulebois <kibi(a)debian.org>
---
configure.ac | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
dri-devel-bounces(a)lists.sourceforge.net told me to only send mail to the
new address, so I'll be sending my other patches again in a second.
diff --git a/configure.ac b/configure.ac
index 1998204..8e1d19d 100644
--- a/configure.ac
+++ b/configure.ac
@@ -19,7 +19,7 @@
# CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
AC_PREREQ(…
[View More]2.60)
-AC_INIT([libdrm], 2.4.24, [dri-devel(a)lists.sourceforge.net], libdrm)
+AC_INIT([libdrm], 2.4.24, [dri-devel(a)lists.freedesktop.org], libdrm)
AC_USE_SYSTEM_EXTENSIONS
AC_CONFIG_SRCDIR([Makefile.am])
AM_INIT_AUTOMAKE([dist-bzip2])
--
1.7.4.1
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=26852
Cyril Brulebois <kibi(a)debian.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kibi(a)debian.org
--- Comment #7 from Cyril Brulebois <kibi(a)debian.org> 2011-03-05 10:10:11 PST ---
Ping? As described in the initial report, there's no reason to prefer system
headers over those in the …
[View More]same source… I don't understand Sérgio's objection (I
fail to see what's illogical).
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=29363
Summary: [r300g] Starcraft 2: "r300 VP: Compiler error"
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: drakkk(a)centrum.cz
Created an attachment (id=37527)
--> (https://bugs.freedesktop.org/…
[View More]attachment.cgi?id=37527)
terminal output
When running with Wine 1.3.0 patched with slightly modified hack from bug
29137, I'm now able to start Starcraft 2, menus are working OK, however in game
almost everything is black.
mesa: afa925066c158ac49e3b0f883f67debd8545bf26
GPU: RV530
kernel: 2.6.35
Some chosen terminal output, full log attached:
r300 VP: Compiler error:
Vertex program has too many instructions
Using a dummy shader instead.
If there's an 'unknown opcode' message, please file a bug report and attach
this log.
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader #27:
fixme:d3d_shader:print_glsl_info_log Note: 'for (tmpInt0 ... )' body is too
large/complex to unroll
I'm not sure if this is only r300g bug, because some users with intel graphic
cards reported similar issues at Wine bugzilla,
http://bugs.winehq.org/show_bug.cgi?id=22971.
BTW disabling use of GLSL in Wine allows the terrain to be displayed more or
less properly, however units and buildings are still invisible
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=29022
Lucas Stach <dev(a)lynxeye.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dev(a)lynxeye.de
--- Comment #8 from Lucas Stach <dev(a)lynxeye.de> 2011-03-05 10:16:01 ---
If this problem occurs on a NVA8 it's not an regression. NVA3+ have some random
lockups where nobody figured out why.…
[View More] So it never worked okay, although some
changes in the codebase could have made it more likely to trigger the lockup.
I strongly suspect the PGRAPH_TRAP is a unrelated bug, since we never saw
anything in the logs after random lockup.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[View Less]
https://bugzilla.kernel.org/show_bug.cgi?id=29022
Marc <marc(a)osknowledge.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[REGRESSION? 2.6.38-rc4] |[REGRESSION? 2.6.38-rc4]
|nouveau NV50 screen freeze |nouveau NV50/NVA8 screen
| |freeze
--- Comment #7 from Marc <marc(a)osknowledge.org> 2011-…
[View More]03-05 09:55:56 ---
Hey, we have somthing in the logs:
Mar 5 09:57:44 marc kernel: [71218.224538] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar 5 09:57:44 marc kernel: [71218.224554] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar 5 09:57:44 marc kernel: [71218.224705] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar 5 09:57:44 marc kernel: [71218.224717] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar 5 09:57:44 marc kernel: [71218.224726] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 083008 warp 1, opcode
00f8f3e6 00f8f3e6
Mar 5 09:57:44 marc kernel: [71218.224899] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar 5 09:57:44 marc kernel: [71218.224911] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar 5 09:57:44 marc kernel: [71218.224921] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 083008 warp 1, opcode
00f8f3e6 00f8f3e6
Mar 5 09:57:44 marc kernel: [71218.224992] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar 5 09:57:44 marc kernel: [71218.225003] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 0: INVALID_OPCODE at 080000 warp 0, opcode
000033cc 00ffffff
Mar 5 09:57:44 marc kernel: [71218.225013] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP_EXEC - TP 0 MP 1: INVALID_OPCODE at 083008 warp 1, opcode
00f8f3e6 00f8f3e6
Mar 5 09:57:44 marc kernel: [71218.225162] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP - Ch 4/5 Class 0x8597 Mthd 0x15e0 Data 0x00000000:0x00000000
Mar 5 09:57:44 marc kernel: [71218.225168] [drm] nouveau 0000:01:00.0:
PGRAPH_TRAP_MP - TP0: Unhandled ustatus 0x00020000
Mar 5 09:58:11 marc kernel: [71246.831804] [drm] nouveau 0000:01:00.0:
nouveau_channel_free: freeing fifo 4
Mar 5 09:58:24 marc kernel: [71259.463319] [drm] nouveau 0000:01:00.0:
Allocating FIFO number 4
Mar 5 09:58:24 marc kernel: [71259.473828] [drm] nouveau 0000:01:00.0:
nouveau_channel_alloc: initialised FIFO 4
This, however, seems to be something different. When I reported the bug there
were no such logs. Maybe they just didn't get into kern.log or there are two
bugs.
If you need more info on something, please ask.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
[View Less]