Recent content by Forsaken

Yep, now I can confirm AXE11000's 386.7 is also affected. Took about 16 days to catch one.

And this is the point. I flashed my AXE11000 with 386.5 with that suggested fix included and got zero panics since that time. Neither I got any related warnings in the logs. The error completely gone. I can speculate 386.5 has this "AVS" feature disabled (by default?). But recent reports that...

Really strange things are happening here. For me it is opposite: panics have completely gone after I switched to Merlin. The only difference - I'm still on 386.5. Planning to switch to .7 shortly. Will keep an eye on this after update.

Very interesting. As I mentioned previously, about 2 moth ago I compiled and flashed @RMerlin 's v386.5 with that BUG_ON line changed to WARN_ON. Didn't have any reboot since that time. That said, I didn't have any NAND-related warnings in the remote logs as well. Suspecting Asuswrt-Merlin 386.5...

This is very, very strange. With proposed change - it should not panic at that line anymore! Unless for some crazy reason WARN_ON macro is mapped to the same stuff as BUG_ON... Wonder if you want to try RMerlin's 386.5 with that modification applied?

That what they gave me as well. Is this still "BUG: failure at drivers/mtd/nand/brcmnand/brcmnand.c:1339/brcmnand_send_cmd()!" panic message?

@strunker , Just got notification from ASUS another user who is being testing firmware got an error so they prepared another firmware version. Is that you or does it mean somebody else has same problem?

@RMerlin, For some reasons stopped getting notifications about new replies for this thread, so just noticed your reply. Sure will try to contact them. Living great on your 386_5 for almost a week, but as @strunker said the issue is too random to make conclusions. Thank you for helping us...

Well, it is pretty close to stock: https://github.com/RMerl/asuswrt-merlin.ng/wiki/Installation Linux kernel version is the same as stock, at least. So as closed-sourced broadcomm components, I would believe. So I would think it is not going to magically go away. But it at least gives a...

Most of mine were preserved. Just had to play with Samba configuration a little bit. AFAIK - just simple as flashing stock back, factory reset + restore previously saved config. Yep. Again, just to emphasize: I would not anticipate it will magically gone with just flashing "original" 386.5...

Couple updates from my side. First, I got another Kernel panic last Monday ~14h after reboot, which is definitely bad news indicating that even everyday reboot will not guarantee 100% reliability. Second, ASUS released another firmware, but this is rather neutral since there is nothing specific...

My status as well: 40+ days w/o panic with scheduled reboots. At the beginning of the February switched to rebooting three times a week (from previous "everyday"). Going to change to "two times a week" in March and then "once a week" in April, unless they release mentioned firmware earlier...

Ok, giving following trace we both have: 2021-10-01T09:40:42-05:00 user 3 kernel: bcm63xx_nand ff801800.nand: intfc status 700000e0 status = 0x700000e0 = 01110000000000000000000011100000 They are checking for the following: NAND_CTRL_RDY | NAND_STATUS_READY, which is (INTFC_CTLR_READY |...

Could you please check and share uptime of your unit? @strunker is right - it is pretty easy to miss(interpret) this stuff unless you know where to look at.

Hi strunker, Seems we are in the same boat here :). I noticed something similar on one of the old firmwares (42489-43986) once or twice, but it never happened with 45850 or newer. But it was before I started digging into the logs, so it might be different after all. Try to schedule everyday...