the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140531/719b2623/attachment.html>
if it's the fault of
something else, though.
--
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/20140531/18b1a683/attachment.html>
ignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140531/9bd36fde/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20140531/3518fc48/attachment.html>
>From 357d4ba36284eee4c2a99085450a9039735767c6 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 10:22:17 +0900
Subject: [PATCH 5/5] gpu/drm/ttm: Pass GFP flags in order to avoid deadlock.
Commit 7dc19d5a "drivers: convert shrinkers to new count/scan API" added
deadlock warnings
>From d960cdf1e1c91172b86ab9517e576e5fb7e71785 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 10:05:02 +0900
Subject: [PATCH 4/5] gpu/drm/ttm: Fix possible stack overflow by recursive
shrinker calls.
While ttm_dma_pool_shrink_scan() tries to take mutex before doing GFP_KERNEL
>From 4e8d1a83629c5966bfd401c5f2187355624194f2 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 09:59:44 +0900
Subject: [PATCH 3/5] gpu/drm/ttm: Use mutex_trylock() to avoid deadlock inside
shrinker functions.
I can observe that RHEL7 environment stalls with 100% CPU usage when
>From 19927a63c5d2dcda467373c31d810be42e40e190 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 09:47:02 +0900
Subject: [PATCH 2/5] gpu/drm/ttm: Choose a pool to shrink correctly in
ttm_dma_pool_shrink_scan().
We can use "unsigned int" instead of "atomic_t" by updating start_po
>From c1af6a76f8566d049d3cf24635a43b4a83a6 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Sat, 31 May 2014 09:39:22 +0900
Subject: [PATCH 1/5] gpu/drm/ttm: Fix possible division by 0 in
ttm_dma_pool_shrink_scan().
list_empty(&_manager->pools) being false before taking _manager->lock
does
Am 30.05.2014 18:40, schrieb Alex Deucher:
> Setting the power state prior to restoring the display
> hardware leads to blank screens on some systems. Drop
> the power state set from dpm resume. The power state
> will get set as part of the mode set sequence. Also
> add an explicit power state s
Hi Dave,
You'll get piles of those, and you get to rewrite the (x86) dma
implementation to fix them.
There's two parts of the problem:
- We hang onto dma mappings forever, and we don't enforce any
ownership. Actually we can't since our userspace _wants_ to access
some memory ranges while the gpu
Hi Linus,
Mostly quiet now,
i915: fixing userspace visiblie issues, all stable marked
radeon: one more pll fix, two crashers, one suspend/resume regression.
Dave.
The following changes since commit c7208164e66f63e3ec1759b98087849286410741:
Linux 3.15-rc7 (2014-05-25 16:06:00 -0700)
are ava
12 matches
Mail list logo
