dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 69497] New: X1950XTX performance issue
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=69497 Priority: medium Bug ID: 69497 Assignee: dri-devel(a)lists.freedesktop.org Summary: X1950XTX performance issue Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI I don't care much because I don't use this card anymore, but since I did some benchmarks I will report it because I know there are still a lot of peoples who use R300g. http://openbenchmarking.org/result/1309172-SO-X1950XTX238 I got 37 fps in openarena with the X1950XTX, while it should be at least 70+ (http://www.phoronix.com/scan.php?page=article&item=amd_r300g_mesa92&num=2) Kernel 3.12 System logs: http://openbenchmarking.org/system/1309172-SO-X1950XTX238/x1950xtx -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 69395] New: [DPM] Forcing lowest power state when no display is attached is bad because of OpenCL
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=69395 Priority: medium Bug ID: 69395 Assignee: dri-devel(a)lists.freedesktop.org Summary: [DPM] Forcing lowest power state when no display is attached is bad because of OpenCL Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Actually I can't use my HD 7950 with KDE becuase of https://bugs.freedesktop.org/show_bug.cgi?id=69341 https://bugs.freedesktop.org/show_bug.cgi?id=64297 so I attached my display the Intel HD 4000. I still do bitcoin mining (OpenCL) on the 7950 and I notice it doesn't switch to higher power states anymore (everything works flawlessly if I attach the display to the 7950). Forcing the card to the lowest power state if no display is attached is a bad behavious because of GPGPU computing. I'm using Linux 3.12-pre (drm-next). -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 69062] New: Corrupted visuals in Gnome3 (A6-4400M)
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=69062 Priority: medium Bug ID: 69062 Assignee: dri-devel(a)lists.freedesktop.org Summary: Corrupted visuals in Gnome3 (A6-4400M) Severity: normal Classification: Unclassified OS: Linux (All) Reporter: lrn1986(a)gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 85385 --> https://bugs.freedesktop.org/attachment.cgi?id=85385&action=edit Corrupted shell On boot gdm3 looks fine (displays a list of users). When i choose a user from the list, the animation plays out - and that's when the corruption starts (missing text and missing graphics). I can still log in by typing the password. Once logged in, gnome shell looks fine at first. Opening the Activities screen might cause minor corruption (for example, hovering over icons on the left panel might show corrupted selection rectangle fadein). Typing in the Activities screen _always_ causes major corruption in visuals. Only Gnome shell (top bar, Activities, window switcher) is affected. Applications continue to be drawn correctly. Gnome shell reset (Alt+F2, r) cleans up corruption from the shell (completely or almost completely), but it quickly returns. Tried changing radeon.gartsize on boot - no difference. No errors on Xorg.log No errors in dmesg This is a regression (things used to work ~half a year ago) Versions: *Gnome3 3.8 Debian sid/experimental *kernel: git://people.freedesktop.org/~airlied/linux 86a7e1224a68511d3a1ae0b7e11581b9d37723ae (also tried older kernels, as far as 3.8rc4 - same thing, this doesn't seem to be kernel-dependent) *drm git://anongit.freedesktop.org/git/mesa/drm d18cd0c7ccf88c9f6585aaa3cc57f0f064d7310b *mesa git://anongit.freedesktop.org/git/mesa/mesa 505fad04f10eee1efdfcd8986b4d484b49d39986 *xorg (radeon driver, xserver, and its dependencies) git latest versions on 06.09.2013 A screenshot is attached. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 68178] New: evergreen: hard lockup on suspend and resume with current firmware
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=68178 Priority: medium Bug ID: 68178 Assignee: dri-devel(a)lists.freedesktop.org Summary: evergreen: hard lockup on suspend and resume with current firmware Severity: major Classification: Unclassified OS: Linux (All) Reporter: nine(a)detonation.org Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 84133 --> https://bugs.freedesktop.org/attachment.cgi?id=84133&action=edit dmesg of my system for information As soon as the up to date firmware package is installed, my system hangs on suspend and again on resume with the screen turned off and the system not reacting to anything. Tested it on various kernels with the earliest being 3.7.10 (current openSUSE kernel) and the latest being 3.11-rc5. I tried to get more information, but there are no logs, the screen is turned off and even netconsole did not show more. Do you have suggestions about how to debug this or things that I can try to narrow it down? My GPU is a: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Redwood [Radeon HD 5670] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device e151 Flags: bus master, fast devsel, latency 0, IRQ 48 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f4420000 (64-bit, non-prefetchable) [size=128K] I/O ports at e000 [size=256] Expansion ROM at f4400000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Kernel driver in use: radeon Attaching dmesg of a running system just for info. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 68059] New: with radeon.dpm=1, Xorg crashed a while after resume
by bugzilla-daemon＠freedesktop.org 19 Nov '19

19 Nov '19

https://bugs.freedesktop.org/show_bug.cgi?id=68059 Priority: medium Bug ID: 68059 Assignee: dri-devel(a)lists.freedesktop.org Summary: with radeon.dpm=1, Xorg crashed a while after resume Severity: critical Classification: Unclassified OS: Linux (All) Reporter: wrxzzj(a)gmail.com Hardware: x86 (IA32) Status: NEW Version: DRI CVS Component: DRM/Radeon Product: DRI Created attachment 84008 --> https://bugs.freedesktop.org/attachment.cgi?id=84008&action=edit dmesg I test with kernel 3.11rc5, mesa 9.2git, xorg 1.14.2, Radeon HD6310. with radeon.dpm enabled, after resume from RAM, Xorg crashed a while. attachment is my dmesg log. -- You are receiving this mail because: You are the assignee for the bug.

1 15

[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

← Newer
1
...
8
9
10
11
12
13
14
...
112
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015