Date: Tue, 12 Jan 2021 12:54:00 +0100 From: Hans Petter Selasky <hps@selasky.org> To: Jakob Alvermark <jakob@alvermark.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Panic after updating Message-ID: <75784796-b513-5573-abc4-8c445d03c007@selasky.org> In-Reply-To: <af76d2fc-cc6f-4ca4-c293-ae1ff8f2a51d@alvermark.net> References: <87512669-f0b9-eb2f-1103-170a29384ea8@alvermark.net> <ad969a6e-4029-b85c-f304-1198b05ad725@selasky.org> <34a9dafd-9690-1b33-abf8-017ad31cf2ab@alvermark.net> <e407413b-730a-d60d-f50d-0b6f490da74a@selasky.org> <60e4db60-c816-463e-0e08-a33c674ad4da@alvermark.net> <af76d2fc-cc6f-4ca4-c293-ae1ff8f2a51d@alvermark.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ian@FreeBSD.org>
> 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.
--HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75784796-b513-5573-abc4-8c445d03c007>