7590 in bootloop: I can recover it with the avm program, but still bootloop.

[PeterPawn]

Step by step - what's the trigger of the watchdog? It's useless to look for a problem with that patch, if the reason is another one (even if it's rather improbable).

EDIT: And if the "Remove telephony" patch isn't supported for your model (which I'm not sure of), you still can try to apply the needed changes manually - but that's a subject for later.

 

[saronno]

I tried to "cat /dev/debug" after the watchdog trigger

[ 25.796455] sysrq: Loglevel set to 4
[ 25.804885]
[ 25.804885] [avm_debug] redirecting kernel-messages (/dev/debug)



BusyBox v1.36.1 (2023-10-07 20:10:29 CEST) built-in shell (ash)

root@fritz:~# cat /dev/debug
[ 26.107441][2][piglet]slow: dect_loader-bootmode
[ 28.959156][1][piglet]slow: dect_loader-bootmode
[ 33.802920][1]set_reboot_status: NMI-Watchdog-Reset(NMI) - NMI(1)SUM(1)UP(33)UTC(33)FW(07.57)HW(226)HWS(4)BV(1.3258)BN(107893)FS(07.57)BT(1)BD(0)
[ 33.814614][0]stop_cpu_hook cpu0 - stopped status=1100fc00
[ 33.814622][2]stop_cpu_hook cpu2 - stopped status=1100fc00
[ 33.814627][3]stop_cpu_hook cpu3 - stopped status=1100fc00

PS: Trying to upload the firmware I notice that now, it actually doesn't seem to write the new one ...
this is happening now that I am trying to do the editing of the firmware modding fwmod before the packing step begins.
Could the removal of some files (s11-piglet for example) of the modified filesystem, triggering miscalculation in size of the filesystem image or something like that?

[    5.471753] 0100           30000 ram0 [    5.475355]  (driver?)
[    5.477761] 1f00            8192 mtdblock0 [    5.481654]  (driver?)
[    5.483976] 1f01            1024 mtdblock1 [    5.488006]  (driver?)
[    5.490417] 1f02            4096 mtdblock2 [    5.494325]  (driver?)
[    5.496666] 1f03            8192 mtdblock3 [    5.500655]  (driver?)
[    5.502987] 1f04          502784 mtdblock4 [    5.506989]  (driver?)
[    5.509341] 1f05           45108 mtdblock5 [    5.513327]  (driver?)
[    5.515660] 1f06           45108 mtdblock6 [    5.519665]  (driver?)
[    5.522014] 1f07            2268 mtdblock7 [    5.526002]  (driver?)
[    5.528334] 1f08          391356 mtdblock8 [    5.532338]  (driver?)
[    5.534684] No filesystem could mount root, tried: [    5.539373]  ext3
[    5.541282]  ext2[    5.543000]  ext4
[    5.544926]  squashfs[    5.546993]  antfs
[    5.549007]  fuseblk[    5.550986]
[    5.552469] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,6)