Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca composed on 2021-02-12 15:53 (UTC+0100): > And today, lockup happened with smplayer (with mpv under the hood) so it > is more general issue with X/kernel/hardware. :( I would continue using the DVI port, but with a DVI-to-HDMI adapter, long enough to determine if the problem is exclusive to the HDMI port itself. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca writes: > > Yesterday this lockup happens with monitor connected by DVI. So my > theory that these lockups are related to DVI/HDMI connection became > untrue. And today, lockup happened with smplayer (with mpv under the hood) so it is more general issue with X/kernel/hardware. :( KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Re: AMD GPU + HDMI + vlc = lockup
On Sat, 06 Feb 2021 12:38:30 +0100 Kamil Jońca wrote: > > > > Is your HD 5450 passively cooled? If yes, you might try placing a > > case fan > > Yes. I try to avoid fans, but I think I have no choice. If noise is your objection to fans, have some reviews of quiet equipment: https://silentpcreview.com -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: AMD GPU + HDMI + vlc = lockup
Felix Miata writes: > Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100): > >> Yesterday this lockup happens with monitor connected by DVI. So my >> theory that these lockups are related to DVI/HDMI connection became untrue. >> I will try to investigate further. Again thanks to Felix for his >> efforts so far. > > You never answered one of my last questions: > "Have you tried watching top as you start VLC?" Sorry. I did it now. It is about 90-110 % regardless lockup or not. > > Is your HD 5450 passively cooled? If yes, you might try placing a case fan Yes. I try to avoid fans, but I think I have no choice. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca writes: > Felix Miata writes: > >> Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100): >> >>> Yesterday this lockup happens with monitor connected by DVI. So my >>> theory that these lockups are related to DVI/HDMI connection became untrue. >>> I will try to investigate further. Again thanks to Felix for his >>> efforts so far. >> >> You never answered one of my last questions: >> "Have you tried watching top as you start VLC?" > > Sorry. I did it now. It is about 90-110 % regardless lockup or not. I mean vlc takes ~90-110% CPU. KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca composed on 2021-02-06 09:41 (UTC+0100): > Yesterday this lockup happens with monitor connected by DVI. So my > theory that these lockups are related to DVI/HDMI connection became untrue. > I will try to investigate further. Again thanks to Felix for his > efforts so far. You never answered one of my last questions: "Have you tried watching top as you start VLC?" Is your HD 5450 passively cooled? If yes, you might try placing a case fan somewhere where it can blow on the GPU's heat sink. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca writes: > There is desktop box with sid. > > sudo lspci|grep -i vga > 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Cedar [Radeon HD 5000/6000/7350/8350 Series] > > So far I have monitor connected via DVI > > Recently I connected monitor via hdmi output (instead old one) > And strange things starts happend. > When I tried to play movie with vlc there were hand for few seconds and > then monitor "resets", and there were only black rectanle - have to > reopen movie. > Yesterday this lockup happens with monitor connected by DVI. So my theory that these lockups are related to DVI/HDMI connection became untrue. I will try to investigate further. Again thanks to Felix for his efforts so far. KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Re: AMD GPU + HDMI + vlc = lockup
Felix Miata writes: > Kamil Jońca composed on 2021-02-04 07:14 (UTC+0100): > >> Felix Miata writes: > >>> How quickly after video start does this happen, right away, or only after a >>> while? > >> when I launch vlc with list of movie files. vlc "waits" (and then there >> >> [] > > There what? vlc hangs. And then theres is GPU reset and vlc is functionable again, can play movies. When I turn off vlc and then start it again - story repeats. > > I suppose the hang could be from CPU initializing VLC before the video > actually TBH I doubt, but I'll try. > starts running. Have you tried watching top as you start VLC? How powerful is > your > CPU? cat /proc/cpuinfo|head -n 30 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz stepping: 11 microcode : 0xbc cpu MHz : 2327.594 cache size : 4096 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 4 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca lahf_lm pti tpr_shadow vnmi flexpriority vpid dtherm vmx flags : vnmi flexpriority tsc_offset vtpr vapic bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips: 4655.18 clflush size: 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: ... repeated four times ... > > When I have trouble with VLC, I often find trouble absent using SMplayer. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca composed on 2021-02-04 07:14 (UTC+0100): > Felix Miata writes: >> How quickly after video start does this happen, right away, or only after a >> while? > when I launch vlc with list of movie files. vlc "waits" (and then there > > [] There what? >> Display: x11 server: X.Org 1.20.10 driver: loaded: modesetting > "Display: x11 server: X.Org 1.20.10 driver: loaded: radeon display ID: :0" > but when I changed to "modesetting" I also noticed hangup. > BTW what is difference between the two in terms of performance for > example? I don't know whether the difference is detectable in the absence of benchmarking. > [...] >> OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.3 >> compat-v: 3.1 direct render: Yes > OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-2-amd64 LLVM 11.0.1) > v: 3.3 Mesa 20.3.3 compat-v: 3.1 direct render: Yes > How can I test "llvmpipe" here? AFAIK, llvmpipe is used by the Modesetting DDX, while Radeon DDX uses AMD CEDAR. Whether either could possibly use the other I have no idea, but since the Modesetting uses a very different technology, I suspect it's not possible. >> Info:...Shell: Bash v: 5.1.4 running in: konsole inxi: 3.3.00 >> # dmesg | grep adeon ... >> [ 38.389555] radeon :01:00.0: VRAM: 1024M 0x - >> 0x3FFF (1024M used) >> [ 38.389561] radeon :01:00.0: GTT: 1024M 0x4000 - >> 0x7FFF >> [ 38.389820] [drm] radeon: 1024M of VRAM memory ready >> [ 38.389824] [drm] radeon: 1024M of GTT memory ready. ... > similar but only 512M vram. I suppose the hang could be from CPU initializing VLC before the video actually starts running. Have you tried watching top as you start VLC? How powerful is your CPU? When I have trouble with VLC, I often find trouble absent using SMplayer. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: AMD GPU + HDMI + vlc = lockup
[ I replied yesterday, but I cannot see this on list ] Felix Miata writes: > Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100): > ... >> kjonca@alfa:~%uname -a >> Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64 >> GNU/Linux >> kjonca@alfa:~%cat /etc/debian_version >> bullseye/sid > >> This is sid upgraded ~ weekly. > > How quickly after video start does this happen, right away, or only after a > while? when I launch vlc with list of movie files. vlc "waits" (and then there [] > Graphics: > Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] > vendor: PC Partner Limited driver: radeon v: kernel bus ID: 01:00.0 > chip ID: 1002:68f9 class ID: 0300 > Display: x11 server: X.Org 1.20.10 driver: loaded: modesetting "Display: x11 server: X.Org 1.20.10 driver: loaded: radeon display ID: :0" but when I changed to "modesetting" I also noticed hangup. BTW what is difference between the two in terms of performance for example? [...] > OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.3 > compat-v: 3.1 direct render: Yes OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-2-amd64 LLVM 11.0.1) v: 3.3 Mesa 20.3.3 compat-v: 3.1 direct render: Yes How can I test "llvmpipe" here? > Info:...Shell: Bash v: 5.1.4 running in: konsole inxi: 3.3.00 > # dmesg | grep adeon > [ 38.052237] [drm] radeon kernel modesetting enabled. > [ 38.387770] fb0: switching to radeondrmfb from VESA VGA > [ 38.388095] radeon :01:00.0: vgaarb: deactivate vga console > [ 38.389555] radeon :01:00.0: VRAM: 1024M 0x - > 0x3FFF (1024M used) > [ 38.389561] radeon :01:00.0: GTT: 1024M 0x4000 - > 0x7FFF > [ 38.389820] [drm] radeon: 1024M of VRAM memory ready > [ 38.389824] [drm] radeon: 1024M of GTT memory ready. > [ 38.926339] radeon :01:00.0: firmware: direct-loading firmware > radeon/CEDAR_pfp.bin > [ 39.013160] radeon :01:00.0: firmware: direct-loading firmware > radeon/CEDAR_me.bin > [ 39.07] radeon :01:00.0: firmware: direct-loading firmware > radeon/CEDAR_rlc.bin > [ 39.526315] radeon :01:00.0: firmware: direct-loading firmware > radeon/CEDAR_smc.bin > [ 39.554674] [drm] radeon: dpm initialized > [ 39.774437] radeon :01:00.0: firmware: direct-loading firmware > radeon/CYPRESS_uvd.bin > [ 39.778359] [drm] enabling PCIE gen 2 link speeds, disable with > radeon.pcie_gen2=0 > [ 39.794951] radeon :01:00.0: WB enabled > [ 39.794958] radeon :01:00.0: fence driver on ring 0 use gpu addr > 0x4c00 > [ 39.794963] radeon :01:00.0: fence driver on ring 3 use gpu addr > 0x4c0c > [ 39.795338] radeon :01:00.0: fence driver on ring 5 use gpu addr > 0x0005c418 > [ 39.795763] radeon :01:00.0: radeon: MSI limited to 32-bit > [ 39.795872] radeon :01:00.0: radeon: using MSI. > [ 39.795914] [drm] radeon: irq initialized. > [ 40.686752] [drm] Radeon Display Connectors > [ 40.794401] fbcon: radeondrmfb (fb0) is primary device > [ 40.894386] radeon :01:00.0: [drm] fb0: radeondrmfb frame buffer device > [ 40.917823] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on > minor 0 similar but only 512M vram. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Re: AMD GPU + HDMI + vlc = lockup
Felix Miata writes: > Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100): > ... >> kjonca@alfa:~%uname -a >> Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64 >> GNU/Linux >> kjonca@alfa:~%cat /etc/debian_version >> bullseye/sid > >> This is sid upgraded ~ weekly. > > How quickly after video start does this happen, right away, or only after a > while? Directly after starting, vlc "hangs" for a while, and then this strange things happening. > > I tried with Bullseye, and it seems OK still after playing 20+ minutes out of > 58 > of satellite source recording of CBS' main high bitrate MPEG-4 stream, with > VLC > on the VGA 1680x1050 in fullscreen mode. Switching to the HDMI 1920x1200 it's > still > working, with top showing vlc around 320% CPU: [... snip ] Thank you for comprehensive test. I will try to debug it deeper. KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca writes: > Felix Miata writes: > >> Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100): >> ... >>> kjonca@alfa:~%uname -a >>> Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64 >>> GNU/Linux >>> kjonca@alfa:~%cat /etc/debian_version >>> bullseye/sid >> >>> This is sid upgraded ~ weekly. >> >> How quickly after video start does this happen, right away, or only after a >> while? > > Directly after starting, vlc "hangs" for a while, and then this strange things > happening. An then works without problems. Till next run. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca composed on 2021-02-02 21:37 (UTC+0100): ... > kjonca@alfa:~%uname -a > Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64 GNU/Linux > kjonca@alfa:~%cat /etc/debian_version > bullseye/sid > This is sid upgraded ~ weekly. How quickly after video start does this happen, right away, or only after a while? I tried with Bullseye, and it seems OK still after playing 20+ minutes out of 58 of satellite source recording of CBS' main high bitrate MPEG-4 stream, with VLC on the VGA 1680x1050 in fullscreen mode. Switching to the HDMI 1920x1200 it's still working, with top showing vlc around 320% CPU: # inxi -C CPU: Info: Quad Core model: AMD Phenom II X4 965 bits: 64 type: MCP L2 cache: 2 MiB Speed: 3400 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 3400 2: 3400 3: 3400 4: 3400 # inxi -GISay System: Host: ga970 Kernel: 5.10.0-2-amd64 x86_64 bits: 64... Desktop: Trinity R14.0.10 tk: Qt 3.5.0 info: kicker wm: Twin 3.0 dm: TDM Distro: Debian GNU/Linux bullseye/sid Graphics: Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: PC Partner Limited driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9 class ID: 0300 Display: x11 server: X.Org 1.20.10 driver: loaded: modesetting display ID: :0 screens: 1 Screen-1: 0 s-res: 3600x1200 s-dpi: 108 s-size: 846x282mm (33.3x11.1") s-diag: 892mm (35.1") Monitor-1: HDMI-1 res: 1920x1200 hz: 60 dpi: 94 size: 519x324mm (20.4x12.8") diag: 612mm (24.1") Monitor-2: VGA-1 res: 1680x1050 hz: 60 dpi: 90 size: 474x296mm (18.7x11.7") diag: 559mm (22") OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.3 compat-v: 3.1 direct render: Yes Info:...Shell: Bash v: 5.1.4 running in: konsole inxi: 3.3.00 # dmesg | grep adeon [ 38.052237] [drm] radeon kernel modesetting enabled. [ 38.387770] fb0: switching to radeondrmfb from VESA VGA [ 38.388095] radeon :01:00.0: vgaarb: deactivate vga console [ 38.389555] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [ 38.389561] radeon :01:00.0: GTT: 1024M 0x4000 - 0x7FFF [ 38.389820] [drm] radeon: 1024M of VRAM memory ready [ 38.389824] [drm] radeon: 1024M of GTT memory ready. [ 38.926339] radeon :01:00.0: firmware: direct-loading firmware radeon/CEDAR_pfp.bin [ 39.013160] radeon :01:00.0: firmware: direct-loading firmware radeon/CEDAR_me.bin [ 39.07] radeon :01:00.0: firmware: direct-loading firmware radeon/CEDAR_rlc.bin [ 39.526315] radeon :01:00.0: firmware: direct-loading firmware radeon/CEDAR_smc.bin [ 39.554674] [drm] radeon: dpm initialized [ 39.774437] radeon :01:00.0: firmware: direct-loading firmware radeon/CYPRESS_uvd.bin [ 39.778359] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 39.794951] radeon :01:00.0: WB enabled [ 39.794958] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 [ 39.794963] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c [ 39.795338] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0005c418 [ 39.795763] radeon :01:00.0: radeon: MSI limited to 32-bit [ 39.795872] radeon :01:00.0: radeon: using MSI. [ 39.795914] [drm] radeon: irq initialized. [ 40.686752] [drm] Radeon Display Connectors [ 40.794401] fbcon: radeondrmfb (fb0) is primary device [ 40.894386] radeon :01:00.0: [drm] fb0: radeondrmfb frame buffer device [ 40.917823] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on minor 0 -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: AMD GPU + HDMI + vlc = lockup
Felix Miata writes: > Kamil Jońca composed on 2021-01-28 17:58 (UTC+0100): > >> When I back to DVI monitor everthing work without errors. > > Did you find a solution? No. I back to my old DVI monitor. :( > > Which Debian? I too have a PC with HD 5450 Radeon. I could try to reproduce if > knowing what to boot is what I have installed. kjonca@alfa:~%uname -a Linux alfa 5.10.0-2-amd64 #1 SMP Debian 5.10.9-1 (2021-01-20) x86_64 GNU/Linux kjonca@alfa:~%cat /etc/debian_version bullseye/sid This is sid upgraded ~ weekly. KJ -- http://wolnelektury.pl/wesprzyj/teraz/
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jońca composed on 2021-01-28 17:58 (UTC+0100): > When I back to DVI monitor everthing work without errors. Did you find a solution? Which Debian? I too have a PC with HD 5450 Radeon. I could try to reproduce if knowing what to boot is what I have installed. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: AMD GPU + HDMI + vlc = lockup
Dan Ritter writes: > Kamil Jo?ca wrote: >> >> There is desktop box with sid. >> >> sudo lspci|grep -i vga >> 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] >> Cedar [Radeon HD 5000/6000/7350/8350 Series] >> >> So far I have monitor connected via DVI >> >> Recently I connected monitor via hdmi output (instead old one) >> And strange things starts happend. >> When I tried to play movie with vlc there were hand for few seconds and >> then monitor "resets", and there were only black rectanle - have to >> reopen movie. > > ... > >> this is quite reproductible. Can I make anything about it? >> When I back to DVI monitor everthing work without errors. > > Is it on every movie or just this one? Sorry, I think I described it wrongly. It is rather connected to start vlc not to play movie as such. IE. if I have some movies on playlist then after start vlc I got GPU hangup (as described) and then I can play any movie from the list without problems. Moreover mplayer also plays these movies without any troubles and hangups. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Re: AMD GPU + HDMI + vlc = lockup
Kamil Jo?ca wrote: > > There is desktop box with sid. > > sudo lspci|grep -i vga > 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] > Cedar [Radeon HD 5000/6000/7350/8350 Series] > > So far I have monitor connected via DVI > > Recently I connected monitor via hdmi output (instead old one) > And strange things starts happend. > When I tried to play movie with vlc there were hand for few seconds and > then monitor "resets", and there were only black rectanle - have to > reopen movie. ... > this is quite reproductible. Can I make anything about it? > When I back to DVI monitor everthing work without errors. Is it on every movie or just this one? I have seen several video files where VLC will lock up for 30+ seconds, then can continue. I don't know what causes it. -dsr-
AMD GPU + HDMI + vlc = lockup
There is desktop box with sid. sudo lspci|grep -i vga 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] So far I have monitor connected via DVI Recently I connected monitor via hdmi output (instead old one) And strange things starts happend. When I tried to play movie with vlc there were hand for few seconds and then monitor "resets", and there were only black rectanle - have to reopen movie. In logs I got something like: alfa kernel: [114324.608912] [drm:cypress_dpm_set_power_state [radeon]] *ERROR* rv770_restrict_performance_levels_before_switch failed alfa kernel: [114335.021950] radeon :08:00.0: ring 5 stalled for more than 10252msec alfa kernel: [114335.021959] radeon :08:00.0: GPU lockup (current fence id 0x0002112c last fence id 0x00021130 on ring 5) alfa kernel: [114335.533922] radeon :08:00.0: ring 5 stalled for more than 10764msec alfa kernel: [114335.533931] radeon :08:00.0: GPU lockup (current fence id 0x0002112c last fence id 0x00021130 on ring 5) alfa kernel: [114336.047455] radeon :08:00.0: couldn't schedule ib alfa kernel: [114336.047519] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! alfa kernel: [114336.047581] radeon :08:00.0: couldn't schedule ib alfa kernel: [114336.047606] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)! alfa kernel: [114336.048724] radeon :08:00.0: Saved 23 dwords of commands on ring 0. alfa kernel: [114336.048738] radeon :08:00.0: GPU softreset: 0x0019 alfa kernel: [114336.048741] radeon :08:00.0: GRBM_STATUS = 0xE0001CA0 alfa kernel: [114336.048744] radeon :08:00.0: GRBM_STATUS_SE0 = 0x8003 alfa kernel: [114336.048747] radeon :08:00.0: GRBM_STATUS_SE1 = 0x0007 alfa kernel: [114336.048749] radeon :08:00.0: SRBM_STATUS = 0x200800C0 alfa kernel: [114336.048752] radeon :08:00.0: SRBM_STATUS2 = 0x alfa kernel: [114336.048755] radeon :08:00.0: R_008674_CP_STALLED_STAT1 = 0x0100 alfa kernel: [114336.048758] radeon :08:00.0: R_008678_CP_STALLED_STAT2 = 0x00011000 alfa kernel: [114336.048760] radeon :08:00.0: R_00867C_CP_BUSY_STAT = 0x00068404 alfa kernel: [114336.048763] radeon :08:00.0: R_008680_CP_STAT = 0x80878647 alfa kernel: [114336.048766] radeon :08:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 alfa kernel: [114336.062121] radeon :08:00.0: GRBM_SOFT_RESET=0x7F6B alfa kernel: [114336.062283] radeon :08:00.0: SRBM_SOFT_RESET=0x0100 alfa kernel: [114336.063441] radeon :08:00.0: GRBM_STATUS = 0x3828 alfa kernel: [114336.063445] radeon :08:00.0: GRBM_STATUS_SE0 = 0x0007 alfa kernel: [114336.063447] radeon :08:00.0: GRBM_STATUS_SE1 = 0x0007 alfa kernel: [114336.063450] radeon :08:00.0: SRBM_STATUS = 0x200800C0 alfa kernel: [114336.063453] radeon :08:00.0: SRBM_STATUS2 = 0x alfa kernel: [114336.063456] radeon :08:00.0: R_008674_CP_STALLED_STAT1 = 0x alfa kernel: [114336.063458] radeon :08:00.0: R_008678_CP_STALLED_STAT2 = 0x alfa kernel: [114336.063461] radeon :08:00.0: R_00867C_CP_BUSY_STAT = 0x alfa kernel: [114336.063463] radeon :08:00.0: R_008680_CP_STAT = 0x alfa kernel: [114336.063466] radeon :08:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 alfa kernel: [114336.063479] radeon :08:00.0: GPU reset succeeded, trying to resume alfa kernel: [114336.088752] [drm] PCIE GART of 1024M enabled (table at 0x0014C000). alfa kernel: [114336.05] radeon :08:00.0: WB enabled alfa kernel: [114336.088890] radeon :08:00.0: fence driver on ring 0 use gpu addr 0x2c00 alfa kernel: [114336.088893] radeon :08:00.0: fence driver on ring 3 use gpu addr 0x2c0c alfa kernel: [114336.089607] radeon :08:00.0: fence driver on ring 5 use gpu addr 0x0005c418 alfa kernel: [114336.106128] [drm] ring test on 0 succeeded in 1 usecs alfa kernel: [114336.106140] [drm] ring test on 3 succeeded in 2 usecs alfa kernel: [114336.282680] [drm] ring test on 5 succeeded in 1 usecs alfa kernel: [114336.282694] [drm] UVD initialized successfully. alfa kernel: [114336.325529] [drm] ib test on ring 0 succeeded in 0 usecs alfa kernel: [114336.325592] [drm] ib test on ring 3 succeeded in 0 usecs alfa kernel: [114337.073849] [drm] ib test on ring 5 succeeded this is quite reproductible. Can I make anything about it? When I back to DVI monitor everthing work without errors. KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
