Date: Mon, 25 Mar 2019 12:18:37 -0500 From: Karl Denninger <karl@denninger.net> To: ticso@cicely.de, Ian Lepore <ian@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: Options for FBSD support with LCD device - new project [[Maybe related: I2c issues on the Pi2]] Message-ID: <d19e42a8-eff5-a111-0bf4-8d4f802f95ba@denninger.net> In-Reply-To: <20190325170948.GN57400@cicely7.cicely.de> References: <CE40E2B5-2244-4EF9-B67F-34A54D71E2E8@jeditekunum.com> <f60ea6d2-b696-d896-7bcb-ac628f41f7b8@denninger.net> <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> <fc694564b1cf8bfa781ff86a7d5d7d09de68ad0e.camel@freebsd.org> <20190325170534.GM57400@cicely7.cicely.de> <20190325170948.GN57400@cicely7.cicely.de>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On 3/25/2019 12:09, Bernd Walter wrote:
> 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.
Not in my case - the board that was doing it, I power-cycled it and it
disappeared has NOTHING on any of the header/GPIO pins except for the
three wires connected to the USB/Serial interface for the console.
--
Karl Denninger
karl@denninger.net <mailto:karl@denninger.net>
/The Market Ticker/
/[S/MIME encrypted email preferred]/
[-- Attachment #2 --]
0 *H
010
`He 0 *H
00 H^Ōc!5
H0
*H
01 0 UUS10U Florida10U Niceville10U
Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA0
170817164217Z
270815164217Z0{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA0"0
*H
0
h-5B>[;olӴ0~͎O9}9Ye*$ g !ukvʶLzN`jL>MD'7U 45CB+kY`bd~b*c3Ny-78ju]9H euέsӬDؽmgwER?&UURj'}9nWD i`XcbGz \gG=u%\Oi13ߝ4
K44pYQr]Ie/r0+eEޝݖ0C15Mݚ@JSZ(zȏ NTa(25DD5.l<g[[Z arQQ%Buȴ~~`IohRbʳڟu2MS8EdFUClCMaѳ !}ș+2k/bųE,n当ꖛ\(8 WV8 d]b yXw ܊:I39
00 U ]^§Q\ӎ0U #0T039N0b01 0 UUS10U Florida10U Niceville10U
Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA @Ui0U 0 0U 0
*H
:P U!>vJ n io -#ן]Wyu jǑR̀Q
nƇ!G ѦF g\ yLx gw=OPycehf[ }ܷ['4ڝ\[p 6\o.B&JF" ZC{;*o*mcCcLY߾`
t*S!(` ]DHP5A~/NPp6=mhk밣'doA$86hm5ӚS@ j ެEgl
)0JG`%k35PaC?σ
׳HEt}!P㏏%*BxbQwaKG$6 h¦Mve; [o-Iی&
I,Tc ߎ#t wPA@l0P+KXBպT zGv;NcI3&J ĬUPNa?/%W6G۟N000 k#Xd\ =0
*H
0{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA0
170817212120Z
220816212120Z0W1 0 UUS10U Florida10U
Cuda Systems LLC10U karl@denninger.net0"0
*H
0
T[I-ΆϏ dn;Å@שy.us~_ZG%<MYd\gvfnsa1'6Egyjs"C [{~ _K Pn+<*pv#Q+H/7[-vqDV^U>f%GX)H.|l`M(Cr >е͇6#odc"YljҦln8@5SA0&ۖ"OGj?UDWZ5 dDB 7k-)9Izs-JAv
J 6L$Ն1SmY.Lqw*SH;EF'DĦH]MOgQQ|Mٙג2Z9y@ y]}6ٽeY9Y2xˆ$T=e CǺǵbn֛{j |@LLt1[Dk5:$= ` M 00<+00.0,+0 http://ocsp.cudasystems.net:88880 U 0 0 `HB0U 0 U %0++03 `HB
&$OpenSSL Generated Client Certificate0 U %՞V =;bzQ0U #0]^§Q\ӎϡ01 0 UUS10U Florida10U Niceville10U
Cuda Systems LLC10U Cuda Systems CA1!0 U Cuda Systems LLC 2017 CA H^Ōc!5
H0 U 0karl@denninger.net0
*H
۠A0-j%--$% g2#ޡ1^>{K+uGE v1ş7Af&b&O; .;A5* U)ND2bF|\= ]<sˋL!wrw٧> YMÄ3\mWR hSv!_zvl? 3_ xU%\^#O*Gk̍YI_&Fꊛ@&1n } ͬ:{hTP3B.;bU8:Z=^Gw8 !k-@xE@i,+'Iᐚ:f hztX7/(hY` O.1}a`%RW^akǂpCAufgDix UTЩ/7}%=jnVZvcF<M=
2^GKH5魉
_O4ެByʈySkw=5@h.0z>
W1000{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0
`He E0 *H
1 *H
0 *H
1
190325171837Z0O *H
1B@uc] w?kfWMZH i-Ɵ^IS *3R.P00l *H
1_0]0 `He*0 `He0
*H
0*H
0
*H
@0+0
*H
(0 +7100{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0 *H
10{1 0 UUS10U Florida10U
Cuda Systems LLC10U Cuda Systems CA1%0#U Cuda Systems LLC 2017 Int CA k#Xd\ =0
*H
hPÎt6;û
cFX7 YvQkMImW]@2cI7*~! -R}TrEB5&4U~ 9\f3\0WVyC"F cA2~ŋL$HY}:UutWroJ)zq|f\ƁV%,2FvH;[j<SԑǸ!êN)6Vh2dӯR'S <oq-
z_'eN0J-&7ZM"E
?UB:U4N7gRZ"hl"tğ.b@94佧k5CSVLCP_g
s~ɑ.1Vଜq( !N :hʝO6 ?] $ zŅ# =W M63(w֔eJxhQ)1bY^j)QH] ld ʈjsBM
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d19e42a8-eff5-a111-0bf4-8d4f802f95ba>