Release Asuswrt-Merlin 386.7 is now available for all Gnuton's models too

GNUton

Senior Member
Hi there,
After a long beta cycle I would like to announce the availablity of the new stable for GNUton's model.
The images can be downloaded from here.

The models that I currently support are:
  • DSL-AC68U
  • DSL-AX82U/DSL-AX5400
  • RT-AX82U
  • TUF-AX5400
  • TUF-AX3000
  • ZenWiFi AX (X8) / RT-AX95Q
Please note this is the first stable release for TUF-AX3000. So enjoy it!
If you do not see your router supported, feel free to leave to add or upvote it to the list here.

Once again thanks to all people giving feedback to the builds and @RMerlin, Asus for all the rest and CircleCI.
Every build is just possible thanks to you all.

Cheers,
Antonio
 

CarsonL

Occasional Visitor
I have been getting disconnection on my wireless backhaul node every 12 hours. Any ideas on it?

Main router : XT12 running on AsusWRT (49723)
Node : XT8 Running on 386.07_2

Here are the logs. (Notice the time slot around 16:51 to 16:52)

Aug 9 16:05:20 miniupnpd[4059]: remove port mapping 51413 TCP because it has expired
Aug 9 16:42:37 miniupnpd[4059]: upnp_event_process_notify: connect(192.168.50.142:2869): Connection timed out
Aug 9 16:42:37 miniupnpd[4059]: upnpevents_processfds: 0xc2e210, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-04421a3861f8 after an ERROR cb: http://192.168.50.142:2869/upnp/eventing/ceiehpdqzy
Aug 9 16:42:42 miniupnpd[4059]: upnp_event_process_notify: connect(192.168.50.142:2869): Connection timed out
Aug 9 16:42:42 miniupnpd[4059]: upnpevents_processfds: 0xc2e210, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-04421a3880df after an ERROR cb: http://192.168.50.142:2869/upnp/eventing/bxmdmmilij
Aug 9 16:51:50 wlceventd: wlceventd_proc_event(530): wl1.1: Auth D4:C8:B0:5A:28:10, status: Successful (0), rssi:0
Aug 9 16:51:50 wlceventd: wlceventd_proc_event(540): wl1.1: ReAssoc D4:C8:B0:5A:28:10, status: Successful (0), rssi:-96
Aug 9 16:51:51 wlceventd: wlceventd_proc_event(511): wl1.1: Disassoc D4:C8:B0:5A:28:10, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:51:51 wlceventd: wlceventd_proc_event(494): wl1.1: Deauth_ind D4:C8:B0:5A:28:10, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 9 16:52:06 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: Disassociated due to inactivity (4), rssi:-66
Aug 9 16:52:07 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Aug 9 16:52:25 wlceventd: wlceventd_proc_event(530): wl1.1: Auth B0:3C:DC:7D:36:47, status: Successful (0), rssi:-86
Aug 9 16:52:25 wlceventd: wlceventd_proc_event(559): wl1.1: Assoc B0:3C:DC:7D:36:47, status: Successful (0), rssi:-86
Aug 9 16:52:34 wlceventd: wlceventd_proc_event(559): eth6: Assoc 7C:10:C9:56:A1:88, status: Successful (0), rssi:-68
Aug 9 16:52:38 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: 4-way handshake timeout (f), rssi:-67
Aug 9 16:52:39 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: 4-way handshake timeout (f), rssi:-67
Aug 9 16:52:41 wlceventd: wlceventd_proc_event(494): wl1.1: Deauth_ind B0:3C:DC:7D:36:47, status: 0, reason: Unspecified reason (1), rssi:0
Aug 9 16:52:41 wlceventd: wlceventd_proc_event(511): wl1.1: Disassoc B0:3C:DC:7D:36:47, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:52:44 wlceventd: wlceventd_proc_event(530): eth6: Auth 7C:10:C9:56:A1:88, status: Successful (0), rssi:0
Aug 9 16:52:44 wlceventd: wlceventd_proc_event(559): eth6: Assoc 7C:10:C9:56:A1:88, status: Successful (0), rssi:-69
Aug 9 16:52:44 kernel: wfd_registerdevice Successfully registered dev wds2.0.1 ifidx 1 wfd_idx 2
Aug 9 16:52:44 kernel: Register interface [wds2.0.1] MAC: 04:42:1a:38:5c:b8
Aug 9 16:52:48 wlceventd: wlceventd_proc_event(511): wds2.0.1: Disassoc 7C:10:C9:56:A1:88, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:52:48 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 9 16:52:48 kernel: No wdev corresponding to bssidx: 0x0 found! Ignoring event.
Aug 9 16:52:48 kernel: No wdev corresponding to bssidx: 0x0 found! Ignoring event.
Aug 9 16:52:48 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Aug 9 16:52:58 wlceventd: wlceventd_proc_event(559): eth4: Assoc 7C:10:C9:56:A1:81, status: Successful (0), rssi:-56
Aug 9 16:52:58 kernel: wfd_registerdevice Successfully registered dev wds0.0.1 ifidx 2 wfd_idx 0
Aug 9 16:52:58 kernel: Register interface [wds0.0.1] MAC: 04:42:1a:38:5c:b0
Aug 9 16:52:58 wlceventd: wlceventd_proc_event(530): eth6: Auth 7C:10:C9:56:A1:88, status: Successful (0), rssi:-69
Aug 9 16:52:58 wlceventd: wlceventd_proc_event(559): eth6: Assoc 7C:10:C9:56:A1:88, status: Successful (0), rssi:-69
Aug 9 16:52:58 kernel: wfd_registerdevice Successfully registered dev wds2.0.1 ifidx 1 wfd_idx 2
Aug 9 16:52:58 kernel: Register interface [wds2.0.1] MAC: 04:42:1a:38:5c:b8
Aug 9 16:52:59 rc_service: cfg_server 3319:notify_rc update_sta_binding
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(530): eth5: Auth 44:07:0B:95:46:AA, status: Successful (0), rssi:-93
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(559): eth5: Assoc 44:07:0B:95:46:AA, status: Successful (0), rssi:-93
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(494): eth5: Deauth_ind 44:07:0B:95:46:AA, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(511): eth5: Disassoc 44:07:0B:95:46:AA, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:53:03 wlceventd: wlceventd_proc_event(559): eth4: Assoc 58:B6:23:08:64:DF, status: Successful (0), rssi:-86
Aug 9 16:53:03 wlceventd: wlceventd_proc_event(559): eth4: Assoc 64:90:C1:7D:6F:7B, status: Successful (0), rssi:-85
Aug 9 16:53:17 wlceventd: wlceventd_proc_event(530): eth4: Auth A4:39:B3:4F:50:31, status: Successful (0), rssi:0
Aug 9 16:53:17 wlceventd: wlceventd_proc_event(559): eth4: Assoc A4:39:B3:4F:50:31, status: Successful (0), rssi:-83
Aug 9 16:53:23 rc_service: cfg_server 3319:notify_rc update_sta_binding
Aug 9 16:53:25 roamast: eth4: sta-ap-band-bind deauth [a4:39:b3:4f:50:31]
Aug 9 16:53:25 roamast: eth4: remove client [a4:39:b3:4f:50:31] from monitor list
Aug 9 16:53:25 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind A4:39:B3:4F:50:31, status: 0, reason: Previous authentication no longer valid (2), rssi:-83
Aug 9 16:53:25 roamast: eth4: sta-ap-band-bind deauth [64:90:c1:7d:6f:7b]
Aug 9 16:53:25 roamast: eth4: remove client [64:90:c1:7d:6f:7b] from monitor list
Aug 9 16:53:25 roamast: eth4: sta-ap-band-bind deauth [58:b6:23:08:64:df]
Aug 9 16:53:25 roamast: eth4: remove client [58:b6:23:08:64:df] from monitor list
Aug 9 16:53:25 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 64:90:C1:7D:6F:7B, status: 0, reason: Previous authentication no longer valid (2), rssi:-86
Aug 9 16:53:26 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind A4:39:B3:4F:50:31, status: 0, reason: Previous authentication no longer valid (2), rssi:-83
Aug 9 16:53:26 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 64:90:C1:7D:6F:7B, status: 0, reason: Previous authentication no longer valid (2), rssi:-86
Aug 9 16:53:26 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 58:B6:23:08:64:DF, status: 0, reason: Previous authentication no longer valid (2), rssi:-87
Aug 9 16:53:27 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 58:B6:23:08:64:DF, status: 0, reason: Previous authentication no longer valid (2), rssi:-87
Aug 9 17:05:20 miniupnpd[4059]: remove port mapping 51413 TCP because it has expired

Thank you.
 

kernol

Very Senior Member
I have been getting disconnection on my wireless backhaul node every 12 hours. Any ideas on it?

Main router : XT12 running on AsusWRT (49723)
Node : XT8 Running on 386.07_2

Here are the logs. (Notice the time slot around 16:51 to 16:52)

Aug 9 16:05:20 miniupnpd[4059]: remove port mapping 51413 TCP because it has expired
Aug 9 16:42:37 miniupnpd[4059]: upnp_event_process_notify: connect(192.168.50.142:2869): Connection timed out
Aug 9 16:42:37 miniupnpd[4059]: upnpevents_processfds: 0xc2e210, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-04421a3861f8 after an ERROR cb: http://192.168.50.142:2869/upnp/eventing/ceiehpdqzy
Aug 9 16:42:42 miniupnpd[4059]: upnp_event_process_notify: connect(192.168.50.142:2869): Connection timed out
Aug 9 16:42:42 miniupnpd[4059]: upnpevents_processfds: 0xc2e210, remove subscriber uuid:3ddcd1d3-2380-45f5-b069-04421a3880df after an ERROR cb: http://192.168.50.142:2869/upnp/eventing/bxmdmmilij
Aug 9 16:51:50 wlceventd: wlceventd_proc_event(530): wl1.1: Auth D4:C8:B0:5A:28:10, status: Successful (0), rssi:0
Aug 9 16:51:50 wlceventd: wlceventd_proc_event(540): wl1.1: ReAssoc D4:C8:B0:5A:28:10, status: Successful (0), rssi:-96
Aug 9 16:51:51 wlceventd: wlceventd_proc_event(511): wl1.1: Disassoc D4:C8:B0:5A:28:10, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:51:51 wlceventd: wlceventd_proc_event(494): wl1.1: Deauth_ind D4:C8:B0:5A:28:10, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 9 16:52:06 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: Disassociated due to inactivity (4), rssi:-66
Aug 9 16:52:07 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Aug 9 16:52:25 wlceventd: wlceventd_proc_event(530): wl1.1: Auth B0:3C:DC:7D:36:47, status: Successful (0), rssi:-86
Aug 9 16:52:25 wlceventd: wlceventd_proc_event(559): wl1.1: Assoc B0:3C:DC:7D:36:47, status: Successful (0), rssi:-86
Aug 9 16:52:34 wlceventd: wlceventd_proc_event(559): eth6: Assoc 7C:10:C9:56:A1:88, status: Successful (0), rssi:-68
Aug 9 16:52:38 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: 4-way handshake timeout (f), rssi:-67
Aug 9 16:52:39 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: 4-way handshake timeout (f), rssi:-67
Aug 9 16:52:41 wlceventd: wlceventd_proc_event(494): wl1.1: Deauth_ind B0:3C:DC:7D:36:47, status: 0, reason: Unspecified reason (1), rssi:0
Aug 9 16:52:41 wlceventd: wlceventd_proc_event(511): wl1.1: Disassoc B0:3C:DC:7D:36:47, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:52:44 wlceventd: wlceventd_proc_event(530): eth6: Auth 7C:10:C9:56:A1:88, status: Successful (0), rssi:0
Aug 9 16:52:44 wlceventd: wlceventd_proc_event(559): eth6: Assoc 7C:10:C9:56:A1:88, status: Successful (0), rssi:-69
Aug 9 16:52:44 kernel: wfd_registerdevice Successfully registered dev wds2.0.1 ifidx 1 wfd_idx 2
Aug 9 16:52:44 kernel: Register interface [wds2.0.1] MAC: 04:42:1a:38:5c:b8
Aug 9 16:52:48 wlceventd: wlceventd_proc_event(511): wds2.0.1: Disassoc 7C:10:C9:56:A1:88, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:52:48 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 7C:10:C9:56:A1:88, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 9 16:52:48 kernel: No wdev corresponding to bssidx: 0x0 found! Ignoring event.
Aug 9 16:52:48 kernel: No wdev corresponding to bssidx: 0x0 found! Ignoring event.
Aug 9 16:52:48 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2
Aug 9 16:52:58 wlceventd: wlceventd_proc_event(559): eth4: Assoc 7C:10:C9:56:A1:81, status: Successful (0), rssi:-56
Aug 9 16:52:58 kernel: wfd_registerdevice Successfully registered dev wds0.0.1 ifidx 2 wfd_idx 0
Aug 9 16:52:58 kernel: Register interface [wds0.0.1] MAC: 04:42:1a:38:5c:b0
Aug 9 16:52:58 wlceventd: wlceventd_proc_event(530): eth6: Auth 7C:10:C9:56:A1:88, status: Successful (0), rssi:-69
Aug 9 16:52:58 wlceventd: wlceventd_proc_event(559): eth6: Assoc 7C:10:C9:56:A1:88, status: Successful (0), rssi:-69
Aug 9 16:52:58 kernel: wfd_registerdevice Successfully registered dev wds2.0.1 ifidx 1 wfd_idx 2
Aug 9 16:52:58 kernel: Register interface [wds2.0.1] MAC: 04:42:1a:38:5c:b8
Aug 9 16:52:59 rc_service: cfg_server 3319:notify_rc update_sta_binding
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(530): eth5: Auth 44:07:0B:95:46:AA, status: Successful (0), rssi:-93
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(559): eth5: Assoc 44:07:0B:95:46:AA, status: Successful (0), rssi:-93
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(494): eth5: Deauth_ind 44:07:0B:95:46:AA, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Aug 9 16:53:02 wlceventd: wlceventd_proc_event(511): eth5: Disassoc 44:07:0B:95:46:AA, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Aug 9 16:53:03 wlceventd: wlceventd_proc_event(559): eth4: Assoc 58:B6:23:08:64:DF, status: Successful (0), rssi:-86
Aug 9 16:53:03 wlceventd: wlceventd_proc_event(559): eth4: Assoc 64:90:C1:7D:6F:7B, status: Successful (0), rssi:-85
Aug 9 16:53:17 wlceventd: wlceventd_proc_event(530): eth4: Auth A4:39:B3:4F:50:31, status: Successful (0), rssi:0
Aug 9 16:53:17 wlceventd: wlceventd_proc_event(559): eth4: Assoc A4:39:B3:4F:50:31, status: Successful (0), rssi:-83
Aug 9 16:53:23 rc_service: cfg_server 3319:notify_rc update_sta_binding
Aug 9 16:53:25 roamast: eth4: sta-ap-band-bind deauth [a4:39:b3:4f:50:31]
Aug 9 16:53:25 roamast: eth4: remove client [a4:39:b3:4f:50:31] from monitor list
Aug 9 16:53:25 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind A4:39:B3:4F:50:31, status: 0, reason: Previous authentication no longer valid (2), rssi:-83
Aug 9 16:53:25 roamast: eth4: sta-ap-band-bind deauth [64:90:c1:7d:6f:7b]
Aug 9 16:53:25 roamast: eth4: remove client [64:90:c1:7d:6f:7b] from monitor list
Aug 9 16:53:25 roamast: eth4: sta-ap-band-bind deauth [58:b6:23:08:64:df]
Aug 9 16:53:25 roamast: eth4: remove client [58:b6:23:08:64:df] from monitor list
Aug 9 16:53:25 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 64:90:C1:7D:6F:7B, status: 0, reason: Previous authentication no longer valid (2), rssi:-86
Aug 9 16:53:26 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind A4:39:B3:4F:50:31, status: 0, reason: Previous authentication no longer valid (2), rssi:-83
Aug 9 16:53:26 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 64:90:C1:7D:6F:7B, status: 0, reason: Previous authentication no longer valid (2), rssi:-86
Aug 9 16:53:26 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 58:B6:23:08:64:DF, status: 0, reason: Previous authentication no longer valid (2), rssi:-87
Aug 9 16:53:27 wlceventd: wlceventd_proc_event(494): eth4: Deauth_ind 58:B6:23:08:64:DF, status: 0, reason: Previous authentication no longer valid (2), rssi:-87
Aug 9 17:05:20 miniupnpd[4059]: remove port mapping 51413 TCP because it has expired

Thank you.
Posted in the wrong thread ??? If XT8 is your NODE - then these logs must be posted from your XT12 ... so nothing to do with @GNUton firmware.
If you search the forum for wlceventd: you will find lots of posts suggesting you chill and ignore them ;).
 

CarsonL

Occasional Visitor
Posted in the wrong thread ??? If XT8 is your NODE - then these logs must be posted from your XT12 ... so nothing to do with @GNUton firmware.
If you search the forum for wlceventd: you will find lots of posts suggesting you chill and ignore them ;).

It's making my Wireless Backhaul node to disconnect from the main router.

What I'm curious is "Aug 9 16:52:07 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2"

While devices on my other second node and the main router doesn't disconnects, it happens randomly between the nodes.
 

kernol

Very Senior Member
It's making my Wireless Backhaul node to disconnect from the main router.

What I'm curious is "Aug 9 16:52:07 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 2"

While devices on my other second node and the main router doesn't disconnects, it happens randomly between the nodes.

Intermittent interference maybe?? - but bottom line is it does not cause any actual disconnections of devices/clients.

I really don't see you getting any benefit by avid Asus stock firmware on your XT12 Main AiMesh Router [where all the controls and actions emanate from] and then running Merlin via @GNUton on your XT8 AiMesh Node [which basically renders it a dumb "access point" to the functions of the main Router].

Merlinware is available for your XT12 - so rather run same version of Merlin on both [in this case 386.7_2 ] ... or just run latest Asus Stock firmware on both.
 

Dodgydrains

Regular Contributor
I have 4x XT8's and been updating Gnuton's build manually one each of them. Is there a way to update all 4 units in one go, similar to Asus official OTA?
 

wbennett77

Regular Contributor
RT-AX82U running for 12 hours and all looks good so far.:)
 

kernol

Very Senior Member
@TrebleTA I cannot lock the thread. I am not an admin, or I am just dumb and I dunno how to do that :p:D

I am mighty impressed with your continued application in the development of code for the DSL and other models not supported by Merlin. {ThumbsUp}

Keep it up .... but do request @RMerlin to lock your old version threads so that only the latest one is available for feedback etc.
It is what he does for his own release threads.

Either that - or perhaps ask him to bestow on you sufficient admin privileges to enable you to do it yourself.
Best to send him a pm with links to the threads that need to be locked down - so that his busy schedule is not unduly disturbed.
 

RMerlin

Asuswrt-Merlin dev
Keep it up .... but do request @RMerlin to lock your old version threads so that only the latest one is available for feedback etc.
It is what he does for his own release threads.
I did it earlier today when GNuton said he couldn`t lock it (which I interpreted as "I want to lock it" :) )
 

Shams7861

New Around Here
Hi All,

two quick questions, i have a 2 xt8's in aimesh mode with wired backhall.

is it possible or any way to force certain clients like IOT devices like smart lights onto the 2.4ghz network with asuswrt ?

I have most of most my IOT on the guest network but alot of my smart lights loose access when enable triband smart connect.

ive looked through and tried to find a definitive answer as this has been asked a million times. does the custom firmware void warranty, im from the uk. from reading it shouldnt but in the rare case i somehow brick my xt8s can i still reflash the og firmware or is there any hardware checkers like on android phones which detect custom firmware etc.

[Reposting as it was in the old/wrong thread]

thanks for your time.

Report
 

TrebleTA

Senior Member
And in that thread I said yes there was by putting them on a guest network or putting the mac address in the wifi 5ghz block list.
20220812_192855.jpg
 

patsio

Occasional Visitor
Hi,
Today, i upgraded to 386.7 (AC68U). I see the following entries to my log
Code:
Aug 13 17:18:44 kernel: lighttpd/4464: potentially unexpected fatal signal 11.
Aug 13 17:18:44 kernel: Pid: 4464, comm:             lighttpd
Aug 13 17:18:44 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Aug 13 17:18:44 kernel: PC is at 0x40c35b04
Aug 13 17:18:44 kernel: LR is at 0x402115b0
Aug 13 17:18:44 kernel: pc : [<40c35b04>]    lr : [<402115b0>]    psr: 20000010
Aug 13 17:18:44 kernel: sp : bee71038  ip : 4021ddd4  fp : 000009e0
Aug 13 17:18:44 kernel: r10: 00000058  r9 : 40c56180  r8 : 0744e2c8
Aug 13 17:18:44 kernel: r7 : 40c561b4  r6 : 00223578  r5 : 40c504f8  r4 : 00000049
Aug 13 17:18:44 kernel: r3 : 002235c0  r2 : 0744e2c9  r1 : 00223578  r0 : 40c5619c
Aug 13 17:18:44 kernel: Flags: nzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 13 17:18:44 kernel: Control: 10c53c7d  Table: 9cc6404a  DAC: 00000015
Aug 13 19:27:49 kernel: lighttpd/15525: potentially unexpected fatal signal 11.
Aug 13 19:27:49 kernel: Pid: 15525, comm:             lighttpd
Aug 13 19:27:49 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Aug 13 19:27:49 kernel: PC is at 0x40be0b04
Aug 13 19:27:49 kernel: LR is at 0x404ff5b0
Aug 13 19:27:49 kernel: pc : [<40be0b04>]    lr : [<404ff5b0>]    psr: 20000010
Aug 13 19:27:49 kernel: sp : bed99038  ip : 4050bdd4  fp : 000009e0
Aug 13 19:27:49 kernel: r10: 00000058  r9 : 40c01180  r8 : 0744e2c8
Aug 13 19:27:49 kernel: r7 : 40c011b4  r6 : 00222ff8  r5 : 40bfb4f8  r4 : 00000049
Aug 13 19:27:49 kernel: r3 : 00223040  r2 : 0744e2c9  r1 : 00222ff8  r0 : 40c0119c
Aug 13 19:27:49 kernel: Flags: nzCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Aug 13 19:27:49 kernel: Control: 10c53c7d  Table: 9cc6404a  DAC: 00000015
Aug 13 20:17:01 kernel: nvram: c

First time i see this "lighttpd/15525: potentially unexpected fatal signal 11"
By the way, i don't use any JFFS custom scripts and configs.
Any ideas pls?!
 

L&LD

Part of the Furniture
You can choose to ignore these informational logs.
 

RMerlin

Asuswrt-Merlin dev
You can choose to ignore these informational logs.
These actually indicate that lighttpd (the AiCloud web server) has crashed, so it probably needs to be investigated by @GNUton .
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top