https://bugs.freedesktop.org/show_bug.cgi?id=75649
Priority: medium
Bug ID: 75649
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Glitchy output using only HDMI on laptop with AMD
Mobility Radeon HD 3450/3470
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: tderensis(a)gmail.com
Hardware: x86 (IA32)
Status: NEW
Version: 10.0
Component: Drivers/Gallium/r600
Product: Mesa
Screen flickering and horizontal black/white lines mixed in with output on
redraw. This only happens when using HDMI output to a single external 1920x1080
monitor and not when using dual monitors or the single laptop screen. If the
screen is static or I move the mouse over a single color background, no
glitching happens. It seems that the more that needs to get redrawn in the
frame, the worse it gets.
I'm not sure how long this has been a problem because I rarely use a single
monitor. I'll report back when mesa 10.1 is released on Arch.
System info from Phoronix Test Suite:
Hardware:
Processor: Intel Core 2 Duo P8400 @ 2.27GHz (2 Cores), Motherboard: Sony VAIO,
Chipset: Intel Mobile 4 MCH + ICH9M, Memory: 3072MB, Disk: 320GB Western
Digital WD3200BEKT-7, Graphics: AMD Mobility Radeon HD 3450/3470 256MB
(680/800MHz), Audio: Realtek ALC262, Monitor: DELL ST2220L, Network: Marvell
88E8055 PCI-E Gigabit + Qualcomm Atheros AR928X Wireless
Software:
OS: Linux, Kernel: 3.13.5-1-ARCH (x86_64), Desktop: Cinnamon 2.0.14, Display
Server: X Server 1.15.0, Display Driver: radeon 7.3.0, OpenGL: 3.1 Mesa 10.0.3
Gallium 0.4, Compiler: GCC 4.8.2 20140206 + Clang 3.4 + LLVM 3.4, File-System:
ext4, Screen Resolution: 1920x1080
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75127
Priority: medium
Bug ID: 75127
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Radeon SUMO: atombios stuck executing
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: sandy.8925(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment 94246
--> https://bugs.freedesktop.org/attachment.cgi?id=94246&action=edit
linux_kernel_3.14-rc2_dmesg
I have a laptop with Radeon HD6520G GPU.
I am running Arch Linux 64 bit with Linux 3.14-rc2 kernel and Mesa 10.0.3
During shutdown, suspend and resume, GPU hangs and I get error messages in the
kernel that state:
[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing D05E (len 62,
WS 0, PS 0) @ 0xD07A
Earlier, shutdown would work fine, and laptop would also suspend quickly.
However now I find that suspend and shutdown take a long time and I see the
above error messages.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75102
Priority: medium
Bug ID: 75102
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Radeon 4890 getting a blank screen and fans go up to
100% (kernel 3.13.3)
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: peterasplund(a)gentoo.se
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
I've been fiddling around with the cooling on my Radeon 4890 and replaced it
with an Arctic Cooling I had mounted on my old 4850 card.
It worked for a while, but then the screens went black and the fan maxed out
completely. BUT I noticed that the computer was still running, so it hadn't
crashed. I could SSH in and reboot it manually.
I figured the card had gotten to hot, so I switched the coolers again. But the
problem was still there! I started monitoring the temperatures, and they really
weren't any hotter than normal. Around 45 degrees C. The weird behavior still
repeated itself, even when just browsing the web for a couple of minutes. One
time it happened after only 2-3 minutes!
I then booted into Windows to see if the problem was there, and nothing
happened. I ran benchmarks (3D Mark) and played Left 4 Dead on highest settings
for an hour, and no issues. I then booted into Linux, and it still happened.
So I then realized I had updated the kernel to 3.13.3 from 3.12.3, and I booted
into the old kernel instead. And now I've been running some "emerges" for an
hour, and browsed the web, without any issues.
Is it possible some weird bug has gotten into the 3.13 kernel? I googled the
issue, and saw that there were several posts about the same behavior on the
Catalyst drivers a year or so back. Even on Windows that is.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74974
Priority: medium
Bug ID: 74974
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi] x264 OpenCL does not work
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic(a)linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
I opened this bug just to keep track of the issue:
https://mailman.videolan.org/pipermail/x264-devel/2014-February/010385.html
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74973
Priority: medium
Bug ID: 74973
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi] Gimp OpenCL does not work
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic(a)linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Start gimp with GEGL_USE_OPENCL=yes
Open an image, tools --> gegl operation --> motion blur --> crash
3.14 and latest graphic stack from git including llvm-3.5 and mesa 10.2
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74315
Priority: medium
Bug ID: 74315
Assignee: dri-devel(a)lists.freedesktop.org
Summary: radeon_dp_getdpcd: DPCD debug output mangled
Severity: normal
Classification: Unclassified
OS: All
Reporter: paulepanter(a)users.sourceforge.net
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715603]
[drm:radeon_dp_getdpcd], DPCD:
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715606]
[drm:radeon_dp_getdpcd], 11
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715613]
[drm:radeon_dp_getdpcd], 0a
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715617]
[drm:radeon_dp_getdpcd], 84
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715622]
[drm:radeon_dp_getdpcd], 01
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715626]
[drm:radeon_dp_getdpcd], 00
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715629]
[drm:radeon_dp_getdpcd], 0b
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715633]
[drm:radeon_dp_getdpcd], 01
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715636]
[drm:radeon_dp_getdpcd], 01
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715640]
[drm:radeon_dp_getdpcd], 02
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715643]
[drm:radeon_dp_getdpcd], 00
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715646]
[drm:radeon_dp_getdpcd], 00
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715650]
[drm:radeon_dp_getdpcd], 00
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715653]
[drm:radeon_dp_getdpcd], 00
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715657]
[drm:radeon_dp_getdpcd], 00
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715660]
[drm:radeon_dp_getdpcd], 00
Feb 1 09:46:29 my_asus_u38n_system kernel: [ 83.715663]
[drm:radeon_dp_getdpcd],
The macro `DRM_DEBUG_KMS` seems to add line breaks add the end, so the current
formatting is unexpected. At least the separate line break after the for loop
is not needed.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74211
Priority: medium
Bug ID: 74211
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Discrete videocard is missing linux 3.13
Severity: normal
Classification: Unclassified
OS: All
Reporter: anton.sudak(a)gmail.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 93039
--> https://bugs.freedesktop.org/attachment.cgi?id=93039&action=edit
dmesg
Discrete videocard is missing linux 3.13. There no
/sys/kernel/debug/vgaswitcheroo and xrandr --listproviders shows me only Intel
videocard. Videocard also missing in lspci output. I provide dmesg, there are
some traces which can be related to this bug. I already tried
The last working kernel version for me is 3.12.9.
My configuration:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks
[Radeon HD 7650A/7670A]
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73848
Priority: medium
Bug ID: 73848
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [Radeon] Blank screen after boot with kernel 3.12.x,
xorg 1.15
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: marti(a)juffo.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
With ASUS Radeon R9 270, just after I boot up and GDM is supposed to start, my
screen goes blank and some GPU faults are reported in dmesg.
Upgrading to kernel 3.13 solves this issue.
One time the graphics also recovered with 3.12.8 after coming back from
suspend, but I have not been able to reproduce that.
Using up-to-date Arch Linux testing with:
xorg-server 1.15.0
mesa 10.0.2
libdrm 2.4.51
xf86-video-ati 7.2.0
kernel versions tested: 3.12.8, 3.12.1, 3.11.5, 3.10.10
The following errors are reported in dmesg (full log attached):
radeon 0000:01:00.0: GPU fault detected: 147 0x005e7001
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x091C0002
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x1E070001
VM fault (0x01, vmid 15) at page 152829954, read from CP (112)
radeon 0000:01:00.0: GPU fault detected: 147 0x02de8801
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
VM fault (0x00, vmid 0) at page 0, read from unknown (0)
radeon 0000:01:00.0: GPU fault detected: 147 0x02de8801
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000
VM fault (0x00, vmid 0) at page 0, read from unknown (0)
radeon 0000:01:00.0: GPU fault detected: 147 0x04df8402
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00080826
radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x1F084002
VM fault (0x02, vmid 15) at page 526374, write from TC (132)
--
You are receiving this mail because:
You are the assignee for the bug.