1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

RT-AC87 running as media bridge rebooting every 3-5 days.

Discussion in 'Asuswrt-Merlin' started by Piki, Jul 12, 2018.

  1. Piki

    Piki New Around Here

    Joined:
    Jul 12, 2018
    Messages:
    3
    Hi

    Im running my RT-AC87 with Merlin 384.5 as a media bridge to provide a ethernet interface to my NAS and HTPC.

    I have been running it for 3 weeks now and i did a restore to factory defaults before i configured it as a media bridge. It is running just as i want it most of the time but every 3-5 days i just reboots it. Yesterday when it happened i was home and could look through the logs where i found some things that im not really sure how to interpret.

    The first is what seems to be the actual reason for the reboot that was presented when it was starting up again:

    Code:
    Feb 14 01:00:11 kernel: _ Reboot message ... _______________________________________________________
    Feb 14 01:00:11 kernel: <0>Kernel panic - not syncing: Attempted to killᅰ˴!
    Feb 14 01:00:11 kernel: <4>[<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c02cc4d8>] (panic+0x7c/0x1a8)
    Feb 14 01:00:11 kernel: <4>[<c02cc4d8>] (panic+0x7c/0x1a8) from [<c0065660>] (do_exit+0x5cc/0x674)
    Feb 14 01:00:11 kernel: <4>[<c0065660>] (do_exit+0x5cc/0x674) from [<c0065964>] (do_group_exit+0x3c/0xbc)
    Feb 14 01:00:11 kernel: <4>[<c0065964>] (do_group_exit+0x3c/0xbc) from [<c00701ac>] (get_signal_to_deliver+0x28c/0x3d4)
    Feb 14 01:00:11 kernel: <4>[<c00701ac>] (get_signal_to_deliver+0x28c/0x3d4) from [<c0040448>] (do_signal+0x54/0x5cc)
    Feb 14 01:00:11 kernel: <4>[<c0040448>] (do_signal+0x54/0x5cc) from [<c0040ef4>] (do_notify_resume+0x50/0x5c)
    Feb 14 01:00:11 kernel: <4>[<c0040ef4>] (do_notify_r>] (work_pending+0x24/0x28)
    Feb 14 01:00:11 kernel: <2>Cnwind_backtrace+0x0/0xf8) from [<c003d334>] (do_IPI+0x114/0x154)x154) from [<c0387a88>] (__irq_s(0xcf955da8 to 0xcf955df0)
    Feb 14 01:00:11 kernel: <4>5d00 00000000
    Feb 14 01:00:11 kernel: <4>5dc0: 00000000 d08b0000 cf955e24 00000003 c03e61b ffffffff
    Feb 14 01:00:11 kernel: <4>[<c0387a88>] (__irq5530>] (hndnand_read+0x20/0x28) <c019adb4>] (part_read+0x64/0xe8+0x204/0x294) from [<c007a6fc>]
    Feb 14 01:00:11 kernel: ____________________________________________________________________________
    
    While looking through the logs i also saw the following lines every 5 minutes. At first i thought it had something to do with renewed DHCP lease but that is set to 24 hours so it seems to be too often for that.

    Code:
    Jul 12 16:14:03 rc_service: udhcpc_lan 4675:notify_rc start_dnsmasq
    Jul 12 16:14:03 LAN_network_changes_(%s/%s_-->_%: 192.168.88.151
    Jul 12 16:14:03 rc_service: udhcpc_lan 4675:notify_rc stop_samba
    Jul 12 16:14:03 rc_service: udhcpc_lan 4675:notify_rc start_samba
    Jul 12 16:14:03 rc_service: waitting "stop_samba" via udhcpc_lan ...
    Jul 12 16:14:04 Samba_Server: smb daemon is stopped
    Jul 12 16:14:04 kernel: gro disabled
    Jul 12 16:19:03 rc_service: udhcpc_lan 4912:notify_rc start_dnsmasq
    Jul 12 16:19:03 LAN_network_changes_(%s/%s_-->_%: 192.168.88.151
    Jul 12 16:19:03 rc_service: udhcpc_lan 4912:notify_rc stop_samba
    Jul 12 16:19:03 rc_service: udhcpc_lan 4912:notify_rc start_samba
    Jul 12 16:19:03 rc_service: waitting "stop_samba" via udhcpc_lan ...
    Jul 12 16:19:04 Samba_Server: smb daemon is stopped
    Jul 12 16:19:04 kernel: gro disabled
    Anyone that have any idea what the crash log is telling me or what the reason for the crashing is?
     
  2. kfp

    kfp Very Senior Member

    Joined:
    Jun 26, 2014
    Messages:
    707
    First log is not complete so hard to tell what is causing the kernel panic, my guess is the wireless driver.

    As for second log, I don’t think it is what’s causing the crash/reboot, but other face of the same coin where MB cannot get a DHCP IP from main router (because wireless is dead?).
     
    Piki likes this.
  3. Piki

    Piki New Around Here

    Joined:
    Jul 12, 2018
    Messages:
    3
    Thanks for your comments.

    I attached the log that i saved when it occured yesterday if there might be anything else in there that could give a clue.

    I should also say that i dont notice anything strange about about it while im using any devices connected to it-. Im streaming netflix to my HTPC through ot and that works flawlessly. Also i have been using it as an AP for over a year with the only reeboots when i i updated to a new firmware.
     

    Attached Files:

  4. kfp

    kfp Very Senior Member

    Joined:
    Jun 26, 2014
    Messages:
    707
    Ah. The kernel panic messages are actually part of the boot up process (not actually when it happened). Looking closer it seems like it crashed at hndnand_read, I’m not familiar with this. (Looks like platform specific code to read from flash?)

    As for the DHCP entries, it’s weird that it has always been there. Are you setting the IP of the MB statically?
     
  5. Piki

    Piki New Around Here

    Joined:
    Jul 12, 2018
    Messages:
    3
    Im getting a dynamic IP through DHCP. Unfortunately im not in control of the that part of the network so i havent tried setting a static IP.
     
  6. kfp

    kfp Very Senior Member

    Joined:
    Jun 26, 2014
    Messages:
    707
    Wild guess, the DHCP response you’re getting contains options that the MB doesn’t understand (but can still set the IP before it dies?)

    The watchdog then restarts it every five minutes (and crashes again).