dri-devel October 2013

dri-devel@lists.freedesktop.org

171 participants
926 discussions

[Bug 67994] New: System freezes when playing video on open source AMD drivers with VDPAU
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67994 Priority: medium Bug ID: 67994 Assignee: dri-devel(a)lists.freedesktop.org Summary: System freezes when playing video on open source AMD drivers with VDPAU Severity: normal Classification: Unclassified OS: Linux (All) Reporter: scorp.exe(a)yandex.ua Hardware: x86 (IA32) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Kernel - Linux 3.11rc4 Version mesa-common-dev - 9.2.0~git20130729+9.2.9b8ad643-0ubuntu0sarvatt~raring Version libg3dvl-mesa - 9.3~git1308091520.e8d897~gd~r Driver - Gallium 0.4 To repeat the freezing - start the video on player with support for VDPAU (mplayer or XBMC), stop it, and then run another video. -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 67970] New: Kernel bugs related to the powersaving features of mobility radeon x1400
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67970 Priority: medium Bug ID: 67970 Assignee: dri-devel(a)lists.freedesktop.org Summary: Kernel bugs related to the powersaving features of mobility radeon x1400 Severity: blocker Classification: Unclassified OS: Linux (All) Reporter: shayanmansuri(a)yahoo.com Hardware: All Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I have a Mobility Radeon X1400 (RV500 Family) on my dell inspiron 6400 (or it's called inspiron 1501 or 1505 elsewhere). I use Open-source drivers and they work for me and I have no problem with anything except the powermanagement at kernel level. When I want to activate powersaving feature I use these commands: 1. when I use this command: echo dynpm > /sys/class/drm/card0/device/power_method nothing happens. I mean GPU frequency remain high. I even do not use a GUI. I'm in the shell. 2. when I use these commands echo profile > /sys/class/drm/card0/device/power_method echo low > /sys/class/drm/card0/device/power_profile I receive these error: kernel:[ 192.253008] NMI: PCI system error (SERR) for reason b1 on CPU 0. kernel:[ 192.253016] Dazed and confused, but trying to continue I have noticed that the kernel do not changes the GPU and Vram frequencies correctly in the profile mode. This is what I get when I set it to mid: # echo mid > /sys/class/drm/card0/device/power_profile # cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 432000 kHz current engine clock: 209250 kHz default memory clock: 396000 kHz current memory clock: 135000 kHz PCIE lanes: 1 This is what I get when I set it to low: # echo low > /sys/class/drm/card0/device/power_profile # cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 432000 kHz current engine clock: 324000 kHz default memory clock: 396000 kHz current memory clock: 135000 kHz PCIE lanes: 1 This is what I get when I set it to high: # echo high > /sys/class/drm/card0/device/power_profile # cat /sys/kernel/debug/dri/0/radeon_pm_info default engine clock: 432000 kHz current engine clock: 432000 kHz default memory clock: 396000 kHz current memory clock: 396000 kHz PCIE lanes: 0 If you look at the above values, it is obvious that the current clock of mid and low profiles should be replaced with each other. I've tested this in different distribution of GNU/Linux with different kernel versions: Including Ubuntu, LMDE, Archlinux and Chakra. with these kernel versions: 2.6.38, 2.6.39, 3.0.0 RC5, 3.0.0-1-amd64 in LMDE, and lately with 3.4.55 LTS in ubuntu 12.04.2. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 67946] New: Switching to Integrated card to vgaswitcheroo with radeon.audio=1 makes kernel to hang
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67946 Priority: medium Bug ID: 67946 Assignee: dri-devel(a)lists.freedesktop.org Summary: Switching to Integrated card to vgaswitcheroo with radeon.audio=1 makes kernel to hang Severity: normal Classification: Unclassified OS: All Reporter: mail(a)3v1n0.net Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I've a Mobility Radeon HD 5650 muxed with an intel card. If I boot with radeon.audio=1 and I switch the radeon card off when pulseaudio is running, then the kernel hangs as soon as I close X: [ 489.177732] hda-intel 0000:01:00.1: Disabling via VGA-switcheroo [ 489.297129] hda-intel 0000:01:00.1: Cannot lock devices! [ 489.297139] radeon: switched off [ 489.300356] [drm] Disabling audio support [ 489.319552] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000015e418 and cpu addr 0xffffc90009df0418 [ 489.973886] ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event: unsupported [ 489.973903] _handle_hotplug_event_root: Bus check notify on \_SB_.PCI0 [ 678.992375] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 678.992453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996303] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 683.996377] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C3DC (len 871, WS 0, PS 0) @ 0xC439 [ 689.000275] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 689.000349] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 694.004285] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 694.004363] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.008330] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 699.008414] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.514458] init: tty1 main process (2460) killed by QUIT signal [ 699.514489] init: tty1 main process ended, respawning [ 704.012405] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 704.012492] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 709.016515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 709.016596] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 These errors doesn't happen instead if I close X and kill pulseaudio before switching cards. Not sure if this is a pulseaudio issue or a kernel one (that should notify pulseaudio about the unplugged HDMI audio card). -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 67876] New: linux v4.11-rc1 many drm:radeon_ttm_backend_bind ERROR failed to bind 2025 pages issued during boot
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67876 Priority: medium Bug ID: 67876 Assignee: dri-devel(a)lists.freedesktop.org Summary: linux v4.11-rc1 many drm:radeon_ttm_backend_bind ERROR failed to bind 2025 pages issued during boot Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jim.cromie(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI during boot of linux 3.11-rc1+ apparently just after switch over to fb, I get a raft of errors like this (copied from a photo) [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 2250 pages at 0x000000.. [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (always-same-tuple) size : 888xxxxx bytes alignment : 0 bytes domains : 2 Eventually, they stop, and boot continues normally, and machine is functional. If I hit escape (any key?) then the stream of errors is interrupted, and systemd boot continues, again normally. dmesg then contains many of these: (almost exclusively these) WARNING: at /home/jimc/projects/lx/linux-2.6/drivers/gpu/drm/radeon/radeon_gart.c:280 radeon_gart_bind+0xe9/0xf0 [radeon]() trying to bind memory to uninitialized GART ! Modules linked in: ebtable_nat ebtables configs ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_CHECKSUM iptable_mangle bridge stp llc be2iscsi rfcomm iscsi_boot_sysfs bnx2i bnep cnic uio cxgb4i cxgb4 cxgb3i cxgb3 nf_conntrack_tftp ip6t_REJECT xt_physdev mdio libcxgbi ib_iser nf_conntrack_ipv6 rdma_cm ib_addr iw_cm nf_conntrack_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 ib_cm ib_sa xt_state nf_conntrack ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6table_filter ip6_tables it87 hwmon_vid snd_hda_codec_hdmi snd_hda_codec_via snd_hda_intel snd_hda_codec snd_usb_audio snd_usbmidi_lib nfsd snd_hwdep auth_rpcgss oid_registry nfs_acl lockd snd_seq snd_pcm sunrpc snd_rawmidi snd_page_alloc snd_seq_device acpi_cpufreq btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops snd_timer mperf videobuf2_core videodev media snd r8169 tulip serio_raw sp5100_tco i2c_piix4 k10temp dcdbas microcode rfkill mii soundcore vhost_net tun macvtap macvlan kvm_amd kvm uinput binfmt_misc ata_generic pata_acpi usb_storage pata_atiixp radeon i2c_algo_bit drm_kms_helper ttm drm i2c_core CPU: 0 PID: 161 Comm: plymouthd Tainted: G W 3.10.0-rc5-x2-00131-gdc50ba7 #27 Hardware name: Dell Inc. Inspiron 546 /0F896N, BIOS A11 01/19/2010 0000000000000009 ffff88021f81b8c8 ffffffff81610fc9 ffff88021f81b908 ffffffff8104a590 ffff88021f81b8e8 ffff88022148c100 ffff88021ffd4000 ffff88021ffd4a18 ffff88021f81bad8 ffff880209c16448 ffff88021f81b968 Call Trace: [<ffffffff81610fc9>] dump_stack+0x19/0x1b [<ffffffff8104a590>] warn_slowpath_common+0x70/0xa0 [<ffffffff8104a676>] warn_slowpath_fmt+0x46/0x50 [<ffffffffa009cc99>] radeon_gart_bind+0xe9/0xf0 [radeon] [<ffffffffa009a127>] radeon_ttm_backend_bind+0x37/0xa0 [radeon] [<ffffffffa0069d0f>] ttm_tt_bind+0x4f/0x70 [ttm] [<ffffffffa006c1bf>] ttm_bo_handle_move_mem+0x59f/0x630 [ttm] [<ffffffffa006cd90>] ? ttm_bo_mem_space+0x180/0x360 [ttm] [<ffffffffa006d097>] ttm_bo_move_buffer+0x127/0x140 [ttm] [<ffffffffa006d14a>] ttm_bo_validate+0x9a/0x110 [ttm] [<ffffffffa006d4be>] ttm_bo_init+0x2fe/0x3c0 [ttm] [<ffffffffa009b861>] radeon_bo_create+0x181/0x200 [radeon] [<ffffffffa009b530>] ? radeon_bo_clear_va+0x60/0x60 [radeon] [<ffffffffa00ae046>] radeon_gem_object_create+0xa6/0x180 [radeon] [<ffffffffa00ae4bb>] radeon_gem_create_ioctl+0x6b/0x120 [radeon] [<ffffffffa0015499>] drm_ioctl+0x549/0x680 [drm] [<ffffffffa00ae450>] ? radeon_gem_pwrite_ioctl+0x30/0x30 [radeon] [<ffffffff81078713>] ? __wake_up+0x53/0x70 [<ffffffff811c1beb>] ? fsnotify+0x24b/0x340 [<ffffffff81195107>] do_vfs_ioctl+0x97/0x580 [<ffffffff8127b8ca>] ? inode_has_perm.isra.32.constprop.62+0x2a/0x30 [<ffffffff8127cc77>] ? file_has_perm+0x97/0xb0 [<ffffffff81195681>] SyS_ioctl+0x91/0xb0 [<ffffffff81183e02>] ? SyS_write+0x52/0xa0 [<ffffffff8161f1c2>] system_call_fastpath+0x16/0x1b ---[ end trace 9dba5d10af0bf040 ]--- [drm:radeon_ttm_backend_bind] *ERROR* failed to bind 2250 pages at 0x00000000 [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (9216000, 2, 4096, -22) FWIW - git describe has apparently mis-labeled the kernel, its not really v3.10-rc5+ but rather v3.11-rc1-minus Ive git bisected it down to: (note the SHA match w kernel's -gXXX) commit dc50ba7f9a6d9a920409892c7f30bce266067345 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Wed Jun 26 00:33:35 2013 -0400 drm/radeon/kms: add dpm support for evergreen (v4) This adds dpm support for evergreen asics. This includes: - clockgating - dynamic engine clock scaling - dynamic memory clock scaling - dynamic voltage scaling - dynamic pcie gen1/gen2 switching (requires additional acpi support) Set radeon.dpm=1 to enable. v2: reduce stack usage, rename ulv struct v3: fix thermal interrupt check notices by Jerome v4: fix state enable Signed-off-by: Alex Deucher <alexander.deucher(a)amd.com> The previous commit boots fine: commit 66229b200598a3b66b839d1759ff3f5b17ac5639 Author: Alex Deucher <alexander.deucher(a)amd.com> Date: Wed Jun 26 00:11:19 2013 -0400 drm/radeon/kms: add dpm support for rv7xx (v4) dmesg for that kernel looked to have info thats pertinent to whats been done in Alex's patchset at this commit, so heres the relevant parts. [jimc@groucho bootlogs]$ grep -Ei 'radeon|drm' dmesg-3.10.0-rc5-x2-00130-g66229b2 [ 1.730634] [drm] Initialized drm 1.1.0 20060810 [ 1.752826] dynamic_debug:ddebug_add_module: 1 debug prints in module radeon [ 1.754453] [drm] radeon kernel modesetting enabled. [ 1.754752] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68E1 0x1787:0x3000). [ 1.754789] [drm] register mmio base: 0xFE9E0000 [ 1.754790] [drm] register mmio size: 131072 [ 1.755653] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) [ 1.755655] radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF [ 1.756022] [drm] Detected VRAM RAM=1024M, BAR=256M [ 1.756027] [drm] RAM width 64bits DDR [ 1.756139] [drm] radeon: 1024M of VRAM memory ready [ 1.756140] [drm] radeon: 512M of GTT memory ready. [ 1.756212] radeon 0000:01:00.0: radeon_uvd: Can't load firmware "radeon/CYPRESS_uvd.bin" [ 1.756271] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 1.757275] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 1.757328] [drm] Loading CEDAR Microcode [ 1.781141] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 1.781252] radeon 0000:01:00.0: WB enabled [ 1.781255] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88021ffa4c00 [ 1.781257] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88021ffa4c0c [ 1.781260] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 1.781260] [drm] Driver supports precise vblank timestamp query. [ 1.781281] radeon 0000:01:00.0: irq 42 for MSI/MSI-X [ 1.781293] radeon 0000:01:00.0: radeon: using MSI. [ 1.781316] [drm] radeon: irq initialized. [ 1.797570] [drm] ring test on 0 succeeded in 1 usecs [ 1.797628] [drm] ring test on 3 succeeded in 1 usecs [ 1.797753] [drm] ib test on ring 0 succeeded in 0 usecs [ 1.797776] [drm] ib test on ring 3 succeeded in 0 usecs [ 1.797977] [drm] Radeon Display Connectors [ 1.797978] [drm] Connector 0: [ 1.797979] [drm] HDMI-A-1 [ 1.797980] [drm] HPD2 [ 1.797982] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c [ 1.797983] [drm] Encoders: [ 1.797984] [drm] DFP1: INTERNAL_UNIPHY1 [ 1.797985] [drm] Connector 1: [ 1.797986] [drm] DVI-D-1 [ 1.797986] [drm] HPD4 [ 1.797988] [drm] DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 0x644c 0x644c [ 1.797988] [drm] Encoders: [ 1.797989] [drm] DFP2: INTERNAL_UNIPHY [ 1.797990] [drm] Connector 2: [ 1.797991] [drm] VGA-1 [ 1.797992] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [ 1.797993] [drm] Encoders: [ 1.797994] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 1.798039] [drm] Internal thermal controller with fan control [ 1.798069] [drm] radeon: power management initialized [ 1.895209] [drm] fb mappable at 0xD0142000 [ 1.895210] [drm] vram apper at 0xD0000000 [ 1.895211] [drm] size 9216000 [ 1.895212] [drm] fb depth is 24 [ 1.895213] [drm] pitch is 7680 [ 1.895331] fbcon: radeondrmfb (fb0) is primary device [ 2.120738] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device [ 2.120740] radeon 0000:01:00.0: registered panic notifier [ 2.120746] [drm] Initialized radeon 2.34.0 20080528 for 0000:01:00.0 on minor 0 [jimc@groucho bootlogs]$ So thats what I got right now. I hope to try a few things myself soon, but I'll test a patch promptly. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 67825] New: Screen corruption/lockups on Northern Islands (BARTS) with dpm active
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67825 Priority: medium Bug ID: 67825 Assignee: dri-devel(a)lists.freedesktop.org Summary: Screen corruption/lockups on Northern Islands (BARTS) with dpm active Severity: normal Classification: Unclassified OS: Linux (All) Reporter: Alexander(a)Schwarz-Regensburg.de Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 83713 --> https://bugs.freedesktop.org/attachment.cgi?id=83713&action=edit Greps from dmesg for "drm" and "radeon" I'm receiving massive screen corruptions on my Radeon HD 6870 when I use dpm on an rc1/2/3/4 kernel with the following symptoms: There's flickering all over the screen, artifacts and after trying to open anything related to graphics (glxgears, animated menus in KDE, etc...) the machine freezes and can only be revived with a hard reset. Sometimes the machine doesn't even get so far and freezes immediately before. This is accompanied by a black screen or blue lines on the screen. The huge issue is: there's absolutely no error in dmesg and dpm is also automatically set in power_method I'm including grep'd dmesg's for "drm" and "radeon" anyways, to illustrate that everything seems to load fine. More information about the card and my system: XFX Radeon HD 6870 Black Edition with stock bios on an Arch Linux 64 bit system. I'm using the newest mesa-git, libdrm, xf86-video-ati-git and ati-dri-git. It's nearly impossible to gather more information than dmesg, because the system is extremely unstable when using dpm. When I'm NOT setting radeon.dpm=1 the system boots fine, has 3D acceleration and I've not a single issue with my graphics stack. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 67790] New: error message on suspend: *ERROR* Could not force DPM to low
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67790 Priority: medium Bug ID: 67790 Assignee: dri-devel(a)lists.freedesktop.org Summary: error message on suspend: *ERROR* Could not force DPM to low Severity: normal Classification: Unclassified OS: All Reporter: johannes.hirte(a)fem.tu-ilmenau.de Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI On suspend dmesg shows the following error message: [ 236.137036] PM: Syncing filesystems ... done. [ 236.673588] Freezing user space processes ... (elapsed 0.007 seconds) done. [ 236.680901] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. [ 236.681975] Suspending console(s) (use no_console_suspend to debug) [ 236.693223] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 236.695019] sd 0:0:0:0: [sda] Stopping disk [ 237.336598] [drm:rv770_stop_dpm] *ERROR* Could not force DPM to low. [ 239.009616] radeon 0000:01:00.0: power state changed by ACPI to D3cold [ 239.009696] PM: suspend of devices complete after 2315.934 msecs [ 239.009861] PM: late suspend of devices complete after 0.162 msecs I've not seen any problems, suspend and resume worked correct so far. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 67722] New: RV620 GPU kept resetting with radeon.dpm=1 ([drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67722 Priority: medium Bug ID: 67722 Assignee: dri-devel(a)lists.freedesktop.org Summary: RV620 GPU kept resetting with radeon.dpm=1 ([drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: daisuke14164(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 83593 --> https://bugs.freedesktop.org/attachment.cgi?id=83593&action=edit dmesg Graphics: ATI RV620/M82 [Mobility Radeon HD 3450/3470] Kernel: latest git build of drm-fixes-3.11 Mesa: latest git build OS: Arch ARCH: x86_64 DE: KDE 4.11 RC https://bugs.freedesktop.org/show_bug.cgi?id=66963 was fixed but here comes new problem. When booting into X(KDE splash screen), it seemed to freeze(even after a cold reset), but I managed to switch to tty and get the dmesg. Xorg log is fine. In the end I have to shutdown. This situation seems to be more often than normal booting. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 67359] New: No direct rendering with Radeon HD 7750
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67359 Priority: medium Bug ID: 67359 Assignee: dri-devel(a)lists.freedesktop.org Summary: No direct rendering with Radeon HD 7750 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: 74.schutt(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 83043 --> https://bugs.freedesktop.org/attachment.cgi?id=83043&action=edit Xorg.0.log for no direct rendering I've got a Radeon HD 7750: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cape Verde PRO [Radeon HD 7750] and I'm not getting direct rendering: # grep rendering /var/log/Xorg.0.log [ 33.034] (WW) RADEON(0): Direct rendering disabled # glxinfo | grep string server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.1, 256 bits) OpenGL version string: 2.1 Mesa 9.1.4 OpenGL shading language version string: 1.20 # ls -l /dev/dri/* crw-rw----+ 1 root video 226, 0 Jul 26 07:41 /dev/dri/card0 crw-rw---- 1 root video 226, 64 Jul 26 07:41 /dev/dri/controlD64 and my username is in the video group: # grep video /etc/group video:x:27:root,jim I'm running Gentoo with a kernel.org kernel: 3.11.0-rc2-00185-g07bc9dc My system is built on an Asus PC8WS motherboard with UEFI BIOS. It's all new, and I've never had working direct rendering on this system. I build my kernel with the Radeon driver built in, and firmware included: # egrep "RADEON|EXTRA" .config CONFIG_EXTRA_FIRMWARE="radeon/VERDE_ce.bin radeon/VERDE_mc.bin radeon/VERDE_me.bin radeon/VERDE_pfp.bin radeon/VERDE_rlc.bin radeon/VERDE_smc.bin radeon/TAHITI_uvd.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" CONFIG_DRM_RADEON=y # CONFIG_DRM_RADEON_UMS is not set # CONFIG_FB_RADEON is not set AFAIK the firmware is the most recent available: # sha1sum /lib/firmware/radeon/{VERDE,TAHITI_uvd}* 9cda1adf01acdbf7de9171524828603b74edfcd6 /lib/firmware/radeon/VERDE_ce.bin b7993a2036b59a1b5bf6b5433d614f5c97596487 /lib/firmware/radeon/VERDE_mc.bin 29caf82d03f6bc6299777e23c028ec76dad51a71 /lib/firmware/radeon/VERDE_me.bin 3ccb727b909b4e6496cb48fda1e888671bfde19a /lib/firmware/radeon/VERDE_pfp.bin 8ba612da9ffedc0df18ed3593a2e65cb76f058f3 /lib/firmware/radeon/VERDE_rlc.bin 56ac1628276545c4ff1cd682461e4609547d79f4 /lib/firmware/radeon/VERDE_smc.bin 28c406a7dc5d3a223b79e5e76c35d7bb845071e3 /lib/firmware/radeon/TAHITI_uvd.bin Here's the main Gentoo X package versions I'm running: media-libs/mesa-9.1.4 x11-base/xorg-drivers-1.13 x11-base/xorg-server-1.13.4 x11-base/xorg-x11-7.4-r2 I've attached an X server log, and here's everything from dmesg that appears to be related to graphics: [ 0.000000] Command line: BOOT_IMAGE=(hd1,gpt1)/efi/linux/vmlinuz-3.11.0-rc2-00185-g07bc9dc root=LABEL=sys_root ro acpi_enforce_resources=lax radeon.dpm=1 [ 0.000000] Kernel command line: BOOT_IMAGE=(hd1,gpt1)/efi/linux/vmlinuz-3.11.0-rc2-00185-g07bc9dc root=LABEL=sys_root ro acpi_enforce_resources=lax radeon.dpm=1 [ 0.322036] efifb: probing for efifb [ 0.322127] efifb: framebuffer at 0xe0000000, mapped to 0xffffc9000ad00000, using 1984k, total 1984k [ 0.322129] efifb: mode is 800x600x32, linelength=3328, pages=1 [ 0.322131] efifb: scrolling: redraw [ 0.322133] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.324356] fb0: EFI VGA frame buffer device [ 0.364525] [drm] Initialized drm 1.1.0 20060810 [ 0.365086] [drm] radeon kernel modesetting enabled. [ 0.365636] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver [ 0.366329] [drm] initializing kernel modesetting (VERDE 0x1002:0x683F 0x1787:0x200B). [ 0.366909] [drm] register mmio base: 0xF7E00000 [ 0.367456] [drm] register mmio size: 262144 [ 0.368707] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used) [ 0.369287] radeon 0000:01:00.0: GTT: 512M 0x0000000040000000 - 0x000000005FFFFFFF [ 0.369865] [drm] Detected VRAM RAM=1024M, BAR=256M [ 0.370434] [drm] RAM width 128bits DDR [ 0.371017] [TTM] Zone kernel: Available graphics memory: 8209962 kiB [ 0.371579] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 0.372135] [TTM] Initializing pool allocator [ 0.372687] [TTM] Initializing DMA pool allocator [ 0.373243] [drm] radeon: 1024M of VRAM memory ready [ 0.373782] [drm] radeon: 512M of GTT memory ready. [ 0.374830] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 0.375584] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e [ 0.376105] [drm] PCIE gen 3 link speeds already enabled [ 0.376635] [drm] Loading VERDE Microcode [ 0.692398] [drm] PCIE GART of 512M enabled (table at 0x0000000000276000). [ 0.693008] radeon 0000:01:00.0: WB enabled [ 0.693520] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88040df85c00 [ 0.694569] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff88040df85c04 [ 0.695675] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff88040df85c08 [ 0.696817] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88040df85c0c [ 0.697977] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff88040df85c10 [ 0.699201] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc9000b035a18 [ 0.700458] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 0.701095] [drm] Driver supports precise vblank timestamp query. [ 0.701749] radeon 0000:01:00.0: irq 40 for MSI/MSI-X [ 0.701756] radeon 0000:01:00.0: radeon: using MSI. [ 0.702420] [drm] radeon: irq initialized. [ 0.722205] [drm] ring test on 0 succeeded in 2 usecs [ 0.722843] [drm] ring test on 1 succeeded in 1 usecs [ 0.723458] [drm] ring test on 2 succeeded in 1 usecs [ 0.724127] [drm] ring test on 3 succeeded in 4 usecs [ 0.724731] [drm] ring test on 4 succeeded in 4 usecs [ 1.901452] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 2.922147] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 3.943124] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 4.964083] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 5.984845] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 7.005588] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 8.026315] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 9.047036] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 10.067738] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 11.088419] [drm:r600_uvd_init] *ERROR* UVD not responding, trying to reset the VCPU!!! [ 11.109017] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!! [ 11.109588] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1). [ 11.110974] [drm] ib test on ring 0 succeeded in 0 usecs [ 11.111448] [drm] ib test on ring 1 succeeded in 0 usecs [ 11.111895] [drm] ib test on ring 2 succeeded in 0 usecs [ 11.112319] [drm] ib test on ring 3 succeeded in 0 usecs [ 11.112720] [drm] ib test on ring 4 succeeded in 1 usecs [ 11.113577] [drm] Radeon Display Connectors [ 11.113901] [drm] Connector 0: [ 11.114201] [drm] DP-1 [ 11.114476] [drm] HPD4 [ 11.114737] [drm] DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c [ 11.115013] [drm] Encoders: [ 11.115276] [drm] DFP1: INTERNAL_UNIPHY2 [ 11.115540] [drm] Connector 1: [ 11.115796] [drm] HDMI-A-1 [ 11.116053] [drm] HPD1 [ 11.116311] [drm] DDC: 0x6570 0x6570 0x6574 0x6574 0x6578 0x6578 0x657c 0x657c [ 11.116601] [drm] Encoders: [ 11.116890] [drm] DFP2: INTERNAL_UNIPHY2 [ 11.117173] [drm] Connector 2: [ 11.117438] [drm] DVI-I-1 [ 11.117706] [drm] HPD2 [ 11.117973] [drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c [ 11.118272] [drm] Encoders: [ 11.118573] [drm] DFP3: INTERNAL_UNIPHY [ 11.118882] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 11.119229] [drm] Internal thermal controller with fan control [ 11.119604] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e [ 11.119965] == power state 0 == [ 11.120314] ui class: none [ 11.120663] internal class: boot [ 11.121003] caps: [ 11.121326] uvd vclk: 0 dclk: 0 [ 11.121645] power level 0 sclk: 30000 mclk: 14900 vddc: 950 vddci: 900 pcie gen: 3 [ 11.121995] status: c r b [ 11.122353] == power state 1 == [ 11.122710] ui class: performance [ 11.123075] internal class: none [ 11.123435] caps: [ 11.123789] uvd vclk: 0 dclk: 0 [ 11.124147] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.124539] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.124925] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.125303] status: [ 11.125678] == power state 2 == [ 11.126051] ui class: none [ 11.126427] internal class: uvd [ 11.126811] caps: video [ 11.127179] uvd vclk: 72000 dclk: 56000 [ 11.127544] power level 0 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.127933] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.128315] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.128704] status: [ 11.129092] == power state 3 == [ 11.129470] ui class: none [ 11.129839] internal class: ulv [ 11.130208] caps: [ 11.130574] uvd vclk: 0 dclk: 0 [ 11.130934] power level 0 sclk: 30000 mclk: 15000 vddc: 800 vddci: 900 pcie gen: 3 [ 11.131314] power level 1 sclk: 30000 mclk: 15000 vddc: 800 vddci: 900 pcie gen: 3 [ 11.131680] power level 2 sclk: 30000 mclk: 15000 vddc: 800 vddci: 900 pcie gen: 3 [ 11.132040] status: [ 11.136916] switching from power state: [ 11.137280] ui class: none [ 11.137644] internal class: boot [ 11.137998] caps: [ 11.138332] uvd vclk: 0 dclk: 0 [ 11.138671] power level 0 sclk: 30000 mclk: 14900 vddc: 950 vddci: 900 pcie gen: 3 [ 11.139037] status: c b [ 11.139402] switching to power state: [ 11.139768] ui class: performance [ 11.140137] internal class: none [ 11.140494] caps: [ 11.140840] uvd vclk: 0 dclk: 0 [ 11.141184] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.141543] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.141909] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.142278] status: r [ 11.143477] [drm] radeon: dpm initialized [ 11.180331] [drm] fb mappable at 0xE1388000 [ 11.180709] [drm] vram apper at 0xE0000000 [ 11.181071] [drm] size 9216000 [ 11.181435] [drm] fb depth is 24 [ 11.181796] [drm] pitch is 7680 [ 11.182142] fb: conflicting fb hw usage radeondrmfb vs EFI VGA - removing generic driver [ 11.182567] fbcon: radeondrmfb (fb1) is primary device [ 11.182604] switching from power state: [ 11.182605] ui class: performance [ 11.182605] internal class: none [ 11.182606] caps: [ 11.182606] uvd vclk: 0 dclk: 0 [ 11.182607] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.182608] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.182608] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.182609] status: c r [ 11.182609] switching to power state: [ 11.182609] ui class: performance [ 11.182610] internal class: none [ 11.182610] caps: [ 11.182610] uvd vclk: 0 dclk: 0 [ 11.182611] power level 0 sclk: 30000 mclk: 15000 vddc: 825 vddci: 900 pcie gen: 3 [ 11.182612] power level 1 sclk: 40000 mclk: 112500 vddc: 950 vddci: 950 pcie gen: 3 [ 11.182612] power level 2 sclk: 80000 mclk: 112500 vddc: 1100 vddci: 950 pcie gen: 3 [ 11.182613] status: c r [ 11.841979] radeon 0000:01:00.0: fb1: radeondrmfb frame buffer device [ 11.842679] radeon 0000:01:00.0: registered panic notifier [ 11.843386] [drm] Initialized radeon 2.34.0 20080528 for 0000:01:00.0 on minor 0 Any ideas about what I might be doing wrong would be greatly appreciated. Please let me know what other information might be needed to work this out. Thanks -- Jim -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 67178] New: discrete radeon HD 6400M/7400M intense heating even though it's "off"
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67178 Priority: medium Bug ID: 67178 Assignee: dri-devel(a)lists.freedesktop.org Summary: discrete radeon HD 6400M/7400M intense heating even though it's "off" Severity: normal Classification: Unclassified OS: Linux (All) Reporter: tpo_deb(a)sourcepole.ch Hardware: x86-64 (AMD64) Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI kernel 3.11-rc1 (also tested with 3.10 from Debian, 3.7, 3,2) # lspci -vnnn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (rev ff) (prog-if ff) This is a HP Pavillon dv7 6130ez Sometimes, at random, the radeon card goes into full heat production mode. This seems to occur a while (a few minutes?) after wakeup from resume, however I'm not sure about that. Suspending and resuming the laptop a few times (1 <= x <= ~4) seems to calm the card down again. Power consumption according to powertop goes from ~14W up to ~50W. This happens even though the card should be in theory switched off. Aka: # cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr:0000:00:02.0 1:DIS: :Off:0000:01:00.0 # echo IGD > /sys/kernel/debug/vgaswitcheroo/switch # echo OFF > /sys/kernel/debug/vgaswitcheroo/switch doesn't seem to have no effect whatsoever. It *seems* that setting "radeon.dpm=1" kernel boot options and then: # echo "battery" > /sys/class/drm/card$no/device/power_dpm_state puts the card in an "active" but "relatively low" power consumption mode. It is then using about 20W (instead of the "normal" ~14W) so it's continuously faning out slightly warm air. And it "seems that when the card is running in this mode, then it won't get so often, or ever (I'm not very sure) into the berserk heating mode. The lowest observed power consumption of the laptop is ~7W. It'd be very nice if it'd be possible to shut the card down electrically via software and stay in this 7W mode. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 67169] New: Black screen after waking from sleep
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=67169 Priority: medium Bug ID: 67169 Assignee: dri-devel(a)lists.freedesktop.org Summary: Black screen after waking from sleep Severity: normal Classification: Unclassified OS: All Reporter: marco(a)scannadinari.co.uk Hardware: Other Status: NEW Version: 9.1 Component: Drivers/DRI/Radeon Product: Mesa Created attachment 82813 --> https://bugs.freedesktop.org/attachment.cgi?id=82813&action=edit xorg log Waking the screen from sleep wakes it but all i get is a black screen. I am able to type and change ttys, etc, but after `systemctl restart gdm` as root the screen gets 'No signal'. The setting that causes this is GNOME's 'Blank screen' option in Settings>Power>Blank Screen I can confirm that AMD's proprietary drivers fix this. -- You are receiving this mail because: You are the assignee for the bug.

1 9

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel October 2013