https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #8 from Vitaly Ostrosablin ---
Attempted to run reproducer app in Xephyr. It appears exactly like on host with
Java 8 in attached screenshot. I.e. with white button. However, clicking the
button just adds the text into textarea, as
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #7 from Vitaly Ostrosablin ---
Created attachment 128804
--> https://bugs.freedesktop.org/attachment.cgi?id=128804=edit
Comparison of reproducer app under java 8 and java 7 with git mesa
Checked out two days old revision of mesa.
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #6 from Vitaly Ostrosablin ---
Yes, no problem. However, my XOrg was compiled without Xephyr, so I rebuilt it.
Unfortunately, I've decided to update mesa to latest commit as well, but it
seems that one of recent commits breaks
https://bugs.freedesktop.org/show_bug.cgi?id=99195
--- Comment #4 from Michel Dänzer ---
Any chance you can bisect Mesa?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=99236
Michel Dänzer changed:
What|Removed |Added
Component|DRM/AMDgpu |Drivers/Gallium/radeonsi
https://bugs.freedesktop.org/show_bug.cgi?id=99303
Marek Olšák changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=97879
--- Comment #47 from Marek Olšák ---
The freezes are not caused by shader compilation. I don't know what's causing
them. They are too long (even 10 seconds). A CPU profiler shows the time is not
spent in the driver. It's spent in RocketLeague.
https://bugs.freedesktop.org/show_bug.cgi?id=99303
--- Comment #4 from Hi-Angel ---
Thank you, worked for me too!
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=99303
--- Comment #3 from MWATTT ---
This patch works for me (tried on glxgears). Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=99303
--- Comment #2 from Marek Olšák ---
Created attachment 128802
--> https://bugs.freedesktop.org/attachment.cgi?id=128802=edit
possible fix
Would you please try this patch?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=99307
Alex Deucher changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99303
Alex Deucher changed:
What|Removed |Added
CC||megwattt at gmail.com
--- Comment #1
https://bugs.freedesktop.org/show_bug.cgi?id=99307
Bug ID: 99307
Summary: [r600g, bisected] Segmentation fault in every
application
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=99303
Bug ID: 99303
Summary: [REGRESSION][BISECTED] DMs are crashing on start with
"radeon"
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #42 from cyrwyn ---
I had already removed vga=788 from command line. It makes no difference. It was
meant just to set the display resolution for grub before the kernel boots.
However, grub2 now requires other instructions.
New info
https://bugs.freedesktop.org/show_bug.cgi?id=98743
--- Comment #5 from Samuel Pitoiset ---
I can't reproduce the bug. Which version of mesa/llvm are you using?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment
https://bugs.freedesktop.org/show_bug.cgi?id=99292
--- Comment #2 from Christoph Haag ---
Oops, it has the same name, so I overwrote the other one. It really should be a
new trace though.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=98520
--- Comment #26 from Michel Dänzer ---
(In reply to Eugenij Shkrigunov from comment #23)
> I have no symptoms from #99078
The bug results in incorrect shader code generation, which could cause other
symptoms. If reverting that commit doesn't
https://bugs.freedesktop.org/show_bug.cgi?id=98520
--- Comment #25 from Eugenij Shkrigunov ---
Sorry for the noise, this information may be helpful.
I have installed mesa-13.0.3, latest Steam beta (with fix libxcb, libX) and
llvm-3.9.1: "Star Conflict" randomly hang whole computer (only SysRq
https://bugs.freedesktop.org/show_bug.cgi?id=99191
--- Comment #3 from Samuel Pitoiset ---
I think the correct status should be NOTOURBUG but whatever.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=99292
--- Comment #1 from smoki ---
This is same trace like in closed bug 99191 that no driver could run normaly.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment
https://bugs.freedesktop.org/show_bug.cgi?id=99191
smoki changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=98743
--- Comment #4 from piejacker875 at gmail.com ---
Here's an apitrace
https://transfer.sh/tzF87/verdun.x86-64.trace.xz
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=98743
piejacker875 at gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugs.freedesktop.org/show_bug.cgi?id=98238
--- Comment #17 from Marek Olšák ---
The remaining bug can be an instruction scheduling issue: v_interp is moved
outside of the WQM or moved after the KILL opcode (which can break the WQM) or
moved into a branch (same issue).
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=98238
Edmondo Tommasina changed:
What|Removed |Added
CC||edmondo.tommasina at gmail.com
---
https://bugs.freedesktop.org/show_bug.cgi?id=99292
Bug ID: 99292
Summary: GPU hang in High Fidelity
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority:
https://bugs.freedesktop.org/show_bug.cgi?id=99291
Andy Furniss changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99291
--- Comment #2 from Alex Deucher ---
There is a gamma fix in the latest amd-staging-4.7 branch I just pushed. Does
that help?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=99291
--- Comment #1 from Andy Furniss ---
Forgot to put -
This is a single monitor connected via DVI.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=99291
Bug ID: 99291
Summary: R9285 amd-staging-4.7 bad gamma since drm/amd/display:
Implement gamma correction using input LUT
Product: DRI
Version: DRI git
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=98795
--- Comment #2 from Samuel Pitoiset ---
Does setting LIBGL_DRI3_DISABLE=1 help?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=99191
--- Comment #1 from Samuel Pitoiset ---
This app looks like totally buggy.
Rendering is broken with NVIDIA blob and Nouveau on Maxwell, on SKL and
radeonsi. :)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #41 from Alex Deucher ---
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.11-pclos1
root=UUID=4507d394-b92d-4d28-94a0-45eb537f32cb ro splash quiet
resume=UUID=8da19a6f-6a18-46a2-920e-f9f81125e74b nomodeset vga=788
Remove
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #40 from Tom St Denis ---
[ 12.873675] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel
modesetting.
amdgpu isn't loaded so it's kinda hard to support that config.
Why not blacklist amdgpu and remove your dm/wm
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #39 from cyrwyn ---
Created attachment 128782
--> https://bugs.freedesktop.org/attachment.cgi?id=128782=edit
dmesg
dmesg of 1/05/17
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #38 from cyrwyn ---
Created attachment 128781
--> https://bugs.freedesktop.org/attachment.cgi?id=128781=edit
Xorg.log
Xorg.log of working screen with nomodeset using fb.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #37 from cyrwyn ---
I also have an HP g121wm laptop with an A10 8700p apu/gpu chipset (carrizo R6).
Ever since the removal of the catalyst driver and replacement with the Xorg
amdgpu driver at least 6 months ago, shortly after the
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #9 from Reimar Imhof ---
(In reply to Michel Dänzer from comment #7)
> Any chance you can use git bisect to find the change between 4.8 and 4.9
> which introduced the problem?
Sorry, I can't.
> There should be a
https://bugs.freedesktop.org/show_bug.cgi?id=98897
--- Comment #22 from Alex Deucher ---
Created attachment 128780
--> https://bugs.freedesktop.org/attachment.cgi?id=128780=edit
fix
This patch should fix it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #8 from Reimar Imhof ---
Created attachment 128779
--> https://bugs.freedesktop.org/attachment.cgi?id=128779=edit
Xorg.0.log with activated Xorg amdgup driver
I found an Xorg amdgpu.conf file at the arch linux wiki:
Section
https://bugs.freedesktop.org/show_bug.cgi?id=98238
--- Comment #15 from almos ---
I confirm that Marek's patch series greatly improves the situation, but the
black transitions are not eliminated completely. The foliage is good now, but
the rocks are still bad.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=95438
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=95551
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=97338
--- Comment #6 from Samuel Pitoiset ---
A possible fix here:
https://lists.freedesktop.org/archives/mesa-dev/2017-January/139686.html
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=99285
Bug ID: 99285
Summary: Total War: Warhammer hang on campaign map
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=98856
--- Comment #1 from Samuel Pitoiset ---
Could you provide an apitrace that reproduces the issue?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=99219
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=98520
--- Comment #24 from Eugenij Shkrigunov ---
Updating llvm-3.9.1 and removing libxcb*, libX* from steam (bug #97174) fix
"Star Conflict". Sorry for inconvenience.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99019
--- Comment #8 from Samuel Pitoiset ---
Possible fix is here https://reviews.llvm.org/D28351
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
https://bugs.freedesktop.org/show_bug.cgi?id=98785
Vedran MiletiÄ changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=98785
--- Comment #4 from Vedran MiletiÄ ---
> Related LLVM bug: https://llvm.org/bugs/show_bug.cgi?id=31019
Fixed.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=98784
--- Comment #10 from network723 at rkmail.ru ---
I made traces of Talos and blender affected by this bug
I'm sorry, but I couldn't upload it anywhere else:
http://file.karelia.ru/t8766g/
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=98520
--- Comment #23 from Eugenij Shkrigunov ---
(In reply to Michel Dänzer from comment #22)
> (In reply to Eugenij Shkrigunov from comment #17)
> > I have noticed the same behaviour exactly after update llvm from 3.9.0 to
> > 3.9.1
>
> Maybe try
https://bugs.freedesktop.org/show_bug.cgi?id=99158
Christian König changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=98903
--- Comment #2 from Ernst Sjöstrand ---
This was probably an old libxcb in the steam runtime, like:
https://github.com/ValveSoftware/steam-for-linux/issues/4638
FYI.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #7 from Michel Dänzer ---
Any chance you can use git bisect to find the change between 4.8 and 4.9 which
introduced the problem?
(In reply to Reimar Imhof from comment #6)
> Do I need a special config for loading the amdgpu driver?
https://bugs.freedesktop.org/show_bug.cgi?id=98784
--- Comment #9 from Michel Dänzer ---
This is likely a Talos bug, making incorrect assumptions about the number of
buffers / the contents of the back buffer after SwapBuffers. If somebody can
make an apitrace reproducing the problem, that could
https://bugs.freedesktop.org/show_bug.cgi?id=97634
--- Comment #9 from Robin KERDILES ---
I was still getting issues with amdgpu when I tested linux 4.9 + merge from
drm-next 4.10 but the dmesg changed (another error code).
Will try another merge in next days and post the new error codes.
--
https://bugs.freedesktop.org/show_bug.cgi?id=98520
--- Comment #22 from Michel Dänzer ---
Everybody please be careful not to turn this into another report which becomes
useless due to mixing up multiple issues which aren't directly related. Lots of
different things can cause GPU hangs and other
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #15 from smoki ---
(In reply to wiak from comment #9)
> Hey i got the exact same issue with a Samsung HU7505 4k60 television using
> amdgpu on xubuntu 16.04.1/16.10, amdgpu-pro-16.50-362463 drivers work in
> 4k60 until the display is
https://bugs.freedesktop.org/show_bug.cgi?id=98604
--- Comment #11 from Michel Dänzer ---
Can you get a backtrace of a crash with gdb?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=99158
--- Comment #8 from Andy Furniss ---
(In reply to Marek Olšák from comment #7)
> Nevermind. This series should fix it for VDPAU and VAAPI:
>
> https://patchwork.freedesktop.org/series/17480/
Yea, it's OK with these, thanks.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99278
Bug ID: 99278
Summary: kwin corruption when desktop effects enabled
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #6 from Reimar Imhof ---
Just something I do not understand:
While having a look at the Xorg.log I couldn't find anything about loading
xf86-video-amdgpu.
I just found lines about
/usr/lib64/xorg/modules/drivers/ati_drv.so
and
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #5 from Reimar Imhof ---
I've attached the logs and the info about changed components.
They are all from
download.opensuse.org/repositories/X11:/XOrg/openSUSE_Leap_42.2/
The flicker problem is not about the menu but the drop down
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #4 from Reimar Imhof ---
Created attachment 128758
--> https://bugs.freedesktop.org/attachment.cgi?id=128758=edit
rpm -qa --queryformat "%{Name} - %{Version} - %{Vendor}\n" | grep
build.opensuse.org/X11
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #3 from Reimar Imhof ---
Created attachment 128757
--> https://bugs.freedesktop.org/attachment.cgi?id=128757=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #2 from Reimar Imhof ---
Created attachment 128756
--> https://bugs.freedesktop.org/attachment.cgi?id=128756=edit
dmesg.txt
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=99275
--- Comment #1 from Alex Deucher ---
Please attach your xorg log and dmesg output. Is it just the menu that
flickers or the whole screen? Did you also change any other components (mesa,
ddx, etc.)?
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=99275
Bug ID: 99275
Summary: Kernel 4.9: amdgpu regression; gui flickers; amd
radeon rx 460
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux
https://bugs.freedesktop.org/show_bug.cgi?id=99019
--- Comment #7 from Samuel Pitoiset ---
Thanks for the info Marek, this helped me to figure out the issue.
I have a fix locally for that hang, will think more before sending it though.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #3 from Samuel Pitoiset ---
It seems like the issue has been recently fixed.
I can't reproduce it with the following config:
OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.3.0 /
4.8.13-1-ARCH, LLVM 4.0.0)
OpenGL core
https://bugs.freedesktop.org/show_bug.cgi?id=99120
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #27 from
https://bugs.freedesktop.org/show_bug.cgi?id=99120
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=99120
--- Comment #26 from Larry <5lokuf+c77xmvwa3y1jk at sharklasers.com> ---
(In reply to Arek RuÅniak from comment #25)
> Hi, before you start reinstall whole system you can always try:
>
> 1) check this all things with completely new user
https://bugs.freedesktop.org/show_bug.cgi?id=99019
--- Comment #6 from Marek Olšák ---
The shader ends up in an infinite loop because of this:
...
v_cmpx_le_f32_e32 vcc, 0, v0
s_branch BB0_30
s_cbranch_execnz BB0_30
; BB#29:
exp null off, off, off, off done vm
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #14 from wiak at nwgat.net ---
Created attachment 128750
--> https://bugs.freedesktop.org/attachment.cgi?id=128750=edit
amdgpu-pro-xrandr.log
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #13 from wiak at nwgat.net ---
Created attachment 128749
--> https://bugs.freedesktop.org/attachment.cgi?id=128749=edit
amdgpu-pro-xorg.log
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #12 from wiak at nwgat.net ---
Created attachment 128748
--> https://bugs.freedesktop.org/attachment.cgi?id=128748=edit
amdgpu-pro-dmesg
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #11 from wiak at nwgat.net ---
Created attachment 128747
--> https://bugs.freedesktop.org/attachment.cgi?id=128747=edit
xrandr
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #10 from wiak at nwgat.net ---
Created attachment 128746
--> https://bugs.freedesktop.org/attachment.cgi?id=128746=edit
xorg log
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #9 from wiak at nwgat.net ---
Hey i got the exact same issue with a Samsung HU7505 4k60 television using
amdgpu on xubuntu 16.04.1/16.10, amdgpu-pro-16.50-362463 drivers work in 4k60
until the display is turned off and then it gives
https://bugs.freedesktop.org/show_bug.cgi?id=98333
--- Comment #8 from wiak at nwgat.net ---
Created attachment 128745
--> https://bugs.freedesktop.org/attachment.cgi?id=128745=edit
dmesg log
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=99120
--- Comment #25 from Arek RuÅniak ---
Hi, before you start reinstall whole system you can always try:
*) check this all things with completly new user account
*) try switch to modesetting ddx
*) clean xorg.conf.d/* (make backup before)
--
https://bugs.freedesktop.org/show_bug.cgi?id=99158
--- Comment #7 from Marek Olšák ---
Nevermind. This series should fix it for VDPAU and VAAPI:
https://patchwork.freedesktop.org/series/17480/
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=99158
--- Comment #6 from Marek Olšák ---
We could get a race if vlVdpOutputSurfaceDMABuf is called from a different
thread than the context is normally used with. Can that happen?
You can try to test this:
diff --git
https://bugs.freedesktop.org/show_bug.cgi?id=99158
--- Comment #5 from Christian König ---
Yeah and that actually makes sense, by using linear layout you also disable
DCC.
Does using R600_DEBUG=nodcc help as well?
Marek please take a look at the backtraces in the first post. It sounds like
https://bugs.freedesktop.org/show_bug.cgi?id=99120
--- Comment #24 from Larry <5lokuf+c77xmvwa3y1jk at sharklasers.com> ---
Switching to amd-staging-4.7 with the fc25 provided mesa-13.0.2 didn't change
anything. However, Booting into fc25 liveusb (and installing some stuff) shows
that weston and
https://bugs.freedesktop.org/show_bug.cgi?id=98238
--- Comment #14 from Arek RuÅniak ---
Edmondo, these patches made big difference but not resolved all "black
transition". Some wooden surfaces flickers still (rx470 too)
But It's still better then before commit
https://bugs.freedesktop.org/show_bug.cgi?id=97055
--- Comment #15 from Thomas J. Moore ---
(In reply to SET from comment #13)
> My HP laptop with AMD A10-7300 (Kaveri iGPU, Topaz dGPU) has a fully working
> X up to kernel 4.9 (not beyond) with these module options applied as such :
Thanks. I
https://bugs.freedesktop.org/show_bug.cgi?id=98604
--- Comment #10 from smoki ---
(In reply to Chris Rankin from comment #9)
> (In reply to smoki from comment #8)
> > Does this still work for you with DRI2? Asking becuase DRI2 seems now
> > affected also.
>
> I can't say, because Adobe has now
https://bugs.freedesktop.org/show_bug.cgi?id=98604
--- Comment #9 from Chris Rankin ---
(In reply to smoki from comment #8)
> Does this still work for you with DRI2? Asking becuase DRI2 seems now
> affected also.
I can't say, because Adobe has now "upgraded" its Flash plugin to v24 and
removed
https://bugs.freedesktop.org/show_bug.cgi?id=99120
--- Comment #23 from Larry <5lokuf+c77xmvwa3y1jk at sharklasers.com> ---
Thank you for going to the trouble of checking internally.
(In reply to Tom St Denis from comment #22)
> Chatting internally one of our developers also has a VERDE with a
https://bugs.freedesktop.org/show_bug.cgi?id=98604
--- Comment #8 from smoki ---
(In reply to Chris Rankin from comment #5)
> I don't see your point here. AFAIK the Flash plugin knows nothing about
> either DRI2 or DRI3, and it works fine with DRI2...
Does this still work for you with DRI2?
https://bugs.freedesktop.org/show_bug.cgi?id=99253
Alex Deucher changed:
What|Removed |Added
QA Contact|mesa-dev at lists.freedesktop. |dri-devel at
lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=98238
--- Comment #13 from Edmondo Tommasina ---
This series from Marek fixes the issue for me (RX 470):
https://lists.freedesktop.org/archives/mesa-dev/2017-January/139432.html
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99261
--- Comment #3 from Alex Deucher ---
(In reply to SET from comment #2)
> I tried to bisect for the first time, here's what I did :
>
> git bisect start
> git bisect bad
> git bisect good v4.9
> Bisecting: 5782 revisions left to test after this
https://bugs.freedesktop.org/show_bug.cgi?id=99261
--- Comment #2 from SET ---
I tried to bisect for the first time, here's what I did :
git bisect start
git bisect bad
git bisect good v4.9
Bisecting: 5782 revisions left to test after this (roughly 13 steps)
https://bugs.freedesktop.org/show_bug.cgi?id=99264
--- Comment #1 from Daniël Mantione ---
Created attachment 128735
--> https://bugs.freedesktop.org/attachment.cgi?id=128735=edit
Xorg log file (no weird things are visible here)
--
You are receiving this mail because:
You are the assignee
101 - 200 of 32557 matches
Mail list logo