dri-devel February 2014

dri-devel@lists.freedesktop.org

154 participants
967 discussions

[PATCH] dma-buf: update debugfs output
by Sumit Semwal 03 Feb '14

03 Feb '14

Russell King observed 'wierd' looking output from debugfs, and also suggested better ways of getting device names (use KBUILD_MODNAME, dev_name()) This patch addresses these issues to make the debugfs output correct and better looking. Signed-off-by: Sumit Semwal <sumit.semwal(a)linaro.org> --- drivers/base/dma-buf.c | 18 ++++++++---------- include/linux/dma-buf.h | 2 +- 2 files changed, 9 insertions(+), 11 deletions(-) diff --git a/drivers/base/dma-buf.c b/drivers/base/dma-buf.c index cfe1d8b..bf89fe3 100644 --- a/drivers/base/dma-buf.c +++ b/drivers/base/dma-buf.c @@ -621,7 +621,7 @@ static int dma_buf_describe(struct seq_file *s) return ret; seq_printf(s, "\nDma-buf Objects:\n"); - seq_printf(s, "\texp_name\tsize\tflags\tmode\tcount\n"); + seq_printf(s, "size\tflags\tmode\tcount\texp_name\n"); list_for_each_entry(buf_obj, &db_list.head, list_node) { ret = mutex_lock_interruptible(&buf_obj->lock); @@ -632,24 +632,22 @@ static int dma_buf_describe(struct seq_file *s) continue; } - seq_printf(s, "\t"); - - seq_printf(s, "\t%s\t%08zu\t%08x\t%08x\t%08ld\n", - buf_obj->exp_name, buf_obj->size, + seq_printf(s, "%08zu\t%08x\t%08x\t%08ld\t%s\n", + buf_obj->size, buf_obj->file->f_flags, buf_obj->file->f_mode, - (long)(buf_obj->file->f_count.counter)); + (long)(buf_obj->file->f_count.counter), buf_obj->exp_name); - seq_printf(s, "\t\tAttached Devices:\n"); + seq_printf(s, "\tAttached Devices:\n"); attach_count = 0; list_for_each_entry(attach_obj, &buf_obj->attachments, node) { - seq_printf(s, "\t\t"); + seq_printf(s, "\t"); - seq_printf(s, "%s\n", attach_obj->dev->init_name); + seq_printf(s, "%s\n", dev_name(attach_obj->dev)); attach_count++; } - seq_printf(s, "\n\t\tTotal %d devices attached\n", + seq_printf(s, "\nTotal %d devices attached\n", attach_count); count++; diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h index dfac5ed..f886985 100644 --- a/include/linux/dma-buf.h +++ b/include/linux/dma-buf.h @@ -171,7 +171,7 @@ struct dma_buf *dma_buf_export_named(void *priv, const struct dma_buf_ops *ops, size_t size, int flags, const char *); #define dma_buf_export(priv, ops, size, flags) \ - dma_buf_export_named(priv, ops, size, flags, __FILE__) + dma_buf_export_named(priv, ops, size, flags, KBUILD_MODNAME) int dma_buf_fd(struct dma_buf *dmabuf, int flags); struct dma_buf *dma_buf_get(int fd); -- 1.8.3.2

1 0

[Bug 74428] System crashes from Counter-strike: Source
by bugzilla-daemon＠freedesktop.org 03 Feb '14

03 Feb '14

1 0

[Bug 73418] New: OpenCL hangs graphics on CAYMAN
by bugzilla-daemon＠freedesktop.org 03 Feb '14

03 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=73418 Priority: medium Bug ID: 73418 Assignee: dri-devel(a)lists.freedesktop.org Summary: OpenCL hangs graphics on CAYMAN Severity: normal Classification: Unclassified OS: All Reporter: v10lator(a)myway.de Hardware: Other Status: NEW Version: 10.0 Component: Drivers/DRI/R600 Product: Mesa Created attachment 91722 --> https://bugs.freedesktop.org/attachment.cgi?id=91722&action=edit dmesg snippet from mesa 10.0.1 When I try to run some OpenCL code from within X the screen freezes, goes black, goes on again while still frozen, ... this repeats a few times till it won't come back again and all I have left is my monitor in standby and my keyboard not reacting to any input. When I try to run some OpenCL code from a console (Cntrl + Alt + F1) and go back to X while the OpenCL code is still running it's the same as above. When I try to run some OpenCL code from a console and go back to X after the OpenCL code is finished I have a black monitor with my mouse cursor (I'm even able to move it) for a few seconds, then my desktop is back. While it produces the black screen (with mouse cursor) there's also GPU hang logged to dmesg. Reproducable with bfgminer or the tests from http://cgit.freedesktop.org/~tstellar/opencl-example/ with mesa 10.0.1 as well as 10.1 (git-646c16a). -- You are receiving this mail because: You are the assignee for the bug.

1 12

[PATCH] drm/gma500: remove stub .open/postclose
by David Herrmann 02 Feb '14

02 Feb '14

These are unused and can safely be dropped. DRM core verifies they're non-NULL before it calls them. Cc: Patrik Jakobsson <patrik.r.jakobsson(a)gmail.com> Signed-off-by: David Herrmann <dh.herrmann(a)gmail.com> --- drivers/gpu/drm/gma500/psb_drv.c | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/drivers/gpu/drm/gma500/psb_drv.c b/drivers/gpu/drm/gma500/psb_drv.c index 1199180..d224503 100644 --- a/drivers/gpu/drm/gma500/psb_drv.c +++ b/drivers/gpu/drm/gma500/psb_drv.c @@ -588,15 +588,6 @@ static int psb_stolen_memory_ioctl(struct drm_device *dev, void *data, return 0; } -static int psb_driver_open(struct drm_device *dev, struct drm_file *priv) -{ - return 0; -} - -static void psb_driver_close(struct drm_device *dev, struct drm_file *priv) -{ -} - static long psb_unlocked_ioctl(struct file *filp, unsigned int cmd, unsigned long arg) { @@ -672,9 +663,7 @@ static struct drm_driver driver = { .disable_vblank = psb_disable_vblank, .get_vblank_counter = psb_get_vblank_counter, .lastclose = psb_lastclose, - .open = psb_driver_open, .preclose = psb_driver_preclose, - .postclose = psb_driver_close, .gem_free_object = psb_gem_free_object, .gem_vm_ops = &psb_gem_vm_ops, -- 1.8.5.3

2 1

[Bug 70706] Regression in fbconfig
by bugzilla-daemon＠freedesktop.org 01 Feb '14

01 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=70706 --- Comment #15 from Stefan Brüns <stefan.bruens(a)rwth-aachen.de> --- openSUSE ships a xorg config file in the glamor package: $> cat /etc/X11/xorg.conf.d/05-glamor.conf Section "Module" Load "dri2" Load "glamoregl" EndSection --- I think this was a workaround to get correct GL symbol tables. As the GL loader has changed with xserver 1.15 this is probably no longer needed. Commenting out (#) the two Load commands fixed this for me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 71448] New: [UVD] qvdpautest is very slow on radeonsi (HD 7950)
by bugzilla-daemon＠freedesktop.org 01 Feb '14

01 Feb '14

https://bugs.freedesktop.org/show_bug.cgi?id=71448 Priority: medium Bug ID: 71448 Assignee: dri-devel(a)lists.freedesktop.org Summary: [UVD] qvdpautest is very slow on radeonsi (HD 7950) Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI http://bpaste.net/show/148239/ kernel is 3.13 (~agd5f drm-next-3.13). The whole graphic stack is from git except xorg-server which is 1.14.3. -- You are receiving this mail because: You are the assignee for the bug.

1 40

[Bug 67571] New: BUG: unable to handle kernel paging in amd E350 hdmi init
by bugzilla-daemon＠bugzilla.kernel.org 01 Feb '14

01 Feb '14

https://bugzilla.kernel.org/show_bug.cgi?id=67571 Bug ID: 67571 Summary: BUG: unable to handle kernel paging in amd E350 hdmi init Product: Drivers Version: 2.5 Kernel Version: 3.13.0-rc5 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: eric.valette(a)free.fr Regression: No Created attachment 119351 --> https://bugzilla.kernel.org/attachment.cgi?id=119351&action=edit complete dmesg Here is an extract of the dmeg log. We are several to be bitten by the same bug as described here: http://forum.xbmc.org/showthread.php?tid=174854&pid=1577781#pid1577781 [drm] Found smc ucode version: 0x00010200 [ 40.117359] BUG: unable to handle kernel paging request at ffffec2000000900 [ 40.117377] IP: [<ffffffff810a796f>] kfree+0x41/0xe2 [ 40.117396] PGD 0 [ 40.117404] Oops: 0000 [#1] PREEMPT SMP [ 40.117413] Modules linked in: radeon cfbfillrect cfbimgblt cfbcopyarea i2c_algo_bit backlight drm_kms_helper ttm drm fb fbdev [ 40.117445] CPU: 1 PID: 3029 Comm: Xorg Not tainted 3.13.0-rc5 #6 [ 40.117454] Hardware name: To be filled by O.E.M. To be filled by O.E.M./Inagua CRB, BIOS 4.6.4 06/15/2011 [ 40.117463] task: ffff88013ba5f2c0 ti: ffff88009d1ce000 task.ti: ffff88009d1ce000 [ 40.117470] RIP: 0010:[<ffffffff810a796f>] [<ffffffff810a796f>] kfree+0x41/0xe2 [ 40.117484] RSP: 0018:ffff88009d1cfa40 EFLAGS: 00010286 [ 40.117492] RAX: ffffea0000000000 RBX: 0000100000024414 RCX: 0000000000000000 [ 40.117499] RDX: 0000000000010005 RSI: 0000000000005f78 RDI: 0000100000024414 [ 40.117505] RBP: 0000000000000c00 R08: ffffec2000000900 R09: 0000000000000c00 [ 40.117512] R10: ffffffffa00a7da5 R11: ffffffffa00a7f08 R12: ffff8800a2c01200 [ 40.117518] R13: ffff88013b298000 R14: 0000000000000000 R15: ffff88013aaa6b00 [ 40.117526] FS: 00007f94df8fe980(0000) GS:ffff88013fd00000(0000) knlGS:0000000000000000 [ 40.117533] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 40.117539] CR2: ffffec2000000900 CR3: 00000000a36e3000 CR4: 00000000000007e0 [ 40.117544] Stack: [ 40.117549] ffff88013b298000 ffffffffa00f11e2 00007c44a00f62be 00007d2c00007c48 [ 40.117559] ffff8800a2c01200 0000000000000003 0000000000000000 ffffffffa01750b1 [ 40.117569] 0000100000024414 0000188000024414 0000180000028488 ffffffff00024414 [ 40.117579] Call Trace: [ 40.117686] [<ffffffffa00f11e2>] ? evergreen_hdmi_setmode+0x3cc/0x7e1 [radeon] [ 40.117705] [<ffffffffa0071732>] ? drm_crtc_helper_set_mode+0x30a/0x40a [drm_kms_helper] [ 40.117726] [<ffffffffa007248c>] ? drm_crtc_helper_set_config+0x5ff/0x842 [drm_kms_helper] [ 40.117798] [<ffffffffa00b4392>] ? radeon_crtc_set_config+0x41/0xe8 [radeon] [ 40.117843] [<ffffffffa001d3e7>] ? drm_mode_set_config_internal+0x44/0xac [drm] [ 40.117885] [<ffffffffa001f8cb>] ? drm_mode_setcrtc+0x3e8/0x499 [drm] [ 40.117917] [<ffffffffa00148b3>] ? drm_ioctl+0x26f/0x394 [drm] [ 40.117957] [<ffffffffa001f4e3>] ? drm_mode_setplane+0x335/0x335 [drm] [ 40.118015] [<ffffffffa0096045>] ? radeon_drm_ioctl+0x45/0x77 [radeon] [ 40.118028] [<ffffffff810b962a>] ? do_vfs_ioctl+0x356/0x421 [ 40.118039] [<ffffffff810b9743>] ? SyS_ioctl+0x4e/0x7b [ 40.118054] [<ffffffff8147a322>] ? system_call_fastpath+0x16/0x1b [ 40.118059] Code: 00 00 00 80 ff 77 00 00 49 01 f8 48 0f 42 05 b9 86 96 00 49 01 c0 48 b8 00 00 00 00 00 ea ff ff 49 c1 e8 0c 49 c1 e0 06 49 01 c0 <49> 8b 00 f6 c4 80 74 04 4d 8b 40 30 49 8b 00 a8 80 75 22 49 f7 [ 40.118149] RIP [<ffffffff810a796f>] kfree+0x41/0xe2 [ 40.118160] RSP <ffff88009d1cfa40> [ 40.118165] CR2: ffffec2000000900 [ 40.118173] ---[ end trace e7d41f7cbae99794 ]--- -- You are receiving this mail because: You are watching the assignee of the bug.

1 19

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2014