https://bugs.freedesktop.org/show_bug.cgi?id=72425
Priority: medium
Bug ID: 72425
Assignee: dri-devel(a)lists.freedesktop.org
Summary: divide by zero error in radeon_surface.c when opening
chrome with WebGL enabled
Severity: normal
Classification: Unclassified
OS: All
Reporter: crwulff(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
…
[View More]Component: libdrm
Product: DRI
Created attachment 90384
--> https://bugs.freedesktop.org/attachment.cgi?id=90384&action=edit
Fix divide by zero in radeon_surface
Passing a tile_split of zero to eg_surface_init_2d causes a divide by zero
error. Launching chromium with WebGL enabled on a AMD Llano (A8-3850) exhibits
this behavior and webgl then fails to work. The attached patch fixes the
problem and allows WebGL to work in chrome on this platform.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=66332
Priority: medium
Bug ID: 66332
Assignee: dri-devel(a)lists.freedesktop.org
Summary: drmHandleEvent returns 0 on read() failure
Severity: normal
Classification: Unclassified
OS: All
Reporter: mgold(a)qnx.com
Hardware: All
Status: NEW
Version: XOrg CVS
Component: libdrm
Product: DRI
drmHandleEvent contains this …
[View More]code:
len = read(fd, buffer, sizeof buffer);
if (len == 0)
return 0;
if (len < sizeof *e)
return -1;
In the (len < sizeof *e) check, len gets promoted to size_t (which is
unsigned); so when len is negative "return -1" won't be executed. Instead, the
function continues to the end and returns 0. (The documentation states
drmHandleEvent will return -1 if the read fails.)
If there's an error like EBADF, the caller won't detect it and might end up
busy-waiting. Rewriting the condition as (len < (int)(sizeof *e)) will fix
this.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=61269
Priority: medium
Bug ID: 61269
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Support libkms on FreeBSD
Severity: normal
Classification: Unclassified
OS: FreeBSD
Reporter: bugzilla(a)tecnocode.co.uk
Hardware: All
Status: NEW
Version: XOrg CVS
Component: libdrm
Product: DRI
Created attachment 75298
--&…
[View More]gt; https://bugs.freedesktop.org/attachment.cgi?id=75298&action=edit
Fix detection of Intel-style atomic primitives on amd64 (patch by Brian Waters)
Series of 3 patches coming up which allow libdrm to be compiled with KMS
support on FreeBSD.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
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 …
[View More]`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.
[View Less]
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 …
[View More]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.
[View Less]
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: …
[View More]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.
[View Less]
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/…
[View More]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.
[View Less]