Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Mar 2019 14:00:18 -0600
From:      Ian Lepore <ian@freebsd.org>
To:        Karl Denninger <karl@denninger.net>, ticso@cicely.de
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]]
Message-ID:  <4f4e94ea0aeb325440960782aafe2dcb7a7b6ad3.camel@freebsd.org>
In-Reply-To: <e0d25d47-98c9-4722-f798-bac2509450d8@denninger.net>
References:  <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <C68D7E6E-03C1-448F-8638-8BD1717DBF44@jeditekunum.com> <ac7d434f16f3a89f5ef247678d6becdbeded5c3f.camel@freebsd.org> <CE40E2B5-2244-4EF9-B67F-34A54D71E2E8@jeditekunum.com> <f60ea6d2-b696-d896-7bcb-ac628f41f7b8@denninger.net> <20190319161423.GH57400@cicely7.cicely.de> <52df098fdc0caf5de1879c93239534fffbd49b56.camel@freebsd.org> <40f57de2-2b25-3981-a416-b9958cc97636@denninger.net> <669892ac3fc37b0843a156c0ab102316829103fd.camel@freebsd.org> <663f2566-b035-7011-70eb-4163b41e6e55@denninger.net> <20190325164827.GL57400@cicely7.cicely.de> <3db9cf8a-68ee-e339-67bf-760ee51464fd@denninger.net> <fc17ac0f77832e840b9fffa9b1074561f1e766d8.camel@freebsd.org> <d96c7f42-f01b-8990-a558-ee92d631b51d@denninger.net> <30c8e58c15aec809522b5aa563755d66fea0f4ac.camel@freebsd.org> <e0d25d47-98c9-4722-f798-bac2509450d8@denninger.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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@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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4f4e94ea0aeb325440960782aafe2dcb7a7b6ad3.camel>