Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]]
Ian Lepore
ian at freebsd.org
Mon Mar 25 20:00:34 UTC 2019
On Mon, 2019-03-25 at 14:25 -0500, Karl Denninger wrote:
> On 3/25/2019 12:37, Ian Lepore wrote:
> > > >
> > > [...]
> >
> > Apply this patch...
> >
> >
https://svnweb.freebsd.org/base/head/sys/kern/kern_intr.c?view=patch&r1=345475&r2=345474&pathrev=345475
> >
> > -- Ian
>
> Here's where it's coming from:
>
> root at rpi2:~ # vmstat -i
> interrupt total rate
> local_intc0,1:-mer0 80944 1361
> local_intc0,3:-mer0 32210287 541604
> local_intc0,8:-ntc0 888341 14937
> local_intc0,9: pmu0 2 0
> intc0,1: mbox0 40 1
> intc0,2: vchiq0 2 0
> intc0,17:-x_dwcotg0 1242279 20888
> intc0,28: bcm_dma0 74686 1256
> intc0,61: iichb0 1 0
> intc0,65: uart0 1856 31
> intc0,70:-dhci_bcm0 8952 151
> cpu0:rendezvous 13 0
> cpu1:rendezvous 14 0
> cpu2:rendezvous 15 0
> cpu3:rendezvous 18 0
> cpu2:ast 1 0
> cpu0:preempt 3167 53
> cpu1:preempt 13062 220
> cpu2:preempt 11133 187
> cpu0:hardclock 2 0
> Total 34534815 580690
>
>
We really need to change the name of the local_intc controller to
something shorter. I'm going to venture a guess that -mer0 is
'timer0'. That leads to the question of whether the driver is broken
somehow, or whether some callout is being scheduled for a crazy-high
rate.
-- Ian
More information about the freebsd-arm
mailing list