dri-devel March 2014

dri-devel@lists.freedesktop.org

144 participants
926 discussions

[Bug 76286] New: Kernel v3.13 hang during boot now that dpm is enabled for radeon driver - Radeon HD4870
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=76286 Priority: medium Bug ID: 76286 Assignee: dri-devel(a)lists.freedesktop.org Summary: Kernel v3.13 hang during boot now that dpm is enabled for radeon driver - Radeon HD4870 Severity: major Classification: Unclassified OS: Linux (All) Reporter: OmegaPhil+FreeDesktop.BugTracker(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 95961 --> https://bugs.freedesktop.org/attachment.cgi?id=95961&action=edit Kernel log for session with manual radeon module loading with modesetting enabled Flagged as major as this prevents kernel boot if the user doesnt know how to disable the functionality with the kernel boot parameters. Originally reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741619 , Debian kernel v3.13 enables dpm by default - partway through the boot process (when cryptsetup is opening encrypted disks), the kernel hangs (confirmed with no response to ping). The kernel boots fine with radeon.dpm=0. Following instructions (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741485#10) I booted with radeon.modeset=0, made sure X wasn't running and radeon was unloaded, then modprobe'd radeon modeset=1 - after a small delay everything hung. I have attached kern.log (REISUB FTW this time it seems?), there is an X log but that simply gave up after finding no modesetting support, before the point where I reloaded radeon. kern.log is verbose as I always boot with full debugging information, but in this case its useless as nothing appears to be logged associated with the radeon load (and I'm assuming the magic sync worked). In terms of fighting the issue, I have C and C++ experience but no real kernel debugging EXP and certainly nothing todo with the graphical stack. =============================== uname -a: Linux omega1 3.13-1-amd64 #1 SMP Debian 3.13.5-1 (2014-03-04) x86_64 GNU/Linux Debian Testing X server: 1.15.0 Radeon: 7.3.0 -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 76210] New: Temperature sensor is showing too high temperatures
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=76210 Priority: medium Bug ID: 76210 Assignee: dri-devel(a)lists.freedesktop.org Summary: Temperature sensor is showing too high temperatures Severity: minor Classification: Unclassified OS: All Reporter: nicolas.belouin(a)heptaoctet.net Hardware: Other Status: NEW Version: unspecified Component: Drivers/Gallium/radeonsi Product: Mesa The temperature sensors are showing a temperature of 511°C when the radeon card is in sleep mode, the normal temperature is displayed when the card is used. -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 76130] New: Radeon HD 4570 set dpm state fails after suspend
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=76130 Priority: medium Bug ID: 76130 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD 4570 set dpm state fails after suspend Severity: normal Classification: Unclassified OS: Linux (All) Reporter: crew4ok(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 95731 --> https://bugs.freedesktop.org/attachment.cgi?id=95731&action=edit dmesg Right before the system go to suspend, the following line appears in dmesg: [drm:rv730_stop_dpm] *ERROR* Could not force DPM to low After wakeup i see this in dmesg: [drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed Also i notice a degradation in performance in some games (e.g. in Teeworlds before the suspend i have 60fps, after suspend - 30-40 fps). -- You are receiving this mail because: You are the assignee for the bug.

1 25

[Bug 75719] New: mplayer -vo gl consume more CPU on r200
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75719 Priority: medium Bug ID: 75719 Assignee: dri-devel(a)lists.freedesktop.org Summary: mplayer -vo gl consume more CPU on r200 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: smoki00790(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI OS is current Debian Sid 32bit, card 1002:5960... So this is on r200 i spotted playing any video file vith gl render (but also many videos in games are also affected), bisecting says it started with this code in ttm: http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-next&id=a095c60bd0… And it performs the same also in 3.14-rc5 kernel :). It consume cca 40% or more CPU power after that commit... that *more* depends on video file and if it is in game or playing video file with mplayer -vo gl. Mesa version seems doesn't metter i tried 9.2 git, 10.0 git, 10.1 git and current git master. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 75649] New: Glitchy output using only HDMI on laptop with AMD Mobility Radeon HD 3450/3470
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 15

[Bug 75136] New: Radeon HD
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75136 Priority: medium Bug ID: 75136 Assignee: dri-devel(a)lists.freedesktop.org Summary: Radeon HD Severity: normal Classification: Unclassified OS: Linux (All) Reporter: tmciolek(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Radeon DRM fails on boot... this is observed with kernle 3.12.x and 3.13.x [ 92.918254] [drm:radeon_dp_link_train_cr] *ERROR* displayport link status failed [ 92.918258] [drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed [ 92.932698] ------------[ cut here ]------------ [ 92.932712] WARNING: CPU: 5 PID: 3664 at drivers/gpu/drm/drm_crtc.c:2029 drm_mode_set_config_internal+0x62/0xac [drm]() [ 92.932713] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp tun bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables bnep rfcomm bluetooth parport_pc parport binfmt_misc ipv6 it87 hwmon_vid firewire_sbp2 loop fuse radeon ttm drm_kms_helper drm snd_hda_codec_hdmi snd_usb_audio snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_usbmidi_lib snd_hwdep snd_pcm_oss pwc snd_mixer_oss snd_pcm videobuf2_vmalloc joydev videobuf2_memops hid_apple v4l2_common hid_generic usbhid evdev snd_page_alloc hid videobuf2_core acpi_cpufreq snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq kvm_amd videodev cfbfillrect freq_table kvm processor k10temp pcspkr serio_raw cfbimgblt edac_core cfbcopyarea media sp5100_tco snd_seq_device snd_timer thermal_sys snd edac_mce_amd i2c_algo_bit i2c_piix4 i2c_core hwmon soundcore button ext3 jbd sg sr_mod sd_mod cdrom crc_t10dif crct10dif_common dm_mod xhci_hcd ata_generic ahci libahci pata_jmicron libata ehci_pci firewire_ohci microcode ohci_pci ohci_hcd firewire_core ehci_hcd r8169 usbcore crc_itu_t scsi_mod mii usb_common [ 92.932769] CPU: 5 PID: 3664 Comm: Xorg Not tainted 3.12.9 #1 [ 92.932771] Hardware name: Gigabyte Technology Co., Ltd. GA-870A-UD3/GA-870A-UD3, BIOS F5 08/01/2011 [ 92.932773] 0000000000000006 ffffffff8138712a 0000000000000000 ffffffff810348cb [ 92.932776] ffffffffa03c0b0f ffff88040bf26000 ffff88040c382240 0000000000000000 [ 92.932778] ffff88040bf26000 ffffffffa03c0b0f ffff8800cf89de20 ffff88040c382240 [ 92.932780] Call Trace: [ 92.932786] [<ffffffff8138712a>] ? dump_stack+0x4a/0x7e [ 92.932790] [<ffffffff810348cb>] ? warn_slowpath_common+0x74/0x89 [ 92.932797] [<ffffffffa03c0b0f>] ? drm_mode_set_config_internal+0x62/0xac [drm] [ 92.932803] [<ffffffffa03c0b0f>] ? drm_mode_set_config_internal+0x62/0xac [drm] [ 92.932810] [<ffffffffa03c2d0e>] ? drm_mode_setcrtc+0x41d/0x4c2 [drm] [ 92.932816] [<ffffffffa03b7a4b>] ? drm_ioctl+0x289/0x3bf [drm] [ 92.932822] [<ffffffffa03c28f1>] ? drm_mode_setplane+0x32e/0x32e [drm] [ 92.932825] [<ffffffff810e5c49>] ? do_mmap_pgoff+0x2d8/0x33d [ 92.932829] [<ffffffff81114655>] ? vfs_ioctl+0x1b/0x28 [ 92.932831] [<ffffffff81114d71>] ? do_vfs_ioctl+0x32d/0x3e8 [ 92.932833] [<ffffffff81114e7a>] ? SyS_ioctl+0x4e/0x7b [ 92.932836] [<ffffffff813902e6>] ? system_call_fastpath+0x1a/0x1f [ 92.932837] ---[ end trace d0bfb4b26dcd2b69 ]--- card is a Barts LE [Radeon HD 6790] with monitors plugged into two DVI ports Distro is Debian/Jesse xorg packages installed are:ii xorg-sgml-doctools 1:1.11-1 all Common tools for building X.Org SGML documentation ii xserver-xorg 1:7.7+6 amd64 X.Org X server ii xserver-xorg-core 2:1.14.5-1 amd64 Xorg X server - core server ii xserver-xorg-dev 2:1.14.5-1 amd64 Xorg X server - development files ii xserver-xorg-input-all 1:7.7+6 amd64 X.Org X server -- input driver metapackage ii xserver-xorg-input-evdev 1:2.8.2-1 amd64 X.Org X server -- evdev input driver ii xserver-xorg-input-mouse 1:1.9.0-1+b1 amd64 X.Org X server -- mouse input driver ii xserver-xorg-input-synaptics 1.7.3-1 amd64 Synaptics TouchPad driver for X.Org server ii xserver-xorg-input-vmmouse 1:13.0.0-1+b1 amd64 X.Org X server -- VMMouse input driver to use with VMWare ii xserver-xorg-input-wacom 0.23.0+20131011-1 amd64 X.Org X server -- Wacom input driver ii xserver-xorg-video-ati 1:7.3.0-1 amd64 X.Org X server -- AMD/ATI display driver wrapper ii xserver-xorg-video-mach64 6.9.4-1+b1 amd64 X.Org X server -- ATI Mach64 display driver ii xserver-xorg-video-r128 6.9.2-1 amd64 X.Org X server -- ATI r128 display driver ii xserver-xorg-video-radeon 1:7.3.0-1 amd64 X.Org X server -- AMD/ATI Radeon display driver Other questions: please ask Happy to apply and/or test patches -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 75134] New: UVD doesn't survive a GPU crash on a Radeon HD 6770
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=75134 Priority: medium Bug ID: 75134 Assignee: dri-devel(a)lists.freedesktop.org Summary: UVD doesn't survive a GPU crash on a Radeon HD 6770 Severity: normal Classification: Unclassified OS: All Reporter: nmiell(a)gmail.com Hardware: Other Status: NEW Version: unspecified Component: Drivers/DRI/Radeon Product: Mesa UVD isn't reinitialized after a GPU crash. GPU is a Radeon HD 6770, which is a Evergreen-based Juniper XT. Kernel is 3.13.3-201.fc20.x86_64 X is xorg-x11-server-Xorg-1.14.4-6.fc20.x86_64 Mesa is current master (adad8fb2e947e3ea9e9d84cb3722e46de91346e4). Reproducing: 1. vdpauinfo's output before the crash: Decoder capabilities: name level macbs width height ------------------------------------------- MPEG1 0 9216 2048 1152 MPEG2_SIMPLE 3 9216 2048 1152 MPEG2_MAIN 3 9216 2048 1152 H264_BASELINE 41 9216 2048 1152 H264_MAIN 41 9216 2048 1152 H264_HIGH 41 9216 2048 1152 VC1_SIMPLE 1 9216 2048 1152 VC1_MAIN 2 9216 2048 1152 VC1_ADVANCED 4 9216 2048 1152 2. Crash the GPU. DoubleFine's The Cave or Brütal Legend are good for this. 3. vdpauinfo's output after the crash: Decoder capabilities: name level macbs width height ------------------------------------------- MPEG1 0 1048576 16384 16384 MPEG2_SIMPLE 3 1048576 16384 16384 MPEG2_MAIN 3 1048576 16384 16384 4. Relevant kernel logs: radeon 0000:01:00.0: GPU lockup CP stall for more than 10104msec radeon 0000:01:00.0: GPU lockup (waiting for 0x000000000012605f last fence id 0x0000000000126059 on ring 0) [drm] Disabling audio 0 support radeon 0000:01:00.0: Saved 311 dwords of commands on ring 0. radeon 0000:01:00.0: GPU softreset: 0x00000009 radeon 0000:01:00.0: GRBM_STATUS = 0xF0001828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x80000003 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40040000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048002 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268643 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88031ac2dc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88031ac2dc0c radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9001219c418 [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] Enabling audio 0 support ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD radeon 0000:01:00.0: GPU lockup CP stall for more than 10001msec radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000126064 last fence id 0x0000000000126060 on ring 0) [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). radeon 0000:01:00.0: ib ring test failed (-35). [drm] Disabling audio 0 support radeon 0000:01:00.0: GPU softreset: 0x00000009 radeon 0000:01:00.0: GRBM_STATUS = 0xF0001828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x80000003 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40040000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268643 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume CE: hpet increased min_delta_ns to 20115 nsec CE: hpet increased min_delta_ns to 30172 nsec [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88031ac2dc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88031ac2dc0c radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9001219c418 [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] Enabling audio 0 support [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 1 usecs ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD [drm:uvd_v1_0_ib_test] *ERROR* radeon: failed to get create msg (-22). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). switching from power state: ui class: none internal class: boot caps: video uvd vclk: 0 dclk: 0 power level 0 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 1 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: c b switching to power state: ui class: performance internal class: none caps: single_disp video uvd vclk: 0 dclk: 0 power level 0 sclk: 15700 mclk: 30000 vddc: 950 vddci: 0 power level 1 sclk: 50000 mclk: 110000 vddc: 1100 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: r ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD [drm] Disabling audio 0 support radeon 0000:01:00.0: Saved 247 dwords of commands on ring 0. radeon 0000:01:00.0: GPU softreset: 0x00000009 radeon 0000:01:00.0: GRBM_STATUS = 0xF0001828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x80000003 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x20000AC0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40040000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00048006 radeon 0000:01:00.0: R_008680_CP_STAT = 0x80268647 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 radeon 0000:01:00.0: GPU reset succeeded, trying to resume [drm] PCIE gen 2 link speeds already enabled [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). radeon 0000:01:00.0: WB enabled radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88031ac2dc00 radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88031ac2dc0c radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0xffffc9001219c418 [drm] ring test on 0 succeeded in 1 usecs [drm] ring test on 3 succeeded in 1 usecs [drm] ring test on 5 succeeded in 1 usecs [drm] UVD initialized successfully. [drm] Enabling audio 0 support ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD [drm] ib test on ring 0 succeeded in 0 usecs [drm] ib test on ring 3 succeeded in 1 usecs [drm:uvd_v1_0_ib_test] *ERROR* radeon: failed to get create msg (-22). [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-22). switching from power state: ui class: none internal class: boot caps: video uvd vclk: 0 dclk: 0 power level 0 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 1 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: c b switching to power state: ui class: performance internal class: none caps: single_disp video uvd vclk: 0 dclk: 0 power level 0 sclk: 15700 mclk: 30000 vddc: 950 vddci: 0 power level 1 sclk: 50000 mclk: 110000 vddc: 1100 vddci: 0 power level 2 sclk: 80000 mclk: 110000 vddc: 1125 vddci: 0 status: r ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD ALSA sound/pci/hda/hda_eld.c:684 HDMI ATI/AMD: no speaker allocation for ELD -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 75127] New: Radeon SUMO: atombios stuck executing
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 46

[Bug 75102] New: Radeon 4890 getting a blank screen and fans go up to 100% (kernel 3.13.3)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 15

[Bug 74974] New: [radeonsi] x264 OpenCL does not work
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

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.

1 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2014