Re: Panic after updating

2021-01-13 Thread Ian Lepore
On Wed, 2021-01-13 at 10:37 +0100, Jakob Alvermark wrote: > On 1/13/21 10:07 AM, Hans Petter Selasky wrote: > > > > > > Yes! That works! Thank you! > > > > > > > See: > > > > https://cgit.freebsd.org/src/commit/?id=bafb682656724d06045fa494efb83a4312036f1f > > > > > > > Nice! Thanks again!

Re: Panic after updating

2021-01-13 Thread Jakob Alvermark
On 1/13/21 10:07 AM, Hans Petter Selasky wrote: Yes! That works! Thank you! See: https://cgit.freebsd.org/src/commit/?id=bafb682656724d06045fa494efb83a4312036f1f Nice! Thanks again! Jakob ___ freebsd-current@freebsd.org mailing list https:/

Re: Panic after updating

2021-01-13 Thread Hans Petter Selasky
Yes! That works! Thank you! See: https://cgit.freebsd.org/src/commit/?id=bafb682656724d06045fa494efb83a4312036f1f --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any

Re: Panic after updating

2021-01-12 Thread Jakob Alvermark
On 1/12/21 6:10 PM, Hans Petter Selasky wrote: On 1/12/21 2:46 PM, Hans Petter Selasky wrote: On 1/12/21 2:40 PM, Jakob Alvermark wrote: On 1/12/21 2:16 PM, Hans Petter Selasky wrote: 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:

Re: Panic after updating

2021-01-12 Thread Ian Lepore
On Tue, 2021-01-12 at 19:56 +0100, Hans Petter Selasky wrote: > On 1/12/21 7:45 PM, Ian Lepore wrote: > > > > - for (int i = 0; i <= sc->sc_npins; i++) { > > > > + for (int i = 0; i != sc->sc_npins; i++) { > > > > mtx_destroy(&sc->sc_pin_intr[i].mtx); > > > >

Re: Panic after updating

2021-01-12 Thread Hans Petter Selasky
On 1/12/21 7:45 PM, Ian Lepore wrote: - for (int i = 0; i <= sc->sc_npins; i++) { + for (int i = 0; i != sc->sc_npins; i++) { mtx_destroy(&sc->sc_pin_intr[i].mtx); free(&sc->sc_pin_intr[i].pin, M_GPIOC); } --HPS If that is the problem, I'd

Re: Panic after updating

2021-01-12 Thread Ian Lepore
On Tue, 2021-01-12 at 18:10 +0100, Hans Petter Selasky wrote: > On 1/12/21 2:46 PM, Hans Petter Selasky wrote: > > On 1/12/21 2:40 PM, Jakob Alvermark wrote: > > > > > > On 1/12/21 2:16 PM, Hans Petter Selasky wrote: > > > > On 1/12/21 1:43 PM, Jakob Alvermark wrote: > > > > > > > > > > On 1/12/2

Re: Panic after updating

2021-01-12 Thread Hans Petter Selasky
On 1/12/21 2:46 PM, Hans Petter Selasky wrote: On 1/12/21 2:40 PM, Jakob Alvermark wrote: On 1/12/21 2:16 PM, Hans Petter Selasky wrote: 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 ne

Re: Panic after updating

2021-01-12 Thread Hans Petter Selasky
On 1/12/21 2:40 PM, Jakob Alvermark wrote: On 1/12/21 2:16 PM, Hans Petter Selasky wrote: 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

Re: Panic after updating

2021-01-12 Thread Jakob Alvermark
On 1/12/21 2:16 PM, Hans Petter Selasky wrote: 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.

Re: Panic after updating

2021-01-12 Thread Hans Petter Selasky
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 th

Re: Panic after updating

2021-01-12 Thread Jakob Alvermark
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 ff3468ac94597efdcb

Re: Panic after updating

2021-01-12 Thread Hans Petter Selasky
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:  

Re: Panic after updating

2021-01-12 Thread Jakob Alvermark
On 1/12/21 9:33 AM, Jakob Alvermark wrote: On 1/11/21 7:08 PM, Hans Petter Selasky wrote: On 1/11/21 5:24 PM, Jakob Alvermark wrote: On 1/11/21 1:14 PM, Hans Petter Selasky wrote: On 1/11/21 11:12 AM, Jakob Alvermark wrote: Updated my Acer laptop from r367734 to main-c255666-g1790f5e654f

Re: Panic after updating

2021-01-12 Thread Jakob Alvermark
On 1/11/21 7:08 PM, Hans Petter Selasky wrote: On 1/11/21 5:24 PM, Jakob Alvermark wrote: On 1/11/21 1:14 PM, Hans Petter Selasky wrote: On 1/11/21 11:12 AM, Jakob Alvermark wrote: Updated my Acer laptop from r367734 to main-c255666-g1790f5e654f Rebooting with the newly build kernel i get

Re: Panic after updating

2021-01-11 Thread Hans Petter Selasky
On 1/11/21 5:24 PM, Jakob Alvermark wrote: On 1/11/21 1:14 PM, Hans Petter Selasky wrote: On 1/11/21 11:12 AM, Jakob Alvermark wrote: Updated my Acer laptop from r367734 to main-c255666-g1790f5e654f Rebooting with the newly build kernel i get this panic. Fatal    trap 12: page fault while

Re: Panic after updating

2021-01-11 Thread Jakob Alvermark
On 1/11/21 6:07 PM, Matthias Apitz wrote: On Mon, 11 Jan 2021 17:24:39 +0100, Jakob Alvermark wrote: On 1/11/21 1:14 PM, Hans Petter Selasky wrote: On 1/11/21 11:12 AM, Jakob Alvermark wrote: Updated my Acer laptop from r367734 to main-c255666-g1790f5e654f Rebooting with the newly build ke

Re: Panic after updating

2021-01-11 Thread Matthias Apitz
On Mon, 11 Jan 2021 17:24:39 +0100, Jakob Alvermark wrote: > > On 1/11/21 1:14 PM, Hans Petter Selasky wrote: >> On 1/11/21 11:12 AM, Jakob Alvermark wrote: >>> >>> Updated my Acer laptop from r367734 to main-c255666-g1790f5e654f >>> >>> >>> Rebooting with the newly build kernel i get this panic. >

Re: Panic after updating

2021-01-11 Thread Jakob Alvermark
On 1/11/21 1:14 PM, Hans Petter Selasky wrote: On 1/11/21 11:12 AM, Jakob Alvermark wrote: Updated my Acer laptop from r367734 to main-c255666-g1790f5e654f Rebooting with the newly build kernel i get this panic. Fatal    trap 12: page fault while in kernel mode cpuid    = 1; apic id = 02

Re: Panic after updating

2021-01-11 Thread Hans Petter Selasky
On 1/11/21 11:12 AM, Jakob Alvermark wrote: Updated my Acer laptop from r367734 to main-c255666-g1790f5e654f Rebooting with the newly build kernel i get this panic. Fatal    trap 12: page fault while in kernel mode cpuid    = 1; apic id = 02 fault    virtual address = 0x103 fault