Re: kern/134658: [bce] bce driver fails on PowerEdge m610 blade.

2010-01-20 Thread Oliver Fromme
David Christensen wrote (on 2009-08-01): > Sorry, this is the 5709S and I haven't had an opportunity to > implement this PHY yet. Unfortunately it's more than just a > change to miidevs since the SerDes is actually an IEEE clause > 45 compliant device (instead of the more common Clause 22 >

Re: "PHY read timeout" with bce2 & 3 on FreeBSD 8.0

2010-01-20 Thread Charles Owens
Pyun YongHyeon wrote: > On Mon, Jan 18, 2010 at 10:40:55AM -0500, Charles Owens wrote: >> Hello, >> >> I'm working with a system (IBM System x3550 M2) that has four onboard >> bce(4) NICs. Using FreeBSD 8.0, the first two seem to function fine, >> but the second two do not, yielding messages like

RE: kern/134658: [bce] bce driver fails on PowerEdge m610 blade.

2010-01-20 Thread David Christensen
> While trying to debug the same issue I stumbled across this > thread ... We've got HS22 blades (IBM BladeCenter) which > habe the BCM5709S and suffer from exactly the same problem. > > Dave, are there any news regarding the PHY implementation? > > If there's decent documentation I might even

best way to optimize ipfw-dummynet interaction ?

2010-01-20 Thread Luigi Rizzo
Hi, I am trying to solve the following problem: when ipfw passes a packet to dummynet, the packet is tagged with a 'pipe number' which dummynet needs to look up to find the pointer to the correct object -- something like this: IPFW_LOCK() rule = find_matching_rule(); 1. ... p

Re: kern/134658: [bce] bce driver fails on PowerEdge m610 blade.

2010-01-20 Thread Hugo Koji Kobayashi
On Wed, Jan 20, 2010 at 10:57:15AM -0800, David Christensen wrote: > > While trying to debug the same issue I stumbled across this > > thread ... We've got HS22 blades (IBM BladeCenter) which > > habe the BCM5709S and suffer from exactly the same problem. > > > > Dave, are there any news regard

RE: bce(4) BCM5907 CTX write errors on 7.2 driver

2010-01-20 Thread David Christensen
> > Thanks for testing. I want to pass the changes by a couple other > > people before I go ahead with a commit. > > > > Dave > > > > Hi Dave, > > I was just wondering when these changes will hit the tree, I have been > running your patch in production for some time now and all seems well. J

Re: kern/143034: [panic] system reboots itself in tcp code [regression]

2010-01-20 Thread linimon
Old Synopsis: system reboots itself New Synopsis: [panic] system reboots itself in tcp code [regression] Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Jan 20 21:58:59 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). h

RE: kern/134658: [bce] bce driver fails on PowerEdge m610 blade.

2010-01-20 Thread David Christensen
> > > If there's decent documentation I might even give it a > try myself, > > > provided that it's not too complex. (I've done hardware > programming > > > before, but I've never touched a NIC/PHY driver, except for very > > > trivial fixes.) > > > > > > > Pyunh has taken an active interes

freeBSD8.0 multicast routing problem

2010-01-20 Thread yanqing you
how to enable multicast routing in freeBSD8.0,please give the steps of configuration. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: kern/143046: [mxge] [panic] panics since mxge(4) update

2010-01-20 Thread linimon
Old Synopsis: panics since mxge(4) update New Synopsis: [mxge] [panic] panics since mxge(4) update Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 21 04:56:43 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://