Bug 111789 - drm/etnaviv: command buffer outside valid memory window (on cubox i4), Linux 5.3
Summary: drm/etnaviv: command buffer outside valid memory window (on cubox i4), Linux 5.3
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: unspecified
Hardware: ARM Linux (All)
: not set not set
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-23 18:17 UTC by Vlado Plaga
Modified: 2019-11-19 08:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg from kernel 5.3, loading firmware (39.24 KB, text/plain)
2019-09-23 18:17 UTC, Vlado Plaga
no flags Details
kodi.jpeg (83.41 KB, image/jpeg)
2019-09-25 06:24 UTC, usual user
no flags Details

Description Vlado Plaga 2019-09-23 18:17:07 UTC
Created attachment 145475 [details]
dmesg from kernel 5.3, loading firmware

I'm trying to get somewhat accelerated video output out of my CuBox i4 (imx6 cpu, GC2000 graphics), but I don't have any luck with kernels 5.0, 5.2, or 5.3.

I tried recent Armbian and Fedora (30 and 31 beta).

The etnaviv messages from dmesg are:

[   18.891291] etnaviv etnaviv: bound 130000.gpu (ops gpu_ops [etnaviv])
[   18.895022] etnaviv etnaviv: bound 134000.gpu (ops gpu_ops [etnaviv])
[   18.898366] etnaviv etnaviv: bound 2204000.gpu (ops gpu_ops [etnaviv])
[   18.898385] etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
[   18.929873] etnaviv-gpu 130000.gpu: command buffer outside valid memory window
[   18.931182] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
[   19.075240] etnaviv-gpu 134000.gpu: command buffer outside valid memory window
[   19.076522] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
[   19.076542] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
[   19.083510] [drm] Initialized etnaviv 1.2.0 20151214 for etnaviv on minor 1

I'll attach the complete dmesg - or you can see it here: http://ix.io/1WAW

Google brought me to Russell King's similar problem from June:
https://lists.freedesktop.org/archives/dri-devel/2019-June/224474.html

I don't know why the problem disappeared for him, though.

Initially I reported the problem at the armbian forum:
https://forum.armbian.com/topic/11539-no-hdmi-with-linux-image-dev-cubox-kernel-5211/

I'm more of a user than a developer, especially when it comes to the Linux kernel. But I can test switches or patches.

Any help would be appreciated!
Comment 1 usual user 2019-09-24 09:19:27 UTC
I use "cma=256@2G" at the kernel command line as a workaround for now.
Comment 2 usual user 2019-09-24 11:24:48 UTC
Ups, it is "cma=256M@2G" of course. Sorry for the typo.
Comment 3 Vlado Plaga 2019-09-24 19:16:30 UTC
Cool, thank you, "usual user"! Your "cma=256M@2G" works for me. No more "command buffer outside valid memory window", and I could start Weston with weston-launch! The terminal there had a nice shadow, and I could drag it around smoothly.

(But Fedora 31 for arm apparently does not offer vlc, mplayer, or kodi... so I'm gonna try Armbian again next, with the switch)
Comment 4 usual user 2019-09-25 06:24:43 UTC
Created attachment 145508 [details]
kodi.jpeg

Fedora can not ship for one or other legal reason what you are asking for.
But if you enable https://rpmfusion.org all you asked for is available.
E.g. Kodi is at 18.4 final currently. See kodi.jpeg while playing bbb.
Comment 5 usual user 2019-10-19 12:01:39 UTC
Regression fix [1] just landed. The "@2G" workaround is no longer required.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f3057ad767542be7bbac44e548cb44017178a163
Comment 6 Martin Peres 2019-11-19 08:54:11 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/misc/issues/6.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.