[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 --- Comment #3 from Jouni Mettälä --- Created attachment 242511 --> https://bugzilla.kernel.org/attachment.cgi?id=242511=edit recent picture of panic -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 --- Comment #4 from Jouni Mettälä --- I still get oops on 4.9-rc2. Picture is attached. It looks different than already fixed bug, for me at least. Kevin, you have probably different bug. Reboot doesn't work for me. What is last known good

[Bug 181401] New: Radeon and 5k resolution 5120x2880

https://bugzilla.kernel.org/show_bug.cgi?id=181401 Bug ID: 181401 Summary: Radeon and 5k resolution 5120x2880 Product: Drivers Version: 2.5 Kernel Version: 4.8.4 Hardware: All OS: Linux Tree: Mainline

[Bug 181401] Radeon and 5k resolution 5120x2880

https://bugzilla.kernel.org/show_bug.cgi?id=181401 --- Comment #1 from blesk2 at gmail.com --- Created attachment 242601 --> https://bugzilla.kernel.org/attachment.cgi?id=242601=edit Photo of display xrandr --output DisplayPort-0 --mode 2560x2880 --right-of DisplayPort-1 --output DisplayPort-1

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 --- Comment #5 from Michel Dänzer --- (In reply to Jouni Mettälä from comment #0) > I tried to bisect. There was some uncertainity. Still bisect said > c0d5fb4d0d9224ccaad0475c9b58740873970e7e is the first bad commit. That's a pure merge

[Bug 176961] resume from suspend not working with nvidia980 Ti, drivers 352 - 370, kernels 3.16 - 4.4

https://bugzilla.kernel.org/show_bug.cgi?id=176961 Zhang Rui changed: What|Removed |Added Component|Hibernation/Suspend |Video(DRI - non Intel)

[Bug 176961] resume from suspend not working with nvidia980 Ti, drivers 352 - 370, kernels 3.16 - 4.4

https://bugzilla.kernel.org/show_bug.cgi?id=176961 --- Comment #4 from emailjonathananderson-fedora at yahoo.com --- Good question. Can you please direct me how to test this? -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 176311] Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip

https://bugzilla.kernel.org/show_bug.cgi?id=176311 --- Comment #2 from Vedran Miletić --- Created attachment 242711 --> https://bugzilla.kernel.org/attachment.cgi?id=242711=edit dmesg -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 176311] Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip

https://bugzilla.kernel.org/show_bug.cgi?id=176311 --- Comment #3 from Vedran Miletić --- Created attachment 242721 --> https://bugzilla.kernel.org/attachment.cgi?id=242721=edit xorg log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 176311] Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip

https://bugzilla.kernel.org/show_bug.cgi?id=176311 Vedran Miletić changed: What|Removed |Added Tree|Mainline|Fedora Kernel

[Bug 183311] New: Firefox Support phone /(/1~877~424~6647/)/ Firefox phone number ::USA

https://bugzilla.kernel.org/show_bug.cgi?id=183311 Bug ID: 183311 Summary: Firefox Support phone /(/1~877~424~6647/)/ Firefox phone number ::USA Product: Drivers Version: 2.5 Kernel Version: Firefox Support phone

[Bug 178281] wine-staging apps freezes the machine with RX460

https://bugzilla.kernel.org/show_bug.cgi?id=178281 --- Comment #11 from fin4478 at hotmail.com --- I made TF2 gaming stable by disabling kernel debugging and setting cpu timer to 300Hz. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 176311] Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip

https://bugzilla.kernel.org/show_bug.cgi?id=176311 --- Comment #4 from Michel Dänzer --- Does this still happen with current xf86-video-ati Git, or at least the 7.7.1 release? -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 117181] graphic glitches for Kernel > 4.2 Intel HD 5xx and skylake

https://bugzilla.kernel.org/show_bug.cgi?id=117181 Jani Nikula changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 178281] wine-staging apps freezes the machine with RX460

https://bugzilla.kernel.org/show_bug.cgi?id=178281 --- Comment #12 from fin4478 at hotmail.com --- With Tomb Raider Legend the game hangs Xserver in one minute when playing at fullhd.Dropping resolution to 720p allows to play stable. drm-next-4.10-wip and Oipaf ppa mesa from yesterday used. There

[Bug 178281] wine-staging apps freezes the machine with RX460

https://bugzilla.kernel.org/show_bug.cgi?id=178281 --- Comment #13 from fin4478 at hotmail.com --- I tested latest drm-next-4.10-wip today that have couple of more patches that yesterday. Still Xserver hangs when playing Tomb Raider Legend at full hd. With dmesg, I have these errors at boot: [

[Bug 178281] wine-staging apps freezes the machine with RX460

https://bugzilla.kernel.org/show_bug.cgi?id=178281 --- Comment #14 from fin4478 at hotmail.com --- One hour ago published Oibaf Mesa fixed Xserver hanging when playing TR Legend at fullhd. https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/+packages -- You are receiving this mail

[Bug 178281] wine-staging apps freezes the machine with RX460

https://bugzilla.kernel.org/show_bug.cgi?id=178281 --- Comment #15 from fin4478 at hotmail.com --- New Mesa did not fix this. Playing at fullhd TR Legend still hangs xserver in 3 minutes. Tried 2 times, same effect. Works as good as with an 300Hz overclocked non debug 4.9-rc2 kernel from

[Bug 63941] Can't control brightness with ATI 5650/Intel Ironlake when switched to radeon

https://bugzilla.kernel.org/show_bug.cgi?id=63941 Jani Nikula changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 --- Comment #50 from Alex Deucher --- Your system does not appear to support powerdown of the dGPU. From your log: [9.611183] ATPX version 1, functions 0x0181 Bit 1 of the functions should be set if it does. -- You are receiving this

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 Jouni Mettälä changed: What|Removed |Added Regression|No |Yes --- Comment #6 from Jouni

[Bug 178221] radeon performance drop from 4.8 to 4.9-rc1 in Shadow of Mordor

https://bugzilla.kernel.org/show_bug.cgi?id=178221 Thorsten Leemhuis changed: What|Removed |Added CC||regressions at leemhuis.info ---

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 --- Comment #7 from Alex Deucher --- As per comment 1, shutdown was working even with the commit that adds the shutdown callback earlier in the cycle. Some other change appears to have regressed it. -- You are receiving this mail because: You

[Bug 178221] radeon performance drop from 4.8 to 4.9-rc1 in Shadow of Mordor

https://bugzilla.kernel.org/show_bug.cgi?id=178221 --- Comment #4 from Alex Deucher --- Fix pull was requested last week: https://lists.freedesktop.org/archives/dri-devel/2016-October/122110.html -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 --- Comment #8 from Borislav Petkov --- What about this one: https://lkml.kernel.org/r/3b57a593-776b-b008-a5f2-672b9343f18a at lwfinger.net I don't know the code so I can't say whether testing the ->ddc_bus ptr is the proper fix... -- You

[Bug 185681] New: amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 Bug ID: 185681 Summary: amdgpu: powerplay initialization failed Product: Drivers Version: 2.5 Kernel Version: 4.9.0-rc3-1.gb005706-vanilla Hardware: x86-64 OS: Linux

[Bug 185681] amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 Nayan Deshmukh changed: What|Removed |Added CC||nayan26deshmukh at gmail.com ---

[Bug 185681] amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #2

[Bug 185681] amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 --- Comment #3 from René Linder --- Created attachment 243361 --> https://bugzilla.kernel.org/attachment.cgi?id=243361=edit Kernel 4.8.4 dmesg Output -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 185681] amdgpu: powerplay initialization failed

https://bugzilla.kernel.org/show_bug.cgi?id=185681 --- Comment #4 from René Linder --- I going to try to revert the last Patches on Powerplay. This will need a moment. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 --- Comment #9 from Alex Deucher --- Yes, that should fix it. All of the board I tested with had a ddc bus on all connectors so it never came up before. This only triggers on really old boards with TV connectors which don't have a DDC bus for

[Bug 178421] [regression] Radeon Oops on shutdown

https://bugzilla.kernel.org/show_bug.cgi?id=178421 --- Comment #10 from Borislav Petkov --- Yap, it does. Just did two suspend-to-disk runs. Thanks. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 100871] radeon fails to initialize one DisplayPort monitor

https://bugzilla.kernel.org/show_bug.cgi?id=100871 Reg changed: What|Removed |Added CC||reg at regproctor.com --- Comment #11 from Reg

[Bug 100871] radeon fails to initialize one DisplayPort monitor

https://bugzilla.kernel.org/show_bug.cgi?id=100871 --- Comment #12 from Reg --- Created attachment 231661 --> https://bugzilla.kernel.org/attachment.cgi?id=231661=edit dmsg - All 6 screens good kernel-3.16.7-35-default -- You are receiving this mail because: You are watching the assignee of

[Bug 100871] radeon fails to initialize one DisplayPort monitor

https://bugzilla.kernel.org/show_bug.cgi?id=100871 --- Comment #13 from Reg --- Created attachment 231671 --> https://bugzilla.kernel.org/attachment.cgi?id=231671=edit Xorg.0.log - All 6 screens good kernel-3.16.7-35-default -- You are receiving this mail because: You are watching the

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 RussianNeuroMancer changed: What|Removed |Added CC||russianneuromancer at ya.ru ---

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 --- Comment #43 from Alex Deucher --- Is this still an issue with kernel 3.8? A bunch of PX fixes went into that kernel. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #34 from Kontantin Ivanov --- Created attachment 231981 --> https://bugzilla.kernel.org/attachment.cgi?id=231981=edit dmesg 4.8.0 rc4 radeon.uvd=0 radeon.dpm=0 -- You are receiving this mail because: You are watching the assignee

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #35 from Kontantin Ivanov --- Created attachment 231991 --> https://bugzilla.kernel.org/attachment.cgi?id=231991=edit Xorg.0.log 4.8.0 rc4 -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #36 from Kontantin Ivanov --- The card doesn't work with and without UVD. I've trying radeon.uvd=0 with radeon.dpm=0. Firmware from git repository. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 --- Comment #44 from Teofilis Martisius --- Hi, Last I tried it was 4.7. I removed my laptop from the quirks list and ATOMBIOS stuck in loop message still happened. I'll test this with 4.8-rc4 over the weekend. Sincerely, Teofilis -- You are

[Bug 60533] CVE-2013-7445: Remote web page triggerable DOS in Linux DRM graphics.

https://bugzilla.kernel.org/show_bug.cgi?id=60533 --- Comment #40 from Mikhail --- kernel 4.8.0-0.rc4 and interface still freeze when free memory is absent: stracing of gnome-shell: # strace -t -p 1489 strace: Process 1489 attached 19:36:11 ioctl(8, DRM_IOCTL_I915_GEM_CREATE, 0x7ffc860b7690) =

[Bug 60533] CVE-2013-7445: Remote web page triggerable DOS in Linux DRM graphics.

https://bugzilla.kernel.org/show_bug.cgi?id=60533 --- Comment #41 from Mikhail --- 17:01:49 recvmsg(29, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable) 17:01:49 poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=8, events=POLLIN}, {fd=10, events=POLLIN}, {fd=20,

[Bug 60533] CVE-2013-7445: Remote web page triggerable DOS in Linux DRM graphics.

https://bugzilla.kernel.org/show_bug.cgi?id=60533 --- Comment #42 from Mikhail --- 17:17:15 ioctl(8, DRM_IOCTL_I915_GEM_BUSY, 0x7ffd3e0c1fc0) = 0 17:17:15 ioctl(8, DRM_IOCTL_I915_GEM_SET_DOMAIN, 0x7ffd3e0c1f10) = 0 17:17:15 ioctl(8, DRM_IOCTL_I915_GEM_SW_FINISH, 0x7ffd3e0c20a0) = 0 17:17:15

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 Boris Carvajal changed: What|Removed |Added CC||boris2.9 at gmail.com --- Comment #45

[Bug 100871] radeon fails to initialize one DisplayPort monitor

https://bugzilla.kernel.org/show_bug.cgi?id=100871 Reg changed: What|Removed |Added Attachment #231661|0 |1 is obsolete|

[Bug 100871] radeon fails to initialize one DisplayPort monitor

https://bugzilla.kernel.org/show_bug.cgi?id=100871 --- Comment #15 from Reg --- Hm, I can't edit that last message. Here are a couple of corrections: Where I showed: xrandr --output DisplayPort-${1} --mode 1920x1080 sleep xrandr --output DisplayPort-${1} --mode 2560x1440 It should

[Bug 100871] radeon fails to initialize one DisplayPort monitor

https://bugzilla.kernel.org/show_bug.cgi?id=100871 --- Comment #16 from Reg --- Update: Regarding c14 (comment 14) about the ./display-on.sh. Even though running this script can turn the display on that was erroneously off during boot the display will turn itself back off after a few seconds or

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 --- Comment #46 from Teofilis Martisius --- Created attachment 232761 --> https://bugzilla.kernel.org/attachment.cgi?id=232761=edit dmesg output from 4.8-rc4 when turning OFF dGPU via vgaswitcheroo -- You are receiving this mail because: You

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 --- Comment #47 from Teofilis Martisius --- Created attachment 232771 --> https://bugzilla.kernel.org/attachment.cgi?id=232771=edit dmesg output from 4.8-rc4 with RADEON_PX_QUIRK_DISABLE_PX quirks removed -- You are receiving this mail

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 --- Comment #48 from Teofilis Martisius --- Hi, I ran two tests over the weekend. First, I tried booting up stock 4.8-rc4. glxgears runs fine both on APU and dGPU. But it fails when I try to turn OFF my dGPU by doing: echo OFF

[Bug 119831] "nomodeset" required to boot - MSI laptop G72 6QE, nouveau graphics

https://bugzilla.kernel.org/show_bug.cgi?id=119831 Peter Wu changed: What|Removed |Added CC||peter at lekensteyn.nl --- Comment #15 from

[Bug 155711] Aorus X5, Backlight hotkeys non-functional

https://bugzilla.kernel.org/show_bug.cgi?id=155711 Zhang Rui changed: What|Removed |Added Component|Power-Video |Video(DRI - non Intel)

[Bug 115011] [drm:radeon_acpi_init [radeon]] *ERROR* Cannot find a backlight controller

https://bugzilla.kernel.org/show_bug.cgi?id=115011 Luya Tshimbalanga changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug 115011] [drm:radeon_acpi_init [radeon]] *ERROR* Cannot find a backlight controller

https://bugzilla.kernel.org/show_bug.cgi?id=115011 --- Comment #14 from Alex Deucher --- You aren't seeing the message because it was removed in newer kernels. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 115011] [drm:radeon_acpi_init [radeon]] *ERROR* Cannot find a backlight controller

https://bugzilla.kernel.org/show_bug.cgi?id=115011 --- Comment #15 from Luya Tshimbalanga --- (In reply to Alex Deucher from comment #14) > You aren't seeing the message because it was removed in newer kernels. Thank you for the clarification. Should I set the status as code fix then? -- You

[Bug 115011] [drm:radeon_acpi_init [radeon]] *ERROR* Cannot find a backlight controller

https://bugzilla.kernel.org/show_bug.cgi?id=115011 Luya Tshimbalanga changed: What|Removed |Added Resolution|PATCH_ALREADY_AVAILABLE |CODE_FIX -- You are receiving this

[Bug 156651] New: The 4.7 kernel will not boot with a GTX 970

https://bugzilla.kernel.org/show_bug.cgi?id=156651 Bug ID: 156651 Summary: The 4.7 kernel will not boot with a GTX 970 Product: Drivers Version: 2.5 Kernel Version: 4.7 Hardware: Intel OS: Linux Tree:

[Bug 156651] The 4.7 kernel will not boot with a GTX 970

https://bugzilla.kernel.org/show_bug.cgi?id=156651 Pierre Moreau changed: What|Removed |Added CC||pierre.morrow at free.fr --- Comment #1

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 Kontantin Ivanov changed: What|Removed |Added Kernel Version|4.8.0-040800rc2 |4.8.0-040800rc5 -- You are

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #37 from Kontantin Ivanov --- I'm always ready to help with this bug. Actually, UVD is not important for me. But the card I want to use. May be there is some documentation how to work with similar problems... ? -- You are receiving

[Bug 155711] Aorus X5, Backlight hotkeys non-functional

https://bugzilla.kernel.org/show_bug.cgi?id=155711 --- Comment #10 from seqrteam at gmail.com --- That makes sense. In case it was something with the nvidia driver, I tried a few different nvidia driver versions (with their associated kernel modules): 352.79. 361.45, and 367.44 (the latest).

[Bug 102401] Radeon Displayport Audio Warping

https://bugzilla.kernel.org/show_bug.cgi?id=102401 --- Comment #13 from Maxqia --- Looking back with an extra year of programming knowledge, it seems like commit 7726e72b3d6879ee5fc743a230eb6f5afa12844b doesn't do anything except add a drm_detect_monitor_audio to the hdmi audio pathway ...,

[Bug 102401] Radeon Displayport Audio Warping

https://bugzilla.kernel.org/show_bug.cgi?id=102401 Maxqia changed: What|Removed |Added Attachment #185441|0 |1 is obsolete|

[Bug 117151] amdgpu: Fails to initialize R7 260x (Bonaire)

https://bugzilla.kernel.org/show_bug.cgi?id=117151 Parker Reed changed: What|Removed |Added Resolution|CODE_FIX|PATCH_ALREADY_AVAILABLE -- You are

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 Kontantin Ivanov changed: What|Removed |Added Severity|normal |low --- Comment #38 from Kontantin

[Bug 68571] GPU lockup on AMD Radeon HD6850 with DPM=1

https://bugzilla.kernel.org/show_bug.cgi?id=68571 Weber K. changed: What|Removed |Added CC||weberkai at yahoo.com.br --- Comment #78 from

[Bug 71891] 3.13 fails to boot with the radeon module

https://bugzilla.kernel.org/show_bug.cgi?id=71891 Weber K. changed: What|Removed |Added CC||weberkai at yahoo.com.br --- Comment #49 from

[Bug 68571] GPU lockup on AMD Radeon HD6850 with DPM=1

https://bugzilla.kernel.org/show_bug.cgi?id=68571 --- Comment #79 from Weber K. --- Forgot to mention: And relatime,lazytime,commit=60 in fstab I believe maybe dpm need some fs information to work well. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 71891] 3.13 fails to boot with the radeon module

https://bugzilla.kernel.org/show_bug.cgi?id=71891 --- Comment #50 from Weber K. --- Forgot to mention: And relatime,lazytime,commit=60 in fstab I believe maybe dpm need some fs information to work well. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 68571] GPU lockup on AMD Radeon HD6850 with DPM=1

https://bugzilla.kernel.org/show_bug.cgi?id=68571 --- Comment #80 from Alex Deucher --- dpm has nothing to do with the filesystem. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 68571] GPU lockup on AMD Radeon HD6850 with DPM=1

https://bugzilla.kernel.org/show_bug.cgi?id=68571 --- Comment #81 from Weber K. --- I think so as well... Anyway before, I had to put this in kernel parameters, or else, black screen and hang up during boot: radeon.dpm=0 And since I put this in grub.cfg and fstab, never had a black screen

[Bug 68571] GPU lockup on AMD Radeon HD6850 with DPM=1

https://bugzilla.kernel.org/show_bug.cgi?id=68571 --- Comment #82 from Weber K. --- Ooops... Forgot to mention... I appreciate your good work supporting kernel! Thank all of you very much! -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 68571] GPU lockup on AMD Radeon HD6850 with DPM=1

https://bugzilla.kernel.org/show_bug.cgi?id=68571 --- Comment #83 from Michel Dänzer --- (In reply to Weber K. from comment #81) > And since I put this in grub.cfg and fstab, never had a black screen again: > rootflags=relatime,lazytime,commit=60 iommu=noagp radeon.dpm=1 It could be

[Bug 172381] New: nouveau kernel module leaks memory on hibernate.

https://bugzilla.kernel.org/show_bug.cgi?id=172381 Bug ID: 172381 Summary: nouveau kernel module leaks memory on hibernate. Product: Drivers Version: 2.5 Kernel Version: 4.8rc6 Hardware: All OS: Linux Tree:

[Bug 141741] drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM

https://bugzilla.kernel.org/show_bug.cgi?id=141741 --- Comment #14 from Jose Barros --- Created attachment 239331 --> https://bugzilla.kernel.org/attachment.cgi?id=239331=edit dmesg | egrep 'drm|radeon' on 4.6.0-kali1-amd64 -- You are receiving this mail because: You are watching the

[Bug 141741] drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM

https://bugzilla.kernel.org/show_bug.cgi?id=141741 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #15

[Bug 172421] New: radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 Bug ID: 172421 Summary: radeon: allow to set the TMDS frequency by a special kernel parameter Product: Drivers Version: 2.5 Kernel Version: 4.8.0-rc7+ Hardware: All

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #1 from Elmar Stellnberger --- Created attachment 239371 --> https://bugzilla.kernel.org/attachment.cgi?id=239371=edit shipment notification: R5 230 marketed as 4K-ready -- You are receiving this mail because: You are watching

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #2 from Elmar Stellnberger --- Created attachment 239381 --> https://bugzilla.kernel.org/attachment.cgi?id=239381=edit patch introducing radeon.hdmimhz for kernel 4.8.0-rc2 -- You are receiving this mail because: You are watching

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #3

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #4 from Elmar Stellnberger --- It is not true that this card would only feature a TMDS of 297 over DP. The card I have bought does only have HDMI, DVI and 4K and it was sold as 4K-ready as you can see from the first attachement.

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #5 from Elmar Stellnberger --- ... and VGA -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #6 from Alex Deucher --- The asic supports 4K over DP or duallink DVI. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #7 from Elmar Stellnberger --- It obviously works stable over HDMI as well. Besides this I have just tested an ATI Mobility Radeon HD 2600 XT/2700 and it can provide 3840x2160_22.00 over its HDMI port with a radeon.hdmimhz of 250.

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #8 from Alex Deucher --- Running the hardware out of spec is not something we want to support. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #9 from Elmar Stellnberger --- any other opinion by someone else on this issue? -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #12 from Elmar Stellnberger --- Today I approached to try out the dual-link feature of the DVI-port. First I had verified with AOC that my u2868pqu monitor in deed supports dual-link over DVI. Then I connected the DVI output of my

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 Christian König changed: What|Removed |Added CC||deathsimple at vodafone.de ---

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 Roland Scheidegger changed: What|Removed |Added CC||rscheidegger at gmx.ch --- Comment

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #14 from Christian König --- (In reply to Roland Scheidegger from comment #13) > Personally I've always thought the risk of damaging hardware with any kind > of overclocking is just about exactly zero as long as you don't increase >

[Bug 175411] New: Using 144Hz results in unusable display

https://bugzilla.kernel.org/show_bug.cgi?id=175411 Bug ID: 175411 Summary: Using 144Hz results in unusable display Product: Drivers Version: 2.5 Kernel Version: 4.7.4 Hardware: x86-64 OS: Linux Tree: Fedora

[Bug 107381] radeon VCE init error (-110) -- AMD/Intel Mars Hybrid Graphics

https://bugzilla.kernel.org/show_bug.cgi?id=107381 Gauthier P. changed: What|Removed |Added CC||kendos.kenlen at gmail.com --- Comment

[Bug 107001] Radeon HDMI audio lost after resuming from suspend

https://bugzilla.kernel.org/show_bug.cgi?id=107001 --- Comment #3 from Timo Valtoaho --- Fix still working for 4.8.0 -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 176301] New: Fiji DisplayPort drm_crtc_helper_set_config *ERROR* failed to set mode on

https://bugzilla.kernel.org/show_bug.cgi?id=176301 Bug ID: 176301 Summary: Fiji DisplayPort drm_crtc_helper_set_config *ERROR* failed to set mode on Product: Drivers Version: 2.5 Kernel Version: 4.7.5-200.fc24.x86_64

[Bug 176311] New: Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip

https://bugzilla.kernel.org/show_bug.cgi?id=176311 Bug ID: 176311 Summary: Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip Product: Drivers Version: 2.5 Kernel Version: 4.7.5-200.fc24.x86_64

[Bug 176301] Fiji DisplayPort drm_crtc_helper_set_config *ERROR* failed to set mode on

https://bugzilla.kernel.org/show_bug.cgi?id=176301 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1

[Bug 176311] Fiji DisplayPort amdgpu_crtc_page_flip *ERROR* failed to get vblank before flip

https://bugzilla.kernel.org/show_bug.cgi?id=176311 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #1

[Bug 173041] Nouveau random hangs in g84_gr_tlb_flush (NVIDIA GT240)

https://bugzilla.kernel.org/show_bug.cgi?id=173041 madicine6 at gmail.com changed: What|Removed |Added CC||madicine6 at gmail.com ---

[Bug 153911] Nouveau driver overly verbose

https://bugzilla.kernel.org/show_bug.cgi?id=153911 --- Comment #2 from be11f157cd19c4a2ba1e9c70a38b1a74 at protonmail.com --- I apologize for exaggerating the bug. It is not as severe as I described previously but more than a inconvenience. Here's the output of a dmesg from kernel 4.8:

  1   2   3   4   5   6   7   8   9   10   >