00:14
ndufresne3 has joined #linux-amlogic
00:15
Stricted has joined #linux-amlogic
00:16
ndufresne has quit [Ping timeout: 252 seconds]
00:16
ndufresne3 is now known as ndufresne
00:21
GNUtoo has joined #linux-amlogic
00:21
GNUtoo has quit [Ping timeout: 240 seconds]
01:22
vagrantc has quit [Quit: leaving]
01:45
<
steev >
Tested-by is also helpful for kernel development
02:30
GNUtoo has quit [Remote host closed the connection]
02:30
GNUtoo has joined #linux-amlogic
03:42
buzzmarshall has quit [Quit: Konversation terminated!]
04:16
_9A3LI has joined #linux-amlogic
04:17
_9A3LI1 has quit [Ping timeout: 260 seconds]
05:38
Consolatis has joined #linux-amlogic
05:38
Consolatis has quit [Killed (erbium.libera.chat (Nickname regained by services))]
06:30
tolszak has joined #linux-amlogic
06:48
anessen976 has joined #linux-amlogic
07:24
tdebrouw has joined #linux-amlogic
08:37
<
narmstrong >
adema: anything is important, reporting is as important as fixing the bugs
11:21
Terry1373229 has quit [Quit: Ping timeout (120 seconds)]
11:22
Terry1373229 has joined #linux-amlogic
13:21
<
tdebrouw >
On my a311d board, I sometimes get a "Kernel panic - not syncing: Asynchronous SError Interrupt"
13:21
<
tdebrouw >
I have it with a buildroot rootfs
13:21
<
tdebrouw >
I have it with an ubuntu rootfs
13:22
<
tdebrouw >
It's really uncommon
13:22
<
tdebrouw >
It can take days to get it
13:23
<
tdebrouw >
Sometimes I'm running stress-ng, other times I'm not doing anything with it
13:23
<
tdebrouw >
I'm not sure what is causing it
13:26
<
tdebrouw >
pastebin above: a regular ubuntu - not running any programs
13:27
<
tdebrouw >
this one: stress-ng was just killed with ctrl-c
13:27
<
tdebrouw >
I currently don
13:28
<
tdebrouw >
*I currently don't know where to start looking
13:28
<
tdebrouw >
I thought it was a temperature issue, but that doesn't seem to be the case.
13:28
<
tdebrouw >
any idea?
13:29
<
tdebrouw >
any pointers?
13:29
<
tdebrouw >
where should I start to look for this?
13:29
<
narmstrong >
tdebrouw: did you remove the sub GHz DVFS opps ?
13:30
<
tdebrouw >
I don't think so
13:30
<
tdebrouw >
checking
13:31
<
tdebrouw >
I didn't touch those
13:33
<
tdebrouw >
I can give that patch a try
13:34
<
narmstrong >
I was planning to push it for fixes, if it helps you I'll push it asap
13:36
<
tdebrouw >
it might take a few days before it triggers again :-/
13:36
<
tdebrouw >
but thanks for helping me once again
14:50
vagrantc has joined #linux-amlogic
15:09
tolszak has quit [Ping timeout: 250 seconds]
15:11
tolszak has joined #linux-amlogic
15:18
tolszak has quit [Ping timeout: 250 seconds]
15:32
<
adeepv >
narmstrong seems a113x has this bug too. we were forced to raise min cpu freq to 250-500mhz on jethub devices
15:40
LTanure has joined #linux-amlogic
15:41
<
LTanure >
Hi, it seems Vim3 disables VCC_5V during boot for 50ms
15:41
<
LTanure >
I am powering my device from pins 1,2 5V
15:42
<
LTanure >
but it doesnt work because my device is put in a weird state after probe because of this 5V drop during boot
15:43
<
LTanure >
If I change regulator-vcc_5v , gpio = <&gpio GPIOH_8 GPIO_OPEN_DRAIN>;
15:44
<
LTanure >
to something not GPIOH_8, like GPIOH_6 the issue doesnt happen, but also I cant see that PIN GPIOH_6 being put low
15:44
<
LTanure >
So it makes me believe isnt the kernel doing the low is something else
15:45
elastic_dog has quit [Ping timeout: 260 seconds]
15:48
elastic_dog has joined #linux-amlogic
15:53
tdebrouw has quit [Quit: Leaving.]
15:56
<
narmstrong >
LTanure: hmm, is this with mainline uboot ?
15:56
<
narmstrong >
LTanure: or from Linux >
15:58
<
narmstrong >
LTanure: try adding ` regulator-boot-on;` property in the regulator node
15:59
<
LTanure >
testing ...
16:00
<
narmstrong >
maybe it's how the GPIO open drain sequence is done
16:01
<
LTanure >
U-boot info U-Boot 2021.04-armbian (Aug 08 2021 - 15:02:06 +0200) khadas-vim3
16:06
buzzmarshall has joined #linux-amlogic
16:10
<
LTanure >
regulator-boot-on seems to keep the 5V there
16:10
<
LTanure >
but now my hw doesnt come up after boot
16:20
<
narmstrong >
hmm, howcome ? since there is no more a dropout it should work ?
16:31
<
LTanure >
dont know
16:31
<
LTanure >
I am investigating
16:32
<
LTanure >
I dont understand regulator-boot-on
16:32
<
LTanure >
is u-boot doing something?
16:55
<
LTanure >
yeah, VCC 5v remains 5v during reboot, which is good
16:55
<
LTanure >
but my hw powers off totally
17:00
LTanure has quit [Remote host closed the connection]
17:35
anessen9765 has joined #linux-amlogic
17:37
anessen976 has quit [Ping timeout: 260 seconds]
17:37
anessen9765 is now known as anessen976
18:28
tdebrouw has joined #linux-amlogic
18:49
anessen976 has quit [Ping timeout: 250 seconds]
19:18
<
_9A3LI >
Ako Florida ostane u USA, guverner bi se mogel kandidirati za POTUS a onda mnogima sjebati koncepciju, osim ako ne opadne po stepenicama i samoubije se
19:18
<
_9A3LI >
opss, wrong ch ! ;)
19:18
_9A3LI has left #linux-amlogic [#linux-amlogic]
20:22
tdebrouw has quit [Quit: Leaving.]
21:24
anessen9765 has joined #linux-amlogic
21:37
Consolatis has quit [Quit: Consolatis]
22:07
Consolatis has joined #linux-amlogic
23:03
buzzmarshall has quit [Quit: Konversation terminated!]
23:21
camus has quit [Ping timeout: 260 seconds]