From owner-freebsd-arm@freebsd.org Wed Apr 3 08:51:17 2019 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF19215648A8 for ; Wed, 3 Apr 2019 08:51:16 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C31DA6CF86; Wed, 3 Apr 2019 08:51:15 +0000 (UTC) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id x338p5S5025903; Wed, 3 Apr 2019 01:51:05 -0700 (PDT) (envelope-from freebsd-rwg@gndrsh.dnsmgr.net) Received: (from freebsd-rwg@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id x338p5JG025902; Wed, 3 Apr 2019 01:51:05 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201904030851.x338p5JG025902@gndrsh.dnsmgr.net> Subject: Re: insanely-high interrupt rates In-Reply-To: To: Ian Lepore Date: Wed, 3 Apr 2019 01:51:05 -0700 (PDT) CC: Karl Denninger , ticso@cicely.de, "freebsd-arm@freebsd.org" X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Rspamd-Queue-Id: C31DA6CF86 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.60 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.05)[-0.049,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.37)[0.373,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[dnsmgr.net]; AUTH_NA(1.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: gndrsh.dnsmgr.net]; NEURAL_SPAM_LONG(0.35)[0.350,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:13868, ipnet:69.59.192.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.03)[ip: (0.13), ipnet: 69.59.192.0/19(0.07), asn: 13868(0.04), country: US(-0.06)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2019 08:51:17 -0000 > On Mon, 2019-03-25 at 12:16 -0500, Karl Denninger wrote: > > On 3/25/2019 12:05, Ian Lepore wrote: > > > On Mon, 2019-03-25 at 11:58 -0500, Karl Denninger wrote: > > > > On 3/25/2019 11:48, Bernd Walter wrote: > > > > > On Mon, Mar 25, 2019 at 11:33:32AM -0500, Karl Denninger wrote: > > > > > > > [insanely high interrupt rates] > > > Is the interrupt rate consistent from second to second? Running > > > 'vmstat 1' for a while might be useful to see that. That many > > > interrupts almost sounds like a line is floating, but if that were > > > the > > > case I'd expect a widely varying number of int/sec. > > > > > > If you build custom kernels, it might be helpful to apply r345475 > > > locally... it will display partial device names instead of just '+' > > > when the name doesn't fit in the vmstat output. > > > > > > -- Ian > > > > No, but it's in the same general range -- around 500k although it does > > flop around some, and occasionally by a lot (e.g. if I sit and watch it > > it'll occasionally put up VERY different numbers -- e.g. a ~730k number, > > then it goes back, etc.) > > > > I don't generally build custom kernels on these but I CAN put this into > > the STABLE tree I'm building that from since I keep a separate one for > > Crochet builds on these boxes. Where do I find that specific delta? (I > > usually just svn things and I don't want to roll it all the way back to > > there, right -- or do I?) > > > > I now have an rpi2b, and I see the same thing you do in the 'vmstat -i' > output, including rates like 500K int/sec on cpu3 timer0. But while it > was behaving like that, the output from 'vmstat 1' showed a perfectly > steady 8800-9200 int/sec, which is certainly more consistent with top > showing under 2% being used for combined system+interrupt. > > I think the problem here is with vmstat -i, not with actual interrupts. > Something about the stats reporting is wrong on armv6/v7. > > Note that this is completely separate from the spurious interrupt > problem, which I still haven't been able to reproduce. I do not know if this data is of any relavance but when I was trying to get a Samsung chrome book snow working: https://wiki.freebsd.org/FreeBSD/arm/Chromebook I had tons of problems with spurious interrupts if I tried to use the internal keyboard. I found that if I plugged a USB keyboard in and never touched the built in keyboard I could infact get booted to multiuser and use the system somewhat. This testing was done on head before the stable/12 branch, I can re-aquire the hardware if there is anyone interested in helping to debug this platform. > -- Ian -- Rod Grimes rgrimes@freebsd.org