From owner-freebsd-arm@freebsd.org Mon Mar 25 17:05:50 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 A447615462DD for ; Mon, 25 Mar 2019 17:05:50 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1.eu.mailhop.org (outbound1.eu.mailhop.org [52.28.251.132]) (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 DECC275D18 for ; Mon, 25 Mar 2019 17:05:49 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1553533548; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=LrNWZnmeD8tNH2M/CM+d99eslG8yy2PXkZTf3YvHEX7m9L1gLWk+erTC1H9dMkt+Bys+aiUouufNG A7MGdydvVGTROunKFB248lusejthqQYB/HnQs67C+Wwow5d3Cp8oG6K0y/bbljWc9gdsEXSFqE2c9m eRiTP2V+B4knBBN/eW/46iXFBVTOahscxKUgFOVsbamlSIWSpNT4zdncAkQNyxB37RvPhjhVd7NIXc 048zZVQAB6gBnbHaeDhLsWWEJt55KDQ86e8x6e7YtcLueMc0tPZwHxBwakr+ocOCPKk/92RlETeYgv cC0jCYb48dFtlrajjq/pnBfgQfq8+4A== 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=lnJMAY4sZtBAxtOe/0VhFS/cHVTY67mA8QIwuFiGlBo=; b=oqElSqXptTmq1ifmcTQK2AC2O7FiLTWCoOK8t/U9F8fTY9jQvharAiQ2J9ddZGa7sdFWg6tnc4bk/ wQA6wJY5oQE8mDMfsUVYqXMnIIGBVe3sy7qstO4PpGxiTc3QjOkf3lGFOHoit1h2rDkcqxmt5KSDJO djn6BIqlPritsfNo0pL2HFiyshg+VLU1ejMw1YA8miRJBXBDixBm+SgrtaaLago/1k+6nj1paXTFB5 DKjUT8rWdVRY4j38D3H6iDl1Lp3hluE5t39my+lWW3Y2SDwtPg+/C0xnIqR8aXGeFjpkwK/1DfWXku lDGUSxbi13zOQuu5f8IioxucL5ooaMQ== ARC-Authentication-Results: i=1; outbound3.eu.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=lnJMAY4sZtBAxtOe/0VhFS/cHVTY67mA8QIwuFiGlBo=; b=aIwkWrXkEdhrclQf2m8jd3IEJ3TPaN7AdliWvJGj578cDv55OwBcZNzEnd6/57V8lBXWX/H7q6JPp jWGzIKn6uD58A2N6S9aSm/xuc8Gz0W4q7M7jWKb1mO1RMynbhmDzJsbyjc4QvEwyyFUXOr7iOPSA+l J85y2xuHB2uViqp9UIWu8sZkX6NrHFz93DtOnAU5xTLx+PKSOlixhTEUumg/QlXZbgJ6OJw5UfnQwR xb+0eZZaOGp8KMXq5/uoggxdIw4sR524EumrMBMyZnI0aDaCVyMWu8+XA+H8vQKkaq39LDbo7XVn2L oDLiIhsGJNT7CZ86pCAZG7lbIpnNxfg== X-MHO-RoutePath: aGlwcGll X-MHO-User: 3940bd38-4f20-11e9-908b-352056dbf2de 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.eu.mailhop.org (Halon) with ESMTPSA id 3940bd38-4f20-11e9-908b-352056dbf2de; Mon, 25 Mar 2019 17:05:44 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2PH5g3b083679; Mon, 25 Mar 2019 11:05:42 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: Subject: Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]] From: Ian Lepore To: Karl Denninger , ticso@cicely.de Cc: "freebsd-arm@freebsd.org" Date: Mon, 25 Mar 2019 11:05:42 -0600 In-Reply-To: <3db9cf8a-68ee-e339-67bf-760ee51464fd@denninger.net> 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: DECC275D18 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_SHORT(-0.98)[-0.982,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:16509, ipnet:52.28.0.0/16, 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: Mon, 25 Mar 2019 17:05:50 -0000 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: > > > > What do you mean by an insane rate? It's normal for the usb > > > > controller > > > > to be showing around thousands of int/sec. Despite what seems > > > > like a > > > > high rate, even on an on rpi-b it uses under 2% cpu to service > > > > that. > > > > > > > > root@rpi:~ # vmstat -i > > > > interrupt total rate > > > > intc0,2: vchiq0 2 0 > > > > intc0,11: systimer0 10103206 1110 > > > > intc0,17:-x_dwcotg0 218596055 24007 > > > > intc0,28: bcm_dma0 834 0 > > > > intc0,61: iichb0 5778 1 > > > > intc0,65: uart0 1817 0 > > > > intc0,70:-dhci_bcm0 172 0 > > > > Total 228707864 25118 > > > > > > > > -- Ian > > > > > > The story gets more odd. > > > > > > The same *physical* unit that I saw this on last night with no > > > I2c > > > device connected I restarted this morning -- changing NOTHING -- > > > and it > > > disappeared. > > > > > > But -- on another unit it's still there (I haven't shut down, > > > pulled > > > power and restarted that one.) > > > > > > vmstat -i on both doesn't show anything all that odd: > > > misbehaving that's not there, and neither are the missed > > > interrupt > > > complaints. > > > > > > But again, last night the one that this morning is NOT > > > misbehaving WAS, > > > and was showing the exact same thing. > > > > > > So this looks like something that is not being initialized > > > property at > > > boot time, and sometimes however it comes up causes trouble, and > > > other > > > times it does not -- which is likely to make it a "lot" of fun to > > > find. > > > > By causing trouble - do you mean it doesn't work? > > I noticed that my system has this message: > > nxprtc0: RTC clock not running > > Warning: bad time from time-of-day clock, system time will not be > > set accurately > > This shouldn't happen, but I wonder if the iic communication works > > at all. > > I likely wouldn't notice if the rtc failed. > > Maybe there was an initial problem at start as you said. > > Will reboot it and see what happens. > > After a reboot the message about the rtc is gone. > > Have to wait at least a day to see if the Spurious are gone too. > > In both cases on my boxes everything is working, but that's not > unexpected because of the way my code works (it dynamically detects a > change in configuration in that if it tries to open the I2c bus when > there's a configuration file for devices on it, and it fails, it will > try again in a few seconds -- and if you remove the config then it > will > shut down the I/O path in a short while and stop.) > > On the units that exhibit the problem the load average is 1.0 + > whatever > is real *and* the crazy interrupt rate is present. On the ones that > are > not neither is the case; the native and real load average is present > and > the interrupt rate is normal. > > In the case of the unit that the problem showed up on and then > disappeared, however, while there's an I2c config defined there's no > device connected to it on my bench. > > But I suspect this is something banging the interrupts on the CPU > that > is not attached to anything in the code, and the reason I suspect > that > is that on a given boot it either happens or not, and if it does then > nothing I can do will make it stop -- and likewise, nothing I can do > will make it start if it doesn't on boot. That implies that whatever > it > is it's not code-specific nor .ko-loaded specific either, in that if > it > was related specifically to an I2c device being talked to actively > then > when I killed the code that was using I2c or booted without the > device > connected (or never started the code that attempted to probe the bus > and > attach to the device in question) it wouldn't do it at all -- but > that's > not true. > > The one that stopped doing it I then attached both an I2c device that > it > was looking for and also connected a "modem-style" device (which > caused > umodem.ko to autoload, as expected) and it came up as well, without a > problem -- and without triggering the mad interrupt storm. > 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