From owner-freebsd-hardware@FreeBSD.ORG Sat Nov 14 21:26:31 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74A891065670 for ; Sat, 14 Nov 2009 21:26:31 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 095428FC17 for ; Sat, 14 Nov 2009 21:26:30 +0000 (UTC) Received: by fxm27 with SMTP id 27so4796652fxm.3 for ; Sat, 14 Nov 2009 13:26:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=UGXZHWMgbQFF8w6W1cIh1OD3+MHmMi4ODKuECGzMnjs=; b=ILqUrBRSOemsOEV+1hWzXEGCwTIvnzEqA4rnI+tV1CeGpQIM1hkwy89sKpFrvWzNk6 CQNP9/3e4thzl1l6cAa1blg5l7kxBi4tmuzEkSSrTONGqabn6sj2iCDBF77XfeE5EcZR oiM1ZA/OQdGltv6ygLk82YpG+scPOwS+a1umg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=Wv9WjjHOUBbAjgl6Y/TRVuE6SvgASHo+i9YJN/B1SCleriyZwvYUL2VTGWrhymtOlW aelx05knwR4Sagi/tZdgqPi/HoPmKjpLvj/M56EosGSZjw6Djp5Jj3S8w9cLvDDHmby4 QTJ8g+sORGljxqJYwtU7IJQMX+bNkCMNzkzO4= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.85.69 with SMTP id t47mr1054551wee.107.1258232273079; Sat, 14 Nov 2009 12:57:53 -0800 (PST) In-Reply-To: <4AFF17FF.9020802@quip.cz> References: <4AFF17FF.9020802@quip.cz> From: Ivan Voras Date: Sat, 14 Nov 2009 21:57:33 +0100 X-Google-Sender-Auth: 96287b7911cca61d Message-ID: <9bbcef730911141257w4d7b7f1tc3fb18c5bdcfe57a@mail.gmail.com> To: Miroslav Lachman <000.fbsd@quip.cz> Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Curiously unable to access network - bce, 7.2-RELEASE on a HP blade server X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2009 21:26:31 -0000 2009/11/14 Miroslav Lachman <000.fbsd@quip.cz>: > Ivan Voras wrote: >> >> I forgot to attach hardware details: >> >> bce0: HP NC373i Multifunction Gigabit Server Adapter (B2) ASIC >> 0x57081021 Rev B2 B/C 0x04040105 Flags 2.5G >> >> Additional data point: I cannot reconfigure the card to 100 Mbit >> operation (currently in 1000baseSX autoselect, full-duplex). >> >> Ivan Voras wrote: >>> >>> The symptoms are: >>> >>> * The device (bce0, bce1) comes up, is visible in ifconfig, can be >>> configured, is UP and RUNNING, everything looks fine >>> * Apparently, it simply doesn't work - no ping responses, TCP, nothing >>> * But tcpdump shows that the NIC apparently does receive multicast >>> router announcements, and some broadcast ARP traffic; only unicast >>> seems to be affected. >>> * Running "netstat 1" shows that apparently there are some packets >>> received - once a second or so, and the "err" counters are 0. >>> * Digging further, the dev.bce.0.stat_IfinFramesL2FilterDiscards >>> contains an increasing number, currently arround 57000 and the >>> dev.bce.0.stat_IfHCInBadOctets also contains an increasing number, >>> currently around 450,000, while ...InOctets is around 30,000 and >>> ...OutBadOctets is 0. >>> >>> From the sysctls it looks like maybe it's discarding valid input >>> packets. I've tried disabling rxcsum, txcsum and TSO without effect. >>> >>> I cannot upgrade or install 8.0 because newusb has some problems with >>> the hardware. >>> >>> Any ideas? > > Can it be related to this PR 134788? > http://www.freebsd.org/cgi/query-pr.cgi?pr=134788 > (your problem sounds different, but anyway you can try 7-STABLE bce driver) > > Recent changes in bce driver fixed it for me. I did try booting 8.0 and found the same problem (though I cannot install 8.0 because of an unrelated problem with newusb). Judging by the dates in the PR, the fix should also be present in 8.