From owner-freebsd-current@freebsd.org Tue Jan 12 12:43:48 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 903044D6EB5 for ; Tue, 12 Jan 2021 12:43:48 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from out.alvermark.net (out.alvermark.net [185.34.136.138]) (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 4DFVcg5778z3CCx for ; Tue, 12 Jan 2021 12:43:47 +0000 (UTC) (envelope-from jakob@alvermark.net) Received: from c-f649235c.06-431-73746f70.bbcust.telenor.se ([92.35.73.246] helo=mail.alvermark.net) by out.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1kzJ1U-0002iU-Pg; Tue, 12 Jan 2021 13:43:44 +0100 Received: from [192.168.67.33] by mail.alvermark.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1kzJ1U-000K9j-4Q; Tue, 12 Jan 2021 13:43:44 +0100 Subject: Re: Panic after updating To: Hans Petter Selasky , 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: Jakob Alvermark Message-ID: Date: Tue, 12 Jan 2021 13:43:43 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.4.1 MIME-Version: 1.0 In-Reply-To: <75784796-b513-5573-abc4-8c445d03c007@selasky.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 4DFVcg5778z3CCx X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[alvermark.net:s=x]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.34.136.138]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[alvermark.net: no valid DMARC record]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[185.34.136.138:from:127.0.2.255]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[alvermark.net:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[185.34.136.138:from]; ASN(0.00)[asn:34971, ipnet:185.34.136.0/24, country:IT]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] 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 12:43:48 -0000 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. Jakob