Flint 4.1.0 beta crash log / long restart time

Technical Support for Routers
1

Hello!,

I noticed there was a really long delay for starting up flint like around 5 minutes.

one of those errors contained:

click here 
[    1.608172] coresight-csr 6001000.csr: CSR initialized
[    1.615830] of_graph_get_next_endpoint(): no port node found in /soc/cti@6010000
[    1.620797] of_graph_get_next_endpoint(): no port node found in /soc/cti@6011000
[    1.628350] of_graph_get_next_endpoint(): no port node found in /soc/cti@6012000
[    1.635732] of_graph_get_next_endpoint(): no port node found in /soc/cti@6013000
[    1.643101] of_graph_get_next_endpoint(): no port node found in /soc/cti@6014000
[    1.650490] of_graph_get_next_endpoint(): no port node found in /soc/cti@6015000
[    1.657870] of_graph_get_next_endpoint(): no port node found in /soc/cti@6016000
[    1.665246] of_graph_get_next_endpoint(): no port node found in /soc/cti@6017000
[    1.672618] of_graph_get_next_endpoint(): no port node found in /soc/cti@6018000
[    1.680008] of_graph_get_next_endpoint(): no port node found in /soc/cti@6019000
[    1.687386] of_graph_get_next_endpoint(): no port node found in /soc/cti@601a000
[    1.694762] of_graph_get_next_endpoint(): no port node found in /soc/cti@601b000
[    1.702136] of_graph_get_next_endpoint(): no port node found in /soc/cti@601c000
[    1.709520] of_graph_get_next_endpoint(): no port node found in /soc/cti@601d000
[    1.716908] of_graph_get_next_endpoint(): no port node found in /soc/cti@601e000
[    1.724267] of_graph_get_next_endpoint(): no port node found in /soc/cti@601f000
[    1.731645] of_graph_get_next_endpoint(): no port node found in /soc/cti@6198000
[    1.739100] of_graph_get_next_endpoint(): no port node found in /soc/cti@6199000
[    1.746469] of_graph_get_next_endpoint(): no port node found in /soc/cti@619a000
[    1.753851] of_graph_get_next_endpoint(): no port node found in /soc/cti@619b000
[    1.761267] of_graph_get_next_endpoint(): no port node found in /soc/cti@610c000
[    1.768640] sps_register_bam_device : unable to create IPC Logging 0 for bam 0x06064000
[    1.775805] sps_register_bam_device : unable to create IPC Logging 1 for bam 0x06064000sps_register_bam_device : unable to create IPC Logging 2 for bam 0x06064000
[    1.791511] sps_register_bam_device : unable to create IPC Logging 3 for bam 0x06064000sps_register_bam_device : unable to create IPC Logging 4 for bam 0x06064000
[    1.806006] sps:BAM 0x06064000 is registered.<3>[    1.812684] coresight-tmc 6048000.tmc: TMC REG dump setup failed. ret: -38
[    1.816914] coresight-tmc 6048000.tmc: TMC initialized
[    1.823714] coresight-tmc 6047000.tmc: TMC ETF-ETB dump setup failed. ret: -38
[    1.828765] coresight-tmc 6047000.tmc: TMC REG dump setup failed. ret: -38
[    1.836118] coresight-tmc 6047000.tmc: TMC initialized
[    1.843024] coresight-funnel 6041000.funnel: FUNNEL initialized
[    1.848090] coresight-funnel 6100000.funnel: FUNNEL initialized
[    1.853899] coresight-funnel 6130000.funnel: FUNNEL initialized
[    1.859807] coresight-funnel 6120000.funnel: FUNNEL initialized
[    1.865719] coresight-funnel 61a1000.funnel: FUNNEL initialized
[    1.871777] coresight-etm4x 619c000.etm: ETM REG dump setup failed. ret -38
[    1.877645] coresight-etm4x 619c000.etm: ETM 4.0 initialized
[    1.884461] coresight-etm4x 619d000.etm: ETM REG dump setup failed. ret -38
[    1.890479] coresight-etm4x 619d000.etm: ETM 4.0 initialized
[    1.897067] coresight-etm4x 619e000.etm: ETM REG dump setup failed. ret -38
[    1.903067] coresight-etm4x 619e000.etm: ETM 4.0 initialized
[    1.909675] coresight-etm4x 619f000.etm: ETM REG dump setup failed. ret -38
[    1.915673] coresight-etm4x 619f000.etm: ETM 4.0 initialized
[    1.922238] coresight-replicator-qcom 6046000.replicator: REPLICATOR 1.0 initialized
[    1.928233] coresight-stm 6002000.stm: STM initialized
[    1.936568] of_graph_get_next_endpoint(): no port node found in /soc/hwevent@6101000
[    1.940717] coresight-hwevent 6101000.hwevent: Hardware Event driver initialized

I have upgraded flint without checking the reset settings checkbox.

edit

I forgot to mentoin that I came back after I placed a backup in luci, so perhaps some parts of the log are part of the recovery maybe.

full kernel log:
kernel.zip (11.0 KB)

2

Does this happen one time or all the time?

3

I just tried it again, and it seems to happen persistent, I had my wireguard server active so I disabled this to check if it has been caused by this but it seems its not caused by the server, the wireguard client instance with mullvad is untouched along with nextdns.

I did a closer look to the behaviour on the wifi and on my pc connected on lan and I noticed this:

  1. on pc it keeps trying to identify the network and drops, chrome says network changed address but never restores connection, this look similiar to ip conflicts but I have checked if it conflicts but it does not.

  2. it takes a very long time that the wifi access point is visible (probably not loaded at that time).

  3. once when the wifi access point becomes visible after 3 minutes waiting and I connected my wireless phone, suddenly my computer gets a lan ip and ip resolution.

in the mean time the flints led becomes blue but doesn’t flicker when I can’t get ip resolution.

Could it be that the multi wan script is running even when disabled? or it chooses a wrong interface?

I’m thinking it may relates to this feature but I’m not entirely sure.

though when I went to luci->network for the first time after the upgrade it gave me the message that it tried to convert my network to the new DSA configuration which is strange because my prior firmware was already DSA converted I’m not sure what has been changed.

I have added a full log export I hope it can give some information about the long delay:
logread.zip (24.9 KB)

4

From the log, it takes 1 minutes to boot.
In two minutes, your devices connected.

So seems normal.

Do you think it crashes, i.e. it rebooted several times during boot? You can identify this by checking the LED status.

5

I believe it didn’t crash but it more looked like a boot loop though I cannot find this in the logs, the led stays for a very long time on blue.

I did a reset and made the same setup from scratch and it starts normal, I have made a backup when it was still long booting perhaps I can sent this ?

6

Pls check more. Usually a power problem.