dri-devel February 2014

dri-devel@lists.freedesktop.org

154 participants
967 discussions

[Bug 72457] New: Crash in hwmon_attributes_visible
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=72457 Priority: medium Bug ID: 72457 Assignee: dri-devel(a)lists.freedesktop.org Summary: Crash in hwmon_attributes_visible Severity: normal Classification: Unclassified OS: Linux (All) Reporter: g02maran(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 90435 --> https://bugs.freedesktop.org/attachment.cgi?id=90435&action=edit patch I tried the drm-fixes-3.13 branch but it crashes for me in hwmon_attributes_visible. If I revert commit ec39f64bba3421c2060fcbd1aeb6eec81fe0a42d (drm/radeon/dpm: Convert to use devm_hwmon_register_with_groups) the crash disappears. The attached patch fixes the issue for me. I only had a problem with the hwmon_attributes_visible function, but looking at the code it seems to me that the same fix is needed in radeon_hwmon_show_temp_thresh as well. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 72283] New: [<ffffffffa01b7ecb>] dce6_afmt_write_speaker_allocation+0xdb/0x140 [radeon]
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=72283 Priority: medium Bug ID: 72283 Assignee: dri-devel(a)lists.freedesktop.org Summary: [<ffffffffa01b7ecb>] dce6_afmt_write_speaker_allocation+0xdb/0x140 [radeon] Severity: critical Classification: Unclassified OS: Linux (All) Reporter: bgunteriv(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/r600 Product: Mesa Not sure if this has been known. After trying to update to kernel 3.13rc2, I get problems booting my mini.iso system. Once the system loads, it loses the HDMI signal, and I get no picture. I get errors talking about the HAWAII drivers not loaded: update-initramfs: Generating /boot/initrd.img-3.13.0-031300rc2-generic W: Possible missing firmware /lib/firmware/radeon/HAWAII_smc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/HAWAII_sdma.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/HAWAII_rlc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/HAWAII_mc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/HAWAII_mec.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/HAWAII_ce.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/HAWAII_me.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/HAWAII_pfp.bin for module radeon here are my log files:xbmc@xbmc:~$ dmesg | pastebinit http://paste.ubuntu.com/6514897/ xbmc@xbmc:~$ cat ~/.xbmc/temp/xbmc.log | pastebinit http://paste.ubuntu.com/6514899/ xbmc@xbmc:~$ cat /var/log/Xorg.0.log | pastebinit http://paste.ubuntu.com/6514901/ xbmc@xbmc:~$ DISPLAY=:0 vdpauinfo | pastebinit [1]+ Stopped DISPLAY=:0 vdpauinfo | pastebinit xbmc@xbmc:~$ dpkg -l | grep mesa | pastebinit http://paste.ubuntu.com/6514909/ as you can see, when I try to run DISPLAY=:0 vdpauinfo, my system hangs, and I have to force kill the command. -- You are receiving this mail because: You are the assignee for the bug.

1 34

[Bug 72051] New: [JUNIPER] with kernel 3.12 some HDMI screens are not recognized
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=72051 Priority: medium Bug ID: 72051 Assignee: dri-devel(a)lists.freedesktop.org Summary: [JUNIPER] with kernel 3.12 some HDMI screens are not recognized Severity: normal Classification: Unclassified OS: Linux (All) Reporter: eugene.shalygin+bugzilla.FDO(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 89860 --> https://bugs.freedesktop.org/attachment.cgi?id=89860&action=edit xrandr -q --verbose with screen 1 connected I have two external screens, say screen 1 and 2. Screen 1 have HDMI input and screens 2 is connected via HDMI-to-DVI adapter. With kernel 3.12 screen 1 is not recognized on connect anymore. Booting kernel 3.11.9 makes it work again. When I connect screen 1 nothing appears not in Xorg.0.log nor in dmesg -- You are receiving this mail because: You are the assignee for the bug.

1 15

[Bug 71864] New: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71864 Priority: medium Bug ID: 71864 Assignee: dri-devel(a)lists.freedesktop.org Summary: [RS690] GPU Lockup CP Stall and Resulting Kernel Oops (Kernel 3.2.0) Severity: critical Classification: Unclassified OS: Linux (All) Reporter: reimth(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI [Problem] Since upgrade from kernel 2.6.35 to kernel 3.2.0 (Ubuntu 12.04) we experience numerous kernel freezes (no keyboard/mouse, no kernel logging, no num key change, stop of server applications, e. g. dhcpd, postfix, bind9, magic keys not working, no serial console), that can only be resolved by switching power off (hard reset). There is no clear way to reproduce this bug. The likelihood of the kernel crash increases, if mail GUIs like Evolution or Thunderbird are open or Firefox is open and when switching between these windows. The kernel freezes latest within 6 h. Whereas if just the desktop and xterm is running, the system seems to be stable (48 h and more). The bug can be confirmed under lightdm/unity as desktop, as well as when using mdm/cinnamon. Log information can only be retrieved using netconsole. They show a GPU lockup and CP stall, from which the radeon driver cannot recover. [Configuration Specifics] We run two X Servers: one controlled by the display manager (on vt7 or vt8) and one controlled by xinit (on vt9). See attached process list. We use the DVI port of the integrated Radeon X1200 (RS690) display controller on an ASUS MSA mainboard. One monitor (Samsung) is connected. Radeon driver with KMS enabled is used. [Netconsole Output] The last kernel log messages that reach the netconsole receiver vary: a) The shortest log [212173.596044] radeon 0000:01:05.0: GPU lockup CP stall for more than 10000msec [212175.370234] radeon 0000:01:05.0: failed to reset GPU [212175.406899] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3). [212175.406912] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! b) A longer one [286295.708052] radeon 0000:01:05.0: GPU lockup CP stall for more than 10020msec [286297.455900] radeon 0000:01:05.0: failed to reset GPU [286297.929150] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(14). [286297.929174] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.937321] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(15). [286297.937349] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.943050] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0). [286297.943074] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.947188] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1). [286297.947213] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! [286297.949490] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2). [286297.949509] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! c) GPU reset attempt [179005.128038] radeon 0000:01:05.0: GPU lockup CP stall for more than 10032msec [179005.128068] GPU lockup (waiting for 0x0004E1FF last fence id 0x0004E1F4) [179005.268649] radeon: wait for empty RBBM fifo failed ! Bad things might happen. [179005.409044] Failed to wait GUI idle while programming pipes. Bad things might happen. [179005.410064] radeon 0000:01:05.0: (rs600_asic_reset:348) RBBM_STATUS=0x9401C100 [179005.908155] radeon 0000:01:05.0: (rs600_asic_reset:367) RBBM_STATUS=0x9401C100 [179006.405224] radeon 0000:01:05.0: (rs600_asic_reset:375) RBBM_STATUS=0x9400C100 [179006.902280] radeon 0000:01:05.0: (rs600_asic_reset:383) RBBM_STATUS=0x9400C100 [179006.902315] radeon 0000:01:05.0: restoring config space at offset 0x1 (was 0x100403, writing 0x100407) [179006.902346] radeon 0000:01:05.0: failed to reset GPU [179006.903346] radeon 0000:01:05.0: GPU reset failed d) Successful GPU reset but inaccessible CP [ 1775.356043] radeon 0000:01:05.0: GPU lockup CP stall for more than 10008msec [ 1775.356067] GPU lockup (waiting for 0x000124ED last fence id 0x000124EA) [ 1775.919383] radeon: wait for empty RBBM fifo failed ! Bad things might happen. [ 1776.059845] Failed to wait GUI idle while programming pipes. Bad things might happen. [ 1776.060872] radeon 0000:01:05.0: (rs600_asic_reset:348) RBBM_STATUS=0xB001C100 [ 1776.559021] radeon 0000:01:05.0: (rs600_asic_reset:367) RBBM_STATUS=0x90010140 [ 1777.056092] radeon 0000:01:05.0: (rs600_asic_reset:375) RBBM_STATUS=0x10000140 [ 1777.553160] radeon 0000:01:05.0: (rs600_asic_reset:383) RBBM_STATUS=0x10000140 [ 1777.553197] radeon 0000:01:05.0: restoring config space at offset 0x1 (was 0x100403, writing 0x100407) [ 1777.553232] radeon 0000:01:05.0: GPU reset succeed [ 1777.554232] radeon 0000:01:05.0: GPU reset succeed [ 1777.554263] sched: RT throttling activated [ 1777.749090] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [ 1777.754590] [drm] PCIE GART of 512M enabled (table at 0x0000000036700000). [ 1777.754958] radeon 0000:01:05.0: WB enabled [ 1777.754991] [drm] radeon: ring at 0x0000000080001000 [ 1777.892767] [drm:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD) [ 1777.892774] [drm:r100_cp_init] *ERROR* radeon: cp isn't working (-22). [ 1777.892783] radeon 0000:01:05.0: failed initializing CP (-22). [ 1786.390793] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(11). [ 1786.390818] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB ! A really verbose log with drm.debug set to 0xf has been attached. As well as the usually required information. -- You are receiving this mail because: You are the assignee for the bug.

1 22

[Bug 71753] New: Radeon Audio clock running wrong speed
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71753 Priority: medium Bug ID: 71753 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon Audio clock running wrong speed Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fritsch(a)xbmc.org Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI When syncing radeon audio to a systemclock one realizes that it goes wrong approximately 10ms per 6 seconds. For example with 60hz and 50hz the audio clock is 10ms / 6 seconds too fast, which causes great issues, when watching e.g. LiveTV. When displaying at 24hz the audio clock is approximately 10ms / 6 seconds too slow, which can be workarounded by doubling packages. You can only realize this problem, if you don't use any resample algorithms to make audio fit. Some output from an xbmc.log: Configuration: 50hz no sync playback to display. Kernel 3.12 (Pierre Ossmann patch applied) with mesa git 19:46:13 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62710358734.243919, should be:62710332298.764549, error:-26435.479370 19:46:16 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62712528103.582550, should be:62712508710.849106, error:-19392.733447 19:46:17 T:139718566078208 DEBUG: CPullupCorrection: detected pattern of length 1: 40000.00, frameduration: 40000.000000 19:46:22 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62718996472.639107, should be:62719007584.295349, error:11111.656243 19:46:28 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62725295876.976349, should be:62725306470.191048, error:10593.214698 19:46:35 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62731698477.715050, should be:62731709235.032417, error:10757.317365 19:46:38 T:139719056176896 DEBUG: Thread JobWorker 139719056176896 terminating (autodelete) 19:46:41 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62738297284.064415, should be:62738308465.384331, error:11181.319916 19:46:48 T:139718574470912 DEBUG: CDVDPlayerAudio:: Discontinuity2 - was:62744796455.484329, should be:62744807397.750954, error:10942.266624 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 71697] New: [radeonsi] gtkperf hangs the system
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71697 Priority: medium Bug ID: 71697 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi] gtkperf hangs the system Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI HD 7950 drm-next-3.13 (agd5f tree) libdrm git mesa git xf86-video-ati git xorg-server-1.14.4 + DRI-loader-entrypoint glamor git llvm 3.4 git The system hangs about a minute after gtkperf started, there is nothing in /var/log/messages. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 71067] New: [drm:r600] UVD not responding OR failed testing IB on GFX ring
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=71067 Priority: medium Bug ID: 71067 Assignee: dri-devel(a)lists.freedesktop.org Summary: [drm:r600] UVD not responding OR failed testing IB on GFX ring Severity: normal Classification: Unclassified OS: All Reporter: timothee.romain.ravier(a)gmail.com Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI When I boot 3.10 or 3.11 kernels, I get either one of those errors, apparently at random : * UVD not responding, trying to reset the VCPU -> Full log attached: *freeze-boot-then-yellow.log The display turns yellow when the X server starts. I can still use VT and there is no corruption there. I made sure that I got the latest firmware and I also checked my initrd (following instructions in 65270); * GPU lockup CP stall for more than 10000msec GPU lockup (waiting for 0x000000000000020e last fence id 0x00000000000001ec) r600_ib_test] *ERROR* radeon: fence wait failed (-35) radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35) -> Full log attached: *freeze-cursor.log I can log into my graphical session, but quickly after that, everything freeze and I can only move the cursor which displays as a "corrupted" square. Again VT are fine. I filed only one bug report as I get both issue using the same software and boot command line. At the beginning I had bug 67994, which turned into this one. I tried downgrading the kernel without much success for now. Booting with nomodeset works perfectly (with no accel/KMS obviously) and booting under Windows 7 too. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 70543] New: [r600g] HD5450 + uvd + hdmi flickers
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=70543 Priority: medium Bug ID: 70543 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] HD5450 + uvd + hdmi flickers Severity: normal Classification: Unclassified OS: All Reporter: stompdagger1(a)yahoo.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 87753 --> https://bugs.freedesktop.org/attachment.cgi?id=87753&action=edit X's session log I have a HD5450 hooked up to my lcd tv as part of a multiseat setup. every few seconds the feed flickers. usually I use xbmc to view content but it happens with VBox too. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 70542] New: [r600g] HD5450 + uvd + hdmi flickers
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=70542 Priority: medium Bug ID: 70542 Assignee: dri-devel(a)lists.freedesktop.org Summary: [r600g] HD5450 + uvd + hdmi flickers Severity: normal Classification: Unclassified OS: All Reporter: stompdagger1(a)yahoo.com Hardware: Other Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 87752 --> https://bugs.freedesktop.org/attachment.cgi?id=87752&action=edit seat greetings, I have a HD5450 hooked up to my lcd tv as part of a multiseat setup. every few seconds the feed flickers. usually I use xbmc to view content but it happens with VBox too. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 70514] New: Unresponsive system on boot with radeon + FireGL v7700
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=70514 Priority: medium Bug ID: 70514 Assignee: dri-devel(a)lists.freedesktop.org Summary: Unresponsive system on boot with radeon + FireGL v7700 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: noryb009(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: 9.2 Component: Drivers/Gallium/r600 Product: Mesa I'm using a FireGL V7700 with Arch Linux x64. When booting to a command line, when drivers are loaded, the screen goes into power saving mode, and the system becomes unresponsive. Booting with `nomodeset' works OK. If I run "$ modprobe radeon modeset=1", the screen goes power saving mode, the system stops responding to open ssh session(s), and the caps lock key no longer works (kernel panic?). I've also tested with a Puppy Linux Live-CD, with the same results (unresponsive on driver load). I've tested a HD 4650 in the same system, and everything works fine. $ lspci -v | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV670 GL [FireGL V7700] (prog-if 00 [VGA controller]) -- You are receiving this mail because: You are the assignee for the bug.

1 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel February 2014