https://bugs.freedesktop.org/show_bug.cgi?id=49782
Bug #: 49782
Summary: libdrm 2.4.34 fails to build
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: vuntz(a)gnome.org
CCLD dristat
dristat.o: In function `drmWaitVBlank':
/home/abuild/rpmbuild/BUILD/libdrm-2.4.34/tests/../xf86drm.c:1947: undefined
reference to `clock_gettime'
/home/abuild/rpmbuild/BUILD/libdrm-2.4.34/tests/../xf86drm.c:1958: undefined
reference to `clock_gettime'
collect2: error: ld returned 1 exit status
make: *** [dristat] Error 1
My guess is that -lrt should be passed when linking.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=48599
Bug #: 48599
Summary: Fix compiler warnings in tests/radeon/radeon_ttm.c
Classification: Unclassified
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: vuntz(a)gnome.org
Created attachment 59852
--> https://bugs.freedesktop.org/attachment.cgi?id=59852
Fix compiler warnings in tests/radeon/radeon_ttm.c
The patch from openSUSE solves compiler warnings about use of implicit
declared-functions.
radeon_ttm.c: In function 'radeon_open_fd':
radeon_ttm.c:58:5: warning: implicit declaration of function 'drmOpen'
[-Wimplicit-function-declaration]
radeon_ttm.c: In function 'main':
radeon_ttm.c:73:5: warning: implicit declaration of function 'close'
[-Wimplicit-function-declaration]
radeon_ttm.c: At top level:
It was written by Jan Engelhardt <jengelh(a)medozas.de>
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=39534
Summary: failed tests
Product: DRI
Version: XOrg CVS
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: medium
Component: libdrm
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: guido(a)trentalancia.com
Created an attachment (id=49548)
View: https://bugs.freedesktop.org/attachment.cgi?id=49548
Review: https://bugs.freedesktop.org/review?bug=39534&attachment=49548
Patch to fix udev tests on Intel (when there is actually no Intel drm)
In libdrm from git and latest release (2.4.26), there are some tests that fail:
PASS: openclose
PASS: getversion
PASS: getclient
PASS: getstats
lt-setversion: drmtest.c:46: is_master: Assertion `ret == 0' failed.
/bin/sh: line 5: 382 Aborted ${dir}$tst
FAIL: setversion
lt-updatedraw: drmtest.c:46: is_master: Assertion `ret == 0' failed.
/bin/sh: line 5: 411 Aborted ${dir}$tst
FAIL: updatedraw
PASS: name_from_fd
/bin/sh: line 5: 457 Segmentation fault ${dir}$tst
FAIL: gem_basic
/bin/sh: line 5: 484 Segmentation fault ${dir}$tst
FAIL: gem_flink
/bin/sh: line 5: 510 Segmentation fault ${dir}$tst
FAIL: gem_readwrite
/bin/sh: line 5: 534 Segmentation fault ${dir}$tst
FAIL: gem_mmap
Starting program: /usr/src/libdrm-2.4.26/tests/.libs/gem_basic
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV, Segmentation fault.
0x000000000040115e in drm_open_matching (pci_glob=0x4014ba "8086:*", flags=0)
at drmtest.c:82
82 if (strcmp(udev_device_get_subsystem(parent), "pci") != 0)
(gdb) where
#0 0x000000000040115e in drm_open_matching (pci_glob=0x4014ba "8086:*",
flags=0) at drmtest.c:82
#1 0x0000000000400f73 in main (argc=1, argv=0x7fffffffe298) at gem_basic.c:91
(gdb) print parent
$1 = (struct udev_device *) 0x0
Something should be done to skip certain udev function calls when parent is
NULL.
See attached patch (which works for both 2.4.26 and git). It avoids the
segmentation fault but perhaps, it produces a false positive, I am not sure:
PASS: gem_basic
failed to open intel drm device, skipping
PASS: gem_flink
failed to open intel drm device, skipping
PASS: gem_readwrite
failed to open intel drm device, skipping
PASS: gem_mmap
I have no Intel drm device. I have a Nouveau device. If I disable Intel drm
from build by proper configure options, such tests are automatically skipped
(but Intel is built by default and it's not easy to figure out what's going in
the current situation).
You can always modify the patch to behave slightly different if such tests
should fail.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=35721
Summary: Tests should be always in the check_* target
Product: DRI
Version: XOrg CVS
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: lu_zero(a)gentoo.org
Created an attachment (id=44919)
--> (https://bugs.freedesktop.org/attachment.cgi?id=44919)
Move the test programs from noinst to check
Right now trying to build libdrm w/out cairo fails unexpectedly:
libdrm-9999/tests/modetest/modetest.c:58:19: fatal error: cairo.h: No such file
or directory
I noticed that the tests subdirs have some tests built unconditionally.
The patch partially fixes that
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=77953
Priority: medium
Bug ID: 77953
Assignee: dri-devel(a)lists.freedesktop.org
Summary: i915 Gallium crashes on 2nd generation i3/5/7 card,
and a Weston egl client
Severity: normal
Classification: Unclassified
OS: All
Reporter: nerdopolis1(a)verizon.net
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/i915g
Product: Mesa
It seems that I am getting a crash on egl Wayland clients when I compile mesa
with ilo support.
I have a bt if it's helpful.
I'm realizing I should probably turn off ilo support in my buildscript as it's
too early, but I hope this report is helpful
#0 malloc_consolidate (av=av@entry=0xb7f2c420 <main_arena>) at
malloc.c:4146
#1 0xb7df62d9 in _int_malloc (av=av@entry=0xb7f2c420 <main_arena>,
bytes=bytes@entry=131008) at malloc.c:3423
#2 0xb7df8248 in __GI___libc_malloc (bytes=131008) at malloc.c:2891
#3 0xb7009848 in drm_intel_setup_reloc_list (bo=0x8062288)
at intel_bufmgr_gem.c:552
#4 do_bo_emit_reloc (bo=0x8062288, offset=32452, target_bo=0x80b1168,
target_offset=0, read_domains=2, write_domain=2, need_fence=false)
at intel_bufmgr_gem.c:1679
#5 0xb7006648 in drm_intel_bo_emit_reloc (bo=0x8062288, offset=32452,
target_bo=0x80b1168, target_offset=0, read_domains=2, write_domain=2)
at intel_bufmgr.c:181
#6 0xb74b2e28 in intel_bo_add_reloc ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#7 0xb74b9088 in gen6_pipeline_states ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#8 0xb74c2acc in gen6_pipeline_draw ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#9 0xb74c2b62 in ilo_3d_pipeline_emit_draw_gen6 ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#10 0xb74b5658 in ilo_3d_pipeline_emit_draw ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#11 0xb74b509b in ilo_draw_vbo ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#12 0xb71d6a8f in blitter_draw ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#13 0xb71d6dfb in util_blitter_clear_custom.constprop ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#14 0xb74cdede in ilo_blitter_pipe_clear_fb ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#15 0xb74cad4a in ilo_clear () from
/opt/lib/i386-linux-gnu/egl/egl_gallium.so
#16 0xb73cfd3c in st_Clear () from
/opt/lib/i386-linux-gnu/egl/egl_gallium.so
#17 0xb72d0753 in _mesa_Clear ()
from /opt/lib/i386-linux-gnu/egl/egl_gallium.so
#18 0x08049eb6 in redraw (callback=0x0, time=0, data=0xbfffed4c)
at clients/simple-egl.c:450
#19 main (argc=<optimized out>, argv=0xbffff2c4) at
clients/simple-egl.c:822
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76044
Priority: medium
Bug ID: 76044
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [i915g+llvm] commit "gallium: Use C11 thread
abstractions." breaks memento by conspiracy
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: cme3000(a)gmail.com
Hardware: x86 (IA32)
Status: NEW
Version: git
Component: Drivers/Gallium/i915g
Product: Mesa
This commit breaks the intro memento by conspiracy
(http://www.pouet.net/prod.php?which=24472).
Backtrace with git-3330dec:
glretrace: i915_prim_vbuf.c:477: draw_arrays_fallback: Assertion `0' failed.
Program received signal SIGABRT, Aborted.
0xb7fde424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7fde424 in __kernel_vsyscall ()
#1 0xb7b664d6 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0xb7b69853 in __GI_abort () at abort.c:89
#3 0xb7b5f857 in __assert_fail_base (fmt=0xb7c9a554 "%s%s%s:%u: %s%sAssertion
`%s' failed.\n%n", assertion=assertion@entry=0xb7693f8a "0",
file=file@entry=0xb775f5b3 "i915_prim_vbuf.c", line=line@entry=477,
function=function@entry=0xb775f6ea <__PRETTY_FUNCTION__.9215>
"draw_arrays_fallback") at assert.c:92
#4 0xb7b5f907 in __GI___assert_fail (assertion=assertion@entry=0xb7693f8a "0",
file=file@entry=0xb775f5b3 "i915_prim_vbuf.c", line=477, function=0xb775f6ea
<__PRETTY_FUNCTION__.9215> "draw_arrays_fallback") at assert.c:101
#5 0xb7638d65 in draw_arrays_fallback (nr=<optimized out>, start=<optimized
out>, render=<optimized out>) at i915_prim_vbuf.c:477
#6 i915_vbuf_render_draw_arrays (render=0x83a0ff0, start=<optimized out>,
nr=4092) at i915_prim_vbuf.c:503
#7 0xb7417cf1 in draw_pt_emit_linear (emit=0x83a1cc0, vert_info=0xbfffeff0,
prim_info=0xbffff020) at draw/draw_pt_emit.c:258
#8 0xb75eee7d in emit (prim_info=0xbffff020, vert_info=0xbfffeff0, emit={void
(const struct draw_prim_info *, const struct draw_vertex_info *, struct pt_emit
*)} 0xb75eedd3 <llvm_middle_end_linear_run+883>) at
draw/draw_pt_fetch_shade_pipeline_llvm.c:336
#9 llvm_pipeline_generic (in_prim_info=0xbffff020, fetch_info=0x0,
middle=0x83ec5a0) at draw/draw_pt_fetch_shade_pipeline_llvm.c:468
#10 llvm_middle_end_linear_run (middle=0x83ec5a0, start=0, count=4092,
prim_flags=0) at draw/draw_pt_fetch_shade_pipeline_llvm.c:532
#11 0xb74207a0 in vsplit_segment_simple_linear (vsplit=0x83d6f90, icount=4092,
istart=0, flags=0) at draw/draw_pt_vsplit_tmp.h:240
#12 vsplit_run_linear (frontend=0x83d6f90, start=0, count=4092) at
draw/draw_split_tmp.h:60
#13 0xb7416fb7 in draw_pt_arrays (draw=draw@entry=0x840c650, prim=7, start=0,
count=count@entry=4092) at draw/draw_pt.c:149
#14 0xb741744a in draw_vbo (draw=0x840c650, info=0xbffff1d0,
info@entry=0xbffff2c0) at draw/draw_pt.c:562
#15 0xb762c98e in i915_draw_vbo (pipe=0x83ebc38, info=0xbffff2c0) at
i915_context.c:103
#16 0xb73ff258 in cso_draw_vbo (cso=0x8408db0, info=info@entry=0xbffff2c0) at
cso_cache/cso_context.c:1400
#17 0xb72d7690 in st_draw_vbo (ctx=0x84b7390, prims=0x84052b4, nr_prims=2,
ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=4095,
tfb_vertcount=0x0, indirect=0x0) at state_tracker/st_draw.c:286
#18 0xb72a238f in vbo_exec_vtx_flush (exec=exec@entry=0x8404f04,
keepUnmapped=keepUnmapped@entry=0 '\000') at vbo/vbo_exec_draw.c:409
#19 0xb728d55c in vbo_exec_wrap_buffers (exec=0x8404f04) at
vbo/vbo_exec_api.c:89
#20 vbo_exec_vtx_wrap (exec=0x8404f04) at vbo/vbo_exec_api.c:124
#21 0x080b5396 in _glVertex2f(float, float) ()
#22 0x080f9681 in retrace_glVertex2f(trace::Call&) ()
#23 0x0806ce8e in retrace::Retracer::retrace(trace::Call&) ()
#24 0x08063d37 in retrace::retraceCall(trace::Call*) ()
#25 0x08065994 in retrace::RelayRunner::runLeg(trace::Call*) ()
#26 0x0806587c in retrace::RelayRunner::runRace() ()
#27 0x08064053 in retrace::RelayRace::run() ()
#28 0x0806420f in retrace::mainLoop() ()
#29 0x08064985 in main ()
$ git bisect bad
fd33a6bcd7f1271e80332379131e82e00fe10586 is the first bad commit
commit fd33a6bcd7f1271e80332379131e82e00fe10586
Author: José Fonseca <jfonseca(a)vmware.com>
Date: Fri Apr 26 08:03:33 2013 +0100
gallium: Use C11 thread abstractions.
Note that PIPE_ROUTINE now returns an int.
Reviewed-by: Brian Paul <brianp(a)vmware.com>
Reviewed-by: Chad Versace <chad.versace(a)linux.intel.com>
:040000 040000 dec5215b27af2e3f703e701e323dd5fdeba072eb
a8b06eaa9746db86fa603a657a7b6a5dcd9e3633 M src
Reverting this commit on top of master fixes this crash.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=44342
Bug #: 44342
Summary: [i915g] GPU hang when running Khronos Webgl test suite
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
URL: https://cvs.khronos.org/svn/repos/registry/trunk/publi
c/webgl/sdk/tests/webgl-conformance-tests.html
OS/Version: All
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/i915g
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: pavel.ondracka(a)email.cz
Created attachment 54998
--> https://bugs.freedesktop.org/attachment.cgi?id=54998
terminal output and backtrace
When running Khronos Webgl test suite there is an occasional crash and gpu
hang. This is not 100% reproducible with one test, sometimes it finishes whole
test run OK, sometimes it hangs really fast. Running glsl functions subtests
few time is a row reproduces it here always.
[ 534.984024] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed...
GPU hung
[ 534.984036] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[ 534.987135] [drm:i915_reset] *ERROR* Failed to reset chip.
from terminal, full output and backtrace attached:
i915_drm_batchbuffer.c:187:i915_drm_batchbuffer_flush: Assertion `ret == 0'
failed.
Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
OpenGL renderer string: Gallium 0.4 on i915 (chipset: 945G)
OpenGL version string: 2.0 Mesa 7.12-devel (git-99fbf7c)
Kernel: 3.1.6-1.fc16.i686
xf86-video-intel: 0dc5c0651cb691fb8811cdf3075b3d322f9d37f8 (with SNA enabled)
X.Org X Server 1.11.3
Firefox: 9.0.1
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.