What's new

AC66U B1 random reboot for unknown reason.

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RT-AC66U B1, HW version B2, using merlin 386.3_2 firmware.
Symptom: random reboot, sometime around 20 ~ 40 minutes, sometime right after the router completes boot (I assume the power led slow blink few times means power up complete).

Previous version 386 firmwares also has this problem, however version 384 works fine.
The router is upgraded from 384.19 from WebUI, after upgrade a factory reset was done by holding WPS button while powering up. Also tried upgrade using recovery mode, still has this problem.

This time I managed to capture some log, I see these alert messages but I have no idea if they are related to the reboot. Link to the syslog file is HERE. And HERE.
(the following 3 lines are not in the above log file)
Code:
192.168.5.1    Aug 11 17:24:47    RT-AC66U_B1-0C10-95E2992-C    kern    alert    kernel    Unable to handle kernel NULL pointer dereference at virtual address 00000000
192.168.5.1    Aug 11 17:24:47    RT-AC66U_B1-0C10-95E2992-C    kern    alert    kernel    pgd = c0004000
192.168.5.1    Aug 11 17:24:47    RT-AC66U_B1-0C10-95E2992-C    kern    alert    kernel    [00000000] *pgd=00000000

If any more details needed please let me know, thanks! (the router rebooted itself once again while I write this post :( )
 

heysoundude

Part of the Furniture
Why specifically are you trying to run the latest firmware on it if there is an older version that works without this problem?
If you want something from the latest firmware, maybe it might be best if you upgrade the hardware it was meant to run on?

Someone who knows how to read the logs and determine what they mean will probably be able to help you decipher and fix the error, or it may be that it's simply time to upgrade.
Maybe this helps: https://www.snbforums.com/threads/ax86u-249-amazon.74179/
 
The router reboots right after these logs captured. Can anyone have a look please?

Code:
192.168.5.1    Aug 11 23:09:48    RT-AC66U_B1-0C10-95E2992-C    kern    alert    kernel    Unable to handle kernel NULL pointer dereference at virtual address 00000000
192.168.5.1    Aug 11 23:09:48    RT-AC66U_B1-0C10-95E2992-C    kern    alert    kernel    pgd = cdb78000
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    alert    kernel    [00000000] *pgd=9db81031, *pte=00000000, *ppte=00000000
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    emerg    kernel    Internal error: Oops: 17 [#1] PREEMPT SMP
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    emerg    kernel    last sysfs file: /sys/class/net/vlan1/brport/port_no
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    PC is at set_skb_tuples+0x354/0x438 [tdts_udbfw]
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    LR is at set_skb_tuples+0x124/0x438 [tdts_udbfw]
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    pc : [<bf4f6d6c>]    lr : [<bf4f6b3c>]    psr: 20000113
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    sp : cdaa9a30  ip : 00000000  fp : cdaa9a68
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    r10: cdaa9a6e  r9 : cea11270  r8 : cdaa9a7e
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    r7 : 00000006  r6 : cea111e0  r5 : cda2fa80  r4 : cdaa9a68
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    r3 : 00000050  r2 : 00000000  r1 : 00001950  r0 : 00000000
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    Control: 10c53c7d  Table: 9db7804a  DAC: 00000015
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    emerg    kernel    Process dnsmasq (pid: 855, stack limit = 0xcdaa8270)
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  tdts_udbfw  bf4f6000  25852
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  tdts_udb  bf46a000  180812
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  tdts  bf7af000  417034
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_nat_sip  bf7a8000  5031
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_conntrack_sip  bf79f000  15713
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_nat_h323  bf798000  4761
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_conntrack_h323  bf78a000  33807
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_nat_rtsp  bf784000  3202
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_conntrack_rtsp  bf77e000  4067
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_nat_ftp  bf778000  1144
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  nf_conntrack_ftp  bf771000  4909
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  ip6table_mangle  bf76b000  934
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  sr_mod  bf763000  10842
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  cdrom  bf756000  30901
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  xt_length  bf750000  769
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  ip6t_ROUTE  bf74a000  2954
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  ip6t_REJECT  bf744000  2172
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  thfsplus  bf727000  84702
192.168.5.1    Aug 11 23:09:49    RT-AC66U_B1-0C10-95E2992-C    kern    warning    kernel    module:  tntfs  bf6a0000  493645
 
The router just rebooted once again, this time looks like it gives a very detailed syslog? Not everytime it outputs this much log, sometime it just reboots without any log.
Link to the log file is HERE. (not the full log, I cut the log file from the first kernel alert message.)
 
The router just rebooted once again, this time looks like it gives a very detailed syslog? Not everytime it outputs this much log, sometime it just reboots without any log.
Link to the log file is HERE. (not the full log, I cut the log file from the first kernel alert message.)
Seems you use Trend Micro try to turn if off and test if reboot persists.
 
I'd also suggest that you turn off all custom scripts to see if one of those is causing the problem.

Post the complete log file from the router itself rather than a partial log from your remote syslog server.
 
Seems you use Trend Micro try to turn if off and test if reboot persists.
Yes I do turned on Trend Micro features, I think that will make my router and home network safer ...? Anyway thanks for the suggestion, will try this!
 
I'd also suggest that you turn off all custom scripts to see if one of those is causing the problem.

Post the complete log file from the router itself rather than a partial log from your remote syslog server.

Thanks for the reply, I just formatted jffs partition, will see if reboot still persists.
Btw, those scripts works fine with 384.19 firmware, will they cause issues in 386 firmwares?

Post the complete log file from the router itself rather than a partial log from your remote syslog server.

I thought log is cleared after reboot so I setup a syslog server, will check it next time.
 
Last edited:
Looks like one or more of my custom script and config file on the jffs partition causing this issue, now I'm restoring them one by one trying to find which file has problem.
 
The router started reboot randomly again, I was able to save the syslog from router webui, please take a look.
I assume my custom firewall-start script casuing this, the script is attached below. This script file is the only one I created, all other scripts were created by amtm.

Edit: Unable to attach the log file, posted on this Gist instead.
 

Attachments

  • firewall-start.txt
    345 bytes · Views: 101
Last edited:

Sign Up For SNBForums Daily Digest

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