[Bug 106293] Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 --- Comment #6 from Theo --- Created attachment 139546 --> https://bugs.freedesktop.org/attachment.cgi?id=139546=edit Another backtrace (In reply to Michel Dänzer from comment #4) > Can you maybe also provide > the output

[Bug 106293] Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 --- Comment #5 from Theo --- Created attachment 139545 --> https://bugs.freedesktop.org/attachment.cgi?id=139545=edit Desired Xorg log for floating point exception caused by Mathematica (In reply to Michel Dänzer from

[Bug 106293] Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 --- Comment #4 from Michel Dänzer --- Please attach the corresponding Xorg log file. So far, this looks like an X server bug: cpp == 0 in radeon_alloc_pixmap_bo, which means pixmap->drawable.bitsPerPixel <= 7 after

[Bug 10418] Powerbook DVI out only works when booted with monitor attached

https://bugs.freedesktop.org/show_bug.cgi?id=10418 Alex Deucher changed: What|Removed |Added Status|NEEDINFO|RESOLVED

[Bug 87992] X crash because si_restrict_performance_levels_before_switch(?)

https://bugs.freedesktop.org/show_bug.cgi?id=87992 Öyvind Saether changed: What|Removed |Added Status|NEEDINFO|RESOLVED

[Bug 106293] Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 --- Comment #3 from Theo --- Created attachment 139349 --> https://bugs.freedesktop.org/attachment.cgi?id=139349=edit GDB backtrace Mathematica 11.1.1 floating point exception -- You are receiving this mail because: You

[Bug 106327] Kwin/AmdGPU driver crash when Hit Alt + Tab

https://bugs.freedesktop.org/show_bug.cgi?id=106327 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 106309] MST Multi-Stream Transport Kills All Displays Using Radeon Driver On Radeon HD 7570

https://bugs.freedesktop.org/show_bug.cgi?id=106309 --- Comment #2 from pl...@riseup.net --- >Is there a particular reason you filed this against the Xorg driver instead of >the kernel driver? No it kills all displays right after the kernel is loaded and xorg isn't started so I know it's related

[Bug 106327] Kwin/AmdGPU driver crash when Hit Alt + Tab

https://bugs.freedesktop.org/show_bug.cgi?id=106327 Viktor Kecskes changed: What|Removed |Added CC|

[Bug 106327] New: Kwin/AmdGPU driver crash when Hit Alt + Tab

https://bugs.freedesktop.org/show_bug.cgi?id=106327 Bug ID: 106327 Summary: Kwin/AmdGPU driver crash when Hit Alt + Tab Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 106293] Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 --- Comment #2 from Michel Dänzer --- Can you get a gdb backtrace of the crash? -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati

[Bug 106309] MST Multi-Stream Transport Kills All Displays Using Radeon Driver On Radeon HD 7570

https://bugs.freedesktop.org/show_bug.cgi?id=106309 --- Comment #1 from Michel Dänzer --- Is there a particular reason you filed this against the Xorg driver instead of the kernel driver? If you really think there's a Xorg driver issue, we'd need to see the Xorg log file and

[Bug 106293] Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 --- Comment #1 from Theo --- The exact Mathematica version is 11.1.1.0. The error happens independent of desktop environment or logged-in user. The crash happens only with options "AccelMethod" "glamor" and "DRI" "2". With

[Bug 106309] New: MST Multi-Stream Transport Kills All Displays Using Radeon Driver On Radeon HD 7570

https://bugs.freedesktop.org/show_bug.cgi?id=106309 Bug ID: 106309 Summary: MST Multi-Stream Transport Kills All Displays Using Radeon Driver On Radeon HD 7570 Product: xorg Version: unspecified Hardware: Other

[Bug 106293] New: Floating point exception

https://bugs.freedesktop.org/show_bug.cgi?id=106293 Bug ID: 106293 Summary: Floating point exception Product: xorg Version: 7.6 (2010.12) Hardware: Other OS: All Status: NEW Severity: normal

[Bug 96396] Segfault in Xorg after RADEON(0): Failed to make 28944x66x32bpp GBM bo

https://bugs.freedesktop.org/show_bug.cgi?id=96396 --- Comment #12 from Theo --- I get the same kind of error on a current openSUSE Tumbleweed: (EE) RADEON(0): Failed to make 9893x308x32bpp GBM bo with backtrace messages about libglamoregl.so as in OP's X.Org log. It

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 Michel Dänzer changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #9 from Grazvydas Ignotas --- Created attachment 138960 --> https://bugs.freedesktop.org/attachment.cgi?id=138960=edit *drmmode_crtc printout -- You are receiving this mail because: You are the assignee for

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #8 from Michel Dänzer --- (In reply to Grazvydas Ignotas from comment #7) > Anything wrong with just checking if drmmode_crtc->scanout_damage is not > NULL? That would just be a band-aid.

[Bug 106149] New: X fails to start with Raven Ridge APU and 1440p monitor on DVI

https://bugs.freedesktop.org/show_bug.cgi?id=106149 Bug ID: 106149 Summary: X fails to start with Raven Ridge APU and 1440p monitor on DVI Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS:

[Bug 106149] X fails to start with Raven Ridge APU and 1440p monitor on DVI

https://bugs.freedesktop.org/show_bug.cgi?id=106149 --- Comment #1 from Öyvind Saether --- Created attachment 138949 --> https://bugs.freedesktop.org/attachment.cgi?id=138949=edit xorg log of xorg failure to start -- You are receiving this mail because: You are the

[Bug 106149] X fails to start with Raven Ridge APU and 1440p monitor on DVI

https://bugs.freedesktop.org/show_bug.cgi?id=106149 Öyvind Saether changed: What|Removed |Added Resolution|--- |WONTFIX

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 sam.halli...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 sam.halli...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 --- Comment #6 from sam.halli...@gmail.com --- This seems to be much better in kernel build 4.16.2-2-ARCH and I no longer need the amdgpu.dc=0 kernel flag. -- You are receiving this mail because: You are the assignee for the

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #7 from Grazvydas Ignotas --- No it doesn't (both original patch and the one that was pushed). Anything wrong with just checking if drmmode_crtc->scanout_damage is not NULL? amdgpu_scanout_update() already does

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #6 from Michel Dänzer --- Does https://patchwork.freedesktop.org/patch/217412/ prevent this, by any chance? -- You are receiving this mail because: You are the assignee for the

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #5 from Grazvydas Ignotas --- Created attachment 138672 --> https://bugs.freedesktop.org/attachment.cgi?id=138672=edit gdb log Strange, it reproduces for me on a fresh wine prefix (which means everything on

[Bug 105573] AddScreen/ScreenInit failed for gpu driver 0 -1 / amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=105573 Michel Dänzer changed: What|Removed |Added Assignee|xorg-t...@lists.x.org

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #4 from Michel Dänzer --- Thanks, but unfortunately, the attached executable crashes for me. Does it depend on anything in particular being installed in the Wine prefix, or any specific Wine configuration? Any

[Bug 60011] Radeon HD 7690M XT black laptop screen after boot, plug+unplug external monitor workaround fix

https://bugs.freedesktop.org/show_bug.cgi?id=60011 Benny Ammitzbøll changed: What|Removed |Added Status|RESOLVED|CLOSED

[Bug 60011] Radeon HD 7690M XT black laptop screen after boot, plug+unplug external monitor workaround fix

https://bugs.freedesktop.org/show_bug.cgi?id=60011 Benny Ammitzbøll changed: What|Removed |Added Status|NEW

[Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core)

https://bugs.freedesktop.org/show_bug.cgi?id=105911 Michel Dänzer changed: What|Removed |Added CC|

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #3 from Grazvydas Ignotas --- Created attachment 138644 --> https://bugs.freedesktop.org/attachment.cgi?id=138644=edit wine's dxgi test exe You need to build wine from source, I'm using the 64bit version, which

[Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core)

https://bugs.freedesktop.org/show_bug.cgi?id=105911 --- Comment #4 from Matthias Nagel --- Created attachment 138636 --> https://bugs.freedesktop.org/attachment.cgi?id=138636=edit xorg log under kernel 4.16.0 -- You are receiving this mail because: You are the

[Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core)

https://bugs.freedesktop.org/show_bug.cgi?id=105911 --- Comment #2 from Matthias Nagel --- Created attachment 138634 --> https://bugs.freedesktop.org/attachment.cgi?id=138634=edit dmesg output of kernel 4.16.0 -- You are receiving this mail because: You are the

[Bug 105911] DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core)

https://bugs.freedesktop.org/show_bug.cgi?id=105911 --- Comment #1 from Matthias Nagel --- Created attachment 138633 --> https://bugs.freedesktop.org/attachment.cgi?id=138633=edit dmesg output of kernel 4.14.32 -- You are receiving this mail because: You are the

[Bug 105911] New: DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core)

https://bugs.freedesktop.org/show_bug.cgi?id=105911 Bug ID: 105911 Summary: DVI-D monitor connected to DVI-I output not detected (regression from kernel 4.14.32 to kernel 4.16.0 using graphic core) Product: xorg

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 --- Comment #5 from sam.halli...@gmail.com --- Unfortunately, making a video would be extremely difficult. The flashes are completely random, I have not found any way to reproduce it and sometimes it can be 30 minutes or an hour without a

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #2 from Michel Dänzer --- Do you have any pointers to information about how to run this test? -- You are receiving this mail because: You are the assignee for the

[Bug 105299] Hotplug eGPU crashes xorg

https://bugs.freedesktop.org/show_bug.cgi?id=105299 Michel Dänzer changed: What|Removed |Added Assignee|xorg-driver-ati@lists.x.org

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 --- Comment #4 from Michel Dänzer --- Does it also happen with amdgpu.dc=0 on the kernel command line? Can you make a video showing what the flashes look like? -- You are receiving this mail because: You are the assignee

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 Michel Dänzer changed: What|Removed |Added Attachment #138362|text/x-log |text/plain

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 Michel Dänzer changed: What|Removed |Added Attachment #138361|text/x-log |text/plain

[Bug 105837] 0 AD Graphics Corruption

https://bugs.freedesktop.org/show_bug.cgi?id=105837 Michel Dänzer changed: What|Removed |Added QA Contact|xorg-t...@lists.x.org

[Bug 105837] 0 AD Graphics Corruption

https://bugs.freedesktop.org/show_bug.cgi?id=105837 --- Comment #1 from Sherif --- Screenshots can be found in the given URL. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing

[Bug 105837] 0 AD Graphics Corruption

https://bugs.freedesktop.org/show_bug.cgi?id=105837 Sherif changed: What|Removed |Added URL|

[Bug 105837] New: 0 AD Graphics Corruption

https://bugs.freedesktop.org/show_bug.cgi?id=105837 Bug ID: 105837 Summary: 0 AD Graphics Corruption Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity:

[Bug 105824] RX 550: Screen corruption with compton (regression)

https://bugs.freedesktop.org/show_bug.cgi?id=105824 Dave Gilbert changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug 105824] RX 550: Screen corruption with compton (regression)

https://bugs.freedesktop.org/show_bug.cgi?id=105824 --- Comment #1 from Christoph Haag --- With a current xorg git + mesa git stack I don't have that problem, but I had it and made bug 104597. tl;dr: workaround should be allow_rgb10_configs=false compton or the

[Bug 105824] New: RX 550: Screen corruption with compton (regression)

https://bugs.freedesktop.org/show_bug.cgi?id=105824 Bug ID: 105824 Summary: RX 550: Screen corruption with compton (regression) Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW

[Bug 98832] Distorted colours after suspend / resume cycle

https://bugs.freedesktop.org/show_bug.cgi?id=98832 Alex Deucher changed: What|Removed |Added Status|REOPENED|RESOLVED

[Bug 98832] Distorted colours after suspend / resume cycle

https://bugs.freedesktop.org/show_bug.cgi?id=98832 --- Comment #14 from Alex Deucher --- (In reply to Christoph Lutz from comment #12) > I still can reproduce the bug on a current bionic system (which has 4.15 now) Sounds like you may be seeing a different bug. -- You

[Bug 98832] Distorted colours after suspend / resume cycle

https://bugs.freedesktop.org/show_bug.cgi?id=98832 --- Comment #13 from Christoph Lutz --- One possible workaround for this bug is setting the kernel (module) parameter radeon.dpm=0 -- You are receiving this mail because: You are the assignee for the

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 --- Comment #3 from sam.halli...@gmail.com --- Created attachment 138362 --> https://bugs.freedesktop.org/attachment.cgi?id=138362=edit Xorg.0.log -- You are receiving this mail because: You are the assignee for the

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 --- Comment #2 from sam.halli...@gmail.com --- Created attachment 138361 --> https://bugs.freedesktop.org/attachment.cgi?id=138361=edit dmesg.log -- You are receiving this mail because: You are the assignee for the

[Bug 105744] randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 --- Comment #1 from Alex Deucher --- Please attach your dmesg output and xorg log. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati

[Bug 105299] Hotplug eGPU crashes xorg

https://bugs.freedesktop.org/show_bug.cgi?id=105299 --- Comment #1 from Alex Deucher --- Does it work properly if you use the amdgpu xorg driver rather than modesetting? Please also attach your dmesg output. -- You are receiving this mail because: You are the assignee

[Bug 105744] New: randomly flashing screen with RX 580

https://bugs.freedesktop.org/show_bug.cgi?id=105744 Bug ID: 105744 Summary: randomly flashing screen with RX 580 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal

[Bug 105736] xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 --- Comment #1 from Grazvydas Ignotas --- Created attachment 138348 --> https://bugs.freedesktop.org/attachment.cgi?id=138348=edit workaround patch This patch workarounds the issue and wine's tests run to completion. --

[Bug 105736] New: xorg/amdgpu crash when running wine's dxgi tests

https://bugs.freedesktop.org/show_bug.cgi?id=105736 Bug ID: 105736 Summary: xorg/amdgpu crash when running wine's dxgi tests Product: xorg Version: git Hardware: Other OS: All Status: NEW Severity: normal

[Bug 73116] [R9 270x] Intermittent flickering of entire screen

https://bugs.freedesktop.org/show_bug.cgi?id=73116 --- Comment #11 from Jan Vlug --- This issue seems to be manifest for a whole range of AMD Radeon GPUs under Gnome on Wayland after resume from suspend. See: https://bugs.freedesktop.org/show_bug.cgi?id=105729 -- You

[Bug 73116] [R9 270x] Intermittent flickering of entire screen

https://bugs.freedesktop.org/show_bug.cgi?id=73116 Jan Vlug changed: What|Removed |Added See Also|

[Bug 105299] Hotplug eGPU crashes xorg

https://bugs.freedesktop.org/show_bug.cgi?id=105299 Lucas P. changed: What|Removed |Added Assignee|xorg-t...@lists.x.org |xorg-driver-ati@lists.x.org

[Bug 105573] AddScreen/ScreenInit failed for gpu driver 0 -1 / amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=105573 CthUlhUzzz changed: What|Removed |Added Assignee|xorg-driver-ati@lists.x.org

[Bug 105573] AddScreen/ScreenInit failed for gpu driver 0 -1 / amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=105573 Michel Dänzer changed: What|Removed |Added Attachment #138173|application/x-trash |text/plain

[Bug 105573] AddScreen/ScreenInit failed for gpu driver 0 -1 / amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=105573 CthUlhUzzz changed: What|Removed |Added Component|Server/DDX/Xorg |Driver/AMDgpu

[Bug 105530] Stuttering on Raven Ridge when TearFree is on

https://bugs.freedesktop.org/show_bug.cgi?id=105530 Michel Dänzer changed: What|Removed |Added Attachment #138142|text/x-log |text/plain

[Bug 105530] Stuttering on Raven Ridge when TearFree is on

https://bugs.freedesktop.org/show_bug.cgi?id=105530 Michel Dänzer changed: What|Removed |Added Attachment #138141|text/x-log |text/plain

[Bug 105526] Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 --- Comment #7 from Hamish Wilson --- Just got my updates and everything is working fine again. Thanks for all that you do guys. :-) -- You are receiving this mail because: You are the assignee for the

[Bug 105530] Stuttering on Raven Ridge when TearFree is on

https://bugs.freedesktop.org/show_bug.cgi?id=105530 --- Comment #3 from txtsd --- → glxinfo | grep -i "OpenGL" OpenGL vendor string: X.Org OpenGL renderer string: AMD RAVEN (DRM 3.25.0 /

[Bug 105530] Stuttering on Raven Ridge when TearFree is on

https://bugs.freedesktop.org/show_bug.cgi?id=105530 --- Comment #2 from txtsd --- Created attachment 138143 --> https://bugs.freedesktop.org/attachment.cgi?id=138143=edit xrandr --verbose -- You are receiving this mail because: You are the assignee for

[Bug 105530] Stuttering on Raven Ridge when TearFree is on

https://bugs.freedesktop.org/show_bug.cgi?id=105530 txtsd changed: What|Removed |Added CC|

[Bug 105530] New: Stuttering on Raven Ridge when TearFree is on

https://bugs.freedesktop.org/show_bug.cgi?id=105530 Bug ID: 105530 Summary: Stuttering on Raven Ridge when TearFree is on Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 105526] Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 105526] Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 --- Comment #5 from Ernst Sjöstrand --- https://lists.freedesktop.org/archives/amd-gfx/2018-March/020141.html was released today, maybe helps? -- You are receiving this mail because: You are the assignee for the

[Bug 105526] Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 Hamish Wilson changed: What|Removed |Added Attachment #138137|0 |1 is

[Bug 105526] Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 --- Comment #3 from Hamish Wilson --- Created attachment 138139 --> https://bugs.freedesktop.org/attachment.cgi?id=138139=edit journalctl output -- You are receiving this mail because: You are the assignee for the

[Bug 105526] Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 --- Comment #2 from Hamish Wilson --- Created attachment 138138 --> https://bugs.freedesktop.org/attachment.cgi?id=138138=edit Error Message This is the error that appears after Xorg dies and I am returned to the console.

[Bug 105526] Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 --- Comment #1 from Hamish Wilson --- Created attachment 138137 --> https://bugs.freedesktop.org/attachment.cgi?id=138137=edit jouranctl output -- You are receiving this mail because: You are the assignee for the

[Bug 105526] New: Consistent crashes with Zaphod mode after update

https://bugs.freedesktop.org/show_bug.cgi?id=105526 Bug ID: 105526 Summary: Consistent crashes with Zaphod mode after update Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 98832] Distorted colours after suspend / resume cycle

https://bugs.freedesktop.org/show_bug.cgi?id=98832 Christoph Lutz changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #9 from Petrus --- Downgrading to xorg-server-1.19.5 solves the problem, too. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 92889] Sound output using DisplayPort is NOT played during the first 3-5 seconds (on several audio hardware)

https://bugs.freedesktop.org/show_bug.cgi?id=92889 --- Comment #29 from Etienne URBAH --- The issue is still the same with Linux kernel 4.16.0-041600rc5 from http://kernel.ubuntu.com/~kernel-ppa/mainline -- You are receiving this mail because: You are the assignee for the

[Bug 105431] New: coredump trying to stop xorg (Radeon RX 550)

https://bugs.freedesktop.org/show_bug.cgi?id=105431 Bug ID: 105431 Summary: coredump trying to stop xorg (Radeon RX 550) Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #7 from Daniel --- I can't seem to reproduce the crash atm, so I am posting a snippet of the syslog of the time this crash probably appeared. Both EXA or the modesetting driver are indeed avoiding the

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #6 from Daniel --- Created attachment 137934 --> https://bugs.freedesktop.org/attachment.cgi?id=137934=edit /var/log/messages during X crash -- You are receiving this mail because: You are the assignee

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #5 from Michel Dänzer --- The Xorg log file shows a crash 1734 seconds after boot. Does anything appear in dmesg around the same time? Can you bisect xserver to find the first commit this happens with? Note that

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #4 from Daniel --- Created attachment 137861 --> https://bugs.freedesktop.org/attachment.cgi?id=137861=edit Xorg.0.log -- You are receiving this mail because: You are the assignee for the

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #3 from Michel Dänzer --- Please attach the Xorg log file corresponding to a failure. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #2 from Daniel --- Kernel 4.15.7, mesa 18.0.0_rc4, libdrm 2.4.91 -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati

[Bug 105381] [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 --- Comment #1 from Daniel --- Created attachment 137860 --> https://bugs.freedesktop.org/attachment.cgi?id=137860=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Bug 105381] New: [RV710][DRM] Invalid command stream

https://bugs.freedesktop.org/show_bug.cgi?id=105381 Bug ID: 105381 Summary: [RV710][DRM] Invalid command stream Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 105364] Driver hangs with xorg / git head

https://bugs.freedesktop.org/show_bug.cgi?id=105364 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 105364] Driver hangs with xorg / git head

https://bugs.freedesktop.org/show_bug.cgi?id=105364 --- Comment #3 from Greg White --- Indeed. That fixed it. Thanks! -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list

[Bug 105364] Driver hangs with xorg / git head

https://bugs.freedesktop.org/show_bug.cgi?id=105364 --- Comment #2 from Michel Dänzer --- (In reply to Greg White from comment #0) > No log file is produced. A log file is always produced, maybe look in ~/.local/share/xorg/ . > This is with the latest xorg from git. If

[Bug 105364] Driver hangs with xorg / git head

https://bugs.freedesktop.org/show_bug.cgi?id=105364 --- Comment #1 from Greg White --- Modesetting does still function. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list

[Bug 105364] New: Driver hangs with xorg / git head

https://bugs.freedesktop.org/show_bug.cgi?id=105364 Bug ID: 105364 Summary: Driver hangs with xorg / git head Product: xorg Version: git Hardware: Other OS: All Status: NEW Severity: normal

[Bug 105316] vsync in Vulkan applications doesn't work correctly with both radv and amdvlk

https://bugs.freedesktop.org/show_bug.cgi?id=105316 --- Comment #8 from tempel.jul...@gmail.com --- Well, I guess it's acceptable for an enthusiast who wants to play without vsync to press a hotkey before starting a game to change TearFree behavior. :) -- You are receiving this mail because:

[Bug 105316] vsync in Vulkan applications doesn't work correctly with both radv and amdvlk

https://bugs.freedesktop.org/show_bug.cgi?id=105316 --- Comment #7 from Michel Dänzer --- (In reply to tempel.julian from comment #6) > Else one would need some ugly workaround like starting another Xorg session > without TearFree if the goal is to play a game without vsync

<    6   7   8   9   10   11   12   13   14   15   >