AT&T Community Forums

System log flooded with warnings, can't open DHCP page on PACE 5268

When I try to open the DHCP page on my Pace 5268, the page just sits there blank while the loading icon spins by the tab name. This happens on any browser I try (Chrome, FF, Edge). I have rebooted a few times. This last time I went into the system logs and cleared it. When to the DHCP page, then back to the logs and it is filled with warnings that I have no idea what they mean. Here is just the first page of them, and they continually get longer the longer I wait for the page to load (currently I've waited up to 20 minutes)

System Log Lists

Type	Date/Time	Event Description
warn	Nov 12 07:50:37	kern: kernel: [ 2589.186000] ---[ end trace f8aeb6cb676dd0aa ]---
warn	Nov 12 07:50:37	kern: kernel: [ 2589.184000]
warn	Nov 12 07:50:37	kern: kernel: [ 2589.170000] FAP1: [0]:0000fabf [1]:00000a16 [2]:00000000 [3]:00000000 [4]:00000000 [5]:00000000 [6]:00000000 [7]:00000000 [8]:00000000 [9]:00000000
warn	Nov 12 07:50:37	kern: kernel: [ 2589.157000] FAP0: [0]:0000fabf [1]:00000a16 [2]:00000000 [3]:00000000 [4]:00000000 [5]:00000000 [6]:00000000 [7]:00000000 [8]:00000000 [9]:00000000
warn	Nov 12 07:50:37	kern: kernel: [ 2589.154000] FAP Information:
warn	Nov 12 07:50:37	kern: kernel: [ 2589.152000]
warn	Nov 12 07:50:37	kern: kernel: [ 2589.147000] [<80015648>] kernel_thread_helper+0x10/0x18
warn	Nov 12 07:50:37	kern: kernel: [ 2589.143000] [<80051128>] kthread+0x90/0x98
warn	Nov 12 07:50:37	kern: kernel: [ 2589.136000] [<c091301c>] bcm63xx_enet_rx_thread+0x1b0/0x4c0 [bcm_enet]
warn	Nov 12 07:50:37	kern: kernel: [ 2589.131000] [<8003928c>] local_bh_enable+0xe0/0xec
warn	Nov 12 07:50:37	kern: kernel: [ 2589.127000] [<800390b8>] do_softirq+0xa4/0xac
warn	Nov 12 07:50:37	kern: kernel: [ 2589.122000] [<80038ce4>] __do_softirq+0x10c/0x1dc
warn	Nov 12 07:50:37	kern: kernel: [ 2589.117000] [<802f5e70>] net_rx_action+0x1c0/0x2c4
warn	Nov 12 07:50:37	kern: kernel: [ 2589.112000] [<802f45cc>] process_backlog+0xf8/0x20c
warn	Nov 12 07:50:37	kern: kernel: [ 2589.106000] [<802f4394>] __netif_receive_skb+0x584/0x6c4
warn	Nov 12 07:50:37	kern: kernel: [ 2589.100000] [<803562ec>] ip_local_deliver_finish+0x128/0x354
warn	Nov 12 07:50:37	kern: kernel: [ 2589.096000] [<8037c008>] tcp_v4_rcv+0x9b0/0xac0
warn	Nov 12 07:50:37	kern: kernel: [ 2589.091000] [<803796e4>] tcp_v4_do_rcv+0x138/0x39c
warn	Nov 12 07:50:37	kern: kernel: [ 2589.085000] [<80371e98>] tcp_rcv_established+0x1b0/0x788
warn	Nov 12 07:50:37	kern: kernel: [ 2589.080000] [<80375784>] __tcp_push_pending_frames+0x30/0xa4
warn	Nov 12 07:50:37	kern: kernel: [ 2589.075000] [<80374dd8>] tcp_write_xmit+0x178/0xa90
warn	Nov 12 07:50:37	kern: kernel: [ 2589.069000] [<80374160>] tcp_transmit_skb+0x430/0x9a0
warn	Nov 12 07:50:37	kern: kernel: [ 2589.065000] [<8035c4b0>] ip_queue_xmit+0x154/0x40c
warn	Nov 12 07:50:37	kern: kernel: [ 2589.060000] [<8035c320>] ip_local_out+0x14/0x50
warn	Nov 12 07:50:37	kern: kernel: [ 2589.055000] [<8035c2f8>] __ip_local_out+0x1a8/0x1bc
warn	Nov 12 07:50:37	kern: kernel: [ 2589.050000] [<80337868>] nf_hook_slow+0x94/0x17c
warn	Nov 12 07:50:37	kern: kernel: [ 2589.046000] [<8033775c>] nf_iterate+0xb8/0x130
warn	Nov 12 07:50:37	kern: kernel: [ 2589.038000] [<c1b7260c>] dmz_ip_pkt_handler_local_out+0x130/0x190 [pace_flowmgr]
warn	Nov 12 07:50:37	kern: kernel: [ 2589.033000] [<802fac60>] dev_queue_xmit+0x4e8/0x6e8
warn	Nov 12 07:50:37	kern: kernel: [ 2589.027000] [<802fa614>] dev_hard_start_xmit+0x538/0x69c
warn	Nov 12 07:50:37	kern: kernel: [ 2589.022000] [<802f6808>] skb_checksum_help+0x190/0x198
warn	Nov 12 07:50:37	kern: kernel: [ 2589.017000] [<80462a4c>] skb_warn_bad_offload+0xb0/0xd8
warn	Nov 12 07:50:37	kern: kernel: [ 2589.012000] [<8003233c>] warn_slowpath_fmt+0x2c/0x38
warn	Nov 12 07:50:37	kern: kernel: [ 2589.006000] [<80032288>] warn_slowpath_common+0x78/0xa4
warn	Nov 12 07:50:37	kern: kernel: [ 2589.002000] [<8045f358>] dump_stack+0x8/0x34
warn	Nov 12 07:50:37	kern: kernel: [ 2588.999000] Call Trace:
warn	Nov 12 07:50:37	kern: kernel: [ 2588.998000]
warn	Nov 12 07:50:37	kern: kernel: [ 2588.996000]
warn	Nov 12 07:50:37	kern: kernel: [ 2588.991000] [<80015638>] kernel_thread_helper+0x0/0x18
warn	Nov 12 07:50:37	kern: kernel: [ 2588.987000] [<80051098>] kthread+0x0/0x98
warn	Nov 12 07:50:37	kern: kernel: [ 2588.981000] [<80015648>] kernel_thread_helper+0x10/0x18
warn	Nov 12 07:50:37	kern: kernel: [ 2588.977000] [<80051128>] kthread+0x90/0x98
warn	Nov 12 07:50:37	kern: kernel: [ 2588.971000] [<c0912e6c>] bcm63xx_enet_rx_thread+0x0/0x4c0 [bcm_enet]
warn	Nov 12 07:50:37	kern: kernel: [ 2588.966000] [<802d0000>] nvram_get+0x90/0x104
warn	Nov 12 07:50:37	kern: kernel: [ 2588.961000] [<800518d8>] autoremove_wake_function+0x0/0x50
warn	Nov 12 07:50:37	kern: kernel: [ 2588.955000] [<80466d44>] _raw_spin_lock_irqsave+0x3c/0x4c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.948000] [<c091301c>] bcm63xx_enet_rx_thread+0x1b0/0x4c0 [bcm_enet]
warn	Nov 12 07:50:37	kern: kernel: [ 2588.943000] [<80050c60>] kthread_should_stop+0x0/0x10
warn	Nov 12 07:50:37	kern: kernel: [ 2588.938000] [<8003928c>] local_bh_enable+0xe0/0xec
warn	Nov 12 07:50:37	kern: kernel: [ 2588.933000] [<80460000>] pcpu_dump_alloc_info+0x70/0x338
warn	Nov 12 07:50:37	kern: kernel: [ 2588.928000] [<800390b8>] do_softirq+0xa4/0xac
warn	Nov 12 07:50:37	kern: kernel: [ 2588.924000] [<80040000>] del_timer+0x20/0xb8
warn	Nov 12 07:50:37	kern: kernel: [ 2588.919000] [<80050c60>] kthread_should_stop+0x0/0x10
warn	Nov 12 07:50:37	kern: kernel: [ 2588.913000] [<80460000>] pcpu_dump_alloc_info+0x70/0x338
warn	Nov 12 07:50:37	kern: kernel: [ 2588.908000] [<80038ce4>] __do_softirq+0x10c/0x1dc
warn	Nov 12 07:50:37	kern: kernel: [ 2588.901000] [<c090d434>] bcm63xx_enet_recycle_skb_or_data+0x0/0x30c [bcm_enet]
warn	Nov 12 07:50:37	kern: kernel: [ 2588.896000] [<802f5e70>] net_rx_action+0x1c0/0x2c4
warn	Nov 12 07:50:37	kern: kernel: [ 2588.891000] [<802f45cc>] process_backlog+0xf8/0x20c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.886000] [<8006957c>] ktime_get_real+0x18/0x38
warn	Nov 12 07:50:37	kern: kernel: [ 2588.881000] [<802f4394>] __netif_receive_skb+0x584/0x6c4
warn	Nov 12 07:50:37	kern: kernel: [ 2588.876000] [<803566cc>] ip_local_deliver+0x68/0xb8
warn	Nov 12 07:50:37	kern: kernel: [ 2588.870000] [<803562ec>] ip_local_deliver_finish+0x128/0x354
warn	Nov 12 07:50:37	kern: kernel: [ 2588.865000] [<8037c008>] tcp_v4_rcv+0x9b0/0xac0
warn	Nov 12 07:50:37	kern: kernel: [ 2588.861000] [<80313c20>] _blog_emit+0xbc/0x11c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.856000] [<803796e4>] tcp_v4_do_rcv+0x138/0x39c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.850000] [<80371e98>] tcp_rcv_established+0x1b0/0x788
warn	Nov 12 07:50:37	kern: kernel: [ 2588.845000] [<80375784>] __tcp_push_pending_frames+0x30/0xa4
warn	Nov 12 07:50:37	kern: kernel: [ 2588.839000] [<c1bf4a30>] ipt_do_table+0x57c/0x7d0 [ip_tables]
warn	Nov 12 07:50:37	kern: kernel: [ 2588.833000] [<80374dd8>] tcp_write_xmit+0x178/0xa90
warn	Nov 12 07:50:37	kern: kernel: [ 2588.829000] [<802e9a10>] __alloc_skb+0x74/0x15c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.824000] [<80374160>] tcp_transmit_skb+0x430/0x9a0
warn	Nov 12 07:50:37	kern: kernel: [ 2588.819000] [<802e7a8c>] __skb_clone+0x24/0x154
warn	Nov 12 07:50:37	kern: kernel: [ 2588.815000] [<80013860>] ret_from_irq+0x0/0x4
warn	Nov 12 07:50:37	kern: kernel: [ 2588.810000] [<8035c4b0>] ip_queue_xmit+0x154/0x40c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.805000] [<8035c320>] ip_local_out+0x14/0x50
warn	Nov 12 07:50:37	kern: kernel: [ 2588.800000] [<802e47c4>] __sk_dst_check+0x50/0x74
warn	Nov 12 07:50:37	kern: kernel: [ 2588.796000] [<80359d70>] dst_output+0x0/0x18
warn	Nov 12 07:50:37	kern: kernel: [ 2588.790000] [<800124bc>] plat_irq_dispatch+0x18c/0x310
warn	Nov 12 07:50:37	kern: kernel: [ 2588.785000] [<8035c2f8>] __ip_local_out+0x1a8/0x1bc
warn	Nov 12 07:50:37	kern: kernel: [ 2588.780000] [<80466cd8>] _raw_spin_unlock_bh+0x18/0x38
warn	Nov 12 07:50:37	kern: kernel: [ 2588.775000] [<8007cdfc>] generic_handle_irq+0x3c/0x5c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.770000] [<80359d70>] dst_output+0x0/0x18
warn	Nov 12 07:50:37	kern: kernel: [ 2588.765000] [<80466bc0>] _raw_spin_unlock+0x10/0x40
warn	Nov 12 07:50:37	kern: kernel: [ 2588.760000] [<80080e98>] handle_level_irq+0xe4/0x138
warn	Nov 12 07:50:37	kern: kernel: [ 2588.756000] [<80337868>] nf_hook_slow+0x94/0x17c
warn	Nov 12 07:50:37	kern: kernel: [ 2588.751000] [<80359d70>] dst_output+0x0/0x18
warn	Nov 12 07:50:37	kern: kernel: [ 2588.747000] [<80359d70>] dst_output+0x0/0x18
warn	Nov 12 07:50:37	kern: kernel: [ 2588.742000] [<8033775c>] nf_iterate+0xb8/0x130
warn	Nov 12 07:50:37	kern: kernel: [ 2588.736000] [<80466c04>] _raw_spin_unlock_irqrestore+0x14/0x70
warn	Nov 12 07:50:37	kern: kernel: [ 2588.731000] [<8007d840>] handle_irq_event_percpu+0xd4/0x224
warn	Nov 12 07:50:37	kern: kernel: [ 2588.723000] [<c1b7260c>] dmz_ip_pkt_handler_local_out+0x130/0x190 [pace_flowmgr]

Responses

Lonewolf147

Contributor

•

4 Messages

1 year ago

Just a follow up. I went to the page and left the house. Got home 2.5 hours later and the page had finally loaded.

0

ATTHelp

Community Support

•

231.5K Messages

1 year ago

Hi there, @Lonewolf147. Looks like your router is slow to load its DHCP page. Let's look at this together.

When it comes to a slow loading router GUI(graphical user interface), a good rule of thumb is, that you need to plugged directly into the routers Ethernet port and not work via Wi-Fi.

Once thing that you can to do remedy this concern is to factory reset the router. Warning: This will delete all custom settings and will revert the router back to its off-the line state. Here are the steps:

Press and hold the gateway Reset button for at least 10 seconds. If you let go before 10 seconds, the gateway will reboot, but it won’t reset.
Wait until the gateway restarts and all the status lights are lit.
See if the Broadband or Service status lights are solid green. If so, the reset worked.

A question for you.

When was the last that the rouiter has been replaced? The reason why we need to know that is the router could be at the end of its shelf life.

Try the factory reset above, and if it doesn't work then we can think about either sending a tech with a replacement router or we can send to on to you by mail.

Please let us know what you would like to do.

Matthew, AT&T Community Specialist

0

Lonewolf147

Contributor

•

4 Messages

1 year ago

This is the original router that I was issued when I got my fiber service. I tried a factory reset and reset my network settings. I'm still getting the same issue. Do you think a new router would be a good next step?

0

ATTHelp

Community Support

•

231.5K Messages

1 year ago

Welcome back, @Lonewolf147. Thanks for the update.

Sine the resolution we recommended did not work, then it might be that the router has come to the end of its shelf life. So getting a replacement, would be a great idea. We can look into that with you.

In order for us to proceed, please accept this invitation to join us in the AT&T Direct Message space. You will see a chat icon, next to a bell icon, in the upper right corner of this thread, next to your Forums profile icon. Our next message will appear there.

In the meantime, please gather your account information together. Do not post it publicly. We will ask for it in the Direct Message space. Also, think about how you would like to have the replacement delivered to you. We have two choices: