From owner-freebsd-bugs@FreeBSD.ORG Fri Apr 18 15:46:19 2014 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9EF04ACD for ; Fri, 18 Apr 2014 15:46:19 +0000 (UTC) Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5ED1F1DB1 for ; Fri, 18 Apr 2014 15:46:19 +0000 (UTC) Received: by mail-yk0-f180.google.com with SMTP id 19so1479263ykq.25 for ; Fri, 18 Apr 2014 08:46:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=k9feaKgJgdHveNJUTBaDo3gldu9aeiJ8bfoaFX+ye08=; b=oyK1ktktTXMjTg0ODAYwLQt2DtzJK2kH211ZXwsI6U4x6WW6OGDjgdxzyA/oQhqF8F G6sGFP5AHJaRHtfXpldtHjgnd8TAajy7zT2uX31oA89TZiMUy4jZDkMOvZWhwXDm8y2v ad5GGmQlRsf6n0v0KaEMe5LcqEPvsdn36PGuOonIK2KIAvWlqT1rWb9pmgC7WGeRV0sY Hb0NNRjWyZ+GGTiTA+fGLTWDVy5SPc624x2EE2LiQpv42UCL+tHuB1mEolu2SZo0Lj2g hrIUt3zVs1xhBJEp8DGmnyxV0zxazaSPgrHgnpaiVuAd6cwwzgNfMy0Yr1k+g4BOCVk9 Fswg== X-Received: by 10.236.206.166 with SMTP id l26mr1952952yho.105.1397835978587; Fri, 18 Apr 2014 08:46:18 -0700 (PDT) Received: from [192.168.1.76] (75-63-29-182.lightspeed.irvnca.sbcglobal.net. [75.63.29.182]) by mx.google.com with ESMTPSA id t9sm54214501yhg.18.2014.04.18.08.46.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Apr 2014 08:46:18 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Solarflare LACP bug? From: aurfalien In-Reply-To: Date: Fri, 18 Apr 2014 08:46:16 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <29406A3B-ACDF-4B8F-9E8A-D78A33758C85@gmail.com> References: <7977DD1B-BB2A-4E36-AFBD-51E7AB7F498B@gmail.com> To: hiren panchasara X-Mailer: Apple Mail (2.1874) Cc: freebsd-bugs@freebsd.org X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2014 15:46:19 -0000 On Apr 17, 2014, at 11:09 AM, hiren panchasara = wrote: > On Wed, Apr 16, 2014 at 7:01 PM, aurfalien = wrote: >> Hi, >>=20 >> I=92ve a Solarflare SFN5162F dual port 10Gb ethernet adapter. >>=20 >> While the card works fine as individual ports, upon configuring LACP = the machine suddenly reboots. >>=20 >> Here are my commands; >>=20 >> ifconfig sfxge0 up >> ifconfig sfxge1 up >> ifconfig lagg0 create >> * ifconfig lagg0 up laggproto lacp laggport sfxge0 laggport sfxge1 = 10.0.10.99/16 >>=20 >> * This is were the system reboots. >>=20 >> I believe this to be a bug, what other info can I supply to help = determine if it is or simply user error? >=20 > I do not know much about LACP or solarflare but you can start with > following and someone with more knowledge in that area will help you: Hi Hiren and many thanks for the reply. > - FreeBSD version you are using - uname -a I=92m using both the latest version of FreeBSD 9.2 and 10. > - ifconfig output lagg0: flags=3D8843 metric 0 mtu = 9000 = options=3Dc07ab = capabilities=3Dc07ab ether 00:0f:53:08:44:7c inet 10.0.10.99 netmask 0xffff0000 broadcast 10.0.255.255 nd6 options=3D9 media: Ethernet autoselect status: active supported media: media autoselect laggproto lacp lagghash l2,l3,l4 laggport: sfxge1 flags=3D1c laggport: sfxge0 flags=3D1c > - Any errors you see in /var/log/messages or dmesg. No errors in logs as the system suddenly dumps and reboots uncleanly. = However I=92ll look to enable crash dumps on these particular systems. > - turn on any debugging knobs available with your card drivers I=92ll look into enabling that. I don=92t think any one in tech has the = luxury of saying =93I don=92t know=94 and instead must say =93I=92ll = look into that=94 :) I was first made aware of this issue using FreeNAS and figured to test = the upstream providers warez so to speak. The problem persists as I = expected and do have there crash dumps, just not FreeBSDs crash dumps. Something about tripping an assert. I don=92t think FreeNAS can do much = about it as the problem lies in the FreeBSD Solarflare driver. Kind of = kicking myself with going bleeding edge on the NIC but the Solarflare = sounded soo good on paper. I would say that if the drivers in FreeBSD were as mature as Intel, then = Solarflare for the win for sure. But its all about the drivers. - aurf "Janitorial Services"=