Date: Thu, 13 Sep 2012 21:47:15 +0200 From: Giulio Ferro <auryn@zirakzigil.org> To: freebsd-net@freebsd.org, "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Issue with igb and lagg (was Re: Problem with link aggregation + sshd) Message-ID: <50523843.8040006@zirakzigil.org> In-Reply-To: <CAOjFWZ47wES2RdkuftP7FGJqwDFN=t6z%2Bjbh6zSeuLJGJas81w@mail.gmail.com> References: <5033FB17.7020600@zirakzigil.org> <503884A0.50708@zirakzigil.org> <FF06542A-9507-4C8C-99EC-8275B04D4CF1@my.gd> <E183609A-19E1-4EF4-B08D-FAA55779E193@my.gd> <503BC8F5.3040208@zirakzigil.org> <CAE63ME6oi_5Yam5wXuJzYBhhv%2BN6MnQPOXReXo2Ugo1hjvv25Q@mail.gmail.com> <503E7A16.6030600@zirakzigil.org> <5044F62E.8030001@zirakzigil.org> <CAPyG9gMaNnLJOE00bH66qpAoJfdU=YtpUvz24fj%2B1nyvjDDCAg@mail.gmail.com> <504FA735.709@zirakzigil.org> <CAOjFWZ4kr3sVmymCgh5Fchhm2QR42GAquwHhdgA=MBLY4U-xhA@mail.gmail.com> <5050E107.6090403@zirakzigil.org> <CAOjFWZ682YTzN-PQwujdm=kVvyQpJzNb7wtbVNZnMcjOn_gFeg@mail.gmail.com> <CAFOYbcmXv7d7=mfafR3JsEkwgSN1dZtmvqmp1p2PXyV27oH9GQ@mail.gmail.com> <CAOjFWZ47wES2RdkuftP7FGJqwDFN=t6z%2Bjbh6zSeuLJGJas81w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/12/2012 10:51 PM, Freddie Cash wrote: > On Wed, Sep 12, 2012 at 1:48 PM, Jack Vogel <jfvogel@gmail.com> wrote: >> On Wed, Sep 12, 2012 at 12:40 PM, Freddie Cash <fjwcash@gmail.com> wrote: >>> Thanks for checking. I've used lagg(4) with igb, just not on 9.x. >>> >>> You're right, it seems to be pointing to the igb(4) driver in 9.x >>> compared to < 9.0. >>> >> How do you determine that since it doesn't happen without lagg? I've no >> reports of igb hanging otherwise and its being used extensively. > > Well, I did say "seems to". :) > > igb+lagg worked for us on 8.3. Haven't tried it since moving to 9.0 > and 9-STABLE on those three boxes. > > igb+lagg doesn't work for him on 9.0. Although, I don't recall if > non-LACP options were tried earlier in this thread, or if it's just > the LACP mode that's failing. If one mode works (say failover) and > LACP mode doesn't, that "seems to" point to lagg. Sorry, forgot to mention it. I tried both failover and lacp: neither worked. The switch is a Dell powerconnect 6248 with ports configured for aggragation. I first tried on a 9.1 prerelease, then on a 9.0 release to have everything clean. In both ssh, both as server and as client, become unresponsive and unkillable. The problem might also lie within ssh/d, but I somehow doubt it. I haven't tried other network services.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50523843.8040006>