From: Daniel Feenberg
To: Alexander V. Chernikov
Cc: Barney Cordoba ; "freebsd-net@freebsd.org"
Sent: Friday, July 26, 2013 4:59 PM
Subject: Re: Recommendations for 10gbps NIC
On Fri, 26 Jul 2013, Alexander V. Chernikov wrote:
> On 26.07.2013 19:30,
Old Synopsis: SCTP connection hangs on COOKIE_ECHOED
New Synopsis: [sctp] SCTP connection hangs on COOKIE_ECHOED
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Fri Jul 26 21:45:01 UTC 2013
Responsible-Changed-Why:
Over to maintaine
Old Synopsis: bluetooth takes 30-50 attempts to pair to keyboard and will not
re-connect
New Synopsis: [bluetooth] bluetooth takes 30-50 attempts to pair to keyboard
and will not re-connect
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed
On Fri, 26 Jul 2013, Alexander V. Chernikov wrote:
On 26.07.2013 19:30, Barney Cordoba wrote:
*From:* Alexander V. Chernikov
*To:* Boris Kochergin
*Cc:* freebsd-net@freebsd.org
*Sent:* Thursday, July 25, 2013 2:10 PM
My only experience with 10gbps on FreeBSD is on my friend's server --
Solarstorm SFN5161T 10GBASE-T Server Adapter
I guess the model you'd want is the SFN5162F and then you put in any
SFP+ adapters you want, so this would cover your 10GBASE-SR requirement.
The driver is new as of 9.1-RELEASE. I
On 26.07.2013 19:30, Barney Cordoba wrote:
*From:* Alexander V. Chernikov
*To:* Boris Kochergin
*Cc:* freebsd-net@freebsd.org
*Sent:* Thursday, July 25, 2013 2:10 PM
*Subject:* Re: Recommendations for 10gbps NIC
On 25.0
From: Alexander V. Chernikov
To: Boris Kochergin
Cc: freebsd-net@freebsd.org
Sent: Thursday, July 25, 2013 2:10 PM
Subject: Re: Recommendations for 10gbps NIC
On 25.07.2013 00:26, Boris Kochergin wrote:
> Hi.
Hello.
>
> I am looking for recommendations f
Hello list!
Currently our pxeloader prefer to get NFS server information by its own
instead of using cached one.
This is how it is done:
pxe_open() indirectly opens socket (PXENV_UDP_OPEN, with cached IP from
BOOTPLAYER).
After that, bootp() resolve is done, resulting in (probably) more
"val
> >
> > bce0: mem
> > 0xda00-0xdbff irq 36 at device 0.0 on pci1
> > miibus0: on bce0
> > brgphy0: PHY 1 on miibus0
> > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> > 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
> > bce0: Ethernet add
Hi Xu Zhe,
If I were you I would first of all check cables. They might be the cause.
Secondly, if cables are good, to me this report very much resembles a PR I
reported a
few weeks ago - http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/179926
Check its set and look at the patch I submitted. It's a
10 matches
Mail list logo