https://bugzilla.kernel.org/show_bug.cgi?id=199749
--- Comment #15 from notsyncing (song...@gmail.com) ---
Still freezed under two Android source compilation + 2 intellij idea + 10
firefox tabs + EVE online playing after 3 hours. Sysrq does not work, need hard
reset. No log was recorded.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=107013
Bug ID: 107013
Summary: Include stdint.h in drm.h
Product: DRI
Version: XOrg git
Hardware: Other
OS: Mac OS X (All)
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=107012
--- Comment #5 from Timothy Pearson ---
Confirm that latest patch works on a Radeon RX 470.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-dev
https://bugs.freedesktop.org/show_bug.cgi?id=107012
Timothy Pearson changed:
What|Removed |Added
Attachment #140294|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=106942
--- Comment #1 from Andrey Grodzovsky ---
Seems like your SW queue to insert commands to HW is full and hence Xorg is
stuck waiting for available space in the queue for the new command to be
inserted. We changed the architecture off the SW sche
https://bugs.freedesktop.org/show_bug.cgi?id=107012
--- Comment #3 from Timothy Pearson ---
Comment on attachment 140294
--> https://bugs.freedesktop.org/attachment.cgi?id=140294
Fix crashes
Review of attachment 140294:
-
I wasn'
https://bugs.freedesktop.org/show_bug.cgi?id=106970
--- Comment #2 from Andrey Grodzovsky ---
What's the scenario ?
Please check if your git tree contains this change -
drm/scheduler: Avoid using wait_event_killable for dying process
Andrey
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=107012
--- Comment #2 from Simon McVittie ---
(In reply to Simon McVittie from comment #1)
> Shouldn't this be a signed char, to make the size of the struct the same on
> all architectures?
I should have said: to make the size of this field the same a
https://bugs.freedesktop.org/show_bug.cgi?id=107012
--- Comment #1 from Simon McVittie ---
Comment on attachment 140294
--> https://bugs.freedesktop.org/attachment.cgi?id=140294
Fix crashes
Review of attachment 140294:
-
::: src/
On Sat, Jun 23, 2018 at 6:20 PM, Fabio Estevam wrote:
> Hi Russell,
>
> On Thu, Jun 21, 2018 at 7:23 AM, Russell King - ARM Linux
> wrote:
>> When removing and reloading the etnaviv module, the following splat
>> occurs:
>
> We are missing to call platform_device_unregister() in etnaviv_exit().
>
https://bugs.freedesktop.org/show_bug.cgi?id=106879
--- Comment #6 from javcasalc ---
setting amdgpu.runpm=0 didn't make any difference ... :(
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-deve
https://bugs.freedesktop.org/show_bug.cgi?id=107012
Bug ID: 107012
Summary: [PATCH] Radeon SI driver not architecture safe,
crashes on ppc64[el]
Product: Mesa
Version: git
Hardware: PowerPC
OS: All
From: Fabio Estevam
Russell King reported:
"When removing and reloading the etnaviv module, the following splat
occurs:
sysfs: cannot create duplicate filename '/devices/platform/etnaviv'
CPU: 0 PID: 1471 Comm: modprobe Not tainted 4.17.0+ #1608
Hardware name: Marvell Dove (Cubox)
Backtrace:
[]
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #11 from José Pekkarinen ---
aw, and yes, if I don't blacklist the module, the trace happens, which
certainly blows my mind, as it's built in, modprobe shouldn't affect it.
José.
--
You are receiving this mail because:
You are the
Hi Russell,
On Thu, Jun 21, 2018 at 7:23 AM, Russell King - ARM Linux
wrote:
> When removing and reloading the etnaviv module, the following splat
> occurs:
We are missing to call platform_device_unregister() in etnaviv_exit().
Calling platform_device_unregister() like in the patch from the lin
https://bugs.freedesktop.org/show_bug.cgi?id=104854
--- Comment #10 from José Pekkarinen ---
Created attachment 140293
--> https://bugs.freedesktop.org/attachment.cgi?id=140293&action=edit
dri config to work it around.
I spent some more time toying this around and I found that, building
the dr
Hi Thierry
On Tue, 2018-06-12 at 14:59 -0600, Rob Herring wrote:
> On Mon, Jun 04, 2018 at 01:16:48PM +0200, Christoph Fritz wrote:
> > This patch adds support for Innolux G070Y2-L01 7" WVGA (800x480) TFT LCD
> > panel.
> >
> > Signed-off-by: Christoph Fritz
> > ---
> > .../bindings/display/pan
I haven't thought through this comment all that hard but would it make
sense to have three timestamps, CPU, GPU, CPU so that you have error bars
on the GPU timestamp? At the very least, two timestamps would be better
than one so that, when we pull it into the kernel, it can provide something
m
This extension adds a single function to query the current GPU
timestamp, just like glGetInteger64v(GL_TIMESTAMP, ×tamp). This
function is needed to complete the implementation of
GOOGLE_display_timing, which needs to be able to correlate GPU and CPU
timestamps.
v2: Adopt Jason Ekstrand's codi
This extension fetches the current GPU timestamp from the hardware,
just like the OpenGL API glGetInteger64v(GL_TIMESTAMP, ×tamp)
function.
I need this to correlate GPU and CPU timestamps for the
GOOGLE_display_timing extension, but I think it will be useful for
applications as well.
I'm not sure
This extension adds a single function to query the current GPU
timestamp, just like glGetInteger64v(GL_TIMESTAMP, ×tamp). This
function is needed to complete the implementation of
GOOGLE_display_timing, which needs to be able to correlate GPU and CPU
timestamps.
v2: Adopt Jason Ekstrand's codi
This extension adds a single function to query the current GPU
timestamp, just like glGetInteger64v(GL_TIMESTAMP, ×tamp). This
function is needed to complete the implementation of
GOOGLE_display_timing, which needs to be able to correlate GPU and CPU
timestamps.
Signed-off-by: Keith Packard
---
https://bugs.freedesktop.org/show_bug.cgi?id=105018
--- Comment #35 from Adam Bolte ---
I believe I've been seeing the same bug as of late.
[Sat Jun 23 23:02:04 2018] [ cut here ]
[Sat Jun 23 23:02:04 2018] kernel BUG at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amd
https://bugs.freedesktop.org/show_bug.cgi?id=106363
--- Comment #6 from Gregor Münch ---
Thanks for your explanations Alex.
Maybe useful for other:
It turned out that Steam client has probably a bug preventing screensaver
getting active.
https://github.com/ValveSoftware/steam-for-linux/issues/5
24 matches
Mail list logo
