Hi, all!
I am working on a para-virtualized frontend DRM driver for Xen [1]
which implements display device I/O interface for Xen guest OSes [2].
At the moment I am rebasing the existing implementation from 4.9 kernel
to recent and found that when user-space DRM application exits then CRTC's
On 1/30/2018 1:12 AM, Rob Herring wrote:
On Fri, Jan 19, 2018 at 05:13:42PM +0530, Vivek Gautam wrote:
qcom,smmu-v2 is an arm,smmu-v2 implementation with specific
clock and power requirements. This smmu core is used with
multiple masters on msm8996, viz. mdss, video, etc.
Add bindings for the
Hi,
We are working with new laptops that have the AMD Ravenl Ridge
chipset with this `/proc/cpuinfo`
https://gist.github.com/mschiu77/b06dba574e89b9a30cf4c450eaec49bc
With the latest kernel 4.15, there're lots of different
panics/oops during boot so no chance to get into X. It also
Hi Peter,
On Wed, Jan 31, 2018 at 3:57 PM, Peter Malone wrote:
> Fixing arbitrary kernel leak in case FBIOGETCMAP_SPARC in
> sbusfb_ioctl_helper().
>
> 'index' is defined as an int in sbusfb_ioctl_helper().
> We retrieve this from the user:
> if (get_user(index, >index)
On 1/31/2018 5:53 PM, Robin Murphy wrote:
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
The smmu needs to be functional only when the respective
master's using it are active. The device_link feature
helps to track such functional dependencies, so that
Bartlomiej,
On Wed, Jan 31, 2018 at 12:57 PM, Bartlomiej Zolnierkiewicz
wrote:
> On Tuesday, January 30, 2018 02:14:10 PM Mathieu Malaterre wrote:
>> Bartlomiej,
>>
>> On Wed, Jan 3, 2018 at 3:47 PM, Bartlomiej Zolnierkiewicz
>> wrote:
>> >
>>
Il 08/gen/2018 09:46 PM, "Sean Paul" ha scritto:
On Mon, Jan 08, 2018 at 03:41:49PM -0500, Sean Paul wrote:
> On Sat, Jan 06, 2018 at 12:59:58AM +0100, Mauro Rossi wrote:
> > Porting of original commit 76fb87e675 of Jim Bish in android-ia master
to fdo
> >
> > Original
Blank help texts are probably either a typo, a Kconfig misunderstanding,
or some kind of half-committing to adding a help text (in which case a
TODO comment would be clearer, if the help text really can't be added
right away).
Best to remove them, IMO.
Signed-off-by: Ulf Magnusson
On Sat, Jan 27, 2018 at 02:49:22AM +, Dhinakaran Pandiyan wrote:
> Drivers can use this in their retry loops too.
with all this layers of retries it is good that we find some consistency
somewhere
is this written down on any part of eDP spec?
Last time I saw there was different retries
https://bugs.freedesktop.org/show_bug.cgi?id=104064
--- Comment #3 from Bjorn ---
Probably also worth noting that as of 4.15, my laptop hangs with a black screen
on suspend/resume. Magic SysRq seems to be about the only thing the computer
responds to if I close and then
https://bugs.freedesktop.org/show_bug.cgi?id=104064
--- Comment #2 from Bjorn ---
Created attachment 137103
--> https://bugs.freedesktop.org/attachment.cgi?id=137103=edit
dmesg output without amdgpu.dc=1
I'm seemingly hitting this too, on 4.15. Note that I get it with or
Hi Michal:
How about only
EXPORT_SYMBOL_GPL(total_swap_pages) ?
Thanks
Roger(Hongbo.He)
-Original Message-
From: He, Roger
Sent: Wednesday, January 31, 2018 1:52 PM
To: 'Michal Hocko' ; Koenig, Christian
Cc: linux...@kvack.org;
But what we could do is to rely on a fixed limit like the Intel driver
does and I suggested before.
E.g. don't copy anything into a shmemfile when there is only x MB of
swap space left.
Here I think we can do it further, let the limit value scaling with total
system memory.
For
On 01/31/2018 09:50 PM, Rob Clark wrote:
On Wed, Jan 31, 2018 at 1:40 AM, Archit Taneja wrote:
On 01/29/2018 10:45 PM, Rob Herring wrote:
On Wed, Jan 17, 2018 at 03:04:47PM +0530, Archit Taneja wrote:
Add the compatible string for 14nm DSI PHY (used in
https://bugs.freedesktop.org/show_bug.cgi?id=104520
--- Comment #8 from xman <20830...@qq.com> ---
I am also hitting the same issue.
[ 1516.880515] [drm] GPU HANG: ecode 9:0:0x85db, reason: Hang on rcs0,
action: reset
[ 1516.880517] [drm] GPU hangs can indicate a bug anywhere in the entire
Hi Dave,
A few more misc fixes for 4.16.
The following changes since commit 559f17bec508548850654dd04525fd69d90f6d4e:
Merge tag 'drm-misc-next-fixes-2018-01-18' of
git://anongit.freedesktop.org/drm/drm-misc into drm-next (2018-01-25 11:42:25
+1000)
are available in the git repository at:
https://bugs.freedesktop.org/show_bug.cgi?id=104888
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
On Wed, Jan 31, 2018 at 9:20 PM, Ilia Mirkin wrote:
> Yeah, a lot of people were getting that, as a result of some drm/ttm
> hugepage usage.
>
> Christian, did a fix ever end up going out? If so, what kernel was it
> included in?
https://lkml.org/lkml/2018/1/16/106
Alex
>
Yeah, a lot of people were getting that, as a result of some drm/ttm
hugepage usage.
Christian, did a fix ever end up going out? If so, what kernel was it
included in?
-ilia
On Wed, Jan 31, 2018 at 11:05 AM, Ricardo Nabinger Sanchez
wrote:
> Hello,
>
> I've noticed
https://bugs.freedesktop.org/show_bug.cgi?id=104880
--- Comment #6 from Konstantin A. Lepikhov ---
s/hardware issue/not a hardware issue/ )
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=104880
--- Comment #5 from Konstantin A. Lepikhov ---
(In reply to Harry Wentland from comment #4)
> Does it help if you enable the following kernel configs?
>
> CONFIG_SND_HDA=y
> CONFIG_SND_HDA_INTEL=y
>
https://bugs.freedesktop.org/show_bug.cgi?id=104880
--- Comment #4 from Harry Wentland ---
Does it help if you enable the following kernel configs?
CONFIG_SND_HDA=y
CONFIG_SND_HDA_INTEL=y
CONFIG_SND_HDA_DSP_LOADER=y
CONFIG_SND_HDA_PREALLOC_SIZE=64
CONFIG_SND_HDA_HWDEP=y
https://bugs.freedesktop.org/show_bug.cgi?id=104880
--- Comment #3 from Konstantin A. Lepikhov ---
(In reply to Michel Dänzer from comment #2)
> (In reply to Konstantin A. Lepikhov from comment #0)
> > Kernel - 4.14.15 + DC patches till end of Oct 2017.
>
> That's pretty
https://bugs.freedesktop.org/show_bug.cgi?id=104888
--- Comment #3 from Harry Wentland ---
Curiously enough this is the first time I've heard of setterm. I'm not sure if
it's really supported but I tried amdgpu, non-amdgpu (i.e. vbios), and an Intel
platform and on
https://bugs.freedesktop.org/show_bug.cgi?id=104831
--- Comment #4 from Martin Bednar ---
Created attachment 137095
--> https://bugs.freedesktop.org/attachment.cgi?id=137095=edit
kwin backtrace
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=104831
--- Comment #3 from Martin Bednar ---
Just booted with 18.0-rc3. Plasma started up just fine. Alt+tab in kwin
however... Different bug?
#6 0x7f5b039615bd in r600_draw_vbo () from /usr/lib64/dri/r600_dri.so
#7
https://bugs.freedesktop.org/show_bug.cgi?id=104888
--- Comment #2 from Robin Kauffman ---
(In reply to Harry Wentland from comment #1)
> You can try amdgpu.dc_log=1 and drm.debug=4.
Thanks, I'll try both of these and report back.
>
> Does the display blank out and
https://bugs.freedesktop.org/show_bug.cgi?id=104190
--- Comment #3 from Tommy Vestermark ---
I can confirm seeing the same artifacts in CSGO on a R9 285 (Tonga) using
Ubuntu 17.10 with Mesa 17.3.2, LLVM 5.0 (Padoka Stable PPA).
--
You are receiving this mail because:
You
On 2018-01-30 05:28 AM, Maarten Lankhorst wrote:
> Op 29-01-18 om 16:41 schreef Leo Li:
>> Updated IGT results seem sane:
>> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7698/shards.html
>>
>> Would someone be able to apply this patch?
>>
> Thanks for the reminder, pushed.
>
Thanks,
https://bugs.freedesktop.org/show_bug.cgi?id=104888
--- Comment #1 from Harry Wentland ---
You can try amdgpu.dc_log=1 and drm.debug=4.
Does the display blank out and then wake right back up or do you see no change
at all on the display when trying to enter dpms?
--
https://bugs.freedesktop.org/show_bug.cgi?id=104888
Bug ID: 104888
Summary: DPMS issue w/ GFX8/Polaris10/Ellesmere/Rx-480-8GiB &
agd5f's drm-next-4.17-wip
Product: DRI
Version: XOrg git
Hardware: Other
OS:
On Wed, Jan 31, 2018 at 10:51 AM, Alexandru-Cosmin Gheorghe
wrote:
> Hi John,
>
> I took your patches for a spin on Hikey960. Some findings:
> Even with this patch I'm getting some tearing on Hikey960, not a lot as you
> reported on Hikey, still there are some
Hi John,
I took your patches for a spin on Hikey960. Some findings:
Even with this patch I'm getting some tearing on Hikey960, not a lot as you
reported on Hikey, still there are some small black squares, less than 10 of
aproximetly 20x20.
So I investigated a little bit through drm_hwcomposer and
On Wed, Jan 31, 2018 at 8:01 AM, Emil Velikov wrote:
> On 30 January 2018 at 05:42, John Stultz wrote:
>> On Fri, Jan 26, 2018 at 10:33 AM, Emil Velikov
>> wrote:
>>> Hi all,
>>>
>>> Couple of ideas/notes,
>>>
>>> On
Add support for the A6XX family of Adreno GPUs. The biggest addition
is the GMU (Graphics Management Unit) which takes over most of the
power management of the GPU itself but in a ironic twist of fate
needs a goodly amount of management itself. Add support for the
A6XX core code, the GMU and the
From: Sharat Masetty
Add initial register headers for A6XX targets.
Signed-off-by: Sharat Masetty
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/adreno/a6xx.xml.h | 1600 +
This is an RFC for the initial version of a6xx support for the Adreno a6xx GPU
family as found on the sdm845 SoC. This code is ahead of most of the rest of
the sdm845 code that would be needed to actually bring up a device and it is
definitely far in advance of any user side support for the a6xx
Hi,
On Wed, Jan 31, 2018 at 7:16 AM, Sean Paul wrote:
> On Wed, Jan 31, 2018 at 7:54 AM, Lucas Stach wrote:
>> Am Dienstag, den 30.01.2018, 21:29 +0100 schrieb Thierry Escande:
>>> From: Sean Paul
>>>
>>> Change the mode
On Mon, Jan 22, 2018 at 2:36 AM, Julia Lawall wrote:
> From: Fengguang Wu
>
> Remove unneeded semicolon.
>
> Generated by: scripts/coccinelle/misc/semicolon.cocci
>
> Signed-off-by: Fengguang Wu
> Signed-off-by: Julia Lawall
On Wed, Jan 31, 2018 at 1:40 AM, Archit Taneja wrote:
>
>
> On 01/29/2018 10:45 PM, Rob Herring wrote:
>>
>> On Wed, Jan 17, 2018 at 03:04:47PM +0530, Archit Taneja wrote:
>>>
>>> Add the compatible string for 14nm DSI PHY (used in MSM8996/APQ8096).
>>> From 14nm PHY
On 2018-01-31 09:31 AM, Chris Chiu wrote:
> Hi,
> We are working with new laptops that have the AMD Ravenl Ridge
> chipset with this `/proc/cpuinfo`
> https://gist.github.com/mschiu77/b06dba574e89b9a30cf4c450eaec49bc
>
> With the latest kernel 4.15, there're lots of different
>
https://bugs.freedesktop.org/show_bug.cgi?id=104819
Emil Velikov changed:
What|Removed |Added
Status|NEW |RESOLVED
In the past the ast driver relied upon the fbdev emulation helpers to
call ->load_lut at boot-up. But since
commit b8e2b0199cc377617dc238f5106352c06dcd3fa2
Author: Peter Rosin
Date: Tue Jul 4 12:36:57 2017 +0200
drm/fb-helper: factor out pseudo-palette
that's cleaned up
On 30 January 2018 at 05:42, John Stultz wrote:
> On Fri, Jan 26, 2018 at 10:33 AM, Emil Velikov
> wrote:
>> Hi all,
>>
>> Couple of ideas/notes,
>>
>> On 10 January 2018 at 20:36, Rob Herring wrote:
>>> On Wed, Jan 10, 2018 at
Hi Benjamin,
Great, Many thanks,
Tested-by: Philippe Cornu
Philippe :-)
On 01/31/2018 09:05 AM, Benjamin Gaignard wrote:
> In all cases we have to check pitch and size calculations to speed up
> data transfer.
>
> Fixes: 21f815bf773c ("drm/stm: drv: Improve data
Quoting Gustavo Padovan (2018-01-31 12:32:21)
> Hi,
>
> 2017-08-11 Jason Ekstrand :
>
> > From: Chris Wilson
> >
> > This is an illegal scenario, to free the fence whilst there are pending
> > callbacks. Currently, we emit a WARN and then cast
On Sat, Jan 20, 2018 at 12:30 AM, Gustavo A. R. Silva
wrote:
>
> Quoting Felix Kuehling :
>
>> Looks good. This change is Reviewed-by: Felix Kuehling
>>
>>
>
> Thanks Felix.
> --
> Gustavo
>
Applied to -next
Oded
>
>
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=104880
Michel Dänzer changed:
What|Removed |Added
CC|
So I've made an error when sending this out, it includes some stuff
that is already on 4.15. Sorry about that, the only one that is needs
to go in is this one:
Daniel Vetter (1):
drm/cirrus: Load lut in crtc_commit
The pull request is fine, just the generated e-mail is wrong.
Thanks!
https://bugzilla.kernel.org/show_bug.cgi?id=194899
Janpieter Sollie (janpieter.sol...@dommel.be) changed:
What|Removed |Added
Status|NEW |RESOLVED
On Wed, Jan 31, 2018 at 7:54 AM, Lucas Stach wrote:
> Am Dienstag, den 30.01.2018, 21:29 +0100 schrieb Thierry Escande:
>> From: Sean Paul
>>
>> Change the mode for Sharp lq123p1jx31 panel to something more
>> rockchip-friendly such that we can use
Hi Dave,
This one got applied late to drm-misc-fixes, it should go to 4.16
anyway. Please pull, Thanks.
Gustavo
drm-misc-fixes-2018-01-31:
- fix lut loading for cirrus
The following changes since commit a8750ddca918032d6349adbf9a4b6555e7db20da:
Linux 4.15-rc8 (2018-01-14 15:32:30 -0800)
are
Hi Dave,
two fixes for the 4.16 cycle from the drm-misc-next-fixes.
drm-misc-next-fixes-2018-01-31:
This contains a fix to restrict what lessee can do with masters and
another one when waiting for timeouts on reservation objects.
The following changes since commit
https://bugs.freedesktop.org/show_bug.cgi?id=104520
--- Comment #7 from Eric Blau ---
Created attachment 137088
--> https://bugs.freedesktop.org/attachment.cgi?id=137088=edit
/sys/class/drm/card0/error file
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=104520
--- Comment #6 from Eric Blau ---
I'm in the same boat. I get frequent hangs as reported:
kernel: [drm] GPU HANG: ecode 8:0:0x2e6b4c79, in Xorg [2680], reason: Hang on
rcs0, action: reset
kernel: [drm] GPU hangs can indicate a
Since USB connector bindings are available we can describe it on TM2(e).
Signed-off-by: Andrzej Hajda
---
arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi
From: Maciej Purski
Currently MHL chip must be turned on permanently to detect MHL cable. It
duplicates micro-USB controller's (MUIC) functionality and consumes
unnecessary power. Lets use extcon attached to MUIC to enable MHL chip
only if it detects MHL cable.
Since extcon property is not allowed in DT, extcon subsystem requires
another way to get extcon device. Lets try the simplest approach - get
edev by of_node.
Signed-off-by: Andrzej Hajda
Acked-by: Chanwoo Choi
---
v2: changed label to follow local
OF graph describes MHL data lanes between MHL and respective USB
connector.
Signed-off-by: Andrzej Hajda
---
.../boot/dts/exynos/exynos5433-tm2-common.dtsi | 31 +++---
1 file changed, 28 insertions(+), 3 deletions(-)
diff --git
Hi,
This patchset introduces USB physical connector bindings, together with working
example.
I have added comments in relevant patches to describe possible issues.
In v2 I have addressed comments by Rob and Laurent, thanks
Changes are described in patches.
Regards
Andrzej
Andrzej Hajda (4):
These bindings allow to describe most known standard USB connectors
and it should be possible to extend it if necessary.
USB connectors, beside USB can be used to route other protocols,
for example UART, Audio, MHL. In such case every device passing data
through the connector should have
On Fri, 22 Dec 2017, Anusha Srivatsa wrote:
> Forward Error Correction is supported on DP 1.4.
> This patch adds corresponding DPCD register definitions.
>
> v2: Add dri-devel mailing list to the CC list(Jani)
>
> v3: Change names, add missing masks (Manasi)
>
> v4: Add
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which gets
called once when the
On Wed, Jan 31, 2018 at 12:04:52PM +0530, Nautiyal, Ankit K wrote:
>
>
> On 1/30/2018 12:23 AM, Ville Syrjälä wrote:
> > On Fri, Jan 12, 2018 at 11:51:33AM +0530, Nautiyal, Ankit K wrote:
> >> From: Ankit Nautiyal
> >>
> >> If the user mode does not support
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
The smmu device probe/remove and add/remove master device callbacks
gets called when the smmu is not linked to its master, that is without
the context of the master device. So calling runtime apis in those
https://bugs.freedesktop.org/show_bug.cgi?id=104597
--- Comment #10 from Mario Kleiner ---
Created attachment 137087
--> https://bugs.freedesktop.org/attachment.cgi?id=137087=edit
Possible fix, tested against server 1.19 branch.
This patch fixes the problem
Am Dienstag, den 30.01.2018, 21:29 +0100 schrieb Thierry Escande:
> From: Sean Paul
>
> Change the mode for Sharp lq123p1jx31 panel to something more
> rockchip-friendly such that we can use the fixed PLLs to
> generate the pixel clock
This should really switch to a
Hi,
2017-08-11 Jason Ekstrand :
> From: Chris Wilson
>
> This is an illegal scenario, to free the fence whilst there are pending
> callbacks. Currently, we emit a WARN and then cast aside the callbacks
> leaving them dangling. Alternatively, we
On Wed, Jan 31, 2018 at 12:04:50PM +0100, Daniel Vetter wrote:
> In the past the ast driver relied upon the fbdev emulation helpers to
> call ->load_lut at boot-up. But since
>
> commit b8e2b0199cc377617dc238f5106352c06dcd3fa2
> Author: Peter Rosin
> Date: Tue Jul 4 12:36:57
On 19/01/18 11:43, Vivek Gautam wrote:
From: Sricharan R
The smmu needs to be functional only when the respective
master's using it are active. The device_link feature
helps to track such functional dependencies, so that the
iommu gets powered when the master device
https://bugs.freedesktop.org/show_bug.cgi?id=100979
--- Comment #11 from Przemek ---
Created attachment 137085
--> https://bugs.freedesktop.org/attachment.cgi?id=137085=edit
kernel log during hibernate
Kernel log taken during hibernate process. Netbook was booted up with
On Tuesday, January 30, 2018 02:14:10 PM Mathieu Malaterre wrote:
> Bartlomiej,
>
> On Wed, Jan 3, 2018 at 3:47 PM, Bartlomiej Zolnierkiewicz
> wrote:
> >
> > On Thursday, December 21, 2017 11:07:56 PM Mathieu Malaterre wrote:
> >> When the linux kernel is build with
On Wed, 31 Jan 2018, Daniel Thompson wrote:
> On Fri, Jan 26, 2018 at 08:20:08PM +0530, Aishwarya Pant wrote:
>> Add documentation for sysfs interfaces of lp8788 backlight driver by
>> looking through the code and the git commit history.
>>
>> Signed-off-by: Aishwarya
On Fri, Jan 26, 2018 at 08:23:57PM +0530, Aishwarya Pant wrote:
> Add documentation for sysfs interfaces of Texas Instruments lm3639
> backlight + flash led driver chip by looking through git commits and
> reading code.
>
> Signed-off-by: Aishwarya Pant
> ---
>
https://bugs.freedesktop.org/show_bug.cgi?id=100979
--- Comment #10 from Przemek ---
After some research I think that messages "swiotlb buffer is full" and
"swiotlb: coherent allocation failed" are not related to this bug:
https://lkml.org/lkml/2018/1/16/106
--
You are
On Wed, 31 Jan 2018, Daniel Vetter wrote:
> I'm stepping down, also handing all the drm-misc stuff to the new
> team. Plan is that Sean handles 4.17, and Maarten then has fun with
> 4.18 as his first release.
>
> Cc: Maarten Lankhorst
>
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #12 from Przemek ---
I dont know if it is related, but:
https://lkml.org/lkml/2018/1/16/106
--
You are receiving this mail because:
You are the assignee for the bug.___
Op 31-01-18 om 12:02 schreef Gustavo Padovan:
> 2018-01-31 Daniel Vetter :
>
>> I'm stepping down, also handing all the drm-misc stuff to the new
>> team. Plan is that Sean handles 4.17, and Maarten then has fun with
>> 4.18 as his first release.
>>
>> Cc: Maarten Lankhorst
On Thursday, 2018-01-25 16:14:45 -0800, Dylan Baker wrote:
> Signed-off-by: Dylan Baker
Reviewed-by: Eric Engestrom
> ---
>
> I have tested building every mesa driver against this (with and without udev!)
> so I'm pretty sure that this is
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #28 from Daniel Vetter (dan...@ffwll.ch) ---
Created attachment 273941
--> https://bugzilla.kernel.org/attachment.cgi?id=273941=edit
test patch for deposite pirate
Should apply on any recent-ish kernel. Please apply, boot, and grab
On Fri, Jan 26, 2018 at 08:20:08PM +0530, Aishwarya Pant wrote:
> Add documentation for sysfs interfaces of lp8788 backlight driver by
> looking through the code and the git commit history.
>
> Signed-off-by: Aishwarya Pant
> ---
>
In the past the ast driver relied upon the fbdev emulation helpers to
call ->load_lut at boot-up. But since
commit b8e2b0199cc377617dc238f5106352c06dcd3fa2
Author: Peter Rosin
Date: Tue Jul 4 12:36:57 2017 +0200
drm/fb-helper: factor out pseudo-palette
that's cleaned up and
2018-01-31 Daniel Vetter :
> I'm stepping down, also handing all the drm-misc stuff to the new
> team. Plan is that Sean handles 4.17, and Maarten then has fun with
> 4.18 as his first release.
>
> Cc: Maarten Lankhorst
> Cc: David
https://bugs.freedesktop.org/show_bug.cgi?id=100979
--- Comment #9 from Przemek ---
I have just upgraded kernel to 4.15.
There is a big progress. Laptop can now successfully suspend (S3) and resume
many times in a row.
_Thank you very much for your hard work_.
But
So I think preventing validation on same place is a simpler way:
process B bo's place is fpfn~lpfn, it will only try to evict LRU BOs
in that range, while eviction, we just prevent those validation to
this range(fpfn~lpfn), if out of this range, the allocation/validation
still can be go on.
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #27 from Daniel Vetter (dan...@ffwll.ch) ---
Ok I've reviewed all the drivers where Peter Rosin's patch series removed the
load_lut hook:
- ast: fixed with my patch
- mga200g: already has a callchain like crtc_commit -> dpms ->
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #26 from Daniel Vetter (dan...@ffwll.ch) ---
Re #commment 24: crtc_commit is for modesets, the legacy helpers do _not_ call
the DPMS functions in that case. radeon does what every reasonable legacy kms
driver did and calls the dpms
On 2018年01月26日 22:35, Christian König wrote:
I just realized that a change I'm thinking about for a while would
solve your problem as well, but keep concurrent allocation possible.
See ttm_mem_evict_first() unlocks the BO after evicting it:
ttm_bo_del_from_lru(bo);
Quoting Christian König (2017-08-13 14:04:29)
> Am 11.08.2017 um 19:01 schrieb Chris Wilson:
> > This is an illegal scenario, to free the fence whilst there are pending
> > callbacks. Currently, we emit a WARN and then cast aside the callbacks
> > leaving them dangling. Alternatively, we could set
I'm stepping down, also handing all the drm-misc stuff to the new
team. Plan is that Sean handles 4.17, and Maarten then has fun with
4.18 as his first release.
Cc: Maarten Lankhorst
Cc: David Airlie
Cc: Gustavo Padovan
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #11 from Przemek ---
Similar with Radeon R4 APU - a6 6310
Kernel 4.15, mesa 17.3.3:
"swiotlb_tbl_map_single: 10 callbacks suppressed
[76882.115961] amdgpu :00:01.0: swiotlb buffer is full (sz: 2097152 bytes)
On Wed, Jan 31, 2018 at 11:03:39AM +0200, Oded Gabbay wrote:
> On Tue, Jan 30, 2018 at 12:33 PM, Daniel Vetter wrote:
> > On Mon, Jan 29, 2018 at 05:40:02PM +0200, Oded Gabbay wrote:
> >> In dma_fence_release() there is a WARN_ON which could be triggered by
> >> several cases of
https://bugs.freedesktop.org/show_bug.cgi?id=104880
--- Comment #1 from Konstantin A. Lepikhov ---
Created attachment 137080
--> https://bugs.freedesktop.org/attachment.cgi?id=137080=edit
dmesg w/ drm debug and dc_log=1
Added dmesg with enabled debugging from drm and
https://bugs.freedesktop.org/show_bug.cgi?id=104880
Konstantin A. Lepikhov changed:
What|Removed |Added
Hardware|Other |x86-64
https://bugs.freedesktop.org/show_bug.cgi?id=104880
Bug ID: 104880
Summary: No sound via DP on R9 Fury (4.14 + DC patches)
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity:
https://bugs.freedesktop.org/show_bug.cgi?id=104306
Michel Dänzer changed:
What|Removed |Added
Resolution|--- |FIXED
On Tue, Jan 30, 2018 at 12:33 PM, Daniel Vetter wrote:
> On Mon, Jan 29, 2018 at 05:40:02PM +0200, Oded Gabbay wrote:
>> In dma_fence_release() there is a WARN_ON which could be triggered by
>> several cases of wrong dma-fence usage. This patch adds a comment to
>> explain two
Discussed with Roger just now, we can try "void si_swapinfo(struct
sysinfo *val)" function to get the total swap space.
Regards,
David Zhou
On 2018年01月31日 16:12, Christian König wrote:
Yeah, indeed. But what we could do is to rely on a fixed limit like
the Intel driver does and I suggested
https://bugs.freedesktop.org/show_bug.cgi?id=104876
Marta Löfstedt changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
https://bugs.freedesktop.org/show_bug.cgi?id=104876
Marta Löfstedt changed:
What|Removed |Added
Status|NEW |RESOLVED
1 - 100 of 164 matches
Mail list logo