From owner-freebsd-arm@freebsd.org Mon Mar 25 16:52:32 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 AD51B1545C8C for ; Mon, 25 Mar 2019 16:52:32 +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 B604475390 for ; Mon, 25 Mar 2019 16:52:31 +0000 (UTC) (envelope-from ian@freebsd.org) ARC-Seal: i=1; a=rsa-sha256; t=1553532750; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=jjeQCh75JI7wi5M8FnN4ldD+UOZPyzmXNmDXfaZ9KbC1+nL1II6tg/s5+/rKujY9CcgmrXzsUt6ug LFMaV0+aE0Gm/R6HQ9ioS0uNxESnKzjxgKK+wwnpMQaBrRaB6jawXxs/W6iXAEaZqzMx86SOcxSrcq chbppijwI1HADCYXvPYLkhUayJhUhMdEYBQMKFF6LLC3YDCFX0KlKbIjHK2PrZhUy/uNTUgR+NSo73 KeBMNu2t9ztFSLgBArgWdwZntrdiH8rjEoPTDWvy/JxSWFq7VhxGG5C5EtE5mzrIaLJe6mWsvsOYLo A4S3BkTQ1xFQw6UNPkFGYudB9OEkiAA== 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=cTCxDwabceLeGFAsONz+j863+cFmHDghwdG3xf6ppYA=; b=V1zNvgqSAUi5VUKgDWZErMbIQ5FE2UOV1RWC95CfdbZMa1wSFfpz9l2CiTQ59YMOo6hYVH7tEae9L tib6dAVR2/sBVdVqVYIwq/cRBTjvTCh8xFeN7KL9t9ErNrotTBsGPfqGk2peV8BT3Su9G4FClrq8qq 8HUwP3RuQ4BdxTU0WzjHpGDkLx8GtmFVDltOU6ofqnzuw+l0CiWo4InFbEB15s9Iv8mNW4TEA+mDuN Rq7xDnMeIqIRjI3clw+KTgzpSHHivOFRKoJUIWXJ+GcDCTdtf76Q3Siw60HrchbktqLZ7JrewoSxyi V006lpMp8GXwnYCctwqooaAGCG7xf5w== 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=cTCxDwabceLeGFAsONz+j863+cFmHDghwdG3xf6ppYA=; b=MlMUS7enSooZJGGkEnCDxI01VY0SfhV7izS5jml7lfnoUTibpbO6hth5vFvfk7vfep33q7+M9ZH/O CPkAZid2e7iPq3vpgloNooRs9UcXFqNQxyAft9tKV5uQdM1Wej0TflQDe6Si5iLMmh7AFdfae2keCS Dk8voIA+4YlT9fwGYNXYk53ngTj28i58/b8ON9uB3zFLChv/NyPwpfUagapHbuDXQ9oBIuHATtkniP Q66yag+IRqgRvfh4CqrpTR0/egIVFzFA1yVgGIUYRnVqfNpSmPGJVEaYwSt/iDc4ji4t8JOcPlOdEQ g4nxsRgmWngEAVFA54mDFFQ285F/XSQ== X-MHO-RoutePath: aGlwcGll X-MHO-User: 5eb25d1b-4f1e-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 5eb25d1b-4f1e-11e9-9bb1-1f29e4676f89; Mon, 25 Mar 2019 16:52:29 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id x2PGqQfe083617; Mon, 25 Mar 2019 10:52:26 -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: ticso@cicely.de, Karl Denninger Cc: "freebsd-arm@freebsd.org" Date: Mon, 25 Mar 2019 10:52:26 -0600 In-Reply-To: <20190325164827.GL57400@cicely7.cicely.de> 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> 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: B604475390 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.981,0]; ASN(0.00)[asn:16509, ipnet:54.186.0.0/15, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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 16:52:32 -0000 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. -- Ian