What's new

Sporadic GT-AXE11000 reboots due to kernel panic

  • 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!

I have two AXE-11000's and both reboot like within 2-5days, as back in previous append. I reported to ASUS and they advised my issue was a wireless issue and try different firmwares. I've tried... Merlin's 386.7_2, 386.7_0, 386.5_2 and ASUS FW_GT_AXE11000_300438649675, FW_GT_AXE11000_300438647875 no resolution to reboots on either unit.
In the last reboot yesterday (no devices attached) syslog went from 27Jul 06:30 (when it crashed) to 5May 01:05 and lots of logs within seconds, frequent broadcom words, then back to 27Jul 07:26 in a gap of 56mins later. I attached the log for those that might be interested, or have ideas. Updated ASUS with this last crash, not heard back yet.

I'm using now for primary household a GT-AX6000 running 386.7_0 then _2 and no issues at all, very happy with this unit & it's performance. My playing on 6GHz halted at present. :-(
 

Attachments

  • T460S Wayne - syslog.txt
    144.3 KB · Views: 85
Time to test the 386.7_2 release then.

Well, 386.7_2 didn't work then.
Lasted almost 4 days then had two Kernel panics in a row.
At least it came back up without intervention this time.
 
My reply was to @Forsaken, but if you're having the same issues, have you performed a full reset to factory defaults after flashing the latest firmware first? And, not using/inserting the USB drive you're using for amtm, during the test period?
 
Just happened , 386.7_2 just restarted my AX86U. Might have to roll back to 386.5 at this point. 5 days uptime.
 
Now had 14days (so far...) without reboot on my AXE11000, this a first time, by at least 7 days using ASUS code "FW_GT_AXE11000_300438649675". YIPPEE!! Now wishing (dreaming) for the @RMerlin variant (or later) of this release (probably 388 level) in months to come.
| 24days now as of 22:34 20Aug'22.
 
Last edited:
Now had 14days (so far...) without reboot on my AXE11000, this a first time, by at least 7 days using ASUS code "FW_GT_AXE11000_300438649675". YIPPEE!! Now wishing (dreaming) for the @RMerlin variant (or later) of this release (probably 388 level) in months to come.

This makes no sense, Merlin's firmware uses 386_48966 GPL. This is very close to the release number you state.
From what I can see there would be only a minor difference and NOT affect this problem.

Merlin can you comment?

CC
 
Now had 14days (so far...) without reboot on my AXE11000, this a first time, by at least 7 days using ASUS code "FW_GT_AXE11000_300438649675". YIPPEE!!

I don't think that's nearly long enough to start celebrating!
When I first got my AX86S, it ran for 31 days before it rebooted.
 
Merlin can you comment?
I have no idea what changed at the kernel level between these two GPL versions. If a specific fix is involved, then it wouldn`t require a much larget version jump to include it.
 
Can I just chime in. I have a TUF-AX3000. I have had a similar issue, came on the forums to try and find a solution, found nothing of interest, ASUS also told me to RMA....... not that it would help as it's clearly a software/driver issue.

I have solved my issues approx 99%. So I had kernal panics, modem freezes and rebooting, wifi drop outs etc. Now interesting fact .... alot of Telstra Modems here in Australia have been blue screening windows computers with incompatable wifi cards because ''Protected Frames'' was on.

So what I changed on mine which solved the majority of my issue was:

-Turned off WPA3 - Disabled Protected Frames
-Disabled All IP6 (anywhere I could find it) - apparently this helps with Linux issues.
-Disabled Traffic Analyser.
-Changed NAT Back From 'Full Cone' to 'Symmetric'
-TCP Adjustments (TCP Connections Limit to 100000, halfed all other settings) - Helps with Kernel Panic?

And then I had WIFI Compatability Issues. Again still working through these but I found actually turning off WIFI6 (160Hz) majorly helped me.

Hope some of this info helps someone.
 
I'm having exactly the same issue with AsusWRT Merlin 386.7_2 on GT-AXE11000. I have however noticed that Asus has recently (17/10/2022) posted a 3.0.0.4.388.21224 - so much further along than Merlin. Has anyone tried it yet and checked the kernel panics?
 
Just to report back. I ended up returning both my TUF AX-3000's and fought to get a refund which I did.

Stuff messing aroung with nonsense. I went to a TP-Link ER605 Omada setup with the Omada Controller and a Roof/Wall Mount POE WIFI6 Access Point all tied into the Omada system. (same money as I had bought two of the ASUS). No issues. But essentially the ER605 ...... where my TUF AX-3000 random reboot all the damn time, my ER605 hasn't rebooted ONCE! Been in operation since October 1st.

The ASUS TUF AX-3000 I had bought were GREAT routers......... rather WOULD HAVE BEEN if they had actually worked properly, unforunately they didn't. So I'm out.
 
Just chiming in here... AX86S experienced first random reboot this evening with merlin 388.1. FWIW, I did just add an AC86u as a mesh node with it, and that one is on 386.7_2. I turned off wpa3... will post if it happens again.
 
Just chiming in here... AX86S experienced first random reboot this evening with merlin 388.1. FWIW, I did just add an AC86u as a mesh node with it, and that one is on 386.7_2. I turned off wpa3... will post if it happens again.
Same, still happening on my AX86U on 388.1
 
I'm was still getting random reboots on my AX86S running 388.1

The only thing is, I wasn't getting the "Kernel panic - not syncing: BUG!" entries on my syslog server, it just reboots with no comment in the log file.

I've gone back to 386.7_2 now as it seems to reboot less often and at least I can see what happened in the log.
 
Did this ever get solved? Still on 386.5_2 and still occasionally getting a random reboot after 9-11 days or so.
 
Did this ever get solved? Still on 386.5_2 and still occasionally getting a random reboot after 9-11 days or so.

For me they disappeared with 388.2_2
Latest release (3004.388.4) is still good.
 
I am having the same problem with random reboots. The latest one happened after 16 days today:
Code:
Oct  3 10:16:04 RT-AX86U-A4ECD4D-C kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
Oct  3 10:16:04 RT-AX86U-A4ECD4D-C kernel: bcm63xx_nand ff801800.nand: intfc status 700000e0
Oct  3 10:16:04 RT-AX86U-A4ECD4D-C kernel: BUG: failure at drivers/mtd/nand/brcmnand/brcmnand.c:1339/brcmnand_send_cmd()!
Oct  3 10:16:04 RT-AX86U-A4ECD4D-C kernel: Kernel panic - not syncing: BUG!
Oct  3 10:16:04 RT-AX86U-A4ECD4D-C kernel: CPU: 2 PID: 453 Comm: jffs2_gcd_mtd9 Tainted: P           O    4.1.52 #2

I have an RT-AX86U running 3004.388.4. I ran 386.5_2 until recently. However, I experienced random reboots every couple of days to two weeks since last year.

Has there been any work-around or solution? Why doesn't everyone have these reboots?
 

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