1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

assertion (!tcp_write_queue_empty(sk)) | Once that error pops up, N16 crashes

Discussion in 'Tomato Firmware' started by remlei, May 31, 2014.

  1. remlei

    remlei Networkin' Nut Member

    This is usually generated in my RT-N16 and then crash. Under v119 TomatoUSB Shibby

    Code:
    user.err kernel: KERNEL: assertion (!tcp_write_queue_empty(sk)) failed at net/ipv4/tcp_timer.c (285)
    The cause is unknown but I use it only for tranmission and pyload (all routing capabilities is disabled) via optware.

    N16 is connected to N10u (which is working fine)as the main router.

    Once the router crashes, everything is unavailable from transmission to pyload, from webui of tomato and dropbear. But N16 is still pingable by its static IP address.

    According to logs, that is stored under my cifs partition (mounted under N10u storage since Id rather store my logs there) and the certain error always pops up when router crashes.

    Any help will be appreciated.
     
  2. mstombs

    mstombs Network Guru Member

    assertion failure in the kernel is likely to be pretty fatal - but actually means there is an a compiler option to speed to not check to speed things up for others...
    Pretty likely you are running out of socket memory - suggest reduce No of peers/connections
     
  3. remlei

    remlei Networkin' Nut Member

    I set transmission with 150 connection with 30 connections open on downloading torrents and 10 connection for seeding, only 1 torrent is downloading with 25peers connected. and other 3 torrents are seeding.

    i got it lowered to 50 connection with 20 connections for download and 2 connection for seeding, still the issue is present. Now I tried terminating the optware application unmounting any USB drives and let it run standby for 3 hours, but heck it still crashed with the same error. It just sitting idle without doing anything as N10u is handling the routing stuff to internet.

    The fix that I know for now is to activate the WAN feature and let it do it self the NAT. And router gets stable for hours and hours without crash.
     

Share This Page