Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #63705

Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Wed, Mar 27, 2019 at 03:29:21PM +0100, Fabian Pietsch wrote:
> Package: src:linux
> Version: 4.19.28-2
> Followup-For: Bug #925334
> 
> Dear Maintainer,
> 
> the bug is still present in the current version. It took a freshly
> booted, idle system 3304 seconds for the bug to occur, though,
> so this time rather an hour (than 10-30min as stated before).
> 
> After the bug has happened, I get the following information from sysfs:
> 
> | root@rpi3:/sys/bus/platform/drivers/vc4_v3d# for I in enabled status active_time suspended_time; do echo -n "$I=$(cat 3fc00000.v3d/power/runtime_$I) "; done; echo
> | enabled=enabled status=error active_time=16800 suspended_time=55464216
> 
> And again:
> 
> | enabled=enabled status=error active_time=16800 suspended_time=55479160
> 
> So vc4_v3d which reported the error seems to be in status=error
> and counts as suspended. Manual attempts to get it to resume again,
> now that more cma is free again, failed, but there are probably ways
> I don't know about.
> 
> "echo on > .../power/control" changed runtime_enabled=forbidden
> (and echo auto > control changed it back to runtime_enabled=enabled),
> but runtime_status remained at "error".
> 
> Regards, Fabian
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: arm64 (aarch64)
> 
> Kernel: Linux 4.19.0-4-arm64 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_CRAP
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

Hi,

As discussed on IRC, thanks for your bug report and for the refresh.

Could you test, two stuffs for me ? :

1. The VC4 driver seems to use runtime pm operations, could you try to
disable runtime suspend completly (there are kernel parameters for this
if I remember correctly) ?

2. Your kernel cmdline are... weird, could you try with minimalistic
kernel cmdline ? Only keep console= for logging to uart and/or to your
tty0 and keep your rootfs.


Thanks,
Romain

Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3 Fabian Pietsch <fabian-debian@canvon.de> - 2019-03-23 12:10 +0100
  Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3 Fabian Pietsch <fabian-debian@canvon.de> - 2019-03-27 15:40 +0100
    Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3 Romain Perier <romain.perier@gmail.com> - 2019-03-27 21:40 +0100
      Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3 Fabian Pietsch <fabian-debian@canvon.de> - 2019-04-03 12:40 +0200
        Bug#925334: vc4: CMA fills up and screen not updated anymore on raspi3 Fabian Pietsch <fabian-debian@canvon.de> - 2019-04-03 15:30 +0200

csiph-web