Page 4 of 6 FirstFirst ... 2 3 4 5 6 LastLast
Results 31 to 40 of 55
  1. #31
    Banned Array
    Join Date
    Jun 2017
    Reputation
    11
    Posts
    67

    Hi,
    Cables have been changed, different PC used and issue persists. Noticed on the last connection issue when link rate was negotiated and the router crashed that there was a CPU stall:

    Jul 11 11:28:38 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
    Jul 11 11:28:43 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 100 mbps full duplex
    Jul 11 11:28:57 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
    Jul 11 11:29:48 kernel: INFO: rcu_preempt self-detected stall on CPU { 0} (t=6001 jiffies g=114008 c=114007 q=11613)
    Jul 11 11:29:48 kernel: rcu_preempt kthread starved for 6001 jiffies!
    Jul 11 11:29:48 kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected by 2, t=6002 jiffies, g=114008, c=114007, q=11613)
    Jul 11 11:29:48 kernel: Call trace:
    Jul 11 11:29:48 kernel: [<ffffffc00008573c>] __switch_to+0x64/0x80
    Jul 11 11:29:48 kernel: rcu_preempt kthread starved for 6002 jiffies!
    Jul 11 11:29:48 kernel: Call trace:
    Jul 11 11:29:48 kernel: [<ffffffc0000876d8>] dump_backtrace+0x0/0x150
    Jul 11 11:29:48 kernel: [<ffffffc00008783c>] show_stack+0x14/0x20
    Jul 11 11:29:48 kernel: [<ffffffc0000b7afc>] sched_show_task+0xa4/0x100
    Jul 11 11:29:48 kernel: [<ffffffc0000bab28>] dump_cpu_task+0x40/0x50
    Jul 11 11:29:48 kernel: [<ffffffc0000d5ce8>] rcu_dump_cpu_stacks+0xa0/0xf0
    Jul 11 11:29:48 kernel: [<ffffffc0000d9c94>] rcu_check_callbacks+0x4bc/0x8b8
    Jul 11 11:29:48 kernel: [<ffffffc0000dc3d4>] update_process_times+0x3c/0x70
    Jul 11 11:29:48 kernel: [<ffffffc0000ea37c>] tick_nohz_handler+0xa4/0x108
    Jul 11 11:29:48 kernel: [<ffffffc00036da78>] arch_timer_handler_phys+0x30/0x40
    Jul 11 11:29:48 kernel: [<ffffffc0000d1c8c>] handle_percpu_devid_irq+0x7c/0xa0
    Jul 11 11:29:48 kernel: [<ffffffc0000cd9c4>] generic_handle_irq+0x34/0x50
    Jul 11 11:29:48 kernel: [<ffffffc0000cdcd4>] __handle_domain_irq+0x5c/0xb8
    Jul 11 11:29:48 kernel: [<ffffffc000080c20>] gic_handle_irq+0x38/0x90
    Jul 11 11:29:48 kernel: Exception stack(0xffffffc032a2f3a0 to 0xffffffc032a2f4c0)
    Jul 11 11:29:48 kernel: f3a0: fc66ed48 ffffffbf 2e4069c0 ffffffc0 32a2f4e0 ffffffc0 004eab50 ffffffc0
    Jul 11 11:29:48 kernel: f3c0: 80e9c70a 00000000 80e9c308 00000000 00000000 00000000 008fa1d0 ffffff80
    Jul 11 11:29:48 kernel: f3e0: 0000788a 00000000 80666208 00000000 c57eec51 00000000 00000056 00000000
    Jul 11 11:29:48 kernel: f400: 00000008 00000000 fffffee6 00000000 00000000 00000000 a7debb01 00000000
    Jul 11 11:29:48 kernel: f420: 00caa000 ffffff80 00000000 00000000 00000000 00000000 00000000 00000000
    Jul 11 11:29:48 kernel: f440: 00000001 00000000 00000003 00000000 0000001a 00000000 fc66ed48 ffffffbf
    Jul 11 11:29:48 kernel: f460: 2e4069c0 ffffffc0 2e4069c0 ffffffc0 340d1800 ffffffc0 006e0a30 ffffffc0
    Jul 11 11:29:48 kernel: f480: 006e0a20 ffffffc0 00000000 00000000 00000000 00000000 34023000 ffffffc0
    Jul 11 11:29:48 kernel: f4a0: 2e406cc0 ffffffc0 32a2f4e0 ffffffc0 003b9e40 ffffffc0 32a2

  2. #32
    Administrator Array MasterC@ASUS's Avatar
    Join Date
    Aug 2014
    Reputation
    96
    Posts
    1,492

    Hi Mark,
    If you have verified those are not causing the issue, please contact ASUS in your region to have your Rapture looked at. A new firmware will probably not make a difference.

    Thanks.

  3. #33
    Banned Array
    Join Date
    Jun 2017
    Reputation
    11
    Posts
    67

    Had the router swapped out today and will see how it goes. I do however disagree that it was a hardware issue, as most if not all CPU stalls are caused by a problem with the OS. Hence I go back to my original statement that the firmware is more than likely the cause of so many issues experienced by a multitude of users.

    Regards
    Mark

  4. #34
    Banned Array
    Join Date
    Jun 2017
    Reputation
    11
    Posts
    67

    Well new replacement router does this same with link negotiation (though the router has not crashed yet) starting at lowest speed in example below 10 mbps full duplex then dropping and renegotiating at 1000 mbps full duplex. This indicates an issue with the software and not hardware as protocol for negotiation should start at the highest speed and drop down not vice versa.
    This is another of the many problems that needs to be addressed in the next firmware update. Any approx eta for new firmware as the synology RT2600AC is starting to look good from a stability viewpoint?


    Jul 12 15:41:57 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
    Jul 12 15:42:03 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 10 mbps full duplex
    Jul 12 15:42:04 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link DOWN.
    Jul 12 15:42:08 kernel: eth2 (Ext switch port: 1) (Logical Port: 9) Link UP 1000 mbps full duplex

    Regards
    Mark
    Last edited by MarkSW; 07-12-2017 at 04:00 AM.

  5. #35
    Administrator Array MasterC@ASUS's Avatar
    Join Date
    Aug 2014
    Reputation
    96
    Posts
    1,492

    Hi Mark,
    If the same thing happened again with a new router, you need to consider the possibility your network card or cable is causing this issue. Firmware cannot fix hardware issues.

  6. #36
    Banned Array
    Join Date
    Jun 2017
    Reputation
    11
    Posts
    67

    Hi,

    Changed back to old router RT-N66U and no issues negotiating link. Tried with a different PC and new router = link negotiating issue!
    While I appreciate your input regarding hardware can you explain to me why on firmware 11243 it will negotiate twice (as above) to get full speed, yet with firmware 12184 it will negotiate 3-4 times to get full speed (and sometimes crash)? To me this says it is the OS controlling the negotiation - correct me if I am wrong.

    Regards
    Mark

  7. #37
    Banned Array
    Join Date
    Jun 2017
    Reputation
    11
    Posts
    67

    Another CPU stall occurred - this happened when 5 people were connected 2 of which were streaming. Correct me if I am wrong but a CPU stall is generally caused by a software issue. There are numerous people online complaining of sporadic reboots, some of which occur when the router is under load. Surely all of these people cannot have faulty hardware and in my personal opinion this is indicative of poorly compiled software/software issues.
    I am prepared to give this router a go if newer firmware is available but at this time the RT2600AC is looking mighty appealing.

    Regards
    Mark

  8. #38
    Administrator Array MasterC@ASUS's Avatar
    Join Date
    Aug 2014
    Reputation
    96
    Posts
    1,492

    Hi Mark,

    I am still not able to replicate your issue, nor am I able to find any extra info from other cases of sporadic reboots on our forum and SmallNetBuilder's. We have people looking at your system log now, not in real-time of course

    If it is indeed the firmware, we won't have an ETA for the next update until that is confirmed.

    For now, it would help us if you please private message me:
    1. Your place of purchase, and which service center/store provided the replacement.
    2. Exactly what hardware you have connected to the ports which are having link negotiation issues.
    3. References of any other users who are experiencing random reboots.

    Thanks Mark.

  9. #39
    Banned Array
    Join Date
    Jun 2017
    Reputation
    11
    Posts
    67

    PM sent.

  10. #40
    Banned Array
    Join Date
    Jun 2017
    Reputation
    11
    Posts
    67

    Update:
    I have narrowed down some of my issues to a combination of firmware and Game ports 1 and 2. These test were carried out by hot plugging the PC LAN cable into all of the routers LAN ports and also disabling and re-enabling the network adapter on the Win 10 PC, which simulates the PC going into sleep mode and waking up and where some of my issues also occurred, such as router GUI slow down, reboots and CPU stalls.
    Latest firmware 12184:
    Game ports 1 and 2- any link negotiation intermittently occurs with lower speed being negotiated first (sometimes 10 or 100 Mbps or both)this is then dropped and then 1000 Mbps is negotiated where it stays. Ports 3 and 4 negotiate at 1000 Mbps straight off the bat. Ports 5-8 show no negotiation in the system log but all connect at 1000 Mbps.
    Older firmware 11243:
    Ports 1and 2 will negotiate at 1000 Mbps most times and are shown in the system log. Ports 3-8 show no negotiation in the system log but all connect at 1000 Mbps. The older firmware tends to work much better when it comes to link negotiation.
    GUI slowdown and slow speeds only occur on Game ports 1 and 2 and this is generally when the PC comes out of sleep or when the network cable is unplugged then plugged back, or when a change is done to the router such as DHCP mapping, which results in the router rebooting and the port links must be negotiated again. Although the links on the port show a link of 1000 Mbps has been negotiated, router speeds are significantly reduced and actual throughput on ports 1 and 2 is only 3-5 Mbps when tested on Speedtest. However, unplugging and re-plugging the LAN cable or disabling and re-enabling the network connection on the PC results in my full download speed of 100 Mbps being attained. It is also important to note that I had a switch plugged into Game port 2, through which a lot of the household traffic was coming. Since moving this switch cable to another port issues have been significantly reduced.
    All of this in my opinion point to the issue being with the firmware and some sort of underlying problem with the switch software in the firmware specifically relating to the "Special Game Ports" 1 and 2.
    Please feel free to correct me if you think my analyses might be wrong or if you have any suggestions.

    Regards
    Mark

Page 4 of 6 FirstFirst ... 2 3 4 5 6 LastLast

Posting Permissions

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