radeon regression 3.11.0-rc2+

On 07/24/2013 04:24 PM, Alex Deucher wrote: > On Tue, Jul 23, 2013 at 6:22 PM, Antti Palosaari wrote: >> Hello >> I just upgraded Kernel from 3.10.0-rc6+ to 3.11.0-rc2+ and ran serious >> problems. That Kernel is current Linux Media master, which contains some >> upcoming media stuff that should

[Bug 67276] kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD)

bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/073e1e3e/attachment.html>

[Bug 67276] kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD)

ttp://lists.freedesktop.org/archives/dri-devel/attachments/20130724/14bf1da7/attachment.html>

[Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/15c25bc5/attachment-0001.html>

[PATCH v5 4/4] drm/vma: provide drm_vma_node_unmap() helper

Instead of unmapping the nodes in TTM and GEM users manually, we provide a generic wrapper which does the correct thing for all vma-nodes. v2: remove bdev->dev_mapping test in ttm_bo_unmap_virtual_unlocked() as ttm_mem_io_free_vm() does nothing in that case (io_reserved_vm is 0). v4: Fix docbook

[PATCH v5 3/4] drm/ttm: convert to unified vma offset manager

Use the new vma-manager infrastructure. This doesn't change any implementation details as the vma-offset-manager is nearly copied 1-to-1 from TTM. The vm_lock is moved into the offset manager so we can drop it from TTM. During lookup, we use the vma locking helpers to take a reference to the

[PATCH v5 2/4] drm/gem: convert to new unified vma manager

Use the new vma manager instead of the old hashtable. Also convert all drivers to use the new convenience helpers. This drops all the (map_list.hash.key << PAGE_SHIFT) non-sense. Locking and access-management is exactly the same as before with an additional lock inside of the vma-manager, which

[PATCH v5 1/4] drm: add unified vma offset manager

If we want to map GPU memory into user-space, we need to linearize the addresses to not confuse mm-core. Currently, GEM and TTM both implement their own offset-managers to assign a pgoff to each object for user-space CPU access. GEM uses a hash-table, TTM uses an rbtree. This patch provides a

[Bug 67276] New: kernel-3.11 [drm:r600_uvd_ring_test] *ERROR* radeon: ring 5 test failed (0xCAFEDEAD)

aven't find a way to forcibly reproduce it. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/7e60217d/attachment.html>

[Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup

es that I'm using so perhaps no hardlocks with the DPM code so far :) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/c6591cd0/attachment.html>

drm/crtc-helper: explicit DPMS on after modeset

Hello Daniel Vetter, The patch 25f397a429df: "drm/crtc-helper: explicit DPMS on after modeset" from Jul 19, 2013, leads to the following warning: "drivers/gpu/drm/drm_crtc_helper.c:681 drm_crtc_helper_set_config() info: ignoring unreachable code." drivers/gpu/drm/drm_crtc_helper.c

drm/nouveau: fix locking issues in page flipping paths

Hello Ben Skeggs, The patch 060810d7abaa: "drm/nouveau: fix locking issues in page flipping paths" from Jul 8, 2013, leads to the following Smatch warning: "drivers/gpu/drm/nouveau/nouveau_display.c:599 nouveau_crtc_page_flip() error: double unlock 'mutex:>cli->mutex'"

drm/nouveau: do not allow negative sizes for now

Hello Maarten Lankhorst, This is a semi-automatic email about new static checker warnings. The patch 0108bc808107: "drm/nouveau: do not allow negative sizes for now" from Jul 7, 2013, leads to the following Smatch complaint: drivers/gpu/drm/nouveau/nouveau_bo.c:222 nouveau_bo_new()

[PATCH 4/5] drm/i915: Add async page flip support for IVB

es/dri-devel/attachments/20130724/1fd8ccce/attachment.pgp>

[PATCH v4 2/4] drm/gem: convert to new unified vma manager

Hi On Wed, Jul 24, 2013 at 5:52 PM, Daniel Vetter wrote: > On Tue, Jul 23, 2013 at 02:47:14PM +0200, David Herrmann wrote: >> Use the new vma manager instead of the old hashtable. Also convert all >> drivers to use the new convenience helpers. This drops all the >> (map_list.hash.key <<

[Bug 67265] r600g causes KWin crashes with kernel 3.9

... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/339165ef/attachment.html>

[Bug 67265] r600g causes KWin crashes with kernel 3.9

are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/67c6210d/attachment.html>

[PATCH v4 1/4] drm: add unified vma offset manager

Hi On Wed, Jul 24, 2013 at 5:35 PM, Daniel Vetter wrote: > On Tue, Jul 23, 2013 at 02:47:13PM +0200, David Herrmann wrote: >> If we want to map GPU memory into user-space, we need to linearize the >> addresses to not confuse mm-core. Currently, GEM and TTM both implement >> their own

[PATCH v4 4/4] drm/vma: provide drm_vma_node_unmap() helper

On Tue, Jul 23, 2013 at 02:47:16PM +0200, David Herrmann wrote: > Instead of unmapping the nodes in TTM and GEM users manually, we provide > a generic wrapper which does the correct thing for all vma-nodes. > > v2: remove bdev->dev_mapping test in ttm_bo_unmap_virtual_unlocked() as >

[PATCH v4 3/4] drm/ttm: convert to unified vma offset manager

On Tue, Jul 23, 2013 at 02:47:15PM +0200, David Herrmann wrote: > Use the new vma-manager infrastructure. This doesn't change any > implementation details as the vma-offset-manager is nearly copied 1-to-1 > from TTM. > > The vm_lock is moved into the offset manager so we can drop it from TTM. >

[PATCH v4 2/4] drm/gem: convert to new unified vma manager

On Tue, Jul 23, 2013 at 02:47:14PM +0200, David Herrmann wrote: > Use the new vma manager instead of the old hashtable. Also convert all > drivers to use the new convenience helpers. This drops all the > (map_list.hash.key << PAGE_SHIFT) non-sense. > > Locking and access-management is exactly the

3.10.2 : new warning WARNING: at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable+0x7ce/0x800 [i915]()

Realized this today while booting a ThinkPad T420 with integrated intel graphic : Jul 24 17:36:10 n22 kernel: [ cut here ] Jul 24 17:36:10 n22 kernel: WARNING: at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable+0x7ce/0x800 [i915]() Jul 24 17:36:10 n22

[PATCH v4 1/4] drm: add unified vma offset manager

On Tue, Jul 23, 2013 at 02:47:13PM +0200, David Herrmann wrote: > If we want to map GPU memory into user-space, we need to linearize the > addresses to not confuse mm-core. Currently, GEM and TTM both implement > their own offset-managers to assign a pgoff to each object for user-space > CPU

[Bug 61182] r600g causes KWin, Gnome Shell and Unity crashes with kernel 3.8

ves/dri-devel/attachments/20130724/d9e859ea/attachment.html>

[Bug 67265] r600g causes KWin crashes with kernel 3.9

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/2bebcd1a/attachment.html>

[Bug 67265] r600g causes KWin crashes with kernel 3.9

bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/3803907d/attachment.html>

[Bug 67265] r600g causes KWin crashes with kernel 3.9

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/3f429a24/attachment.html>

[Bug 67265] r600g causes KWin crashes with kernel 3.9

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/6994cdbc/attachment.html>

[Bug 67265] New: r600g causes KWin crashes with kernel 3.9

quot;accessibility cups dbus exceptions gif glib mng qt3support tiff xinerama xv (-aqua) -c++0x -debug -egl -gtkstyle -nas -nis (-pch) -trace" 0 kB -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbe

[PATCH] [RFC] drm/nouveau: bring back hdmi audio device after switcheroo power down

After a full device powerdown via the optimus power switch, we seem to lose the HDMI device completely on power on, this keep track of whether we had a hdmi audio sub function device at power on, and pokes a magic register to make it reappear after the optimus power switch is thrown. This at

[RFC 8/9] drm: track pending user-space actions

Op 24-07-13 16:24, David Herrmann schreef: > Hi > > On Wed, Jul 24, 2013 at 4:03 PM, Maarten Lankhorst > wrote: >> Op 24-07-13 15:43, David Herrmann schreef: >>> If we want to support real hotplugging, we need to block new syscalls from >>> entering any drm_* fops. We also need to wait for these

[RFC 8/9] drm: track pending user-space actions

Hi On Wed, Jul 24, 2013 at 4:03 PM, Maarten Lankhorst wrote: > Op 24-07-13 15:43, David Herrmann schreef: >> If we want to support real hotplugging, we need to block new syscalls from >> entering any drm_* fops. We also need to wait for these to finish before >> unregistering a device. >> >>

[RFC 8/9] drm: track pending user-space actions

Op 24-07-13 15:43, David Herrmann schreef: > If we want to support real hotplugging, we need to block new syscalls from > entering any drm_* fops. We also need to wait for these to finish before > unregistering a device. > > This patch introduces drm_dev_get/put_active() which mark a device as >

[PATCH 2/2] drm/exynos: add runtime pm interfaces to g2d driver

This patch makes g2d power domain and clock to be controlled through pm runtime interfaces instead of controlling them respectively. Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 40 +- 1 files changed, 28

[PATCH 1/2] drm/exynos: consider common clock framework to g2d driver.

This patch just changes clk_enable/disable to clk_prepare_enable/clk_disable_unprepare, and adds related exception codes. Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 17 ++--- 1 files changed, 14 insertions(+), 3 deletions(-)

[PATCH 0/2] drm/exynos: update g2d driver

This patch set includes a fixup patch that considers common clock framework, and adds runtime pm interfaces for -next. Inki Dae (2): drm/exynos: consider common clock framework to g2d driver. drm/exynos: add runtime pm interfaces to g2d driver drivers/gpu/drm/exynos/exynos_drm_g2d.c | 35

[Bug 61182] r600g causes KWin, Gnome Shell and Unity crashes with kernel 3.8

think you are hitting a different issue. Please open a new bug. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130

[RFC 9/9] drm: support immediate unplugging

Our current unplug-helpers remove all nodes from user-space and mark the device as unplugged. However, any pending user-space call is still continued. We wait for the last close() call to actually unload the device. This patch uses the drm_dev_get_active() infrastructure to allow immediate

[RFC 8/9] drm: track pending user-space actions

If we want to support real hotplugging, we need to block new syscalls from entering any drm_* fops. We also need to wait for these to finish before unregistering a device. This patch introduces drm_dev_get/put_active() which mark a device as active during file-ops. If a device is unplugged,

[RFC 7/9] percpu_rw_sempahore: export symbols for modules

DRM could make great use of percpu-rwsems to track active users and wait for them during hw hotplugging. Export symbols and allow using them in runtime loadable modules. Signed-off-by: David Herrmann --- lib/Makefile | 2 +- lib/percpu-rwsem.c | 7 +++ 2 files changed, 8

[RFC 6/9] drm: move device unregistration into drm_dev_unregister()

Analog to drm_dev_register(), we now provide drm_dev_unregister() which does the reverse. drm_dev_put() is still in place and combines the calls to drm_dev_unregister() and drm_dev_free() so buses don't have to change. *_get() and *_put() are used for reference-counting in the kernel. However,

[RFC 5/9] drm: introduce drm_dev_free() to fix error paths

The error paths in DRM bus drivers currently leak memory as they don't correctly revert drm_dev_alloc(). Introduce drm_dev_free() to free DRM devices which haven't been registered, yet. We must be careful not to introduce any side-effects with cleanups done in drm_dev_free(). drm_ht_remove(),

[RFC 4/9] drm: move drm_lastclose() to drm_fops.c

Try to keep all functions that handle DRM file_operations into drm_fops.c so internal helpers can be marked static later. This makes the split between the 3 core files more obvious: - drm_stub.c: DRM device allocation/destruction and management - drm_fops.c: DRM file_operations (except for

[RFC 3/9] drm/agp: fix AGP cleanup paths

Introduce two new helpers, drm_agp_clear() and drm_agp_destroy() which clear all AGP mappings and destroy the AGP head. This allows to reduce the AGP code in core DRM and move it all to drm_agpsupport.c. Also use these new helpers to clean up AGP allocations in the drm_dev_register() error path.

[RFC 2/9] drm: merge device setup into drm_dev_register()

All bus drivers do device setup themselves. This requires us to adjust all of them if we introduce new core features. Thus, merge all these into a uniform drm_dev_register() helper. Note that this removes the drm_lastclose() error path for AGP as it is horribly broken. Moreover, no bus driver

[RFC 1/9] drm: add drm_dev_alloc() helper

Instead of managing device allocation+initialization in each bus-driver, we should do that in a central place. drm_fill_in_dev() already does most of it, but also requires the global drm lock for partial AGP device registration. Split both apart so we have a clean device initialization/allocation

[RFC 0/9] DRM: Device Handling Cleanup

Hi This series fixes unplugging of DRM devices. It introduces four new helpers which replace the old drm_put_dev(), drm_unplug_dev(), drm_fill_in_dev() helpers: - drm_dev_alloc() Allocate a DRM device, initialize all static objects and fill in driver data. The device is not registered nor

[Bug 61182] r600g causes KWin, Gnome Shell and Unity crashes with kernel 3.8

are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/8a4add95/attachment.html>

[PATCH] [RFC] drm/nouveau: bring back hdmi audio device after switcheroo power down

On Wed, Jul 24, 2013 at 05:13:42PM +1000, Dave Airlie wrote: > After a full device powerdown via the optimus power switch, we seem > to lose the HDMI device completely on power on, this keep track of > whether we had a hdmi audio sub function device at power on, and > pokes a magic register to

[Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup

because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/77c13b37/attachment.html>

[PATCH 18/20] drm/gem: completely close gem_open vs. gem_close races

On Tue, Jul 16, 2013 at 09:12:09AM +0200, Daniel Vetter wrote: > The gem flink name holds a reference onto the object itself, and this > self-reference would prevent an flink'ed object from every being > freed. To break that loop we remove the flink name when the last > userspace handle

[PATCH] drm/gem: fix up flink name create race

On Wed, Jul 24, 2013 at 11:02:02AM +0200, Daniel Vetter wrote: > On Wed, Jul 24, 2013 at 8:04 AM, Daniel Vetter > wrote: > > This is the 2nd attempt, I've always been a bit dissatisified with the > > tricky nature of the first one: > > > >

[PATCH 4/5] drm/i915: Add async page flip support for IVB

attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 827 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/ac67786f/attachment.pgp>

[PATCH 3/3] qxl: convert qxl driver to proper use for reservations

From: Dave Airlie The recent addition of lockdep support to reservations and their subsequent use by TTM showed up a number of potential problems with the way qxl was using TTM objects. a) it was allocating objects, and reserving them later without validating underneath the

[PATCH 2/3] qxl: allow creation of pre-pinned objects and use for releases.

From: Dave Airlie In order to fix an issue with reservations we need to create the releases as pre-pinned objects, this changes the placement interface and bo creation interface to allow creating pinned objects to save nested reservations later. This is just a stepping stone

[PATCH 1/3] drm/qxl: add delayed fb operations

From: Dave Airlie Due to the nature of qxl hw we cannot queue operations while in an irq context, so we queue these operations as best we can until atomic allocations fail, and dequeue them later in a work queue. Daniel looked over the locking on the list and agrees it

qxl fb rendering and reservations fixes

Okay these are a bit large but I'd like to put them into -fixes ASAP, as qxl totally fails on -rc1/2 due to the lockdep and reservation warnings, The first patch is just a fix for broken rendering while rendering from an irq context, it also fixes sleep while atomic issues. The second patch is

[PATCH 1/2] anon_inodes: allow external inode allocations

Hi Al Any comment on this? Regards David On Thu, Jul 11, 2013 at 1:45 AM, David Herrmann wrote: > DRM core shares a single address_space across all inodes that belong to > the same DRM device. This allows efficient unmapping of user-space > mappings during buffer destruction. However, there

FAILED: patch "[PATCH] drm/i915: make compact dma scatter lists creation work with" failed to apply to 3.10-stable tree

On Tue, Jul 23, 2013 at 09:54:57AM -0700, gregkh at linuxfoundation.org wrote: > > The patch below does not apply to the 3.10-stable tree. You can drop it. The patch is already in 3.10 and it does not need to be backported to earlier trees. There was a snaffu were I thought David would post

[PATCH] drm/gem: fix up flink name create race

On Wed, Jul 24, 2013 at 8:04 AM, Daniel Vetter wrote: > This is the 2nd attempt, I've always been a bit dissatisified with the > tricky nature of the first one: > > http://lists.freedesktop.org/archives/dri-devel/2012-July/025451.html > > The issue is that the flink ioctl can race with calling

[PATCH] [RFC] drm/nouveau: bring back hdmi audio device after switcheroo power down

rm_kms_helper_poll_enable(dev); > + nouveau_reenable_hdmi_device(dev); > dev->switch_power_state = DRM_SWITCH_POWER_ON; > } else { > printk(KERN_ERR "VGA switcheroo: switched nouveau off\n"); Otherwise this looks good, Thanks, Paul -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/3c7d7caf/attachment.pgp>

[Bug 63599] [r600] SUMO2 GPU lockup CP stall (kernel 3.2.47, 3.4, 3.8, 3.9, 3.10)

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/7e433eed/attachment-0001.html>

[PATCH 1/1] drm/exynos: Remove module.h header inclusion

Since Exynos DRM drivers do not support module build, remove module.h header file inclusion from files that do not have any users. Signed-off-by: Sachin Kamat --- drivers/gpu/drm/exynos/exynos_ddc.c |1 - drivers/gpu/drm/exynos/exynos_drm_fimc.c|1 -

[Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup

chments/20130724/e1c8dabb/attachment.html>

[PATCH 06/20] drm/gem: inline drm_gem_object_handle_reference

On Tue, Jul 23, 2013 at 10:43 PM, Rob Clark wrote: > On Tue, Jul 23, 2013 at 8:31 AM, Daniel Vetter > wrote: >> On Tue, Jul 23, 2013 at 2:07 PM, Rob Clark wrote: >>> On Tue, Jul 16, 2013 at 3:11 AM, Daniel Vetter >>> wrote: Only one callsite and since ->handle_count is not a simple

[BUG] radeon: suspend resume

On Tue, Jul 23, 2013 at 2:59 PM, Sami Kerola wrote: > On 17 July 2013 11:19, Michel D?nzer wrote: >> On Mit, 2013-07-17 at 10:58 +0100, Sami Kerola wrote: >>> On 15 July 2013 11:35, Michel D?nzer wrote: >>> > On Son, 2013-07-14 at 13:26 +0100, Sami Kerola wrote: >>> >> >>> >> Jul 14 12:51:31

radeon regression 3.11.0-rc2+

On Tue, Jul 23, 2013 at 6:22 PM, Antti Palosaari wrote: > Hello > I just upgraded Kernel from 3.10.0-rc6+ to 3.11.0-rc2+ and ran serious > problems. That Kernel is current Linux Media master, which contains some > upcoming media stuff that should not still has any effect, but lets mention > for

[Bug 60879] [radeonsi] X11 can't start with acceleration enabled

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/3448586b/attachment.html>

[PATCH] drm/gem: fix up flink name create race

This is the 2nd attempt, I've always been a bit dissatisified with the tricky nature of the first one: http://lists.freedesktop.org/archives/dri-devel/2012-July/025451.html The issue is that the flink ioctl can race with calling gem_close on the last gem handle. In that case we'll end up with a

[PATCH 1/3] drm/qxl: add delayed fb operations

On Wed, Jul 24, 2013 at 4:00 AM, Dave Airlie wrote: > From: Dave Airlie > > Due to the nature of qxl hw we cannot queue operations while in an irq > context, so we queue these operations as best we can until atomic allocations > fail, and dequeue them later in a work queue. > > Daniel looked

[PATCH 06/20] drm/gem: inline drm_gem_object_handle_reference

On Wed, Jul 24, 2013 at 2:00 AM, Dave Airlie wrote: > On Tue, Jul 23, 2013 at 10:43 PM, Rob Clark wrote: >> On Tue, Jul 23, 2013 at 8:31 AM, Daniel Vetter >> wrote: >>> On Tue, Jul 23, 2013 at 2:07 PM, Rob Clark wrote: On Tue, Jul 16, 2013 at 3:11 AM, Daniel Vetter wrote: >

[Bug 66805] [radeonsi] half life 2 base games are segfaulting

bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130724/98027fa8/attachment.html>

[Bug 60381] AMD Radeon 7770 Ghz edition Crash with DPM active

https://bugzilla.kernel.org/show_bug.cgi?id=60381 --- Comment #33 from rafael castillo --- well step by step is getting better, im happy enough to get stable desktop now and since my card render KDE like an monster reclocking is not uber important for me right now. thanks for an awesome job ;)

[Bug 60381] AMD Radeon 7770 Ghz edition Crash with DPM active

https://bugzilla.kernel.org/show_bug.cgi?id=60381 --- Comment #32 from Alex Deucher --- The dynamic re-clocking doesn't currently work reliably on SI asics. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 60381] AMD Radeon 7770 Ghz edition Crash with DPM active

https://bugzilla.kernel.org/show_bug.cgi?id=60381 --- Comment #31 from rafael castillo --- uvd reclocks fine but the desktop flicker when it does -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 60381] AMD Radeon 7770 Ghz edition Crash with DPM active

https://bugzilla.kernel.org/show_bug.cgi?id=60381 --- Comment #30 from rafael castillo --- ok i tried the latest patches in drm-fixes and the crashes seemed to stop but i can't get the gpu to reclock i tried /sys/class/drm/card0/device/power_dpm_state to performance alone and it never scales

radeon regression 3.11.0-rc2+

Hello I just upgraded Kernel from 3.10.0-rc6+ to 3.11.0-rc2+ and ran serious problems. That Kernel is current Linux Media master, which contains some upcoming media stuff that should not still has any effect, but lets mention for sure. Display started freezing and gone black, I think two

[PATCH] drm: i915_gem_inactive_scan: insufficient nr_to_scan size

On Tue, Jul 23, 2013 at 11:18:06PM +0400, Artem Savkov wrote: > nr_to_scan needs to be (unsigned) long, not int, otherwise we get negative > values on 32bit systems during shrink resulting in lots of messages like one > below. > > [ 4078.989603] shrink_slab: i915_gem_inactive_scan+0x0/0xc0

[PATCH] drm: i915_gem_inactive_scan: insufficient nr_to_scan size

nr_to_scan needs to be (unsigned) long, not int, otherwise we get negative values on 32bit systems during shrink resulting in lots of messages like one below. [ 4078.989603] shrink_slab: i915_gem_inactive_scan+0x0/0xc0 negative objects to delete nr=-289580136 Introduced in "drivers: convert

[PATCH] drm/gem: fix up flink name create race

This is the 2nd attempt, I've always been a bit dissatisified with the tricky nature of the first one: http://lists.freedesktop.org/archives/dri-devel/2012-July/025451.html The issue is that the flink ioctl can race with calling gem_close on the last gem handle. In that case we'll end up with a

[PATCH 2/2] drm/exynos: add runtime pm interfaces to g2d driver

This patch makes g2d power domain and clock to be controlled through pm runtime interfaces instead of controlling them respectively. Signed-off-by: Inki Dae inki@samsung.com Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 40

Re: [PATCH] [RFC] drm/nouveau: bring back hdmi audio device after switcheroo power down

Am Mittwoch, den 24.07.2013, 17:13 +1000 schrieb Dave Airlie: After a full device powerdown via the optimus power switch, we seem to lose the HDMI device completely on power on, this keep track of keep*s* whether we had a hdmi audio sub function device at power on, and pokes a magic register

Re: [PATCH] drm/gem: fix up flink name create race

On Wed, Jul 24, 2013 at 8:04 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote: This is the 2nd attempt, I've always been a bit dissatisified with the tricky nature of the first one: http://lists.freedesktop.org/archives/dri-devel/2012-July/025451.html The issue is that the flink ioctl can race

[Bug 60879] [radeonsi] X11 can't start with acceleration enabled

https://bugs.freedesktop.org/show_bug.cgi?id=60879 --- Comment #39 from Hristo Venev mustrum...@gmail.com --- What is the difference between OpenCL integer division and OpenGL shader integer division? -- You are receiving this mail because: You are the assignee for the bug.

Re: [PATCH 1/2] anon_inodes: allow external inode allocations

Hi Al Any comment on this? Regards David On Thu, Jul 11, 2013 at 1:45 AM, David Herrmann dh.herrm...@gmail.com wrote: DRM core shares a single address_space across all inodes that belong to the same DRM device. This allows efficient unmapping of user-space mappings during buffer destruction.

[Bug 67002] evergreen: after resume from suspend-to-ram operation is really slow with the latest DPM changes + gpu lockup

https://bugs.freedesktop.org/show_bug.cgi?id=67002 --- Comment #8 from jackdac...@gmail.com --- ok,so the atombios error is fixed now what would the next step be to gradually fix this ? (so the uvd error after resume gpu lock/hang) switch to gcc 4.7* ? would that make a change ? the gcc

[Bug 63599] [r600] SUMO2 GPU lockup CP stall (kernel 3.2.47, 3.4, 3.8, 3.9, 3.10)

https://bugs.freedesktop.org/show_bug.cgi?id=63599 --- Comment #22 from Paul Wolneykien mano...@altlinux.org --- (In reply to comment #21) That just disables the use of vram for exa pixmaps. You can accomplish the same thing by adding: Option EXAPixmaps false to the device section of your

[PATCH 2/3] drm/exynos: add dt-binding documentation for rotator

This patch adds a dt-binding document for exynos rotator. It describes which nodes should be defined to use the rotator. Signed-off-by: Chanho Park chanho61.p...@samsung.com Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com --- .../bindings/drm/exynos/samsung-rotator.txt| 35

[PATCH 3/3] dts: ARM: add a rotator node for exynos4

This patch adds a device node of rotator for exynos4 platform. It has proper register and clock information. It also has limit table to get restrictions of the image size. Signed-off-by: Chanho Park chanho61.p...@samsung.com Signed-off-by: Kyungmin Park kyungmin.p...@samsung.com ---

[PATCH 0/3] device tree support for exynos rotator

This patchset includes dt support for exynos rotator. The exynos4 platform is only dt-based since 3.10, we should convert driver data and ids to dt-based parsing methods. The rotator driver has a limit table to get size limit. The minimum size of RGB888 format is 8 x 8 and maximum size is 8K x 8K.

[PATCH 1/3] drm/exynos: add device tree support for rotator

The exynos4 platform is only dt-based since 3.10, we should convert driver data and ids to dt-based parsing methods. The rotator driver has a limit table to get size limit. The minimum size of RGB888 format is 8 x 8 and maximum size is 8K x 8K. The other format, YCbCr420 2-Plane has 32 x 32 min

RE: [PATCH 2/3] drm/exynos: add dt-binding documentation for rotator

Hi Mark, Thank you for your review. -Original Message- From: Mark Rutland [mailto:mark.rutl...@arm.com] Sent: Monday, July 22, 2013 5:48 PM To: Chanho Park Cc: inki@samsung.com; kgene@samsung.com; linux-samsung- s...@vger.kernel.org; jy0922.s...@samsung.com; devicetree-

RE: [PATCH 2/3] drm/exynos: add dt-binding documentation for rotator

-Original Message- From: Inki Dae [mailto:inki@samsung.com] Sent: Tuesday, July 23, 2013 10:36 AM To: 'Chanho Park'; 'Mark Rutland'; 'Chanho Park' Cc: kgene@samsung.com; linux-samsung-...@vger.kernel.org; jy0922.s...@samsung.com; sw0312@samsung.com; dri-

[PATCH 05/27] drivers/gpu/host1x/drm: don't check resource with devm_ioremap_resource

devm_ioremap_resource does sanity checks on the given resource. No need to duplicate this in the driver. Signed-off-by: Wolfram Sang w...@the-dreams.de --- Please apply via the subsystem-tree. drivers/gpu/host1x/drm/hdmi.c |3 --- 1 file changed, 3 deletions(-) diff --git

FAILED: patch [PATCH] drm/i915: make compact dma scatter lists creation work with failed to apply to 3.10-stable tree

The patch below does not apply to the 3.10-stable tree. If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to sta...@vger.kernel.org. thanks, greg k-h -- original commit in Linus's

[PATCH 00/27] devm cleanup, part #1, take #3

Here is another bit of cleaning up the devm usage. It is again removing the resource check with devm_ioremap_resource, because a) new drivers came in and b) coccinelle had a bug and missed to find a couple of occasions. Unlike last time, I think it is better if these patches go in via the

Re: [BUG] radeon: suspend resume

On 17 July 2013 11:19, Michel Dänzer mic...@daenzer.net wrote: On Mit, 2013-07-17 at 10:58 +0100, Sami Kerola wrote: On 15 July 2013 11:35, Michel Dänzer mic...@daenzer.net wrote: On Son, 2013-07-14 at 13:26 +0100, Sami Kerola wrote: Jul 14 12:51:31 kerolasa-home kernel: radeon

[PATCH] drm: i915_gem_inactive_scan: insufficient nr_to_scan size

nr_to_scan needs to be (unsigned) long, not int, otherwise we get negative values on 32bit systems during shrink resulting in lots of messages like one below. [ 4078.989603] shrink_slab: i915_gem_inactive_scan+0x0/0xc0 negative objects to delete nr=-289580136 Introduced in drivers: convert

Re: [PATCH] drm: i915_gem_inactive_scan: insufficient nr_to_scan size

On Tue, Jul 23, 2013 at 11:18:06PM +0400, Artem Savkov wrote: nr_to_scan needs to be (unsigned) long, not int, otherwise we get negative values on 32bit systems during shrink resulting in lots of messages like one below. [ 4078.989603] shrink_slab: i915_gem_inactive_scan+0x0/0xc0 negative

[PATCH 1/1] drm/exynos: Remove module.h header inclusion

Since Exynos DRM drivers do not support module build, remove module.h header file inclusion from files that do not have any users. Signed-off-by: Sachin Kamat sachin.ka...@linaro.org --- drivers/gpu/drm/exynos/exynos_ddc.c |1 - drivers/gpu/drm/exynos/exynos_drm_fimc.c|1 -

  1   2   >