Panic(?) on 380.59 RTAC88U

PabloAbonia

Regular Contributor
I got the following in my log while I was away, and have never seen something like this before. Unexpected reboot, as no shutdown messages seem apparent.

Upon reboot I saw the messages copied below and I wondering about the following possibilities:
Problem with IGMP snooper(?), bad USB key (?), bad router(?), bad router memory(?), router attack(?), firmware bug(?), and (?).

There had also been a jffs error a week or two before, occurring within the space of the two parts of this log. I also found several versions of my router showing up repeatedly as a DLNA server on my Windows 10 machine. A RTAC68U running as an AP, which while also appearing repetitively as a DLNA server, does not manifest the odd log abnormalities seen for my main router.

The only other thing of potential relevance is that AI Protection (with the email alerts) was on and I don't clearly recall having turned it on. As my network was behaving a little funky, I looked at the log and saw send mail alerts which I have never seen before. This led to a little more checking and this post.

Which possibility would you regard as most likely and how would you proceed?

Pablo

20:00:18 kernel: [dump prev ops] from 80000000, local len(11161)
Jul 31 20:00:18 kernel: _ Reboot message ... _______________________________________________________
Jul 31 20:00:18 kernel: <4>Emergency Sync complete
Jul 31 20:00:18 kernel: <6>mod epilog takes 0��U�fies
Jul 31 20:00:18 kernel: <6>IDPfw: Exit IDPfw
Jul 31 20:00:18 kernel: <4>Stop the IPS/AppID engine...
Jul 31 20:00:19 kernel: <6>IDPfw: Exit chrdev /dev/idpfw with major 191
Jul 31 20:00:19 kernel: <7>[udb_exit:959] Free udb at 99f52000
Jul 31 20:00:19 kernel: <7>[udb_exit:960] Free app at a2f9e000
Jul 31 20:00:19 kernel: <7>[udb_exit:961] Free patrol table at a366b000
Jul 31 20:00:19 kernel: <4>
Jul 31 20:00:19 kernel: <4>gro disabled
Jul 31 20:00:19 kernel: <6>device eth0 left promiscuous mode
Jul 31 20:00:19 kernel: <6>br0: port 1(vlan1) entering forwarding state
Jul 31 20:00:19 kernel: <6>device eth0 entered promiscuous mode
Jul 31 20:00:19 kernel: <6>br0: topology change detected, propagating
Jul 31 20:00:19 kernel: <6>br0: port 1(vlan1) entering forwarding state
Jul 31 20:00:19 kernel: <6>br0: port 1(vlan1) entering forwarding state
Jul 31 20:00:19 kernel: <6>br0: port 3(wl0.1) entering forwarding state
Jul 31 20:00:19 kernel: <6>br0: port 2(eth1) entering forwarding state

Followed moments later by:

Jul 31 20:00:19 kernel: <6>device fwd1 left promiscuous mode
Jul 31 20:00:19 kernel: <6>device eth0 left promiscuous mode
Jul 31 20:00:19 kernel: <6>device vlan1 left promiscuous mode
Jul 31 20:00:19 kernel: <6>br0: port 1(vlan1) entering disabled state
Jul 31 20:00:19 kernel: <6>device eth1 left promiscuous mode
Jul 31 20:00:19 kernel: <6>br0: port 2(eth1) entering disabled state
Jul 31 20:00:19 kernel: <6>device wl0.1 left promiscuous mode
Jul 31 20:00:19 kernel: <6>br0: port 3(wl0.1) entering disabled state
Jul 31 20:00:19 kernel: <4>EMF_ERROR: Hooks already unregistered
Jul 31 20:00:19 kernel: <4>EMF_ERROR: Hooks already unregistered
Jul 31 20:00:19 kernel: <4>EMF_ERROR: Interface br0 doesn't exist
Jul 31 20:00:19 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:17c terminated OK
Jul 31 20:00:19 kernel: <4>EMF_ERROR: Interface br0 doesn't exist
Jul 31 20:00:19 kernel: <4>dhd_detach(): thread:dhd_watchdog_thread:178 terminated OK
Jul 31 20:00:19 kernel: <4>EMF_ERROR: Interface br0 doesn't exist
Jul 31 20:00:19 kernel: <4>mm/memory.c:216: bad pmd 4001140e.
Jul 31 20:00:19 kernel: <4>mm/memory.c:216: bad pmd 4021140e.
Jul 31 20:00:19 kernel: <4>mm/memory.c:216: bad pmd 4041140e.
Jul 31 20:00:19 kernel: <4>mm/memory.c:216: bad pmd 4061140e.
Jul 31 20:00:19 kernel: <4>mm/memory.c:216: bad pmd 4081140e.
Jul 31 20:00:19 kernel: <4>mm/memory.c:216: bad pmd 40a1140e.
 
Last edited:

Similar threads

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