From owner-freebsd-x11@freebsd.org Sun Jan 20 04:12:33 2019 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3441C14A395C for ; Sun, 20 Jan 2019 04:12:33 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE14284F8C; Sun, 20 Jan 2019 04:12:32 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id C058F17331; Sun, 20 Jan 2019 04:12:32 +0000 (UTC) From: Jan Beich To: Chung-Yeol Lee Cc: freebsd-x11@freebsd.org Subject: Re: Xorg server segmentation fault when monitor is not connected. References: Date: Sun, 20 Jan 2019 05:12:28 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Rspamd-Queue-Id: CE14284F8C X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.85 / 15.00]; TAGGED_RCPT(0.00)[]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_SHORT(-0.85)[-0.848,0]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-0.998,0] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2019 04:12:33 -0000 Chung-Yeol Lee writes: >> > Is this a known issue? >> >> Not enough details. The crash fingerprint is obscured by lack of symbols, >> so it's not possible to search if anyone reported a similar issue upstream. >> > > Sorry for the lack of context. I hoped this is known issue or something > obvious from its symptom. > here's better stack trace with debug symbol: > #0 memcpy () at /usr/src/lib/libc/amd64/string/memmove.S:306 > #1 0x0000000802834af8 in r600_create_vertex_fetch_shader (ctx=0x8010fa340, > count=2, elements=0x7fffffffd8c0) at r600_asm.c:2783 > #2 0x0000000802690636 in util_blitter_create (pipe=0x8010fa340) at > util/u_blitter.c:302 > #3 0x000000080283cd5f in r600_create_context (screen=0x806674100, > priv=0x0, flags=0) at r600_pipe.c:231 [...] Looks similar to https://lists.freedesktop.org/archives/amd-gfx/2018-May/022218.html fixed by https://github.com/FreeBSDDesktop/kms-drm/commit/1d67729d7c5f which is part of drm-fbsd12.0-kmod >= 4.16.g20181210. xf86-video-ati better works on radeonkms under /boot/modules/ from drm-fbsd12.0-kmod. xf86-video-ati-legacy is for radeonkms under /boot/kernel/ from base system. Check which kernel driver is loaded via $ kldstat -v | fgrep radeon As AMD Radeon 7450 (aka ARUBA 0x9993) is supported by both base and ports I wonder if you've accidentally loaded the wrong one. > #13 0x0000000801b2b1be in gbm_create_device () from > /usr/local/lib/libgbm.so.1 > #14 0x0000000801b0299d in radeon_glamor_pre_init (scrn=0x801ba5000) at > radeon_glamor.c:135 > #15 0x0000000801aee262 in RADEONPreInitAccel_KMS (pScrn=0x801ba5000) at > radeon_kms.c:1358 > #16 0x0000000801aecffe in RADEONPreInit_KMS (pScrn=0x801ba5000, flags=0) at > radeon_kms.c:1773 Looks like a crash from glamor. If switching drivers didn't help try forcing DRI2 and/or using EXA instead. See radeon(4x) manpage. -- Disclaimer: I don't use AMD hardware (yet), so you may want to wait for feedback from others.