Re: AMD GPU + HDMI + vlc = lockup
- To: debian-user@lists.debian.org
- Subject: Re: AMD GPU + HDMI + vlc = lockup
- From: Kamil Jońca <kjonca@poczta.onet.pl>
- Date: Thu, 04 Feb 2021 07:14:13 +0100
- Message-id: <[🔎] 87im78bbre.fsf@alfa.kjonca>
- In-reply-to: <BEhXH-4n9-1@gated-at.bofh.it> (Felix Miata's message of "Wed, 03 Feb 2021 05:30:01 +0100")
- References: <BCiOd-3VH-3@gated-at.bofh.it> <BEb5T-eG-13@gated-at.bofh.it> <BEb5T-eG-11@gated-at.bofh.it> <BEhXH-4n9-1@gated-at.bofh.it>
[ I replied yesterday, but I cannot see this on list ]
Felix Miata <mrmazda@earthlink.net> 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 0000:01:00.0: vgaarb: deactivate vga console
> [ 38.389555] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
> [ 38.389561] radeon 0000:01:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
> [ 38.389820] [drm] radeon: 1024M of VRAM memory ready
> [ 38.389824] [drm] radeon: 1024M of GTT memory ready.
> [ 38.926339] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/CEDAR_pfp.bin
> [ 39.013160] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/CEDAR_me.bin
> [ 39.066667] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/CEDAR_rlc.bin
> [ 39.526315] radeon 0000:01:00.0: firmware: direct-loading firmware radeon/CEDAR_smc.bin
> [ 39.554674] [drm] radeon: dpm initialized
> [ 39.774437] radeon 0000: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 0000:01:00.0: WB enabled
> [ 39.794958] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00
> [ 39.794963] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c
> [ 39.795338] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418
> [ 39.795763] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
> [ 39.795872] radeon 0000: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 0000:01:00.0: [drm] fb0: radeondrmfb frame buffer device
> [ 40.917823] [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0
similar but only 512M vram.
KJ
--
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Reply to: