Date: Fri, 15 Oct 2021 23:25:01 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Jan Beich <jbeich@freebsd.org> Cc: FreeBSD User <freebsd@walstatt-de.de>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: 13-STABLE/drm-fbsd13-kmod: Firefox crash: Bad system call Message-ID: <YWnjnUsf66oNv4LY@kib.kiev.ua> In-Reply-To: <35p2-jazc-wny@FreeBSD.org> References: <20211015095233.19c841d0@hermann.fritz.box> <35p2-jazc-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 15, 2021 at 10:20:55PM +0200, Jan Beich wrote:
> FreeBSD User <freebsd@walstatt-de.de> writes:
>
> > After updating 13-STABLE to 13.0-STABLE #3 stable/13-n247671-70db230dcbd: Thu Oct 14
> > 20:48:53 CEST 2021 amd64 on a Lenovo E540 notebook with Intel iGPU and also updating port
> > graphics/drm-fbsd13-kmod to drm-fbsd13-kmod-5.4.144.g20211013, graphics/libdrm to
> > libdrm-2.4.107_1,1, Firefox (firefox-93.0_1,2) crashes now with the following message:
>
> Which revision "13-STABLE" was before the update? If you didn't change
> any kernel options (and bump into a pilot error) bisecting may help.
>
> >
> > [~] firefox
> > Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with
> > reason=AbnormalShutdown (t=0.216076) Exiting due to channel error. Bad system
> > callgraphics/libdrm.
>
> Run under truss(1) or ktrace(1) (enable tracing descendants) to get the
> syscall name or number. For example, Firefox requires CAPABILITIES for
> cap_rights_{limit,init} and COMPAT_FREEBSD11 [1] for pre-ino64 via Rust.
>
> [1] https://github.com/rust-lang/libc/pull/2406
If you set kern.lognosys=3, it should be quite loud advertized which syscall
was missed, ie. console + control terminal.
terminal)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YWnjnUsf66oNv4LY>