Hi all,
we are still affected by this issue from 2019 on 5.10.
For example when setting "cma=256M" on phycore imx6q with 2G ram we get:
[ 12.573276] etnaviv etnaviv: command buffer outside valid memory window
[ 12.616460] etnaviv etnaviv: command buffer outside valid mem
ision: 5108
[0.530748] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
[0.530833] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
[0.530853] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
...
[5.374046] etnaviv etnaviv: command buffer outside valid memory w
https://bugs.freedesktop.org/show_bug.cgi?id=111789
Martin Peres changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111789
--- Comment #5 from usual user ---
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
--
You ar
https://bugs.freedesktop.org/show_bug.cgi?id=111789
--- Comment #4 from usual user ---
Created attachment 145508
--> https://bugs.freedesktop.org/attachment.cgi?id=145508&action=edit
kodi.jpeg
Fedora can not ship for one or other legal reason what you are asking for.
But if you enable https://
https://bugs.freedesktop.org/show_bug.cgi?id=111789
--- Comment #3 from Vlado Plaga ---
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 co
https://bugs.freedesktop.org/show_bug.cgi?id=111789
--- Comment #2 from usual user ---
Ups, it is "cma=256M@2G" of course. Sorry for the typo.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-deve
https://bugs.freedesktop.org/show_bug.cgi?id=111789
--- Comment #1 from usual user ---
I use "cma=256@2G" at the kernel command line as a workaround for now.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailin
https://bugs.freedesktop.org/show_bug.cgi?id=111789
Bug ID: 111789
Summary: drm/etnaviv: command buffer outside valid memory
window (on cubox i4), Linux 5.3
Product: DRI
Version: unspecified
Hardware: ARM
On Thu, Jun 27, 2019 at 04:49:30PM +0200, Lucas Stach wrote:
> Am Donnerstag, den 27.06.2019, 15:32 +0100 schrieb Russell King - ARM Linux
> admin:
> > On Thu, Jun 27, 2019 at 11:04:17AM +0100, Russell King - ARM Linux admin
> > wrote:
> > > On Thu, Jun 27, 2019 at 11:20:15AM +0200, Lucas Stach w
Am Donnerstag, den 27.06.2019, 15:32 +0100 schrieb Russell King - ARM Linux
admin:
> On Thu, Jun 27, 2019 at 11:04:17AM +0100, Russell King - ARM Linux admin
> wrote:
> > On Thu, Jun 27, 2019 at 11:20:15AM +0200, Lucas Stach wrote:
> > > Am Samstag, den 22.06.2019, 17:16 +0100 schrieb Russell Kin
On Thu, Jun 27, 2019 at 11:04:17AM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Jun 27, 2019 at 11:20:15AM +0200, Lucas Stach wrote:
> > Am Samstag, den 22.06.2019, 17:16 +0100 schrieb Russell King - ARM Linux
> > admin:
> > > While updating my various systems for the TCP SACK issue, I n
On Thu, Jun 27, 2019 at 11:20:15AM +0200, Lucas Stach wrote:
> Am Samstag, den 22.06.2019, 17:16 +0100 schrieb Russell King - ARM Linux
> admin:
> > While updating my various systems for the TCP SACK issue, I notice
> > that while most platforms are happy, the Cubox-i4 is not. During
> > boot, we
Am Samstag, den 22.06.2019, 17:16 +0100 schrieb Russell King - ARM Linux admin:
> While updating my various systems for the TCP SACK issue, I notice
> that while most platforms are happy, the Cubox-i4 is not. During
> boot, we get:
>
> [0.00] cma: Reserved 256 MiB at 0x3000
> ...
> [
While updating my various systems for the TCP SACK issue, I notice
that while most platforms are happy, the Cubox-i4 is not. During
boot, we get:
[0.00] cma: Reserved 256 MiB at 0x3000
...
[0.00] Kernel command line: console=ttymxc0,115200n8 console=tty1
video=mxcfb0:dev=hdmi
15 matches
Mail list logo
