What's new

Asus AC68U panic ( reboots )

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

NickG

New Around Here
Hi all
My router again has started to randomly reboot , really cant put my finger on what is causing it, very very random. I did have this same issue a couple of months ago or so and ended up flashing the router and then setting everything back up.
This time i have set the router to send the logs to Splunk so had a look as these are the last logs i am seeing before a gap ( reboot )

Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c02cc438>] (panic+0x7c/0x1a8) from [<c00416f8>] (die+0x1ac/0x1dc)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c02cc438>] (panic+0x7c/0x1a8)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c016bdec>] (xz_dec_run+0x6ec/0xc68) from [<c01226c4>] (squashfs_xz_uncompress+0x108/0x254)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c016d6d4>] (xz_dec_lzma2_run+0x698/0x898) from [<c016bdec>] (xz_dec_run+0x6ec/0xc68)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c016c780>] (lzma_main+0x1dc/0xa98) from [<c016d6d4>] (xz_dec_lzma2_run+0x698/0x898)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0387b08>] (__irq_svc+0x48/0xe8) from [<c016c780>] (lzma_main+0x1dc/0xa98)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0387fe0>] (asm_do_IRQ+0x60/0xbc) from [<c0387b08>] (__irq_svc+0x48/0xe8)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c00678ec>] (irq_exit+0x58/0x6c) from [<c0387fe0>] (asm_do_IRQ+0x60/0xbc)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0388388>] (__do_softirq+0xac/0x148) from [<c00678ec>] (irq_exit+0x58/0x6c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c037c3a4>] (net_rx_action+0xb0/0x17c) from [<c0388388>] (__do_softirq+0xac/0x148)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c01f8d00>] (process_backlog+0x108/0x1e4) from [<c037c3a4>] (net_rx_action+0xb0/0x17c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c01f8194>] (__netif_receive_skb+0x164/0x54c) from [<c01f8d00>] (process_backlog+0x108/0x1e4)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c02b7c5c>] (br_handle_frame+0x194/0x24c) from [<c01f8194>] (__netif_receive_skb+0x164/0x54c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0221054>] (nf_hook_slow+0xa4/0x178) from [<c02b7c5c>] (br_handle_frame+0x194/0x24c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c037d4c4>] (nf_iterate+0x94/0xb4) from [<c0221054>] (nf_hook_slow+0xa4/0x178)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf00cdf8>] (emf_br_pre_hook+0xd0/0x110 [emf]) from [<c037d4c4>] (nf_iterate+0x94/0xb4)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf00b6a0>] (emfc_input+0x1e8/0x318 [emf]) from [<bf00cdf8>] (emf_br_pre_hook+0xd0/0x110 [emf])
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf0142d4>] (igsc_emf_enabled+0x7c/0xa4 [igs]) from [<bf00b6a0>] (emfc_input+0x1e8/0x318 [emf])
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf014e18>] (igsc_sdb_member_add+0xfc/0x348 [igs]) from [<bf0142d4>] (igsc_emf_enabled+0x7c/0xa4 [igs])
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf014e18>] (PC is at igsc_sdb_member_add+0xfc/0x348 [igs])

I have attached a .txt with about a minute or so of the kernel logs just before the panic.

Anyone have any ideas on how to fix ?
 

Attachments

  • logs.txt
    22.2 KB · Views: 114
Hi all
My router again has started to randomly reboot , really cant put my finger on what is causing it, very very random. I did have this same issue a couple of months ago or so and ended up flashing the router and then setting everything back up.
This time i have set the router to send the logs to Splunk so had a look as these are the last logs i am seeing before a gap ( reboot )

Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c02cc438>] (panic+0x7c/0x1a8) from [<c00416f8>] (die+0x1ac/0x1dc)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0043ff8>] (unwind_backtrace+0x0/0xf8) from [<c02cc438>] (panic+0x7c/0x1a8)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c016bdec>] (xz_dec_run+0x6ec/0xc68) from [<c01226c4>] (squashfs_xz_uncompress+0x108/0x254)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c016d6d4>] (xz_dec_lzma2_run+0x698/0x898) from [<c016bdec>] (xz_dec_run+0x6ec/0xc68)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c016c780>] (lzma_main+0x1dc/0xa98) from [<c016d6d4>] (xz_dec_lzma2_run+0x698/0x898)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0387b08>] (__irq_svc+0x48/0xe8) from [<c016c780>] (lzma_main+0x1dc/0xa98)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0387fe0>] (asm_do_IRQ+0x60/0xbc) from [<c0387b08>] (__irq_svc+0x48/0xe8)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c00678ec>] (irq_exit+0x58/0x6c) from [<c0387fe0>] (asm_do_IRQ+0x60/0xbc)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0388388>] (__do_softirq+0xac/0x148) from [<c00678ec>] (irq_exit+0x58/0x6c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c037c3a4>] (net_rx_action+0xb0/0x17c) from [<c0388388>] (__do_softirq+0xac/0x148)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c01f8d00>] (process_backlog+0x108/0x1e4) from [<c037c3a4>] (net_rx_action+0xb0/0x17c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c01f8194>] (__netif_receive_skb+0x164/0x54c) from [<c01f8d00>] (process_backlog+0x108/0x1e4)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c02b7c5c>] (br_handle_frame+0x194/0x24c) from [<c01f8194>] (__netif_receive_skb+0x164/0x54c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c0221054>] (nf_hook_slow+0xa4/0x178) from [<c02b7c5c>] (br_handle_frame+0x194/0x24c)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<c037d4c4>] (nf_iterate+0x94/0xb4) from [<c0221054>] (nf_hook_slow+0xa4/0x178)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf00cdf8>] (emf_br_pre_hook+0xd0/0x110 [emf]) from [<c037d4c4>] (nf_iterate+0x94/0xb4)
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf00b6a0>] (emfc_input+0x1e8/0x318 [emf]) from [<bf00cdf8>] (emf_br_pre_hook+0xd0/0x110 [emf])
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf0142d4>] (igsc_emf_enabled+0x7c/0xa4 [igs]) from [<bf00b6a0>] (emfc_input+0x1e8/0x318 [emf])
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf014e18>] (igsc_sdb_member_add+0xfc/0x348 [igs]) from [<bf0142d4>] (igsc_emf_enabled+0x7c/0xa4 [igs])
Jul 30 15:31:40 192.168.1.1 Jul 30 15:31:40 DSL-AC68U-6CC8-909676F-C kernel: [<bf014e18>] (PC is at igsc_sdb_member_add+0xfc/0x348 [igs])

I have attached a .txt with about a minute or so of the kernel logs just before the panic.

Anyone have any ideas on how to fix ?

What firmware version and are you resetting that firmware before configuring it?

OE
 
So for firmware i had installed before was
Version 3.0.0.4.384_81981 . When i reset it i did the whole reset to factory settings etc and then updated it to the mentioned firmware and then configured it.
I just installed the latest firmware which came out 2 weeks ago or so hoping it might be ok...
 
So for firmware i had installed before was
Version 3.0.0.4.384_81981 . When i reset it i did the whole reset to factory settings etc and then updated it to the mentioned firmware and then configured it.
I just installed the latest firmware which came out 2 weeks ago or so hoping it might be ok...

Read this to understand why to reset after installing firmware:

OE
 

Similar threads

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