From owner-freebsd-current@freebsd.org Tue Jan 12 13:17:07 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 775FF4D7AE9 for ; Tue, 12 Jan 2021 13:17:07 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DFWM64483z3FW3 for ; Tue, 12 Jan 2021 13:17:05 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2020.home.selasky.org (unknown [178.17.145.105]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id EBE7E2604E4; Tue, 12 Jan 2021 14:16:57 +0100 (CET) Subject: Re: Panic after updating To: Jakob Alvermark , FreeBSD Current References: <87512669-f0b9-eb2f-1103-170a29384ea8@alvermark.net> <34a9dafd-9690-1b33-abf8-017ad31cf2ab@alvermark.net> <60e4db60-c816-463e-0e08-a33c674ad4da@alvermark.net> <75784796-b513-5573-abc4-8c445d03c007@selasky.org> From: Hans Petter Selasky Message-ID: <5724744d-7710-4c3c-416b-01314cb196d4@selasky.org> Date: Tue, 12 Jan 2021 14:16:46 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4DFWM64483z3FW3 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[2a01:4f8:c17:6c4b::2:from]; R_SPF_ALLOW(-0.20)[+a:mail.turbocat.net]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[selasky.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2a01:4f8:c17:6c4b::2:from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/29, country:DE]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2021 13:17:07 -0000 On 1/12/21 1:43 PM, Jakob Alvermark wrote: > > On 1/12/21 12:54 PM, Hans Petter Selasky wrote: >> On 1/12/21 12:32 PM, Jakob Alvermark wrote: >>> Alright, after a new bisect run I got a different result, so I most >>> likely did something wrong the first time. >>> >>> ff3468ac94597efdcbc56f372528dfc98b114dac is the first bad commit >>> commit ff3468ac94597efdcbc56f372528dfc98b114dac >>> Author: Ian Lepore >>> Date:   Sat Dec 12 18:34:15 2020 +0000 >>> >>>      Provide userland notification of gpio pin changes ("userland >>> gpio interrupts"). >>> >>> >>> Maybe more likely this is causing the panic? >> >> Doesn't make sense :-( >> >> Can you try to fetch the latest 13-current as of now and re-build the >> kernel? I noticed some issues myself which got fixed. > > > I did that, still panics the same way. > > But, the commit above is about gpio, and I do have 'bytgpio_load="YES"' > in my /boot/loader.conf > > If I boot the kernel without that it works. > > 'kldload bytgpio' panics the machine. > Could you screenshot the panic backtrace after kldload of bytegpio ? --HPS