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 <i...@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.
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
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
