Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 31 Mar 2010 10:40:48 +0200
From:      Attila Nagy <bra@fsn.hu>
To:        pyunyh@gmail.com
Cc:        Jonathan Feally <vulture@netvulture.com>, Mailing List FreeBSD Stable <freebsd-stable@freebsd.org>, Michael Loftis <mloftis@wgops.com>
Subject:   Re: 8-STABLE freezes on UDP traffic (DNS), 7.x doesn't
Message-ID:  <4BB30A90.1030605@fsn.hu>
In-Reply-To: <20100330180710.GM1473@michelle.cdnetworks.com>
References:  <4BAB718C.3090001@fsn.hu> <886B21E1787F0003B89E34B6@[192.168.1.44]>	<4BB087B7.3030602@fsn.hu>	<20100329183848.GE1473@michelle.cdnetworks.com>	<4BB0FDC6.7050105@fsn.hu>	<20100329194131.GG1473@michelle.cdnetworks.com>	<4BB1CFD1.9040602@fsn.hu> <4BB21EA7.4080107@netvulture.com>	<4BB21F79.5060807@fsn.hu> <20100330180710.GM1473@michelle.cdnetworks.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Pyun YongHyeon wrote:
> On Tue, Mar 30, 2010 at 05:57:45PM +0200, Attila Nagy wrote:
>   
>> Jonathan Feally wrote:
>>     
>>> Attila Nagy wrote:
>>>       
>>>>>>>> Bingo, this solved the problem. The current uptime nears four days.
>>>>>>>> Previously I couldn't go further than a day.
>>>>>>>>
>>>>>>>> The machine gets very light TCP load (and other machines which
>>>>>>>> get work
>>>>>>>> well), so I guess it's UDP RX or TX checksum related
>>>>>>>>           
>>>>>>>>                 
>>> I also have had my network go dead on a recent 8.0-STABLE on bge
>>> system. Console is alive, but network just stops. I am running it as a
>>> router with untagged on bge0 and nat of traffic on vlan201 tagged on
>>> top of bge1. I haven't had it lock up in 3 days, but I will try the
>>> -txcsum and -rxcsum on both interfaces to see if the problem still
>>> persists or not. I do have a lot of tcp traffic, but there is also
>>> unsolicited udp flying in as well.
>>>       
>> Well, it's a short time to judge from, but with rx,txcsum disabled, the
>> machine froze nearly instantly (less than one hour of uptime), while
>> with tso disabled, it still works.
>> So for now I think tso causes the problems.
>> BTW, now that we are talking about that, I remember that I've disabled
>> it on a lot of machines previously, because I've had strange issues.
>>     
>
> Would you show me the dmesg output(only bce(4) part)?
>   
Sure:
bce0: <HP NC373i Multifunction Gigabit Server Adapter (B2)> mem
0xfa000000-0xfbffffff irq 16 at device 0.0 on pci7
miibus0: <MII bus> on bce0
brgphy0: <BCM5708S 1000/2500BaseSX PHY> PHY 2 on miibus0
brgphy0:  1000baseSX-FDX, 2500baseSX-FDX, auto
bce0: Ethernet address: 00:1b:78:75:f0:34
bce0: [ITHREAD]
bce0: ASIC (0x57081021); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); B/C
(4.4.1); Flags (MSI|2.5G)
bce1: <HP NC373i Multifunction Gigabit Server Adapter (B2)> mem
0xf6000000-0xf7ffffff irq 16 at device 0.0 on pci3
miibus1: <MII bus> on bce1
brgphy1: <BCM5708S 1000/2500BaseSX PHY> PHY 2 on miibus1
brgphy1:  1000baseSX-FDX, 2500baseSX-FDX, auto
bce1: Ethernet address: 00:1b:78:75:f0:38
bce1: [ITHREAD]
bce1: ASIC (0x57081021); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); B/C
(4.4.1); Flags (MSI|2.5G)

The NIC's firmware is up to date (latest available on HP firmware update
CD).



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BB30A90.1030605>