dri-devel June 2015

dri-devel@lists.freedesktop.org

188 participants
1140 discussions

[Bug 62967] New: Game Dungeon Defenders crash my whole system.
by bugzilla-daemon＠freedesktop.org 15 Jul '16

15 Jul '16

https://bugs.freedesktop.org/show_bug.cgi?id=62967 Priority: medium Bug ID: 62967 Assignee: dri-devel(a)lists.freedesktop.org Summary: Game Dungeon Defenders crash my whole system. Severity: normal Classification: Unclassified OS: All Reporter: lvella(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 77255 --> https://bugs.freedesktop.org/attachment.cgi?id=77255&action=edit glxinfo output When I run Dungeon Defenders, the game window pops up and the first intro animation runs very slowly (a red logo building in front of a white backgroud), then at the second animation, a seeming magic circle with purple fire, my computer halts and freezes completely, and I have to reboot. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 90218] Kerbal Space Program crashes with Souther Islands
by bugzilla-daemon＠freedesktop.org 15 Jul '16

15 Jul '16

https://bugs.freedesktop.org/show_bug.cgi?id=90218 Bug ID: 90218 Summary: Kerbal Space Program crashes with Souther Islands Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: lvella(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org I had no problem playing the game (aside from low FPS) with i965 on the same machine, stock drivers from Ubuntu 14.10. Now, with a new GFX r9 280X, the game runs OK, but may randomly crash the entire system and I must hard reset the computer. I could not find anything relevant on the dmesg log from the last crashed session, the last message was from boot procedure. Last time it crashed I was on the Mission Center screen, from Carrer Mode. I also remember it crashed when I switched workspace with the game running (XFce, no composition, I pressed ctrl + alt + leftarrow, it swiched, displayed Chrome window running there, and crashed). The driver is no longer Ubuntu stock, and I am using from this PPA: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers with the following env var: R600_DEBUG=sb It crashed with Ubuntu 14.10, and crashed yesterday again, after updating to Ubuntu 15.04. The relevant part from glxinfo: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TAHITI OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel (git-7f5a8ac 2015-04-25 utopic-oibaf-ppa) OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile It fares better than fglrx, that crashes the game just past main menu. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 90221] Triangle boundary artifact on Shadow Warrior game
by bugzilla-daemon＠freedesktop.org 15 Jul '16

15 Jul '16

https://bugs.freedesktop.org/show_bug.cgi?id=90221 Bug ID: 90221 Summary: Triangle boundary artifact on Shadow Warrior game Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: lvella(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 115419 --> https://bugs.freedesktop.org/attachment.cgi?id=115419&action=edit Wall with light effect triggering the artifact. On game Shawdow Warrior, with Southern Island chip, drivers from this PPA: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers Experienced both on Ubuntu 14.10 and, after upgrade, on Ubuntu 15.04. Some special effects trigger a visible artifact on triangle primitive boundaries, probably, see screenshot attached. With fglrx, the issue is not present. It seems the problem is on some post-processing shader, because, as can be seen in the screenshot, the visible triangles does not respect the boundary of scene objects, and if I move the mouse, they are fixed relative to the screen. Running with the following env var (otherwise the game is unplayable slow on current video settings): R600_DEBUG=sb Relevant info from glxinfo: OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TAHITI OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel (git-7f5a8ac 2015-04-25 utopic-oibaf-ppa) OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 86669] SSH Account request
by bugzilla-daemon＠freedesktop.org 13 Jul '16

13 Jul '16

https://bugs.freedesktop.org/show_bug.cgi?id=86669 Bug ID: 86669 Summary: SSH Account request Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: General Assignee: dri-devel(a)lists.freedesktop.org Reporter: seanpaul(a)chromium.org realname: Sean Paul email: seanpaul(a)chromium.org acctname: seanpaul rsa: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDPkbopYTyjCHuBOjkjec0ERFcIAH7KjVbOUFdB4+6bXvpWnUR9FxupvL36XWI2jF9T9suBZipoD22cvpsXK2PGPmzNGeICgRnyzGrnq5ZlV3mYq8WyapAXypohbIVfnP8Dz43Qtjf6y1v5xsd4K0fIjoRdjQ+vCAO0ZFYpo1xMI14nrUQtx4WIPXd12p95Rv8cML7vGqA+E31M6ZSguTvvjR6On/2O0ynrSkELofLhgj9ZnSKfjaBz2pbC2GzED/V82+Rjsr/k1ox1ZtzFAeIDBSt3ZwRu32gwelFVftxw0botiAzv+od4/Jq/9SKMzraSt+Fm/eWRFjkWjaAHE4DB seanpaul(a)chromium.org gpg: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1 mQENBFRzXGYBCADnkUuZDKswJpSznqtB+CM3N6G3j0937g4kNAfWzfVHWjliQH9D muIVUBsiCc/gd1RRZbu8ohidBa4qbcPBPBgqc5Lv4Lqw1lbu+Dfu2g7IlcQB7s+S kWepSWnL7rLS2aRzRbJQyXGViA5Gavnp35Amirb8VuI/EChArODO2jWijQUHeWYJ 3fRnMyJKm5NkPmOZnirclLib3shpgUxJUS5u97D7AH9Wt9KK7+9GqA/c7tY5+KGm vZEWM9T75AmwRuaEU1cBiWmDAyGLZ7Cg2RjeGHkyt1E/RLutRq18PEFmVaLCfeOG 4I71j7M9XZW7qIaPOI0XB/U5EmdLCGTWnNjHABEBAAG0IVNlYW4gUGF1bCA8c2Vh bnBhdWxAY2hyb21pdW0ub3JnPokBOAQTAQIAIgUCVHNcZgIbAwYLCQgHAwIGFQgC CQoLBBYCAwECHgECF4AACgkQGcCPkB86pMdeugf/R+Hh9UJNp4TKYi0DePLDwedC vk/FBY8AjAWBuiV0Rhaumr5DwEW4Zgv4qjrIqub4dlI0Ty4+g8Y2Cox6Kzgpz2vg 6KwVkgGg2nO3cnw2AtS9rYq/Dd72kfT41Wq7MA0GqA6CnrXKZKz3t+bhKHwCQTRJ 2SIfMPysFsfDHVC4oxoKcM5g0D5+ktqGpzxHa5SHsDkmccNlHJ4lTrfd7qXq9X9A aBgvpMMkqIm2hkAqeAhPliyU/cmYCGLEgFRq5MnXrDryEwRmFt1YO1AGOx4XO5wr nQz5YxKgxCLM8irn9HwYRArFs4gZyHExPbJTdYD8aH3erFSvWlnVL1TCVQS3oLkB DQRUc1xmAQgAsQYCU6QBuUJLZK1MSinxT4wg4Ye1DHAal5P3tDqqUc6R7spKghsN /HIbM5jiyr+Y4CE2xp2nZOt7W8L1dKbYVCtd3ywD/S+9iY7Rz3aN/S0UC5x3oK26 F8rpexI7cY0Zuqt0v8fmCSTK3gCMEU5L1CB+guwmV0scb3VIso/i2ik99e2IDR8+ ibUyo8fGGuHrQiuAu5wzsbzceSoXDdlNECKHD6I47cKgv/+/TOt7m41w3Lx3cE5k +YKlJ+me80L96v3kW3zUAAf1xepcUODlDoMkMv3gaUs33WLYf6ky5qmJvOgAvoVK uBpnALQpjW/QQaUHk9lNsvgv6hRNoTewiwARAQABiQEfBBgBAgAJBQJUc1xmAhsM AAoJEBnAj5AfOqTHTmcH+gPLQosqYw55ViV/KaUtgHKrlOyE+KpV6FcBqCBzrWZY 4cyg66pPbR0HcV8CmzqCpi+hC0tGIT2/JO0YN8bbIbRre8PNvkXxHFs3KIyr5ihh 43mzuMSRKEsEKZIt0/nAMI19ljqNArBWKpXlMwU6s5+C2b2c+fYMM5d3TxjgtPdt YkWA9BTnrGWcLNw4fPnXFGRWQz0fKjR7Wq3HZpny8pe2eX/jDBIAyn5lFmRr61dD NCyW4DIV5gfvkiZ7l1sRuqKcOCWs0Lj/VWyyzm24pn9zjavKCxBrC1O+mpknziBc Yd6azQezzPw/45syfBD4Iy2KDtfRB/YOyESrBQFjGIY= =mKjp -----END PGP PUBLIC KEY BLOCK----- -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 75241] New: radeon_compute_pll_avivo broken in 3.15-rc3
by bugzilla-daemon＠bugzilla.kernel.org 05 Jul '16

05 Jul '16

https://bugzilla.kernel.org/show_bug.cgi?id=75241 Bug ID: 75241 Summary: radeon_compute_pll_avivo broken in 3.15-rc3 Product: Drivers Version: 2.5 Kernel Version: 3.15-rc3 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: clemens(a)ladisch.de Regression: Yes After upgrading from rc2 to rc3, my RS880 no longer outputs a signal that my monitor is able to show. Bisected to this: commit c2fb3094669a3205f16a32f4119d0afe40b1a1fd Author: Christian König <christian.koenig(a)amd.com> Date: Sun Apr 20 13:24:32 2014 +0200 drm/radeon: improve PLL limit handling in post div calculation This improves the PLL parameters when we work at the limits of the allowed ranges. Debug output with black screen: kernel: [drm:drm_crtc_helper_set_config] attempting to set mode from userspace kernel: [drm:drm_mode_debug_printmodeline] Modeline 29:"1600x1200" 60 162000 1600 1664 1856 2160 1200 1201 1204 1250 0x48 0x5 kernel: [drm:radeon_encoder_set_active_device] setting active device to 00000200 from 00000200 00000200 for encoder 2 kernel: [drm:drm_crtc_helper_set_mode] [CRTC:14] kernel: [drm:radeon_atom_encoder_dpms] encoder dpms 21 to mode 3, devices 00000001, active_devices 00000000 kernel: [drm:radeon_compute_pll_avivo] 162000 - 161990, pll dividers - fb: 2036.3 ref: 30, post 6 With this commit reverted (and working screen): kernel: [drm:radeon_compute_pll_avivo] 162000 - 16106, pll dividers - fb: 1023.5 ref: 13, post 7 -- You are receiving this mail because: You are watching the assignee of the bug.

1 35

[Bug 48472] New: GPU Lockup while running demo in wine
by bugzilla-daemon＠freedesktop.org 24 Jun '16

24 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=48472 Bug #: 48472 Summary: GPU Lockup while running demo in wine Classification: Unclassified Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: nathanhirschauer(a)verfriemelt.org While running Razor 1911 - Scene is dead (http://www.chiptune.com/razor/rzr-the_scene_is_dead.zip) in wine I get a GPU Lockup: [ 690.049988] radeon 0000:01:00.0: GPU lockup CP stall for more than 10233msec [ 690.049993] GPU lockup (waiting for 0x00002749 last fence id 0x00002746) [ 690.051188] radeon 0000:01:00.0: GPU softreset [ 690.051191] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xE5700030 [ 690.051193] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00110103 [ 690.051195] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200000C0 [ 690.051202] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE [ 690.066201] radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 [ 690.082204] radeon 0000:01:00.0: R_008010_GRBM_STATUS=0xA0003030 [ 690.082206] radeon 0000:01:00.0: R_008014_GRBM_STATUS2=0x00000003 [ 690.082208] radeon 0000:01:00.0: R_000E50_SRBM_STATUS=0x200080C0 [ 690.083209] radeon 0000:01:00.0: GPU reset succeed [ 690.103443] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 690.103467] radeon 0000:01:00.0: WB enabled [ 690.134854] [drm] ring test succeeded in 1 usecs [ 690.134861] [drm] ib test succeeded in 1 usecs I'm using mesa-git (c653287) with Linux 3.2.13 (Arch Linux) and Xorg 1.12.0.901 on a Thinkpad R500 (which has the following VGA Controller: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] (Mobility Radeon HD 3450) Attached the a logfile with WINEDEBUG=+wgl,+opengl. Seems like the lockup occurs while the following message appears (Line 1232): trace:opengl:wine_glDrawArrays (7, 0, 4) I hope I attached all important files/infos - If I forgot something, let me know. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 78987] New: black screen when trying to enable external VGA screen on Trinity APU laptop
by bugzilla-daemon＠freedesktop.org 19 Jun '16

19 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=78987 Priority: medium Bug ID: 78987 Assignee: dri-devel(a)lists.freedesktop.org Summary: black screen when trying to enable external VGA screen on Trinity APU laptop Severity: major Classification: Unclassified OS: All Reporter: dev(a)lynxeye.de Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 99447 --> https://bugs.freedesktop.org/attachment.cgi?id=99447&action=edit dmesg from failing machine Plugging in an VGA monitor and trying to enable it results in black screen on both the internal laptop display as well as the external VGA monitor. The graphics is dead after this, I have not found any way to restore the screen. However the machine is still responding to ssh and I was able to pick up an quite interesting dmesg snapshot. If you need me to test patches or need any other information, just ping me. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 46713] New: HDMI audio played back at a wrong rate
by bugzilla-daemon＠freedesktop.org 15 Jun '16

15 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=46713 Bug #: 46713 Summary: HDMI audio played back at a wrong rate Classification: Unclassified Product: DRI Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: tvrtko.ursulin(a)onelan.co.uk I am experiencing audio being played back at roughly 28665Hz instead of expected 44100Hz. This rate is derived for timing for how long it takes to play sample of a known size. Pitch of audio being played is obviously comical. Hardware: AMD G-T56N (Radeon HD 6310) box connected to the monitor via native HDMI connector. This is with kernel.org 3.3.0-rc4 kernel. Only thing I see in kernel log with apparent relevance is this: [ 56.086500] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.086526] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.086545] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.086561] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.127063] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=1 [ 56.127090] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.127109] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.127125] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.387045] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.387069] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.387086] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.699469] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.699494] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.699510] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 56.990752] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.990777] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 56.990795] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 56.990811] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.001054] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.001079] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.001095] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.302064] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.302092] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.302108] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.420102] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=1 [ 57.420130] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.420149] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.420165] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.437447] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.437471] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.437489] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.437505] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.493091] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=1 [ 57.493117] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.493136] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.493152] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.618528] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.618552] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.618568] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 57.919028] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 57.919059] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 57.919075] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 58.220081] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 58.220115] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 58.220131] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 58.521039] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 [ 58.521071] ALSA sound/pci/hda/hda_eld.c:337 HDMI: ELD buf size is 0, force 128 [ 58.521087] ALSA sound/pci/hda/hda_eld.c:356 HDMI: invalid ELD data byte 0 [ 63.136948] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. While playing back hw_info looks fine: aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: SB [HDA ATI SB], device 0: ALC883 Analog [ALC883 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: SB [HDA ATI SB], device 1: ALC883 Digital [ALC883 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 cat /proc/asound/card0/pcm3p/sub0/hw_params access: RW_INTERLEAVED format: S16_LE subformat: STD channels: 2 rate: 44100 (44100/1) period_size: 5504 buffer_size: 22016 Not sure what other info should I provide? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 32

[Bug 76564] New: [AMD Fusion E-350] Radeon UVD giving incorrect fps when playing videos
by bugzilla-daemon＠freedesktop.org 15 Jun '16

15 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=76564 Priority: medium Bug ID: 76564 Assignee: dri-devel(a)lists.freedesktop.org Summary: [AMD Fusion E-350] Radeon UVD giving incorrect fps when playing videos Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jeroenk61(a)hotmail.com Hardware: x86-64 (AMD64) Status: NEW Version: 10.1 Component: Drivers/Gallium/r600 Product: Mesa Created attachment 96302 --> https://bugs.freedesktop.org/attachment.cgi?id=96302&action=edit dmesg I'm currently experiencing problems when playing videos on my AMD fusion e-350 with HD6310 graphics(r600) with OpenELEC 4 beta2, which uses Mesa 10.1 and the latest Linux 3.13 kernel. This is with the system connected through HDMI to my television. Either the video is being decoded too slow, which causes skipped frames, or it is decoding too fast, which causes missed frames. 23.976fps becomes 23.92/23.95 and sometimes goes to 22.93fps 25fps becomes 25.02 or 25.05fps 29.97 interlaced decodes with around 58fps instead of 59.94fps. It is if like the clock that is used for decoding is all over the place (PLL issue?) I confirmed with the old OpenELEC 3, which uses AMD's fglrx, and everything is playing perfectly and the fps is spot on, as in. 23.98fps, 25fps and 59.94fps. I also tried disabling the new VDPAU hardware acceleration and VDPAU mixer, but with no effect. All tests were done with the television frame rate being matched to the content, so for example in the case of 23.976fps content the television is at the same frequency. -- You are receiving this mail because: You are the assignee for the bug.

1 91

[Bug 82279] New: SDL applications crash when changing video mode: double free or corruption
by bugzilla-daemon＠freedesktop.org 15 Jun '16

15 Jun '16

https://bugs.freedesktop.org/show_bug.cgi?id=82279 Priority: medium Bug ID: 82279 Assignee: dri-devel(a)lists.freedesktop.org Summary: SDL applications crash when changing video mode: double free or corruption Severity: normal Classification: Unclassified OS: Linux (All) Reporter: xamaniqinqu(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 104195 --> https://bugs.freedesktop.org/attachment.cgi?id=104195&action=edit GDB backtrace of Dosbox crash. Overview: SDL applications crash when changing video mode, "corrupted double-linked list" and "double free or corruption" are printed to stderr. The applications tested are Dosbox and Enemy Territory: Quake Wars. Steps to reproduce: 1) Install an abandonware game such as Commander Keen 4 2) Run it in Dosbox 3) Depending on the game, press a key to start the game proper Actual results: The application crashes upon changing video mode. Expected results: The application changes video mode without causing a crash. Build date and platform: Build date of all components: 2014-08-07 Platform: Gentoo GNU/Linux x86_64 Linux kernel version: 3.16 Additional information: Bisecting revealed the culprit commit to be "58d2afa2232060b88f9c444ce7a0d6e63c841bb2: radeonsi: fix leaking the bound state on destruction v2". See attachments for backtraces. -- You are receiving this mail because: You are the assignee for the bug.

1 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2015