On Thu, 8 Feb 2007, I wrote:
6.2 seems to be missing your fix for the time_uptime time warp -- after
"route delete #remotehost", the negative expire time is slightly less
$
than the uptime under 6.2, but it apparently should be slightly less
than 0 as in ~5.2 and -current. I d
On Wed, 7 Feb 2007, Bruce Evans wrote:
On Wed, 7 Feb 2007, Oleg Bulyzhin wrote:
On Wed, Feb 07, 2007 at 01:31:39AM +1100, Bruce Evans wrote:
I use jdp's quicker fix. It works fine for detecting cable unplug
and replug, but link detection is still very bad at boot time and
I've now tested y
On Wed, 7 Feb 2007, Oleg Bulyzhin wrote:
On Wed, Feb 07, 2007 at 01:31:39AM +1100, Bruce Evans wrote:
I use jdp's quicker fix. It works fine for detecting cable unplug
and replug, but link detection is still very bad at boot time and
after down/up (seems to be worse for down/up than unplug/rep
On Wed, Feb 07, 2007 at 01:31:39AM +1100, Bruce Evans wrote:
> On Tue, 6 Feb 2007, Oleg Bulyzhin wrote:
>
> >Sorry for the late reply - i was AFK for some time and didnt read mails.
> >Patch against 6.2R attached, please let me know does it helps or not.
>
> I didn't test the old version of this
On Tue, 6 Feb 2007, Oleg Bulyzhin wrote:
Sorry for the late reply - i was AFK for some time and didnt read mails.
Patch against 6.2R attached, please let me know does it helps or not.
I didn't test the old version of this since I have too many local changes
in my non-6.x versions. I might tes
Ok, I have patched and rebuild the kernel. Looks ok now.
Here some info:
media 100baseTX mediaopt full-duplex
serverA (Broadcom BCM5705K) <192.168.254.1/30> (iperf server)
serverB (Broadcom BCM5704) <192.168.254.2/30> (iperf client)
# iperf -c 192.168.254.1 -t 60 -i 5
--
On Thu, Jan 25, 2007 at 05:05:32PM +0100, Robin Gruyters wrote:
> On 13-Jan-2007 Oleg Bulyzhin wrote:
> >
> >> Could you please test attached patch? It should fix ierrs issue
> >and should not
> >> break link events (would be fine to test it: unplug/plug cable,
> >try to change
> >> media with
Quoting Bruce Evans <[EMAIL PROTECTED]>:
On Thu, 25 Jan 2007, Robin Gruyters wrote:
On 13-Jan-2007 Oleg Bulyzhin wrote:
Could you please test attached patch? It should fix ierrs issue and
should not
break link events (would be fine to test it: unplug/plug cable, try
to change
media with
On Thu, 25 Jan 2007, Robin Gruyters wrote:
On 13-Jan-2007 Oleg Bulyzhin wrote:
> Could you please test attached patch? It should fix ierrs issue and
should not
> break link events (would be fine to test it: unplug/plug cable, try to
change
> media with ifconfig, change media on other end of
On 13-Jan-2007 Oleg Bulyzhin wrote:
> Could you please test attached patch? It should fix ierrs issue
and should not
> break link events (would be fine to test it: unplug/plug cable,
try to change
> media with ifconfig, change media on other end of wire).
>
Hi ya,
Just wondering will this
On 13-Jan-2007 Oleg Bulyzhin wrote:
>> Could you please test attached patch? It should fix ierrs issue and should
>> not
>> break link events (would be fine to test it: unplug/plug cable, try to change
>> media with ifconfig, change media on other end of wire).
>>
>
> Oops, previous patch was in
On Sat, Jan 13, 2007 at 01:14:55PM +0300, Oleg Bulyzhin wrote:
> On Tue, Jan 09, 2007 at 04:14:16PM -0800, John Polstra wrote:
>
> > I've been using #2 today, and it's working well so far. I
> > implemented it like this. (Ignore the version numbers; I'm working
> > in a private repository.)
> >
On Tue, Jan 09, 2007 at 04:14:16PM -0800, John Polstra wrote:
> I've been using #2 today, and it's working well so far. I
> implemented it like this. (Ignore the version numbers; I'm working
> in a private repository.)
>
> --- if_bge.c8 Jan 2007 22:46:51 - 1.26
> +++ if_bge.c9
On Mon, Jan 08, 2007 at 04:33:29PM -0800, John Polstra wrote:
> On 30-Dec-2006 Bruce Evans wrote:
> > More debugging showed that almost any of the reads of the phy in mii
> > cause an input error,
>
> The errors appear to be caused by the code in bge_miibus_{read,write}reg
> that clears and then r
On 09-Jan-2007 Oleg Bulyzhin wrote:
> On Mon, Jan 08, 2007 at 04:33:29PM -0800, John Polstra wrote:
>> On 30-Dec-2006 Bruce Evans wrote:
>> > More debugging showed that almost any of the reads of the phy in mii
>> > cause an input error,
>>
>> The errors appear to be caused by the code in bge_miib
On 30-Dec-2006 Bruce Evans wrote:
> More debugging showed that almost any of the reads of the phy in mii
> cause an input error,
The errors appear to be caused by the code in bge_miibus_{read,write}reg
that clears and then restores the BGE_MIMODE_AUTOPOLL bit of the
BGE_MI_MODE register. If you r
On Tue, 2 Jan 2007, David Christensen wrote:
These happen under loads that can't be handled, and generally cause
thousands of input errors every second. The hardware records dropped
packets separately from other input errors, but unfortunately
all types
of input errors are counted together in i
> These happen under loads that can't be handled, and generally cause
> thousands of input errors every second. The hardware records dropped
> packets separately from other input errors, but unfortunately
> all types
> of input errors are counted together in if_ierrors, and I haven't done
> more
On Sun, 31 Dec 2006, Bruce Evans wrote:
[cc changed from developers to net]
On Wed, 13 Dec 2006, Bruce Evans wrote:
On Tue, 12 Dec 2006, Doug Barton wrote:
This guy's first message about this problem was very detailed, and he
seems highly motivated. Anyone want to help him out?
This might
[cc changed from developers to net]
On Wed, 13 Dec 2006, Bruce Evans wrote:
On Tue, 12 Dec 2006, Doug Barton wrote:
This guy's first message about this problem was very detailed, and he
seems highly motivated. Anyone want to help him out?
This might be because bge now actually reports error
20 matches
Mail list logo
