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

2018-03-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105316 --- Comment #6 from tempel.jul...@gmail.com --- You are right, I've hidden the titlebar of Firefox' window and moved it to the top of the screen where I could spot tearing in windowed mode without compositor. I just hope situation can be

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

2018-03-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105316 --- Comment #5 from Michel Dänzer --- (In reply to tempel.julian from comment #4) I'm sorry, but you're just getting lucky with radeonsi. With Firefox, maybe the tearing could only occur in the title bar / toolbar area. If

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

2018-03-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105316 --- Comment #4 from tempel.jul...@gmail.com --- Thanks for still responding, despite of the closed ticket. I can assure you that with OpenGL/RadeonSI in an Xorg session, application's own vsync really does work correctly without the help of a

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

2018-03-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105316 --- Comment #3 from Michel Dänzer --- (In reply to tempel.julian from comment #2) > RadeonSI does work correctly with vsync, there is no tearing in any window That's only possible with a compositor which can prevent

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

2018-03-01 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105316 --- Comment #2 from tempel.jul...@gmail.com --- RadeonSI does work correctly with vsync, there is no tearing in any window (be it a game or application). Only Vulkan drivers are affected. And amdvlk is also affected in fullscreen. -- You are

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

2018-03-01 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105316 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED

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

2018-03-01 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105316 Bug ID: 105316 Summary: vsync in Vulkan applications doesn't work correctly with both radv and amdvlk Product: xorg Version: unspecified Hardware: x86-64 (AMD64)

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #17 from Mario Kleiner --- Hmm. That incorrect file actually looked good. DRI3+Present enabled, pageflip errors gone as expected. Date also seemed to be plausible. Are you sure that was wrong? --

[Bug 101038] Radeon 9650 (rv350): gpu reset/lockup (dri3, ppc)

2018-02-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=101038 --- Comment #9 from erhar...@mailbox.org --- Interesting finding: After I rebuilt my Gentoo on the G5 with gcc 7.3.0 the freezes are gone, only GPU lockups happen. These lockups occur more rarely and are harder to provoke, also the machine gets

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 james.coulth...@verizon.net changed: What|Removed |Added Attachment #137593|0 |1 is obsolete|

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #15 from james.coulth...@verizon.net --- Created attachment 137593 --> https://bugs.freedesktop.org/attachment.cgi?id=137593=edit Xorg.0.log of DRI Option 3 setting on 7.10 -- You are receiving this mail because: You are the

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #14 from james.coulth...@verizon.net --- (In reply to Mario Kleiner from comment #13) > If you create a file named /etc/X11/xorg.conf > > with this text snippet... > > Section "Device" > Identifier "Card0" > Driver

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #13 from Mario Kleiner --- If you create a file named /etc/X11/xorg.conf with this text snippet... Section "Device" Identifier "Card0" Driver "ati" Option "DRI" "3" EndSection

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #12 from james.coulth...@verizon.net --- Just looked at Michael's change... hah, look at that. DRI option 3 must force 32 bit depth? -- You are receiving this mail because: You are the assignee for the

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #11 from james.coulth...@verizon.net --- (In reply to Michel Dänzer from comment #10) > James, does > > Option "DRI" "3" > > avoid the problem? If so, it's probably the issue Mario mentioned. If not, > please attach the

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #10 from Michel Dänzer --- James, does Option "DRI" "3" avoid the problem? If so, it's probably the issue Mario mentioned. If not, please attach the corresponding Xorg log file again. -- You are receiving

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #9 from Mario Kleiner --- A r300, so accordign to your log, the driver uses DRI2 + EXA. I think this would hit the bug which iirc was introduced in 7.10.0 which causes pageflipping failure under

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update; display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 james.coulth...@verizon.net changed: What|Removed |Added Summary|Blank screen with only |Blank screen with only

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #8 from james.coulth...@verizon.net --- Created attachment 137560 --> https://bugs.freedesktop.org/attachment.cgi?id=137560=edit Xorg.0.log of 7.9 radeon driver session -- You are receiving this mail because: You are the assignee

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #7 from james.coulth...@verizon.net --- That fixed it. I downloaded the 7.9 *.deb. I executed: > sudo dpkg -i > xserver-xorg-video-radeon-hwe-16.04_7.9.0-0ubuntu1_16.04.1_amd64.deb > sudo apt-get -f install > sudo apt-mark hold

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #4 from james.coulth...@verizon.net --- Result of changing to modesetting driver: The system booted straight to desktop without the need to manually switch to VT7. Screen was not blank at startup; however, the screen did not display

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 Michel Dänzer changed: What|Removed |Added Attachment #137559|application/x-trash |text/plain

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #3 from james.coulth...@verizon.net --- Created attachment 137559 --> https://bugs.freedesktop.org/attachment.cgi?id=137559=edit Xorg.0.log of modesetting driver session This is the Xorg.0.log of the environment when the

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #2 from james.coulth...@verizon.net --- (In reply to Michel Dänzer from comment #1) > (In reply to james.coulthard from comment #0) > > > > It upgraded the following libraries (`/var/log/dpkg.log [pkg][old ver][new > > ver]`): > >

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 --- Comment #1 from Michel Dänzer --- (In reply to james.coulthard from comment #0) > > It upgraded the following libraries (`/var/log/dpkg.log [pkg][old ver][new > ver]`): Are those the only packages that were upgraded?

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 Michel Dänzer changed: What|Removed |Added Attachment #137544|text/x-log |text/plain

[Bug 105217] Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 james.coulth...@verizon.net changed: What|Removed |Added URL|

[Bug 105217] New: Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly grows

2018-02-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105217 Bug ID: 105217 Summary: Blank screen with only mouse pointer after 7.10 radeon driver update (mesa 17.2.8); display does not switch to tty7 upon lightdm start; Xorg.0.log quickly

[Bug 105021] suspend / rx550 / extremely slow after 2nd thaw

2018-02-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105021 Michel Dänzer changed: What|Removed |Added Component|Driver/AMDgpu |DRM/AMDgpu

[Bug 103141] RX550 / cannot send 2560x1080 via hdmi

2018-02-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103141 arne_woer...@yahoo.com changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug 103141] RX550 / cannot send 2560x1080 via hdmi

2018-02-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103141 --- Comment #3 from arne_woer...@yahoo.com --- with 4.15.0.1-MANJARO it works fine... -arne -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list

[Bug 105021] suspend / rx550 / extremely slow after 2nd thaw

2018-02-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105021 --- Comment #2 from arne_woer...@yahoo.com --- i reported it already here: 1. https://bugzilla.kernel.org/show_bug.cgi?id=198619 2. https://forum.manjaro.org/t/issue-with-resume-and-kernel-4-15/39802 and my CPU is an AMD A10-5800K... -- You

[Bug 105021] suspend / rx550 / extremely slow after 2nd thaw

2018-02-09 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=105021 --- Comment #1 from arne_woer...@yahoo.com --- Created attachment 137242 --> https://bugs.freedesktop.org/attachment.cgi?id=137242=edit 4.15.1-1-MANJARO / journalctl -r -- You are receiving this mail because: You are the assignee for the

[Bug 104914] xrandr crashes xorg server on RADEON HD10000 if started in 16 bpp mode

2018-02-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104914 Alex Deucher changed: What|Removed |Added Attachment #137130|text/x-log |text/plain

[Bug 104914] xrandr crashes xorg server on RADEON HD10000 if started in 16 bpp mode

2018-02-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104914 --- Comment #1 from Kyku --- Created attachment 137131 --> https://bugs.freedesktop.org/attachment.cgi?id=137131=edit dmesg output -- You are receiving this mail because: You are the assignee for the

[Bug 104914] New: xrandr crashes xorg server on RADEON HD10000 if started in 16 bpp mode

2018-02-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104914 Bug ID: 104914 Summary: xrandr crashes xorg server on RADEON HD1 if started in 16 bpp mode Product: xorg Version: unspecified Hardware: x86 (IA32) OS:

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

2018-01-30 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=10418 Ben Crocker changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment

[Bug 98832] Distorted colours after suspend / resume cycle

2018-01-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98832 Alex Deucher changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 104620] R9 280x (Tahiti) not working properly on Ubuntu 17.10

2018-01-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104620 --- Comment #2 from Michel Dänzer --- Please attach the corresponding Xorg log file and the output of dmesg and glxinfo. -- You are receiving this mail because: You are the assignee for the

[Bug 104617] Window is always black until resized

2018-01-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104617 --- Comment #1 from Michel Dänzer --- Please attach the corresponding Xorg log file. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati

[Bug 104620] R9 280x (Tahiti) not working properly on Ubuntu 17.10

2018-01-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104620 --- Comment #1 from Oğuz Can Soyselçuk --- Also, I don't know if this is related. But ubuntu fails to boot when i enable "IGD Multi-Monitor" from my bios settings. Both the live-cd/usb and the installed system gets

[Bug 104620] New: R9 280x (Tahiti) not working properly on Ubuntu 17.10

2018-01-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104620 Bug ID: 104620 Summary: R9 280x (Tahiti) not working properly on Ubuntu 17.10 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status:

[Bug 104617] New: Window is always black until resized

2018-01-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104617 Bug ID: 104617 Summary: Window is always black until resized Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: normal

[Bug 98832] Distorted colours after suspend / resume cycle

2018-01-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98832 --- Comment #10 from mirh --- Yes, supposedly this should have been fixed in 4.15 (18c437caa5b18a235dd65cec224eab54bebcee65) Checks it. -- You are receiving this mail because: You are the assignee for the

[Bug 104531] Cannot turn monitor off over DP cable

2018-01-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104531 --- Comment #1 from Marcin Deranek --- Created attachment 136603 --> https://bugs.freedesktop.org/attachment.cgi?id=136603=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Bug 104531] New: Cannot turn monitor off over DP cable

2018-01-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104531 Bug ID: 104531 Summary: Cannot turn monitor off over DP cable Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity:

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

2018-01-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=73116 --- Comment #10 from Hadrien Lacour --- It's worthy to say that "high" does flicker too, it just seems more rare. -- You are receiving this mail because: You are the assignee for the

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

2018-01-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=73116 --- Comment #9 from Hadrien Lacour --- It seems worthy to say that "high" does flicker too (it just seems more rare). -- You are receiving this mail because: You are the assignee for the

[Bug 104519] crash of the computer

2018-01-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104519 --- Comment #1 from arnaud --- Created attachment 136589 --> https://bugs.freedesktop.org/attachment.cgi?id=136589=edit log file -- You are receiving this mail because: You are the assignee for the

[Bug 104519] New: crash of the computer

2018-01-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104519 Bug ID: 104519 Summary: crash of the computer Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major

[Bug 102909] radeon 0000:03:00.0: ring 0 stalled for more than 10000msec

2018-01-01 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102909 Kai-Heng Feng changed: What|Removed |Added Component|Driver/Radeon |DRM/Radeon

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

2017-12-21 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=73116 --- Comment #8 from Hadrien Lacour --- Hello, another one experiencing it here (nothing in Xorg.0.log or dmesg). uname -a: Linux gentoo 4.14.8-gentoo #1 SMP Wed Dec 20 20:09:58 CET 2017 x86_64 AMD FX(tm)-8350

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

2017-12-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=92889 --- Comment #28 from Alex Deucher --- (In reply to Etienne URBAH from comment #27) > > Therefore, the origin of this issue could be the ALSA driver, and I will try > to report this issue at https://www.alsa-project.org

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

2017-12-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=92889 --- Comment #27 from Etienne URBAH --- I definitely confirm that this issue is NOT specific to AMD/ATI Tahiti XT, but also appears with following NVIDIA hardware : $ lspci -nn -v -s 1:0 01:00.0 3D controller [0302]: NVIDIA

[Bug 104216] Firefox quirks (black and/or white squares)

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

[Bug 104216] Firefox quirks (black and/or white squares)

2017-12-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104216 --- Comment #2 from Germano Massullo --- Created attachment 136092 --> https://bugs.freedesktop.org/attachment.cgi?id=136092=edit screenshot 3 -- You are receiving this mail because: You are the assignee for the

[Bug 104216] Firefox quirks (black and/or white squares)

2017-12-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104216 --- Comment #1 from Germano Massullo --- Created attachment 136091 --> https://bugs.freedesktop.org/attachment.cgi?id=136091=edit screenshot 2 -- You are receiving this mail because: You are the assignee for the

[Bug 104216] New: Firefox quirks (black and/or white squares)

2017-12-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104216 Bug ID: 104216 Summary: Firefox quirks (black and/or white squares) Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW

[Bug 104205] displayport connected monitor doesn't initialize display

2017-12-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104205 Michel Dänzer changed: What|Removed |Added QA Contact|xorg-t...@lists.x.org |

[Bug 104205] New: displayport connected monitor doesn't initialize display

2017-12-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104205 Bug ID: 104205 Summary: displayport connected monitor doesn't initialize display Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux

[Bug 33183] mouse cursor turns into thin vertical dashed line

2017-12-07 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=33183 --- Comment #50 from Michel Dänzer --- (In reply to H Zeng from comment #49) > When I was about to select texts in Konsole, suddenly the window did not > respond to my mouse click. Then I found the mouse cursor was stalked as

[Bug 103147] Radeon X600 (RV370): gpu reset/lockup (PCIe, ppc64)

2017-12-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103147 --- Comment #4 from erhar...@mailbox.org --- Had some time to test kernels 4.14.4 and 4.15-rc2. Sadly nothing new concerning this issue. -- You are receiving this mail because: You are the assignee for the

[Bug 33183] mouse cursor turns into thin vertical dashed line

2017-12-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=33183 --- Comment #49 from H Zeng --- I ran into a similar situation just now. Here is my system environment: ``` openSUSE Tumbleweed: 20171129 KDE Plasma: 5.11.3 Qt: 5.9.2 KDE Frameworks: 5.40.0 KDE Applications: 17.08.3 Kernel:

[Bug 104043] TV out garbled with linux > 3.2 (RV516)

2017-12-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104043 Alex Deucher changed: What|Removed |Added Assignee|xorg-driver-ati@lists.x.org

[Bug 104043] TV out garbled with linux > 3.2 (RV516)

2017-12-03 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104043 --- Comment #2 from Alex Deucher --- Please attach your xorg log and dmesg output. Can you bisect? -- You are receiving this mail because: You are the assignee for the

[Bug 104043] TV out garbled with linux > 3.2 (RV516)

2017-12-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104043 --- Comment #1 from frodz...@gmail.com --- Correction, the problem happens with linux versions > 3.2 -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati

[Bug 104043] TV out garbled with linux > 3.2 (RV516)

2017-12-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104043 frodz...@gmail.com changed: What|Removed |Added Summary|TV out garbled with linux > |TV out garbled with linux >

[Bug 104043] New: TV out garbled with linux > 3.16 (RV516)

2017-12-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104043 Bug ID: 104043 Summary: TV out garbled with linux > 3.16 (RV516) Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal

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

2017-11-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=92889 --- Comment #26 from Etienne URBAH --- The issue is still the same with Linux kernel 4.15.0-041500rc1 from http://kernel.ubuntu.com/~kernel-ppa/mainline -- You are receiving this mail because: You are the assignee for the

[Bug 98798] Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

2017-11-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98798 --- Comment #9 from Alex Deucher --- Created attachment 135739 --> https://bugs.freedesktop.org/attachment.cgi?id=135739=edit possible fix The attached patch makes the change. Whether the pci maintainers will accept it

[Bug 98798] Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

2017-11-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98798 --- Comment #8 from Michel Dänzer --- Joseph, before the steps outlined by Alex, make sure the firmware-amd-graphics package from stretch-backports is installed. -- You are receiving this mail because: You are the assignee

[Bug 98798] Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

2017-11-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98798 Alex Deucher changed: What|Removed |Added Resolution|--- |NOTOURBUG

[Bug 98798] Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

2017-11-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98798 Joseph Olstad changed: What|Removed |Added Hardware|Other |x86-64 (AMD64) ---

[Bug 98798] Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff

2017-11-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98798 Joseph Olstad changed: What|Removed |Added Status|RESOLVED|REOPENED

[Bug 102909] radeon 0000:03:00.0: ring 0 stalled for more than 10000msec

2017-11-25 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102909 David Faure changed: What|Removed |Added Assignee|de...@desrt.ca

[Bug 102643] xf86-video-ati 7.10.0 with EXA acceleration GDM corruption unable to log into GNOME session

2017-11-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102643 --- Comment #24 from Joakim Tjernlund --- (In reply to Michel Dänzer from comment #23) > (In reply to Joakim Tjernlund from comment #22) > > makes it build but no idea if it runs > > Looks good, can you send a

[Bug 102643] xf86-video-ati 7.10.0 with EXA acceleration GDM corruption unable to log into GNOME session

2017-11-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102643 --- Comment #23 from Michel Dänzer --- (In reply to Joakim Tjernlund from comment #22) > makes it build but no idea if it runs Looks good, can you send a patch generated with git format-patch (including your Signed-off-by

[Bug 102643] xf86-video-ati 7.10.0 with EXA acceleration GDM corruption unable to log into GNOME session

2017-11-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102643 --- Comment #22 from Joakim Tjernlund --- Just moving: --- a/src/radeon.h +++ b/src/radeon.h @@ -712,9 +712,9 @@ uint32_t radeon_get_pixmap_tiling(PixmapPtr pPix); static inline Bool

[Bug 102643] xf86-video-ati 7.10.0 with EXA acceleration GDM corruption unable to log into GNOME session

2017-11-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102643 --- Comment #21 from Joakim Tjernlund --- (In reply to Joakim Tjernlund from comment #20) > (In reply to Michel Dänzer from comment #18) > > Thanks for the report and testing the fix, but please only resolve bug >

[Bug 102643] xf86-video-ati 7.10.0 with EXA acceleration GDM corruption unable to log into GNOME session

2017-11-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=102643 --- Comment #20 from Joakim Tjernlund --- (In reply to Michel Dänzer from comment #18) > Thanks for the report and testing the fix, but please only resolve bug > reports once the fix has landed in Git. > >

[Bug 103863] Screen doesn't light up with "amdgpu.dc=1"

2017-11-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103863 Michel Dänzer changed: What|Removed |Added Component|Driver/AMDgpu |DRM/AMDgpu

[Bug 103863] Screen doesn't light up with "amdgpu.dc=1"

2017-11-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103863 --- Comment #2 from Benjamin Bellec --- I forgot to precise this is a DisplayPort connection. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 103863] Screen doesn't light up with "amdgpu.dc=1"

2017-11-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103863 --- Comment #1 from Benjamin Bellec --- Created attachment 135680 --> https://bugs.freedesktop.org/attachment.cgi?id=135680=edit dmesg log -- You are receiving this mail because: You are the assignee for the

[Bug 103863] New: Screen doesn't light up with "amdgpu.dc=1"

2017-11-23 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103863 Bug ID: 103863 Summary: Screen doesn't light up with "amdgpu.dc=1" Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 34486] Poor xterm/exa perf with ColorTiling on.

2017-11-20 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=34486 Michel Dänzer changed: What|Removed |Added Resolution|--- |WONTFIX

[Bug 34486] Poor xterm/exa perf with ColorTiling on.

2017-11-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=34486 Petr Pisar changed: What|Removed |Added Resolution|INVALID |---

[Bug 34486] Poor xterm/exa perf with ColorTiling on.

2017-11-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=34486 Andy Furniss changed: What|Removed |Added Resolution|--- |INVALID

[Bug 103771] no HDMI audio Radeon RX 460

2017-11-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103771 Alex Deucher changed: What|Removed |Added Resolution|--- |NOTABUG

[Bug 103771] no HDMI audio Radeon RX 460

2017-11-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103771 Marcelo Lacerda changed: What|Removed |Added CC|

[Bug 103771] no HDMI audio Radeon RX 460

2017-11-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103771 Marcelo Lacerda changed: What|Removed |Added OS|All |Linux

[Bug 103771] New: no HDMI audio Radeon RX 460

2017-11-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103771 Bug ID: 103771 Summary: no HDMI audio Radeon RX 460 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

2017-11-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103613 Michel Dänzer changed: What|Removed |Added Resolution|--- |FIXED

[Bug 98832] Distorted colours after suspend / resume cycle

2017-11-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98832 --- Comment #9 from Alberto --- I'm experiencing this bug with an R5 230 (basically a 6450) and linux 4.11.1. I can confirm that reverting b9729b17a414f99c61f4db9ac9f9ed987fa0cbfe solves the issue for me. Since it's a one

[Bug 103292] Rainbow screen of death on start up

2017-11-13 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103292 MaxV changed: What|Removed |Added Resolution|--- |FIXED

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

2017-11-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103613 EoD changed: What|Removed |Added Blocks||103618 Referenced Bugs:

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

2017-11-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103613 --- Comment #8 from Michel Dänzer --- (In reply to EoD from comment #7) > With and w/o the patch, there no problems when I use modesetting instead of > xf86-video-intel. > > Does this mean it's clearly an Intel issue now?

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

2017-11-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103613 --- Comment #7 from EoD --- (In reply to Michel Dänzer from comment #6) > (In reply to EoD from comment #5) > > The patch avoids the crash, but the 2ndary screen does not change. It just > > stays active (power LED is on) with a

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

2017-11-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103613 --- Comment #6 from Michel Dänzer --- (In reply to EoD from comment #5) > The patch avoids the crash, but the 2ndary screen does not change. It just > stays active (power LED is on) with a blank screen. Does that only

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

2017-11-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103613 --- Comment #5 from EoD --- (In reply to Michel Dänzer from comment #4) > Created attachment 135295 [details] [review] > Use the correct ScrnInfoPtr in redisplay_dirty > > Does this xf86-video-amdgpu patch fix it? The patch

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

2017-11-08 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103613 Michel Dänzer changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop

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