Re: Possible kernel bug in tcp.c?

From: Naoki (naoki_at_valuecommerce.com)
Date: 05/31/04

  • Next message: Greg Wildman: "Re: FC2 on Intel 440GX (was FC1 on Intel 440GX)"
    Date: Tue, 01 Jun 2004 01:09:56 +0900
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    
    
    
    Ohh, should mention this is only happening (so far) to my eepro100 machines, the tg3 boxes are ok.
    Will update of that ceases to be the case.
    -n.

    Naoki wrote:
    That's bizarre. 

    These machines that are dying are only running HTTP traffic.  Everything else is firewalled off with iptables and no other services are running.
    It's occurring daily and really worrying me to the point of reverting to 2.4.22.

    Should I attach gdb and try to grab some more info?

    -n.

    xyzzy@hotpop.com wrote:
    On Monday 31 May 2004 11:15, Naoki wrote:
      
    I've got machines crashing under FC2 with kernel 2.6.5-1.358.  Couldn't
    catch the exact kernel messages sorry but here are the rough details.
    
    assertion failed kernel messages.
    
    net/ipv4/tcp.c:1568
    net/ipv4/tcp.c:1632
    
    The ethernet driver is :
    
    e100: Intel(R) PRO/100 Network Driver, 3.0.17
    
    Crashing ( and hanging with these messages scrolling at a hefty rate)
    alsmost daily because of it.
    No problem before with FC1 and 2.4 kernel.
    
    Any ideas?
        
    
    Is this failing on a SAMBA connection?
    
    >From what I can see in the code, it is a BUG_TRAP on the MSG_PEEK flag being 
    set by the time it reaches the tcp code (line 1632 also traps if MSG_TRUNC is 
    set, but I think that the trap at 1568 for MSG_PEEK alone is the relevant 
    one).  SMB, CIF, and NCP are the only network file systems that seem to set 
    this flag.  Also, if you are running on a Sparc64/Solaris.
    
    Looks like some sort of weird networking problem in the 2.6 kernel.
    
    
      


    
    

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Greg Wildman: "Re: FC2 on Intel 440GX (was FC1 on Intel 440GX)"

    Relevant Pages

    • allocation failures with CBQ bandwidth limiting & high net use (was Re: Filesystem kernel hangup
      ... limiting, queuing and prioritization, *and* high network use (using ... "full_kernel_output" file for an idea of what kernel messages I was ... My IRQ is shared with that above TV card, ... kernel messages for about two hours from boot to crash). ...
      (Linux-Kernel)
    • mass "tulip_stop_rxtx() failed", network stops
      ... 02:01.0 Ethernet controller: Linksys NC100 Network Everywhere Fast ... We are running four more machines like that, ... kernel they are running. ... On some of them, there are serious problems with a network, and they ...
      (Linux-Kernel)
    • Re: PROBLEM: Network sky2 Module
      ... They both have this issue with the sky2 network device driver whereby the device would stop working and need to be brought down and back up. ... On the X86_64 kernel on a 100Mbit network, this is a very occasional thing, while on the i386 kernel on a 1Gbit network the device only works for a few minutes at a time. ... If i set the MTU to 7200 then the device seems to stay functional, but then i see long delays when it's talking to 100Mbit devices with standard 1500 MTU that are outside of its LAN segment. ... Yes, I have found that I get far less problem in this area leaving the MTU at 1500, then putting a larger MTU into the routing table for segments, or even just machines, where I know there is direct connectivity. ...
      (Linux-Kernel)
    • First packets not being sent - ARP?
      ... I have two Linux machines connected to each other ... However- I noticed that sometimes the "first" few packets of a message ... *Both machines are running Linux Kernel 2.4.20, ... *Each machine has TWO network cards- one set is connected to a network, ...
      (comp.os.linux.networking)
    • Re: Possible kernel bug in tcp.c?
      ... These machines that are dying are only running HTTP traffic. Everything else is firewalled off with iptables and no other services are running. ... I've got machines crashing under FC2 with kernel 2.6.5-1.358. ... catch the exact kernel messages sorry but here are the rough details. ... SMB, CIF, and NCP are the only network file systems that seem to set this flag. ...
      (Fedora)