https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191786
Alexander Vereeken changed:
What|Removed |Added
CC||Alexander88207@protonmail.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191786
Graham Perrin changed:
What|Removed |Added
Keywords||patch
--- Comment #4 from Graham P
Am 18.09.2019 um 08:21 schrieb Harry Schmalzbauer:
Am 11.05.2018 um 19:26 schrieb Harry Schmalzbauer:
Bezüglich Harry Schmalzbauer's Nachricht vom 10.05.2018 21:17
(localtime):
Hello,
if I pull the TP connection from my i217 Clarkville, HEAD still reports
media
1000Base-T status "active".
On 12/01/16 13:07, Pieper, Jeffrey E wrote:
> Sean,
>
> This is a client (em) part, and should be 10CE (Boazman/Boulder Creek).
>
> Jeff
Yeah, you're right. I think I transposed some numbers instead of
copy/paste.
Do you have this part lying around to test against?
sean
signature.asc
Des
-Original Message-
From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On
Behalf Of Sean Bruno
Sent: Thursday, December 01, 2016 9:53 AM
To: freebsd-net@freebsd.org
Subject: Re: Intel 82567V-2 using em driver, no carrier or constant link-state
changes with
On 11/27/16 12:40, Michael Knap wrote:
> Preface: I've been a long-time linux user, and I am enjoying the BSD
> experience. For the following scenario, I have reproduced these results
> with 3 or more cables which are known to be good.
>
> Using FreeBSD 10.3 Stable :
> FreeBSD 10.3-STABLE #0 r29
Preface: I've been a long-time linux user, and I am enjoying the BSD
experience. For the following scenario, I have reproduced these results
with 3 or more cables which are known to be good.
Using FreeBSD 10.3 Stable :
FreeBSD 10.3-STABLE #0 r295946+07c41cd(9.10-STABLE): Wed Nov 9 00:19:25
UTC 20
Summary|bce link state changes to |[bce] [patch] bce link
|same state are ignored by |state changes to same state
|lagg|are ignored by lagg
--- Comment #3 from Mark Linimon ---
Over to maintainers.
--
You are receiving this mail
> Revision 205024 - (annotate)
> Thu Mar 11 17:56:46 2010 UTC (2 months, 3 weeks ago) by qingli
>
> The if_tap interface is of IFT_ETHERNET type, but it
> does not set or update the if_link_state variable.
> As such RT_LINK_IS_UP() fails for the if_tap interface.
>
> Also, the RT_LINK_IS_UP() needs
ad
similar problems. The problem occurs with all if_bge.c versions less
than maybe a year old (I haven't investigated in detail).
Cutting a long story short, it seems that somewhere along the line some
code accounting for encoding errors incorrectly showing up as link state
changes has been los
> That's the development branch. I'm talking about the driver version.
> Inside the if_bce.c file, you will find this:
>
> /**
>**/ /* BCE Driver Version
> */
> /***
--On Monday, September 25, 2006 19:20:22 +0400 Ilya Nikitin
<[EMAIL PROTECTED]> wrote:
Which driver version is that? I had to update the if_bce.c file from
version 0.9.5 to 0.9.6 to correct a problem with the NIC ceasing to pass
traffic and requiring a reboot to restore connectivity. (I'm runn
>
> Which driver version is that? I had to update the if_bce.c file from
> version 0.9.5 to 0.9.6 to correct a problem with the NIC ceasing to pass
> traffic and requiring a reboot to restore connectivity. (I'm running 6.1
> RELEASE.)
>
> Is this a newer version?
Yes, it's strongly newer:
if_b
--On Monday, September 25, 2006 10:51:54 +0400 Ilya Nikitin
<[EMAIL PROTECTED]> wrote:
On 9/21/06, Gleb Smirnoff <[EMAIL PROTECTED]> wrote:
No change. The link state is still floating.
/S
I've solved this problem by using bge drivers from 6.2-BETA1. There
aren't bge flapping now !!!
Wh
> On 9/21/06, Gleb Smirnoff <[EMAIL PROTECTED]> wrote:
>
> No change. The link state is still floating.
>
> /S
I've solved this problem by using bge drivers from 6.2-BETA1. There aren't bge
flapping now !!!
Ilya Nikitin, Syste
On 9/21/06, Gleb Smirnoff <[EMAIL PROTECTED]> wrote:
On Thu, Sep 21, 2006 at 12:32:56PM +0200, Slawek Zak wrote:
S> >Please try to add hw.bge.fake_autoneg=1 to /boot/loader.conf. May be
S> >this will help.
S>
S> I did it, but sysctl doesn't show the value.
S>
S> w3-6# sysctl hw.bge
S> sysctl: unk
On Thu, Sep 21, 2006 at 12:32:56PM +0200, Slawek Zak wrote:
S> >Please try to add hw.bge.fake_autoneg=1 to /boot/loader.conf. May be
S> >this will help.
S>
S> I did it, but sysctl doesn't show the value.
S>
S> w3-6# sysctl hw.bge
S> sysctl: unknown oid 'hw.bge'
S>
S> This sysctl seems to be defi
code. When
S> I disable internal port on chassis built-in ethernet switch, kernel
S> floods syslog with messages about link state changes and coalescing
S> them. Log snippet follows:
S>
S> Sep 13 14:58:28 w3-6 kernel: bge1: link state changed to DOWN
S> Sep 13 14:58:28 w3-6 kernel:
t-in ethernet switch, kernel
S> floods syslog with messages about link state changes and coalescing
S> them. Log snippet follows:
S>
S> Sep 13 14:58:28 w3-6 kernel: bge1: link state changed to DOWN
S> Sep 13 14:58:28 w3-6 kernel: bge1: link state changed to UP
S> Sep 13 14:58:29 w3
On 9/13/06, David Christensen <[EMAIL PROTECTED]> wrote:
I can't access the information on this web site through Mozilla after
clicking "I Accept".
Hm. I've just found out that posting direct links to documents is too
Web 1.0 for ibm.com. Here is link to the parent page - works for me:
http://
> I'm testing network failover on IBM BladeCenter running FreeBSD 6.1
> STABLE for Sep 6th.
>
> I suspect a problem with link state change detection in bge code. When
> I disable internal port on chassis built-in ethernet switch, kernel
> floods syslog with messages about
Hi,
I'm testing network failover on IBM BladeCenter running FreeBSD 6.1
STABLE for Sep 6th.
I suspect a problem with link state change detection in bge code. When
I disable internal port on chassis built-in ethernet switch, kernel
floods syslog with messages about link state change
22 matches
Mail list logo
