Asuswrt-Merlin 384.8 is now available

[Stevens243]

Just got a kernel error on my 86U running 384.8
Just logged in, and clicked on System Log tab.

Dec  7 10:41:48 kernel: pgd = ffffffc0153e8000
Dec  7 10:41:48 kernel: [0074c074] *pgd=0000000014802003, *pud=0000000014802003, *pmd=000000001489f003, *pte=0000000000000000
Dec  7 10:41:48 kernel: CPU: 0 PID: 769 Comm: httpd Tainted: P           O    4.1.27 #2
Dec  7 10:41:48 kernel: Hardware name: Broadcom-v8A (DT)
Dec  7 10:41:48 kernel: task: ffffffc01e032bc0 ti: ffffffc0153f8000 task.ti: ffffffc0153f8000
Dec  7 10:41:48 kernel: PC is at 0xf6db1aa0
Dec  7 10:41:48 kernel: LR is at 0x26cd4
Dec  7 10:41:48 kernel: pc : [<00000000f6db1aa0>] lr : [<0000000000026cd4>] pstate: 20000010
Dec  7 10:41:48 kernel: sp : 00000000ffc9cab8
Dec  7 10:41:48 kernel: x12: 000000000008c71c
Dec  7 10:41:48 kernel: x11: 00000000000791e0 x10: 0000000000000001
Dec  7 10:41:48 kernel: x9 : 0000000000738150 x8 : 0000000000000000
Dec  7 10:41:48 kernel: x7 : 0000000000736290 x6 : 0000000000712ca0
Dec  7 10:41:48 kernel: x5 : 000000000074c068 x4 : 000000000074c068
Dec  7 10:41:48 kernel: x3 : 00000000ffffffff x2 : 00000000f6c5d7a8
Dec  7 10:41:48 kernel: x1 : 0000000000000000 x0 : 000000000074c068
Dec  7 10:42:01 watchdog: restart httpd
Dec  7 10:42:01 rc_service: watchdog 779:notify_rc stop_httpd
Dec  7 10:42:01 rc_service: watchdog 779:notify_rc start_httpd
Dec  7 10:42:01 RT-AC86U: start httpd:80

You are the 3rd person to report this. Mine is a page back and old man reported on page 6...

 

[Julio]

https://r.tapatalk.com/shareLink?ur...hare_tid=1385261&share_fid=16103&share_type=t


There is the whole process of flashing the router, as I said before I updated firmware and now does not leave change it, trying to cob several versions without effect, leave it with factory values and nothing, someone can help me from now thanks

Enviado desde mi BLA-L09 mediante Tapatalk

 

[octopus]

https://r.tapatalk.com/shareLink?url=http://www.chw.net/foro/showthread.php?t=1385261&share_tid=1385261&share_fid=16103&share_type=t


There is the whole process of flashing the router, as I said before I updated firmware and now does not leave change it, trying to cob several versions without effect, leave it with factory values and nothing, someone can help me from now thanks

Enviado desde mi BLA-L09 mediante Tapatalk

IF it is a TM-AC1900 converted router you cant upgrade any more.

 

[Striker317]

Did you read the link?

likely doesn't want to believe that they are out of luck. sorry, too bad.

 

[jrmtz85]

Had some issues with my upgrade, but everything seems fine now.
Background:
Asus 86U. Was on 384.7.2 and now 3.84.8.
Running AI protection suite, QOS and traffic analyzer on.
About a month ago I finally installed AMTM and Diversion. Everything was fine and then 2 weeks ago I did Skynet. All good.

So, before the update, I turned off the router, and removed the USB drive. Booted up and upgrade went fine.
Once I was back in, I noticed the CPU/RAM trackers had stopped moving after about 20 seconds. I clicked on another tab, and it asked me to sign in to the router again. Same thing kept happening. Unplugged again, cleared browser cache and cookies, an rebooted router. Same thing kept happening. Router seemed to work since network stayed up, but management interface was borked.

Unplugged again, and put USB drive back in to get the scripts running again. Everything seems fine now. Been running for hours without issues.

Also, unrelated to this issue, I'd noticed that since my Diversion/Skynet install, CPUs were always hovering at 50%ish, even when network was idle. Since the upgrade, down to little to no CPU when idle. Not sure what was going on here.

 

[dave14305]

So, before the update, I turned off the router, and removed the USB drive. Booted up and upgrade went fine.
Once I was back in, I noticed the CPU/RAM trackers had stopped moving after about 20 seconds. I clicked on another tab, and it asked me to sign in to the router again. Same thing kept happening. Unplugged again, cleared browser cache and cookies, an rebooted router. Same thing kept happening. Router seemed to work since network stayed up, but management interface was borked.

It sounds like httpd might have been crashing. It's been mentioned in earlier posts as a common problem.

 

[Centrifuge]

You are the 3rd person to report this. Mine is a page back and old man reported on page 6...

That's happening on stock 384.45149 86U FW also.

 

[akb]

Has anyone noticed any issues with IPsec server? I tried everything including factory reset and upgrade, and no matter what IPsec stops working after a few hours requiring a reboot of the router. No logs what so ever as I enabled a remote syslog server.

 

[unsynaps]

dnsmasq failed to start after update. Seems it is choking on some settings for PXE menus that worked in the last version.

Commented them out and will dig into what changed with dnsmasq.

 

[john9527]

dnsmasq failed to start after update. Seems it is choking on some settings for PXE menus that worked in the last version.

Commented them out and will dig into what changed with dnsmasq.

Known problem with fix for next release....
https://www.snbforums.com/threads/asuswrt-merlin-384-8-is-now-available.50189/page-9#post-447744

 

[DroidST]

Experienced an issue on 2.4GHz this morning. I have a temperature monitoring system with 4 sensors for our Coach which is parked next to our house (need to keep an eye when <freezing temps outside). It connects whenever a sensor reports a change (minimum one minute between) or approx every 3-5 minutes (if no change reported by the sensor) on the 2.4GHz band, then it disconnects. I use an app on my Samsung S7 for status and getting alerts. This is how I noticed the issue so quickly, around 9:20am.

Around 9am this morning I saw an update (there have been regular updates 24/7 since updating the 86U to the initial Beta2 and putting it into service) but after that, there were no updates. I had to leave for errands (4-5 hours). When I got back home, I tried to connect to the 2.4GHz band on my S7. It would not connect. I tried 2 laptops at 2.4GHz, could not connect. These clients normally connect on 5GHz and any other client that supports that band.

I copied the General Log and saved it. Didn't see anything special though unfortunately I have 'more urgent than debug selected currently'.

It seemed a wifi laser printer was connected on 2.4GHz still according to the wireless log but I didn't test it.

I power cycled the 86U and all back to normal.

The only change I made yesterday afternoon was to change QOS Type to fq_codel (from sfq) and then I rebooted the router.

I'll keep an eye one this, if it happens again, I'll set General Log to All though I am not sure that will help.

 

[Easy Limits]

Just updated to 384.8 on a 86U.

Anyone else having a problem with rebooting via the GUI? I had to use the power button several times after reboot failure when using the reboot button in the GUI. My 86U LED's on the front would go dark and it would be unresponsive.

 

[Gitsum]

Just updated to 384.8 on a 86U.

Anyone else having a problem with rebooting via the GUI? I had to use the power button several times after reboot failure when using the reboot button in the GUI. My 86U LED's on the front would go dark and it would be unresponsive.

Happened to me before also. Same router.

 

[scjr]

Just updated to 384.8 on a 86U.

Anyone else having a problem with rebooting via the GUI? I had to use the power button several times after reboot failure when using the reboot button in the GUI. My 86U LED's on the front would go dark and it would be unresponsive.

Is this the reboot behavior where the countdown timer hangs and it eventually refreshes to the login page? If so, it has happened here. @skeal gave me a tip to prevent this. Reboot from the “System Log” page. I haven’t experienced the hanging issue since.

 

[skeal]

Attempted an update to my RT-AC68U from 384.5 to 384.8 and my router reset itself to factory and after a reboot it stayed at version 384.5. Not reading any documentation I thought maybe this was a step up update, i then tried the 384.7_2 update and the same thing happened. Not to worried, just odd as this is behavior i have never had before from this router.

Is this really a TM-AC1900?

 

[Striker317]

Attempted an update to my RT-AC68U from 384.5 to 384.8 and my router reset itself to factory and after a reboot it stayed at version 384.5. Not reading any documentation I thought maybe this was a step up update, i then tried the 384.7_2 update and the same thing happened. Not to worried, just odd as this is behavior i have never had before from this router.

https://www.snbforums.com/threads/the-tm-ac1900-is-not-supported.48056/

 

[Julio]

[QUOTE = "DOspital, post: 448419, miembro: 58763"] Intenté una actualización de mi RT-AC68U de 384.5 a 384.8 y mi enrutador se restableció a la fábrica y, después de reiniciar, se mantuvo en la versión 384.5. Sin leer ninguna documentación, pensé que tal vez se trataba de una actualización progresiva, luego probé la actualización 384.7_2 y sucedió lo mismo. No estoy preocupado, solo es extraño ya que este es un comportamiento que nunca he tenido antes desde este enrutador. [/ QUOTE]

El mismo problema que tengo, funciona sin problemas, pero solo estoy en 384.5 sin poder actualizar a la próxima versión.

 

[octopus]

[QUOTE = "DOspital, post: 448419, miembro: 58763"] Intenté una actualización de mi RT-AC68U de 384.5 a 384.8 y mi enrutador se restableció a la fábrica y, después de reiniciar, se mantuvo en la versión 384.5. Sin leer ninguna documentación, pensé que tal vez se trataba de una actualización progresiva, luego probé la actualización 384.7_2 y sucedió lo mismo. No estoy preocupado, solo es extraño ya que este es un comportamiento que nunca he tenido antes desde este enrutador. [/ QUOTE]

El mismo problema que tengo, funciona sin problemas, pero solo estoy en 384.5 sin poder actualizar a la próxima versión.

English please

 

[Julio]

English please

I tried an update of my RT-AC68U from 384.5 to 384.8 and my router was reset to the factory and, after rebooting, it remains in version 384.5. However, there is no documentation, I thought maybe it is a progressive update, then I tried update 384.7_2 and the same thing happened. I'm not worried, it's just weird since this is behavior that has never been before this router. [/ APPOINTMENT]

The same problem that I have, works without problems, but I'm only in 384.5 without being able to update the next version



Enviado desde mi BLA-L09 mediante Tapatalk

 

[cmkelley]

Happened to me before also. Same router.

Ditto. So far 384.8_1 seems to be okay.