On Fri, 25 Feb 2022 20:45:55 +0100 MichaIng wrote:
>
> Package: chromium
> Version: 98.0.4758.102-1~deb11u1
>
> Latest Chromium on Debian Bullseye fails to start on aarch64/arm64
> systems. Different ones with different kernels were tested, though all

> Linux 5.10 variants, using (and generally supporting) modesetting DDX.


Which boards did you test with?


>
> Only v98 from security repo is affected, v90 from "regular" Bullseye
> repo starts fine.
>
> -------
> [2380:2380:0220/184034.039483:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.122230:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.167681:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.198424:ERROR:system_web_app_manager.cc(320)]
> Exceeded SWA install retry attempts. Skipping installation, will retry
> on next OS update or when locale changes.
> [2380:2380:0220/184034.200305:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.225990:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> *** stack smashing detected ***: terminated
> *** stack smashing detected ***: terminated
> [2380:2380:0220/184034.240862:ERROR:gpu_process_host.cc(978)] GPU
> process exited unexpectedly: exit_code=6
> [2380:2380:0220/184034.240968:FATAL:gpu_data_manager_impl_private.cc(448)]
> GPU process isn't usable. Goodbye.
> -------
>
> The X server itself works well, any other X application starts fine, X
> server logs show no errors, but a regular exit like when you exit the X

> client. It's hence definitely Chromium itself which fails. We tried all


What desktops were you using? Was this under X or wayland? Does it make a difference if you run chromium with --ozone-platform=x11 or --ozone-platform=wayland ?  What about --use-gl=desktop ?


> kind of GPU related flags, like "--disable-gpu", changing renderer,
> disabling GPU rasterization and all such, any combination or skipping
> all of them, even the ones shipped by default with the package
> (/etc/chromium.d) makes no difference. Starting with xinit (as root),
> startx or from desktop doesn't make a difference either.
>
> Best regards,
>
> Micha
>
>

Reply via email to