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

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

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

On Thu, Jul 25, 2013 at 10:07:02PM +0200, Sedat Dilek wrote: > What means the bang line? > > [54.564] (II) GLX: Initialized DRI2 GL provider for screen 0 > [54.565] bang: 1159 > [54.565] > Fatal server error: > [54.565] failed to create screen resources That means between the

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

2 (194) -- 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/20130725/2223a8de/attachment.html>

[pull] radeon drm-fixes-3.11

From: Alex Deucher Hi Dave, Just a few more patches to fix some issues with dpm on rv6xx. The following changes since commit cef1d00cd56f600121ad121875655ad410a001b8: drm/radeon: fix combios tables on older cards (2013-07-22 15:57:14 -0400) are available in the

[PULL] drm-intel-fixes

Hi Dave, Brown-paper-bag pull request here. The snb rc6 fix from the last pull broke forcewake BIOS dirt cleanup, which with fixed. But that fix broke the spinlock init sequence, which results in an ugly BUG when spinlock debugging is enabled :( So I get to throw another patch at cc: stable to

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

On Thu, Jul 25, 2013 at 8:13 PM, Keith Packard wrote: > Daniel Vetter writes: > >> On Wed, Jul 24, 2013 at 06:40:16PM -0700, Keith Packard wrote: >>> Daniel Vetter writes: >>> >>> > We could just unconditionally increase the alignement in >>> > intel_pin_and_fence_fb_obj - we already have more

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

On Thu, Jul 25, 2013 at 09:12:41PM +0200, Sedat Dilek wrote: > New -3 dmesg. That puts the ball back in the ddx's court. Next debugging patch: diff --git a/src/intel_driver.c b/src/intel_driver.c index f4d76bb..1f4f299 100644 --- a/src/intel_driver.c +++ b/src/intel_driver.c @@ -170,6 +170,7 @@

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

On Thu, Jul 25, 2013 at 08:50:59PM +0200, Sedat Dilek wrote: > Against what tree is this applicable? It is definitely not drm-intel-nightly. Applied cleanly to nightly here, but just in case here's a rebased version: diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

On Thu, Jul 25, 2013 at 08:03:06PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:55 PM, Sedat Dilek wrote: > > F*ck. Wrong patch refreshed. > > > > New dmesg attached. Hmm, not seeing any difference, so let's add a couple more lines just to be sure: (apologies I didn't stash the

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

On Thu, Jul 25, 2013 at 07:52:22PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:26 PM, Chris Wilson > wrote: > > On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote: > >> On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson >> chris-wilson.co.uk> wrote: > >> > Basically boils down to

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

On Thu, Jul 25, 2013 at 07:15:03PM +0200, Sedat Dilek wrote: > On Thu, Jul 25, 2013 at 7:01 PM, Chris Wilson > wrote: > > Basically boils down to either an object allocation failure or mmaping > > failure. I think dmesg with drm.debug=7 is the next step. > > Attached! Thanks for taking care.

[RFC 1/1] drm/pl111: Initial drm/kms driver for pl111

From: Tom Cooksey This is a mode-setting driver for the pl111 CLCD display controller found on various ARM reference platforms such as the Versatile Express. The driver supports setting of a single mode (640x480) and has only been tested on Versatile Express with a Cortex-A9

[RFC 0/1] drm/pl111: Initial drm/kms driver for pl111

From: Tom Cooksey Please find below the current state of our pl111 DRM/KMS driver. This is lightly tested on a Versatile Express using X running the xf86-video-armsoc DDX driver[i] with the patches applied to drm-next as of ~last week. To actually see anything on the DVI

[PATCH] drm/mm: include required headers in drm_mm.h

This was meant as response to: Subject: [drm-intel:drm-intel-nightly 154/166] include/drm/drm_mm.h:67:2: error: unknown type name 'spinlock_t' Message-ID: <51f14693.g5HGdcuw2v3m8FOd%fengguang.wu at intel.com> In case it didn't link to it correctly. Somehow this bug doesn't occur here on my

[PATCH] drm/mm: include required headers in drm_mm.h

We need BUG_ON(), spinlock_t and standard kernel data-types so include the right headers. Signed-off-by: David Herrmann --- include/drm/drm_mm.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/include/drm/drm_mm.h b/include/drm/drm_mm.h index a30c9aa..d3f0aa1 100644 ---

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

VT switch > >> [ 40.396] ddxSigGiveUp: Closing log > >> [40.398] Server terminated with error (1). Closing log file. > > > > Please attach the full Xorg.0.log so that I can make a few guesses. > > Linux-kernel: This happens with drm-intel-nightly pulled into next-20130725. Basically boils down to either an object allocation failure or mmaping failure. I think dmesg with drm.debug=7 is the next step. -Chris -- Chris Wilson, Intel Open Source Technology Centre

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

On Thu, Jul 25, 2013 at 06:11:18PM +0200, Sedat Dilek wrote: > Might be OT, but I cannot use my X graphics stack containing > libdrm-2.4.46, mesa-9.1.5 and intel-ddx 2.21.12-git (tried also > v2.21.11). > Switching back to the one from Ubuntu/precise lets my X start. > > > [40.379] (II)

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

. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/13777155/attachment.html>

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

;>>> >>> >> >>>>>> Removed tree: >>> >> >>>>>> arm-dt (at maintainer's request) >>> >> >>>>>> >>> >> >>>>>> The wireless-next tree lost i

[PATCH 4/4] drm/mm: remove unused API

On Thu, Jul 25, 2013 at 03:56:02PM +0200, David Herrmann wrote: > We used to pre-allocate drm_mm nodes and save them in a linked list for > later usage so we always have spare ones in atomic contexts. However, this > is really racy if multiple threads are in an atomic context at the same > time

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

t its build failure and gained a conflict > >> >>>>>> against Linus' tree. > >> >>>>>> > >> >>>>>> The tty tree lost its build failure. > >> >>>>>> > >> >>>>>> Th

[PATCH 2/4] drm/ttm: replace drm_mm_pre_get() by direct alloc

On Thu, Jul 25, 2013 at 03:56:00PM +0200, David Herrmann wrote: > Instead of calling drm_mm_pre_get() in a row, we now preallocate the node > and then use the atomic insertion functions. This has the exact same > semantics and there is no reason to use the racy pre-allocations. > > Note that

[PATCH 1/4] drm/mm: add "best_match" to drm_mm_insert_node()

On Thu, Jul 25, 2013 at 03:55:59PM +0200, David Herrmann wrote: > Add a "best_match" argument similar to the drm_mm_search_*() helpers so we > can convert TTM to use them in follow up patches. We can also inline the > non-generic helpers and move them into the header to allow compile-time >

[Bug 66963] r600: linux 3.11RC isn't booting with radeon.dpm=1 option in grub

ttp://lists.freedesktop.org/archives/dri-devel/attachments/20130725/179ecbc5/attachment.html>

[PATCH 4/4] drm/mm: remove unused API

We used to pre-allocate drm_mm nodes and save them in a linked list for later usage so we always have spare ones in atomic contexts. However, this is really racy if multiple threads are in an atomic context at the same time and we don't have enough spare nodes. Moreover, all remaining users run in

[PATCH 3/4] drm/i915: pre-alloc instead of drm_mm search/get_block

i915 is the last user of the weird search+get_block drm_mm API. Convert it to an explicit kmalloc()+insert_node(). This drops the last user of the node-cache in drm_mm. We can remove it now in a follow-up patch. Cc: Daniel Vetter Signed-off-by: David Herrmann ---

[PATCH 2/4] drm/ttm: replace drm_mm_pre_get() by direct alloc

Instead of calling drm_mm_pre_get() in a row, we now preallocate the node and then use the atomic insertion functions. This has the exact same semantics and there is no reason to use the racy pre-allocations. Note that ttm_bo_man_get_node() does not run in atomic context. Nouveau already uses

[PATCH 1/4] drm/mm: add "best_match" to drm_mm_insert_node()

Add a "best_match" argument similar to the drm_mm_search_*() helpers so we can convert TTM to use them in follow up patches. We can also inline the non-generic helpers and move them into the header to allow compile-time optimizations. Signed-off-by: David Herrmann --- drivers/gpu/drm/drm_mm.c

[PATCH 0/4] DRM: Remove MM "Pre-Alloc"

Hi See patch 4/4 for a more detailed explanation of this series. I basically kill off the whole drm_mm pre-alloc code as it really doesn't make any sense with todays infrastructure. No drm_mm user runs in atomic context. We use pre-alloc only to allow allocation while holding a spin-lock. But we

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

t; > >>>>>> The wireless-next tree lost its build failure and gained a conflict > >>>>>> against Linus' tree. > >>>>>> > >>>>>> The tty tree lost its build failure. > >>>>>> > >>>>>> The staging tree gained a build fai

[Bug 60623] White Screen on boot with radeon.dpm=1

https://bugzilla.kernel.org/show_bug.cgi?id=60623 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1

[PATCH 0/2] drm/tilcdc drm/i2c/tda998x workaround for sync issues on TI SoC

On Thu, Jul 25, 2013 at 2:32 PM, Darren Etheridge wrote: > Russell King and Sebastian Hasselbarth had proposed some very good changes > for the tda998x HDMI encoder driver. But when those changes were tested > on BeagleBone Black against the tilcdc driver many modes would no longer > display

[PATCH 2/2] drm/i915: Add async page flip support for SNB

Just copies the IVB code Signed-off-by: Keith Packard --- drivers/gpu/drm/i915/intel_display.c | 17 + 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c index 166aa2c..4a118c3 100644 ---

[PATCH 1/2] drm/i915: Add async page flip support for IVB

This adds the necesary register defines for async page flipping through the command ring, and then hooks those up for Ivybridge (gen7) page flipping. Signed-off-by: Keith Packard --- drivers/gpu/drm/i915/i915_reg.h | 6 ++ drivers/gpu/drm/i915/intel_display.c | 37

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

> Generally I think checking our current sw state instead of reading hw > registers would be safer, e.g. in case we start to queue up more than > one pageflip. For async pageflips in benchmark mode "flip as fast as > you can queue" would be a sensible mode. Ok, I've moved the tiling checks to the

[PATCH 3/4] drm/i915: pre-alloc instead of drm_mm search/get_block

On Thu, Jul 25, 2013 at 03:56:01PM +0200, David Herrmann wrote: > i915 is the last user of the weird search+get_block drm_mm API. Convert it > to an explicit kmalloc()+insert_node(). This drops the last user of the > node-cache in drm_mm. We can remove it now in a follow-up patch. > > Cc: Daniel

[Bug 60623] New: White Screen on boot with radeon.dpm=1

https://bugzilla.kernel.org/show_bug.cgi?id=60623 Bug ID: 60623 Summary: White Screen on boot with radeon.dpm=1 Product: Drivers Version: 2.5 Kernel Version: 3.11.0-999-generic Hardware: x86-64 OS: Linux

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

-- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/602079c3/attachment.html>

[RFC 0/1] drm/pl111: Initial drm/kms driver for pl111

On Thu, Jul 25, 2013 at 1:17 PM, wrote: > From: Tom Cooksey > > Please find below the current state of our pl111 DRM/KMS driver. This > is lightly tested on a Versatile Express using X running the > xf86-video-armsoc DDX driver[i] with the patches applied to drm-next > as of ~last week. To

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

en post an updated dump? -- 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/20130725/e723215a/attachment.html>

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

de doesn't provide any advantages at this point. -- 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/20130725/5d9a175a/attachment.html>

[PATCH] drm/ttm: inline drm_bo_setup_vm()

This helper is used only once and just wraps a call to drm_vma_offset_add(). Remove this unneeded indirection to safe 10 lines of code. Signed-off-by: David Herrmann --- drivers/gpu/drm/ttm/ttm_bo.c | 22 ++ 1 file changed, 2 insertions(+), 20 deletions(-) diff --git

[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/20130725/234292d0/attachment.html>

[PATCH 2/2] drm/tilcdc fixup mode to workaound sync for tda998x

Add a fixup function that will flip the hsync priority and add a hskew value that is used to shift the tda998x to the right by a variable number of pixels depending on the mode. This works around an issue with the sync timings that tilcdc is outputing. Signed-off-by: Darren Etheridge ---

[PATCH 1/2] drm/i2c/tda998x prepare for tilcdc sync workaround

Add necessary support for flipping the hsync signal and shifting the display to the right by a certain number of pixels. Changes only take effect if adjusted_mode is changed in fixup function. Signed-off-by: Darren Etheridge --- drivers/gpu/drm/i2c/tda998x_drv.c | 10 ++ 1 files

[PATCH 0/2] drm/tilcdc drm/i2c/tda998x workaround for sync issues on TI SoC

Russell King and Sebastian Hasselbarth had proposed some very good changes for the tda998x HDMI encoder driver. But when those changes were tested on BeagleBone Black against the tilcdc driver many modes would no longer display correctly. After analyzing the sync signals from the TI lcd

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

- 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/20130725/fc4104ac/attachment.html>

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

he wireless-next tree lost its build failure and gained a conflict >>>>> against Linus' tree. >>>>> >>>>> The tty tree lost its build failure. >>>>> >>>>> The staging tree gained a build failure for which I disabled a drive

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

tachments/20130725/05b893b8/attachment.html>

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

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

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

. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/e59db041/attachment.html>

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

ost its build failure and gained a conflict >> against Linus' tree. >> >> The tty tree lost its build failure. >> >> The staging tree gained a build failure for which I disabled a driver. >> >> --

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

its build failure. >>>>>> >>>>>> The staging tree gained a build failure for which I disabled a driver. >>>>>> >>>>>> >>>>>

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

inus' tree. >>>> >>>> The tty tree lost its build failure. >>>> >>>> The staging tree gained a build failure for which I disabled a driver. >>>> >>>> >>>> >

[Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

The tty tree lost its build failure. >>> >>> The staging tree gained a build failure for which I disabled a driver. >>> >>> ---- >>> >> >> [ CCing drm and drm-intel folks ] >> >> With today's next-20130725 I see the following: > > Use of dev_priv->gt_

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

--- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/b9bee1f6/attachment.html>

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

Daniel Vetter writes: > On Wed, Jul 24, 2013 at 06:40:16PM -0700, Keith Packard wrote: >> Daniel Vetter writes: >> >> > We could just unconditionally increase the alignement in >> > intel_pin_and_fence_fb_obj - we already have more strict requirements due >> > to a bunch of w/a in other

linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

e tty tree lost its build failure. > > The staging tree gained a build failure for which I disabled a driver. > > > [ CCing drm and drm-intel folks ] With today's next-20130725 I see the following: [ 17.122627

[PATCH] drm/ttm: inline drm_bo_setup_vm()

On Thu, Jul 25, 2013 at 8:08 AM, David Herrmann wrote: > This helper is used only once and just wraps a call to > drm_vma_offset_add(). Remove this unneeded indirection to safe 10 lines of > code. > > Signed-off-by: David Herrmann Review-by: Jerome Glisse > --- >

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

On Wed, Jul 24, 2013 at 06:40:16PM -0700, Keith Packard wrote: > Daniel Vetter writes: > > > We could just unconditionally increase the alignement in > > intel_pin_and_fence_fb_obj - we already have more strict requirements due > > to a bunch of w/a in other places. So shouldn't hurt at all

[Bug 60527] [IVB hybrid] Linux 3.10.0: black screen on Asus UX32VD, please revert -> Revert "drm/i915: revert eDP bpp clamping code changes"

https://bugzilla.kernel.org/show_bug.cgi?id=60527 --- Comment #9 from Fabio Erculiani --- Created attachment 107016 --> https://bugzilla.kernel.org/attachment.cgi?id=107016=edit dmesg from a working kernel (3.10.1) This is from a working kernel (with the commit reverted) and was captured on

[Bug 60527] [IVB hybrid] Linux 3.10.0: black screen on Asus UX32VD, please revert -> Revert "drm/i915: revert eDP bpp clamping code changes"

https://bugzilla.kernel.org/show_bug.cgi?id=60527 --- Comment #8 from Fabio Erculiani --- Created attachment 107015 --> https://bugzilla.kernel.org/attachment.cgi?id=107015=edit dmesg from a broken kernel (3.10.2) This is from the "broken" kernel (without the commit reverted) -- You are

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/e93b9d0b/attachment.html>

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

d -- 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/20130725/90c857e2/attachment-0001.html>

[Bug 67187] Radeon HD6950: UVD not responding, trying to reset the VCPU

. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/d71a282f/attachment.html>

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

nts/20130725/bf638761/attachment.html>

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

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/20130725/b877df7b/attachment.html>

[git pull] drm qxl fixes

Okay as I warned, the qxl driver was running a bit free and loose with its ttm object reservations and the new lockdep enabled reservation tracking shone a bright light into it, it also with the new reservations mutexes hits a possible deadlock during boot. the first patch is a real fix to

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

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

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

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

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/7db084fc/attachment.html>

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/a01704c5/attachment-0001.html>

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

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

[Bug 67283] New: VDPAU doesn't work on hybrid laptop through DRI_PRIME

URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130725/05c52c53/attachment.html>

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

On Wed, Jul 24, 2013 at 01:26:32PM -0700, Keith Packard wrote: > Daniel Vetter writes: > > > Matching tiling modes is actually already a requirement on gen4+ (since > > the tiling bit and the linear/tiled offset registers can't be changed with > > a MI_DISPLAY_FLIP command). > > Async flip has

[Bug 66963] r600: linux 3.11RC isn't booting with radeon.dpm=1 option in grub

https://bugs.freedesktop.org/show_bug.cgi?id=66963 --- Comment #7 from Sergey --- Some findings: The actual hand happens in drivers/gpu/drm/radeon/rv6xx_dpm.c: int rv6xx_dpm_enable(struct radeon_device *rdev) on 'r600_start_dpm(rdev)' call. Makes sense that configurations are harmless before

[Bug 67187] Radeon HD6950: UVD not responding, trying to reset the VCPU

https://bugs.freedesktop.org/show_bug.cgi?id=67187 --- Comment #4 from Harald Judt h.j...@gmx.at --- There is some inconsistency in my testing. As one can deduce from dmesg.out, I was using tuxonice hybrid suspend/resume (behold the alternating S4/S3 lines) and that might have a bad influence on

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

https://bugs.freedesktop.org/show_bug.cgi?id=66805 --- Comment #20 from Laurent carlier lordhea...@gmail.com --- (In reply to comment #18) Created attachment 82875 [details] [review] Mesa Patch #2 v3 If you replace the v2 patch with this v3 patch, does it fix the crash? Now portal (and it

[Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME

https://bugs.freedesktop.org/show_bug.cgi?id=67283 Christian König deathsim...@vodafone.de changed: What|Removed |Added Status|NEW |RESOLVED

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

On Wed, Jul 24, 2013 at 06:40:16PM -0700, Keith Packard wrote: Daniel Vetter dan...@ffwll.ch writes: We could just unconditionally increase the alignement in intel_pin_and_fence_fb_obj - we already have more strict requirements due to a bunch of w/a in other places. So shouldn't hurt at

[Bug 60527] [IVB hybrid] Linux 3.10.0: black screen on Asus UX32VD, please revert - Revert drm/i915: revert eDP bpp clamping code changes

https://bugzilla.kernel.org/show_bug.cgi?id=60527 --- Comment #8 from Fabio Erculiani lx...@sabayon.org --- Created attachment 107015 -- https://bugzilla.kernel.org/attachment.cgi?id=107015action=edit dmesg from a broken kernel (3.10.2) This is from the broken kernel (without the commit

[Bug 60527] [IVB hybrid] Linux 3.10.0: black screen on Asus UX32VD, please revert - Revert drm/i915: revert eDP bpp clamping code changes

https://bugzilla.kernel.org/show_bug.cgi?id=60527 --- Comment #9 from Fabio Erculiani lx...@sabayon.org --- Created attachment 107016 -- https://bugzilla.kernel.org/attachment.cgi?id=107016action=edit dmesg from a working kernel (3.10.1) This is from a working kernel (with the commit reverted)

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

. The staging tree gained a build failure for which I disabled a driver. [ CCing drm and drm-intel folks ] With today's next-20130725 I see the following: Use of dev_priv-gt_lock in I915_WRITE through

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

https://bugs.freedesktop.org/show_bug.cgi?id=67276 --- Comment #3 from Joshua Cov. joshua...@gmail.com --- I have to say that I'm using kernel 3.10.3 with all radeon patches (drm-next-3.11 and drm-fixes-3.11) applied to it. The prooblem started after applying the fixes... However I needed to fix

[PATCH] drm/ttm: inline drm_bo_setup_vm()

This helper is used only once and just wraps a call to drm_vma_offset_add(). Remove this unneeded indirection to safe 10 lines of code. Signed-off-by: David Herrmann dh.herrm...@gmail.com --- drivers/gpu/drm/ttm/ttm_bo.c | 22 ++ 1 file changed, 2 insertions(+), 20

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

https://bugs.freedesktop.org/show_bug.cgi?id=67276 --- Comment #4 from Alex Deucher ag...@yahoo.com --- If you didn't pull in the drm reservation changes you don't need the fix. Do you have this problem straight 3.11? -- You are receiving this mail because: You are the assignee for the bug.

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

https://bugs.freedesktop.org/show_bug.cgi?id=67276 --- Comment #5 from Joshua Cov. joshua...@gmail.com --- (In reply to comment #4) If you didn't pull in the drm reservation changes you don't need the fix. Do you have this problem straight 3.11? I pull everything from your git that you sent

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

https://bugs.freedesktop.org/show_bug.cgi?id=67276 --- Comment #8 from Joshua Cov. joshua...@gmail.com --- (In reply to comment #7) (In reply to comment #5) Can this commit be the culprit of the problem? Yes, it could be. As I said, it was a fix for the new reservation code which it

[PATCH 0/4] DRM: Remove MM Pre-Alloc

Hi See patch 4/4 for a more detailed explanation of this series. I basically kill off the whole drm_mm pre-alloc code as it really doesn't make any sense with todays infrastructure. No drm_mm user runs in atomic context. We use pre-alloc only to allow allocation while holding a spin-lock. But we

[PATCH 1/4] drm/mm: add best_match to drm_mm_insert_node()

Add a best_match argument similar to the drm_mm_search_*() helpers so we can convert TTM to use them in follow up patches. We can also inline the non-generic helpers and move them into the header to allow compile-time optimizations. Signed-off-by: David Herrmann dh.herrm...@gmail.com ---

[PATCH 2/4] drm/ttm: replace drm_mm_pre_get() by direct alloc

Instead of calling drm_mm_pre_get() in a row, we now preallocate the node and then use the atomic insertion functions. This has the exact same semantics and there is no reason to use the racy pre-allocations. Note that ttm_bo_man_get_node() does not run in atomic context. Nouveau already uses

[PATCH 4/4] drm/mm: remove unused API

We used to pre-allocate drm_mm nodes and save them in a linked list for later usage so we always have spare ones in atomic contexts. However, this is really racy if multiple threads are in an atomic context at the same time and we don't have enough spare nodes. Moreover, all remaining users run in

[PATCH 3/4] drm/i915: pre-alloc instead of drm_mm search/get_block

i915 is the last user of the weird search+get_block drm_mm API. Convert it to an explicit kmalloc()+insert_node(). This drops the last user of the node-cache in drm_mm. We can remove it now in a follow-up patch. Cc: Daniel Vetter daniel.vet...@ffwll.ch Signed-off-by: David Herrmann

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

https://bugs.freedesktop.org/show_bug.cgi?id=67276 --- Comment #10 from Joshua Cov. joshua...@gmail.com --- (In reply to comment #9) (In reply to comment #8) I'll take a look later if I can backport the reservation code back to 3.10 (if it's worth). I see some commits

Re: [PATCH 2/4] drm/ttm: replace drm_mm_pre_get() by direct alloc

On Thu, Jul 25, 2013 at 03:56:00PM +0200, David Herrmann wrote: Instead of calling drm_mm_pre_get() in a row, we now preallocate the node and then use the atomic insertion functions. This has the exact same semantics and there is no reason to use the racy pre-allocations. Note that

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

build failure. The staging tree gained a build failure for which I disabled a driver. [ CCing drm and drm-intel folks ] With today's next-20130725 I see the following: Use of dev_priv

Re: [PATCH 4/4] drm/mm: remove unused API

On Thu, Jul 25, 2013 at 03:56:02PM +0200, David Herrmann wrote: We used to pre-allocate drm_mm nodes and save them in a linked list for later usage so we always have spare ones in atomic contexts. However, this is really racy if multiple threads are in an atomic context at the same time and we

Re: [Intel-gfx] linux-next: Tree for Jul 25 [ call-trace: drm | drm-intel related? ]

. [ CCing drm and drm-intel folks ] With today's next-20130725 I see the following: Use of dev_priv-gt_lock in I915_WRITE through intel_disable_gt_powersave before spin lock init, caused by commit 181d1b9e31c668259d3798c521672afb8edd355c

[Bug 60623] White Screen on boot with radeon.dpm=1

https://bugzilla.kernel.org/show_bug.cgi?id=60623 Alex Deucher alexdeuc...@gmail.com changed: What|Removed |Added CC||alexdeuc...@gmail.com

[PATCH] drm/mm: include required headers in drm_mm.h

We need BUG_ON(), spinlock_t and standard kernel data-types so include the right headers. Signed-off-by: David Herrmann dh.herrm...@gmail.com --- include/drm/drm_mm.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/include/drm/drm_mm.h b/include/drm/drm_mm.h index a30c9aa..d3f0aa1 100644

  1   2   >