"unhandled level 3 translation fault (11)" on roamast

[achanwl]

Hi all,

I have just started using aimesh, before was just manual setup main router + few APs, but tired of maintaining multiple devices individually, and want to take advantage of the centralized management. I have rt-ac86u as the aimesh router, with a few aimesh nodes like rt-ac68w/rt-ac1900/rt-ac88u.

They are running the latest 384.14_2 firmware.

I always have roaming assistant enabled with RSSI set at -65. Never have the below issue before when running as main router + few APs.

Now I'm seeing from the log, whenever roamast runs (I'm guessing it's trying to move the client to a different AP), I'd get "unhandled level 3 translation fault (11)".

Like this in the log:

Jan 12 12:06:20 roamast: determine candidate node [xx:xx:xx:xx:xx:xx](rssi: -42dbm) for client [xx:xx:xx:xx:xx:xx](rssi: -69dbm) to roam
Jan 12 12:06:20 kernel: roamast[4801]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Jan 12 12:06:20 kernel: pgd = ffffffc00b4fe000
Jan 12 12:06:20 kernel: [00000000] *pgd=000000000a08c003, *pud=000000000a08c003, *pmd=000000000b507003, *pte=0000000000000000
Jan 12 12:06:20 kernel: CPU: 0 PID: 4801 Comm: roamast Tainted: P           O    4.1.27 #2
Jan 12 12:06:20 kernel: Hardware name: Broadcom-v8A (DT)
Jan 12 12:06:20 kernel: task: ffffffc0192e9480 ti: ffffffc013cf4000 task.ti: ffffffc013cf4000
Jan 12 12:06:20 kernel: PC is at 0x10772c
Jan 12 12:06:20 kernel: LR is at 0xf69f97d4
Jan 12 12:06:20 kernel: pc : [<000000000010772c>] lr : [<00000000f69f97d4>] pstate: 60070010
Jan 12 12:06:20 kernel: sp : 00000000f69c7308
Jan 12 12:06:20 kernel: x12: 00000000f6b04c40
Jan 12 12:06:20 kernel: x11: 0000000000000000 x10: 0000000000000001
Jan 12 12:06:20 kernel: x9 : 0000000000168828 x8 : 0000000000000000
Jan 12 12:06:20 kernel: x7 : 0000000000000001 x6 : 00000000f7086ce0
Jan 12 12:06:20 kernel: x5 : 00000000f69c7380 x4 : 00000000f69c733c
Jan 12 12:06:20 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jan 12 12:06:20 kernel: x1 : 0000000000000020 x0 : 0000000000000000

And doesn't look like it was successful getting the client to roam to a different node because the process generates kernel error.

Is it a known issue? Anyone seeing it too or just me? I know there is the dcd process has similar thing, but that's different here.

Before, with main router + APs, I recall I have never seen the roamast messages, it's like even I had it set to enable, roamast wasn't doing anything when it's not in aimesh config. Likely I don't completely understand how it works in different mode?

And I have another issue with aimesh, which I should probably start a different thread.

Feels like maybe I shouldn't switch to aimesh mode... and should go back to main router + APs mode... sigh...

Thanks in advance for any pointers/suggestions.

-Alan

 

[luzumsuz]

İ also get this issue

 

[jksmurf]

@jksmurf You crash is slightly different the the OP. You are getting the "dcd Tainted" crash. There are over a hundred posts about this. For example: https://www.snbforums.com/threads/crashes.61914/

Oh. Oops, apologies I'm probably not too good at spotting the difference. Seems from that post and this https://www.snbforums.com/threads/ac86u-dcd-tainted-on-merlin-384-8_2.54967/ that while it should have been fixed in 384.9 it was not; and that the Trendmicro disabling is the only recourse?

[EDIT]I will delete it here and add it to another post. Apologies for cross-posting.

 

[jazzer]

Hi all,

I have just started using aimesh, before was just manual setup main router + few APs, but tired of maintaining multiple devices individually, and want to take advantage of the centralized management. I have rt-ac86u as the aimesh router, with a few aimesh nodes like rt-ac68w/rt-ac1900/rt-ac88u.

They are running the latest 384.14_2 firmware.

I always have roaming assistant enabled with RSSI set at -65. Never have the below issue before when running as main router + few APs.

Now I'm seeing from the log, whenever roamast runs (I'm guessing it's trying to move the client to a different AP), I'd get "unhandled level 3 translation fault (11)".

Like this in the log:

Jan 12 12:06:20 roamast: determine candidate node [xx:xx:xx:xx:xx:xx](rssi: -42dbm) for client [xx:xx:xx:xx:xx:xx](rssi: -69dbm) to roam
Jan 12 12:06:20 kernel: roamast[4801]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
Jan 12 12:06:20 kernel: pgd = ffffffc00b4fe000
Jan 12 12:06:20 kernel: [00000000] *pgd=000000000a08c003, *pud=000000000a08c003, *pmd=000000000b507003, *pte=0000000000000000
Jan 12 12:06:20 kernel: CPU: 0 PID: 4801 Comm: roamast Tainted: P           O    4.1.27 #2
Jan 12 12:06:20 kernel: Hardware name: Broadcom-v8A (DT)
Jan 12 12:06:20 kernel: task: ffffffc0192e9480 ti: ffffffc013cf4000 task.ti: ffffffc013cf4000
Jan 12 12:06:20 kernel: PC is at 0x10772c
Jan 12 12:06:20 kernel: LR is at 0xf69f97d4
Jan 12 12:06:20 kernel: pc : [<000000000010772c>] lr : [<00000000f69f97d4>] pstate: 60070010
Jan 12 12:06:20 kernel: sp : 00000000f69c7308
Jan 12 12:06:20 kernel: x12: 00000000f6b04c40
Jan 12 12:06:20 kernel: x11: 0000000000000000 x10: 0000000000000001
Jan 12 12:06:20 kernel: x9 : 0000000000168828 x8 : 0000000000000000
Jan 12 12:06:20 kernel: x7 : 0000000000000001 x6 : 00000000f7086ce0
Jan 12 12:06:20 kernel: x5 : 00000000f69c7380 x4 : 00000000f69c733c
Jan 12 12:06:20 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Jan 12 12:06:20 kernel: x1 : 0000000000000020 x0 : 0000000000000000

And doesn't look like it was successful getting the client to roam to a different node because the process generates kernel error.

Is it a known issue? Anyone seeing it too or just me? I know there is the dcd process has similar thing, but that's different here.

Before, with main router + APs, I recall I have never seen the roamast messages, it's like even I had it set to enable, roamast wasn't doing anything when it's not in aimesh config. Likely I don't completely understand how it works in different mode?

And I have another issue with aimesh, which I should probably start a different thread.

Feels like maybe I shouldn't switch to aimesh mode... and should go back to main router + APs mode... sigh...

Thanks in advance for any pointers/suggestions.

-Alan

I have a AC86 as a aimesh node and see tons of similar kernel errors. I don't see the line about 'unhandled level 3 translation fault' but the other lines below roamast.

Mar 10 21:38:41 roamast: determine candidate node [xx:xx:xx:xx:xx:xx](rssi: -61dbm) for client [xx:xx:xx:xx:xx:xx(rssi: -76dbm) to roam
Mar 10 21:38:41 kernel: pgd = ffffffc014c89000
Mar 10 21:38:41 kernel: [00000000] *pgd=0000000015371003, *pud=0000000015371003, *pmd=00000000139c5003, *pte=0000000000000000
Mar 10 21:38:41 kernel: CPU: 0 PID: 9864 Comm: roamast Tainted: P           O    4.1.27 #2
Mar 10 21:38:41 kernel: Hardware name: Broadcom-v8A (DT)
Mar 10 21:38:41 kernel: task: ffffffc019234100 ti: ffffffc014cf0000 task.ti: ffffffc014cf0000
Mar 10 21:38:41 kernel: PC is at 0xfc8f0
Mar 10 21:38:41 kernel: LR is at 0xf6ecc7d4
Mar 10 21:38:41 kernel: pc : [<00000000000fc8f0>] lr : [<00000000f6ecc7d4>] pstate: 60070010
Mar 10 21:38:41 kernel: sp : 00000000f6e9a308
Mar 10 21:38:41 kernel: x12: 00000000f6fd7c40
Mar 10 21:38:41 kernel: x11: 0000000000000001 x10: 0000000000000001
Mar 10 21:38:41 kernel: x9 : 000000000015783c x8 : 0000000000000000
Mar 10 21:38:41 kernel: x7 : 0000000000000001 x6 : 00000000f7559ce0
Mar 10 21:38:41 kernel: x5 : 00000000f6e9a380 x4 : 00000000f6e9a33c
Mar 10 21:38:41 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Mar 10 21:38:41 kernel: x1 : 0000000000000020 x0 : 0000000000000000

 

[cooloutac]

I just started getting a similar error as OP, level 3 unhandled exception but not romast its with dcd. but it started happening after adding an aimesh node and turning on trend micro. 384.19

 

[chavo]

the same problem RT-AC86U 384.19

May 29 15:37:13 kernel: transmission-da[7176]: unhandled level 2 translation fault (11) at 0x00000000, esr 0x92000046
May 29 15:37:13 kernel: pgd = ffffffc01c81c000
May 29 15:37:13 kernel: [00000000] *pgd=0000000031f7c003, *pud=0000000031f7c003, *pmd=0000000000000000
May 29 15:37:13 kernel: CPU: 0 PID: 7176 Comm: transmission-da Tainted: P           O    4.1.27 #2
May 29 15:37:13 kernel: Hardware name: Broadcom-v8A (DT)
May 29 15:37:13 kernel: task: ffffffc03e04e180 ti: ffffffc001b40000 task.ti: ffffffc001b40000
May 29 15:37:13 kernel: PC is at 0x7f8c108948
May 29 15:37:13 kernel: LR is at 0x7f8bf39490
May 29 15:37:13 kernel: pc : [<0000007f8c108948>] lr : [<0000007f8bf39490>] pstate: 20000000
May 29 15:37:13 kernel: sp : 0000007f8b88f3e0
May 29 15:37:13 kernel: x29: 0000007f8b88f3e0 x28: 00000000000004e5
May 29 15:37:13 kernel: x27: 0000007f85f20090 x26: 0000007f772d2dc0
May 29 15:37:13 kernel: x25: 0000000000004000 x24: 0000007f8c108850
May 29 15:37:13 kernel: x23: 0000000000000442 x22: 0000000000000442
May 29 15:37:13 kernel: x21: 0000000000004000 x20: 0000007f765ea6f0
May 29 15:37:13 kernel: x19: fffffffffffffbbe x18: 00000000000000a1
May 29 15:37:13 kernel: x17: 0000007f8bf39510 x16: 000000000047a7b0
May 29 15:37:13 kernel: x15: 0000007f840000b0 x14: 0000000000000000
May 29 15:37:13 kernel: x13: 2b7b4034029f9282 x12: 90e794ea1071cd9d
May 29 15:37:13 kernel: x11: 0000000000000000 x10: 0000000000000007
May 29 15:37:13 kernel: x9 : 000000000000270f x8 : 00000000000000de
May 29 15:37:13 kernel: x7 : 31cd77f816aa2a66 x6 : ea7e99c223a123c0
May 29 15:37:13 kernel: x5 : 0000000000000442 x4 : 0000007f765eb2d8
May 29 15:37:13 kernel: x3 : 0000000000000000 x2 : 0000000000000442
May 29 15:37:13 kernel: x1 : 0000007f765eae96 x0 : 0000000000000000

 

[ColinTaylor]

the same problem RT-AC86U 384.19

Your error is different. Your's is with Transmission (transmission-da).