[Bug 118701] x86_64 GMA500 reports /dev/dri/card0: failed to set DRM interface version 1.4: Inappropriate ioctl for device

https://bugzilla.kernel.org/show_bug.cgi?id=118701 --- Comment #3 from Patrik Jakobsson --- Created attachment 217321 --> https://bugzilla.kernel.org/attachment.cgi?id=217321&action=edit Add compat ioctl Turns out we didn't have compat_ioctl hooked up. Does the patch I attached fix your proble

[Bug 118611] Using the 4.6 Kernel causes one Radeon screen to intermittently power cycle.

https://bugzilla.kernel.org/show_bug.cgi?id=118611 --- Comment #3 from K. Paden --- Here you are, -Khalid On 05/23/2016 09:35 PM, bugzilla-daemon at bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=118611 > > --- Comment #2 from Michel Dänzer --- > Also, please attach

[Bug 118611] Using the 4.6 Kernel causes one Radeon screen to intermittently power cycle.

https://bugzilla.kernel.org/show_bug.cgi?id=118611 --- Comment #4 from K. Paden --- Created attachment 217341 --> https://bugzilla.kernel.org/attachment.cgi?id=217341&action=edit DMESG.txt -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 117411] [radeon][HD5650][REDWOOD][bisected] X.Org multiple delays during server start

https://bugzilla.kernel.org/show_bug.cgi?id=117411 no.spam.to.me at ish.de changed: What|Removed |Added Regression|No |Yes Summary|[radeon]

[Bug 118911] New: [radeon][HD5650][REDWOOD] DPM stalls boot for 16 seconds

https://bugzilla.kernel.org/show_bug.cgi?id=118911 Bug ID: 118911 Summary: [radeon][HD5650][REDWOOD] DPM stalls boot for 16 seconds Product: Drivers Version: 2.5 Kernel Version: at least since 3.16 Hardware: All

[Bug 118911] [radeon][HD5650][REDWOOD] DPM stalls boot for 16 seconds

https://bugzilla.kernel.org/show_bug.cgi?id=118911 --- Comment #1 from no.spam.to.me at ish.de --- Created attachment 217471 --> https://bugzilla.kernel.org/attachment.cgi?id=217471&action=edit snipped dmesg of kernel 4.6.0 with deactivated dpm -- You are receiving this mail because: You are w

[Bug 118701] x86_64 GMA500 reports /dev/dri/card0: failed to set DRM interface version 1.4: Inappropriate ioctl for device

https://bugzilla.kernel.org/show_bug.cgi?id=118701 --- Comment #4 from Stuart Foster --- (In reply to Patrik Jakobsson from comment #3) > Created attachment 217321 [details] > Add compat ioctl > > Turns out we didn't have compat_ioctl hooked up. Does the patch I attached > fix your problem? Hi

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 Wilfried Klaebe changed: What|Removed |Added CC||linux-kernel at lebenslange-ma

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #12 from Lukas Wunner --- Thanks for the report, Wilfried. Could you please create attachments with dmesg output and Xorg output, both with and without this commit. Your kernel config and Xorg config (if any) would also be helpful. Do

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #13 from Wilfried Klaebe --- Created attachment 217521 --> https://bugzilla.kernel.org/attachment.cgi?id=217521&action=edit config of non-working Linux 4.6.0 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #14 from Wilfried Klaebe --- Created attachment 217531 --> https://bugzilla.kernel.org/attachment.cgi?id=217531&action=edit config of working Linux 4.6.0 (with commit reverted) -- You are receiving this mail because: You are the as

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #15 from Wilfried Klaebe --- Created attachment 217541 --> https://bugzilla.kernel.org/attachment.cgi?id=217541&action=edit kern.log / dmesg of non-working Linux 4.6.0 -- You are receiving this mail because: You are the assignee fo

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #16 from Wilfried Klaebe --- Created attachment 217551 --> https://bugzilla.kernel.org/attachment.cgi?id=217551&action=edit kern.log / dmesg of working Linux 4.6.0 (commit reverted) -- You are receiving this mail because: You are t

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #17 from Wilfried Klaebe --- Created attachment 217561 --> https://bugzilla.kernel.org/attachment.cgi?id=217561&action=edit Xorg.log on non-working Linux 4.6.0 -- You are receiving this mail because: You are the assignee for the bu

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #18 from Wilfried Klaebe --- Created attachment 217571 --> https://bugzilla.kernel.org/attachment.cgi?id=217571&action=edit Xorg.log on working Linux 4.6.0 (commit reverted) -- You are receiving this mail because: You are the assig

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #19 from Wilfried Klaebe --- Created attachment 217581 --> https://bugzilla.kernel.org/attachment.cgi?id=217581&action=edit refind_linux.conf of both cases -- You are receiving this mail because: You are the assignee for the bug.

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #20 from Wilfried Klaebe --- No Xorg config. Especially nothing special for intel or radeon. No special rEFInd features. Files attached. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 118701] x86_64 GMA500 reports /dev/dri/card0: failed to set DRM interface version 1.4: Inappropriate ioctl for device

https://bugzilla.kernel.org/show_bug.cgi?id=118701 --- Comment #5 from Patrik Jakobsson --- Thanks for testing, queued for next and stable -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #21 from Lukas Wunner --- If you revert 4eebd5a4e7269 ("apple-gmux: lock iGP IO to protect from vgaarb changes") instead of 704ab614ec12, does the issue go away? https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #22 from Wilfried Klaebe --- The issue goes away too, then. I don't currently see any difference to when I reverted 704ab614ec12. Xorg comes up on boot like it also did with 4.5.4 (and 4.5.5). -- You are receiving this mail because:

[Bug 85351] 3.17-rc5 hangs on Supermicro X8DAH system

https://bugzilla.kernel.org/show_bug.cgi?id=85351 Joseph Bisch changed: What|Removed |Added CC||joseph.bisch at hpe.com --- Comment #2 fro

[Bug 85351] 3.17-rc5 hangs on Supermicro X8DAH system

https://bugzilla.kernel.org/show_bug.cgi?id=85351 --- Comment #3 from Joseph Bisch --- Created attachment 217761 --> https://bugzilla.kernel.org/attachment.cgi?id=217761&action=edit kern.log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 85351] 3.17-rc5 hangs on Supermicro X8DAH system

https://bugzilla.kernel.org/show_bug.cgi?id=85351 --- Comment #4 from Ralf-Peter Rohbeck --- I blacklisted mgag200 to fix it. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 118611] Using the 4.6 Kernel causes one Radeon screen to intermittently power cycle.

https://bugzilla.kernel.org/show_bug.cgi?id=118611 --- Comment #5 from K. Paden --- Sorry, I am not familiar with git-bisect. It is kernel 4.6. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 118611] Using the 4.6 Kernel causes one Radeon screen to intermittently power cycle.

https://bugzilla.kernel.org/show_bug.cgi?id=118611 --- Comment #6 from Michel Dänzer --- Enter "git bisect howto" in your favourite web search engine. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 118701] x86_64 GMA500 reports /dev/dri/card0: failed to set DRM interface version 1.4: Inappropriate ioctl for device

https://bugzilla.kernel.org/show_bug.cgi?id=118701 Stuart Foster changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #23 from Lukas Wunner --- I've e-mailed Bruno Prémont, author of 4eebd5a4e7269, and cc'ed platform-driver-x86: http://www.spinics.net/lists/platform-driver-x86/msg08889.html I've also cc'ed you but your e-mail address isn't working,

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 --- Comment #24 from Wilfried Klaebe --- Oops, fixed (and double-checked) that email issue. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 119181] New: Hang in amdgpu_vm_bo_update_mapping with powerplay enabled

https://bugzilla.kernel.org/show_bug.cgi?id=119181 Bug ID: 119181 Summary: Hang in amdgpu_vm_bo_update_mapping with powerplay enabled Product: Drivers Version: 2.5 Kernel Version: 4.5.4 Hardware: All OS:

[Bug 119181] Hang in amdgpu_vm_bo_update_mapping with powerplay enabled

https://bugzilla.kernel.org/show_bug.cgi?id=119181 --- Comment #1 from Hristo Venev --- The hang does not occur when the power state is set to low. There are also no rendering glitches (otherwise some frames seem to have random triangles on them). -- You are receiving this mail because: You are

[Bug 119211] New: amdgpu disables fan by default

https://bugzilla.kernel.org/show_bug.cgi?id=119211 Bug ID: 119211 Summary: amdgpu disables fan by default Product: Drivers Version: 2.5 Kernel Version: 4.5.5 Hardware: All OS: Linux Tree: Fedora St

[Bug 119211] amdgpu disables fan by default

https://bugzilla.kernel.org/show_bug.cgi?id=119211 --- Comment #1 from Vedran Miletić --- You should produce some GPU load before the fan activates. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 119211] amdgpu disables fan by default

https://bugzilla.kernel.org/show_bug.cgi?id=119211 --- Comment #2 from Stas Sergeev --- Even besides the fact that GPU was so hot I couldn't even touch it? -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 119211] amdgpu disables fan by default

https://bugzilla.kernel.org/show_bug.cgi?id=119211 --- Comment #3 from Stas Sergeev --- Essentially, when driver initializes, it puts 0 to /sys/class/hwmon/hwmon0/pwm1. And unless you set up fancontrol (which is a major pita), this 0 remain there, no matter how you load you GPU. It should put som

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with active graphics card use.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #19 from Dionisus Torimens --- Ok, true, the issue is still there. No, not multi-GPU. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 88541] Resume of HDMI port fails

https://bugzilla.kernel.org/show_bug.cgi?id=88541 --- Comment #1 from Harald Brennich --- Some new results with openSuse 13.2 : Kernel 3.16.7-32-desktop: suspend/resume work outs of the box Kernel 3.16.7-32-vanilla: external monitor connected via HDMI stays black after resume from suspend -- Yo

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #7 from Dionisus Torimens --- Created attachment 203781 --> https://bugzilla.kernel.org/attachment.cgi?id=203781&action=edit Temperature Graph 1 I'm having some doubts about the temperature hypothesis now. With DPM active, there se

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #8 from Dionisus Torimens --- Created attachment 203791 --> https://bugzilla.kernel.org/attachment.cgi?id=203791&action=edit Temperature Graph BAPM=1 It looks like with BAPM it might more likely be overheating. But I can't reproduc

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #9 from Dionisus Torimens --- Booting with radeon.hard_reset=1 I get this error at the point where I usually get a hang: GPU lockup (current fence id 0x4aa1 last fence id 0x4aa8 on ring 0) -- You are receivin

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #10 from Dionisus Torimens --- Created attachment 203801 --> https://bugzilla.kernel.org/attachment.cgi?id=203801&action=edit Temperature Graph Hard off radeon.fastfb=1 radeon.pcie_gen2=1 radeon.audio=0 radeon.hard_reset=1 Ok, hard

[Bug 89521] Radeon driver fails to set dpm power state after resume from S3

https://bugzilla.kernel.org/show_bug.cgi?id=89521 varikonniemi at hush.com changed: What|Removed |Added CC||varikonniemi at hush.com --- Co

[Bug 76321] Incorrect hwmon temperature when radeon card is turned off

https://bugzilla.kernel.org/show_bug.cgi?id=76321 Pali Rohár changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 112781] New: radeon: f95429e "only init fbdev if we have connectors" breaks suspend on Clevo P170EM laptop

https://bugzilla.kernel.org/show_bug.cgi?id=112781 Bug ID: 112781 Summary: radeon: f95429e "only init fbdev if we have connectors" breaks suspend on Clevo P170EM laptop Product: Drivers Version: 2.5 Kernel Version: 4.5-rc2

[Bug 112921] New: Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 Bug ID: 112921 Summary: Lock-up after screensaver on radeon Product: Drivers Version: 2.5 Kernel Version: 4.4 Hardware: x86-64 OS: Linux Tree: Mainline

[Bug 112921] Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 Jean Delvare changed: What|Removed |Added Regression|No |Yes --- Comment #1 from Jean Delvare ---

[Bug 112921] Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 --- Comment #2 from Jean Delvare --- Created attachment 204371 --> https://bugzilla.kernel.org/attachment.cgi?id=204371&action=edit dmesg output -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 112921] Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 --- Comment #3 from Jean Delvare --- Created attachment 204381 --> https://bugzilla.kernel.org/attachment.cgi?id=204381&action=edit Xorg.0.log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 112921] Lock-up after screensaver on radeon

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

[Bug 113051] New: Crash on resume

https://bugzilla.kernel.org/show_bug.cgi?id=113051 Bug ID: 113051 Summary: Crash on resume Product: Drivers Version: 2.5 Kernel Version: 4.5rc5 Hardware: All OS: Linux Tree: Mainline Status: NEW

[Bug 113051] Crash on resume

https://bugzilla.kernel.org/show_bug.cgi?id=113051 --- Comment #1 from Michel Dänzer --- Please attach the full dmesg output leading up to this. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 112921] Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 Jean Delvare changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from Jean Delvare

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #11 from Dionisus Torimens --- If you'd like any information please let me know now. Because it seems there is not much interest in finding the problem. So I'll have to and will switch back to the proprietary driver. (It turned out t

[Bug 112921] Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 Jean Delvare changed: What|Removed |Added Status|NEEDINFO|ASSIGNED --- Comment #6 from Jean Delvare

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #12 from Dionisus Torimens --- [Wonderful, fglrx doesn't work at all with kernel 4.2... ...] The fastest way to get the system to overheat is to - enable redshift (or probably xgamma) - disable vsync - set dpm to preformance* echo pe

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 Dionisus Torimens changed: What|Removed |Added Attachment #203781|0 |1 is obsolete|

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #13 from Dionisus Torimens --- Created attachment 206301 --> https://bugzilla.kernel.org/attachment.cgi?id=206301&action=edit Temperature Graph with nomodeset radeon.modeset=1 and redshift -- You are receiving this mail because: Y

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #14 from Dionisus Torimens --- Created attachment 206311 --> https://bugzilla.kernel.org/attachment.cgi?id=206311&action=edit Temperature Graph with nomodeset radeon.modeset=1 without redshift -- You are receiving this mail becaus

[Bug 113341] New: GPU Lockup on AMD Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=113341 Bug ID: 113341 Summary: GPU Lockup on AMD Kaveri Product: Drivers Version: 2.5 Kernel Version: 4.4.2 Hardware: x86-64 OS: Linux Tree: Mainline Sta

[Bug 112921] Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 --- Comment #7 from Michel Dänzer --- Which patch did you try? Mario actually came up with a number of separate fixes to address this regression. I think all of them should be in Linus' tree by now (for 4.5). -- You are receiving this mail bec

[Bug 113341] GPU Lockup on AMD Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=113341 --- Comment #1 from Michel Dänzer --- Please attach the output of glxinfo and the Xorg log. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 113341] GPU Lockup on AMD Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=113341 --- Comment #2 from Bernd Steinhauser --- Created attachment 206381 --> https://bugzilla.kernel.org/attachment.cgi?id=206381&action=edit glxinfo -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 113341] GPU Lockup on AMD Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=113341 --- Comment #3 from Bernd Steinhauser --- I forgot about Xorg log, sorry. Since only one old one is kept, it's gone already. Maybe logging to syslog/journal is a good idea ... -- You are receiving this mail because: You are watching the assigne

[Bug 110211] [regression] amdgpu Fury X Unplayable Slow Down on Dota 2

https://bugzilla.kernel.org/show_bug.cgi?id=110211 Mike Lothian changed: What|Removed |Added CC||mike at fireburn.co.uk --- Comment #2 fro

[Bug 110211] [regression] amdgpu Fury X Unplayable Slow Down on Dota 2

https://bugzilla.kernel.org/show_bug.cgi?id=110211 --- Comment #3 from Kevin McCormack --- Then why I'd it playable with 4.3? I know there is no power management until 4.5 -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 110211] [regression] amdgpu Fury X Unplayable Slow Down on Dota 2

https://bugzilla.kernel.org/show_bug.cgi?id=110211 --- Comment #4 from Kevin McCormack --- OK, I was finally able to bisect today and it looks like the culprit is... a7ca8ef93001eaab4c5c7f4f3accfbe6ffcf5f26 is the first bad commit commit a7ca8ef93001eaab4c5c7f4f3accfbe6ffcf5f26 Author: Flora Cui

[Bug 110211] [regression bisected] amdgpu Fury X Unplayable Slow Down on Dota 2

https://bugzilla.kernel.org/show_bug.cgi?id=110211 Kevin McCormack changed: What|Removed |Added Summary|[regression] amdgpu Fury X |[regression bisected]

[Bug 103561] unable to handle kernel paging request with csgo in wine+nine, ttm_bo_del_from_lru

https://bugzilla.kernel.org/show_bug.cgi?id=103561 --- Comment #5 from Christoph Haag --- It's annoying because after this happens the GPU doesn't power off with runpm anymore and requires a reboot. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 110421] New: Reading debugfs file /sys/kernel/debug/dri/0/amdgpu_regs hangs the machine

https://bugzilla.kernel.org/show_bug.cgi?id=110421 Bug ID: 110421 Summary: Reading debugfs file /sys/kernel/debug/dri/0/amdgpu_regs hangs the machine Product: Drivers Version: 2.5 Kernel Version: 4.4.0-0.rc8.git0.1.fc24.x86_64

[Bug 110421] Reading debugfs file /sys/kernel/debug/dri/0/amdgpu_regs hangs the machine

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

[Bug 110421] Reading debugfs file /sys/kernel/debug/dri/0/amdgpu_regs hangs the machine

https://bugzilla.kernel.org/show_bug.cgi?id=110421 --- Comment #2 from Vedran Miletić --- Can't anything be done to avoid the hang? Running cat on that file will hang the machine as well. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 110421] Reading debugfs file /sys/kernel/debug/dri/0/amdgpu_regs hangs the machine

https://bugzilla.kernel.org/show_bug.cgi?id=110421 --- Comment #3 from Christian König --- Not really. You could do large lists of which registers are save for accessing, but we have 256KB register space and need an individual list for pretty much every hardware generation. Sorry but just acce

[Bug 103561] unable to handle kernel paging request with csgo in wine+nine, ttm_bo_del_from_lru

https://bugzilla.kernel.org/show_bug.cgi?id=103561 --- Comment #6 from Michel Dänzer --- This is the same as bug 96721, isn't it? https://bugs.freedesktop.org/show_bug.cgi?id=92258 might be related. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 108561] nouveau: external monitor can not be enabled with hindsight

https://bugzilla.kernel.org/show_bug.cgi?id=108561 --- Comment #6 from Elmar Stellnberger --- It is really a pity that my NVIDIA Corporation G96M [GeForce 9600M GT] has been crossed out of the list of supported cards since an update to kernel 4.3.3-2. It has worked well with the nouveau driver ex

[Bug 108561] nouveau: external monitor can not be enabled with hindsight

https://bugzilla.kernel.org/show_bug.cgi?id=108561 --- Comment #7 from Elmar Stellnberger --- Comment #6 is now resolved: Please excuse the panic; I think that there was just a temporary configuration issue with Arch Linux (see also: https://bugs.freedesktop.org/show_bug.cgi?id=93405); i.e. /dev/

[Bug 110211] [regression bisected] amdgpu Fury X Unplayable Slow Down on Dota 2

https://bugzilla.kernel.org/show_bug.cgi?id=110211 --- Comment #5 from Kevin McCormack --- Well, it seems that things are much better with 4.4rc8! I'm not sure why. It could also be the new Mushkin RAM I installed. I was having a lot of other random issues with my G.Skill Ares kit like lots of bu

[Bug 108261] [regression] [bisected] radeon HDMI audio broken for HD 5450 (cedar)

https://bugzilla.kernel.org/show_bug.cgi?id=108261 Cesko Voeten changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 106901] Brightness / WIFI Key does not generate any events

https://bugzilla.kernel.org/show_bug.cgi?id=106901 --- Comment #26 from Roman Gruber --- uname -a; echo " ";dmesg |grep ACPI Linux ASUS-G75VW 4.4.0-gentoo_14-01-2016 #1 SMP Thu Jan 14 19:15:47 CET 2016 x86_64 Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz GenuineIntel GNU/Linux [0.00] BIOS-e8

[Bug 106901] Brightness / WIFI Key does not generate any events

https://bugzilla.kernel.org/show_bug.cgi?id=106901 Roman Gruber changed: What|Removed |Added Kernel Version|Linux ASUS-G75VW|Linux ASUS-G75VW |4.3.3

[Bug 106901] Brightness / WIFI Key does not generate any events

https://bugzilla.kernel.org/show_bug.cgi?id=106901 --- Comment #27 from Roman Gruber --- Linux ASUS-G75VW 4.4.0-gentoo_14-01-2016 #1 SMP Thu Jan 14 19:15:47 CET 2016 x86_64 Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz GenuineIntel GNU/Linux same behaviour -- You are receiving this mail because: Y

[Bug 106901] Brightness / WIFI Key does not generate any events

https://bugzilla.kernel.org/show_bug.cgi?id=106901 --- Comment #28 from Roman Gruber --- lsmod Module Size Used by nvidia_modeset721045 3 nvidia 9922734 59 nvidia_modeset intel_powerclamp7094 0 xhci_pci3818 0 xhci_hcd

[Bug 108221] amdgpu: mouse cursor flickers + black boxes

https://bugzilla.kernel.org/show_bug.cgi?id=108221 Fred Santos changed: What|Removed |Added Kernel Version|4.3.0-7 |>= 4.3.0-7 See Also|

[Bug 88861] [efi, i915, vgaswitcheroo, black screen, nouveau] Screen goes black when switching from dedicated nvidia graphics card (nouveau) to integrated

https://bugzilla.kernel.org/show_bug.cgi?id=88861 Jani Nikula changed: What|Removed |Added Assignee|intel-gfx-bugs at lists.freede |dri-devel at lists.freedesktop

[Bug 97701] [regression] won't boot unless radeon.audio=0

https://bugzilla.kernel.org/show_bug.cgi?id=97701 Jouni Mettälä changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 98101] New: kernel BUG at drivers/gpu/drm/drm_vma_manager.c:209!

https://bugzilla.kernel.org/show_bug.cgi?id=98101 Bug ID: 98101 Summary: kernel BUG at drivers/gpu/drm/drm_vma_manager.c:209! Product: Drivers Version: 2.5 Kernel Version: 4.01 Hardware: All OS: Linux Tree: Ma

[Bug 95911] Recursive error in radeon device driver module after resume from hibernation

https://bugzilla.kernel.org/show_bug.cgi?id=95911 --- Comment #15 from gitne at excite.co.jp --- (In reply to Michel Dänzer from comment #14) >> Mantas Mikulėnas has determined that git commit 4474f3a91f95 was the last >> known good to work. > > So commit f2ba57b5eab8817d86d0f108fdf1878e51dc0a3

[Bug 98101] kernel BUG at drivers/gpu/drm/drm_vma_manager.c:209!

https://bugzilla.kernel.org/show_bug.cgi?id=98101 --- Comment #1 from Michel Dänzer --- Please attach the full dmesg output. Can you reproduce this problem by doing something in particular, or is it random? Is it a regression, i.e. didn't it happen with an older kernel version? -- You are rec

[Bug 95771] Crash when trying to hibernate

https://bugzilla.kernel.org/show_bug.cgi?id=95771 --- Comment #2 from Michel Dänzer --- (In reply to higuita from comment #1) > New crash dump Does building the kernel without CONFIG_HSA_AMD avoid this one? -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 98101] kernel BUG at drivers/gpu/drm/drm_vma_manager.c:209!

https://bugzilla.kernel.org/show_bug.cgi?id=98101 --- Comment #2 from Apostolos B. --- Created attachment 176601 --> https://bugzilla.kernel.org/attachment.cgi?id=176601&action=edit dmesg -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 98101] kernel BUG at drivers/gpu/drm/drm_vma_manager.c:209!

https://bugzilla.kernel.org/show_bug.cgi?id=98101 --- Comment #3 from Apostolos B. --- I had similar crashes requiring a hard reset but the log messages were different. This is the first time i see something like that. And also it points at where the bug is. Cant reproduce it. Its random. --

[Bug 98751] New: radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 Bug ID: 98751 Summary: radeon: multihead "no signal" on one of the monitors - regression Product: Drivers Version: 2.5 Kernel Version: 4.0.3+ Hardware: All

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 Mikkel Oscar Lyderik changed: What|Removed |Added CC||mikkeloscar at gmail.com R

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

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

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 --- Comment #2 from Mikkel Oscar Lyderik --- Created attachment 177561 --> https://bugzilla.kernel.org/attachment.cgi?id=177561&action=edit dmesg -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 --- Comment #3 from Mikkel Oscar Lyderik --- Created attachment 177571 --> https://bugzilla.kernel.org/attachment.cgi?id=177571&action=edit xorg log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 Mike Noe changed: What|Removed |Added CC||noeerover at gmail.com --- Comment #4 from Mik

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 --- Comment #5 from Mike Noe --- Created attachment 177581 --> https://bugzilla.kernel.org/attachment.cgi?id=177581&action=edit xorg.log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 --- Comment #6 from Mike Noe --- Created attachment 177591 --> https://bugzilla.kernel.org/attachment.cgi?id=177591&action=edit dmesg.txt -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 60523] Radeon DPM not working with 2 monitors attached to Radeon HD5770 (Juniper)

https://bugzilla.kernel.org/show_bug.cgi?id=60523 --- Comment #69 from Digingbil --- Any new insights on this issue guys? Maybe fixed on some latest kernel etc? -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 Robin Bankhead changed: What|Removed |Added CC||kernel at headbank.co.uk --- Comment #7

[Bug 98751] radeon: multihead "no signal" on one of the monitors - regression

https://bugzilla.kernel.org/show_bug.cgi?id=98751 --- Comment #8 from Mikkel Oscar Lyderik --- It's actually a 6950 card I have, same as in #98651. I called it 6990 because that is what lspci tells me, but that might narrow it down? -- You are receiving this mail because: You are watching the

<    1   2   3   4   5   6   7   8   9   10   >