Results 1 to 5 of 5

Threaded View

  1. #1
    New ROGer Array
    Join Date
    Jun 2019
    Reputation
    10
    Posts
    5

    GT-AX11000 Stalling

    First time seeing the router itself stalling.

    On my side, the network was unresponsive, including the router's web interface. Could not even talk to the Cable modem via ip or otherwise.

    After rebooting the router, system log showed the following:
    Code:
    Jul  4 15:15:57 kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 3, t=60006 jiffies, g=28202045, c=28202044, q=9370)
    Jul  4 15:15:57 kernel: Call trace:
    Jul  4 15:15:57 kernel: [<ffffffc000085614>] __switch_to+0x64/0x80
    ...
    Jul  4 15:51:57 kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=2220062 jiffies, g=28202045, c=28202044, q=252000)
    Jul  4 15:51:57 kernel: Call trace:
    Jul  4 15:51:57 kernel: [<ffffffc000085614>] __switch_to+0x64/0x80
    Jul  4 15:54:57 kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 2, t=2400071 jiffies, g=28202045, c=28202044, q=272395)
    Jul  4 15:54:57 kernel: Call trace:
    Jul  4 15:54:57 kernel: [<ffffffc000085614>] __switch_to+0x64/0x80
    Jul  4 15:57:57 kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 1, t=2580072 jiffies, g=28202045, c=28202044, q=292541)
    Jul  4 15:57:57 kernel: Call trace:
    Jul  4 15:57:57 kernel: [<ffffffc000085614>] __switch_to+0x64/0x80
    Rebooted router manually and able to get control back, but curious what could have caused it.

    Did check prior to the initial start of the issue and only saw the following in the log:
    Code:
    Jul  4 03:54:18 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6110)]retrieve firmware information
    Jul  4 03:54:18 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6124)]no need to upgrade firmware
    Jul  4 11:55:36 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
    Jul  4 11:55:36 wlceventd: WLCEVENTD wlceventd_proc_event(401): eth6: Disassoc xx:xx:xx:xx:xx:xx, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
    So I have nothing else to really show what may have caused a problem.

    Router would have had about a 8-9 day run time.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •