[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

--- Comment #4 from Bhargava Chenna. Marreddy  
---
Hi Dev,

Did you get chance to try the steps as per comment #1?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

Marek Zarychta  changed:

   What|Removed |Added

 CC||zarych...@plan-b.pwste.edu.
   ||pl

--- Comment #5 from Marek Zarychta  ---
It could be firmware incompatibility flaw. For a couple of motherboards with
NetXtreme BCM5761 integrated NICs, these NICs haven't worked for me either.
Only FreeBSD was affected. Symptoms were the same and hardware worked fine
under Linux. Update of Broadcom Integrated NIC Firmware in my case has resolved
the issue.

The exact hardware model was:

bge0@pci0:63:0:0:   class=0x02 card=0x3047103c chip=0x168114e4 rev=0x10
hdr=0x00
vendor = 'Broadcom Inc. and subsidiaries'
device = 'NetXtreme BCM5761 Gigabit Ethernet PCIe'
class  = network
subclass   = ethernet

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

--- Comment #6 from d...@syix.com ---
Revisiting this after 3 years...
Now using Freebsd 12
All 4 interfaces start and operate as would be expected.  Nothing has changed
on the server since the extensive attempts to make it work 3 years ago (its
mostly retired now) but all 4 ports are alive and well today.  I did try
different hardware flashes, and gobs of different settings to try to make them
work with no joy.

Could try with Freebsd 11 again I guess, but really, it works, do we care?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


igb(4) media status incorrect when disconnected

2019-04-16 Thread Nick Rogers
Hello,

In 12.0-RELEASE, STABLE, and 13-CURRENT,  gb(4) interfaces report an
incorrect media status after they are disconnected (ethernet cable
unplugged). Ifconfig reports active + autoselect/1000baseT when it should
report inactive.

I filed a bug for this a few weeks ago and have not had any luck...
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724

I am wondering if anyone in this list has any ideas or can help me begin to
pinpoint where things are breaking down. My current thought is either the
driver does not receive the interrupt when its unplugged, or something else
is wrong, but I am unsure how to verify this. An ifconfig down + up always
resolves it (corrects the status).

Thank you.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

Eugene Grosbein  changed:

   What|Removed |Added

 Status|New |Closed
 Resolution|--- |FIXED

--- Comment #7 from Eugene Grosbein  ---
Submitter reports the problem's solved with update to FreeBSD 12.0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 195191] rtadvd(8): Retry on NET_RT_IFLIST sysctl failure like getifaddrs

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195191

Kubilay Kocak  changed:

   What|Removed |Added

   Assignee|h...@freebsd.org |n...@freebsd.org
   Severity|Affects Only Me |Affects Some People
 CC||n...@freebsd.org
  Flags||mfc-stable12?
Summary|[patch] rtadvd(8): rtadvd   |rtadvd(8): Retry on
   |should retry on |NET_RT_IFLIST sysctl
   |NET_RT_IFLIST sysctl|failure like getifaddrs
   |failure like getifaddrs |

--- Comment #4 from Kubilay Kocak  ---
Reset assignee, timeout (2 years)

@Hiroki If you can still take care of this issue, please re-assign yourself

@All If the existing patch (attachment 149611) no longer applies against
CURRENT, it would be great if someone could rebase it to HEAD and confirm that
it still resolves the issue for their use case

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 237197] ipnat dropping connections after upgrade to 11.2

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237197

Kubilay Kocak  changed:

   What|Removed |Added

  Flags||mfc-stable11?
   Keywords||needs-patch
 CC||c...@freebsd.org

--- Comment #11 from Kubilay Kocak  ---
Can we identify a set of bugs (PR's) and/or commits that can/should be merged?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

Kubilay Kocak  changed:

   What|Removed |Added

   Severity|Affects Many People |Affects Some People
 Resolution|FIXED   |Overcome By Events

--- Comment #8 from Kubilay Kocak  ---
Since we don't have a identified or definitive resolver (commit(s)),
resolution: Overcome By Events

This is technically still an issue on FreeBSD 11.x, which is not EoL. If
someone can either identify a set of commits OR PR's that need to be merged to
stable/11 or can reproduce the issue on 11.x with the reported hardware, please
re-open the issue with further details

While I'm here, correct 'Version', which was set for CURRENT (ambiguous), but
the report was for 9.x-11.x

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

Kubilay Kocak  changed:

   What|Removed |Added

 CC||n...@freebsd.org
Version|CURRENT |11.2-RELEASE

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 236819] [tcpdump] capsicum-related changes broke reading IPsec ESP decryption keys from a file

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236819

Kubilay Kocak  changed:

   What|Removed |Added

  Flags||mfc-stable11?,
   ||mfc-stable12?
 CC||n...@freebsd.org
   Keywords||regression
 Status|New |Open

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

--- Comment #9 from Eugene Grosbein  ---
(In reply to Kubilay Kocak from comment #8)

Just to clarify: initial report dates back to January of 2016 while
11.0-RELEASE occured in October of 2016. It is unknown if 11.2-STABLE or
11.2-RELEASE have the problem and changes are bge(4) is already fixed there.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 237197] ipnat dropping connections after upgrade to 11.2

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237197

Cy Schubert  changed:

   What|Removed |Added

 Resolution|--- |Overcome By Events
 Status|Open|Closed

--- Comment #12 from Cy Schubert  ---
11.2-RELEASE does not have nor will it have the ipnat patches applied. You must
wait for 11.3-RELEASE, which IIRC should be GA over summer sometime.

You can svnup your sources to 11-STABLE, which has the fix, or install the
patch directly to your 11.2-RELEASE instead.

All ipfilter patches have been MFCed to 11-STABLE and 12-STABLE. Some have been
MFCed to 10-STABLE however since -CURRENT has diverged too much from 10-STABLE
I an no longer MFCing to it any more.

Wait for 11.3-RELEASE.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

--- Comment #10 from Kubilay Kocak  ---
(In reply to Eugene Grosbein from comment #9)

Thanks Eugene, I'll re-enable earlier versions and set it to 10.2-RELEASE
(Release date: 2015-08-06) so its... less incorrect.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 206168] Broadcom 57xx fails on any version of FreeBSD

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206168

Kubilay Kocak  changed:

   What|Removed |Added

Version|11.2-RELEASE|10.2-RELEASE

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 237197] ipnat dropping connections after upgrade to 11.2

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237197

Kubilay Kocak  changed:

   What|Removed |Added

 Resolution|Overcome By Events  |FIXED
   Assignee|n...@freebsd.org |c...@freebsd.org
   Keywords|needs-patch, needs-qa   |
  Flags|mfc-stable11?   |mfc-stable11+,
   ||mfc-stable12+

--- Comment #13 from Kubilay Kocak  ---
(In reply to Cy Schubert from comment #12)

I understood the request as being for any changes not yet merged (if any were
identified), to be merged to stable/11, not releng/11.2 (where only major
'errata/security' bugs are merged). From your comment, that seems that the fix
to this issue has already been resolved, and merged to both (11, 12) stable
branches, with fixes to be included in 11.3-RELEASE.

Do any other PR exist that references the relevant ipnat commits, so this bug
can be set to depend on them?

With @triage hat:

- Set resolution FIXED: with resolution: update to stable/11 or stable/12
- Assign to committer that resolved (thank you Cy!)
- Set mfc-* flags to track that resolution was merged to both (11, 12) stable
branches

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 237197] ipnat dropping connections after upgrade to 11.2

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237197

Rodney W. Grimes  changed:

   What|Removed |Added

 CC||n...@freebsd.org

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 194485] Userland cannot add IPv6 prefix routes

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194485

Kubilay Kocak  changed:

   What|Removed |Added

   Assignee|h...@freebsd.org |n...@freebsd.org
   Severity|Affects Only Me |Affects Some People
   See Also||https://reviews.freebsd.org
   ||/D15404,
   ||https://reviews.freebsd.org
   ||/D15405,
   ||https://reviews.freebsd.org
   ||/D15406
 CC||n...@freebsd.org
  Flags||mfc-stable11?,
   ||mfc-stable12?
   Keywords|easy, patch |

--- Comment #6 from Kubilay Kocak  ---
Assignee timeout (11 months), reset assignee

If the reviews don't still apply to head, we may need a single
cumulative/complete patch (from each of the three reviews, if/where
applicable), rebased against latest head.

@Christopher Can you clarify which one or more of the three reviews was used
(applied) that resulted in a successful outcome?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 194485] Userland cannot add IPv6 prefix routes

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194485

--- Comment #7 from Christopher Hall  ---
All three reviews were applied to make it work and were applied in order.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 194485] Userland cannot add IPv6 prefix routes

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194485

--- Comment #8 from Christopher Hall  ---
Just the three reviews were used - the patch in this bug report was NOT used, I
thinke the combination of the three reviews is sufficient

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 194485] Userland cannot add IPv6 prefix routes

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194485

Kubilay Kocak  changed:

   What|Removed |Added

 Attachment #148500|0   |1
is obsolete||

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 194485] Userland cannot add IPv6 prefix routes

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194485

Kubilay Kocak  changed:

   What|Removed |Added

   Keywords||patch

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"