From owner-freebsd-x11@freebsd.org Mon Nov 19 17:37:30 2018 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 4450E110DFCB for ; Mon, 19 Nov 2018 17:37:30 +0000 (UTC) (envelope-from matias@pizarro.net) Received: from mail.docbase.net (mail.docbase.net [188.40.142.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68464815FC for ; Mon, 19 Nov 2018 17:37:29 +0000 (UTC) (envelope-from matias@pizarro.net) Received: from mail.docbase.net (unknown [10.0.1.10]) by mail.docbase.net (Postfix) with ESMTP id 35E967FC96 for ; Mon, 19 Nov 2018 18:37:21 +0100 (CET) Authentication-Results: mail.docbase.net (amavisd-new); dkim=pass (1024-bit key) reason="pass (just generated, assumed good)" header.d=pizarro.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pizarro.net; h= content-transfer-encoding:user-agent:message-id:subject:subject :to:from:from:date:date:content-type:content-type:mime-version; s=dkim; t=1542649038; x=1543513039; bh=2CmnInVUBQZi+gAkC5QpQB4N 57LXP1lmZgDWTPrK8QM=; b=RRp6gGpEmcKvi8VDmVWkr+xOxxkVq6M7eFZ3Y+VE N3XzX0MCGV1gqsQK0QD/0UzYbxxMq614OshONNwvXMhP3ZtLJ4KOHNZs/iymffyP LNIxDaMYjrl4w7Z9afmzqwDI7l8dO+kiUwhZ/lWEDbgPxj1+4BUUHqVoAah9Amys huU= X-Virus-Scanned: amavisd-new at mail.docbase.net Received: from mail.docbase.net ([10.0.1.10]) by mail.docbase.net (mail.docbase.net [10.0.1.10]) (amavisd-new, port 10026) with ESMTP id zCjxXYL_jgMz for ; Mon, 19 Nov 2018 18:37:18 +0100 (CET) Received: from mail.docbase.net (unknown [10.0.1.10]) by mail.docbase.net (Postfix) with ESMTPSA id AC34E7FC8C for ; Mon, 19 Nov 2018 18:37:18 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Date: Mon, 19 Nov 2018 18:37:18 +0100 From: matias@pizarro.net To: freebsd-x11@freebsd.org Subject: 12.0-RC1 drm_atomic panic (supervisor read data, protection violation) Message-ID: X-Sender: matias@pizarro.net User-Agent: Roundcube Webmail Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 68464815FC X-Spamd-Result: default: False [-3.39 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[pizarro.net]; XM_UA_NO_VERSION(0.01)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-x11@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_MEDIUM(-1.00)[-0.998,0]; DKIM_TRACE(0.00)[pizarro.net:+]; DMARC_POLICY_ALLOW(-0.50)[pizarro.net,none]; FROM_NO_DN(0.00)[]; MX_GOOD(-0.01)[mail01.docbase.net,mail02.docbase.net,mail.docbase.net]; NEURAL_HAM_SHORT(-0.82)[-0.823,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-0.57)[asn: 24940(-2.82), country: DE(-0.01)]; ASN(0.00)[asn:24940, ipnet:188.40.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Server: mx1.freebsd.org 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: Mon, 19 Nov 2018 17:37:30 -0000 Hello everyone, Thanks for your great work that allows me to use a real OS on my work=20 machine. I have been tracking 12-CURRENT on a ThinkPad T450 without issues until=20 now. I just got myself a T480 and rolled out 12.0-BETA4 and then RC1,=20 with the same packages but I am getting a panic when launching either=20 Sublime Text 3 or Textadept. All my other packages (mpv, libreoffice,=20 Inkscape, Firefox, Chromium, Xfe etc...) are working fine but these two,=20 which are linux binaries (relevant?), trigger the panic, both in BETA4=20 and RC1, using drm-stable-kmod or drm-next-kmod, from quarterly or=20 latest pkg repos. At the moment I have $ pkg info -d drm-next-kmod drm-next-kmod-4.11.g20181027_1: gpu-firmware-kmod-g20181104 Bearing in mind these are running on different hardware: - works, self-compiled kernel: FreeBSD lenovo01 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r334644=20 amd64 - panics, fresh install from BETA4 image, binary-updated to RC1: FreeBSD lenovo01 12.0-RC1 FreeBSD 12.0-RC1 r340470 GENERIC =20 amd64 After 12 hours of trying to sort this out I have run out of ideas. I=20 would appreciate it if you could help me figure out what should my next=20 steps be. I could, for instance: 1) Roll-out 12.0-RC1 on a BE on the machine that works to see if the= =20 issue is linked with the change of hardware 2) Roll-out 12-CURRENT r334644 on a BE on the panicking machine to=20 see if the issue is linked to the change of kernel 3) Compile a DEBUG kernel on the panicking machine to help you=20 diagnose the issue 4) Roll out a patched kernel if the included information inspires=20 you an idea for a patch I have no idea of C or kernel hacking but I am confortable with=20 compiling custom kernels or building ports. I have put the following in a gist, though I include here an extract of=20 part of the dump report to (hopefully) whet your appetite: - /var/crash/core.txt, that contains full boot log, ps -axlww,=20 vmstat -s | -m | -z - /boot/loader.conf - /etc/rc.conf - /etc/sysctl.conf - /var/log/Xorg.0.log (I am not using any Xorg configuration) gist URL:=20 https://gist.github.com/rebost/1a2bbfc45e9273ae5a76a98c3a67a23d I also have the actual vmcore dump at hand if necessary, but that's=20 1,4GB. If there is anything else I can help you help me with, just let me know Thanks for your help, past and future. -- mat=C3=ADas