Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread perryh
YongHyeon PYUN wrote: > On Wed, Oct 12, 2011 at 10:07:02AM -0400, Karim wrote: > > ... why are we ORing the same call twice isn't the same thing > > as calling it once: > > > > bmsr = PHY_READ(sc, E1000_SR) | PHY_READ(sc, E1000_SR); > > The E1000_SR_LINK_STATUS bit is latched low so it should be

Re: Question about GPIO bitbang MII

2011-10-12 Thread YongHyeon PYUN
On Wed, Oct 12, 2011 at 10:42:22PM +0200, Marius Strobl wrote: > On Tue, Oct 11, 2011 at 03:55:31PM -0700, YongHyeon PYUN wrote: > > On Tue, Oct 11, 2011 at 11:23:18PM +0200, Marius Strobl wrote: > > > On Mon, Oct 10, 2011 at 12:22:38PM -0700, YongHyeon PYUN wrote: > > > > On Sun, Oct 09, 2011 at 0

Re: Question about GPIO bitbang MII

2011-10-12 Thread Marius Strobl
On Tue, Oct 11, 2011 at 03:55:31PM -0700, YongHyeon PYUN wrote: > On Tue, Oct 11, 2011 at 11:23:18PM +0200, Marius Strobl wrote: > > On Mon, Oct 10, 2011 at 12:22:38PM -0700, YongHyeon PYUN wrote: > > > On Sun, Oct 09, 2011 at 06:58:38PM +0200, Marius Strobl wrote: > > > > On Fri, Oct 07, 2011 at 1

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread YongHyeon PYUN
On Wed, Oct 12, 2011 at 04:17:09PM -0400, Karim wrote: > On 11-10-12 03:27 PM, YongHyeon PYUN wrote: > >On Wed, Oct 12, 2011 at 02:35:23PM -0400, Karim wrote: > >>Hi, > >>On 11-10-12 01:03 PM, YongHyeon PYUN wrote: > >>>On Wed, Oct 12, 2011 at 10:07:02AM -0400, Karim wrote: > >[...] > > > >>>Hmm, t

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread Karim
On 11-10-12 03:27 PM, YongHyeon PYUN wrote: On Wed, Oct 12, 2011 at 02:35:23PM -0400, Karim wrote: Hi, On 11-10-12 01:03 PM, YongHyeon PYUN wrote: On Wed, Oct 12, 2011 at 10:07:02AM -0400, Karim wrote: [...] Hmm, that indicates driver lost established link. msk(4) will detect this condition

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread YongHyeon PYUN
On Wed, Oct 12, 2011 at 02:35:23PM -0400, Karim wrote: > Hi, > On 11-10-12 01:03 PM, YongHyeon PYUN wrote: > >On Wed, Oct 12, 2011 at 10:07:02AM -0400, Karim wrote: [...] > >Hmm, that indicates driver lost established link. msk(4) will > >detect this condition and stop RX/TX MACs until it knows P

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread Karim
Hi, On 11-10-12 01:03 PM, YongHyeon PYUN wrote: On Wed, Oct 12, 2011 at 10:07:02AM -0400, Karim wrote: On 11-10-11 01:31 PM, Kevin Oberman wrote: On Tue, Oct 11, 2011 at 10:10 AM, YongHyeon PYUN wrote: On Tue, Oct 11, 2011 at 11:40:42AM -0400, Karim wrote: Hi List, Using a Marvell NIC plug

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread YongHyeon PYUN
On Wed, Oct 12, 2011 at 10:07:02AM -0400, Karim wrote: > On 11-10-11 01:31 PM, Kevin Oberman wrote: > >On Tue, Oct 11, 2011 at 10:10 AM, YongHyeon PYUN wrote: > >>On Tue, Oct 11, 2011 at 11:40:42AM -0400, Karim wrote: > >>>Hi List, > >>> > >>>Using a Marvell NIC plugged into a CISCO switch I see t

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread Adrian Chadd
Try "sysctl kern.eventtimer.idletick=1" . Someone has also reported an issue with packet loss and system freezes with idletick=0 (which is the default in -head now.) Adrian ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listi

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread Karim
On 11-10-12 11:15 AM, Karim wrote: On 11-10-12 11:08 AM, Arnaud Lacombe wrote: Hi, On Wed, Oct 12, 2011 at 10:07 AM, Karim wrote: [...] Hi, Thanks for the feedback and detailed information. I have to clarify here; I get the issue even with forcing full duplex. The driver modifications ar

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread Karim
On 11-10-12 11:08 AM, Arnaud Lacombe wrote: Hi, On Wed, Oct 12, 2011 at 10:07 AM, Karim wrote: [...] Hi, Thanks for the feedback and detailed information. I have to clarify here; I get the issue even with forcing full duplex. The driver modifications are minor and shouldn't affect link neg

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread Arnaud Lacombe
Hi, On Wed, Oct 12, 2011 at 10:07 AM, Karim wrote: >> [...] > Hi, > > Thanks for the feedback and detailed information. > > I have to clarify here; I get the issue even with forcing full duplex. > > The driver modifications are minor and shouldn't affect link negotiation or > link state. [...] >

Re: kern/145600: TCP/ECN behaves different to CE/CWR than ns2 reference

2011-10-12 Thread remko
Synopsis: TCP/ECN behaves different to CE/CWR than ns2 reference Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: remko Responsible-Changed-When: Wed Oct 12 14:50:09 UTC 2011 Responsible-Changed-Why: Reassign to networking team. Network people, this already had been

Re: if_msk.c link negotiation / packet drops

2011-10-12 Thread Karim
On 11-10-11 01:31 PM, Kevin Oberman wrote: On Tue, Oct 11, 2011 at 10:10 AM, YongHyeon PYUN wrote: On Tue, Oct 11, 2011 at 11:40:42AM -0400, Karim wrote: Hi List, Using a Marvell NIC plugged into a CISCO switch I see the auto-negotiation failing and even when forcing the device to full-duplex