Date: Sat, 12 Feb 2022 03:01:44 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 261666] x11/nvidia-driver, x11/linux-nvidia-libs: update to 510.47.03. Message-ID: <bug-261666-7141-u6ONyqeS2j@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-261666-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-261666-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D261666 --- Comment #14 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> --- (In reply to Alex S from comment #13) > That backtrace looks nonsensical to me. Neither InitFonts nor=20 > UpdateCurrentTimeIf call each other, for example. Maybe opening a core fi= le=20 > directly with a debugger will get us better result? Yes, it's confusing. And unfortunately, no core generated. I could not find core even if I've run `bfs / -name "*.core" -type f`as root. Only found kept cores before (unrela= ted here). Maybe the pre-compiled-by-nvidia binaries handle sigsegv and not at all invoking coredump. > In general: > 1. Linux emulation bits in the kernel driver can't cause this crash; > 2. PRIME render offloading support on the kernel side doesn't have anyt= hing to=20 > do with this crash; > 3. The module Xorg loads is not patched in any way by the port. Agreed. But PRIME is not used here. Neither enabled by /etc/X11/xorg.conf n= or enabled on BIOS configuration (as disabled internal GPU). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-261666-7141-u6ONyqeS2j>