[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146 --- Comment #9 from Konrad --- I set LAGG on igb0 and igb1 and seems to be ok: lagg0: flags=8843 metric 0 mtu 1500 options=6403bb ether 00:1e:67:27:1d:5e inet 192.168.202.254 netmask 0xff00 broadcast 192.168.202

[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146 --- Comment #10 from Andrey V. Elsukov --- (In reply to Konrad from comment #9) > I set LAGG on igb0 and igb1 and seems to be ok: > but when ix's ports are configured as lagg1, all laggports work properly. > When I switch ix's ports as lag

[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146 --- Comment #11 from Konrad --- Yes, its reproducible. I change lagg configuration in rc.conf and reboot machine. if lagg0 will start with "ix1 flags=0" ix1 will have always "no carrier" even if I remove from laggport. Manually removed ix1

[Bug 221146] [LAGG] Problem with second laggport

2017-08-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221146 Matt Joras changed: What|Removed |Added CC||mjo...@freebsd.org --- Comment #12 fr

Program crashes after 320666

2017-08-04 Thread Kevin Oberman
multimedia/avidemux_qt4 has started dumping core with segfaults and other errors in libthread called from Qt4. I am suspicious that the real problem is in Qt4 and those errors were previously not detected and usually not causing a problem. The problem shows up with kernels at r320666 and later. Th