https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #51 from ReddestDream ---
Also, just FYI, it does look like there are some fixes to display type
detection on AMD GPUs coming in 5.3-rc2. These might fix or at least improve
the multimonitor issue on Radeon VII:
https://bugzilla.kernel.org/show_bug.cgi?id=204345
--- Comment #6 from Joaquin Otsoa (edisonalvari...@bol.com.br) ---
it doesn't happen with 4.19.61 lts. I think it will be easier to check all the
5.1 rc and check when this was introduced.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=111236
--- Comment #5 from KJ Liew ---
Here's the gdb stack-trace with debug build. If you need the same test video
clip, this is what I used
Test h264 clip:
$ youtube-dl -f mp4 https://www.youtube.com/watch?v=azvR__GRQic
Thread 4 "multiqueue0:src"
https://bugzilla.kernel.org/show_bug.cgi?id=204345
--- Comment #5 from Joaquin Otsoa (edisonalvari...@bol.com.br) ---
unfortunately the bug was introduced in 5.1.0 so this is going to take
thousands of commits, I'll do my best.
--
You are receiving this mail because:
You are watching the
https://bugs.freedesktop.org/show_bug.cgi?id=111236
--- Comment #4 from KJ Liew ---
The ArchLinux build does have symbols. When I used my own build
(b_ndebug=if-release), I got better details on vaPutImage() with more detailed
args, but still nothing from radeonsi_dri.so.
Did you actually mean
https://bugzilla.kernel.org/show_bug.cgi?id=204345
Joaquin Otsoa (edisonalvari...@bol.com.br) changed:
What|Removed |Added
Summary|Unigine Superposition hard |Unigine
https://bugzilla.kernel.org/show_bug.cgi?id=204345
Joaquin Otsoa (edisonalvari...@bol.com.br) changed:
What|Removed |Added
Kernel Version|5.1.18 |5.1.20
--
https://bugzilla.kernel.org/show_bug.cgi?id=204345
Joaquin Otsoa (edisonalvari...@bol.com.br) changed:
What|Removed |Added
Summary|Unigine Superposition |Unigine
https://bugzilla.kernel.org/show_bug.cgi?id=204345
--- Comment #4 from Joaquin Otsoa (edisonalvari...@bol.com.br) ---
interesting, kernel 5.2.3 doesn't hard lock the PC, but fps drop, abnormally
(like with 5.1.20) but when looking at the final results, it's not that bad,
about 5% performance hit.
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #71 from Yury Zhuravlev ---
Can somebody try games without any fps limits?
Like vblank_mode=0 and in-game limits.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110813
--- Comment #4 from Yury Zhuravlev ---
but still, exist but close to
https://bugs.freedesktop.org/show_bug.cgi?id=102322 now.
If I remove FPS limit in-game and mesa it's working stable.
Problems somewhere in power management and if card needs
https://bugzilla.kernel.org/show_bug.cgi?id=204345
--- Comment #3 from Joaquin Otsoa (edisonalvari...@bol.com.br) ---
I should be more precise it doesn't crash really it hard locks the pc
completely only the reset button will fix the problem.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=204345
--- Comment #2 from Joaquin Otsoa (edisonalvari...@bol.com.br) ---
With ubuntu ppa vanilla kernel this happens as well.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=204345
--- Comment #1 from Joaquin Otsoa (edisonalvari...@bol.com.br) ---
This is with Linux Mint (Ubuntu 18.04.2 LTS really) I forgot to mention that
this is with the liquorix kernel, maybe I should try with vanilla kernel first.
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=204345
Bug ID: 204345
Summary: Unigine Superposition benchmark notoriously unstable
since 5.1.18 (and possibly before)
Product: Drivers
Version: 2.5
Kernel Version: 5.1.18
https://bugs.freedesktop.org/show_bug.cgi?id=111236
--- Comment #3 from Ilia Mirkin ---
(In reply to Ilia Mirkin from comment #2)
> (In reply to Andre Klapper from comment #1)
> > Can you please compile with debug symbols and provide an updated stacktrace?
>
> Why bother? Isn't the issue pretty
https://bugs.freedesktop.org/show_bug.cgi?id=111236
--- Comment #2 from Ilia Mirkin ---
(In reply to Andre Klapper from comment #1)
> Can you please compile with debug symbols and provide an updated stacktrace?
Why bother? Isn't the issue pretty obvious? mesa calls memcpy, libc thinks that
it's
https://bugs.freedesktop.org/show_bug.cgi?id=111236
--- Comment #1 from Andre Klapper ---
Can you please compile with debug symbols and provide an updated stacktrace?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=111236
Bug ID: 111236
Summary: VA-API radeonsi SIGSEGV __memmove_avx_unaligned
Product: Mesa
Version: 19.1
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=111235
Bug ID: 111235
Summary: radeonsi_drv_video.so should report support for packed
headers
Product: Mesa
Version: git
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=111234
Bug ID: 111234
Summary: amdgpu bug: kernel NULL pointer dereference during
video playback
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS:
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #70 from Mauro Gaspari ---
(In reply to Sylvain BERTRAND from comment #69)
> Don't forget to provide the software stack used:
>
> which sofware (game, cad...)? wine/dxvk? native?
Good point. Games being tested:
Pillars of
https://bugs.freedesktop.org/show_bug.cgi?id=111233
--- Comment #1 from Charles Fursdon ---
Created attachment 144893
--> https://bugs.freedesktop.org/attachment.cgi?id=144893=edit
Xorg.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111233
Bug ID: 111233
Summary: Navi10 not booting to desktop - amdgpu_job_timedout
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111232
Bug ID: 111232
Summary: 3200 Memory Crash My System
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity:
Signed-off-by: Pei Hsuan Hung
Cc: triv...@kernel.org
---
arch/powerpc/kernel/eeh.c | 2 +-
arch/powerpc/platforms/cell/spufs/switch.c | 4 ++--
drivers/extcon/extcon-rt8973a.c | 2 +-
drivers/gpu/drm/arm/malidp_regs.h | 2
https://bugs.freedesktop.org/show_bug.cgi?id=111231
Bas Nieuwenhuizen changed:
What|Removed |Added
QA Contact||dri-devel@lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #11 from deltasquared ---
Some additional information I had neglected to mention in the initial
description in the "excitement" of filing my first bug here...
Relevant hardware is as stated a ryzen 2200G running solely on
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #10 from deltasquared ---
Created attachment 144890
--> https://bugs.freedesktop.org/attachment.cgi?id=144890=edit
Observed graphical corruption - right hand side of monitor
Other side of above.
The sky colour is otherwise
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #9 from deltasquared ---
Created attachment 144889
--> https://bugs.freedesktop.org/attachment.cgi?id=144889=edit
Observed graphical corruption - left hand side of monitor
Taken in two photos as my screen's a rather large one.
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Version|XOrg git|unspecified
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #8 from deltasquared ---
Created attachment 144888
--> https://bugs.freedesktop.org/attachment.cgi?id=144888=edit
dmesg output from boot to stopping dmesg when killing xorg was possible
In this case I was able to kill xorg and
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #7 from deltasquared ---
Created attachment 144887
--> https://bugs.freedesktop.org/attachment.cgi?id=144887=edit
dmesg log from boot to running apitrace replay on the above apitrace trace file
Notably there are a lot more
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Attachment #144884|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Attachment #144883|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #4 from deltasquared ---
Oh dear, it seems I'm getting in a bit of a muddle with the attachments, please
bear with.
--
You are receiving this mail because:
You are the assignee for the
Don't forget to provide the software stack used:
which sofware (game, cad...)? wine/dxvk? native?
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #3 from deltasquared ---
Created attachment 144884
--> https://bugs.freedesktop.org/attachment.cgi?id=144884=edit
apitrace replay --verbose --debug: stderr
stderr of the same as above.
I made them separate as it helped me to have
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #69 from Sylvain BERTRAND ---
Don't forget to provide the software stack used:
which sofware (game, cad...)? wine/dxvk? native?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #2 from deltasquared ---
Created attachment 144883
--> https://bugs.freedesktop.org/attachment.cgi?id=144883=edit
apitrace replay --verbose --debug: stdout
NB: stderr attached separately.
Note that it stops after a certain swap
https://bugs.freedesktop.org/show_bug.cgi?id=111231
--- Comment #1 from deltasquared ---
Created attachment 144882
--> https://bugs.freedesktop.org/attachment.cgi?id=144882=edit
API trace that can reliably cause GPU protection faults on a ryzen 2200G
The adformentioned "dodgy" apitrace trace
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Summary|VM_L2_PROTECTION_FAULT when |random
|loading
https://bugs.freedesktop.org/show_bug.cgi?id=111231
deltasquared changed:
What|Removed |Added
Summary|VM_L2_PROTECTION_FAULT |VM_L2_PROTECTION_FAULT when
https://bugs.freedesktop.org/show_bug.cgi?id=111231
Bug ID: 111231
Summary: VM_L2_PROTECTION_FAULT
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #68 from Mauro Gaspari ---
(In reply to Sylvain BERTRAND from comment #67)
> > ...
> > Vulkan/DXVK
>
> The bugs may be in wine/DXVK then. You should report to a bug to them and
> link
> this bug to theirs.
If any of you opened
Hi
> # modetest -M atmel-lcdc -a -s ...
>
> does not work btw. It just exists without anything shown on the panel.
Looking at the modetest src -a requires both a primary plane + an overlay.
If either is missing modetest just exists with no errors printed.
Another opportunity to improve error
On Fri, Jul 26, 2019 at 07:23:01PM +0200, Andrzej Pietrasiewicz wrote:
> Use the ddc pointer provided by the generic connector.
>
> Signed-off-by: Andrzej Pietrasiewicz
Acked-by: Maxime Ripard
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Hi Daniel.
> > >
> > > *Any* hints why modetest fails when my driver reports the correct formats?
> >
> > Every driver to date supports XR24. So modetest uses that by default.
> > But this fails with your driver since it's an unsupported format.
> > Something like:
> >
> > modetest -M atmel-lcdc
Hi all.
Thanks for the responses.
It turns out this was a PICNIC error
(Problem In Chair, Not In Computer)
On Fri, Jul 26, 2019 at 10:36:26PM +0200, Sam Ravnborg wrote:
> Hi all.
>
> The Atmel at91sam9263 has a nice LCDC IP core that supports several
> formats:
> DRM_FORMAT_XBGR,
https://bugzilla.kernel.org/show_bug.cgi?id=204331
gr...@sub.red changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
50 matches
Mail list logo
