Menu
What's new
By:
Filters Better Search

Beta Asuswrt-Merlin 386.1 Beta is now available

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

Status
Not open for further replies.
@RMerlin

Another strange issue, as soon as I connect my HP Wireless printer, router reboots with following error:

Code: 
May  5 06:05:15 kernel: ubi1: attaching mtd10
May  5 06:05:15 kernel: ubi1: scanning is finished
May  5 06:05:15 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May  5 06:05:15 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May  5 06:05:15 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May  5 06:05:15 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May  5 06:05:15 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May  5 06:05:15 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May  5 06:05:15 kernel: ubi1: max/mean erase counter: 20/9, WL threshold: 4096, image sequence number: 1960956644
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May  5 06:05:15 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1046
May  5 06:05:15 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 1061
May  5 06:05:15 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May  5 06:05:15 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May  5 06:05:15 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May  5 06:05:15 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May  5 06:05:15 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 700E756D-208E-4C91-B256-B51AA3EDE77F, small LPT model
May  5 06:05:15 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May  5 06:05:15 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: ubi1: detaching mtd10
May  5 06:05:15 kernel: ubi1: mtd10 is detached
May  5 06:05:15 kernel: proc_dostring_crashlogsave:  crash log filename is /jffs/crashlog.log
May  5 06:05:15 kernel: ++++ Powering up USB blocks
May  5 06:05:15 kernel: usb3 reseting..........
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: release usb3 reseting..........
May  5 06:05:15 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: usb3 reseting..........
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6

I have tried factory reset router and HP printer both but still issue persist. I was all fine with 384.19.
 
Sun said:
Mix - Some mac addresses belong to guest wifi IPs (randomly assigned by DHCP) and some are DCHP assignments using "Manually Assigned IP around the DHCP list".
Click to expand...
The Manually Assigned ones definitely do produce this result..
 
Sun said:
@RMerlin

Another strange issue, as soon as I connect my HP Wireless printer, router reboots with following error:

Code: 
May  5 06:05:15 kernel: ubi1: attaching mtd10
May  5 06:05:15 kernel: ubi1: scanning is finished
May  5 06:05:15 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May  5 06:05:15 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May  5 06:05:15 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May  5 06:05:15 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May  5 06:05:15 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May  5 06:05:15 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May  5 06:05:15 kernel: ubi1: max/mean erase counter: 20/9, WL threshold: 4096, image sequence number: 1960956644
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May  5 06:05:15 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1046
May  5 06:05:15 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 1061
May  5 06:05:15 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May  5 06:05:15 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May  5 06:05:15 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May  5 06:05:15 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May  5 06:05:15 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 700E756D-208E-4C91-B256-B51AA3EDE77F, small LPT model
May  5 06:05:15 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May  5 06:05:15 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: ubi1: detaching mtd10
May  5 06:05:15 kernel: ubi1: mtd10 is detached
May  5 06:05:15 kernel: proc_dostring_crashlogsave:  crash log filename is /jffs/crashlog.log
May  5 06:05:15 kernel: ++++ Powering up USB blocks
May  5 06:05:15 kernel: usb3 reseting..........
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: release usb3 reseting..........
May  5 06:05:15 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 kernel: usb3 reseting..........
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May  5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6

I have tried factory reset router and HP printer both but still issue persist. I was all fine with 384.19.
Click to expand...
To which issue are you referring?.. the "Buggy Protocol"? which is known about regardless of what is or isnt connected and can be resolved by uising Guest network 2 or 3 rather than one OR Per another user in this thread.. " PS: Doing some tests, I also found out that I solved the "protocol 0800 is buggy" issue by disabling IPV6 (previously configured as Passthrough) on my AX86U. "
 
Swapped out my AC86U for a new AX86U as my main router. Upgraded the new AX to 386.1 Beta 2 and configured from scratch. Working great so far. As soon as 386.1 R0 is available, I'll upgrade both routers and set up the AC86U as a mesh device. Hopefully this will improve device speeds in the farthest away areas of the house. The AX86U is an impressive router, and already I notice snappier performance on my devices (Both hard-wired and wireless).
 
Updated from 384.19 to beta2. I haven't noticed any problems ao far, but didn't have time to test everything. Looks good :)
 
Suzib6sw said:
To which issue are you referring?.. the "Buggy Protocol"? which is known about regardless of what is or isnt connected and can be resolved by uising Guest network 2 or 3 rather than one OR Per another user in this thread.. " PS: Doing some tests, I also found out that I solved the "protocol 0800 is buggy" issue by disabling IPV6 (previously configured as Passthrough) on my AX86U. "
Click to expand...
IPv6 already disabled.
 
@RMerlin Five devices of mine show in the offline client list only, under manually assign addresses. However they are not offline they are connected to the wifi on the AX88U with 386.1 B2. Strange they are also absent from the client list on Network Map page. If I go to the GUI of my attached AC68U access point and click client list, every device I have shows, including the devices on the main router (The AX88U). I would expect that to be normal behavior, but the AX88U fails to list all devices. One thing in common about the five devices, they all have static addresses.
 
@RMerlin

Here is the pastebin of the crashlog. It's happening to me every day now, it will just randomly crash out. As said before I flash to Beta2 then did a factory reset and clear nvram
 
mbze430 said:
@RMerlin

Here is the pastebin of the crashlog. It's happening to me every day now, it will just randomly crash out. As said before I flash to Beta2 then did a factory reset and clear nvram
Click to expand...

The crash occurs in mcpd, which is closed source and outside of my control. No idea might be triggering it, best I can recommend is reproducing the issue with the stock firmware, and reporting it to Asus if you do so.
 
Upgraded from Alpha 4 to Beta 1, reset to defaults and set up everything again manually, updated to beta 2, reboot and no reset so far everything working great. I finally got the TP Switch LACP bonded with my AX86U working great so far after a ruff config process to get it up and running correctly. Open VPN working great also with aes-128-gcm via PIA. Thanks @RMerlin
 
everything working perfectly on Beta 2 aftrer flashing my AC-5300 - Thanks Merlin;)
 
Hello! I just set up aiMesh after installing Beta 2 on my AC86U (router) and AC68U (ethernet node) and AC66U_B1 (wireless node). All seems to be working well. I am curious-- I tried to run the speedtest from the tab in the GUI, and got an error message saying that it was unable to run, and to check my internet connection. Is the speedtest disabled in a mesh environment? And/or is there some setting I need to tweak in order for it to function properly?

And: I had been running FreshJR for VOIP QoS before the upgrade. I gather from my reading that adaptive QoS is working better. Is it still recommended to install a QoS script? I am trying to make as few modifications as possible, in order to simplify maintenance and upgrades. At the moment I have just turned on QoS and set my priorities. Sorry if this is OT...
 
RMerlin said:
The crash occurs in mcpd, which is closed source and outside of my control. No idea might be triggering it, best I can recommend is reproducing the issue with the stock firmware, and reporting it to Asus if you do so.
Click to expand...

I also saw some changes related to mcpd in the latest GPL/SDK update, so maybe that will be fixed by these updates.
 
Kees17760 said:
Hi,

Still the same with beta 2 on my AC2900.
- Clients on Guest network 1 (2,4 GHz) can't access internet, ONLY when the router is connected through PPTP/L2TP.
Once VPN is switched OFF they do have internet access. Did a full reset
Click to expand...
 
Last edited:
Deekers said:
Just want to confirm that Beta 2 has fixed all of the issues above for my AC3100. All wireless clients are showing correctly and AiMesh is performing perfectly.
Click to expand...

I spoke too soon. 24 hours later and my router's home page is saying my ISP's dhcp is messed up. My wireless clients alternate between 0 and the actual number (over 20) every few seconds, my AiMesh node isn't connected, and of course the internet doesn't work. Flashed 384.19 back to it and all problems are gone.

If no one else on an AC3100 is having similar issues, perhaps I need to do a full reset to factory and upgrade next time.

My question is this: If I save my settings to my local computer, do the reset and upgrade, will I be able to restore from my settings backup? If so, will that restore *everything* to include my VPN settings, encryption keys, etc?
 
You haven't done it yet? o_O

A full reset necessitates that you do a minimal and manual install. Using saved backup config files is equivalent to not doing the reset at all.

www.snbforums.com

Would appreciate Wireless Professional Setting recommendations of AIMesh with AX88U as the root router

Hi, I am a new user. Great community here, very useful, so much knowledge, at times overwhelming but all around a great place! I have been an ASUS router user for as long as I remember, but only recently I went down the Merlin route. My current set-up is as follows: Root/Main Router: A new...
www.snbforums.com www.snbforums.com

Use the suggested steps in the post above to get your router to a good/known state and one where the expected defaults can be effectively used, and, as expected.
 
I have an RT-AX58U router.
Worked with Merlin 384_19 without problem. With beta1 and beta 2, the temperature of the 2.4GHz chip jumps to 76°C. Sometimes it comes back to the usual 48°C and after a while it stays at 76° and the performance of 2.4GHz id the very bad.
Factory reset and various updates to the 386 betas did not chenge anything.
Here the temperature with 384.19 (the jumps come frome a smatphone updating over 2.4GHz):
T384_19.jpg


And here wih beta2:

TBeta2.jpg


I am running the 384_19 and waiting for 386.1 stable to make anothe try.

Still good work, Merlin. Thank you for your efforts.
 
Last edited:
Switched to Beta 2 this morning. Really amazing stability and speeds on my 3 node RT-AC68U Mesh setup.

1 node was never used in the past, even though it was closer to some clients.
Distribution between nodes is much faster and feels more optimized.

Looking forward to the final release ;)

Keep up the great work :cool:
Thanks
Alex
 
Download master not work on 386 beta 2 with Ax86u. After download torretn file begin crash.
Code: 
Dec 18 22:14:30 transmission-daemon[6175]: Transmission 2.92 (14714) started (session.c:769)
Dec 18 22:14:30 transmission-daemon[6175]: RPC Server Adding address to whitelist: 127.0.0.1 (rpc-server.c:1078)
Dec 18 22:14:30 transmission-daemon[6175]: RPC Server Adding address to whitelist: *.*.*.* (rpc-server.c:1078)
Dec 18 22:14:30 transmission-daemon[6175]: RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:1288)
Dec 18 22:14:30 transmission-daemon[6175]: RPC Server Whitelist enabled (rpc-server.c:1292)
Dec 18 22:14:30 transmission-daemon[6175]: RPC Server Password required (rpc-server.c:1295)
Dec 18 22:14:30 transmission-daemon[6175]: UDP Failed to set receive buffer: requested 4194304, got 1048576 (tr-udp.c:84)
Dec 18 22:14:30 transmission-daemon[6175]: UDP Please add the line "net.core.rmem_max = 4194304" to /etc/sysctl.conf (tr-udp.c:89)
Dec 18 22:14:30 transmission-daemon[6175]: DHT Generating new id (tr-dht.c:311)
Dec 18 22:14:30 transmission-daemon[6175]: Using settings from "/tmp/mnt/WD4Tb/Download2/config" (daemon.c:578)
Dec 18 22:14:30 transmission-daemon[6175]: Saved "/tmp/mnt/WD4Tb/Download2/config/settings.json" (variant.c:1269)
Dec 18 22:14:30 transmission-daemon[6175]: transmission-daemon requiring authentication (daemon.c:604)
Dec 18 22:14:30 transmission-daemon[6175]: Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:70)
Dec 18 22:14:30 transmission-daemon[6175]: Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:70)
Dec 18 22:14:38 transmission-daemon[6175]: Port Forwarding State changed from "Not forwarded" to "Starting" (port-forwarding.c:92)
Dec 18 22:14:39 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:39 kernel: CPU: 2 PID: 6180 Comm: dm2_transmissio Tainted: P           O    4.1.52 #2
Dec 18 22:14:39 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:39 kernel: task: ffffffc008d0b500 ti: ffffffc02f25c000 task.ti: ffffffc02f25c000
Dec 18 22:14:39 kernel: PC is at 0xf6f20d44
Dec 18 22:14:39 kernel: LR is at 0x2f6b0
Dec 18 22:14:39 kernel: pc : [<00000000f6f20d44>] lr : [<000000000002f6b0>] pstate: 20000010
Dec 18 22:14:39 kernel: sp : 00000000f6cc1760
Dec 18 22:14:39 kernel: x12: 000000000008f570 
Dec 18 22:14:39 kernel: x11: 00000000f6cc18f4 x10: 00000000005a35f8 
Dec 18 22:14:39 kernel: x9 : 000000000059d1c8 x8 : 000000000000000c 
Dec 18 22:14:39 kernel: x7 : 00000000005a3900 x6 : 0000000000000000 
Dec 18 22:14:39 kernel: x5 : 00000000005a3600 x4 : 00000000005cb038 
Dec 18 22:14:39 kernel: x3 : 0000000000000000 x2 : 000000000059d1f8 
Dec 18 22:14:39 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:41 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:41 kernel: CPU: 1 PID: 6262 Comm: dm2_transmissio Tainted: P           O    4.1.52 #2
Dec 18 22:14:41 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:41 kernel: task: ffffffc032b58080 ti: ffffffc014e14000 task.ti: ffffffc014e14000
Dec 18 22:14:41 kernel: PC is at 0xf6e00d44
Dec 18 22:14:41 kernel: LR is at 0x2f6b0
Dec 18 22:14:41 kernel: pc : [<00000000f6e00d44>] lr : [<000000000002f6b0>] pstate: 20000010
Dec 18 22:14:41 kernel: sp : 00000000f6ba1a78
Dec 18 22:14:41 kernel: x12: 000000000008f570 
Dec 18 22:14:41 kernel: x11: 00000000f6ba1c0c x10: 00000000001f6bf8 
Dec 18 22:14:41 kernel: x9 : 00000000001f11b8 x8 : 000000000000000c 
Dec 18 22:14:41 kernel: x7 : 00000000001f6f00 x6 : 0000000000000000 
Dec 18 22:14:41 kernel: x5 : 00000000001f6c00 x4 : 00000000001f7820 
Dec 18 22:14:41 kernel: x3 : 0000000000000000 x2 : 00000000001f11e8 
Dec 18 22:14:41 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:44 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:44 kernel: CPU: 2 PID: 6274 Comm: dm_print_status Tainted: P           O    4.1.52 #2
Dec 18 22:14:44 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:44 kernel: task: ffffffc02f358b00 ti: ffffffc005810000 task.ti: ffffffc005810000
Dec 18 22:14:44 kernel: PC is at 0xf7279d44
Dec 18 22:14:44 kernel: LR is at 0x131a0
Dec 18 22:14:44 kernel: pc : [<00000000f7279d44>] lr : [<00000000000131a0>] pstate: 20000010
Dec 18 22:14:44 kernel: sp : 00000000ff9d96f8
Dec 18 22:14:44 kernel: x12: 00000000000311d8 
Dec 18 22:14:44 kernel: x11: 00000000ff9da284 x10: 00000000f72f9f6c 
Dec 18 22:14:44 kernel: x9 : 0000000000000000 x8 : 0000000000000000 
Dec 18 22:14:44 kernel: x7 : 0000000000000000 x6 : 0000000000011014 
Dec 18 22:14:44 kernel: x5 : 0000000000000000 x4 : 00000000ff9da8db 
Dec 18 22:14:44 kernel: x3 : 0000000000000000 x2 : 000000000000000c 
Dec 18 22:14:44 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:45 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:45 kernel: CPU: 1 PID: 6281 Comm: dm2_transmissio Tainted: P           O    4.1.52 #2
Dec 18 22:14:45 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:45 kernel: task: ffffffc008d0b500 ti: ffffffc005810000 task.ti: ffffffc005810000
Dec 18 22:14:45 kernel: PC is at 0xf71c2d44
Dec 18 22:14:45 kernel: LR is at 0x2f6b0
Dec 18 22:14:45 kernel: pc : [<00000000f71c2d44>] lr : [<000000000002f6b0>] pstate: 20000010
Dec 18 22:14:45 kernel: sp : 00000000f6f63a78
Dec 18 22:14:45 kernel: x12: 000000000008f570 
Dec 18 22:14:45 kernel: x11: 00000000f6f63c0c x10: 000000000028fbf8 
Dec 18 22:14:45 kernel: x9 : 000000000028a1b8 x8 : 000000000000000c 
Dec 18 22:14:45 kernel: x7 : 000000000028ff00 x6 : 0000000000000000 
Dec 18 22:14:45 kernel: x5 : 000000000028fc00 x4 : 0000000000290820 
Dec 18 22:14:45 kernel: x3 : 0000000000000000 x2 : 000000000028a1e8 
Dec 18 22:14:45 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:49 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:49 kernel: CPU: 0 PID: 6301 Comm: dm_print_status Tainted: P           O    4.1.52 #2
Dec 18 22:14:49 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:49 kernel: task: ffffffc014e755c0 ti: ffffffc005a3c000 task.ti: ffffffc005a3c000
Dec 18 22:14:49 kernel: PC is at 0xf7615d44
Dec 18 22:14:49 kernel: LR is at 0x131a0
Dec 18 22:14:49 kernel: pc : [<00000000f7615d44>] lr : [<00000000000131a0>] pstate: 20000010
Dec 18 22:14:49 kernel: sp : 00000000fffe1e28
Dec 18 22:14:49 kernel: x12: 00000000000311d8 
Dec 18 22:14:49 kernel: x11: 00000000fffe29b4 x10: 00000000f7695f6c 
Dec 18 22:14:49 kernel: x9 : 0000000000000000 x8 : 0000000000000000 
Dec 18 22:14:49 kernel: x7 : 0000000000000000 x6 : 0000000000011014 
Dec 18 22:14:49 kernel: x5 : 0000000000000000 x4 : 00000000fffe300b 
Dec 18 22:14:49 kernel: x3 : 0000000000000000 x2 : 000000000000000c 
Dec 18 22:14:49 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:49 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:49 kernel: CPU: 3 PID: 6310 Comm: dm2_transmissio Tainted: P           O    4.1.52 #2
Dec 18 22:14:49 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:49 kernel: task: ffffffc02e18b580 ti: ffffffc008d74000 task.ti: ffffffc008d74000
Dec 18 22:14:49 kernel: PC is at 0xf721ad44
Dec 18 22:14:49 kernel: LR is at 0x2f6b0
Dec 18 22:14:49 kernel: pc : [<00000000f721ad44>] lr : [<000000000002f6b0>] pstate: 20000010
Dec 18 22:14:49 kernel: sp : 00000000f6fbba78
Dec 18 22:14:49 kernel: x12: 000000000008f570 
Dec 18 22:14:49 kernel: x11: 00000000f6fbbc0c x10: 0000000000576bf8 
Dec 18 22:14:49 kernel: x9 : 00000000005711b8 x8 : 000000000000000c 
Dec 18 22:14:49 kernel: x7 : 0000000000576f00 x6 : 0000000000000000 
Dec 18 22:14:49 kernel: x5 : 0000000000576c00 x4 : 0000000000577820 
Dec 18 22:14:49 kernel: x3 : 0000000000000000 x2 : 00000000005711e8 
Dec 18 22:14:49 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:54 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:54 kernel: CPU: 0 PID: 6423 Comm: dm2_transmissio Tainted: P           O    4.1.52 #2
Dec 18 22:14:54 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:54 kernel: task: ffffffc03033f440 ti: ffffffc005810000 task.ti: ffffffc005810000
Dec 18 22:14:54 kernel: PC is at 0xf6ebbd44
Dec 18 22:14:54 kernel: LR is at 0x2f6b0
Dec 18 22:14:54 kernel: pc : [<00000000f6ebbd44>] lr : [<000000000002f6b0>] pstate: 20000010
Dec 18 22:14:54 kernel: sp : 00000000f6c5ca78
Dec 18 22:14:54 kernel: x12: 000000000008f570 
Dec 18 22:14:54 kernel: x11: 00000000f6c5cc0c x10: 0000000000201bf8 
Dec 18 22:14:54 kernel: x9 : 00000000001fc1b8 x8 : 000000000000000c 
Dec 18 22:14:54 kernel: x7 : 0000000000201f00 x6 : 0000000000000000 
Dec 18 22:14:54 kernel: x5 : 0000000000201c00 x4 : 0000000000202820 
Dec 18 22:14:54 kernel: x3 : 0000000000000000 x2 : 00000000001fc1e8 
Dec 18 22:14:54 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:54 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:54 kernel: CPU: 1 PID: 6530 Comm: dm_print_status Tainted: P           O    4.1.52 #2
Dec 18 22:14:54 kernel: Hardware name: Broadcom-v8A (DT)
Dec 18 22:14:54 kernel: task: ffffffc008b78100 ti: ffffffc008d48000 task.ti: ffffffc008d48000
Dec 18 22:14:54 kernel: PC is at 0xf75e1d44
Dec 18 22:14:54 kernel: LR is at 0x131a0
Dec 18 22:14:54 kernel: pc : [<00000000f75e1d44>] lr : [<00000000000131a0>] pstate: 20000010
Dec 18 22:14:54 kernel: sp : 00000000ffadbbb8
Dec 18 22:14:54 kernel: x12: 00000000000311d8 
Dec 18 22:14:54 kernel: x11: 00000000ffadc744 x10: 00000000f7661f6c 
Dec 18 22:14:54 kernel: x9 : 0000000000000000 x8 : 0000000000000000 
Dec 18 22:14:54 kernel: x7 : 0000000000000000 x6 : 0000000000011014 
Dec 18 22:14:54 kernel: x5 : 0000000000000000 x4 : 00000000ffadcd9b 
Dec 18 22:14:54 kernel: x3 : 0000000000000000 x2 : 000000000000000c 
Dec 18 22:14:54 kernel: x1 : 0000000000000000 x0 : 0000000000000000 
Dec 18 22:14:57 kernel: potentially unexpected fatal signal 11.
Dec 18 22:14:57 kernel: CPU: 1 PID: 6542 Comm: dm2_transmissio Tainted: P           O    4.1.52 #
 
Status
Not open for further replies.

Similar threads

RMerlin
  • Locked
Beta Asuswrt-Merlin 386.14 beta is now available
2
Replies
35
Views
9K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 386.14 is now available for AC models
9 10 11
Replies
211
Views
33K
Don Walker
Don Walker
RMerlin
  • Locked
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
2 3 4
Replies
70
Views
12K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
2 3 4
Replies
62
Views
7K
RMerlin
RMerlin
RMerlin
  • Locked
Beta Asuswrt-Merlin 3004.388.8 beta is now available
6 7 8
Replies
155
Views
30K
RMerlin
RMerlin
Similar threads
Thread starter Title Forum Replies Date
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
RMerlin Release Asuswrt-Merlin 386.14 is now available for AC models Asuswrt-Merlin 211
RMerlin Beta Asuswrt-Merlin 386.14 beta is now available Asuswrt-Merlin 35
RMerlin Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models Asuswrt-Merlin 79
RMerlin Beta Asuswrt-Merlin 386.13 beta is now available for AC models Asuswrt-Merlin 32
RMerlin Release Asuswrt-Merlin 386.12_6 is now available for AC models Asuswrt-Merlin 168
kaotic2499 Please add Asuswrt-merlin to GT-BE98 (Non-pro) version Asuswrt-Merlin 6
RMerlin Release Asuswrt-Merlin 3004.388.8_4 is now available Asuswrt-Merlin 72
RMerlin Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices Asuswrt-Merlin 62
F Several Questions Re:Asuswrt-Merlin Feature Implementation Asuswrt-Merlin 2

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 729 (members: 21, guests: 708)
Top