From owner-freebsd-arm@freebsd.org Mon Mar 25 17:09:57 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 493C115464A4 for ; Mon, 25 Mar 2019 17:09:57 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [195.149.99.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A04D875F35; Mon, 25 Mar 2019 17:09:56 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id x2PH9r6R090308 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 25 Mar 2019 18:09:54 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cicely.de; s=default; t=1553533794; bh=dE6Lb2ai2GPWy7/0rwfVevbpVDqPyAHJRq6bTo7VuqM=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To; b=2T85IwY9nL610uQZ5EsfMlmab5vSO+1CJINppP+a50CMmkx4SozJNsJ/Ukkedn0xy MK2ecVOx3GoJN8KoJcTyOv29F7PYhdT5HtnDSfDt8EokS9MgihVVZY88UHfREXMl+h i74H/hymFWOp2QZv1vFpBEgxi1LmON2aWiVR+RfY= Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id x2PH9mTt033259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 25 Mar 2019 18:09:48 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTP id x2PH9m3J090674; Mon, 25 Mar 2019 18:09:48 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id x2PH9mR4090673; Mon, 25 Mar 2019 18:09:48 +0100 (CET) (envelope-from ticso) Date: Mon, 25 Mar 2019 18:09:48 +0100 From: Bernd Walter To: Ian Lepore Cc: ticso@cicely.de, Karl Denninger , "freebsd-arm@freebsd.org" Subject: Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]] Message-ID: <20190325170948.GN57400@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <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> <20190325170534.GM57400@cicely7.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190325170534.GM57400@cicely7.cicely.de> X-Operating-System: FreeBSD cicely7.cicely.de 12.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=4.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de X-Rspamd-Queue-Id: A04D875F35 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cicely.de header.s=default header.b=2T85IwY9 X-Spamd-Result: default: False [-1.79 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[ticso@cicely.de]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[cicely.de:+]; MX_GOOD(-0.01)[cached: mx1.bwct.de]; NEURAL_HAM_SHORT(-0.14)[-0.144,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:21461, ipnet:195.149.99.0/24, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.86)[-0.858,0]; R_DKIM_ALLOW(-0.20)[cicely.de:s=default]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; NEURAL_HAM_LONG(-0.97)[-0.973,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[cicely.de]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[3.99.149.195.list.dnswl.org : 127.0.20.0]; R_SPF_NA(0.00)[]; IP_SCORE(-0.00)[country: DE(-0.01)] 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:09:57 -0000 On Mon, Mar 25, 2019 at 06:05:35PM +0100, Bernd Walter wrote: > On Mon, Mar 25, 2019 at 10:52:26AM -0600, Ian Lepore wrote: > > On Mon, 2019-03-25 at 17:48 +0100, 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. > > > > > > > That's not a symptom of i2c comms failure, it's a symptom of a dead rtc > > battery. The driver has to communicate with the rtc chip to determine > > that the oscillator was stopped. After a reboot all is well, because > > the rtc oscillator gets started when the time is written to the chip, > > and it keeps running through a reboot and only stops on a power cycle. > > Agreed, but there is a story behind. > The board had a design flaw in that it drained the battery over the > pullups into the Pi when the Pi was powered down. > I fixed that circuit and did power down tests as well. > Don't know if the previous boot was after power down, but it is > unlikely that the battery is dead again and if it was a power down then > it was a rather short one. > It is not a test system, I run it 24/7 as a local ntp server since about > only 1-2 months. Well - lets reveal another point. I have removed the pull ups completely, in the assumption that the Pi itself has propper pull ups for at least short wiring. It did work, so I left it that way. So it could indeed be transfer errors by inadequate pull ups causing it. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.