https://bugs.freedesktop.org/show_bug.cgi?id=100443
--- Comment #31 from takeshi ogasawara ---
Hi
I could not identify the cause and tried to replace the power supply unit.
bf:SILVERSTONE SST-ST75F-P (750W)
af:Seasonic SSR-750TD (750W)
The error in the
Hi Linus,
Just had a single AMD fixes pull for Alex for rc1.
Dave.
The following changes since commit 7846b12fe0b5feab5446d892f41b5140c1419109:
Merge branch 'drm-vmwgfx-next' of
git://people.freedesktop.org/~syeh/repos_linux into drm-next
(2017-08-29 10:38:14 +1000)
are available in the git
https://bugs.freedesktop.org/show_bug.cgi?id=102233
--- Comment #1 from Jan Vesely ---
What is the mesa/llvm version?
can you post clinfo?
do you use ocl-icd library? if so can you run setting
OCL_ICD_VENDORS=/etc/OpenCL/vendors/mesa.icd
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102796
--- Comment #1 from Tom Englund ---
apitrace of steam , apitrace32 --api gl steam-native
https://gist.github.com/gulafaran/bb1499808c777b33032297d18d28e3fc
tried with dri2 and xorg modesetting. same rendering issue.
https://bugs.freedesktop.org/show_bug.cgi?id=99553
Bug 99553 depends on bug 99856, which changed state.
Bug 99856 Summary: OpenCL Hello world returns "unsupported call to function
get_local_size"
https://bugs.freedesktop.org/show_bug.cgi?id=99856
What|Removed
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #50 from Shmerl ---
(In reply to Alex Deucher from comment #49)
> You can force a reset by reading /sys/kernel/debug/dri/0/amdgpu_gpu_reset
> but very few if any applications currently use the GL robustness
https://bugzilla.kernel.org/show_bug.cgi?id=193651
--- Comment #25 from Milo (milo...@gmail.com) ---
trying to install a 4.13 kernel and boot times are back to more than 5 minutes
(the failed to send message appears for more than 5 minutes when i run
journalctl -e)
journalctl log -
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #54 from Joshua Cogliati ---
Just for reference, the ring 0 test failed error comes from the line:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/radeon/r600.c#n2848
https://bugs.freedesktop.org/show_bug.cgi?id=95015
--- Comment #13 from Joshua Cogliati ---
Just for reference, this error comes from the line:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/radeon/r600.c#n2848
Basically, the
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #49 from Alex Deucher ---
You can force a reset by reading /sys/kernel/debug/dri/0/amdgpu_gpu_reset but
very few if any applications currently use the GL robustness extensions to
query if the context is lost
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #48 from Shmerl ---
(In reply to Lukas Jirkovsky from comment #47)
> There's no such file on my system. There is a reset file for other PCI
> busses, but not for the GPU.
I don't have it either for RX 480 card.
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #53 from erhar...@mailbox.org ---
Not necessarily. This bug here was introduced somewhere in the 4.11 kernel
development (see bisect), 4.12.x still affected. I don't have this problem with
kernel 4.10.x and 4.9.x.
The other bug
https://bugs.freedesktop.org/show_bug.cgi?id=102800
--- Comment #5 from higu...@gmx.net ---
Created attachment 134267
--> https://bugs.freedesktop.org/attachment.cgi?id=134267=edit
Xorg.0.log after the Off and On
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102800
--- Comment #4 from higu...@gmx.net ---
Created attachment 134266
--> https://bugs.freedesktop.org/attachment.cgi?id=134266=edit
dmesg after turning off and on the radeon card
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=102800
--- Comment #3 from higu...@gmx.net ---
Created attachment 134265
--> https://bugs.freedesktop.org/attachment.cgi?id=134265=edit
dmesg on boot
So sorry again :)
runpn=0 do work, but after doing "echo OFF >
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #47 from Lukas Jirkovsky ---
(In reply to Jan Vesely from comment #45)
> sounds like hung GPU. afaik amdgpu.ko does not support GPU timeout/reset yet.
> you can try reseting the GPU manually via
>
The two functions pass a partially initialized structure back to the
caller after a memset() on the destination.
This is not entirely well-defined, most compilers are sensible enough
to either keep the zero-initialization for the uninitialized members,
but gcc-4.4 does not, and it warns about
https://bugs.freedesktop.org/show_bug.cgi?id=102800
--- Comment #2 from higu...@gmx.net ---
Sorry, radeon.runpm=0 does not work too, the card was powered off, so it was
using Intel card
Enabling the dedicated card still fails with the same error.
the dmesg show this when enabling the card:
[
https://bugs.freedesktop.org/show_bug.cgi?id=102800
--- Comment #1 from Alex Deucher ---
(In reply to higuita from comment #0)
>
>
> Finally, If i boot the system with radeon.runpm=1, it works
>
> Let me know if you need more logs
runpm is enabled by default so
The structure returned from r600_audio_status() is only partially
initialized, and older gcc versions (4.3 and 4.4) warn about this:
drivers/gpu/drm/radeon/r600_hdmi.c: In function 'r600_audio_status':
drivers/gpu/drm/radeon/r600_hdmi.c:108: error: 'status.id' is used
uninitialized in this
https://bugs.freedesktop.org/show_bug.cgi?id=102800
Bug ID: 102800
Summary: DRI_PRIME regression- radeon: Failed to allocate
virtual address for buffer
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
The tracing code in the tegra drm driver can lead to excessive
stack usage in somem tegra_*_show_regs() functions:
drivers/gpu/drm/tegra/dc.c: In function 'tegra_dc_show_regs':
drivers/gpu/drm/tegra/dc.c:1639: error: the frame size of 1704 bytes is larger
than 1024 bytes
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #52 from higu...@gmx.net ---
looks like dupe from #95015
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=102417
Elizabeth changed:
What|Removed |Added
Status|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=102650
Martin Peres changed:
What|Removed |Added
Status|RESOLVED|CLOSED
---
Hello everyone,
just finished a first draft of the libdrm API and some test application:
https://github.com/tobiasjakobi/libdrm/blob/ippv2/exynos/exynos_ipp.h
https://github.com/tobiasjakobi/libdrm/blob/ippv2/tests/exynos/exynos_ipp_test.c
Needs a small patch to the kernel to prevent an Oops
Hi Kieran,
On Friday, 15 September 2017 20:49:15 EEST Kieran Bingham wrote:
> On 15/09/17 18:02, Laurent Pinchart wrote:
> > On Friday, 15 September 2017 19:42:06 EEST Kieran Bingham wrote:
> >> The pipeline needs to ensure that the hardware is idle for suspend and
> >> resume operations.
> >
>
Hi Noralf,
On Friday, 15 September 2017 20:49:26 EEST Noralf Trønnes wrote:
> Den 15.09.2017 04.27, skrev Laurent Pinchart:
> > The custom implementation just calls drm_gem_handle_delete(), which is
> > identical to the default implementation used when the operation handler
> > isn't set. Remove
On Fri, Sep 15, 2017 at 3:40 AM, Hans Verkuil wrote:
> Hi Rob,
>
> On 09/13/17 10:21, Hans Verkuil wrote:
>> On 09/12/2017 04:43 PM, Rob Herring wrote:
>>> On Thu, Aug 31, 2017 at 01:01:54PM +0200, Hans Verkuil wrote:
From: Hans Verkuil
Den 15.09.2017 04.27, skrev Laurent Pinchart:
The drm_gem_dumb_destroy() isn't used in drivers, don't export it.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/drm_dumb_buffers.c | 7 ---
drivers/gpu/drm/drm_gem.c | 1 -
2 files
Den 15.09.2017 04.27, skrev Laurent Pinchart:
The custom implementation just calls drm_gem_handle_delete(), which is
identical to the default implementation used when the operation handler
isn't set. Remove it.
Signed-off-by: Laurent Pinchart
---
Gentle review ping.
On Tuesday, 15 August 2017 16:05:45 EEST Laurent Pinchart wrote:
> Since commit 4a97a3da420b ("drm: Don't update property values for atomic
> drivers") atomic drivers must not update property values as properties
> are read from the state instead. To catch remaining users, the
https://bugzilla.kernel.org/show_bug.cgi?id=191571
--- Comment #8 from Przemek (sop...@gmail.com) ---
I cant say about all APUs, but I have tested the patch, and on MULLINS chip
this solution is working perfect.
Thanks,
Przemek.
--
You are receiving this mail because:
You are watching the
https://bugs.freedesktop.org/show_bug.cgi?id=102797
Bug ID: 102797
Summary: Running unigine superposition benchmark in wine
freezes the system
Product: Mesa
Version: git
Hardware: Other
OS: All
Hello Marek,
Marek Szyprowski wrote:
> This patch adds Exynos IPP v2 subsystem and userspace API.
>
> New userspace API is focused ONLY on memory-to-memory image processing.
> The two remainging IPP operation modes (framebuffer writeback and
> local-path output with image processing) can be
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #46 from Shmerl ---
(In reply to Jan Vesely from comment #45)
> sounds like hung GPU. afaik amdgpu.ko does not support GPU timeout/reset yet.
> you can try reseting the GPU manually via
>
Hi Kieran,
Thank you for the patch.
On Friday, 15 September 2017 19:42:07 EEST Kieran Bingham wrote:
> An early implementation of suspend-resume helpers are available in the
> CRTC module, however they are unused and no longer needed.
>
> With suspend and resume handled by the core DRM atomic
https://bugs.freedesktop.org/show_bug.cgi?id=101731
--- Comment #45 from Jan Vesely ---
(In reply to Shmerl from comment #44)
> (In reply to Lukas Jirkovsky from comment #43)
> > Here are some additional information:
>
> Yes, I observed that as well. You can access the
It wasn't protecting anything, as the single word writes used to
set up or tear down a translation are already inherently atomic,
so the spinlock is pure overhead.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_iommu.c | 7 ---
1 file changed, 7
The handler has never been used, so it's really just dead code.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_mmu.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/gpu/drm/etnaviv/etnaviv_mmu.c
b/drivers/gpu/drm/etnaviv/etnaviv_mmu.c
This is a preparation to remove the etnaviv dependency on the IOMMU
subsystem by importing the relevant parts of the iommu map/unamp
functions into the driver.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_mmu.c | 66 +++
A function doing a single assignment is not really helping the
code flow.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_iommu.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/etnaviv/etnaviv_iommu.c
Using the IOMMU API to manage the internal GPU MMU has been an
historical accident and it keeps getting in the way, as well as
entangling the driver with the inner workings of the IOMMU
subsystem.
Clean this up by removing the usage of iommu_domain, which is the
last piece linking etnaviv to the
They are not used in any way, so can go away.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_iommu.c| 21 -
drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c | 14 --
2 files changed, 35 deletions(-)
diff --git
Those functions are simple enough to fold them into the calling
function. This also fixes a correctness issue, as the alloc/free
functions didn't specifiy the device the memory was allocated for.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_iommu.c | 27
And clean up the header file a bit.
Signed-off-by: Lucas Stach
---
drivers/gpu/drm/etnaviv/etnaviv_mmu.c | 8
drivers/gpu/drm/etnaviv/etnaviv_mmu.h | 8 +---
2 files changed, 5 insertions(+), 11 deletions(-)
diff --git
Hi Kieran,
Thank you for the patch.
On Friday, 15 September 2017 19:42:06 EEST Kieran Bingham wrote:
> The pipeline needs to ensure that the hardware is idle for suspend and
> resume operations.
I'm not sure to really understand this sentence.
> Implement suspend and resume functions using the
https://bugs.freedesktop.org/show_bug.cgi?id=102417
--- Comment #15 from Chris Wilson ---
They are expected to skip, they are tests for a future feature.
--
You are receiving this mail because:
You are the assignee for the
Hi Kieran,
Thank you for the patch.
On Friday, 15 September 2017 19:42:05 EEST Kieran Bingham wrote:
> DRM pipelines utilising the VSP must stop all frame processing as part
> of the suspend operation to ensure the hardware is idle. Upon resume,
> the pipeline must not be started until the DU
https://bugs.freedesktop.org/show_bug.cgi?id=102417
--- Comment #14 from Elizabeth ---
On HSW the 3 tests are going to skip, is that expected or I'm losing some
configuration?
IGT-Version: 1.19-gc718ba8 (x86_64) (Linux: 4.13.0-drm-tip-ww37-commit-9adc9e9+
Den 15.09.2017 00.29, skrev Laurent Pinchart:
Hi Noralf,
On Wednesday, 13 September 2017 18:19:22 EEST Noralf Trønnes wrote:
Den 13.09.2017 07.09, skrev Laurent Pinchart:
On Monday, 11 September 2017 17:31:54 EEST Noralf Trønnes wrote:
Hi,
I want to start out by saying that this patchset
https://bugs.freedesktop.org/show_bug.cgi?id=102796
Bug ID: 102796
Summary: steam not rendering correctly on VEGA 56
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=102633
--- Comment #5 from Fabian Maurer ---
Sure thing, but a driver shouldn't allow to bring down the whole system, right?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102650
--- Comment #3 from Elizabeth ---
Does this need to be verified or can we closed it? Thanks.
--
You are receiving this mail because:
You are the assignee for the
https://bugzilla.kernel.org/show_bug.cgi?id=191571
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
i915.enable_dithering allows to force dithering on all outputs
on (=1) or off (=0). The default is -1 for current automatic
per-pipe selection.
This is useful for debugging and for special case scenarios,
e.g., providing simulated 10 bpc output on 8 bpc digital sinks
if a 10 bpc framebuffer +
The new module parameter enable_hw_color_correction defaults to
true, to retain the current behaviour. If set to false, it will
disable all hardware color correction, like gamma/degamma and
csc.
This is useful for debugging gamma table / csc precision problems,
and to ensure unmodified pixel
Hi,
so these two patches add i915 module parameters to globally override
how the driver handles dithering and gamma/csc conversion.
They serve two purposes: First as debug aid and "airbag" for working
around potential precision problems in getting pixels from rendering
to the display outputs.
https://bugs.freedesktop.org/show_bug.cgi?id=102633
--- Comment #4 from Samuel Pitoiset ---
Fix the app would be much better. :)
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #10 from Justin Mitzel ---
I managed to get Kernel 4.12 of amd-staging working and the problem still
persists.
--
You are receiving this mail because:
You are the assignee for the
On Thu, Sep 14, 2017 at 6:01 AM, Eric Engestrom
wrote:
> Fixes this warning:
>
> freedreno/kgsl/kgsl_ringbuffer.c: In function ‘kgsl_ringbuffer_flush’:
> freedreno/kgsl/kgsl_ringbuffer.c:149:19: warning: cast from pointer to
> integer of different size
https://bugs.freedesktop.org/show_bug.cgi?id=102633
--- Comment #3 from Fabian Maurer ---
Thanks for looking into this.
I can't really agree with the resolution though, it not working is one thing,
but it freezing the whole system is another. Can't something be done to at
Den 15.09.2017 02.45, skrev Eric Anholt:
Noralf Trønnes writes:
Den 30.08.2017 09.40, skrev Daniel Vetter:
On Tue, Aug 29, 2017 at 10:40:04AM -0700, Eric Anholt wrote:
Daniel Vetter writes:
On Mon, Aug 28, 2017 at 8:44 PM, Noralf Trønnes
On Tue, Sep 12, 2017 at 11:19:27AM +0300, Jani Nikula wrote:
> If drm_kms_helper.edid_firmware module parameter is set at
> drm_kms_helper probe time, update the new drm.edid_firmware parameter
> for backwards compatibility.
>
> The drm_kms_helper.edid_firmware is now read-only in sysfs to
On Tue, Sep 12, 2017 at 11:19:26AM +0300, Jani Nikula wrote:
> Handle debugfs override edid and firmware edid at the low level to
> transparently and completely replace the real edid. Previously, we
> practically only used the modes from the override EDID, and none of the
> other data, such as
https://bugs.freedesktop.org/show_bug.cgi?id=102694
John changed:
What|Removed |Added
CC||john.etted...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=196777
--- Comment #8 from Gerd Hoffmann (kra...@redhat.com) ---
https://www.kraxel.org/cgit/linux/log/?h=qxl-4.13
please test
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=102633
Samuel Pitoiset changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
https://bugs.freedesktop.org/show_bug.cgi?id=102633
--- Comment #1 from Samuel Pitoiset ---
Created attachment 134252
--> https://bugs.freedesktop.org/attachment.cgi?id=134252=edit
hacky patch
--
You are receiving this mail because:
You are the assignee for the
From: Christian König
When dma_fence_get_rcu() fails to acquire a reference it doesn't necessary
mean that there is no fence at all.
It usually mean that the fence was replaced by a new one and in this situation
we certainly want to have the new one as result and *NOT*
https://bugzilla.kernel.org/show_bug.cgi?id=196121
--- Comment #1 from mirh (m...@protonmail.ch) ---
Fixed in acfd6ee4fa7ebeee75511825fe02be3f7ac1d668
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel
HDMI support requires some additional off-SoC logic, so Mixer device (part
of HDMI display path) should be disabled by default in SoC dtsi and enabled
then in each board dts. This patch unifies Mixer handling with other
Exynos SoCs.
Signed-off-by: Marek Szyprowski
---
All Exynos 5250 SoCs have HDMI PHY connected via dedicated I2C bus (bus
number 8), so HDMI PHY should be defined in exynos5250.dtsi instead of
duplicating it in every board, which enable HDMI support.
Signed-off-by: Marek Szyprowski
---
Commit 2b7681326dc2 ("drm/exynos: hdmi: remove the i2c drivers and use")
merged to v3.15 kernel added a required 'ddc' property to Exynos HDMI
device tree bindings, which should point to i2c bus used for handling DDC
(mainly reading display's EDID information). It has been enough time to
convert
Hi!
This patchset performs a cleanup of HDMI (and related) device tree
nodes for various Exynos boards. There are no functional changes.
Best regards
Marek Szyprowski
Samsung R Institute Poland
Marek Szyprowski (5):
bindings: mark separate Exynos HDMI DDC node as deprecated
ARM: dts:
Commit 2b7681326dc2 ("drm/exynos: hdmi: remove the i2c drivers and use")
merged to v3.15 kernel added a required 'ddc' property to Exynos HDMI
device tree bindings, which should point to i2c bus used for handling DDC
(mainly reading display's EDID information). Since that commit
separate node with
HDMI support requires some additional off-SoC logic, so HDMI and Mixer
devices should be disabled by default in SoC dtsi and enabled then
in each board dts. This patch unifies HDMI and Mixer handling with other
Exynos SoCs.
Signed-off-by: Marek Szyprowski
---
Quoting Colin King (2017-09-15 00:05:16)
> From: Colin Ian King
>
> sg_table is being initialized and is never read before it is updated
> again later on, hence making the initialization redundant. Remove
> the initialization.
>
> Detected by clang scan-build:
>
Hi Rob,
On 09/13/17 10:21, Hans Verkuil wrote:
> On 09/12/2017 04:43 PM, Rob Herring wrote:
>> On Thu, Aug 31, 2017 at 01:01:54PM +0200, Hans Verkuil wrote:
>>> From: Hans Verkuil
>>>
>>> Document the bindings for the cec-gpio module for hardware where the
>>> CEC line
https://bugzilla.kernel.org/show_bug.cgi?id=196121
Przemek (sop...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Change the tile to:
drm/rockchip: Replace dev_* with DRM_DEV_*
Thanks.
On 2017年09月15日 14:47, Haneen Mohammed wrote:
This patch replace instances of dev_info/err/debug with
DRM_DEV_INFO/ERROR/WARN respectively inorder to use a drm-formatted
specific log messages. Issue corrected with the
On Fri, 2017-09-15 at 08:58 +0200, Julia Lawall wrote:
>
> On Fri, 15 Sep 2017, Haneen Mohammed wrote:
>
> > This patch replace instances of dev_info/err/debug with
> > DRM_DEV_INFO/ERROR/WARN respectively inorder to use a drm-formatted
> > specific log messages. Issue corrected with the help of
https://bugzilla.kernel.org/show_bug.cgi?id=191571
--- Comment #6 from Przemek (sop...@gmail.com) ---
Created attachment 258401
--> https://bugzilla.kernel.org/attachment.cgi?id=258401=edit
proposed patch
As the problem still persist in kernel 4.13 I have made a little patch for it.
With this
https://bugs.freedesktop.org/show_bug.cgi?id=102684
--- Comment #1 from Niklas Haas ---
Can't reproduce the cut-to-black issue, after several attempts (with either
'auto' or 'high' performance mode).
I did notice another issue while testing though, which is sort of
On Fri, 15 Sep 2017, Haneen Mohammed wrote:
> This patch replace instances of dev_info/err/debug with
> DRM_DEV_INFO/ERROR/WARN respectively inorder to use a drm-formatted
> specific log messages. Issue corrected with the help of the following
> Coccinelle script:
>
> @r@
> @@
>
> (
> -dev_info
85 matches
Mail list logo