https://bugs.freedesktop.org/show_bug.cgi?id=79806
Priority: medium
Bug ID: 79806
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Performance degradation after resume
Severity: normal
Classification: Unclassified
OS: All
Reporter: enyecz(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
I have a Radeon HD …
[View More]4350/4550 (RV770) card in my notebook. After resuming from
suspend, there is a significant 3D performance drop (a bit less than 1/4 of
original performance remains). The performance drop is exactly at the same
level as it is after "echo low >
/sys/class/drm/card0/device/power_dpm_force_performance_level", albeit
power_dpm_force_performance_level still contains "auto".
Bug is found in Ubuntu 14.04, but it was there at least since 13.10 (I have
just found the workaround). The bug is there with kernel 3.13 (official), with
3.14 mainline and 3.15-RC8 which was build for Ubuntu 14.10.
Workaround: when resume, execute "echo auto >
/sys/class/drm/card0/device/power_dpm_force_performance_level".
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=79564
Priority: medium
Bug ID: 79564
Assignee: dri-devel(a)lists.freedesktop.org
Summary: glamor with dual radeon segfaults
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: philipp(a)schmitt.co
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
…
[View More]Created attachment 100332
--> https://bugs.freedesktop.org/attachment.cgi?id=100332&action=edit
Xorg.0.log
Hello,
OS: ArchLinux
Xorg: 1.15
xf86-video-ati: 7.3.0
xorg.conf: None
I have two ATI 7750s. When only one card is present, startx works as expected
but when both GPUs are plugged in, it results in a segfault (see attachment).
Reverting to EXA works though.
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=79488
Priority: medium
Bug ID: 79488
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Checkerboard tearing on Radeon card
Severity: normal
Classification: Unclassified
OS: All
Reporter: dan.doel(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created attachment …
[View More]100211
--> https://bugs.freedesktop.org/attachment.cgi?id=100211&action=edit
dmesg while the machine is in the 'tearing' state
For several months now, I've occasionally run into situations where my screen
displays a strange artifact or tearing pattern. It is only visible when things
are changing, of course, and it looks like the monitor is divided into small
squares, and two different 'frames' are drawn alternately. Here is a video of
the problem I took back at the end of February:
https://www.youtube.com/watch?v=e2T8BeE0j74
I've just encountered this again, and it reminded me to finally post a bug.
You'll notice that the video was recorded on a cell phone. I tried using a
desktop recorder (the one built into gnome-shell) and the resulting video did
not display the artifacts. So it would seem to be happening at a level below
what capture can detect.
I'll attach dmesg and xorg logs from when the problem is happening. You'll see
that there are lots of page flip errors in both. However, I think that actually
might be a red herring. Doing a tail -f on the logs, I can cause artifacts to
display (for instance, selecting a different channel in my irc client, causing
highlighting to change, which briefly displays checkerboard highlights) without
a corresponding xorg error. And I also frequently see those errors accompanied
by ordinary tearing. But I can't definitively say that they aren't related,
either.
I'm using:
mesa from git as of about a week ago (rev 63069)
latest glamor (as of 2014-03-13)
xf86-video-ati 7.3.0
kernel 3.14.4
But this has been happening for significantly longer than just those versions.
I have a Radeon HD 7870 (pitcairn).
I'm not certain that I've assigned this bug to the right project, although at
least some of the visible errors involve drm. Apologies if it's the fault of
something else, though.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=79318
Priority: medium
Bug ID: 79318
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [radeonsi] The Witcher 2 wine graphical corruption
Severity: normal
Classification: Unclassified
OS: All
Reporter: darkbasic(a)linuxsystems.it
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
…
[View More]Card is an AMD Radeon HD 7950. I’m using kernel 3.15-rc5 + cherrypicks + PTE
patches (VRAM page table entry compression) + hyperz (R600_DEBUG=hyperz). I’m
also using libdrm git, xf86-video-ati git, llvm 3.5 git with a rebased Tom
Stellard’s si-spill-fixes-v4 branch, mesa git (OpenGL core profile version
string: 3.3 (Core Profile) Mesa 10.3.0-devel (git-57730d6)) and Keith Packard’s
xorg-server glamor-server branch (1.16.0 RC 2).
As you can see from the attached screenshot there is graphical corruption:
http://files.linuxsystems.it/files/the_witcher_2_wine_radeonsi.png
It works flawlessly with Catalyst.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=79223
Priority: medium
Bug ID: 79223
Assignee: dri-devel(a)lists.freedesktop.org
Summary: extra vsync when reading back pixels in xbmc
Severity: normal
Classification: Unclassified
OS: All
Reporter: pierre-bugzilla(a)ossman.eu
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
…
[View More]Something is causing an extra wait for vsync in xbmc when it needs to read back
pixels. This seems to be specific to the radeon driver as I'm not seeing it
with nouveau.
Test scenario:
- Configure xbmc to wait for vsync
- Install something that activates xbmc's capture code (e.g. xbmc's boblight
plugin)
- Play a video whose framerate > screen refresh / 2
You'll see the frame rate reliably locked to screen refresh / 2 under these
circumstances. A major problem as you generally want to run with a 24 Hz
refresh rate for 24 Hz films.
I'm unable to pinpoint exactly the offending GL command as xbmc's rendering is
quite complex. I hope you're more experienced in finding these things. :)
The rough sequence of events is:
1. xbmc renders the scene
2. Wait for vsync
3. Map PBO and memcpy data. (from previous frame)
4. Render small version of scene
5. glReadPixels into PBO
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=78096
Priority: medium
Bug ID: 78096
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Linux 3.14 doesn't boot with Radeon HD 5870
Severity: normal
Classification: Unclassified
OS: All
Reporter: stephane.raimbault(a)gmail.com
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
I …
[View More]updated to the kernel 3.14 provided by Archlinux
(https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=package…)
and I'm not able to boot without passing radeon.modeset=0 to the kernel command
line.
The kernel 3.13 from package 3.13.8-1-ARCH is working properly.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=77677
Priority: medium
Bug ID: 77677
Assignee: dri-devel(a)lists.freedesktop.org
Summary: HDMI audio on ati7750 choppy with ALSA multi-channel
apps
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: socalfisher(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
…
[View More]Component: DRM/Radeon
Product: DRI
Created attachment 97618
--> https://bugs.freedesktop.org/attachment.cgi?id=97618&action=edit
Alsa No Pulseaudio xorg.0.log dmesg aplayL/l codec logs
I am having issues playing sounds over HDMI stereo directly to TV. I am using
XBMC.
When Pulse Audio is installed the sounds play fine in stereo. When I try a
pure alsa installation (no pulse audio) there is severe distortion. Pure ALSA
is needed for applications that only support ALSA, and for HDMI pass-through.
My dedicated Radeon 7750 card only outputs cyclical sounds, quiet voices like
wrong channel, and echos. Setup PC to TV directly HDMI (2.0 audio selected). I
have had the same issue when cpu was an AMD 955BE, and now Intel i7 4770.
Windows 7 plays hdmi audio just fine on the same exact PC/Panasonic
plasma/setup.
1) speaker-test -l 4 -c 2 -r 48000 -D hw:1,3 plays choppy sounds with or
without pulse installed.
2) aplay -D plughw:1,3 /usr/share/sounds/alsa/Front_Center.wav plays fine
Using an A4-3400 HDMI plays perfectly fine on the same TV. As does my Zotac
AQ01.
Not sure if this is related (http://ubuntuforums.org/showthread.php?t=2207698):
SND_PCM_ACCESS_RW_INTERLEAVED vs. SND_PCM_ACCESS_MMAP_INTERLEAVED
I believe XBMC uses SND_PCM_ACCESS_RW_INTERLEAVED for ALSA.
Thanks in advance.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=77394
Priority: medium
Bug ID: 77394
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Desktop freezes often when KDE starts compositing or
mplayer GL window changes
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: nine(a)detonation.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: …
[View More]unspecified
Component: DRM/Radeon
Product: DRI
When I turn on KDE compositing the desktop freezes more often than not. These
freezes can also be provoked when configuring mplayer for GL output and opening
a video file. If that alone is not enough, just change repeatedly from window
to fullscreen and back. Attaching Xorg.0.log and dmesg of such a crash.
I can reboot the system cleanly using alt+sysrq+r and ctrl+alt+del but any
attempts to get a nice backtrace of the X server with gdb failed due to the
process hanging in kernel space.
Hardware:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Curacao XT [Radeon R9 270X]
Running:
kernel 3.14,
libdrm2-2.4.99~git20140411-1.1,
xorg-x11-server-7.6_1.15.99.902-306.1
Mesa-10.2~git20140411-5.1
llvm-r600-3.5~svn20140408-1.1.x86_64
openSUSE 13.1
Downgrading components to openSUSE 13.1 stock versions did not help except for
downgrading the kernel to 3.11.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=77247
Priority: medium
Bug ID: 77247
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Suspend/Hibernate S3 Defect Fusion E350
Severity: normal
Classification: Unclassified
OS: All
Reporter: schumi2004(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
Created …
[View More]attachment 97144
--> https://bugs.freedesktop.org/attachment.cgi?id=97144&action=edit
dmesg with drm.debug=0xe
My first bug ticket so bare with me.
System: AD02 E350
OS: OpenELEC Beta - Generic x86_64 3.95.5
System won't wakeup from Hibernate/Suspend, symptoms are:
- Blackscreen
- No SSH access to system possible at all.
- Disconnect power to get it working again.
The symptoms are only noticeable after a long period of suspend/hibernate (1
hour and up) If you suspend/hibernate system and directly waking it up again
then you won't have it.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=77069
Priority: medium
Bug ID: 77069
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Use semantic naming for microcode files
Severity: minor
Classification: Unclassified
OS: Linux (All)
Reporter: nmschulte(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
This is a …
[View More]rather trivial request, but it would help the uninitiated and long
term maintenance.
It would be nice if the microcode was more semantically named, rather than how
it exists now.
For example, I currently have an issue with UVD on a Radeon HD 8970M, which is
"Neptune XT" based (which is "Pitcairn" based), and I receive the following
logging:
[ 15.942210] [drm] Loading PITCAIRN Microcode
[ 15.966837] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_pfp.bin
[ 15.976695] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_me.bin
[ 15.996448] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_ce.bin
[ 16.015403] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_rlc.bin
[ 16.016529] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_mc.bin
[ 16.026910] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/PITCAIRN_smc.bin
[ 16.045744] radeon 0000:01:00.0: firmware: direct-loading firmware
radeon/TAHITI_uvd.bin
....
[ 65.525470] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 66.537637] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 67.549797] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 68.561967] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 69.574142] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 70.586334] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 71.598533] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 72.610705] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 73.622877] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 74.635068] [drm:uvd_v1_0_start] *ERROR* UVD not responding, trying to reset
the VCPU!!!
[ 74.654938] [drm:uvd_v1_0_start] *ERROR* UVD not responding, giving up!!!
[ 74.654955] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1).
At first glance, I'm thinking: well clearly TAHITI_uvd.bin is incorrect for
PITCAIRN Microcode, but that's not quite how things work. It would be nice to
name the UVD microcode after the actual version of the platform the code is
targeting. Perhaps this is simply a naming collision issue and the UVD
microcode naming is semantic within the context (that is: my Radeon HD 8970M
card really does run the TAHITI version of UVD), but that's doubtful and I
would suggest the names change to be more meaningful, :).
Another proposition is to skip the "fully semantic naming" idea above and just
use symlinks to bridge the two namespaces.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]