https://bugs.freedesktop.org/show_bug.cgi?id=64503
Priority: medium
Bug ID: 64503
Assignee: dri-devel(a)lists.freedesktop.org
Summary: audio glitches when running at 24hz/24p
Severity: normal
Classification: Unclassified
OS: All
Reporter: pierre-bugzilla(a)ossman.eu
Hardware: Other
Status: NEW
Version: unspecified
Component: DRM/Radeon
Product: DRI
(originally reported to Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=954009)
I've recently started trying out 24 Hz again as my TV handles it better, and
XBMC is finally at a point where they can keep things synced up when playing at
exactly the monitor refresh rate.
Unfortunately that broke the HDMI audio output. If I try to output audio when
the refresh rate is at 24 Hz, the receiver will lose audio sync every few
minutes, resulting in silence until it regains sync.
I've tried the following:
- Sending audio over SPDIF from the onboard audio to the same receiver works
fine. Another cable though, and cannot handle high-bitrate formats, so hardly a
long term solution.
- Audio format doesn't seem to matter. I get glitches with PCM, AC3 and DTS.
DTS is the worst, but that might just be because it requires more effort to
sync back up again.
- It's not xbmc that gets confused as sending audio from an entirely different
program results in the same audio glitches (I tried mplayer with -vo null in
the background).
- Doesn't seem to be a application buffering issue as I see no spikes in
either xbmc's or mplayer's sync statistics when the glitch appears.
This is with kernel-3.8.7-201.fc18.x86_64.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=64695
Priority: medium
Bug ID: 64695
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Enabling both MLAA and MLAA color 2D crashes Gnome
Shell on Cayman (6950)
Severity: major
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers(a)gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Forcing MLAA through driconf on Cayman 6950 crashes Gnome Shell if both mlaa
and mlaa color (2D) are set (tested with both set to 8). If one of them is not
set, Gnome Shell doesn't crashes.
MLAA color (2D) seems to have an effect on my Gnome Shell display. Tested with
mesa's commit 7e17e72cb716c56264d4778684f6f23de69a56a1.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=65192
Priority: medium
Bug ID: 65192
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Screensavers lock up machine (screen goes blank,
keyboard unresponsive, sound loops; sysrq/ssh
possible)
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: luziphermcleod(a)yahoo.ie
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
For a while now, some screensavers sometimes lock up my machine. That means all
screens go blank, the keyboard is unresponsive (numpad-key doesn't toggle the
indicator led), the sound loops. But I still can use ssh from a remote machine
and the magic-sysrq-keys also work.
There is nothing to see in neither /var/log/messages (acquired via netconsole)
nor /var/log/Xorg.0.log.
I can trigger the bug (or regression, I think it used to work about 2 months
ago) reliably by using the Xfce4 screensaver settings application, which has a
preview of the screensaver selected. When switching between screensavers, the
lockup quickly occurs. A good candidate is the screensaver named "AntMaze", it
alsmost always locks up my machine (only worked once so far).
Other stuff works quite solid, Half-Life 2 worked multiple hours today.
Setting R600_HYPERZ=0 in /etc/environment didn't help. Also occurs on kernel
3.8.0-rc7.
I'm happy to provide more info if needed.
System Specs:
Intel Core i7-965
2x Radeon HD4870 (rv770, currently only one active without xorg.conf), 2
Monitors
Gentoo Linux
Kernel 3.10.0-rc3
Mesa 9.2.0 (git-60f9b72) git commit 60f9b722ef80c499a94b4e5ab7304dcd739ea569
Revert "i965: fix problem with constant out of bounds access (v2)"
xorg-server-1.14.1
libdrm git commit 8a88e349975a64676f143183e835e6d296f29627 modetest: Make
RGB565 pwetty too
xf86-video-ati git commit commit bd2557ea5ef84b975060e929d5ece53ec464336f DRI2:
add interpolated blanks to frame number in event handlers
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=57875
Priority: medium
Bug ID: 57875
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Second Life viewer bad rendering with git-ec83535
Severity: normal
Classification: Unclassified
OS: All
Reporter: andabata12(a)yahoo.it
Hardware: Other
Status: NEW
Version: unspecified
Component: Drivers/Gallium/r300
Product: Mesa
With git "HEAD at ec83535 automake/gallium: attempt to fix -lrt", Cool VL
Viewer a TPV for Second Life 3D world ( the official Linden Lab viewer is from
ages blocked cause of https://bugs.freedesktop.org/show_bug.cgi?id=39251 ) can
set only basic shaders otherwise with atmospheric, water and reflections
shaders enabled, I have extensive blue triangles during the execution.
On the contrary with graphics drivers from git-54ff536 ( HyperZ enabled by
default) all was right with smooth rendering, lowered cpu usage and augmented
framerate ( 8-10 %).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=59322
Priority: medium
Bug ID: 59322
Assignee: dri-devel(a)lists.freedesktop.org
Summary: r300g MSAA breaks Half-Life 2 in Wine
Severity: normal
Classification: Unclassified
OS: All
Reporter: stefandoesinger(a)gmx.at
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r300
Product: Mesa
When MSAA is enabled in Half-Life 2 running in Wine, the window only contains
garbled output. Disabling multisampling in Wine or in the game settings
restores proper rendering.
A complication is that the game enables 2x MSAA by default if it is available.
A user not knowing this fact will think that 8ed6b140 broke the game. It also
makes disabling multisampling in the game settings a challenge.
Hardware info:
OpenGL vendor string: X.Org R300 Project
OpenGL renderer string: Gallium 0.4 on ATI RV530
OpenGL version string: 2.1 Mesa 9.1-devel (git-8ed6b14)
OpenGL shading language version string: 1.20
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M56P
[Radeon Mobility X1600]
01:00.0 0300: 1002:71c5
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=61182
Priority: medium
Bug ID: 61182
Assignee: dri-devel(a)lists.freedesktop.org
Summary: r600g causes KWin crashes with kernel 3.8
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: eugene.shalygin(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Kwin crashes with current mesa and kernel 3.8. It does not crash with 3.7
kernel. With mesa 9.0.2 and kernel 3.8 kwin also works fine
#5 0x0000003647c892ab in __memset_sse2 () from /lib64/libc.so.6
#6 0x00007f5a8cbf6cf3 in r600_texture_create_object (screen=0x980ca0,
base=0x7fff208b4770, pitch_in_bytes_override=0, buf=0x0,
surface=0x7fff208b3a80) at r600_texture.c:509
#7 0x00007f5a8cbf7339 in r600_texture_create (screen=0x980ca0,
templ=0x7fff208b4770) at r600_texture.c:601
#8 0x00007f5a8cbdbae5 in r600_resource_create (screen=0x980ca0,
templ=0x7fff208b4770) at r600_resource.c:37
#9 0x00007f5a8cc1b4d2 in dri2_drawable_process_buffers (drawable=0xc2b130,
buffers=0x764460, buffer_count=1, atts=0x7fff208b48b0, att_count=1) at
dri2.c:254
#10 0x00007f5a8cc1b9b3 in dri2_allocate_textures (drawable=0xc2b130,
statts=0x7fff208b48b0, statts_count=1) at dri2.c:404
#11 0x00007f5a8cc19f0f in dri_st_framebuffer_validate (stfbi=0xc2b130,
statts=0x7fff208b48b0, count=1, out=0x0) at dri_drawable.c:81
#12 0x00007f5a8cc1a30e in dri_drawable_validate_att (drawable=0xc2b130,
statt=ST_ATTACHMENT_FRONT_LEFT) at dri_drawable.c:206
#13 0x00007f5a8cc1a35c in dri_set_tex_buffer2 (pDRICtx=0x8fef20, target=3553,
format=8409, dPriv=0xbee5e0) at dri_drawable.c:220
#14 0x00007f5a9b82f590 in dri2_bind_tex_image (dpy=0x7d15f0, drawable=29360171,
buffer=8414, attrib_list=0x0) at dri2_glx.c:1002
#15 0x00007f5a9b7f30f5 in __glXBindTexImageEXT (dpy=0x7d15f0,
drawable=29360171, buffer=8414, attrib_list=0x0) at glxcmds.c:2370
#16 0x00007f5a9d1773c3 in KWin::GlxTexture::loadTexture(unsigned long const&,
QSize const&, int) () from /usr/lib64/libkdeinit4_kwin.so
#17 0x00007f5a9d16f175 in KWin::SceneOpenGL::Window::bindTexture() () from
/usr/lib64/libkdeinit4_kwin.so
#18 0x00007f5a9d175a8e in KWin::SceneOpenGL::Window::performPaint(int, QRegion,
KWin::WindowPaintData) () from /usr/lib64/libkdeinit4_kwin.so
#19 0x00007f5a9d16e32f in
KWin::SceneOpenGL2::performPaintWindow(KWin::EffectWindowImpl*, int, QRegion,
KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so
#20 0x00007f5a9d16e4cd in
KWin::SceneOpenGL2::finalDrawWindow(KWin::EffectWindowImpl*, int, QRegion,
KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so
#21 0x00007f5a9d1822b5 in
KWin::EffectsHandlerImpl::drawWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so
#22 0x00007f5a9d16178a in
KWin::Scene::finalPaintWindow(KWin::EffectWindowImpl*, int, QRegion,
KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so
#23 0x00007f5a9d182557 in
KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion,
KWin::WindowPaintData&) () from /usr/lib64/libkdeinit4_kwin.so
#24 0x00007f5a9d16434d in KWin::Scene::paintWindow(KWin::Scene::Window*, int,
QRegion, KWin::WindowQuadList) () from /usr/lib64/libkdeinit4_kwin.so
#25 0x00007f5a9d16367f in KWin::Scene::paintSimpleScreen(int, QRegion) () from
/usr/lib64/libkdeinit4_kwin.so
#26 0x00007f5a9d1616ce in KWin::Scene::finalPaintScreen(int, QRegion,
KWin::ScreenPaintData&) () from /usr/lib64/libkdeinit4_kwin.so
#27 0x00007f5a9d182720 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion,
KWin::ScreenPaintData&) () from /usr/lib64/libkdeinit4_kwin.so
#28 0x00007f5a9d162a68 in KWin::Scene::paintScreen(int*, QRegion*) () from
/usr/lib64/libkdeinit4_kwin.so
#29 0x00007f5a9d171fce in KWin::SceneOpenGL::paint(QRegion,
QList<KWin::Toplevel*>) () from /usr/lib64/libkdeinit4_kwin.so
#30 0x00007f5a9d15ceac in KWin::Compositor::performCompositing() () from
/usr/lib64/libkdeinit4_kwin.so
#31 0x00007f5a9d15d950 in KWin::Compositor::slotCompositingOptionsInitialized()
() from /usr/lib64/libkdeinit4_kwin.so
#32 0x00007f5a9afb418f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#33 0x00007f5a9ae96877 in QFutureWatcherBase::event(QEvent*) () from
/usr/lib64/qt4/libQtCore.so.4
#34 0x00007f5a9a35cd6c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/qt4/libQtGui.so.4
#35 0x00007f5a9a35eaea in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/qt4/libQtGui.so.4
#36 0x00007f5a9cc83336 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#37 0x00007f5a9af9f06e in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/qt4/libQtCore.so.4
#38 0x00007f5a9afa2891 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/qt4/libQtCore.so.4
#39 0x00007f5a9a3f8979 in
QEventDispatcherX11::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/qt4/libQtGui.so.4
#40 0x00007f5a9af9ddcf in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#41 0x00007f5a9af9e058 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/qt4/libQtCore.so.4
#42 0x00007f5a9afa2ba8 in QCoreApplication::exec() () from
/usr/lib64/qt4/libQtCore.so.4
#43 0x00007f5a9d113d2a in kdemain () from /usr/lib64/libkdeinit4_kwin.so
#44 0x0000003647c249b5 in __libc_start_main () from /lib64/libc.so.6
#45 0x0000000000400831 in _start ()
Hardware: Mobility Radeon HD 5850
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=58731
Summary: radeon_uvd: Can't load firmware "radeon/RV710_uvd.bin"
Product: Drivers
Version: 2.5
Kernel Version: 3.10.0-rc2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: smf.linux(a)ntlworld.com
Regression: No
Created an attachment (id=102361)
--> (https://bugzilla.kernel.org/attachment.cgi?id=102361)
dmesg output and other supporting information
[AMD/ATI] RV710 [Radeon HD 4350/4550] on M5A97 PRO and AMD Phenom(tm) II X6
1100T Processor (16Gbyte RAM) fails to load RV710_uvd.bin at boot. I have found
that "request_firmware" call is returning -2 (ENOENT) though the correct file
is available in /lib/firmware/radeon. On further investigation this appears to
stem from "assign_firmware_buf" not having a buffer available (buf->size=0). I
have attached an instrumented dmesg (lines tagged with SMF), lspci and
/lib/firmware/radion listings for information. I am assuming that this video
card should support the UVD functionality.
Please advise.
regards
Stuart Foster
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=62959
Priority: medium
Bug ID: 62959
Assignee: dri-devel(a)lists.freedesktop.org
Summary: r600g (HD 6950 Cayman) fails piglit tests and hangs
system
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers(a)gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Using mesa 0967c362bf378b7415c30ca6d9523d3b2a3a7f5d (and for a long time),
piglit tests fail and hangs the system (ssh session won't respond). Using an HD
6950 (Cayman).
Running "python2 piglit-run.py --no-concurrency tests/r600.tests
results/r600.results/", it fails everytime. According to the "main" file, the
last log info is:
"spec/glsl-1.30/execution/built-in-functions/fs-greaterThan-uvec4-uvec4": {
"info": "Returncode: 0\n\nErrors:\n\n\nOutput:\n",
"returncode": 0,
"command":
"/home/dema1701/projects/display/piglit/framework/../bin/shader_runner
tests/../generated_tests/spec/glsl-1.30/execution/built-in-functions/fs-greaterThan-uvec4-uvec4.shader_test
-auto",
"result": "pass",
"time": 0.10875105857849121
},
"spec/glsl-1.10/execution/variable-indexing/fs-temp-array-mat4-col-row-wr": {
"info": "Returncode: 0\n\nErrors:\n\n\nOutput:\n",
"returncode": 0,
Mesa's build options:
baseExec="./autogen.sh --prefix=/usr \
--enable-debug \
--enable-shared \
--enable-osmesa \
--enable-gbm \
--enable-xvmc \
--enable-vdpau \
--enable-gles1 \
--enable-gles2 \
--enable-openvg \
--enable-xorg \
--enable-xa \
--enable-egl \
--enable-gallium-egl \
--enable-glx-tls \
--enable-texture-float \
--enable-wgl \
--with-gallium-drivers=r600,swrast,svga \
--with-egl-platforms=x11,drm"
"$baseExec --enable-64-bit --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --libdir=/usr/lib/x86_64-linux-gnu
--includedir=/usr/include/x86_64-linux-gnu"
--
You are receiving this mail because:
You are the assignee for the bug.