From owner-freebsd-arm@freebsd.org Wed Apr 3 02:58:09 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 BC1481558C55 for ; Wed, 3 Apr 2019 02:58:08 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound3d.ore.mailhop.org (outbound3d.ore.mailhop.org [54.186.57.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B412D8C666 for ; Wed, 3 Apr 2019 02:58:07 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1554260286; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=S2Zq3voeA1dSMCmKWZogGpjsh3auRVyPkSfHOu6k7Vko9VU1Z7Ur9dBr2VSA1RMkON1GrUa8SxUvV uzcZJPKw5DVoEaU+uMRUHQLfJxTvwPVKGw5tV4D7VicD1Zzt2AjboFRKmIUBfz/DR8tsY312cfsbT6 7spnfLZWIOOEqmskBjbCIV41duV1TmHAaTqAXB8vCj1o4BqLATjXrtbRbMyOG+ZqLw2cEWSH3C3SRO RC5CqTizW2p6rqv3UX5teuc1g6sD+CccwPN9DOObExrqPpFrqub7CUxk/UAfKm9R2N8MbtiL194/Ak eo6T3RdU3dw0nsM1pVxBDg6YlApE8VQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:dkim-signature:from; bh=KLE1eq0f5Xuk4lc3XOvW1zfPZXVbC5nGNM0q+Z7LJNM=; b=aRoDltERDhTmnW6GiI6k7xPX6idyoKKDjeiRPIwFeVN5Eti0JD0Mg0Df02EoOsZe9omiTIGzrQKut 4OJWN2CYOFcNSQI7jetO96/ZtXAfRp6gPqcIrUckQxroJRl2FxoCvdBtDbNWKEKYnbbrqKIS7CEeGU xGXz/0YS05hofR/fJrrLcU+1gjFrv12mFjcOnNljwja5j2yMqY+zljV+UbysNXtzXhuC6hPLeNoRfs SrsUPbBVej7d4YZkJ/6EY45dFuChgfnlo/qtKWbZf7xeIbfM4ylc7WLDF8F1TrRuBONK3XPdFQOdmL x+aIegsMVXwuPtBGitugeWA7dgWl/xw== ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=softfail smtp.mailfrom=freebsd.org smtp.remote-ip=67.177.211.60; dmarc=none header.from=freebsd.org; arc=none header.oldest-pass=0; DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-transfer-encoding:mime-version:content-type:references:in-reply-to: date:cc:to:from:subject:message-id:from; bh=KLE1eq0f5Xuk4lc3XOvW1zfPZXVbC5nGNM0q+Z7LJNM=; b=dz/qV+MYdcPePECzPJkQmbUIcwPuj87nzcTcX4XfXEAkBKMBS6/M3m4waBI1qdEnBRRRMeFKMZ2ET PUtvfbM64Q44f7gr8iOq9PJL1lYpo57kgfQwoWanCFVgDgwVU3KuDCE692X4I6qy7ZkstmYIY8oLPw iXu4dbW3XULAaAqsUccFTyUKLEn8IhMrOfgLCV8ll3XVTWq66ojjh02CbUt3ybJdfSyKQPsARbM2vt pkCLNx87KXzJtK0YhH+TrS2SzlpVjIx752SpNmameIiEHahJpRmc75+hsLCrzlWhrqyfY/1rO/vg3N MhVMmICLnwvKEHJ5K32ZPyZc9dkJ8sg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 4b86020b-55bc-11e9-9bb1-1f29e4676f89 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 4b86020b-55bc-11e9-9bb1-1f29e4676f89; Wed, 03 Apr 2019 02:58:04 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x332w1jQ012122; Tue, 2 Apr 2019 20:58:01 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: insanely-high interrupt rates From: Ian Lepore To: Karl Denninger , ticso@cicely.de Cc: "freebsd-arm@freebsd.org" Date: Tue, 02 Apr 2019 20:58:01 -0600 In-Reply-To: References: <004ddba628b94b80845d8e509ddcb648d21fd6c9.camel@freebsd.org> <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> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 FreeBSD GNOME Team Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: B412D8C666 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.98)[-0.983,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US] 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 02:58:09 -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. -- Ian